Resync config with upstream debian

[ToeiRei]

No description provided.

[ToeiRei]

vm.config was not synced back on distro change. Should be fixed next build

[its0ka]

i compared
https://github.com/ToeiRei/kernel-deb/blob/main/kernel-configs/vanilla.config
and
config-6.7.12-amd64.txt (debian sid kernel .config)

and found differences like CONFIG_MODULE_COMPRESS_XZ and CONFIG_TRANSPARENT_HUGEPAGE_MADVISE.
are they intended or not?

[ToeiRei]

That's intended on vanilla.config due to a feature request - vm.config should be like vanilla.config with less drivers and compression was adapted to use xz a while back as it was easier on the VM in my test runs.

[its0ka]

but as i can see compression is not set in your .config and it takes more space than default debian kernel

[ToeiRei]

I just dug through my archive - it was due to an userland problem back then leading to my kernel being unable to boot. I did plan to reactivate it at some point. Guess I should do a general debian-resync at some point as I can see some changes done upstream that I did not do on my end.

Btw - sid will always be something I don't address as I'm using the config from stable - which is currently "bookworm"

[its0ka]

but what's the point in using old .config with newer kernel? old .config will keep some new things disabled. Your current vanilla.config looks very old (2019 config?), it lacks TLS, MPTCP,... (things that bookworm already has)

[ToeiRei]

The config was based on 6.1 as per debian bookworm for compatibility reasons.

[its0ka]

looks much older to me (reasons above), i guess i'll just wait for debian kernel team to drop kernel 6.8 to sid repo

[ToeiRei]

As I am using my kernel builds in production builds I have to be much more conservative than to use experimental sid settings. You cannot just change things to 'new and cool' if the userland below does not do it.

Still, resync is a must from time to time, which is what I'm doing right now. Next release should have the new configs implemented