The way around this problem is to create a custom boot floppy by discarding the scsi, usb and some other drivers and adding drivers for network cards on your computers. To identify what the device and module your Linux system uses, run /usr/sbin/kudzu -p. In Unisys lab, for example, we have machines with 3Com, Netgear, Intel eepro100 and RTL8139 cards; they require drivers 3c59x.o, 8139too.o, e100.o, tulip.o and mii.o.
mount bootdisk.img /mnt/bootdisk -t vfat -o loop,blocksize=1024 cd /mnt/bootdisk; cp initrd.img $HOME/DRV cd $HOME/DRV gunzip < initrd.img > initrd.data mount initrd.data /mnt/initrd -o loopNow we need to change the content of /mnt/initrd/modules: module-info, modules.cgz, modules.dep, pcitable.
mount drvnet.img /mnt/drvnet -o loop cp modinfo $HOME/DRV/module-info cp modules.cgz $HOME/DRV cp modules.dep $HOME/DRV cp pcitable $HOME/DRV cd $HOME/DRVModify module-info, modules.dep and pcitable leaving only the entries for the appropriate network drivers.
gunzip < modules.cgz | cpio -idvThis creates a new directory called 2.4.20-8BOOT. Remove all .o files in the directory except those for the appropriate network cards, 3c59x.o, 8139too.o, e100.o, tulip.o and mii.o. Compress 2.4.20-8BOOT back into modules.cgz:
find 2.4.20-8BOOT -depth -print | cpio -ov -H crc | gzip --best > modules.cgzCopy the modified files, modinfo, modules.cgz, modules.dep and pcitable into directory /mnt/initrd/modules
umount /mnt/initrd gzip --best < initrd.data > initrd.img cp initrd.img /mnt/bootdiskYou may also copy your kickstart file, ks.cfg, into /mnt/bootdisk and modify syslinux.cfg leaving only the entry for kickstart, for example:
default ks label ks kernel vmlinuz append ks=floppy initrd=initrd.img umount /mnt/bootdiskNow you have a boot disk image ready for unattended kickstart installation.