public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux needs new leadership.
Date: 2 Apr 2002 22:41:28 -0800	[thread overview]
Message-ID: <a8e86o$kpv$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.OSF.4.10.10204010933530.312508-100000@ouray.cudenver.edu> <20020402222639.C2777@alcove.wittsend.com> <3CAA7BB8.69E82CDA@maine.rr.com> <20020402230203.B2722@alcove.wittsend.com>

Followup to:  <20020402230203.B2722@alcove.wittsend.com>
By author:    "Michael H. Warfield" <mhw@wittsend.com>
In newsgroup: linux.dev.kernel
> 
> > "Electricity over IP" is right up there with the Google(tm) Pigeon
> > Clusters a fine addition to the tradition IMHO.
> 
> 	Agreed, but one of my favorites was RFC 1097, "TELNET
> SUBLIMINAL-MESSAGE Option".  That one had people FURIOUS and SCREAMING
> when it came out.  It was declared unethical and illegal.  Then someone
> pointed out that the option code BYTE value was 257.  :->  That and
> the date of April 1, 1989 (Ok, I'm an old fart) delivered a rather
> major clue by four to the side of some stiff necks.  :-)
> 
> 	But, yes...  Electricity over IP joins the hallowed halls of
> honored April 1 RFCs...
> 

Nothing beats RFC 1437, though...

	-hpa
-- 
<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	<amsp@zytor.com>

  reply	other threads:[~2002-04-03  6:42 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-01 16:37 Linux needs new leadership Enkh Tumenbayar
2002-04-02  9:04 ` John P. Looney
2002-04-03  3:26 ` Michael H. Warfield
2002-04-03  3:49   ` David B. Stevens
2002-04-03  4:02     ` Michael H. Warfield
2002-04-03  6:41       ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-02 18:58 Wayne.Brown
     [not found] <20020401201710.GA2619@lpt.ens.fr>
2002-04-01 22:21 ` Cyril Chevrot
2002-04-01 19:59 Linux Needs New Leadership James Fowler
2002-04-01 12:41 Linux needs new leadership Blue R
2002-04-01  7:00 Linus Torvalds
2002-04-01  8:19 ` William Lee Irwin III
2002-04-01 10:58   ` Steve Kump
2002-04-01 14:24   ` Steven Cole
2002-04-01 16:01     ` Tom Rini
2002-04-01  8:45 ` Rob Turk
2002-04-01  8:55 ` Alex Belits
2002-04-01  9:32 ` Hristo Doichev
2002-04-01 13:14   ` Kevin Krieser
2002-04-01 13:30     ` Richard B. Johnson
2002-04-01 17:51       ` Hristo Doichev
2002-04-03  0:59     ` Håvard Lygre
2002-04-03 11:49       ` john slee
2002-04-01  9:57 ` Frank Fiene
2002-03-31 22:56   ` J.A. Magallon
2002-04-01 23:09     ` M. Edward (Ed) Borasky
2002-04-02  9:03       ` Hans-Christian Armingeon
2002-04-03  3:22       ` Michael H. Warfield
2002-04-03 14:00         ` Luigi Genoni
2002-04-03 14:41           ` Alan Cox
2002-04-03 22:34             ` Luigi Genoni
2002-04-02  5:00     ` H. Peter Anvin
2002-04-02 20:16       ` Paul P Komkoff Jr
2002-04-03  3:18       ` Michael H. Warfield
2002-04-02 16:56     ` Diego Calleja
2002-04-02 19:17       ` Erik Ljungström
2002-04-02 18:49         ` Jens Schmidt
2002-04-02 20:23           ` Erik Ljungström
2002-04-02 19:48             ` J.A. Magallon
2002-04-03  0:03           ` Pablo Alcaraz
2002-04-03 19:10             ` Canek Peláez Valdés
2002-04-01 10:14 ` Dale Amon
2002-04-01 14:03   ` Geert Uytterhoeven
2002-04-01 16:26 ` Cyril Chevrot
2002-04-01 17:58 ` Thomas Molina
2002-04-01 18:09 ` Diego Calleja
2002-04-02  0:56   ` Stephen Samuel
2002-04-02 16:42     ` Diego Calleja
2002-04-01 19:03 ` Jeff V. Merkey
2002-04-01 19:12   ` Tim Hockin
2002-04-01 20:44   ` Jeff V. Merkey
2002-04-01 20:34     ` Cort Dougan
2002-04-01 19:56 ` Sandy Harris
2002-04-01 20:11   ` Tux T. Penguin
2002-04-01 20:43 ` Jirat for Linux Kernel ML
2002-04-01 22:48 ` Benny Sjostrand
2002-04-01 23:18   ` Simon Richter

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='a8e86o$kpv$1@cesium.transmeta.com' \
    --to=hpa@zytor.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