Bug 92297
Summary: | pcmcia restart and netfs restart in wrong order | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jón Fairbairn <jon.fairbairn> |
Component: | apmd | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | p.van.egdom, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-03-16 22:21:51 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
Jón Fairbairn
2003-06-04 18:03:41 UTC
Not just netfs, the whole network needs to be restarted after pcmcia as well, right now it is before in FC2. I don't have my eth0 after resume on an IBM TP600E, and I have PCMCIARESTART="yes" and NET_RESTART="yes" in /etc/sysconfig/apmd Same goes for init, any reason we can't finally have pcmcia start before the network by default (which up to now fails unnecessarily and drops to a detailed view during the nice rhgb screen)? Changed in 3.2.2-1 |