public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Using an old kernel .config as the basis for a new .config
Date: Thu, 28 Dec 2017 15:16:17 -0500	[thread overview]
Message-ID: <CAGfcS_mqYvJvOwH29x26qrv6vc3fnVsVEP1wbetMZFpHPMA9Fg@mail.gmail.com> (raw)
In-Reply-To: <BKEC3ORL.52LIN4SG.VYEGKB4Q@BDD2QSTW.OPZSXBIW.3CGMJLJG>

On Thu, Dec 28, 2017 at 3:05 PM, Jack <ostroffjh@users.sourceforge.net> wrote:
>
> You need to copy your old .config into the new kernel source directory.
> "make oldconfig" then uses those values, and only asks you about new items.

It will find an existing config in /boot if you have one named using
the upstream naming convention (which happens if you install the
kernel using make install on a vanilla kernel - I'm not sure about
genkernel or gentoo-sources offhand).

If you have /proc/config.gz enabled then you can also do a zcat
/proc/config.gz > .config to extract your current config.  I always
enable /proc/config.gz since it costs a few kb tops and comes in handy
anytime you're not sure what config you're running (though if you
built some modules after the fact it might not be entirely current).

-- 
Rich


  parent reply	other threads:[~2017-12-28 20:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28 19:52 [gentoo-user] Using an old kernel .config as the basis for a new .config Alan Mackenzie
2017-12-28 20:05 ` Jack
2017-12-28 20:13   ` Alan Mackenzie
2017-12-28 20:16   ` Rich Freeman [this message]
2017-12-28 20:31     ` Neil Bothwick
2017-12-29  0:58   ` [gentoo-user] " Kai Krakow
2017-12-29  1:24     ` Paige Thompson
2017-12-28 20:24 ` [gentoo-user] " Francesco Turco
2017-12-28 20:35 ` Ralph Seichter

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=CAGfcS_mqYvJvOwH29x26qrv6vc3fnVsVEP1wbetMZFpHPMA9Fg@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-user@lists.gentoo.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