From: "Adam J. Richter" <adam@yggdrasil.com>
To: miquels@cistron-office.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: Patch: 2.5.62 devfs shrink
Date: Thu, 27 Feb 2003 19:14:48 -0800 [thread overview]
Message-ID: <200302280314.TAA11682@baldur.yggdrasil.com> (raw)
miquels@cistron-office.nl wrote:
>If you're making it not 100% compatible anyway, now is the time
>to do away with that horrible 'disc' spelling ;). 'disk' is a
>harddisk or floppy disk, 'disc' is for compact disc (try Google
>on both spellings and you'll see that the world agrees ..).
>Just do s/disc/disk/g in devfs_register().
The names of devices are not chosen by fs/devfs/*.[ch]. They
are chosen by the client code in device drivers and elsewhere that
call call devfs. In the case of the /dev/discs/ names, they are
chose by devfs_{create,remove}_partitions in fs/partitions/check.c,
which, from the comments, was apparently written by Linus Torvalds
and Russell King.
Tangential note:
For what it's worth, my preference would be to change from
/dev/discs/disc0/part1 to /dev/disk/0/part1, but I think it would
probably do more harm than good to try to coordinate such a change
with switching devfs. If you want to try to make a change where
people will eventually have to update their systems, I think it would
probably make more sense to survey existing devfs naming practices and
try to come up with some recommendations harmonize them a bit. For
example, should the directory names be singular or plural (/dev/loop
or /dev/loops, /dev/disk or /dev/disks)? I would recommend signular
because it is less English-centric. There are probably four or five
recommendations like these that could be put into a Documentation
file. More consistent naming schemes in anything tend to make
a system more readily usable.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
next reply other threads:[~2003-02-28 3:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 3:14 Adam J. Richter [this message]
2003-02-28 4:03 ` Miles Bader
2003-02-28 8:08 ` Andreas Jellinghaus
2003-02-28 12:50 ` Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2003-02-28 2:49 Adam J. Richter
2003-02-27 23:13 Adam J. Richter
2003-02-28 0:00 ` Miquel van Smoorenburg
2003-02-28 1:37 ` Andrew Walrond
2003-02-26 2:47 miltonm
2003-02-25 10:23 Adam J. Richter
2003-02-25 21:50 ` Andrew Morton
2003-02-26 0:51 ` Dave Jones
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=200302280314.TAA11682@baldur.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron-office.nl \
/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®