All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Wayne.Brown@altec.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Not a typewriter
Date: Thu, 10 May 2001 17:10:26 -0700	[thread overview]
Message-ID: <3AFB2DF2.C527048F@transmeta.com> (raw)
In-Reply-To: <86256A48.007EF161.00@smtpnotes.altec.com>

Wayne.Brown@altec.com wrote:
> 
> On 05/10/2001 at 05:38:32 PM hpa@transmeta.com (H. Peter Anvin) wrote:
> 
> >Sounds like someone has just clarified what the heck it means.  "tty"
> >and "typewriter" aren't exactly the same thing (even though "tty"
> >stands for "teletypewriter" it has come to mean something completely
> >different in a Unix context)... "not a typewriter" is just a
> >completely confusing error message for the uninitiated.
> 
> I disagree.  "Not a typewriter" is part of Unix tradition, and ought to be
> retained as a historical reference.  It's also an opportunity for "the
> uninitiated" to learn a little more and move a little closer to becoming "the
> initiated."
> 

Nowhere else in Unix is a "tty" referred to as a "typewriter".  "Not a
tty" is one thing; "Not a typewriter" is just plain misleading.

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

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

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-10 23:06 Not a typewriter 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2001-05-14  2:59 Wayne.Brown
2001-05-11 23:57 Bingner Sam J. Contractor RSIS
2001-05-11 23:18 Wayne.Brown
2001-05-14 22:22 ` Kai Henningsen
2001-05-11 18:37 Wayne.Brown
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-10 21:42 Richard B. Johnson
2001-05-10 22:38 ` H. Peter Anvin
2001-05-11  7:22 ` Tom Leete

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=3AFB2DF2.C527048F@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=Wayne.Brown@altec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.