From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel upgrade from 5.4 to 5.10: oldconfig "Restart config..."
Date: Mon, 5 Apr 2021 19:43:29 +0100 [thread overview]
Message-ID: <20210405194329.34c3ae00@digimed.co.uk> (raw)
In-Reply-To: <fb8ad37b-bc7a-318e-db9e-ff62c91b1a63@youngman.org.uk>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
On Mon, 5 Apr 2021 19:04:18 +0100, antlists wrote:
> > For the uninitiated, the difference here is that olddefconfig will
> > accept the default configuration value for any new/changed options,
> > whereas oldconfig will prompt the user for input.
> >
> > The former is great if you just don't care and want to accept the
> > default, but it isn't right for every user.
> >
> >
> fwiw, I think I've always just copied the old .config across, then done
> "make menuconfig". I think that also just accepts defaults for anything
> new.
It doesn't, it prompts for every change, with the default preselected.
It's more time consuming than running make olddefconfig but it does give
you the chance to see what the new options are, and read the help if you
need more.
--
Neil Bothwick
Top Oxymorons Number 19: Passive aggression
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-05 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 22:31 [gentoo-user] Kernel upgrade from 5.4 to 5.10: oldconfig "Restart config..." Alarig Le Lay
2021-04-04 22:56 ` Michael
2021-04-05 12:18 ` Alarig Le Lay
2021-04-05 11:27 ` Dr Rainer Woitok
2021-04-05 12:24 ` Alarig Le Lay
2021-04-05 14:06 ` Matt Connell (Gmail)
2021-04-05 18:04 ` antlists
2021-04-05 18:43 ` Neil Bothwick [this message]
2021-04-06 12:59 ` Peter Humphrey
2021-04-06 14:44 ` Neil Bothwick
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=20210405194329.34c3ae00@digimed.co.uk \
--to=neil@digimed.co.uk \
--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