From: Douglas Gilbert <dougg@torque.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.2ac20
Date: Tue, 13 Mar 2001 18:41:53 -0500 [thread overview]
Message-ID: <3AAEB041.9C4AC923@torque.net> (raw)
> David Balazic wrote:
> >
> > Nathan Walp (faceprint@faceprint.com) wrote :
> >
> > > Also, sometime between ac7 and ac18 (spring break kept me from testing
> > > stuff inbetween), i assume during the new aic7xxx driver merge, the
> > > order of detection got changed, and now the ide-scsi virtual host is
> > > host0, and my 29160N is host1. Is this on purpose? It messed up a
> > > bunch of my stuff as far as /dev and such are concerned.
> >
> > SCSI adapters are enumerated randomly(*) , relying on certain numbering
> > will get you into trouble, sooner or later.
> > There is no commonly accepted solution, AFAIK.
> > The same thing can happent to disk enumeration ( sdb becomes sdc )
> > or partition enumeration ( hda6 becomes hda5 ).
> >
> > * - theoreticaly no, but practicaly yes ( most of the time )
>
> SCSI adapters are given host numbers in a random order? Even with no
> hardware changes? Does this make less than sense to anyone else? Every
> kernel EVER up till now has had the real scsi cards (in some particular
> order) then ide-scsi. Have I just been lucky???
Built in scsi adapter drivers are probed in the order in
which they appear in drivers/scsi/Makefile (in the lk 2.4
series). Adapters can be assigned to host numbers using
the "scsihosts" kernel boot option (but this will not
differentiate between 2 adapters controlled by the same
driver (e.g. 2 29160 cards)). Scsi buses are scanned for
devices in ascending order.
If you have lots of SCSI devices then devfs is your friend.
Doug Gilbert
next reply other threads:[~2001-03-13 23:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-13 23:41 Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-13 23:46 Linux 2.4.2ac20 Wayne.Brown
2001-03-13 16:41 David Balazic
2001-03-13 19:24 ` Nathan Walp
2001-03-13 23:02 ` Tim Wright
2001-03-14 9:31 ` David Balazic
2001-03-14 15:12 ` Nathan Walp
2001-03-13 4:36 Alan Cox
2001-03-13 6:28 ` Nathan Walp
2001-03-13 23:17 ` Michal Jaegermann
2001-03-13 23:38 ` Jeff Garzik
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=3AAEB041.9C4AC923@torque.net \
--to=dougg@torque.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