Description of problem: I've been working on getting FC5 to kickstart through a
410 satellite since it's the closest we have to RHEL 5 at the moment, but ran
into a problem. The line "network --bootproto dhcp" isn't included in the
kickstart file by default, so the FC 5 anaconda keeps dropping from an automated
install to a manual install when it reaches the network configuration step. I
don't know if this is a problem for RHEL 4.

How reproducible: Always


Steps to Reproduce:
1. Create an external distribution of FC5.
2. Create a new profile with default values that uses the distribution.
3. View the kickstart file that's generated and see that the network
configuration line isn't included.
  
Actual results: Anaconda on FC5 will switch to manual configuration when it
reaches the network configuration step.


Expected results: The kickstart file should have the line "network --bootproto
dhcp" in it to keep anaconda from dropping into manual mode.

Additional info: I can work around this by adding the network config line via
the Advanced Options.