Bug 47529
Summary: | PCMCIA ethernet devices ALWAYS ifup'd at boot time | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Dax Kelson <dkelson> |
Component: | kernel-pcmcia-cs | Assignee: | Dave Jones <davej> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | mjs, pfrields |
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: | 2004-11-25 08:06:02 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
Dax Kelson
2001-07-05 23:24:11 UTC
I agree that if the card is plugged in before booting, it should honor the ONBOOT. I will try to figure a way on how to do this, the tricky part indeed is what to do when someone inserts a card later on. Currently, it's hard to make a distinction between those events (the on boot case pretends to be a card insertion) The confounding of boot and card insertion doesn't seem to me to be such a bad thing. If ONBOOT=no, then booting or inserting the card doesn't start the interface and it has to be started manually. If ONBOOT=yes, then booting or inserting the card starts the interface automatically. This seems less annoying to me (with a laptop that may not be connected to a network at boot or card insertion) than having no control whatsoever. Consider the following example: You have a modem/ethernet combo card. You insert it to use the modem. Under the current regime, the ether interface will attempt to start even if not connected. In my case, I have a built-in ethernet and a pc-card wireless. The wireless interface always attempts to start on boot, even if the ethernet is connected. If I'm near my WAP, then I end up with both interfaces running, when I may really only want the (faster) ethernet. BTW, this is still the behavior in 7.3. Can the version number be updated somehow? Just saw the update to 7.3. FYI, it happens in 8.0 too. |