Bug 126822 - Section 4.1.22. /etc/sysconfig/network contains obsolete info
Summary: Section 4.1.22. /etc/sysconfig/network contains obsolete info
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rhel-rg
Version: 3.0
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Andrius Benokraitis
QA Contact: John Ha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-06-28 00:09 UTC by Ian Laurie
Modified: 2015-07-14 04:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-06-28 17:58:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ian Laurie 2004-06-28 00:09:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
Gecko/20040113

Description of problem:
Documentation says the /etc/sysconfig/network file contains the
GATEWAY and GATEWAYDEV directives.  Not on my system.  Seems GATEWAY
has been moved to the individual ifcfg-eth<X> files, thus obsoleting
the GATEWAYDEV directive ?

Section "8.2.1. Ethernet Interfaces" documenting the ifcfg-eth<X>
files fails to mention the GATEWAY directive.


Version-Release number of selected component (if applicable):
rhel-rg-en-3-3

How reproducible:
Always

Steps to Reproduce:
1. View the Reference Guide
2. View 4.1.22
3. View 8.2.1
    

Additional info:

Comment 1 Andrius Benokraitis 2004-06-28 15:22:30 UTC
Talking with initscripts developer owner, as the
/usr/share/doc/initscrips-ver/sysconfig.txt file is also incorrect.

Comment 2 Bill Nottingham 2004-06-28 16:50:54 UTC
Yeah, it's a little out of date. Both approaches should actually work.

Comment 3 Andrius Benokraitis 2004-06-28 17:27:09 UTC
Will add GATEWAY to 8.2.1 and subtract GATEWAY and GATEWAYDEV from
4.1.22 per bug reporter for RHEL4-rg documentation. Closing bug as
NEXTRELEASE, as the information isn't incorrect, just needs
clarification for RHEL4.


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