linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [RFC] /sbin/hotplug multiplexor
Date: Mon, 14 Apr 2003 22:19:26 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-105035885109585@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105034677627168@msgid-missing>

Am Montag, 14. April 2003 23:52 schrieb Greg KH:
> On Mon, Apr 14, 2003 at 11:43:17PM +0200, Oliver Neukum wrote:
> > > > Well, for a little elegance you might introduce subdirectories for
> > > > each type of hotplug event and use only them.
> > >
> > > No, that's for the individual scripts/programs to decide.  For example,
> > > that's what the current hotplug scripts do, but that's not at all what
> > > the udev program wants to do.
> >
> > So have them put a symlink into each subdirectory. This is the way it's
> > done for init since times immemorial.
>
> But the number of different "types" keeps growing.  For some programs
> (like udev) they really don't care about the type, and if you add a new
> type, it still works just fine.  Other programs do care about the type,
> so they can look at it and make a judgement based on it.

How can that be? What kind of thing should care about both
device addition and routing changes in the same way?

Not needlessly exposing scripts to event types they are not written
to handle is an advantage.

	Regards
		Oliver



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2003-04-14 22:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 18:59 [RFC] /sbin/hotplug multiplexor Greg KH
2003-04-14 19:16 ` Oliver Neukum
2003-04-14 19:54 ` Greg KH
2003-04-14 20:09 ` Oliver Neukum
2003-04-14 20:33 ` Greg KH
2003-04-14 21:11 ` Oliver Neukum
2003-04-14 21:24 ` Kevin P. Fleming
2003-04-14 21:30 ` Greg KH
2003-04-14 21:34 ` Greg KH
2003-04-14 21:43 ` Oliver Neukum
2003-04-14 21:45 ` Robert Love
2003-04-14 21:52 ` Greg KH
2003-04-14 22:19 ` Oliver Neukum [this message]
2003-04-14 22:21 ` Greg KH
2003-04-14 22:44 ` Greg KH
2003-04-15 19:59 ` David Brownell
2003-04-16 16:01 ` Stephen Williams
2003-04-17 23:27 ` David Brownell
2003-04-18  2:08 ` Stephen Williams
2003-04-18 22:32 ` Greg KH
2003-04-18 23:10 ` Stephen Williams
2003-04-18 23:16 ` David Brownell

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-105035885109585@msgid-missing \
    --to=oliver@neukum.org \
    --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).