Bug 118134

Summary:	Improper handle of PCMCIA network cards in pcmcia init script
Product:	[Fedora] Fedora	Reporter:	Cristiano Duarte <cunha17>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DUPLICATE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	high
Version:	1	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-21 19:01:56 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 Cristiano Duarte 2004-03-12 11:49:30 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031010

Description of problem:
My PCMCIA network card is not waiting for configuration (dhclient), so
all network services that depends on it fail.
I figure out that the startup sequence is causing the problem. When
the startup "pcmcia" service is moved to place 09 instead of 24, all
network services work.
This new behaviour is the same as PCI ethernet cards, since dhclient
waits for DHCP configuration.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
Just turn on a notebook with a PCMCIA network card and a network
service like ntpd configured at boot.

Actual Results:  The network script runs. Since there is no PCMCIA
card configured, it does not configure eth0.
The pcmcia script runs. The network configuration doesn't wait for the
DHCP message and continue the init sequence.
The ntpd script fails since there is no IP address configured yet.

Expected Results:  no ntpd fail or any other network service fail

Additional info:

Maybe it's not necessary to move the pcmcia script to place 09, if the
pcmcia script waits for DHCP configuration.

Comment 1 Bill Nottingham 2004-03-12 19:14:52 UTC


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

Comment 2 Red Hat Bugzilla 2006-02-21 19:01:56 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.