Re: The Next Generation

[Tobias Klauser <tklauser@access.unizh.ch>]

On Mon, Feb 28, 2005 at 10:01:17PM +0100, Kay Sievers wrote:
> On Mon, 2005-02-28 at 21:50 +0100, Marco d'Itri wrote:
> >On Feb 28, Kay Sievers <kay.sievers@vrfy.org> wrote:
> >
> >> 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
> >Please don't... this would make rules files excessively verbose, and I
> >believe that it's already quite clear which rules are conditions and
> >which one are actions.
> 
> Don't worry, there are no plans at the moment. :)
> But I still think that it would be nice to be able to read the kind of
> instruction from the key. Or we may allow '=' and get:
>   BUS="ide", KERNEL="hda", NAME="hda", SYMLINK="disk"?

That'd be very nice! As other people stated before, that's something quite
unusual about udev rules. In every programming language I can think of
and also in configuration files which use similar syntak '=' stands for
an assignment while '=' stands for a comparison. I guess it's not to hard
to implement and you could still keep the old behaviour in to have
backwards compatibility.

That change would make it much easier for "newbies" to start creating udev
rules.

Cheers, Tobias


-------------------------------------------------------
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