public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: salvador <salvador@inti.gov.ar>
To: esr@thyrsus.com
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>, linux-kernel@vger.kernel.org
Subject: Re: Penelope builds a kernel
Date: Tue, 15 Jan 2002 12:53:18 -0300	[thread overview]
Message-ID: <3C44506E.C8F515B2@inti.gov.ar> (raw)
In-Reply-To: <20020114165909.A20808@thyrsus.com> <200201142244.g0EMimd32377@vindaloo.ras.ucalgary.ca> <20020114174523.E23081@thyrsus.com>

"Eric S. Raymond" wrote:

> Richard Gooch <rgooch@ras.ucalgary.ca>:
> > You know, I'm not really interested in whether Melvin or Penelope get
> > a root or not, and it's never occurred to me that kernel design should
> > be based on that.
>
> The phrase "get a root" is entertainingly ambiguous in this context, is it not?
>
> Storytelling is the most effective form of exposition.

Yes, if you mean "to confuse people" ;-)

> It's a way to pull
> technical issues out of the realm of abstraction,

Or get really out of topic. Be careful with your examples, sometimes they have
small errors here and there and the result, even when looks coherent, is invalid.

> and help designers
> realize that there are (at least potentially) real people involved.

Eric, if you want to create a tool that looks for the installed hardware/vendor
configuratio/etc. and from all of this information creates a configure file in the
Linux source tree go ahead. I don't think anybody will stop you if that's a
separated tool and not part of the Linux source tree.
Lets use an example, looks like you really like examples:

1) You create a project called "Linux autoconf".
2) You make it available as a tarball.
3) Some user that likes it downloads and installs the Linux kernel sources.
4) Same user downloads your "nice" tool and also installs it.
5) This user instead of using the traditional configuration methods just runs your
tool and gets all solved .... or all fkd up ;-)

I don't think anybody will stop you from doing such a tool, in fact nobody can,
but you'll need to look for help in other list ;-))

SET

--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set@computer.org set@ieee.org
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013




  parent reply	other threads:[~2002-01-15 15:52 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 [this message]
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=3C44506E.C8F515B2@inti.gov.ar \
    --to=salvador@inti.gov.ar \
    --cc=esr@thyrsus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    /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