From: Andreas Dilger <adilger@turbolabs.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Devlinks. Code. (Dcache abuse?)
Date: Mon, 19 Nov 2001 01:52:42 -0700 [thread overview]
Message-ID: <20011119015242.B1308@lynx.no> (raw)
In-Reply-To: <15348.58752.207182.488419@notabene.cse.unsw.edu.au> <E164gCQ-0003YZ-00@the-village.bc.nu> <15352.32969.717938.153375@notabene.cse.unsw.edu.au>
In-Reply-To: <15352.32969.717938.153375@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Mon, Nov 19, 2001 at 02:47:21PM +1100
On Nov 19, 2001 14:47 +1100, Neil Brown wrote:
> - devfs puts a lot of miscellaneous stuff in the top level.
> I would want to group them into one namespace. e.g.:
> misc/memory/mem
> misc/memory/kmem
> misc/memory/zero
> misc/memory/null
> misc/random/random
> misc/random/urandom
Erm, what about the millions+ of scripts/apps that reference /dev/zero
or /dev/null?
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-19 8:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 10:08 Devlinks. Code. (Dcache abuse?) Neil Brown
2001-11-16 10:26 ` Alan Cox
2001-11-19 3:47 ` Neil Brown
2001-11-19 8:52 ` Andreas Dilger [this message]
2001-11-19 10:30 ` Neil Brown
2001-11-19 10:17 ` Alan Cox
2001-11-19 10:40 ` Neil Brown
2001-11-19 11:14 ` Alan Cox
2001-11-19 11:21 ` Neil Brown
2001-11-19 11:27 ` Alexander Viro
2001-11-20 1:06 ` Neil Brown
2001-11-24 20:44 ` Rob Landley
2001-11-19 20:41 ` Alex Bligh - linux-kernel
2001-11-19 21:36 ` Alan Cox
2001-11-19 22:06 ` Alex Bligh - linux-kernel
2001-11-19 11:05 ` Erik Andersen
2001-11-16 10:33 ` Alexander Viro
2001-11-19 4:02 ` Neil Brown
2001-11-16 19:14 ` Andrew Pimlott
2001-11-16 20:42 ` Neil Brown
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=20011119015242.B1308@lynx.no \
--to=adilger@turbolabs.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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