public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Stephen Clark <sclark46@earthlink.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Automatic config file generator
Date: Thu, 2 Oct 2008 21:35:23 +0400	[thread overview]
Message-ID: <20081002173523.GA2675@x200.localdomain> (raw)
In-Reply-To: <48E4FC91.5010300@earthlink.net>

On Thu, Oct 02, 2008 at 12:53:37PM -0400, Stephen Clark wrote:
> Is there a utility that will examine your system and generate a tailored 
> config file so I don't have to compile a zillion modules.
>
> Currently when I want to build the latest kernel I take the config file from
> my distro, (fedora), but it has every module in the world. So on my
> 1.8ghz core 2 duo laptop it takes about 30 min to build a new kernel.

Switch CONFIG_DEBUG_INFO off.

Anyway, trim your config once with big switch-offs like
CONFIG_INFINIBAND=n or CONFIG_ISDN=n (or something like that) then use
old mainline config when upgrading to new mainline kernel with
"make oldconfig". You'll answer small amount of questions every time because of
new options and developers try very hard to ensure oldconfig always
leaves valid working configuration.

Even more, turn on /proc/config.gz feature to never lose your config.

      parent reply	other threads:[~2008-10-02 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 16:53 Automatic config file generator Stephen Clark
2008-10-02 17:02 ` Cyrill Gorcunov
2008-10-02 17:40   ` Stephen Clark
2008-10-02 17:35 ` Alexey Dobriyan [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=20081002173523.GA2675@x200.localdomain \
    --to=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sclark46@earthlink.net \
    /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