Bug 10496 – Startup script S10network should be changed!

Bug 10496 - Startup script S10network should be changed!

Summary:	Startup script S10network should be changed!

Status:	CLOSED DUPLICATE of bug 7693

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	initscripts (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	10733 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-03-31 16:58 EST by Hugh McLenaghan
Modified:	2014-03-16 22:13 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:	2000-04-12 12:32:41 EDT
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 Hugh McLenaghan 2000-03-31 16:58:53 EST

I don;t know exactly how/who to report this to, so I hope you can pass it
on the correct person.

On laptops the network starts up at S10network and pcmcia starts up at
S45pcmcia.  This is bad, because if you use a pcmcia card it will not work
as is.   In my case I changes S10network to S47network and rebooted.  This
started up both pcmcia and the network with 0 errors.  I would recommend
this be the default setup.

Comment 1 Bill Nottingham 2000-04-03 11:31:59 EDT

In what way did a PCMCIA card not work normally? The PCMCIA
startup should still bring up the network interface, even
after the network script was run.

Comment 2 Bill Nottingham 2000-04-12 12:27:59 EDT

*** Bug 10733 has been marked as a duplicate of this bug. ***

Comment 3 Bill Nottingham 2000-04-12 12:32:59 EDT

*** This bug has been marked as a duplicate of 7693 ***

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