From: Nathan Walp <faceprint@faceprint.com>
To: David Balazic <david.balazic@uni-mb.si>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.2ac20
Date: Wed, 14 Mar 2001 10:12:49 -0500 [thread overview]
Message-ID: <3AAF8A71.1C71D517@faceprint.com> (raw)
In-Reply-To: <3AAE4DB6.8349ACBA@uni-mb.si> <3AAE7406.283D2411@faceprint.com> <3AAF3A56.C4EA2A95@uni-mb.si>
David Balazic wrote:
>
> Nathan Walp wrote:
> >
> > 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 )
> > >
> > > --
> > > David Balazic
> > > --------------
> > > "Be excellent to each other." - Bill & Ted
> > > - - - - - - - - - - - - - - - - - - - - - -
> >
> > 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???
> >
> > Nathan
>
> What I mean that too many factors are affecting the enumeration,
> so that you can not rely on it :
>
> - kernel changes
> - driver changes ( partly overlaps with the previous poit )
> - hardware changes
> - something else ?
>
> There is no policy for this enumeration ( AFAIK ) , so there is
> nothing to rely on , except luck :-)
See, that all makes sense. You can't depend on hardware to detect in
the same order, whether it's SCSI cards, network cards, or anything
really. But the software psuedo-device that is ide-scsi, shouldn't that
pick a spot before or after the hardware and stay there? That's my
point, i guess.
Nathan
next prev parent reply other threads:[~2001-03-14 15:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-13 16:41 Linux 2.4.2ac20 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 [this message]
2001-03-14 15:36 ` magic device renumbering was -- " John Jasen
2001-03-14 16:27 ` Tim Wright
2001-03-14 18:15 ` Greg KH
2001-03-15 1:53 ` Tim Wright
2001-03-15 2:08 ` Greg KH
2001-03-14 18:23 ` Christoph Hellwig
2001-03-14 18:45 ` Peter Svensson
2001-03-14 19:11 ` Lars Kellogg-Stedman
2001-03-14 19:34 ` Andreas Dilger
2001-03-14 19:44 ` Richard B. Johnson
2001-03-15 13:46 ` John Jasen
2001-03-14 20:01 ` Christoph Hellwig
2001-03-16 9:11 ` Stephen C. Tweedie
2001-03-14 19:16 ` Andreas Dilger
2001-03-14 20:08 ` John Jasen
2001-03-15 3:04 ` Stephen Degler
-- strict thread matches above, loose matches on Subject: below --
2001-03-13 23:46 Wayne.Brown
2001-03-13 23:41 Douglas Gilbert
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=3AAF8A71.1C71D517@faceprint.com \
--to=faceprint@faceprint.com \
--cc=david.balazic@uni-mb.si \
--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