From: Rick Stevens <rstevens@vitalstream.com>
To: linux-scsi@vger.kernel.org
Subject: Re: [RFC] Persistent naming of scsi devices
Date: Tue, 09 Apr 2002 18:16:53 -0700 [thread overview]
Message-ID: <3CB39285.8000609@vitalstream.com> (raw)
In-Reply-To: OF8B2F3581.590066BE-ONC1256B95.0068B28C@de.ibm.com
Martin Peschke3 wrote:
<much stuff snipped>
I'm going to wade in here. Based on my experiences on many other
Unixish systems, wouldn't it be simply better to number the things
based on controller position, SCSI ID, LUN and partition? This
has been called "CTL" format in various documents, and many systems
use this method such as Sun, DG AvIIons, DEC, HP and a host of others.
E.g. "/dev/dsk/c0t1d2s3" is controller 0 (first SCSI controller seen on
the bus), target ID 1, LUN 2, partition (slice) 3. Simple, unambiguous
and repeatable.
I understand that other devices may be seen on the PCI if you add or
remove cards. Under this scheme, controller 0 is the first (lowest
slot number) unit found. The next one would be controller 1. Even
if you were to stuff, say, a video card in there, these would _still_
be the first SCSI cards found. The only time a change would occur
is if a SCSI card was installed in a lower slot number or between
other SCSI controllers (and only then if the original cards were
left in) or if the ORDER of the cards was changed in the bus.
As I said, other people smarter than I seem to think it makes sense.
Why not Linux? It's silly to smush things together just to satisfy a
bizzare craving to have a list of devices with no "holes" in it.
Besides "fsck"ing or "mkfs"ing drives, how often do you refer to them
by their names in "/dev", anyway?
This would also work for tape drives. However, they're rooted at
/dev/stape rather than /dev/dsk.
At boot, you could create more mnemonic names as symbolic links to the
CTL names if you wish (as is done with /dev/cdrom and such), but if
you absolutely want to talk to the SAME DEVICE, you use the CTL name.
Just adding my $0.02. We now return you to your regularly scheduled
arguments.
----------------------------------------------------------------------
- Rick Stevens, SSE, VitalStream, Inc. rstevens@vitalstream.com -
- 949-743-2010 (Voice) http://www.vitalstream.com -
- -
- su -; find / -name someone -exec touch \{\} \; -
- - The UNIX way of touching someone -
----------------------------------------------------------------------
next prev parent reply other threads:[~2002-04-10 1:16 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 19:18 [RFC] Persistent naming of scsi devices Martin Peschke3
2002-04-08 20:45 ` Matthew Jacob
2002-04-10 1:16 ` Rick Stevens [this message]
2002-04-10 2:01 ` Matthew Jacob
2002-04-10 2:17 ` Linus Torvalds
2002-04-10 3:37 ` Martin K. Petersen
2002-04-10 13:19 ` Theodore Tso
2002-04-10 14:04 ` Eddie Williams
2002-04-10 17:45 ` Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 20:13 sullivan
2002-06-06 1:08 ` Douglas Gilbert
2002-04-12 18:03 berthiaume_wayne
2002-04-12 17:18 Bryan Henderson
2002-04-12 13:15 berthiaume_wayne
2002-04-11 16:01 Bryan Henderson
2002-04-10 20:24 berthiaume_wayne
2002-04-10 19:02 Martin Peschke3
2002-04-10 16:44 berthiaume_wayne
2002-04-10 15:52 Martin Peschke3
2002-04-10 19:33 ` Matthew Jacob
2002-04-10 15:28 Bryan Henderson
2002-04-10 14:36 berthiaume_wayne
2002-04-10 16:02 ` Matthew Jacob
2002-04-10 14:28 berthiaume_wayne
2002-04-10 1:40 Bryan Henderson
2002-04-08 22:05 Martin Peschke3
2002-04-08 22:17 ` Matthew Jacob
2002-04-08 16:11 Matt_Domsch
2002-04-08 15:18 sullivan
2002-04-08 15:04 ` Christoph Hellwig
2002-04-08 15:59 ` Matthew Jacob
2002-04-08 16:34 ` James Bottomley
2002-04-08 18:27 ` Patrick Mansfield
2002-04-08 19:17 ` James Bottomley
2002-04-09 0:22 ` Douglas Gilbert
2002-04-09 14:35 ` sullivan
2002-04-09 14:55 ` sullivan
2002-04-08 17:51 ` Oliver Neukum
2002-04-08 18:01 ` Christoph Hellwig
2002-04-08 18:18 ` Matthew Jacob
2002-04-08 18:28 ` James Bottomley
2002-04-08 18:34 ` Matthew Jacob
2002-04-08 19:07 ` James Bottomley
2002-04-08 20:41 ` Matthew Jacob
2002-04-08 18:45 ` Tigran Aivazian
2002-04-08 20:18 ` Eddie Williams
2002-04-09 0:48 ` Kurt Garloff
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=3CB39285.8000609@vitalstream.com \
--to=rstevens@vitalstream.com \
--cc=linux-scsi@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.