From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Using Gentoo as server and desktop
Date: Thu, 5 Dec 2024 23:01:36 -0000 (UTC) [thread overview]
Message-ID: <vitbcg$ivd$1@ciao.gmane.io> (raw)
In-Reply-To: 1C58B8DA-9034-44E7-AA7F-B26AEF762221@sarenet.es
On 2024-12-05, Egoitz Aurrekoetxea <egoitz@sarenet.es> wrote:
> Does exist a way... where you could emerge world, update all the
> system, finally end up by upgrading the kernel and being sure that
> the old .config you used through menuconfig (or by any other way of
> importing) would not select erroneous parameters in newer
> kernels?
All my systems run custom-configured kernels built from on stable
gentoo-sources.
All I've ever done for a kernel upgrades is to go into the new kernel
source dir and do the following:
# zcat /proc/zconfig >.config
# make oldconfig
# make
# make install
For the past 20+ years, that has always worked fine for minor version
changes (e.g. 5.15.x ⇒ 5.15.y)
There have been a few major upgrades in the past 20 years when a large
kernel subsystem change required some sort of manual intervention with
a "make menuconfig". But, I can't actually remember the last time it
happened (it's been years).
--
Grant
next prev parent reply other threads:[~2024-12-05 23:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 21:38 [gentoo-user] Using Gentoo as server and desktop Egoitz Aurrekoetxea
2024-12-05 22:02 ` Matt Connell
2024-12-06 9:14 ` egoitz
2024-12-05 23:01 ` Grant Edwards [this message]
2024-12-05 23:20 ` [gentoo-user] " Michael
2024-12-06 9:18 ` egoitz
2024-12-06 14:50 ` Grant Edwards
2024-12-14 14:05 ` Frank Steinmetzger
2024-12-06 9:18 ` egoitz
2024-12-06 0:25 ` [gentoo-user] " syscon edm
2024-12-06 9:20 ` egoitz
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='vitbcg$ivd$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--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