public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: faceprint@faceprint.com (Nathan Walp)
To: "Eric S. Raymond" <esr@thyrsus.com>, linux-kernel@vger.kernel.org
Subject: Re: Penelope builds a kernel
Date: Mon, 14 Jan 2002 19:50:53 -0500	[thread overview]
Message-ID: <20020115005053.GA16892@faceprint.com> (raw)
In-Reply-To: <20020114165909.A20808@thyrsus.com>
In-Reply-To: <20020114165909.A20808@thyrsus.com>

[-- Attachment #1: Type: text/plain, Size: 3076 bytes --]

On Mon, Jan 14, 2002 at 04:59:09PM -0500, Eric S. Raymond wrote:
<snip of over-many-people's-heads description of advanced biology stuff>
> Penelope needs to build a kernel to support her exotic driver, but she
> hasn't got more than the vaguest idea how to go about it.  The
> instructions with the driver source patch tell her to apply it at the
> top level of a current Linux source tree and then just say "build the
> kernel" before getting off into technicalia about the user-space
> tools.
> 
> She could ask that guy who's been eyeing her over at the computer lab
> for help; Penelope knows what a penguin T-shirt means, and he's not
> too bad-looking, if a bit on the skinny side.  On the other hand, she
> knows that guys like that tend to take over the whole process when
> they're trying to be helpful; they can't help displaying their prowess
> and doing more than you asked for, it's biologically wired in.  And
> she's learned that letting someone else take over maintaining your
> equipment properly in a way you don't understand is a good way to have
> it flake out on you just short of a deadline.
> 
> On the third hand, she really *doesn't* want to spend her think time
> absorbing a bunch of irrelevant hardware details just to get the one
> driver she needs up and running.  What she needs is some fast,
> hassle-free technological empowerment, not Yet Another Learning
> Experience. (And a boyfriend would be nice too, while she's wishing.)

So can we assume that our dear sweet Penelope has spent a bit of time
reading l-k and finding out about <insert your favorite brown-paper-bag
release here>?  We wouldn't want her to destroy her newly-created data.
Also, since she has a laptop (which comes with all that finicky laptop
hardware), does the release of the kernel she grabbed have that nasty
tweak that fries the board in her laptop?  (I've heard some rather nasty
horror stories, that's why I ask)

She can't very well patch her vendor kernel, because I sincerely doubt
the patch will apply cleanly, if this driver is such that it needs a
patch as opposed to just a module.

Also, what do we tell Penelope when her other piece of exotic hardware
that *was* supported in the vendor kernel, but isn't supported in the
vanilla kernel, stops working.  Suddenly she can do her advanced biology
stuff, but can't print, or dial up w/ her winmodem, or whatever.

> If Penelope learns from the README file that all *she* has to do is
> type "configure; make" to build a kernel that supports her hardware,
> she can apply that MEMS card patch and build with confidence that the
> effort is unlikely to turn into an infinite time sink.
> 
> Autoconfigure saves the day again.  That guy in the penguin T-shirt
> might even be impressed...

If Penelope is even a remote candidate for this scenario, I think
penguin-boy is already impressed ;-)

-- 
Nathan Walp             || faceprint@faceprint.com
GPG Fingerprint:        ||   http://faceprint.com/
5509 6EF3 928B 2363 9B2B  DA17 3E46 2CDC 492D DB7E


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2002-01-15  0:51 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 [this message]
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
     [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=20020115005053.GA16892@faceprint.com \
    --to=faceprint@faceprint.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