From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Rob Landley <rob@landley.net>
Cc: dougg@torque.net, James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi@vger.kernel.org
Subject: Re: Some quick scsi documentation questions:
Date: Thu, 02 Aug 2007 23:19:51 +0200 [thread overview]
Message-ID: <46B24A77.2050809@s5r6.in-berlin.de> (raw)
In-Reply-To: <46B2256A.3070902@torque.net>
> Rob Landley wrote:
>> On Thursday 26 July 2007 9:15:11 am James Bottomley wrote:
>>> Users have great difficulty understanding how to
>>> map sg to sr (or sd), so we're trying to encourage them only to use the
>>> actual device node, so /dev/sdx or /dev/srn.
>> Actually, these days everybody I know uses /dev/cdrom, expects it to be a
>> symlink, and doesn't care where it points. Last time I used a system that
>> had more than one of the suckers I believe it had /dev/cdrom0, /dev/cdrom1,
>> etc.
>>
>> I note that in the ubuntu system on my laptop, /dev/sr0 is a symlink
>> to /dev/scd0, which is an actual device node with a major and minor that
>> presumably means something to the system, but not to me personally. (Not
>> that I consider Ubuntu 7.04 much of a model on how to arrange devices
>> considering it put a UUID label on every _partition_ on my hard drive and
>> mounts them by label in /etc/fstab rather than that having udev do its job
>> and make stable symlinks.)
>>
>> But it seems that users aren't the only ones who have trouble with this,
>> distro maintainers do too.
Alternatively to partition labels, you can also have udev create
persistently named symlinks for you.
$ ls /dev/disk/by-id/
ata-HTE721010G9AT00_MPC0J1Y0GRKYGD
ata-HTE721010G9AT00_MPC0J1Y0GRKYGD-part1
ata-HTE721010G9AT00_MPC0J1Y0GRKYGD-part2
ieee1394-00101003ae0001e0:00042c:0000
ieee1394-00101003ae0001e0:00042c:0000-part1
scsi-SATA_ST3750640AS_3QD067RX
scsi-SATA_ST3750640AS_3QD067RX-part1
usb-JetFlash_128MB_39680ADE3E2627FB
usb-JetFlash_128MB_39680ADE3E2627FB-part1
The udev rules I have here (Gentoo's) apparently don't do this for
CD/DVD-ROM/R/Ws although that should be possible as well. On the other
hand, application programs like K3B already nicely show devices with
vendor and model strings. I don't know how much effort that imposes on
the application programs.
--
Stefan Richter
-=====-=-=== =--- ---=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-08-02 21:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707252328.28981.rob@landley.net>
[not found] ` <1185455711.3501.46.camel@localhost.localdomain>
2007-07-27 21:29 ` Some quick scsi documentation questions: Rob Landley
2007-08-02 18:41 ` Douglas Gilbert
2007-08-02 21:19 ` Stefan Richter [this message]
2007-08-03 0:55 ` Rob Landley
2007-08-03 10:43 ` Stefan Richter
2007-08-03 21:11 ` Rob Landley
2007-08-04 0:08 ` Stefan Richter
2007-08-04 0:35 ` Stefan Richter
2007-08-05 16:50 ` Douglas Gilbert
2007-08-06 16:29 ` Rob Landley
2007-08-06 18:30 ` Stefan Richter
2007-08-02 21:39 ` Stefan Richter
2007-08-03 1:12 ` Rob Landley
2007-08-03 8:15 ` Stefan Richter
2007-08-03 19:07 ` Rob Landley
2007-08-03 19:37 ` Stefan Richter
2007-08-03 21:39 ` Rob Landley
2007-08-03 0:39 ` Rob Landley
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=46B24A77.2050809@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@steeleye.com \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=rob@landley.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