From: Reid Hekman <reid.hekman@ndsu.nodak.edu>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Aunt Tillie builds a kernel (was Re: ISA hardware discovery --the elegant solution)
Date: 15 Jan 2002 05:35:05 -0600 [thread overview]
Message-ID: <1011094507.19657.15.camel@zeus> (raw)
In-Reply-To: <Pine.LNX.4.33.0201151235110.28503-100000@netfinity.realnet.co.sz>
In-Reply-To: <Pine.LNX.4.33.0201151235110.28503-100000@netfinity.realnet.co.sz>
On Tue, 2002-01-15 at 04:40, Zwane Mwaikambo wrote:
> Normal users should _never_ have to use
> kernel.org trees.
Yikes! Sayings about never saying "never" aside... I should think the
goal is for everyone to be able to use kernel.org trees with reasonable
expectations. I'd like to see the day when distros can include a
pristine tree. I don't expect it, and the need for outside trees isn't
going away, but I'd like to see kernel.org be the canonical Linux for
more production systems, development starts, and non-i386 arch's.
With respect to Aunt Tillie, hardware discovery and kernel configuration
are separate issues. Can't the hardware probes be a separate package?
The autoconfigurator I think will be useful, but can't the configurator
just be dependent on outside packages like other functionality is
dependent on isdn4k-utils or iptables?
Regards,
Reid "thinking this is getting offtopic" Hekman
--
Current: reid.hekman@ndsu.nodak.edu
Permanent: hekman@acm.org
next prev parent reply other threads:[~2002-01-15 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 10:40 Aunt Tillie builds a kernel (was Re: ISA hardware discovery --the elegant solution) Zwane Mwaikambo
2002-01-15 11:35 ` Reid Hekman [this message]
2002-01-16 15:32 ` Bill Davidsen
2002-01-21 14:55 ` Mark H. Wood
[not found] <fa.g54h1nv.126slpt@ifi.uio.no>
[not found] ` <fa.k72pe6v.1tmgn1a@ifi.uio.no>
2002-01-15 13:17 ` Giacomo Catenazzi
2002-01-15 14:50 ` Marco Colombo
2002-01-15 15:01 ` Giacomo Catenazzi
2002-01-15 15:47 ` Marco Colombo
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=1011094507.19657.15.camel@zeus \
--to=reid.hekman@ndsu.nodak.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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