Red Hat Bugzilla – Bug 511297
network logins selection needs to start network at boot
Last modified: 2009-09-09 16:46:35 EDT
Description of problem:
If network logins are selected at install time (NIS, etc), then the network needs to be brought up before a user logs in.
Version-Release number of selected component (if applicable):
Fedora 11 install media
Steps to Reproduce:
1. Install Fedora 11 selecting NIS logins
2. reboot at end of install
3. No network logins are available as the network is not up.
No network logins available.
Network logins available.
If NIS, etc, are selected then you need to turn off Network-Manager and turn on /etc/init.d/network and mark the primary interface as onboot=yes in ifcfg-eth0.
I would also like the choice in general of having network brought up at boot. I always end up having to do these steps by hand and reboot to get my machines setup. So a check box to bring network up at boot would be a good option to add, so you could force the network on at boot even if you are not using NIS, etc. (For example you want NFS mounts for home directories.)
Can you provide the kickstart file you used for installation?
Sorry no, I did it by hand.
When you get to the setup accounts section, select one of the network logins (I used NIS) choices.
The choice you made was in firstboot and not anaconda. Reassigning to firstboot.
It's not firstboot's place to do network configuration. There's currently no network configuration dialog in firstboot and I don't want to add another one, as that just contributes to the problem of more and more dialogs that do the same thing slightly differently. If we do need to bring up the network, either (1) anaconda needs to provide the interface to do it, or (2) we need a good system-wide dialog for bringing up the network that firstboot can then use.