mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: "Eric S. Raymond" <esr@thyrsus.com>,
	CML2 <linux-kernel@vger.kernel.org>,
	kbuild-devel@lists.sourceforge.net, rick@linuxmafia.com
Subject: Re: Kernel configuration.  It's not just a job, it's an adventure!
Date: Sun, 17 Jun 2001 05:40:08 +0200	[thread overview]
Message-ID: <20010617054008.O754@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20010616222709.A11872@thyrsus.com>
In-Reply-To: <20010616222709.A11872@thyrsus.com>; from esr@thyrsus.com on Sat, Jun 16, 2001 at 10:27:09PM -0400

On Sat, Jun 16, 2001 at 10:27:09PM -0400, Eric S. Raymond wrote:
> > go buses
> The buses room.  A sign reads `System buses and controller types'.
> A passage leads upwards.
> 
> Specify the buses, disk controllers, and internal interconnection standards
> that you want your kernel to support.
> It is very dark.  If you continue, you are likely to be eaten by a grue.
> There is an option named EISA here.
> There is an option named PCI here.
> There is an option named PNP here.
> There is an option named PARPORT here.
> There is an option named HOTPLUG here.

> take HOTPLUG
You can now plug, if you are hot enough.

SCNR, but a nice game indeed ;-)

Regards

Ingo Oeser
-- 
Use ReiserFS to get a faster fsck and Ext2 to fsck slowly and gently.

  parent reply	other threads:[~2001-06-17  3:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9ghc7a$ogh$1@ns1.clouddancer.com>
2001-06-17  2:27 ` Eric S. Raymond
2001-06-17  2:38   ` Robert Love
2001-06-17  3:05     ` Eric S. Raymond
2001-06-17  2:57   ` Keith Owens
2001-06-17  3:40   ` Ingo Oeser [this message]
     [not found]   ` <20010617002138.A9374@whitestar.soark.net>
2001-06-17  4:41     ` Eric S. Raymond
2001-06-17 10:37       ` Colonel
2001-06-18  4:48 Wayne.Brown
2001-06-18 14:01 ` Eric S. Raymond

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=20010617054008.O754@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=esr@thyrsus.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rick@linuxmafia.com \
    /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®