I'm continuing with my trials and tribulations in the quest for a working kickstart. Currently, I have a copy of my ks.cfg in my boot image's initrd.img and point to that with the "ks=file:/ks.cfg" -- I also have one in the root directory of the cdrom and point to that with the "ks=cdrom:/ks.cg". This had the benefit of getting rid of the error "Cant copy to /tmp/ks.cfg" ; I would have to think that it's finding the ks.cfg file and using it in both instances. However, after this seeming progress, it goes into the regular install program. This is using a tested ks.cfg which has worked in the past in installs using floppies. By the way, I just wanted to mention to the people who frequent this list how impressed at how helpfull you have all been. I appreciate it a lot. Below is the ks.cfg and below that, my sysconfig. ks ===================================== ============================================================== # Kickstart file automatically generated by anaconda. # ks.cfg install lang en_US langsupport --default en_US.iso885915 en_US.iso885915 keyboard us mouse msintellips/2 --device psaux xconfig --card "ATI Mach64" --videoram 8192 --hsync 31.5-48.5 --vsync 50-70 --re solution 1024x768 --depth 32 rootpw --iscrypted $1$CªÇTÑW2A$vgJP8Y3jcdap4NKyZ/tY./ firewall --disabled authconfig --enableshadow --enablesmbauth --smbservers officesrv --smbworkgroup docmagic timezone America/Los_Angeles #deviceprobe device eth0 tg3 network --bootproto static --ip 192.168.210.250 --gateway 192.168.210.1 --netmas k 255.255.255.0 --nameserver 192.168.210.10 nfs --server=da.docmagic.com --dir=/u2/install/7.3/ bootloader clearpart --linux part /boot --fstype ext3 --size=50 --ondisk=cciss/c0d0 part / --fstype ext3 --size=50000 --ondisk=cciss/c0d0 part /home --fstype ext3 --size=5000 --ondisk=cciss/c0d0 part /u --fstype reiserfs --size=70000 --ondisk=cciss/c0d0 part /u2 --fstype ext3 --size 12500 --ondisk=cciss/c0d0 part swap --size=1024 --ondisk=cciss/c0d0 sysconfig =============================================================== ===================================================================== label ks kernel vmlinuz append ks=nfs:192.168.210.18:/u2/install/ks/da/ks.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=8192 label ks-local kernel vmlinuz append ks=file:/ks.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=8192 label ks-cdrom kernel vmlinuz append ks=cdrom:/ks.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=8192 ----- Original Message ----- From: <james.oden@xxxxxxxxxxx> To: <kickstart-list@xxxxxxxxxx> Sent: Tuesday, December 10, 2002 5:42 AM Subject: Re: Local ks.cfg with an eltorito bootable CD. > > > I've created an eltorito bootable CD using floppy-disk emulation of a > > 2.88 floppy disk. This works very nicely, since it allows me to have the > > extra room (after rm'ing some .o files) to add the network modules for > > my ethernet card. > > > > I'm using redhat 7.3 and have tried using ks=cdrom, ks=file:/ks.cfg, and > > ks=floppy. I would assume that ks=floppy would be the most theoretically > > correct, since eltorito emulates a floppy disk, but I think that it is > > actually looking for the ks.cfg file under /dev/fd0... > > Hi Nick, > > Just use ks=cdrom:(some_path), and put the kickstart file in the ISO image > not > in the floppy image on the ISO image. This started working great in 7.3 > and > beyond (I assume beyond). > > Cheers...james > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list
