From: Guest section DW <dwguest@win.tue.nl>
To: Glenn McGrath <bug1@optushome.com.au>,
Helge Hafting <helgehaf@idb.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: devfs and /proc/ide/hda
Date: Wed, 28 Feb 2001 16:15:40 +0100 [thread overview]
Message-ID: <20010228161540.B19929@win.tue.nl> (raw)
In-Reply-To: <3A9CCA76.3E6AB93A@optushome.com.au> <3A9CD2F3.E26A2884@idb.hist.no> <3A9CD304.26C3A568@optushome.com.au>
In-Reply-To: <3A9CD304.26C3A568@optushome.com.au>; from Glenn McGrath on Wed, Feb 28, 2001 at 09:29:24PM +1100
On Wed, Feb 28, 2001 at 09:29:24PM +1100, Glenn McGrath wrote:
> Well leaving it the way it is doesnt make much sense either really, it
> refers to devices that dont exist.
You are mistaken. The existence of a device is unrekated to the name
someone uses to access it. You may well use /tmp/myowndisk instead
of /dev/hda. In fact some programs do precisely that and use mknod()
to temporarily create a device node with known name, since they
cannot guess what name you may be using for the device.
The kernel also uses names, for example in its boot messages,
and it will call the device hda even when you use /tmp/myowndisk.
There is no intrinsic name for a device - at most a conventional name.
next prev parent reply other threads:[~2001-02-28 15:16 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
2001-02-28 15:15 ` Guest section DW [this message]
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=20010228161540.B19929@win.tue.nl \
--to=dwguest@win.tue.nl \
--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.