From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH 2.4.0.10: Update hotplug
Date: Thu, 02 Nov 2000 19:38:57 -0500 [thread overview]
Message-ID: <3A020920.4559F400@mandrakesoft.com> (raw)
In-Reply-To: <007401c04527$dc094510$6500000a@brownell.org>
David Brownell wrote:
> - 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.
Wrong. Different subsystems -do- define their own events. However,
different subsystems should use the same verbs for the same actions. We
need consistency where possible.
> - "/sbin/hotplug net ..." replaced by "/sbin/network",
> with two custom event types.
Hotplug device insertion and network interface addition/removal are two
fundamentally different things. Further, my code purposefully does not
wrap CONFIG_HOTPLUG around the /sbin/network code, because /sbin/network
has utility outside the domain of hotplug.
Jeff
--
Jeff Garzik | Dinner is ready when
Building 1024 | the smoke alarm goes off.
MandrakeSoft | -/usr/games/fortune
-
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 prev parent reply other threads:[~2000-11-03 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 23:51 PATCH 2.4.0.10: Update hotplug David Brownell
2000-11-03 0:38 ` Jeff Garzik [this message]
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=3A020920.4559F400@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=david-b@pacbell.net \
--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