Gentoo Archives: gentoo-user

From: Meino Christian Cramer <Meino.Cramer@×××.de>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] udev.rules: Two "removeable" SATA-hds...how to map to /dev ???
Date: Fri, 04 Aug 2006 18:34:48
Message-Id: 20060804.203002.71094160.Meino.Cramer@gmx.de
In Reply to: Re: [gentoo-user] udev.rules: Two "removeable" SATA-hds...how to map to /dev ??? by Richard Fish
1 From: "Richard Fish" <bigfish@××××××××××.org>
2 Subject: Re: [gentoo-user] udev.rules: Two "removeable" SATA-hds...how to map to /dev ???
3 Date: Fri, 4 Aug 2006 10:28:38 -0700
4
5 > On 8/4/06, Etaoin Shrdlu <shrdlu@×××××××××××××.org> wrote:
6 > > [Fri Aug 04 11:38:50 root@bach ~]# ls -l /dev/disk/by-id/
7 > > [cut]
8 > > lrwxrwxrwx 1 root root 9 Jul 20 10:50
9 > > ata-Maxtor_6Y080L0_Y2CG9M5E -> ../../hde
10 > > lrwxrwxrwx 1 root root 9 Jul 20 10:50
11 > > ata-Maxtor_6Y080L0_Y3J1HW3E -> ../../hdg
12 >
13 > ARGH! Thanks Etaoin, I forgot about the by-id mappings.
14 >
15 > Meino, take a look at the by-id rules in 60-persistent-storage.rules.
16 > It looks like you can use the ENV{ID_SERIAL} to match SATA drives by
17 > serial.
18 >
19 > > The strange thing is that udev obviously knows the serial number of each
20 > > drive (udevinfo -q all -n /dev/sda *DOES* show the device's serial
21 > > number), but it seems that no file under /sys contains this information
22 >
23 > It uses the /lib/udev/scsi_id program to read the information directly
24 > from the drive.
25 >
26 > /lib/udev/scsi_id -g -s /block/sda -d /dev/sda
27 >
28 > -Richard
29 > --
30 > gentoo-user@g.o mailing list
31 >
32
33 Hi Richard,
34
35 sorry, may be this is again a very nooby question, but...
36
37 Where is that file ("60-persistent-storage.rules") ?
38 "locate" doesn't locate that file on my system...
39
40 Beside that: Great hack! Sounds like a real solution!
41 Thanks a lot!
42
43 Keep booting !
44 mcc
45 --
46 gentoo-user@g.o mailing list

Replies

Subject Author
Re: [gentoo-user] udev.rules: Two "removeable" SATA-hds...how to map to /dev ??? Richard Fish <bigfish@××××××××××.org>