Description of problem:
After a fresh installation of a system, eth0 is not set up. /etc/sysconfig/network-scripts/ifcfg-eth0 does contain the information used during anaconda installation, however, /etc/init.d/network seems to be not run on boot.
Version-Release number of selected component (if applicable):
F 13 netinst.
Steps to Reproduce:
How you configured network on anaconda(dhcp,static.ipv[4,6]), and what was created on /etc/sysconfig/network-scripts/ifcfg-eth0 after system be completely installed?
Thanks for your report.
(In reply to comment #0)
> Description of problem:
> After a fresh installation of a system, eth0 is not set up.
> /etc/sysconfig/network-scripts/ifcfg-eth0 does contain the information used
> during anaconda installation, however, /etc/init.d/network seems to be not run
> on boot.
> Version-Release number of selected component (if applicable):
> F 13 netinst.
> How reproducible:
> Steps to Reproduce:
> Actual results:
> Expected results:
> Additional info:
Did you just do the minimal install? If you did (and therefore do not install NetworkManager), you will need to enable the network service.
After giving the installer the network setup info, it just installs something without further questions. NetworkManager does not seem to be among that.
Was this a text mode install?
It was indeed.
OK. text mode install is a minimal install, so it runs into the above situation.
So what? Why can't Fedora have this fixed what other distributions already have?
The installer does not have a mechanism to enable and disable services based on the package set installed. TBH, the simplest solution would be to put NetworkManager in the minimal install.
TBH that leaves me unsatisfied - openSUSE can do this. I think what they do is always have /etc/init.d/network in the runlevel, but let ifup (which is called as part of network) skip ethX if ifcfg-ethX has been marked as being controlled by NetworkManager.