From: folkert@vanheusden.com (Folkert van Heusden)
To: linux-kernel@vger.kernel.org
Subject: intelligent pre-configuration
Date: Wed, 9 Feb 2005 14:51:31 +0100 [thread overview]
Message-ID: <20050209135129.GM31026@vanheusden.com> (raw)
Hi,
Maybe it's nice to have a pre-kernel-configuration-auto-configurator script
in the kernel.
Like, something that detects (by parsing lspci/lsusb/lssbus's output or so)
what hardware is on-board and then creates an initial .config for your
kernel. That way the chance that you accidently forgot to include that
important ACPI-module (for your laptop) which prevents your processor from
burning gets smaller.
Folkert van Heusden
Op zoek naar een IT of Finance baan? Mail me voor de mogelijkheden!
+------------------------------------------------------------------+
|UNIX admin? Then give MultiTail (http://vanheusden.com/multitail/)|
|a try, it brings monitoring logfiles to a different level! See |
|http://vanheusden.com/multitail/features.html for a feature list. |
+------------------------------------------= www.unixsoftware.nl =-+
Phone: +31-6-41278122, PGP-key: 1F28D8AE
reply other threads:[~2005-02-09 13:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050209135129.GM31026@vanheusden.com \
--to=folkert@vanheusden.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