this post was submitted on 06 Aug 2023
579 points (96.8% liked)

linuxmemes

21263 readers
977 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] avidamoeba@lemmy.ca 4 points 1 year ago* (last edited 1 year ago)

    That's odd. If unattended upgrades are running, the system will do upgrades regularly. That means it's unlikely to get a significant backlog of updates queued up. Upgrade cycles typically finish briefly as a result. All my systems, interactive or headless, are running an update and upgrade cycle every hour. I've yet to to run into a case when I couldn't install a package because apt was in use. It's not impossible, but I haven't. Or at least it's been so long ago that I've forgotten about it. I don't have to think about unpatched vulnerabilities. ☺️