Hi,

I am trying to use kickstart installation for knowledge gain(well to be specific I am preparing for RHCE exam). I prepared an installation floppy with bootnet.img from first installation CD(RH 8.0) and copied my kickstart configuration file (ks.cfg) on this floppy.(cp ks.cfg /mnt/floppy/.)

After that I use this floppy to install Linux using vmware. But when I type

linux ks=floppy

it doesn't take configuration from kickstart file kept on floppy. Instead it starts the installation process in usual way asking "Which media contains installation files?".

I am not able to think of any problem as to why doesn't it look at kickstart configuration file as specified at boot prompt.

Please please help.

Thanks & regards,
Deepika

try

linux ks=file:fd0/ks.cfg

I tried

linux ks=file:fd0/ks.cfg

and It says

Error opening: kickstart file fd0/ks.cfg: no such file or directory

But I am wonderig if this is the correct option I should give as according to Red Hat manuals ->

------------------------------------------------------------------------------------
ks=file:/<file>
The installation program will try to read the file <file> from the filesystem; no mounts will be done. This is normally used if the kickstart file is already on the initrd image

-------------------------------------------------------------------------------

Which doesn't seem to be my case. Am I right?
Please advice.

I guess I'm following a different procedure from you

Mine is based on using the cd to intially boot to the boot prompt

Make kickstart file

create a DOS floppy

mcopy ks.cfg a:

Boot from CD

linux ks=file:fd0/ks.cfg

I guess seeing as you are doing the certification you have to get it going a
specific way though

If your booting from floppy maybe you miss out the actual reference to the drive as it's already on the disk
linux ks=file:/ks.cfg

I also tried it through NFS as below

linux ks=nfs:9.2.172.52:/nfs/exports/ks.

where /nfs/exports is configured to be mounted by everyone on other linux m/c.

but this also does the same thing. It doesn't look for kickstart file on specified NFS server and starts it's own usual installation.

Any idea if this has anything to do with vmware? Though I don't think so.