From: "T. A." <tkhoadfdsaf@hotmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
<esr@thyrsus.com>
Subject: Re: Aunt Tillie builds a kernel (was Re: ISA hardware discovery -- the elegant solution)
Date: Tue, 15 Jan 2002 06:53:35 -0500 [thread overview]
Message-ID: <OE553yz0UJqlG99TTOE0001578f@hotmail.com> (raw)
In-Reply-To: <20020114132618.G14747@thyrsus.com> <m16QCNJ-000OVeC@amadeus.home.nl> <20020114145035.E17522@thyrsus.com>
----- Original Message -----
From: "Eric S. Raymond" <esr@thyrsus.com>
To: <arjan@fenrus.demon.nl>
Cc: <linux-kernel@vger.kernel.org>
Sent: Monday, January 14, 2002 2:50 PM
Subject: Re: Aunt Tillie builds a kernel (was Re: ISA hardware discovery --
the elegant solution)
> arjan@fenrus.demon.nl <arjan@fenrus.demon.nl>:
> > Of course there are other settings that do have impact (CPU type mostly,
> > maybe memory layout) but other than that... distros already ship several
> > binary versions (last I counted Red Hat ships 11 or so with RHL72) to
> > account for CPU type and amount etc.
>
> OK. Scenario #2:
>
> Tillie's nephew Melvin is a junior-grade geek. He's working his way
> through college doing website administration for small businesses. He
> doesn't know C, but he can hack his way around Perl and a little PHP,
> and he can type "configure; make". He's been known to wear a penguin
> T-shirt.
>>> SNIP <<<
> Autoconfigure saves the day. Possibly it even helps Melvin get laid.
> --
> <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
>
I see!!! I see the light now!!! I see it all now!!! I have been
saved!!! If your super doper kernel autoconfigurator goes into the kernel
source tree then all of geekdom will have a possibility of getting laid.
Marvelous. Absolutely marvelous. I always knew coding would be able to
overcome any kind of obstacle for us, even this one. Horrah. 8-D
8-D Of course wantabe geek (if there is such a thing) Melvin could
always do it the hard way. The experience might come in handy for the next
"internet" bubble to arise. With the knowledge he gains he can make enough
paper money to take care of the getting laid problem once and for all (or at
least until the next crash). Besides his current target seams way too easy
if he has a chance at her just because he entered "configure". 8-D
Well anyway seams CML2 is becoming a literal everything and the kitchen
sink. Wow. 8-D So far my new kernel is going to require Python to
configure it, will include an super doper hardware detector so that it can
customize my spiffy new kernel specifically to my hardware, will include
special kernel access for regular users to be able to read my hardware
configuration because its so evil to configure my kernel as root even though
I will have to be root to install it and probably be root to untar/ungzip it
into /usr/src and not to mention removing the old /usr/src/linux, did I read
new driver model for autoconfiguring kernel somewhere too?, and the kernel
will even included a spiffy X Windows, KDE, or gnome (hey why skimp now)
program that installs itself as an icon on the user desktop (no matter what
the distribution, linux-kernel will support all) which the user can then
click on to fire up the kernel self-configuration, self-compiler,
self-installer, and auto boot loader configurator so that Aunt Tilly or the
slutty girl El Geeko has his eyes on can see a "Click here to launch new
kernel" button on their screen after their first reboot, oh and of course we
can't forget that the kernel must know that its either succeeded or failed
so that it could tell the user that and either restore the previous boot
configuration or install itself as the user's new default kernel thus
voiding the plebeian's support contract. But no problem, I'm sure the new
kernel can take care of that too. Just give it time. 8-D
Hilarities aside, I wouldn't mind having a program to automatically
configure a kernel for a system via Windows-like hardware autoconfiguration.
However do have a couple of quick points.
1. Don't see any reason for the kernel hardware autoconfigurator to be
included in the kernel.
2. Don't see any reason the kernel hardware autoconfigurator cannot be
run as root. Actually see one very good reason why it shouldn't be able to
be run as a regular user. Probing certain hardware is inherently dangerous.
Machine can hang. Hardware could be probed to death. Heck a clever coder
could even make use of the user level access required to allow user hardware
autoconfiguration. Wiping disks, destroying flash roms, finding system
backdoors, etc, etc.
3. ISA is pretty much dead outside of certain standard PC equipment.
And of the remaining ISA out there, most in any machine than can still run a
Linux kernel effectively is most likely PNP ISA. Plus there are a few
fairly common ISA cards that can also be found easily. It seams that the
vast majority of Aunt Tillies will be served with just PCI autoconfiguration
and maybe PNP ISA configuration.
next prev parent reply other threads:[~2002-01-15 11:54 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 11:17 ISA hardware discovery -- the elegant solution Michael Lazarou (ETL)
2002-01-14 16:11 ` Eric S. Raymond
2002-01-14 16:59 ` Eli Carter
2002-01-14 17:11 ` Wichert Akkerman
2002-01-14 17:52 ` Aunt Tillie builds a kernel (was Re: ISA hardware discovery -- the elegant solution) Eric S. Raymond
2002-01-14 18:34 ` Alan Cox
2002-01-14 18:26 ` Eric S. Raymond
2002-01-14 18:55 ` Charles Cazabon
2002-01-14 13:32 ` Rob Landley
2002-01-14 18:54 ` Eric S. Raymond
2002-01-14 14:28 ` Rob Landley
2002-01-14 22:34 ` Eric S. Raymond
2002-01-14 23:26 ` Alan Cox
2002-01-15 2:06 ` Eric S. Raymond
2002-01-15 21:08 ` Horst von Brand
2002-01-15 0:09 ` Mark Hahn
2002-01-15 9:14 ` Sean Hunter
2002-01-15 16:36 ` Rob Landley
2002-01-14 23:02 ` Bruce Harada
2002-01-14 15:39 ` Rob Landley
2002-01-15 0:46 ` H. Peter Anvin
2002-01-15 2:22 ` Bruce Harada
2002-01-15 13:27 ` Rob Landley
2002-01-15 12:29 ` Andrew Pimlott
2002-01-16 10:42 ` Horst von Brand
2002-01-15 13:53 ` David Woodhouse
2002-01-15 14:28 ` Bruce Harada
2002-01-15 17:04 ` Thomas Duffy
2002-01-15 18:19 ` Marco Colombo
2002-01-15 18:52 ` Richard B. Johnson
2002-01-15 19:15 ` Manuel McLure
2002-01-15 19:28 ` Marco Colombo
2002-01-15 20:13 ` Richard B. Johnson
2002-01-15 20:30 ` Manuel McLure
2002-01-15 20:41 ` arjanv
2002-01-15 20:56 ` Richard B. Johnson
2002-01-15 21:27 ` Marco Colombo
2002-01-15 21:29 ` Alan Cox
2002-01-15 19:55 ` Alan Cox
2002-01-15 20:59 ` David Woodhouse
2002-01-16 14:53 ` Horst von Brand
2002-01-16 13:57 ` Horst von Brand
2002-01-14 19:29 ` Tom Rini
2002-01-14 19:29 ` Eli Carter
2002-01-14 19:45 ` Dave Jones
2002-01-14 19:52 ` Charles Cazabon
2002-01-15 11:00 ` Horst von Brand
2002-01-14 19:00 ` Alan Cox
2002-01-14 18:44 ` Eric S. Raymond
2002-01-14 19:14 ` Alan Cox
2002-01-14 19:34 ` Tom Rini
2002-01-14 18:59 ` Larry McVoy
2002-01-14 19:02 ` arjan
2002-01-14 19:50 ` Eric S. Raymond
2002-01-14 13:01 ` gmack
2002-01-14 14:43 ` Rob Landley
2002-01-14 20:26 ` Charles Cazabon
2002-01-14 20:19 ` Eric S. Raymond
2002-01-14 20:49 ` Dave Jones
2002-01-14 20:55 ` Brian Gerst
2002-01-14 21:21 ` Alan Cox
2002-01-15 11:40 ` David Woodhouse
2002-01-14 20:37 ` Dave Jones
2002-01-14 20:38 ` Eric S. Raymond
2002-01-14 22:07 ` Jeff Garzik
2002-01-14 22:18 ` Dave Jones
2002-01-14 22:36 ` Jeff Garzik
2002-01-14 22:18 ` Reid Hekman
2002-01-14 23:30 ` Timothy Covell
2002-01-14 21:05 ` Hugh Dickins
2002-01-14 21:15 ` Alan Cox
2002-01-14 22:08 ` Eric S. Raymond
2002-01-14 23:03 ` Alan Cox
2002-01-14 22:41 ` Eric S. Raymond
2002-01-14 23:27 ` Alan Cox
2002-01-15 1:21 ` Eric S. Raymond
2002-01-15 12:31 ` Marco Colombo
2002-01-15 22:17 ` Alex Bligh - linux-kernel
2002-01-15 23:22 ` Tom Rini
2002-01-16 10:49 ` Keith Owens
2002-01-15 11:53 ` T. A. [this message]
2002-01-15 13:53 ` Horst von Brand
2002-01-14 20:30 ` Justin Carlson
2002-01-15 1:30 ` Tom Rini
2002-01-15 22:46 ` Alex Bligh - linux-kernel
2002-01-15 22:56 ` Tom Rini
2002-01-16 4:09 ` Eric S. Raymond
2002-01-14 19:28 ` Ben Collins
2002-01-14 22:41 ` Tom Gilbert
2002-01-14 18:38 ` Dave Jones
2002-01-14 18:53 ` Larry McVoy
2002-01-14 20:50 ` Henrique de Moraes Holschuh
2002-01-15 19:34 ` Horst von Brand
2002-01-15 21:38 ` Alex Bligh - linux-kernel
2002-01-15 23:44 ` Rob Landley
2002-01-16 14:33 ` Alex Bligh - linux-kernel
2002-01-16 13:05 ` Rob Landley
2002-01-16 15:27 ` Horst von Brand
2002-01-15 10:05 ` Horst von Brand
2002-01-14 18:33 ` ISA hardware discovery -- the elegant solution Oliver Xymoron
2002-01-14 23:02 ` Tom Gilbert
2002-01-14 18:58 ` Andrew Pimlott
2002-01-14 21:08 Aunt Tillie builds a kernel (was Re: ISA hardware discovery -- the elegant solution) Dave Jones
[not found] <fa.fslncfv.r6o11i@ifi.uio.no>
[not found] ` <fa.hqe5uev.c60cjs@ifi.uio.no>
2002-01-15 13:00 ` Giacomo Catenazzi
2002-01-15 13:57 ` Alan Cox
2002-01-15 14:02 ` Giacomo Catenazzi
2002-01-16 10:56 ` Horst von Brand
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=OE553yz0UJqlG99TTOE0001578f@hotmail.com \
--to=tkhoadfdsaf@hotmail.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
all inboxes | Powered by JetHome®