rmoroz
10th June 2009, 01:47 AM
I'm trying to create an unattended install disk for Fedora 10 that I can use on isolated computers (i.e. no internet connection). The purpose is to perform a standardized install of Fedora on a PC that will perform some server functions (DHCP, LDAP, SAMBA) and install additional packages (VLC, Amorak) in a lab environment. After searching on-line, most posts seem geared towards setting up a NFS share but that won't work in this circumstance.
I've had limited success using Revisor. I can create a CD/DVD successfully and it will boot, load anaconda, format the file system, and then at about the time it should start installing packages, it stops and asks for networking information. Since the box is stand-alone, entering a static IP or setting it to DHCP has no effect and I end up exiting out. At which time it tells me that it can't find a repository needed to install a package (no specifics given). I can drop to a shell but can't find a log file with more specific information.
I say 'limited success' because if I configure the kickstart file with minimal package groups (@base, @core, @gnome-desktop), this disk will work properly and install without complaining. However, when I add all the packages I need, I get the same error again. I'd hate to have to create a disk by adding files to kickstart one by one and rebuilding it each time.
I've also tried using livecd-creator but the resulting images require (I think) to boot into the live environment first, then install to HDD.
So here's what I need help with:
1. Does livecd require you to do the above or can you make it just install to HDD right from boot?
2. Is there a way to disable the need for network support on an disk created by Revisor?
3. If, in fact, my problem is a missing package that is causing anaconda to complain, is there a way to track down that individual package so I can verify that it's on the created disk?
4. Also, does anyone know if Revisor has a similar command-line option as livecd to point to a cache of previously downloaded packages so that it doesn't have to re-download them each time?
Any help/guidance would be appreciated.
Rocky
I've had limited success using Revisor. I can create a CD/DVD successfully and it will boot, load anaconda, format the file system, and then at about the time it should start installing packages, it stops and asks for networking information. Since the box is stand-alone, entering a static IP or setting it to DHCP has no effect and I end up exiting out. At which time it tells me that it can't find a repository needed to install a package (no specifics given). I can drop to a shell but can't find a log file with more specific information.
I say 'limited success' because if I configure the kickstart file with minimal package groups (@base, @core, @gnome-desktop), this disk will work properly and install without complaining. However, when I add all the packages I need, I get the same error again. I'd hate to have to create a disk by adding files to kickstart one by one and rebuilding it each time.
I've also tried using livecd-creator but the resulting images require (I think) to boot into the live environment first, then install to HDD.
So here's what I need help with:
1. Does livecd require you to do the above or can you make it just install to HDD right from boot?
2. Is there a way to disable the need for network support on an disk created by Revisor?
3. If, in fact, my problem is a missing package that is causing anaconda to complain, is there a way to track down that individual package so I can verify that it's on the created disk?
4. Also, does anyone know if Revisor has a similar command-line option as livecd to point to a cache of previously downloaded packages so that it doesn't have to re-download them each time?
Any help/guidance would be appreciated.
Rocky
