From: Ryan Mack <rmack@mackman.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [BUG] hotplug network agent / apmd bug...
Date: Wed, 25 Jul 2001 20:23:12 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-99609274918817@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99603822900315@msgid-missing>
It's probably a distro bug then, in which case I've already submitted it
to RH.
-Ryan
On Wed, 25 Jul 2001, David Brownell wrote:
> Hmm, I've not hacked apmd stuff in ages, but as I recall
> it didn't ship with any configuration-specific support in
> its scripts -- stuff like "cardctl" and "service" commands.
> Are you positive those aren't distro bugs?
>
> In general it'd make more sense to start networking
> first, I suspect..
>
> - Dave
>
> ----- Original Message -----
> From: "Ryan Mack" <rmack@mackman.net>
> To: <linux-hotplug-devel@lists.sourceforge.net>; <apenwarr@worldvisions.ca>
> Sent: Tuesday, July 24, 2001 10:15 PM
> Subject: [BUG] hotplug network agent / apmd bug...
>
>
> > The apm-script included in apmd-3.0final does the following on resume:
> >
> > cardctl resume/insert
> > service networking start
> >
> > Unfortunately, if one of your pcmcia cards is a PCI-merged networking card
> > such as the 3c575_cb, hotplug does the following upon seeing the card
> > resumed...
> >
> > if networking is started, configure the new interface
> >
> > Thus, because apmd reenables pcmcia before networking, a pcmcia network
> > adapter won't be configured by hotplug.
> >
> > One easy sollution, is that if the pcmcia network adapter is always in the
> > system, you can enable ONBOOT for the interface, and thus the networking
> > script will enable it for you. In my case (frequently switching between
> > LAN and WAN cards), that isn't an option.
> >
> > Anyhow, if one of the two projects could fix this it would be much
> > appreciated. I'd submit a patch, but I'm not sure which project should be
> > patched.
> >
> > Thanks, Ryan Mack
> >
> >
> > _______________________________________________
> > Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
> > Linux-hotplug-devel@lists.sourceforge.net
> > http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
>
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-07-25 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 5:15 [BUG] hotplug network agent / apmd bug Ryan Mack
2001-07-25 14:39 ` David Brownell
2001-07-25 20:23 ` Ryan Mack [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-99609274918817@msgid-missing \
--to=rmack@mackman.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).