linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
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"
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.
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.
On don't have a gui on that one.
Give
systemd-analyze verify /etc/fstab
A try!
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
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