From: Patrick Mansfield <patmans@us.ibm.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-hotplug-devel@lists.sourceforge.net, dm-devel@redhat.com
Subject: Re: udev user specified or human readable /dev names
Date: Wed, 02 Nov 2005 02:01:56 +0000 [thread overview]
Message-ID: <20051102020156.GA17330@us.ibm.com> (raw)
In-Reply-To: <20051102010615.GA18684@vrfy.org>
On Wed, Nov 02, 2005 at 02:06:15AM +0100, Kay Sievers wrote:
> On Tue, Nov 01, 2005 at 04:35:31PM -0800, Patrick Mansfield wrote:
> > But it still would not match, per the issue below, right?
>
> Right, it wouldn't work.
>
> You want this:
> ENV{ID_FULL_PATH}="disk/by-id/scsi-360a98000686f68656c6e7a416f4b6849" SYMLINK+="media-files"
>
> but why don't you just do:
> ENV{ID_BUS}="scsi", ENV{ID_SERIAL}="360a98000686f68656c6e7a416f4b6849", SYMLINK+="media-files"
>
> The second already works, is independent from all other rules and I think
> is simpler.
Yes, I just disagree with it being simpler for all busses/devices.
I was thinking of the sys admin or a tool looking at the current
/dev/disk/by-* and adding rule(s) based on those values to a udev rule
file.
And is there a way to rename or add /dev entries without removing and
adding back a device?
Using ID_BUS and ID_SERIAL via the following lines like this works:
KERNEL="sd*[!0-9]", ENV{ID_BUS}="scsi" ENV{ID_SERIAL}="360a98000686f68656c6e7a416f4b6849", SYMLINK+="user/databaseA"
KERNEL="sd*[0-9]|dasd*[0-9]", ENV{ID_SERIAL}="360a98000686f68656c6e7a416f4b6849", SYMLINK+="user/databaseA-part%n"
KERNEL="sd*[!0-9]", ENV{ID_BUS}="scsi" ENV{ID_SERIAL}="360a98000686f68656c6e7a416f4b2f55", SYMLINK+="user/databaseB"
KERNEL="sd*[0-9]", ENV{ID_SERIAL}="360a98000686f68656c6e7a416f4b2f55", SYMLINK+="user/databaseB-part%n"
Adding the devices then creates:
[root@elm3a49 rules.d]# ls -l /dev/user
total 0
lrwxrwxrwx 1 root root 6 Nov 1 17:46 databaseA -> ../sdm
lrwxrwxrwx 1 root root 7 Nov 1 17:47 databaseA-part1 -> ../sdm1
lrwxrwxrwx 1 root root 6 Nov 1 17:46 databaseB -> ../sdi
lrwxrwxrwx 1 root root 7 Nov 1 17:46 databaseB-part1 -> ../sdi1
lrwxrwxrwx 1 root root 7 Nov 1 17:46 databaseB-part2 -> ../sdi2
-- Patrick Mansfield
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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:[~2005-11-02 2:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 22:53 udev user specified or human readable /dev names Patrick Mansfield
2005-11-02 0:05 ` Kay Sievers
2005-11-02 0:35 ` Patrick Mansfield
2005-11-02 1:06 ` Kay Sievers
2005-11-02 2:01 ` Patrick Mansfield [this message]
2005-11-02 2:53 ` Kay Sievers
2005-11-02 15:30 ` Patrick Mansfield
2005-11-02 23:49 ` 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=20051102020156.GA17330@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=dm-devel@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
/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).