Not aware of any correct pictures, but I can tell you what's wrong with this one

• /usr: explaining it as "Unix System Resources" is a bit vague
• /bin: /bin is usually a symlink to /usr/bin
• /sbin: /sbin is usually a symlink to /usr/sbin, distros like Fedora are also looking into merging sbin into bin
• /opt: many, I'd say most, "add-on applications" put themselves in bin
• /media: /media is usually a symlink to /run/media, also weird to mention CD-ROMs when flash drives and other forms of storage get mounted here by default
• /mnt: i would disagree about the temporary part, as I mentioned before, stuff like flash drives are usually mounted in /run/media by default
• /root: the root user is usually not enabled on home systems
• /lib: /lib is usually a symlink to /usr/lib

I would also like the mention that the FHS standard wasn't designed to be elegant, well thought out system. It mainly documents how the filesystem has been traditionally laid out. I forget which folder(s), but once a new folder has been made just because the main hard drive in a developer's system filled up so they created a new folder named something different on a secondary hard drive.

I don’t get why this sort of picture always gets posted and upvoted when it’s wrong for most distros nowadays.

Snake case.

• Starts with a lowercase, good for shell autocompletion
• No spaces, so no worrying about spaces in shell commands
• '_' is better than '-' because it shows the spaces between words more clearly

Yup. I like their just in December approach too. I have a problem with distrohopping so I'm often re-setting up my system. Every time I do, Thunderbird pops up donation prompts both in the app and in my browser. I get why they do it, but it's annoying when that happens. KDE's approach avoids this pitfall.

Most package managers do not touch your home directory, so they will not delete user data. That needs to be done manually.

Snap and flatpak are exceptions, with an optional argument they will also delete the app's folder (~/snap/appName for snap, ~/.var/app/flatpakID for flatpak).

But is GPL-compatible, unlike ZFS.

The TLDR is that Microsoft released a secure boot update that blocked insecure versions of GRUB. This update was only meant to go out to Windows users since releasing it to dual booted users could break GRUB. However, it was accidentally also released to dual-booted users.

The fix involves disabling dual boot, running a command to reset secure boot, then re-enabling.

Place your bets, are we getting GIMP 3 before 2025?

Blender's Wayland support is not great because they're doing stuff from scratch. They're not using an existing toolkit like GTK, Qt, Electron, or even something like SDL to get Wayland support.

But if you're using an existing toolkit things are much easier and support is automatically there, you just need to do testing to ensure everything works.

The common biggest things that still use Xwayland are Chromium based apps and programs running under wine/proton. Chromium has an experimental Wayland mode that works well enough, but definitely has some bugs, especially around windowing. Wine Wayland is in the works.

No way it's Microsoft neofetch

A reminder that the Linux Foundation does what its members want. The members may not care about the Linux desktop, but more server oriented things and running LLMs on those servers.