Linked by Andrew Youll on Sun 24th Jul 2005 21:01 UTC, submitted by Falko Timme
Permalink for comment 8622
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



Member since:
2005-07-22
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.