From: Jack <ostroffjh@users.sourceforge.net>
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:05:04 -0500 [thread overview]
Message-ID: <BKEC3ORL.52LIN4SG.VYEGKB4Q@BDD2QSTW.OPZSXBIW.3CGMJLJG> (raw)
In-Reply-To: <20171228195236.GA17094@ACM> (from acm@muc.de on Thu Dec 28 14:52:36 2017)
On 2017.12.28 14:52, Alan Mackenzie wrote:
> Hello, Gentoo.
>
> Having just built linux-4.14.7-gentoo, suddenly a new version of the
> kernel, linux-4.14.8-gentoo-r1 has become stable. Configuring a
> kernel from scratch is a repetitive drudge.
>
> There is some way of initialising a new kernel .config from an
> existing one, I am sure, but I can't find it. I've looked at the
> Gentoo wiki, I've looked at (some of) the kernel's own
> documentation. The nearest I can find is make oldconfig, which
> supposedly does what I want, but it just seems to start off with a
> default .config and go through the hundreds of questions one at a
> time.
>
> So, would some kind soul please tell me how to get my old .config
> into a new one properly. Thanks!
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 sounds like it was asking about everything because
it didn't have the old file as a starting point - so was starting from
scratch.
Jack
next prev parent reply other threads:[~2017-12-28 20:05 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 [this message]
2017-12-28 20:13 ` Alan Mackenzie
2017-12-28 20:16 ` Rich Freeman
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=BKEC3ORL.52LIN4SG.VYEGKB4Q@BDD2QSTW.OPZSXBIW.3CGMJLJG \
--to=ostroffjh@users.sourceforge.net \
--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