• 1 Post
  • 358 Comments
Joined 7 months ago
cake
Cake day: March 24th, 2026

help-circle








  • esc@piefed.socialtolinuxmemes@lemmy.world•reboot NOW
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 days ago

    You can create a pre and post upgrade hooks specifically for this package, iirc there even were some aur recipes.

    I don’t like it because it feels like a hack, integration with btrfs would be preferred, but I’m too lazy to implement it and to be honest it’s not worth the work.





  • esc@piefed.socialtolinuxmemes@lemmy.world•reboot NOW
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 days ago

    Reboot is a recommended choice on any linux system after kernel upgrade (systemd as well).

    It’s not a simple package manager and it can do a lot, not on the level of zypper but it’s pretty complete. There are some intentional limitations, true.






  • esc@piefed.socialtolinuxmemes@lemmy.world•reboot NOW
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 days ago

    You can use pacman hooks to backup and then restore modules pre and post kernel upgrade. I’ve used it for some time, it bothered me so I’ve started to think about how to make it better (use btrfs features) but in the end just returned to reboot after upgrade scheme.



  • With LLM it’s closer to 60/40, you can get an MVP in a day or two, but the next step is either impossible or so hard it will require so much resources that it makes it almost impossible. But if you start with a very clear idea of architecture and software stack - in that case you’ll get 80/20. Then the real problem starts - you don’t know your code, and have no idea how everything interacts and there going to be thousands or tens of thousands of lines of shit that does nothing or done something in the past that LLM forgot to remove, or it left a document that describes it so it won’t remove it and so on.