just finished(?) setting up a classroom full of PCs using a net-based kickstart install, and i had one aggravating problem. a number of the boxen had two network cards: * a standard ne2k-pci card * a dlink dfe something, which needs the via-rhine driver for the dlink, since that driver is not on the bootnet.img disk, i was typically prompted for a driver disk, at which point i inserted drivers.img and selected the entry which used the via-rhine driver. so far, so good. when that happened, it worked fine. unfortunately, on some of the boxen, the boot process clearly saw the ne2k card "first" and assigned it to eth0, which totally screwed the dhcp process, since i assigned dhcp addresses based strictly on the other card. one solution: just rip the other card out of the box. a better solution? isn't there something you can append to specify the card to use for the kickstart process like: boot: linux ks eth0="????" i'm sure something like this must work. any suggestions? rday -- Robert P. J. Day Eno River Technologies, Durham NC Unix, Linux and Open Source training "This is Microsoft technical support. How may I misinform you?"
