Help Kickstart

[Tod Thomas]

gb spam wrote:
>>I have been trying to get a kickstart install to work off and on for
>>about a week now.  I finally did a minimal install of FC4 on my box, got
>>the anaconda-ks.cfg file, copied it to a floppy, and uncommented out the
>>part lines just to see if I could get a non-customized kickstart install
>>to work.  No joy.
>>
>>The only thing I can think of is that I have a SCSI hard drive and that
>>the installer can't recognize.  My SCSI dvd drive I'm doing the install
>>from is recognized though and works fine, that's how I did the minimal
>>installation.
>>
>>I'm using the original FC4 ISO images from the FC4 website.  At the
>>prompt I use ks=floppy:/ks-cfg.  I have the ks.cfg on an ext2 formatted
>>floppy disk.  The floppy is fine, and anaconda is reading it.
>>
>>What could I be doing wrong?  I'll be happy to post my ks.cfg if it will
>>help.
> 
> 
> So... what didn't work?
> 
> Have you tried system-config-kickstart?
> 

I'm trying to get a stable build set up for all of my machines so I was 
trying to recreate the build I had on another machine so it could be 
repeated.  I want only a specific set of packages and 
system-config-kickstart only allows the selection of groupings.

So, I tried system-config-kickstart last night.  I used it to get an 
'everything' build working on my other machine, and then took the 
package listing from the anaconda-ks.cfg of the original custom build 
and slid it underneath the %packages --resolvedeps directive and tried 
again.  It failed trying to resolve the dependencies for the @ office 
group.  It put me into a Python debugging session afterwards.

Does the fact that I'm attempting this from a floppy and the RPM's are 
on a set of removeable CD's make any difference?  Perhaps --resolvedeps 
can't do its work because it can't see all the RPM's at install time?

Thanks - Tod