From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Need new modutils aliases for 2.4.0? (Was)Re:Cannothotplugcardbus
Date: Fri, 26 Jan 2001 19:22:12 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98053712015449@msgid-missing> (raw)
Yes, at the PCI level I think that's exactly right.
For "network" hotplugging, I'm not sure what the analagous policy
would be ... what comes to mind is getting the network interface
brought up exactly once. I saw some flakey behavior there a while
back, maybe it's gone now. Aren't there distro portability issues,
like "ifup" not being universal?
- Dave
----- Original Message -----
From: David Hinds <dhinds@sonic.net>
To: David Brownell <david-b@pacbell.net>
Cc: <linux-hotplug-devel@lists.sourceforge.net>
Sent: Friday, January 26, 2001 10:10 AM
Subject: Re: Need new modutils aliases for 2.4.0? (Was)Re:Cannothotplugcardbus cards.
> On Fri, Jan 26, 2001 at 08:44:56AM -0800, David Brownell wrote:
> >
> > That sounds good. Can that also understand the network hotplugging?
> > Or is that going to need work yet?
>
> I'm not sure what you mean? When cardmgr sees a card that has a hot
> plug PCI driver, it will basically ignore the card completely and
> leave everything to /sbin/hotplug. Isn't that what we want?
>
> -- Dave
_______________________________________________
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
next reply other threads:[~2001-01-26 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 19:22 David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-25 21:43 Need new modutils aliases for 2.4.0? (Was) Re: Cannothotplugcardbus Miles Lane
2001-01-26 6:44 ` Miles Lane
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-98053712015449@msgid-missing \
--to=david-b@pacbell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.