Mailing List Archive

On Sunday, 4 April 2021 23:31:50 BST Alarig Le Lay wrote:
> Hello,
>
> Has the 5.10 LTS has been stablised, I tried to upgrade it on some of my
> boxes, but `make oldconfig` doesn’t want to use my old config:
> Here is my make output: https://paste.swordarmor.fr/raw/2rRh
> And here is my config: https://paste.swordarmor.fr/raw/YHaG
>
> Does anyone else has to redo its configuration, and did you manage to
> reuse the old one?
>
> Thanks,

The 'make oldconfig' script steps through the previous configuration
selections and stops at any new options which require your input. In the
pasted output you provided the first option asking for your input is your
preferred compression algorithm for the kernel image. Choose any one of the
list below, or leave it to default (gzip):

Kernel compression mode
> 1. Gzip (KERNEL_GZIP)
2. Bzip2 (KERNEL_BZIP2)
3. LZMA (KERNEL_LZMA)
4. XZ (KERNEL_XZ)
5. LZO (KERNEL_LZO)
6. LZ4 (KERNEL_LZ4)
7. ZSTD (KERNEL_ZSTD) (NEW)
choice[1-7?]:

Then proceed to the next kernel option and so on.

Alarig,

On Monday, 2021-04-05 00:31:50 +0200, you wrote:

> ...
> Has the 5.10 LTS has been stablised, I tried to upgrade it on some of my
> boxes, but `make oldconfig` doesn’t want to use my old config:

I'm always using "make olddefconfig" rather than "make oldconfig" and
had no problems upgrading to 5.10. After running "make olddefconfig" I
use "diff" to compare the new configuration to a backup copy of the old
one, and should something catch my eye I'm correcting it using "make
menuconfig" as usual.

Sincerely,
Rainer

On Sun 04 Apr 2021 23:56:05 GMT, Michael wrote:
> On Sunday, 4 April 2021 23:31:50 BST Alarig Le Lay wrote:
> > Hello,
> >
> > Has the 5.10 LTS has been stablised, I tried to upgrade it on some of my
> > boxes, but `make oldconfig` doesn’t want to use my old config:
> > Here is my make output: https://paste.swordarmor.fr/raw/2rRh
> > And here is my config: https://paste.swordarmor.fr/raw/YHaG
> >
> > Does anyone else has to redo its configuration, and did you manage to
> > reuse the old one?
> >
> > Thanks,
>
> The 'make oldconfig' script steps through the previous configuration
> selections and stops at any new options which require your input. In the
> pasted output you provided the first option asking for your input is your
> preferred compression algorithm for the kernel image. Choose any one of the
> list below, or leave it to default (gzip):
>
> Kernel compression mode
> > 1. Gzip (KERNEL_GZIP)
> 2. Bzip2 (KERNEL_BZIP2)
> 3. LZMA (KERNEL_LZMA)
> 4. XZ (KERNEL_XZ)
> 5. LZO (KERNEL_LZO)
> 6. LZ4 (KERNEL_LZ4)
> 7. ZSTD (KERNEL_ZSTD) (NEW)
> choice[1-7?]:
>
> Then proceed to the next kernel option and so on.

Ah yes indeed, I never had a choice that early in the process. Thus, I
never saw the "Restart config..." and I misunderstood it. Thanks :D

--
Alarig

On Mon 05 Apr 2021 13:27:01 GMT, Dr Rainer Woitok wrote:
> I'm always using "make olddefconfig" rather than "make oldconfig" and
> had no problems upgrading to 5.10. After running "make olddefconfig" I
> use "diff" to compare the new configuration to a backup copy of the old
> one, and should something catch my eye I'm correcting it using "make
> menuconfig" as usual.

It seems to be a nice upgrade process, thanks!

On Mon, 2021-04-05 at 13:27 +0200, Dr Rainer Woitok wrote:
> "make olddefconfig"  rather than  "make oldconfig"

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.

On 05/04/2021 15:06, Matt Connell (Gmail) wrote:
> On Mon, 2021-04-05 at 13:27 +0200, Dr Rainer Woitok wrote:
>> "make olddefconfig"  rather than  "make oldconfig"
>
> 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.

Cheers,
Wol

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

On Monday, 5 April 2021 19:43:29 BST Neil Bothwick wrote:
> 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.

Eh? Did you read 'oldconfig' where 'menuconfig' was written?

> 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.


--
Regards,
Peter.

On Tue, 06 Apr 2021 13:59:11 +0100, Peter Humphrey wrote:

> > > 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.
>
> Eh? Did you read 'oldconfig' where 'menuconfig' was written?

Doh!


--
Neil Bothwick

IBM: I Blame Microsoft