From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev-124, USB tape drive
Date: Fri, 11 Jul 2008 08:05:52 +0000 [thread overview]
Message-ID: <1215763552.4197.12.camel@linux.site> (raw)
In-Reply-To: <48757C12.7020201@mib-infotech.co.nz>
On Fri, 2008-07-11 at 11:36 +1200, John Huttley wrote:
> Ok, attached is my 60-persistent-storage-tape.rules
>
> adding |nst*[0-9] seems to have fixed the issue.
>
> my tape/by-id/ looks like
>
> HP-C7438A-4855310710385844 -> ../../st4
> HP-C7438A-4855310710385844-nst -> ../../nst4
> HP-Ultrium_1-SCSI-HU84H06998 -> ../../st3
> HP-Ultrium_1-SCSI-HU84H06998-nst -> ../../nst3
> HP-Ultrium_2-SCSI-HUL3K02633 -> ../../st2
> HP-Ultrium_2-SCSI-HUL3K02633-nst -> ../../nst2
> QUANTUM-DLT8000-PXB23P0605 -> ../../st1
> QUANTUM-DLT8000-PXB23P0605-nst -> ../../nst1
> QUANTUM-DLT8000-PXB23P0632 -> ../../st0
> QUANTUM-DLT8000-PXB23P0632-nst -> ../../nst0
> STK-L80-LLC02205205 ->../../sg1
>
>
> which in my opinion is a huge improvement, since I can see which drive
> is which and the serial number matches up with the serial number shown
> by tapeinfo.
>
> I think that should be the standard.
Thanks! I've added the nst* matches. We currently prefix all links with
the bus, to keep the id's unique. I left that in for now, we better
should not break _all_ currently used links. :) Why are you using
ID_SERIAL_SHORT? scsi_id already does all the needed logic to produce a
unique id, right?
> The USB drive (C7438A) is now consistent between st and nst, however the
> serial number is HU107108XD not 4855310710385844.
It's the USB serial number from the USB device. I guess that's fine.
> I have no idea how to fix that since the rules now use things like bsg
> and usb_id %p which are entirely undocumented.
/dev/bsg/* is just like sg*, only with a newer protocol version. sg will
eventually go away, and in the longer term we will fix bsg to show up
before the tape/disk/... nodes, so the WAIT_FOR rule can go.
usb_id just tries to extract persistent data from the USB device
strings/descriptors. It's a bit magic, but does basically just what the
command line output shows:
/lib/udev/usb_id --export /devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/input/input10/mouse1
ID_VENDOR=Logitech
ID_MODEL=USB-PS.2_Optical_Mouse
ID_REVISION 00
ID_SERIAL=Logitech_USB-PS.2_Optical_Mouse
ID_TYPE=hid
ID_BUS=usb
/lib/udev/usb_id --export /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host7/target7:0:0/7:0:0:0/block/sdb
ID_VENDOR=SAMSUNG
ID_MODEL=HM160HI
ID_REVISIONì02
ID_SERIAL=SAMSUNG_HM160HI_SAMSUNG_HMS10UJD0PA02660-0:0
ID_SERIAL_SHORT=SAMSUNG_HMS10UJD0PA02660
ID_TYPE=disk
ID_INSTANCE=0:0
ID_BUS=usb
Kay
prev parent reply other threads:[~2008-07-11 8:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 3:03 Udev-124, USB tape drive John Huttley
2008-07-10 22:46 ` Kay Sievers
2008-07-10 23:36 ` John Huttley
2008-07-11 8:05 ` Kay Sievers [this message]
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=1215763552.4197.12.camel@linux.site \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.