I’m sorry, is this some joke I’m too atomic to understand?
lughs in multiple installed kernels
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.
I also use Arch btw. I have an lts kernel installed just in case. Came in handy when the amdgpu driver was broken for a week. The screen was flashing on Wayland.
My PC: “Oh, you touched /etc/fstab? Fuck you”
Give
systemd-analyze verify /etc/fstab
A try!
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.
Wrong. You just need to know what you’re doing and must not be impatient. Just spend 5 damn minutes reading before you do the thing. We don’t always need unnecessary abstractions upon abstractions upon abstractions.
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.
On don’t have a gui on that one.
Reminds me of that time I updated my UEFI firmware which automatically re-enabled secure boot which caused my Nvidia driver to fail to load on boot because Nvidia doesn’t sign them so I was stuck with the noveau(spelling?) driver which would crash when I tried to log into my DE. What an adventure figuring that out was. Oh, and the cherry on top: updating the firmware didn’t fix the initial issue I was troubleshooting.
Ugh, I just went through the same thing last week. Let’s just say that checking if secure boot had been turned back on was NOT one of the first 500 things that came to mind during troubleshooting.
Exactly. I was about to rip my hair out before I thought to check my UEFI settings.
That is brutal lol. RIP.
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 -_-
Yet another Majaro L? Not one to dunk on random distros, but I’ll always make an exception for Manjaro
Only the morons that turn on AUR despite being warned against it ever have problems on Manjaro.
Maybe im misunderstanding something but how is turning on the AUR supposed to prevent the grub file from being updated?
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?
Grub-hook is what I use to prevent this exact situation.
GRUB-HOOK PACKAGE GIVES YOU STABILITY ON THE SYSTEM YOU LOVE
THE KINDA STABILITY THAT MAKES YOU BOOGY
*insert cringe dance*
„Wheres that fucking pendrive again?”
ah shit here we go again
chroot has all the power to fix it, but my mental state cant handle it
Mood
I’ve been their lol. Was cool to learn some new shit but not something I ever want to do again. Have moved to QubesOS and use a Debian base cos Debian simple af
I can’t relate because Bazzite doesn’t let me do stupid shit :)
sudo init 0 because yolo
