From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev.rules.devfs patch
Date: Thu, 15 Jan 2004 15:07:53 +0000 [thread overview]
Message-ID: <20040115150753.GA15742@vrfy.org> (raw)
In-Reply-To: <200401151523.58821.john-hotplug@fjellstad.org>
On Thu, Jan 15, 2004 at 10:00:55AM -0500, Martin Hicks wrote:
> On Thu, Jan 15, 2004 at 03:49:10PM +0100, Kay Sievers wrote:
> > Greg, I would be happy to remove the ugly %D at all.
> > It's unable to handle cdroms, an the 'dis[ck]'/'partition' thing is easy done by two rules.
> > Then the dis[ck] decision is also up to the user :)
>
> Please don't get rid of %D. I just started using it. The problem that
> I'm dealing with is that the directory where the devfs names are created
> are unpredictable so my callout returns the directory that I'm to create
> the devfs names in and I do something like:
>
> BUS="scsi", CALLOUT="blah", ID="*", NAME="%c/%D", SYMLINK="%c/theAlias"
I don't see your need.
Just use two rules matching with the kernel name, or handle the %D in your script.
And ID= is gone now, in udev v013. We are using RESULT= instead.
I vote for killing the %D :)
Kay
-------------------------------------------------------
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-15 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 14:23 udev.rules.devfs patch John L. Fjellstad
2004-01-15 14:49 ` Kay Sievers
2004-01-15 15:00 ` Martin Hicks
2004-01-15 15:07 ` Kay Sievers [this message]
2004-01-15 21:43 ` Greg KH
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=20040115150753.GA15742@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.