Bug 18355 - pcmcia startup needs to come sooner
pcmcia startup needs to come sooner
Status: CLOSED DUPLICATE of bug 15275
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2000-10-04 15:15 EDT by Paul Schroeder
Modified: 2014-03-16 22:16 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-10-04 15:15:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul Schroeder 2000-10-04 15:15:01 EDT
'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 15:54:17 EDT

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

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