Bug 64095 - neat writes ifcfg-ethX files to wrong directory
Summary: neat writes ifcfg-ethX files to wrong directory
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network
Version: 7.3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-25 16:34 UTC by John A. Hull
Modified: 2015-03-05 01:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-05-21 00:23:07 UTC
Embargoed:


Attachments (Terms of Use)

Description John A. Hull 2002-04-25 16:34:26 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0; DigExt)

Description of problem:
Filing under net-tools...can't find neat anymore in component list

neat writes ifcfg-ethX network config files 
to /etc/sysconfig/networking/devices instead of /etc/sysconfig/network-scripts. 
If you try to configure a NIC with neat, you can't bring up the IP address.

netconfig puts the ifcfg files in network-scripts

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


How reproducible:
Always

Steps to Reproduce:
1. Run neat
2. Configure a new NIC
3. Try to bring up NIC on network
4. Find that ifcfg-ethX file is in /etc/sysconfig/networking/devices
	

Additional info:

Comment 1 Phil Knirsch 2002-04-29 12:52:06 UTC
Reasigning to correct component.

Read ya, Phil

Comment 2 Harald Hoyer 2002-05-16 10:16:45 UTC
which version of redhat-config-network?

Comment 3 John A. Hull 2002-05-16 15:49:55 UTC
1.0.0-1

Comment 4 John A. Hull 2002-05-21 00:23:01 UTC
Phil, Any idea when this will be fixed? We're getting ready to ship hampton, 
and would like to be able to recommend that customers upgrade to the errata for 
this package...

Comment 5 John A. Hull 2002-06-06 22:52:03 UTC
This seems to work...don't know what I was doing before.


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