mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rene Rebe <rene.rebe@gmx.net>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org, ziegler@informatik.hu-berlin.de
Subject: Re: IDE controller detection 2.4 +devfs
Date: Fri, 30 Nov 2001 01:27:52 +0100	[thread overview]
Message-ID: <20011130012752.0fd5380a.rene.rebe@gmx.net> (raw)
In-Reply-To: <200111300017.fAU0Hx704241@vindaloo.ras.ucalgary.ca>
In-Reply-To: <20011130001138.78ab1242.rene.rebe@gmx.net> <200111300017.fAU0Hx704241@vindaloo.ras.ucalgary.ca>

On Thu, 29 Nov 2001 17:17:59 -0700
Richard Gooch <rgooch@ras.ucalgary.ca> wrote:

> Rene Rebe writes:

[...]

> 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].

Aeh? I can not follow. I feel completely comfortable with the names (strings)
or subdirs, you use. My problem: I have 2 ide-controllers. I would like
to get them as host0 and host1. Boths with the sub-dirs bus0 and bus1.
Reading your answer I though you mean it is fixed due to the pci-id's - but
they do not match ...

And disabling one channel in the bios shouldn't move the controller
from host0 to host1 ... - I do not see the system-behind that ...

Btw. Thanks for DevFS it really ROCKs!! (Except that USBfs exists
and I can not maintain / controll it via the devfsd :-(()

> If you want to access your drives according to detection order, use
> /dev/discs instead.

Yes I know about this.

> 				Regards,
> 
> 					Richard....
> Permanent: rgooch@atnf.csiro.au
> Current:   rgooch@ras.ucalgary.ca


k33p h4ck1n6
  René

-- 
René Rebe (Registered Linux user: #127875 <http://counter.li.org>)

eMail:    rene.rebe@gmx.net
          rene@rocklinux.org

Homepage: http://www.tfh-berlin.de/~s712059/index.html

Anyone sending unwanted advertising e-mail to this address will be
charged $25 for network traffic and computing time. By extracting my
address from this message or its header, you agree to these terms.

  parent reply	other threads:[~2001-11-30  0:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29 23:11 Rene Rebe
2001-11-30  0:17 ` Richard Gooch
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 [this message]
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=20011130012752.0fd5380a.rene.rebe@gmx.net \
    --to=rene.rebe@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    --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

all inboxes | Powered by JetHome®