From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: new release of udev?
Date: Sun, 22 May 2005 17:38:21 +0000 [thread overview]
Message-ID: <20050522173821.GA9959@vrfy.org> (raw)
In-Reply-To: <20050519065848.GA25640@kroah.com>
On Sun, May 22, 2005 at 03:07:56PM +0200, Marco d'Itri wrote:
> On May 22, Kay Sievers <kay.sievers@vrfy.org> wrote:
>
> > > > It was _you_ who asked to be able to overwrite the system specified rules
> > > > for symlinks. That's not possible this way. And again, how do you prevent
> > > Sure it is: if you want to override any previous value you use SYMLINK> > > instead of the usual SYMLINK+=.
> > System-supplied rules are usually _not_ "previous". This will not work.
> Usually? Users will put their custom rules where it's needed to make
> them work, I do not think this is a great argument.
Well, I personaly prefer to put _all_ my custom rules in _one_ file.
Your solution solves only _your_ problem, which _is_ a great argument.
> > > > overriding the permissions from later system specified rules?
> > > By documenting that system rules files are installed only in specific
> > > parts of the name space, this is something which is needed for every
> > > scheme.
> > What scheme? What namespace? What documentation? Care to be more
> > specific?
> The rules.d/ directory file names. For the debian package I'm documenting
> a policy like "all default permissions are set before 030_*" and "RUN
> rules must be set from z40_* onward" (the actual values will change).
> If the order of rules is important, then this needs to be documented to
> allow users and package maintainers to choose the right file names.
Well, sounds like a pretty complicated requirement to solve a simple problem.
Anyway, I will do the "final assignments". Just ignore it if you don't
like it. :)
I see no problem to clear a value list if "=" is used instead of '+='.
The parser already supports this, I wanted to do this somtimes anyway.
I will _not_ add any more OPTIONS for individual keys like the "last_run_rule",
stuff. That belongs to the key operation itself not in the OPTIONS.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_idt12&alloc_id\x16344&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-05-22 17:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:58 new release of udev? Greg KH
2005-05-19 7:30 ` Kay Sievers
2005-05-19 7:55 ` Greg KH
2005-05-19 10:32 ` Marco d'Itri
2005-05-19 14:12 ` Kay Sievers
2005-05-19 16:09 ` Marco d'Itri
2005-05-19 17:49 ` Darren Salt
2005-05-19 21:02 ` Greg KH
2005-05-19 21:24 ` Darren Salt
2005-05-19 22:31 ` Kay Sievers
2005-05-22 0:59 ` Marco d'Itri
2005-05-22 1:09 ` Kay Sievers
2005-05-22 12:01 ` Marco d'Itri
2005-05-22 12:42 ` Kay Sievers
2005-05-22 12:55 ` Marco d'Itri
2005-05-22 13:00 ` Kay Sievers
2005-05-22 13:07 ` Marco d'Itri
2005-05-22 17:38 ` Kay Sievers [this message]
2005-05-23 6:52 ` Hannes Reinecke
2005-05-23 7:34 ` Marco d'Itri
2005-05-23 9:43 ` Marco d'Itri
2005-06-20 18:10 ` Marco d'Itri
2005-06-20 20:40 ` Kay Sievers
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=20050522173821.GA9959@vrfy.org \
--to=kay.sievers@vrfy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.