Post a Comment
I'd have to agree, Fedora Core is not really your best choice in the server space. The only reason you might want to use it on a server is for applications that require cutting-edge functionality not yet available elsewhere.
A better choice for those needing a RedHat-ish Linux server would be RedHat Enterprise Linux or one of its many free derivatives such as CentOS http://www.centos.org/
I was bemused to see that the author only created /, /boot and swap partitions - I think this isn't too clever for a server setup myself. I usually create a "/otheros" partition which is set to the same size as "/" (which I'm now setting to 6GB for servers to make sure there's at least 2GB free after OS installation) - this allows me to cold install a later OS should I want to upgrade at a later date and still have an immediate fallback to the original OS (I never "warm upgrade" a production server straight into its current "/" partition - too risky, IMHO).
Whatever space is left (usually the vast majority if you've got a reasonably large RAID setup), I call "/data", so that I can store non-system files away from "/" (or, where necessary, soft-link across from / to /data for some trees).
BTW, I think Fedora Core 4 is a little bit too "new" to employ on a production server yet - I'd put it on a test server and let it stew for a bit (especially to pick up the inevitably bug fixes that come in the first few months of its life). It's why I'm running Fedora Core 2 still on a lot of my boxes (despite the whinges from people out there, it's pretty stable and I think good enough for production services, as is probably FC3 - which, let's not forget, is what RHEL 4 is based on).
If I am correct in understanding your requirement, there is a method for installing "unassisted" it is called kickstart and has been a feature of RedHat Linux/RHEL/Fedora for years.
I Use it all the time. Do a sample install with the GUI, tick the relevant box to generate your kickstart file. At the end, save to floppy/cd/medium of choice and you can use it over and over again.
One of my top criteria for building a production system is all about repeatability. By using a ks file then you are sure that you can build the same underlying core system time and time again quickly and easily.
I use Fedora for servers. Yes they are not in a production environment but the "bleeding edge" nature of the distro is just what I want so that I can get a taste of what is to come in RHEL etc and can make my code ready for future versions of RHEL.
I also like the improved HW coverage OOTB in Fedora.
meh, my server is Fedora Core 4, having been network updated from Fedora Core 2 - works like a charm.
Since it's for personal use, I don't care all that much about uptime, but I have yet to see it crash, it's been running perfect.
As for a more advanced server, you wouldn't use this guide anyway. Which is what botheres me - it comes off as a n00b guide, yet it does a LOT of stuff that are irrelevant for newbies.



