From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrading from 5.14 to 6.0 version
Date: Fri, 11 Nov 2022 13:42:10 -0600 [thread overview]
Message-ID: <bf646cd4-aa38-1d7c-5c44-1654c73fce4a@gmail.com> (raw)
In-Reply-To: <CAGfcS_mBnWDceWgR7v_OMDrZjGGidSdmumpV0BH1uxwM=ikNMg@mail.gmail.com>
Rich Freeman wrote:
> On Fri, Nov 11, 2022 at 1:25 AM Dale <rdalek1967@gmail.com> wrote:
>> Is there some major change that causes copying .config file from 5.14 to
>> 5.18 or higher to break?
> So, I just upgraded to 5.15 recently and tend to stick to LTS kernels,
> precisely to minimize this sort of thing.
>
> My guess is that you missed something in make oldconfig, but obviously
> without exact errors that could be completely wrong.
>
> I can't speak to 6.0 specifically, but one thing that I've found is a
> gotcha is when they consolidate config items under higher level ones.
> So they'll take what used to be 50 questions, and turn it into 1
> question with 50 questions underneath it. The 1 question shows up as
> a new config item, and if you don't appreciate what it does and answer
> no to it, then you'll disable every item underneath it.
>
> Basically, don't assume that any new question is a new feature, and if
> you say no you'll still have all the pre-existing features. It could
> be a virtual question and answering no turns off a whole bunch of
> things that you had previously said yes to. You need to review
> oldconfig questions pretty carefully. You could try defaulting the
> answers but even then the defaults aren't always reasonable. They
> don't just turn on things you don't need. For example, by default
> linux turns off CGROUP support, and almost everything uses that today.
> That was just the first thing I checked, and I bet there are a million
> other gotchas like that.
>
> --
> Rich
>
>
I don't blindly answer those questions even tho it can be time consuming
at times. I tend to look at a new feature as something I don't need,
since I'm not adding hardware. I still look to see if it is something
new that could be useful. The new features are usually marked as new so
they're easy to see. What gets me, it asks for something that I've
already done before and it has the option I chose before already
selected but asks me anyway. That's kinda weird.
When I was going through oldconfig, I noticed that when I answered yes
to a new thing, files system option that I could possibly need one day,
that a whole bunch of related new stuff followed behind it. It makes
logical sense but it does open a can of worms for sure.
I wish there was a better way to update kernels but thing is, I can't
figure out a better way to do it either. I suspect if there was a
better way, someone would have figured it out by now anyway. ;-)
Now to reboot this thing, eventually. lol
Dale
:-) :-)
next prev parent reply other threads:[~2022-11-11 19:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 6:25 [gentoo-user] Upgrading from 5.14 to 6.0 version Dale
2022-11-11 10:30 ` Peter Humphrey
2022-11-11 10:35 ` Arve Barsnes
2022-11-11 10:56 ` Wols Lists
2022-11-11 18:12 ` Laurence Perkins
2022-11-11 12:24 ` hitachi303
2022-11-11 19:18 ` Dale
2022-11-11 22:08 ` Dr Rainer Woitok
2022-11-11 14:41 ` Rich Freeman
2022-11-11 19:42 ` Dale [this message]
2022-11-11 18:04 ` Laurence Perkins
2022-11-12 12:08 ` ralfconn
2022-11-12 16:00 ` [gentoo-user] " Nikos Chantziaras
2022-11-12 18:22 ` Dale
2022-11-12 18:43 ` Mark Knecht
2022-11-12 19:13 ` Wol
2022-11-12 20:02 ` Nikos Chantziaras
2022-11-12 20:03 ` Mark Knecht
2022-11-12 21:37 ` Dale
2022-11-14 19:57 ` Nikos Chantziaras
2022-11-14 21:05 ` Dale
2022-11-14 21:44 ` Michael
2022-11-14 23:56 ` Wol
2022-11-15 0:10 ` Dale
2022-11-15 17:46 ` Laurence Perkins
2022-11-15 2:36 ` Grant Edwards
2022-11-14 21:44 ` Mark Knecht
2022-11-12 21:17 ` Rich Freeman
2022-11-21 6:10 ` [gentoo-user] " Dale
2022-11-21 12:20 ` Rich Freeman
2022-11-21 20:52 ` Dale
2022-11-21 16:11 ` [gentoo-user] " Grant Edwards
2022-11-21 16:27 ` Michael
2022-11-21 16:50 ` Grant Edwards
2022-11-21 17:24 ` Michael
2022-11-21 18:12 ` Grant Edwards
2022-11-21 19:26 ` Michael
2022-11-21 19:37 ` Grant Edwards
2022-11-21 21:30 ` Frank Steinmetzger
2022-11-21 18:15 ` Laurence Perkins
2022-11-22 19:01 ` Wol
2022-11-21 16:58 ` Mark Knecht
2022-11-21 17:49 ` Grant Edwards
2022-11-21 19:42 ` Mark Knecht
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=bf646cd4-aa38-1d7c-5c44-1654c73fce4a@gmail.com \
--to=rdalek1967@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