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.
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!
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
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.
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!
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