Can't relate, arch testing never broke in years. Without manual maintenance.
If it where arch, but its manjaro. Somehow during the last kernel update the grub info was not changed to point to the current kernel names...still pointed at the old kernel....and that had been replaced. After figuring all that out in chroot, fix was as simple as changing a single line in that grub file
Manjarno never surprises -_-
The dangers of relying on a prebuilt system which is maintained ... lets just say not state of the art.
Also, would grub-hook be an option?
I'm sorry, is this some joke I'm too atomic to understand?
Do y'all only have one kernel installed?
Yes. If I ever need something else because something unforeseen happened (which has not happened for years, and I use a non-default one), I can boot up from a live USB and fix things.
I use arch btw.
chroot has all the power to fix it, but my mental state cant handle it
Mood
lughs in multiple installed kernels
My PC: "Oh, you touched /etc/fstab? Fuck you"
Give
systemd-analyze verify /etc/fstab
A try!
Systemd solves all of your problems!
But then I'd never get to use my recovery media :(
Users should never have to fiddle with the fstab manually. It's a shame the internet is still pointing to it when asked most of the time instead of explaining the GUI disk tools. Or at least some CLI management tool in case that one exists.
This is the correct mindset to have when trying to push Linux as a viable alternative to the big two.
If you make more things easy for newcomers and just anyone in general, you'll eventually get more users, and a larger base that then correlates to higher overall usage of Linux. You know, like those screenshots of the Linux install base we see every now and then?
You don't have to keep Linux behind arbitrary lines, but for some reason, that's all we like to do.
I can’t relate because Bazzite doesn’t let me do stupid shit :)
My laptop with arch was lying around untouched by 2 months and this shit happened too, after that i switched and daily drived opensuse tumbleweed for PCs and debian stable for servers for a year already
I once fully updated a Gentoo system that hadn't been touched in 4 years. That was an adventure in troubleshooting.
Holy shit
sudo init 0 because yolo
I dont understand, what does this command do?
Turns off the system
laughs in atomic distro
