From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Rene Rebe <rene.rebe@gmx.net>
Cc: linux-kernel@vger.kernel.org,
Valentin Ziegler <ziegler@informatik.hu-berlin.de>
Subject: Re: IDE controller detection 2.4 +devfs
Date: Thu, 29 Nov 2001 17:17:59 -0700 [thread overview]
Message-ID: <200111300017.fAU0Hx704241@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20011130001138.78ab1242.rene.rebe@gmx.net>
In-Reply-To: <20011130001138.78ab1242.rene.rebe@gmx.net>
Rene Rebe writes:
> I like to rereport that the IDE Controllers get strange device-
> node-number in Linux-2.4 (currently vanilla 2.4.16) at least using DevFS.
>
> I reported (~a year ago) that when I disable the primary channel of the
> on-board controller of the Asus-K7M (Irongate based) the second channel
> will be host1 - no host0 can be found.
>
> My today's issue is our K6-2 based server with an Gigabyte Ali-Aladin5
> board. The on-board controller is host0 but the additional Promisse
> TX2 Ultra100 will be host2 ??? no host1 there ... :
>
> server1:~ # l /dev/ide/
> total 0
> drwxr-xr-x 1 root root 0 Jan 1 1970 .
> drwxr-xr-x 1 root root 0 Jan 1 1970 ..
> drwxr-xr-x 1 root root 0 Jan 1 1970 host0
> drwxr-xr-x 1 root root 0 Jan 1 1970 host2
So what's the problem? It's a similar naming scheme as used for
SCSI. It doesn't matter if you have something plugged into a bus, the
host numbering doesn't change. This is a Feature[tm].
If you want to access your drives according to detection order, use
/dev/discs instead.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-11-30 0:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 23:11 IDE controller detection 2.4 +devfs Rene Rebe
2001-11-30 0:17 ` Richard Gooch [this message]
2001-11-30 0:34 ` Richard Gooch
2001-11-30 1:11 ` Richard Gooch
2001-11-30 2:10 ` Richard Gooch
2001-11-30 0:27 ` Rene Rebe
2001-11-30 0:55 ` Rene Rebe
2001-11-30 1:26 ` Rene Rebe
2001-12-05 0:07 ` Rene Rebe
2001-11-30 5:58 ` Greg KH
2001-11-30 7:56 ` Rene Rebe
2001-11-30 8:16 ` Greg KH
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=200111300017.fAU0Hx704241@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.rebe@gmx.net \
--cc=ziegler@informatik.hu-berlin.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;
as well as URLs for NNTP newsgroup(s).