Bug 18355

Summary:	pcmcia startup needs to come sooner
Product:	[Retired] Red Hat Linux	Reporter:	Paul Schroeder <paulsch>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-10-04 19:15:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paul Schroeder 2000-10-04 19:15:01 UTC

'kernel-pcmcia' wasn't available as an option so I selected 'initscripts' thinking that made the most sense for this problem.

I did a custom expert install.  Don't know if this matters, but I'm guessing not....

S45pcmcia as the default causes a couple problems with PCMCIA NICs.  1.  When a pcmcia NIC device is being configured via DHCP it fails.  
The S10network script cannot configure the device if it hasn't started yet.  So pcmcia should start before network.  2.  S45pcmcia starts after 
S17ypbind causing ypbind to fail to locate the NIS server since there is no network connectivity.

May be other problems, but these are what I've noticed...

Comment 1 Bill Nottingham 2000-10-04 19:54:17 UTC


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