I have been down this road before, but am running into some issues. OK, what I am trying to do is create a "boot disk" such that someone in our data center can simply stick the disk in the floppy, reboot the server and it will boot off of that, and begin the kickstart install. So to that end, I have the following in my syslinux.cfg: default linux prompt 1 timeout 600 display snake.msg F1 boot.msg F2 general.msg F3 expert.msg F4 param.msg F5 rescue.msg F7 snake.msg DEFAULT linux LABEL linux KERNEL vmlinuz APPEND ksdevice=eth0 console=tty0 load_ramdisk=1 prompt_ramdisk=0 \ initrd=initrd.img network ip=dhcp ks=nfs:10.10.232.54:/tftpboot/ks.cfg \ selinux=0 However, when it boots off of the diskette, I see the following on VC3: Bootp: no boot file specified Ks server: 10.10.232.54:/tftpboot file: ks-fc2.cfg ... kickstarting through device eth0 ... Mounting nfs path 10.10.232.54:/repo/fedora/linux/core/2/i386/os No valid tree or isos found in 10.10.232.54:/repo/fedora/linux/core/2/i386/os And the install basically aborts. Now, to test this, I ran the same thing only via PXE boot, and that works perfectly mounting the SAME server and location, etc same ks file. Is it possible to do what I am trying (eg create a ks bootdisk and do an nfs install of fc2)? Everything I have read leads me to believe it can. So my question is, why am I seeing two different behaviors? The only REAL difference is via PXE I load the vmlinuz and initrd.img from the FC2/images/pxeboot tree rather than using say bootimg and dd to create a boot disk. Would this cause this type of behavior? I tried to get those two files onto my boot disk but alas they are too large for a 1.44M floppy. Any ideas or pointers?Any help would be greatly appreciated. Thanks in advance Michael Weiner -- Update, I changed the syslinux.cfg to say ks=floppy since I have the ks.cfg on the local boot floppy. And that seems to get around that issue. Now, it goes to NFS mount 10.10.232.54:/repo/fedora/linux/core/2/i386/os and it fails to mount and basically bombs. BTW, I have all this working via PXE, the issue is that I would have to have the person in the data center redo the BIOS' across all 450 odd machines to get the PXE boot to work, and a boot disk seemed to be less work to me, simply stick it in, rather than changing default BIOS settings. Any thoughts? Michael Weiner <http://www.interactive.ag.com/> ... Says it Best. <http://www.americangreetings.com/> Michael Weiner, Linux+, Linux+ SME Senior Systems Administrator AmericanGreetings.com One American Road Cleveland, OH 44144 <http://maps.yahoo.com/py/maps.py?Pyt=Tmap&addr=One+American+Road&csz=Cl eveland%2C+OH++44144&country=us> MWeiner@xxxxxx IM: hUnTeRoZe http://www.interactive.ag.com <http://www.interactive.ag.com/> tel: fax: mobile: (216) 889-5028 (216) 889-5029 (216) 965-8619 Add me to your address book... <https://www.plaxo.com/add_me?u=12885008288&v0=209910&k0=491764583> Want a signature like this? <http://www.plaxo.com/signature>
