From: Chris Adams <cmadams@hiwaay.net>
To: linux-kernel@vger.kernel.org
Subject: Re: /proc/scsi/map
Date: Tue, 18 Jun 2002 15:06:54 -0500 [thread overview]
Message-ID: <20020618150654.A506017@hiwaay.net> (raw)
Once upon a time, Doug Ledford <dledford@redhat.com> said:
>Umm, this patently fails to meet the criteria you posted of "stable device
>name". Adding a controller to a system is just as likely to blow this
>naming scheme to hell as it is to blow the traditional linux /dev/sd?
>scheme. IOW, even though the /proc/scsi/map file looks nice and usefull,
>it fails to solve the very problem you are trying to solve.
I use OSF/1^WDigital Unix^WCompaq^WHP Tru64 Unix here at work, and with
version 5, they've got a nice persistent device naming system (I don't
claim to know how it works however). The first hard drive found is
/dev/disk/dsk0, the second is /dev/disk/dsk1, etc. It doesn't matter
how you get to the drive (which is important if you want multipathing -
the controller and bus should NOT figure into the device name or you are
going to have problems). If you remove dsk0, there won't be another
dsk0 (unless you clean it out of the device database).
--
Chris Adams <cmadams@hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
next reply other threads:[~2002-06-18 20:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 20:06 Chris Adams [this message]
2002-06-18 20:25 ` /proc/scsi/map Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2002-06-17 12:55 /proc/scsi/map Heinz, Michael
2002-06-16 15:59 /proc/scsi/map Borsenkow Andrej
2002-06-15 23:00 /proc/scsi/map Andries.Brouwer
2002-06-15 21:54 /proc/scsi/map Andries.Brouwer
2002-06-15 22:27 ` /proc/scsi/map Douglas Gilbert
2002-06-15 22:40 ` /proc/scsi/map Sancho Dauskardt
2002-06-16 20:36 ` /proc/scsi/map Kurt Garloff
2002-06-15 22:28 ` /proc/scsi/map Sancho Dauskardt
2002-06-15 21:08 /proc/scsi/map Douglas Gilbert
2002-06-15 16:04 /proc/scsi/map Andries.Brouwer
2002-06-16 21:04 ` /proc/scsi/map Kurt Garloff
[not found] <garloff@suse.de>
2002-06-15 13:36 ` /proc/scsi/map Kurt Garloff
2002-06-15 14:08 ` /proc/scsi/map John Summerfield
2002-06-17 11:33 ` /proc/scsi/map Kurt Garloff
2002-06-15 15:52 ` /proc/scsi/map Richard Gooch
2002-06-16 19:41 ` /proc/scsi/map Kurt Garloff
2002-06-17 17:49 ` /proc/scsi/map Ingo Oeser
2002-06-15 19:49 ` /proc/scsi/map Sancho Dauskardt
2002-06-16 19:24 ` /proc/scsi/map Albert D. Cahalan
2002-06-16 21:22 ` /proc/scsi/map Kurt Garloff
2002-06-17 20:35 ` /proc/scsi/map Patrick Mansfield
2002-06-17 20:57 ` /proc/scsi/map Kurt Garloff
2002-06-17 21:47 ` /proc/scsi/map Patrick Mansfield
2002-06-17 22:08 ` /proc/scsi/map Doug Ledford
2002-06-17 23:06 ` /proc/scsi/map Kurt Garloff
2002-06-18 2:40 ` /proc/scsi/map Doug Ledford
2002-06-18 4:32 ` /proc/scsi/map Douglas Gilbert
2002-06-18 5:12 ` /proc/scsi/map Doug Ledford
2002-06-18 9:03 ` /proc/scsi/map 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=20020618150654.A506017@hiwaay.net \
--to=cmadams@hiwaay.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®