From: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
To: Glenn McGrath <bug1@optushome.com.au>
Cc: Helge Hafting <helgehaf@idb.hist.no>, linux-kernel@vger.kernel.org
Subject: Re: devfs and /proc/ide/hda
Date: Wed, 28 Feb 2001 12:58:46 +0100 [thread overview]
Message-ID: <3A9CE7F6.2000202@wanadoo.fr> (raw)
In-Reply-To: <3A9CCA76.3E6AB93A@optushome.com.au> <3A9CD2F3.E26A2884@idb.hist.no> <3A9CD304.26C3A568@optushome.com.au>
Glenn McGrath wrote:
> Helge Hafting wrote:
>
>> Glenn McGrath wrote:
>>
>>> Im running kernel 2.4.1, I have entries like /proc/ide/hda,
>>> /proc/ide/ide0/hda etc irrespective of wether im using devfs or
>>> traditional device names.
>>>
>>> Is always using traditional device names for /proc/ide intentional, or
>>> is it something nobody has gotten around to fixing yet?
>>
>> Using devfs changes the names in /dev. I don't think it
>> is supposed to affect /proc in any way. And there are programs out
>> that use the existing /proc - changing it won't be popular.
>>
>
>
> Well leaving it the way it is doesnt make much sense either really, it
> refers to devices that dont exist.
IMHO ide0 ide1... are naming plugs on the motherboard. They are not
competing with special file names. It is a drawback of devfs to change
the device name when you happen to use a hd as a removable media.
hdd was disc0 and becomes disc1 when you plug in an hda...
Pierre
--
------------------------------------------------
Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------
next prev parent reply other threads:[~2001-02-28 12:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 9:52 devfs and /proc/ide/hda Glenn McGrath
2001-02-28 10:29 ` Helge Hafting
2001-02-28 10:29 ` Glenn McGrath
2001-02-28 11:58 ` Pierre Rousselet [this message]
2001-02-28 15:15 ` Guest section DW
2001-02-28 15:10 ` Guest section DW
2001-03-01 14:41 ` AJ Lewis
2001-03-08 12:32 ` Goswin Brederlow
2001-04-27 16:09 ` AJ Lewis
2001-04-27 16:22 ` Richard Gooch
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=3A9CE7F6.2000202@wanadoo.fr \
--to=pierre.rousselet@wanadoo.fr \
--cc=bug1@optushome.com.au \
--cc=helgehaf@idb.hist.no \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.