Comments by "Anony Mousse" (@anon_y_mousse) on "An Update Borked My Linux System. How Did I Fix It?" video.

@majoraxehole That's funny because I think UEFI needs to go the way of the dodo. It'd be nice if we could have an actual secure boot loader and one that the user could control without a backdoor available to a software vendor, so not UEFI.
3
Just four? Does it make me a hoarder that I've got 20?
1
Sounds like a reason to not use systemd and makes me happy that I don't.
1
That would require you keep the old kernel, and some people don't do that. Personally, I only bother to update the kernel for security updates and I'll definitely keep the most recent previous kernel, but I also have space, something that yet again not everyone has.
1
@marck0060 So then the explanation is clear why he didn't do it, to show others who didn't have his backups how to do it.
1
@leopard3131 All true, but then it also makes the same mistake DT made in assuming Arch. I'd love to see a more generic video on how to solve this problem for every other distro since it seems oddly common these days. Maybe Slackware is just more stable, but I've actually never had this problem.
1
@leopard3131 Sure, it's probably just a wrapper for normal chroot, but the upgrading the kernel part is the real meat of the video and that's not a universal method. Although admittedly, I'd really want him to go over compiling the kernel too, and that's not something that can be done in a 5 minute video.
1
My favorite distro is Slackware, but I'm probably biased.
1