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

    • superkret@feddit.org
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      2 months ago

      Another pro tip: You don’t need to update Arch every day.
      I update about once a month. Just make sure you read the news and deal with your .pacnew files.

      • I’ve gone months between updates. On servers, that’s a little more risky because it CVEs, which can also apply to the kernel, but LTS is probably safe enough there: if there’s a kernel CVE, LTS will be updated.

        I’ve had trouble with pinning the kernel before, though. Last time I did it, I went several months and forgotten I’d done it, and my system got itself wedged because some package was expecting a newer kernel; it took me a while to figure out.

        LTS might be a better option, since that will be caught be dependency management. Pinning can cause version dependency mismatch issues.