From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Gerald V. Livingston II" Date: Sun, 12 Aug 2007 15:46:16 +0000 Subject: Re: Statically nameing a SCSI device Message-Id: <4804.65.170.133.237.1186933576.squirrel@webmail.sysmatrix.net> List-Id: References: <1240.65.170.133.237.1186867534.squirrel@webmail.sysmatrix.net> In-Reply-To: <1240.65.170.133.237.1186867534.squirrel@webmail.sysmatrix.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sun, August 12, 2007 7:24, Kay Sievers said: > On 8/12/07, 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