From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: PATCH : new key MODEFILE
Date: Fri, 16 Mar 2007 00:55:40 +0000 [thread overview]
Message-ID: <1174006540.25945.18.camel@lov.localdomain> (raw)
In-Reply-To: <20070224023614.GA28903@bougret.hpl.hp.com>
On Tue, 2007-02-27 at 09:19 -0800, Jean Tourrilhes wrote:
> On Tue, Feb 27, 2007 at 01:47:27PM +0100, Kay Sievers wrote:
> > On Mon, 2007-02-26 at 09:42 -0800, Jean Tourrilhes wrote:
> >
> > > I designed it so that it's as
> > > generic as possible and can be used for many other things.
> > > For example, you can do :
> > > ------------------------------------------
> > > KERNEL="sdc1", MODEMASK{/mnt/media}="0100", RUN="mount /dev/%k /mnt/media"
> > > ------------------------------------------
> > > You could also do :
> > > ------------------------------------------
> > > KERNEL="sdb", MODEMASK{sda}="0001", MODEMASK{sda}="0002", MODE="0666"
> > > ------------------------------------------
> >
> > The node usually doesn't exist at this time. :)
>
> 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.
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"
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
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-03-16 0:55 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 [this message]
2007-03-16 1:04 ` Jean Tourrilhes
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=1174006540.25945.18.camel@lov.localdomain \
--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).