From: Roman Kagan <rkagan@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: The Next Generation
Date: Mon, 28 Feb 2005 21:25:49 +0000 [thread overview]
Message-ID: <20050228212549.GJ2964@katya> (raw)
In-Reply-To: <20050217190941.GA1561@vrfy.org>
On Mon, Feb 28, 2005 at 09:37:29PM +0100, Kay Sievers wrote:
> On Mon, 2005-02-28 at 22:11 +0300, Roman Kagan wrote:
> >HOTPLUG="sh -c 'for f in /etc/dev.d/default/*.dev; do [ -x \$f ] && \$f; done'"
>
> Sure, something like that should work too. It was easy to do this inside
> of udev, don't know what's better here.
My point was that you wanted udev to be as ligthweight as possible on
one hand, but kept adding functionality, which is not absolutely
necessary, on the other.
> >Another suggestion is of a syntactic sugar kind: would it be too hard to
> >implement key substitution in actions with a generic syntax, rather than
> >adding %-conversion specifier for each possible substitution, e.g.
> >
> >HOTPLUG="foo $SUBSYSTEM $SYSFS{bar} $ENV{baz}"
>
> No, that is not really hard. I thought about something like this too, if
> we are running out of nice characters. :)
The problem with "nice characters" is that each one need additional
doctumentation, too.
> It is nicer to read, yes. But renaming some of the keys would be nice
> too, like:
> ADD_SYMLINK, ADD_HOTPLUG, MATCH_ACTION, SET_GROUP, SET_MODE, SET_NAME
>
> so the key can tell you what it does in reality. Today you need to know
> that KERNEL= is a match instruction, SYMLINK= will add something to a
> list and GROUP= will override any value.
I think that's the distinction between keys to be matched against
(SUBSYSTEM, BUS, ID, etc.), and the actions to be taken (NAME, GROUP,
MODE, HOTPLUG), which was missing from the very beginning. OTOH I'm
with Marco here, that making it too verbose doesn't make a lot of sense.
At most I would add a separator between keys and actions.
Cheers,
Roman.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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
next prev parent reply other threads:[~2005-02-28 21:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 19:09 The Next Generation Kay Sievers
2005-02-17 20:21 ` Marco d'Itri
2005-02-17 20:35 ` Kay Sievers
2005-02-18 5:26 ` Alexander E. Patrakov
2005-02-24 11:29 ` Roman Kagan
2005-02-24 12:26 ` Kay Sievers
2005-02-24 17:51 ` Roman Kagan
2005-02-24 19:37 ` Kay Sievers
2005-02-24 20:39 ` Roman Kagan
2005-02-25 12:54 ` Kevin P. Fleming
2005-02-25 23:17 ` Greg KH
2005-02-25 23:59 ` Marco d'Itri
2005-02-26 0:07 ` Greg KH
2005-02-26 0:18 ` Kay Sievers
2005-02-27 20:13 ` David Brownell
2005-02-27 23:34 ` Kay Sievers
2005-02-28 17:02 ` Roman Kagan
2005-02-28 17:38 ` Kay Sievers
2005-02-28 18:41 ` Kay Sievers
2005-02-28 19:11 ` Roman Kagan
2005-02-28 19:49 ` Marco d'Itri
2005-02-28 20:37 ` Kay Sievers
2005-02-28 20:42 ` Chris Larson
2005-02-28 20:46 ` Kay Sievers
2005-02-28 20:50 ` Marco d'Itri
2005-02-28 21:01 ` Kay Sievers
2005-02-28 21:14 ` Erik van Konijnenburg
2005-02-28 21:25 ` Roman Kagan [this message]
2005-03-01 20:17 ` Tobias Klauser
2005-03-02 7:13 ` 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=20050228212549.GJ2964@katya \
--to=rkagan@mail.ru \
--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).