this post was submitted on 30 Dec 2025
517 points (79.3% liked)

linuxmemes

28663 readers
748 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.
  • Don't come looking for advice, this is not the right community.
  • 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
    [–] cley_faye@lemmy.world 3 points 1 day ago (1 children)

    Might be off topic, but does anyone else dread the outcome of their Linux system after an update?

    Not really. I don't really worry about that on most of my system. There is ONE computer where an update is a source of stress, and that's my main gaming computer where I had to setup dualbooting with windows. I learned the hard way that my motherboard implementation of UEFI kinda want windows to be there, otherwise it's very picky into which disk is parsed for EFI boot entries. But beyond that, nah. Laptop, desktop, company servers… just roll the update/upgrade, and the dist-upgrade when needed, fix the updated configs (for servers) and it's good to go. Been this way for the last decade or so.

    Worthy of note, I'm on ubuntu LTS (24.04 for now) or Debian stable (for servers), so not exactly outdated (I have the latest nvidia drivers…) but not bleeding edge either. I probably avoid a lot of issues this way.

    [–] LucidNightmare@lemmy.dbzer0.com 1 points 1 day ago (1 children)

    Thank you for your reply!

    Are you using the same drive for the dual boot? I ripped a spare SSD from a dead laptop a few years back, and installed tiny11 onto it and used my newer SSD for openSUSE. I've never had any issues this way, if that helps?

    My system is really just for PC gaming, so I understand!

    [–] cley_faye@lemmy.world 1 points 18 hours ago

    Technically, all the boot options were on the same drive (same EFI partition, on the disk that was initially used for years by windows), but for some reason, the motherboard decided "nope, there's no bootloader there".

    I ended up repartitioning the "first" drive seen by the bios to make a 100MB partition at the beginning, named it "EFI system partition", copied all the content of the old one from the other drive, and nuked the actual windows install in the process (not the boot entry though). Now all is good… I hope :D