All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: new release of udev?
Date: Thu, 19 May 2005 14:12:20 +0000	[thread overview]
Message-ID: <20050519141220.GA857@vrfy.org> (raw)
In-Reply-To: <20050519065848.GA25640@kroah.com>

On Thu, May 19, 2005 at 12:32:20PM +0200, Marco d'Itri wrote:
> On May 19, Kay Sievers <kay.sievers@vrfy.org> wrote:
> 
> > Only the use of the RUN key is a bit difficult then. To solve that, I
> > will implement deferred(question mark) assignment, like in Makefiles for
> > the default system-supplied rules to use:
> >   SUBSYSTEM="block", GROUP?="disk"
> > 
> > will only set the permissions if no other rule has already set the
> > group. This should solve that small issue.
> As I explained in our private discussion, this is complex and does not
> solve the SYMLINK problem: users would still not be able to override
> the distribution SYMLINK directives without using last_rule, which is
> not an option because it breaks RUN processing.

Well, SYMLINK is a list not a single value. Why does someone want to
supress the additional system-supplied symlinks?

> With its current semantics, last_rule should almost never be used by
> users.

Yeah, it can be used exactly for what the name stands for. :)

> I still think that having different "last_rule" directives for NAME and
> RUN rules would be a better solution, and it looks much simpler to
> implement and understand too.

I don't think that this is simpler in any kind. That moves the complexity
away from the system-rules to the user-rules. And the system-rule
writer _must_ understand the complexity anyway. :)

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

  parent reply	other threads:[~2005-05-19 14:12 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 [this message]
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
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=20050519141220.GA857@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.