public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Leete <tleete@mountain.net>
To: root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Not a typewriter
Date: Fri, 11 May 2001 03:22:12 -0400	[thread overview]
Message-ID: <3AFB9324.4BD63B62@mountain.net> (raw)
In-Reply-To: <Pine.LNX.3.95.1010510173138.29690A-100000@chaos.analogic.com>

"Richard B. Johnson" wrote:
> 
> I noticed that my favorite "errno" has now gotten trashed by
> the newer 'C' runtime libraries.
> 
> ENOTTY has been for ages, "Not a typewriter".
> It's now been changed to "Inappropriate ioctl for device".
> 
> Methinks that this means that ../linux/include/asm/errno.h now needs
> to be updated:
> 
> -#define        ENOTTY          25      /* Not a typewriter */
> +#define        ENOTTY          25      /* Inappropriate ioctl for device
> */
> 
> None of these strings are in the kernel, but the headers probably should
> show the "latest standard".
> 
> Cheers,
> Dick Johnson

Probably so, but I think:

character device => typewriter
block => sheet of paper
block device => stack of paper

is not a bad analogy.

Cheers
Tom

PS. I didn't dare call it a ream of paper ;-)

-- 
The Daemons lurk and are dumb. -- Emerson

  parent reply	other threads:[~2001-05-11  7:23 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-10 21:42 Not a typewriter Richard B. Johnson
2001-05-10 22:38 ` H. Peter Anvin
2001-05-11  7:22 ` Tom Leete [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-10 23:06 Wayne.Brown
2001-05-10 23:20 ` Hacksaw
2001-05-10 23:52   ` Jonathan Lundell
2001-05-11  0:07     ` Alexander Viro
2001-05-11  2:01       ` Jonathan Lundell
2001-05-11  9:21         ` Malcolm Beattie
2001-05-11  0:10 ` H. Peter Anvin
2001-05-11  1:31   ` David S. Miller
2001-05-11  1:32     ` Blue Lang
2001-05-11  9:31       ` Alan Cox
2001-05-11 12:25   ` Richard B. Johnson
2001-05-11  9:37 ` Alan Cox
2001-05-15 14:01 ` Anuradha Ratnaweera
2001-05-11 16:07 Wayne.Brown
2001-05-11 17:03 ` Joel Jaeggli
2001-05-11 21:43 ` Hacksaw
2001-05-13 23:39   ` Mike A. Harris
2001-05-12  4:18 ` John Alvord
2001-05-13 23:35 ` Mike A. Harris
2001-05-14  1:03   ` Horst von Brand
2001-05-14 14:31     ` John Kodis
2001-05-14 15:25     ` Michael Meissner
2001-05-14 17:01       ` Alan Cox
2001-05-14 17:16         ` Michael Meissner
2001-05-14 17:29         ` Jesse Pollard
2001-05-14 18:04           ` H. Peter Anvin
2001-05-14  1:31   ` Jonathan Lundell
2001-05-11 18:37 Wayne.Brown
2001-05-11 23:18 Wayne.Brown
2001-05-14 22:22 ` Kai Henningsen
2001-05-11 23:57 Bingner Sam J. Contractor RSIS
2001-05-14  2:59 Wayne.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=3AFB9324.4BD63B62@mountain.net \
    --to=tleete@mountain.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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