From: Thomas Dodd <ted@cypress.com>
To: linux-kernel@vger.kernel.org
Subject: Re: spelling of disc (disk) in /devfs
Date: Thu, 08 Feb 2001 17:31:56 -0600 [thread overview]
Message-ID: <3A832C6C.F17B11B5@cypress.com> (raw)
In-Reply-To: <6lah7t4f685qo3igk679ocdo2obfhd9lvg@4ax.com> <20010201034217.A550@foozle.turbogeek.org> <20010201042813.C27725@cadcamlab.org>
Peter Samuelson wrote:
>
> [Jeremy M. Dolan]
> > Disk is spelled 'disk' except for Compact Disc and Digital Versatile
> > Disc. If it wasn't 3:30 in the morning, a patch would be attached.
>
> It wouldn't do any good. Many months ago, Ted Ts'o pleaded with
> Richard Gooch (devfs author, from Australia) to switch to the American
> spelling of the word, for consistency with the rest of the kernel, and
> nothing came of it. At this point you may as well consider
> '/dev/discs' an "interface set in stone". (Come on, do *you* want to
> explain to thousands of people why their /etc/fstab suddenly broke?)
Better still, follow the lead from other Solaris and HP-UX.
/dev/dsk/* block access for hard drives
/dev/rdsk/* char access for hard drives
/dev/diskette block access for floppy drives
/dev/rdiskette char access for floppy drives
/dev/rscsi/* char access for raw scsi (replace /dev/sg* )
Since linux currently doesn't have char access to drives,
rdsk/rdiskette would be ignored untill it is implemented
and needed.
My $0.02
-Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-08 23:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 0:19 spelling of disc (disk) in /devfs Alan Chandler
2001-02-01 0:35 ` List User
2001-02-01 18:27 ` idalton
2001-02-01 19:07 ` alex
2001-02-01 19:08 ` Richard B. Johnson
2001-02-01 23:17 ` Harald Arnesen
2001-02-01 9:42 ` Jeremy M. Dolan
2001-01-31 23:00 ` Michael B. Trausch
2001-02-01 10:28 ` Peter Samuelson
2001-02-01 10:58 ` Alan Cox
2001-02-01 17:21 ` Peter Samuelson
2001-02-08 23:31 ` Thomas Dodd [this message]
2001-02-02 3:32 ` Mike Castle
2001-02-02 9:57 ` Pekka Pietikainen
2001-02-02 14:07 ` mirabilos
2001-02-02 15:47 ` David Woodhouse
2001-02-10 0:41 ` Dr. Kelsey Hudson
2001-02-10 23:17 ` Tony Hoyle
2001-02-10 23:51 ` Albert D. Cahalan
2001-02-11 0:22 ` Rik van Riel
2001-02-11 3:56 ` John Cavan
-- strict thread matches above, loose matches on Subject: below --
2001-02-01 23:04 Wayne.Brown
2001-02-01 0:32 ` Michael B. Trausch
2001-02-01 23:12 ` Mike Harrold
[not found] <fa.gvan6kv.3664g1@ifi.uio.no>
[not found] ` <fa.i0lgugv.dhmm08@ifi.uio.no>
2001-02-02 12:49 ` Tor Arntsen
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=3A832C6C.F17B11B5@cypress.com \
--to=ted@cypress.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox