I didn’t know about the LTS kernel. How does that interact with module packages, like the fscking Broadcom support packages, or bcachesfs (before it for mainlined)? That’s where I’ve historically run into issues with pinning the kernel.
I will absolutely look into this, though. If it prevents the “you need to reboot or else” messages after every Syu, I’m in. On Arch, when you get a message like that, it’s best heeded.
I’ve never had to deal with Broadcom drivers or pinned the kernel, so I can’t tell you anything about that. The LTS kernel (currently 6.6.32-1) still updates regularly, albeit not nearly as often as the stock Arch kernel, so that means fewer updates that require a reboot.
Just install linux-lts and linux-lts-headers via pacman, and you’re good to go.
I didn’t know about the LTS kernel. How does that interact with module packages, like the fscking Broadcom support packages, or bcachesfs (before it for mainlined)? That’s where I’ve historically run into issues with pinning the kernel.
I will absolutely look into this, though. If it prevents the “you need to reboot or else” messages after every Syu, I’m in. On Arch, when you get a message like that, it’s best heeded.
I’ve never had to deal with Broadcom drivers or pinned the kernel, so I can’t tell you anything about that. The LTS kernel (currently 6.6.32-1) still updates regularly, albeit not nearly as often as the stock Arch kernel, so that means fewer updates that require a reboot.
Just install
linux-ltsandlinux-lts-headersvia pacman, and you’re good to go.