Bug 68792 - not writing NETWORKING=no into /etc/sysconfig/network
Summary: not writing NETWORKING=no into /etc/sysconfig/network
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda
Version: limbo
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-14 10:43 UTC by Michael Schwendt
Modified: 2007-04-18 16:44 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-07-24 22:07:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Michael Schwendt 2002-07-14 10:43:29 UTC
Description of problem:
Anaconda writes "NETWORKING=yes" into /etc/sysconfig/network, if network support
is installed. But when network support is not installed, it should write
NETWORKING=no, because various initscripts rely on the availability of such a
definition.


Version-Release number of selected component (if applicable):
7.3.92-4

How reproducible:
Always

Steps to Reproduce:
Perform fresh installation without network support. Look at
/etc/sysconfig/network afterwards.

Actual Results:  Should contain NETWORKING=no.

Expected Results:  Does not contain NETWORKING=no.


Additional info:

A related bug exists in redhat-config-network, which does not write
NETWORKING=yes if network support components are added after installation and
the network is configured.

Comment 1 Michael Fulbright 2002-07-24 22:07:22 UTC
What do you mean when 'no networking support is installed'?

You mean if there are no ethernet ports on the machine?

Comment 2 Michael Schwendt 2002-07-25 01:36:20 UTC
https://listman.redhat.com/pipermail/valhalla-list/2002-July/008137.html

Sorry, it should have been filed against Valhalla. I'm unable to reproduce it
with Limbo, neither with a minimal installation. Even when no Ethernet device is
installed, it puts "NETWORKING=yes".



Note You need to log in before you can comment on or make changes to this bug.