From: Jean Tourrilhes <jt@hpl.hp.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: PATCH : new key MODEFILE
Date: Fri, 16 Mar 2007 01:04:06 +0000 [thread overview]
Message-ID: <20070316010406.GA13009@bougret.hpl.hp.com> (raw)
In-Reply-To: <20070224023614.GA28903@bougret.hpl.hp.com>
On Fri, Mar 16, 2007 at 01:55:40AM +0100, Kay Sievers wrote:
> On Tue, 2007-02-27 at 09:19 -0800, Jean Tourrilhes wrote:
> >
> > Check again the rule, it's more subtle than that.
>
> We don't know, if sda is created before sdb. I don't think we should
> match on other device properties, that just asks for timing trouble,
> especially during coldplug where everything (that hasn't a parent-child
> relation) runs in parallel.
Ok, I admit that my rule was contrieved. And most likely useless.
>
> How about a TEST{<mask>}=<file> key that accepts the usual:
> e, f, d, r, w, x, or an octal bitmask?
> It would look like:
> TEST{r}="/etc/foo"
> TEST{w}="/tmp/foo"
> TEST{0002}="/tmp/foo"
It seems to me that accepting the letters would be a lot of
work, because of the variety of combinations, unless we can grab that
from a library. But we don't want to depend on libraries.
As the setting of mode with MODE="" seems to accept only octal
bitmask, I was trying to match both with the same functionality. In
any case, if you implement letters, MODE="" would be the first place
where I would use it ;-)
> I don't think, we should default to /dev, reading from there is nothing
> we want to encourage anybody to do. And I think a single key per rule
> would be fine for a start.
>
> Thanks,
> Kay
Thinking over it, we may want to think a bit more about
it. Just drop it in your todo list and in a few months check if it
still make sense. I use that method to great effect ;-)
Thanks, and have fun...
Jean
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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
prev parent reply other threads:[~2007-03-16 1:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 2:36 PATCH : new key MODEFILE Jean Tourrilhes
2007-02-24 4:48 ` Andrey Borzenkov
2007-02-24 14:34 ` Kay Sievers
2007-02-24 14:58 ` Marco d'Itri
2007-02-26 17:42 ` Jean Tourrilhes
2007-02-27 12:47 ` Kay Sievers
2007-02-27 17:19 ` Jean Tourrilhes
2007-03-16 0:55 ` Kay Sievers
2007-03-16 1:04 ` Jean Tourrilhes [this message]
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=20070316010406.GA13009@bougret.hpl.hp.com \
--to=jt@hpl.hp.com \
--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).