this post was submitted on 02 Oct 2025
707 points (94.8% liked)

linuxmemes

27540 readers
2197 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 users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
  • 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, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] SnotFlickerman@lemmy.blahaj.zone 13 points 1 day ago* (last edited 1 day ago) (2 children)

    unattended-upgrades and cron jobs for everything else ftw.

    [–] ExtremeDullard@piefed.social 21 points 1 day ago (1 children)

    No Linux system of mine upgrades itself without my explicit consent. That's one of the many reasons why I don't run Windows.

    [–] SnotFlickerman@lemmy.blahaj.zone 22 points 1 day ago (1 children)

    Setting those up is me explicitly giving my consent for it to upgrade on a schedule.

    Yeah alright. That's one way of looking at it πŸ™‚

    I guess what I meant is that I don't like upgrades that happen without me explicitly requesting each and every one of them, and me watching the upgrade process as it happens for errors.

    [–] NeatNit@discuss.tchncs.de 6 points 1 day ago (2 children)

    I never got unattended-upgrades to work for me on the machine I tried it on. Best I could tell, it just didn't do anything. It was frustrating.

    But many years back I set up my raspberry pi with a cron job that was effectively (if not literally) apt update && apt full-upgrade && reboot and that seemed to be working just fine.

    It broke some things (horrifically) for me because headers didn't get updated, modules didn't get rebuilt.

    To make it worse, I didn't set it up. That shit is disabled now. Defunct. Toast. Never again to run.

    [–] boredsquirrel@slrpnk.net 3 points 1 day ago (1 children)

    You need to edit the config file

    [–] NeatNit@discuss.tchncs.de 3 points 22 hours ago (1 children)

    I followed a number of guides to try to get it to work. Including doing that. No dice.

    I still think it's probably user error on my part, but I'm still shocked there was no command to effectively "force run an unattended upgrade now" to test that it works correctly.

    [–] boredsquirrel@slrpnk.net 1 points 9 hours ago

    I even set it up using ansible, should work lol

    Install the package, edit the config file, maybe enable a systemd service, maybe not even that