public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: idalton@ferret.phonewave.net
To: List User <lists@chaven.com>
Cc: Alan Chandler <alan@chandlerfamily.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: spelling of disc (disk) in /devfs
Date: Thu, 1 Feb 2001 10:27:48 -0800	[thread overview]
Message-ID: <20010201102748.B6959@ferret.phonewave.net> (raw)
In-Reply-To: <6lah7t4f685qo3igk679ocdo2obfhd9lvg@4ax.com> <030301c08be6$e494f480$160912ac@stcostlnds2zxj>
In-Reply-To: <030301c08be6$e494f480$160912ac@stcostlnds2zxj>; from lists@chaven.com on Wed, Jan 31, 2001 at 06:35:30PM -0600

On Wed, Jan 31, 2001 at 06:35:30PM -0600, List User wrote:
> If it's any consolation from (this American) I'm glad it's 'disc' (always
> thought that 'disk' was just for those marketing dweebs who couldn't spell
> right
> in the first place).

And in terms of casual usage, I've nearly always used 'disk' in
reference to media that can be mounted read-write, and 'disc' to media
that can only be mounted read-only.

More technically, 'disc' is a single media layer (usually a CD-ROM) and
'disk' is a removable media device with a protective casing.

Non-removable storage are generally refered to as 'drives'.

Yes, it's confusing.

-- Ferret

> ----- Original Message -----
> From: "Alan Chandler" <alan@chandlerfamily.org.uk>
> To: <linux-kernel@vger.kernel.org>
> Sent: Wednesday, January 31, 2001 18:19
> Subject: spelling of disc (disk) in /devfs
> 
> 
> > I accidentally built my 2.4.1 kernel with /devfs so had a interesting
> > few minutes looking round it to see what it was doing.
> >
> > 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.
> >
> > I now find myself confused with the new approach.
-
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/

  reply	other threads:[~2001-02-01 18:28 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 [this message]
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
  -- 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=20010201102748.B6959@ferret.phonewave.net \
    --to=idalton@ferret.phonewave.net \
    --cc=alan@chandlerfamily.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@chaven.com \
    /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