• gerbilOFdoom@lemmy.world
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    1 year ago

    You can set up a Cron job or systemd timer for the root account to run that command regularly, if it is a non-interactive command!

      • gerbilOFdoom@lemmy.world
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        1 year ago

        I’ve never had to interact with system updates in Linux distros beyond saying “yes I want to update” in the last decade. If I didn’t want to, there’s usually a force update flag available to skip the asking part. Would I do this for a server without backups? Absolutely not. For home use? I’ll roll the dice; I have backups even if there’s a couple days of shipping time to get all 12TB mailed to me.

        Of course, major distribution releases are a different monster. Fortunately, I don’t deal with those often and when I do, I migrate instead of upgrade.

        • cyanarchy@sh.itjust.works
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Ah, I forget sometimes that I’m in a general linux community and not the arch community.

          I run arch, btw.

          Which I think is why I have a different attitude about this, the rolling release system can occasionally cause snags. I haven’t had any of the major chaos that other people will warn you about, but I have had some oddities relating to shifting dependencies or upstream changes. I’ve had one or two things refuse to update citing mandatory manual intervention.