public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Zaitsev <pavel@md5.ca>
To: Bruce Harada <bruce@ask.ne.jp>
Cc: esr@thyrsus.com, linux-kernel@vger.kernel.org
Subject: Re: Penelope builds a kernel
Date: Fri, 1 Feb 2002 12:46:58 -0800	[thread overview]
Message-ID: <20020201124658.A602@md5.ca> (raw)
In-Reply-To: <20020114165909.A20808@thyrsus.com> <20020115073749.26b8f7a1.bruce@ask.ne.jp>
In-Reply-To: <20020115073749.26b8f7a1.bruce@ask.ne.jp>; from bruce@ask.ne.jp on Tue, Jan 15, 2002 at 07:37:49AM +0900

Agreed. ESR is reading too much of "Unix haters handbook" and should
take a pinch of reality.
p.

Bruce Harada(bruce@ask.ne.jp)@Tue, Jan 15, 2002 at 07:37:49AM +0900:
> On Mon, 14 Jan 2002 16:59:09 -0500
> "Eric S. Raymond" <esr@thyrsus.com> wrote:
> 
> > Scenario #3: Penelope goes where the geeks are surfing.
> > 
> [SNIP]
> >
> > 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.
> > 
> [SNIP]
> 
> So, she calls up one of the innumerable independent Linux support companies in
> her area (hey, this is a fantasy scenario, right?) and tells them what she
> needs, pays them $30, and guess what? she never needed to run anything
> herself.
> 
> I think some people are getting too involved with the issue to see that SOME
> people probably don't care what kernel they're running, or even what a kernel
> is, they just want to give someone money to fix their problem. It's like your
> local auto-repair shop - someone who knows about car engines wouldn't take
> their car there except for major repairs, because they know what to do in most
> situations, but most people just want to drive. If they ever get sick of
> paying to put the mechanic's kids through college, they will learn how to
> change the oil themselves, but honestly, most people simply can't be bothered.
> 
> And before you say that Linux is supposed to empower the people of the world,
> not limit them, I wouldn't say that learning how to change my oil "empowers"
> me all that much.

-- 
Create like God. Command like a King. Work like a Slave.
110461387
http://gpg.md5.ca
http://perlpimp.com

  parent reply	other threads:[~2002-02-01 20:47 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 [this message]
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
     [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=20020201124658.A602@md5.ca \
    --to=pavel@md5.ca \
    --cc=bruce@ask.ne.jp \
    --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