Up until RedHat 9 we have been able to kickstart without intervention
through a wireless interface (a Cisco Aironet). We use a custom
"initrd.img" with the aironet module. With 9 when it loads up the
"airo.o" the kickstart stops and offers two interfaces which never
happened before:
eth0
wifi0
This appears to be related to a change in interface naming in the
"airo.o" module. The "wifi0" is apparently for straight 802.11 frames
and the "eth0" is for 802.3 frames (at least this is what I'm
interpreting from emails I've Google'd up).
Has anyone been able to get kickstart to not get confused by the
dueling interfaces here? Typically we avoid specifying the interface
to kickstart from in the kickstart config because we use a generic
install for both systems with 10/100baseT interfaces and wireless
interfaces, but this seems to throw a wedge in.
Thanks in advance,
- Matt
