From: David Brownell <david-b@pacbell.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH 2.4.0.10: Update hotplug
Date: Thu, 02 Nov 2000 15:51:45 -0800 [thread overview]
Message-ID: <007401c04527$dc094510$6500000a@brownell.org> (raw)
I'm glad to see the CardBus/PCI and network hotplug
support start happening!
Would you motivate two changes I noticed?
- Changing /sbin/hotplug invocations ... now it can
only support "add" and "del" events. (USB now
uses "add" and "remove", though "remove" doesn't
try to do anything yet.)
This removes the intended flexibility whereby
different subsystems (such as networking) can
define their own events.
- "/sbin/hotplug net ..." replaced by "/sbin/network",
with two custom event types.
The original intent of /sbin/hotplug was to centralize all
the hotplug-related dispatching, addressing both the module
selection/loading problem and device config/setup aspects
of device setup.
By creating another hotplug command (/sbin/network) you're
starting down what seems a slippery slope, where there's
no longer a single dispatch point to enable/disable or
to debug from. Why discard the, err, "conceptual unity"
of one access point for usermode hotplug policy agents?
- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-02 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 23:51 David Brownell [this message]
2000-11-03 0:38 ` PATCH 2.4.0.10: Update hotplug Jeff Garzik
2000-11-03 4:35 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2000-11-02 8:05 Jeff Garzik
2000-11-02 8:01 ` David S. Miller
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='007401c04527$dc094510$6500000a@brownell.org' \
--to=david-b@pacbell.net \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@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