Description of problem:
These are two related bugs in one report.
This is about installing Red Hat Linux without "network support" and then adding
networking components after installation.
1. Upon adding and configuring a network device with redhat-config-network, it
should write NETWORKING=yes into /etc/sysconfig/network.
2. At the same time, it should be capable of replacing an existing NETWORKING=no
definition in /etc/sysconfig/network.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rm -f /etc/sysconfig/network
2. rm -f $(find /etc/sysconfig -name ifcfg\*)
4. create profile, e.g. Ethernet device
5. save changes and exit
6. grep NETWORKING /etc/sysconfig/network
Actual Results: Nothing (i.e. NETWORKING variable not defined in
Expected Results: NETWORKING=yes
When NETWORKING=no exists in /etc/sysconfig/network, redhat-config-network does
NOT replace it either. It should replace NETWORKING=no with NETWORKING=yes.
Various initscripts check for NETWORKING=no, e.g. "service network restart"
would exit silently and would not start a newly configured network.
A related bug exists in Anaconda, which doesn't write NETWORKING=no if network
support is not installed.
fixed in CVS
I'm still seeing some problems with redhat-config-network-1.1.12-1. When first
configuring a network interface, I'm not getting "NETWORKING=yes" written to the
/etc/sysconfig/network file. I am seeing it get changed from 'no' to 'yes' in
the second case above though.
Limbo's installer _always_ writes NETWORKING=yes into /etc/sysconfig/network,
regardless of whether any network devices are found or configured, respectively.
This is a change compared with previous versions (Skipjack, Valhalla) where
installation without "Network Support" would not write into /etc/sysconfig/network.
Nevertheless, redhat-config-network should make sure that it maintains the
NETWORKING variable in /etc/sysconfig/network and adds NETWORKING=yes, if it
doesn't exist already.
NETWORKING=no, however, is a documented features and supported by a lot of
initscripts, so that should be dealt with, too.
ok, fixed ... in case we have devices neat writes/changes to
Fix confirmed with redhat-config-network-1.1.15-1.