My favourite thing about updates on my work Mac is when you say ‘try in one hour’ thinking it’ll ask you then an hour later it aggressively closes your programs. I use Linux, Mac and Windows regularly and Mac has by far the worst update experience out of all of them imo.
I’ve clicked the “install updates tonight” button a bunch of times, it consistently fails to update and then I have to force it to update the next morning. Incredibly poor experience.
Major update? 1 hour. Minor update? 1 hour.
Linux: I can’t stop you.
It could. It just doesn’t want to. Why would it? Its your computer.
If you want to delete / including the EFI partition turning your machine into a paperweight you should be allowed to do so.
I don’t want my mom to be able to turn her computer into a paperweight…
While that is possible. You do have to go out of your way to do that in ways a typical user wouldn’t.
Aside from that like others have said. Just don’t give sudo perms and have them use Flatpak.
Don’t give her sudo permission then.
How she will install anything then
you can add
sudo
permissions for individual users for certain commands only; and i recommend you would do that; i.e. give hersudo
permission for installing/uninstalling applications, but nothing else.Just to be clear, the person answering Flatpaks isn’t being flippant. Any tools, editors or games that Mom wants, she can safely install by searching and clicking ‘intall’, all without enough permissions to harm her computer.
Linux, for less technical parents, is genuinely really nice, now.
Installing old Linux applications IS a problem. They’re available only if someone repackaged them for newer distros. If not they can’t run anymore because of dependencies mismatch.
It’s gotten significantly better with containerization technologies like oci containers and flatpak. Yes it uses more storage, but the drive space pretty cheap
Just supply the dependencies with a chroot. That’s how we did it before distro maintainers started including the 32bit libraries into the 64bit OS.
Flatpak time
nix
solved this by modifying LD_LIBRARY_PATH to point to the desired dependency and/or modifying the binary itself.This is a good reason for static linking. All the dependencies are built into the binary, meaning it is more portable and future proof.
We don’t need flatpak for this!
You can also remove the fr*nch language pack via
rm -fr /
But in all seriosity, i tried to install Linux dual-boot with Windows on my dad’s computer last weekend, and it broke the windows install because it doesn’t support bitlocker (apparently). Maybe i could have gotten it to work, but i abandoned the project after the first failed attempt. Still a bit salty about that. Especially since it was meant to be a demonstration how “quick and easy” installing Linux nowadays supposedly is.
The best way to dual boot windows and linux is with separate drives, not partitions imo.
You’re missing the last step, throw out the windows drive.