From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev - question about current config format
Date: Sat, 10 Jan 2004 04:03:42 +0000 [thread overview]
Message-ID: <20040110040342.GD6911@kroah.com> (raw)
In-Reply-To: <20040109142112.GA752@vrfy.org>
On Sat, Jan 10, 2004 at 05:01:31AM +0100, Kay Sievers wrote:
> On Fri, Jan 09, 2004 at 07:52:43PM -0800, Greg KH wrote:
> > On Sat, Jan 10, 2004 at 02:38:50AM +0100, Kay Sievers wrote:
> > > On Fri, Jan 09, 2004 at 05:30:20PM -0800, Greg KH wrote:
> > > > On Fri, Jan 09, 2004 at 03:21:12PM +0100, Kay Sievers wrote:
> > > > > Every line in udev.rules consists only of a number of <key>="<value>"
> > > > >
> > > > > BUS match with bus type
> > > > > SYSFS_<file> match with device attribute
> > > > > ID/PLACE match with bus "number" or "id"
> > > > > KERNEL match with kernel device name
> > > > > RESULT match with string returned by executed PROGRAM
> > > > > PROGRAM program to execute (true if exec returned with 0)
> > > >
> > > > So don't match on a string value here? Hm, would that make writing
> > > > programs easier? At first glance it might. It also might be a bit
> > > > easier to understand.
> > >
> > > What kind of string value do you mean?
> >
> > Sorry, I meant the string return value of the script. Like I had to
> > hack "good" and "bad" as return values of the name_cd script. The ID> > stuff.
>
> I'm thinking of:
>
> PROGRAM= is true when it exits successful
> RESULT= is compared with the returned string, but it is not neccessary
> like todays ID= if the exit code it enough.
> Just exit with nonzero in your name_cd - no "good" or "bad" :)
Ah, that's much nicer, and pretty sane.
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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:[~2004-01-10 4:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 14:21 udev - question about current config format Kay Sievers
2004-01-10 1:30 ` Greg KH
2004-01-10 1:38 ` Kay Sievers
2004-01-10 3:52 ` Greg KH
2004-01-10 4:01 ` Kay Sievers
2004-01-10 4:03 ` Greg KH [this message]
2004-01-10 5:27 ` Kay Sievers
2004-01-10 5:39 ` 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=20040110040342.GD6911@kroah.com \
--to=greg@kroah.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).