Bug 4790 – /etc/conf.modeles update by netcfg is bad for second ethernet card

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 4790 - /etc/conf.modeles update by netcfg is bad for second ethernet card

Summary:	/etc/conf.modeles update by netcfg is bad for second ethernet card

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	linuxconf (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-08-30 18:55 EDT by pberge
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-12-15 15:58:01 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description pberge 1999-08-30 18:55:02 EDT

in /etc/conf.modules

netcfg put "ne io=0x300" and "ne io=0x240" .... The second
one replaces the
first so the first ethernet card is not found.  netcfg
should use "ne io=0x300,0x240".

Comment 1 Michael K. Johnson 1999-09-20 13:30:59 EDT

netcfg never writes to /etc/conf.modules.
Perhaps you were using linuxconf?

Comment 2 Michael K. Johnson 1999-11-22 13:47:59 EST

I think that "netcfg" was a typo for "netconf" which is part of linuxconf.
I've since heard of this bug in linuxconf from other folks.

Comment 3 Michael K. Johnson 1999-12-02 12:38:59 EST

This should be fixed in linuxconf-1.16r10-1 (or later) that we will release
as an errata update after testing.

Comment 4 Michael K. Johnson 1999-12-15 15:58:59 EST

1.16r10-2 released

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