From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev.rules syntax question
Date: Tue, 23 Nov 2004 00:58:06 +0000 [thread overview]
Message-ID: <1101171486.12199.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20041123004518.GA179133@sgi.com>
On Mon, 2004-11-22 at 16:45 -0800, Jeremy Higdon wrote:
> Hello,
>
> I have a rules file with the following rules:
>
> BUS="scsi", PROGRAM="/sbin/udev_xscsi", SYMLINK="%c"
> BUS="scsi", PROGRAM="/sbin/udev.get_persistent_device_name.sh", NAME="%k" SYMLINK="%c{1+}"
>
>
> By my reading of the documentation, both rules should provide a symlink to
> the canonical name (/dev/sda, or whatever).
>
> However, I only get the symlinks from the second rule. If I change the first
> line to:
>
> BUS="scsi", PROGRAM="/sbin/udev_xscsi", NAME="%k" SYMLINK="%c"
>
>
> then I only get the symlink from the first rule.
That should work, right.
> I'm running udev version 021, if that makes a difference.
Huh, that's 9 months old, the whole project is 20 months old :)
So you may try an update, we are at v046 now :)
That may be the reason:
http://linuxusb.bkbits.net:8080/udev/cset@4061c688A1oxsmFdksypgMHPeY9kEA
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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-11-23 0:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 0:45 udev.rules syntax question Jeremy Higdon
2004-11-23 0:58 ` Kay Sievers [this message]
2004-11-23 7:02 ` Jeremy Higdon
2004-11-23 7:48 ` Greg KH
2004-11-23 8:53 ` Hannes Reinecke
2004-11-23 8:58 ` Kay Sievers
2004-11-23 9:17 ` Hannes Reinecke
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=1101171486.12199.5.camel@localhost.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).