From: Rob Landley <rob@landley.net>
To: linux-kernel@vger.kernel.org
Cc: Roman Zippel <zippel@linux-m68k.org>, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: Quick and dirty miniconfig howto, with feature suggestions.
Date: Sat, 19 Nov 2005 21:25:37 -0600 [thread overview]
Message-ID: <200511192125.37630.rob@landley.net> (raw)
In-Reply-To: <200511170629.42389.rob@landley.net>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
On Thursday 17 November 2005 06:29, Rob Landley wrote:
> --- What is a miniconfig?
>
> A new feature of 2.6.15 lets you use miniature configuration files, listing
> just the symbols you want to enable and letting the configurator enable any
> dependencies to give you a valid configuration.
>
> To make it work, create a mini.config file and run allnoconfig (to create
> a .config file with all unspecified symbols switched off) with the extra
> argument "KCONFIG_ALLCONFIG=mini.config".
And here's a shell script that will automatically create a mini.conf from a
standard .config file.
It does this via the simple expedient of trying to remove each line and seeing
which ones make any difference to the generated .config. (This means it runs
make allnoconfig about 1300 times. This is very very slow, so it displays a
progress indicator.)
To use the script, go into the kernel source directory, create your .config
file (via menuconfig or however), rename that .config file to something else
(like "myconfig"), then run the script like so:
./miniconfig.sh myconfig
(Note you still have to be in the directory where the script can run "make
allnoconfig".) When it finishes, you should have a mini.conf containing the
minimal set of lines necessary to specify that configuration via
"make KCONFIG_ALLCONFIG=mini.config allnoconfig".
I'm sure there's a better way to do this, but this works now.
Rob
[-- Attachment #2: miniconf.sh --]
[-- Type: application/x-shellscript, Size: 906 bytes --]
prev parent reply other threads:[~2005-11-20 3:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 12:29 Quick and dirty miniconfig howto, with feature suggestions Rob Landley
2005-11-20 3:08 ` Roman Zippel
2005-11-20 5:54 ` Rob Landley
2005-11-21 6:15 ` [PATCH] make miniconfig Rob Landley
2005-11-21 16:06 ` [PATCH] make miniconfig (take 2) Rob Landley
2005-11-21 17:26 ` Pavel Machek
2005-11-21 17:46 ` Rob Landley
2005-11-21 17:36 ` Pavel Machek
2005-11-21 17:50 ` Rob Landley
2005-11-21 18:28 ` Pavel Machek
2005-11-21 18:53 ` Rob Landley
2005-11-21 19:24 ` Pavel Machek
2005-11-22 5:14 ` Rob Landley
2005-11-22 22:54 ` Pavel Machek
2005-11-23 8:58 ` Rob Landley
2005-11-23 13:21 ` Pavel Machek
2005-11-24 3:19 ` Rob Landley
2005-11-25 19:45 ` Pavel Machek
2005-11-25 21:45 ` Rob Landley
2005-11-25 22:09 ` Pavel Machek
2005-11-25 22:20 ` Rob Landley
2005-11-26 2:34 ` Kyle Moffett
2005-11-26 12:25 ` Rob Landley
2005-11-26 14:19 ` Pavel Machek
2005-11-26 15:51 ` Rob Landley
2005-11-24 4:02 ` Rob Landley
2005-11-25 19:46 ` Pavel Machek
2005-11-26 1:53 ` Andre Noll
2005-11-22 5:17 ` Rob Landley
2005-11-24 13:56 ` Roman Zippel
2005-11-24 17:45 ` Rob Landley
2005-11-25 1:48 ` Roman Zippel
2005-11-25 8:18 ` Rob Landley
2005-11-25 15:02 ` Roman Zippel
2005-11-25 16:47 ` Rob Landley
2005-11-25 21:12 ` Rob Landley
2005-11-27 23:20 ` Roman Zippel
2005-11-28 0:59 ` Rob Landley
2005-11-29 1:00 ` Roman Zippel
2005-11-29 2:26 ` Rob Landley
2005-11-30 2:29 ` Roman Zippel
2005-11-20 3:25 ` Rob Landley [this message]
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=200511192125.37630.rob@landley.net \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.