linux-hotplug.vger.kernel.org archive mirror
 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: Sun, 22 May 2005 01:09:20 +0000	[thread overview]
Message-ID: <20050522010920.GA5296@vrfy.org> (raw)
In-Reply-To: <20050519065848.GA25640@kroah.com>

On Sun, May 22, 2005 at 02:59:28AM +0200, Marco d'Itri wrote:
> On May 20, Kay Sievers <kay.sievers@vrfy.org> wrote:
> 
> > > Why not? I think it's a very reasonable request. Different people have
> > > different ideas about /dev.
> > 
> > Well I still don't see a real need for this. Anyway, what about some
> > "final assignments" instead:
> >   GROUP:="mygroup" or
> >   SYMLINK:="mylink"
> > would set the value unchangeable for later rules. That may give us finer
> > grained control and if you leave the permissions alone with your
> > user-rule you still get the systems default.
> 
> I don't get it... Now you invented a third kind of assignment, and you
> say that all this is simpler to use and to understand than just
> supporting OPTIONS="last_run_rule" (which would also allow overriding
> the RUN rules and simplify the rules for the console devices).
> 
> I'm attaching a patch which shows how simple supporting this would be.

Too simple! How do you control symlinks, control permissions with
a user-rule. You want a last_symlink_rule, last_permission_rule? I will
implement := final assigments that prevent changes by later rules and
everything should work.

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-22  1:09 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 [this message]
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=20050522010920.GA5296@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 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).