• Kabe@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    7 months ago

    I do not like the frequency of reboots necessitated by kernel upgrades. I know that I could mask it, but IME that eventually causes problems with packages than make .ko kernel modules; it’s just more things to fail, and it makes me really wish Linus would have just based Linux on MINIX.

    Here’s a tip that you might not be aware of: Arch has an LTS kernel. It may seem counter intuitive to run Arch and not have the latest, bleeding edge kernel, but the upside is that you get a stabler, less breakage-prone system.

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

      • Kabe@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        7 months ago

        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.