From: Wayne.Brown@altec.com
To: "Michael B. Trausch" <fd0man@crosswinds.net>
Cc: "Jeremy M. Dolan" <jmd@foozle.turbogeek.org>,
Alan Chandler <alan@chandlerfamily.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: spelling of disc (disk) in /devfs
Date: Thu, 1 Feb 2001 17:04:56 -0600 [thread overview]
Message-ID: <862569E6.007EDB83.00@smtpnotes.altec.com> (raw)
To confuse things even more, I have a "Hewlett-Packard 9114 Disc Drive," which
is really a 720K 3.5-inch diskette drive.
Wayne
"Michael B. Trausch" <fd0man@crosswinds.net> on 01/31/2001 05:00:34 PM
To: "Jeremy M. Dolan" <jmd@foozle.turbogeek.org>
cc: Alan Chandler <alan@chandlerfamily.org.uk>, linux-kernel@vger.kernel.org
(bcc: Wayne Brown/Corporate/Altec)
Subject: Re: spelling of disc (disk) in /devfs
On Thu, 1 Feb 2001, Jeremy M. Dolan wrote:
>
> On Thu, 01 Feb 2001 00:19:56 +0000, Alan Chandler wrote:
> > The thing that struck me most was the spelling of disc with a 'c'. As
> > an Englishman this is the correct spelling for me most of the time,
> > but I have come to accept "as a technical term" disk (as in American)
> > is the right name for these devices.
>
> 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.
>
Anymore, even I refer to everything as discs, I used to be hardcore in
establishing the difference between disks, discs, and diskettes. However,
it's really useless, given that nobody even understands "diskette" in the
general public when I say it, I wind up explaining it.
- Mike
===========================================================================
Michael B. Trausch fd0man@crosswinds.net
Avid Linux User since April, '96! AIM: ML100Smkr
Contactable via IRC (DALNet) or AIM as ML100Smkr
===========================================================================
-
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/
-
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 reply other threads:[~2001-02-01 23:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 23:04 Wayne.Brown [this message]
2001-02-01 0:32 ` spelling of disc (disk) in /devfs 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
-- strict thread matches above, loose matches on Subject: below --
2001-02-01 0:19 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
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
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=862569E6.007EDB83.00@smtpnotes.altec.com \
--to=wayne.brown@altec.com \
--cc=alan@chandlerfamily.org.uk \
--cc=fd0man@crosswinds.net \
--cc=jmd@foozle.turbogeek.org \
--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