The “slow down and then quickly fully freeze”, while it could be other things, might be a low RAM situation. Could be some buggy program that is leaking memory. Try running EarlyOOM or systemd-oomd.

Listen to yourself. What’s a distrobox? Boxbuddy? I’m already annoyed about someone expecting me to learn about this and I’ve used Linux exclusively for 25 years. I actually did Linux from Scratch and used that for 6 months for actual stuff. Telling a noob who wants to do normal things that work on a normal Linux distros that because of the (recommended by you) immutable distro they have, they need a container which has an actual normal linux distro inside it to run the thing they want to run, they’ll want to run away and probably never speak to you again.

And about flatpak: I had so many bugs that somehow only happen when you get the flatpak. And you can’t install command line tools over flatpak, you can’t install servers or drivers. Regular users (especially windows power user types) are likely to run into these things and curse you for recommending the one distro where you can’t just apt install theclitoolineed.

I’m not sure about recommending immutable distros to noobs, I’ve read enough reports from people that want to (or because of some hardware crap, need to) install or mess with some low-level stuff that just won’t work on the immutable distros, plus a bunch of online advice or help will just not be applicable.

I don’t think so and have never heard that, but I could be wrong.

You can just do for f in * (or other shell glob), unless you need find’s fancy search/filtering features.

The shell glob isn’t just simpler, but also more robust, because it works also when the filename contains a newline; find .. | while read -r will crap out on that. Also apparently you want while IFS= read -r because otherwise read might trim whitespace.

If you want to avoid that problem with the newline and still use find, you can use find -exec or find -print0 .. | xargs -0, or find -print0 .. | while IFS= read -r -d ''. I think -print0 is not standard POSIX though.

My built-in SD card reader shows up in lspci as an “SD Host Controller”. Since lspci and lsusb should list everything that’s connected, it should show up there. If it’s not there, it is not connected, or idk, it’s broken maybe. Or it’s not listed with a name, just a number. I think the names come from some database of known devices. Maybe your SD card reader is a unicorn and nobody has ever seen it before and so it’s not in the database.

Pretty sure the main difference is that one puts stuff in a directory called esp (which I assume is a placeholder for the actual directory?), and the other one is put in /efi. That needs to be the path to your efi partition, because that’s where the UEFI expects to find things it can boot. The target is probably redundant, i.e. it defaults to x84_64-efi on Gentoo (maybe not on Arch?) and the id is just a name, you can put whatever there. See man grub-install.

I have never used the Steam beta or Proton-GE or whatever information is spreading out there to noobs about what they should do, and I’ve been gaming exclusively on Linux for more than 20 years. Only do this beta or bleeding edge stuff if you have a problem, and a good reason to believe that will help (like people reporting your specific issue is fixed in beta). Or I guess if you’re bored out of your mind. And expect other issues since it’s fucking beta.

Oh those dang culture warriors, amiright. *shakes fist*

Unlike say you, who would never post an article about how NPR isn’t right-wing enough (lol) on a Linux forum.

I’ve been in the discord and on github for a while

Oh a real life member of the hyprland community, let’s see if the rumors are true.

has a bit of a “personality”, as many good developers have. Nothing wrong with that.

Well, that’s some first-grade bigot apologia. I guess that discord really is bigot central.

Let’s hope this thing blows over quickly.

Is it because your little clubhouse is drawing too much negative attention?