I run Fedora 10 on my work PC. I was about to upgrade to Fedora 12 but decided (appropriately) to let my boss try it out first. He's had a heck of a time out of it. Lots of problems with avhi screwing up DNS for him amongst other things.
You may want to disable Network Manager and kinda revert to the old school way of configuring your NIC. As someone recommended earlier, you can edit the files in /etc/sysconfig/network-scripts and set info there.
If you're more of a pointy-clicky guy, make sure that system-config-network is installed:
Code:
yum install system-config-network
and then:
Code:
yum remove NetworkManager
That should fix your network config problems and bring you back to a config method you're used to. Network Manager is great for a laptop connecting to random wifi networks, but for a server, it's just another hassle.
Aside from running Fedora on my workstation, my department manages approximately 200 CentOS 5.3 / RHEL 5.3 servers. Keep in mind that Fedora is basically a "rolling beta" for redhat, so release versions of Fedora are still considered "beta" to the RH team. If you can stay one iteration behind the latest Fedora release (IE, Fedora 11) then you'll likely have a better experience.
Of course, you could always go with CentOS as well. I like the prettiness of Fedora better though. Combine Fedora with Compiz Fusion and a supported 3D video card and you have serious nerd eye candy. (Very much not recommended for a server environment though)
So, in summation, I recommend Fedora for workstation environments and CentOS for server environments.
As far as SELinux...
SELinux should be marketed as the offical open source package of Evil.
Learn "audit2allow" very well, it will help you. A handy trick with selinux is to set the system to "permissive" for a short while (long enough to let the system do everything it should, maybe a few days?)
And then:
Code:
cd ~
grep denied /var/log/audit/audit.log > deny.log
audit2allow -M MyPolicy < deny.log
semodule -i MyPolicy.pp
setenforce "Enforcing"
Basically, that will grab all of the denied messages that were generated during normal operation and make a custom rule-set to allow those items inside of the enforcing policy. Once done, it will allow all your normal processes to run happily, but still deny any unexpected activity.
Also, "sealert -b" will pop open the browser app. Set it to email you on denial if you haven't done so already.
Thanks for running an awesome forum!
Good luck, and ride safe.
~Scott
