From: "Gerald V. Livingston II" <gerald.hotplug@sysmatrix.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Statically nameing a SCSI device
Date: Sun, 12 Aug 2007 15:46:16 +0000 [thread overview]
Message-ID: <4804.65.170.133.237.1186933576.squirrel@webmail.sysmatrix.net> (raw)
In-Reply-To: <1240.65.170.133.237.1186867534.squirrel@webmail.sysmatrix.net>
On Sun, August 12, 2007 7:24, Kay Sievers said:
> On 8/12/07, gerald.hotplug@sysmatrix.net <gerald.hotplug@sysmatrix.net>
> wrote:
>>
>> Now, that being said, it will be a lot easier for *ME* if I always know
>> exactly where the SATA drives are located in the plain-old /dev tree and
>> if I can call them /dev/sdw or /dev/sdz rather than
>> /dev/disk/by-id/ata-WDC_WD2500YS-01S-WD-WCANY1955037
>>
>> I added this to my local.rules and udevtest says it works great for the
>> first drive I already have installed:
>>
>> KERNEL="sd*[!0-9]", IMPORT="/sbin/scsi_id -g -x $tempnode"
>> KERNEL="sd*[!0-9]",
>> ENV{ID_SERIAL}="SATA_WDC_WD2500YS-01_WD-WCANY1955037", NAME="sdw"
>>
>> As I add the other 3 drives I just need to add lines to identify their
>> serial numbers and set them at sdx, sdy, and sdz.
>
> If you change the default name of the nodes, you will never find the
> disk a possible error log from the kernel belongs to. You should only
> use symlinks.
>
> /dev/disk/* has probably all you need already without any custom rule.
>
> Kay
So, better would be:
KERNEL="sd*[!0-9]", IMPORT="/sbin/scsi_id -g -x $tempnode"
KERNEL="sd*[!0-9]",
ENV{ID_SERIAL}="SATA_WDC_WD2500YS-01_WD-WCANY1955037", SYMLINK+="sdw"
The disks will all be the same model so the info in /dev/disk will be the
same except for a number or two. Too easy to mix them up if I'm looking
for something specific while moving hardware around.
Gerald
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.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:[~2007-08-12 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 21:25 Statically nameing a SCSI device gerald.hotplug
2007-08-12 3:49 ` Greg KH
2007-08-12 5:50 ` Andrey Borzenkov
2007-08-12 8:16 ` gerald.hotplug
2007-08-12 12:24 ` Kay Sievers
2007-08-12 12:43 ` Andrey Borzenkov
2007-08-12 13:00 ` Kay Sievers
2007-08-12 15:46 ` Gerald V. Livingston II [this message]
2007-08-12 16:29 ` Kay Sievers
2007-08-12 16:58 ` Gerald V. Livingston II
2007-08-15 22:16 ` Gerald V. Livingston II
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=4804.65.170.133.237.1186933576.squirrel@webmail.sysmatrix.net \
--to=gerald.hotplug@sysmatrix.net \
--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).