From: Matthew M <matthew.macleod@btinternet.com>
To: esr@thyrsus.com, linux-kernel@vger.kernel.org
Subject: Re: Penelope builds a kernel
Date: Tue, 15 Jan 2002 21:00:10 +0000 [thread overview]
Message-ID: <m16Qagq-000CyBC@Wasteland> (raw)
In-Reply-To: <20020114165909.A20808@thyrsus.com>
In-Reply-To: <20020114165909.A20808@thyrsus.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I have watched this thread, and I am unable to understand what problems
people have with a autoconfigurator!
Eric, go ahead and produce an autoconfigurator. If it works, it will become a
useful tool for those who need it. It will not interfere with the current
practice of manual kernel configuration and will not cause any inconvenience
to developers. And it will be useful!
Think of it in the context of a magic "Build-me-an-optimised-kernel" button
which would appear on the desktop of distro X. Which could be useful.
The point is, people who have no need for an autoconfig tool need not use it.
Melvin configures manually.
Aunt Tillie uses her distro kernels.
The small group of people who have the knowledge/requirement to build their
own kernels, but without sufficent technical knowhow to configure it, and
understand some myriad options, will find the autoconfig tool useful. And
Linux is about covering all the groups, is it not?
Just my 0.02 euro.
*MatthewM*
- --
Paranoia is heightened awareness.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8RJhcoVQMDIAmueURAiMEAKCOP6jgj9/6LEhdXY9X2hnpNAslWQCeIwV6
K86eai2Nl5xtmuu92NbRbZA=
=JV5M
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-01-15 21:02 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 [this message]
2002-01-16 21:31 ` Felix von Leitner
[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=m16Qagq-000CyBC@Wasteland \
--to=matthew.macleod@btinternet.com \
--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