From: Felix von Leitner <usenet-20020116@fefe.de>
To: "Eric S. Raymond" <esr@thyrsus.com>, linux-kernel@vger.kernel.org
Subject: Re: Penelope builds a kernel
Date: Wed, 16 Jan 2002 22:31:59 +0100 [thread overview]
Message-ID: <20020116213159.GC950@fefe.de> (raw)
In-Reply-To: <20020114165909.A20808@thyrsus.com>
In-Reply-To: <20020114165909.A20808@thyrsus.com>
Thus spake Eric S. Raymond (esr@thyrsus.com):
> Scenario #3: Penelope goes where the geeks are surfing.
Why are you posting all this crap to linux-kernel?
[58 lines that say "I want ./configure for the kernel" deleted]
Ever put a recent SuSE or RedHat CD in your computer?
Eric, there are hundreds of perfectly fine Linux problems you could
solve. Distributions will ship with generic kernels and lots of
modules. You are not supposed to patch the kernel unless you have some
minimal expertise. Requiring users to use Python will not help the
situation at all. Pardon the French, but don't you have any real
problems to solve?
You know, the kind of problem where solving it would actually help a few
people? Almost no standard user like Aunt Tilly or Penelope has a
reason to compile a kernel, ever. Rule 1 of computing: optimize the
_common_ case. This case is not common.
Felix
next prev parent reply other threads:[~2002-01-16 21:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 21:59 Penelope builds a kernel Eric S. Raymond
2002-01-14 22:24 ` Jeff Garzik
2002-01-14 22:28 ` Lars Marowsky-Bree
2002-01-14 22:32 ` Davide Libenzi
2002-01-14 22:32 ` Chris Friesen
2002-01-14 22:35 ` Benjamin LaHaise
2002-01-14 22:38 ` Eric S. Raymond
2002-01-14 23:00 ` Benjamin LaHaise
2002-01-14 23:05 ` Eric S. Raymond
2002-01-14 23:38 ` Benjamin LaHaise
2002-01-15 1:53 ` Eric S. Raymond
2002-01-15 2:36 ` Benjamin LaHaise
2002-01-15 11:53 ` Matthias Andree
2002-01-15 22:32 ` James Antill
2002-01-15 22:28 ` Eric S. Raymond
2002-01-16 1:29 ` Alan Cox
2002-01-15 23:00 ` Diego Calleja
2002-01-14 22:37 ` Bruce Harada
2002-01-15 0:56 ` Thomas Duffy
2002-02-01 20:46 ` Pavel Zaitsev
2002-01-14 22:44 ` Richard Gooch
2002-01-14 22:45 ` Eric S. Raymond
2002-01-14 23:15 ` Richard Gooch
2002-01-15 15:53 ` salvador
2002-01-14 23:08 ` Chris Ricker
2002-01-14 23:14 ` Tom Gilbert
2002-01-15 0:50 ` Nathan Walp
2002-01-15 1:24 ` John Levon
2002-01-15 1:39 ` Tom Rini
2002-01-15 2:07 ` John Levon
2002-01-15 3:59 ` Tom Rini
2002-01-15 13:28 ` David Woodhouse
2002-01-15 19:53 ` Ingo Oeser
2002-01-15 20:37 ` David Woodhouse
2002-01-15 21:00 ` Matthew M
2002-01-16 21:31 ` Felix von Leitner [this message]
[not found] <d7.11a4a260.2974c807@aol.com>
2002-01-14 23:51 ` Jeff Garzik
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=20020116213159.GC950@fefe.de \
--to=usenet-20020116@fefe.de \
--cc=esr@thyrsus.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