From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2 i686)


This is similar to bug 20167 that was aparently closed due to inactivity. 
There was no category for installer for the public betas.

I'm setting up KickStart over NFS with boot floppies.  DHCP is used to get
network information.  The clients are SGI 1200 rackmount PCs with three
ethernet interfaces (eepro100 cards).  I am always getting asked which
ethernet device to use during installation.  The KickStart docs say that
the 'network' line can have '--device eth0', but that it only works for
floppy based installs and that DHCP will configure everything (I tried it
anyway).  That being the case, DHCP should be used on all interfaces
instead of asking which one I shoudl use.  The prevents a fully hands-free
install from happening.

My KickStart file:
lang en_US
network --device eth0 --bootproto dhcp
nfs --server 192.168.1.1
firewall --disabled
keyboard us
zerombr yes
clearpart --all
part /    --size 2048
part swap --size 1024
part /var --size 512
part /tmp --size 1024 --grow
install
mouse generic3ps/2
timezone --utc US/Eastern
skipx
rootpw --iscrypted $1$HAwE4Ja5$/zkBxF4yQJfJ6YyNEGPjy1
auth --useshadow --enablemd5
lilo --location mbr
reboot%packages
@ Base
@ Networked Workstation
@ Network Server
@ Development
@ Utilities
tcpdump
wu-ftpd
ntp
mtools
zip
libungif
kaffe
%post --nochroot
/mnt/source/local/install.sh





Reproducible: Always
Steps to Reproduce:
1.  Use above kickstart file with boot floppy.
2.  
3.
	

Actual Results:  You will be asked one question... which ethernet dev to
use.

Expected Results:  Should be asked no questions.  DHCP should probe each
interface automatically.

This happens with Fisher, Wolverine, and Rawhide.  I've never tried any
other version of KickStart.