From: Andrzej Krzysztofowicz <ankry@pg.gda.pl>
To: wolfgang@leila.ping.de (Wolfgang Wegner)
Cc: michael@wd21.co.uk (Michael Pacey), linux-kernel@vger.kernel.org
Subject: Re: Multiple SCSI host adapters, naming of attached devices
Date: Wed, 31 Jan 2001 09:31:29 +0100 (MET) [thread overview]
Message-ID: <200101310831.JAA01369@sunrise.pg.gda.pl> (raw)
In-Reply-To: <200101310038.BAA21051@noefs.ping.de> from "Wolfgang Wegner" at Jan 31, 2001 01:38:39 AM
"Wolfgang Wegner wrote:"
> > Given two host adapters each with 1 disk of ID 0, how do I tell Linux which
> > is sda and which sdb?
> [...]
> which leads me to the question:
> Is there any reason for the (IMHO stupid) "dynamic" naming of
> SCSI devices (in contrast to e.g. IDE devices or the "physical"
> device naming used in Solaris)?
Yes. Shortage of 16-bit major/minor numbers.
> It may be possible always maintaining the "right" order with
> one SCSI chain, but as soon as there is a second bus, it is
> really a pain. Is devfs the only solution?
You can try:
- loading scsi drivers as modules in appropriate order (possibly using
initrd if root filesystem is located on any of them)
- using devfs names.
--
=======================================================================
Andrzej M. Krzysztofowicz ankry@mif.pg.gda.pl
phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math., Technical University of Gdansk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-31 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 22:49 Michael Pacey
2001-01-30 23:06 ` Michael Pacey
2001-01-31 8:26 ` Andrzej Krzysztofowicz
2001-01-31 21:39 ` Michael Pacey
2001-01-31 0:38 ` Wolfgang Wegner
2001-01-31 8:31 ` Andrzej Krzysztofowicz [this message]
2001-01-31 1:05 ` Andreas Dilger
2001-01-31 1:22 ` Michael Pacey
2001-01-31 2:28 ` Andreas Dilger
2001-01-31 2:06 ` Michael Pacey
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=200101310831.JAA01369@sunrise.pg.gda.pl \
--to=ankry@pg.gda.pl \
--cc=ankry@green.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@wd21.co.uk \
--cc=wolfgang@leila.ping.de \
/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®