Technically, no. Until you want to mount something but find /mnt is busy or simply forget about this and mount something there, losing access to previously mounted stuff. The only problem is that you have to remember which mountpoint you use for particular filesystem, while the FHS is designed to avoid this and abstract from physical devices as much as possible.

Why though?

The filesystem is organized to store data by its type, not by the physical storage. In DOS/Windows you stick to separate “disks”, but not in Unix-like OSes. This approach is inconvenient in case of removable media, that’s why /media exists. And /mnt is not suited for any particular purpose, just for the case when you need to manually mount some filesystem to perform occasional actions, that normally never happens.

Just media files, downloads, images , music kinda stuff.

That’s what usually goes to /home/<username>. Maybe mount that device directly to /home? Or, if you want to extend your existent /home partition, use LVM or btrfs to join partitions from various drives. Or mount the partition to some subdirectory of /home/<username>, or even split it and mount its parts to /home/<username>/Downloads, /home/<username>/Movies etc. So you keep the logic of filesystem layout and don’t need to remember where you saved some file (in /home/<username>/Downloads or in /whatever-mountpoint-you-use/downloads).

/mnt is not for everything, it is a temporary mount point. For fixed drives that are constantly mounted you should use another location (that could be anywhere in the filesystem tree).

Mount them where you need. Not /mnt and not /media. Maybe /var or its subdirectory, or /srv, or /opt depending on what kind of data you want to store on that partition.

It is easy to get hacked if you make stupid mistakes. Just don’t make them.

And not only did everything “just work” flawlessly, but it’s so much faster and more polished than I ever knew Linux to be!

Congrats, you are very lucky. But try to survive couple of version upgrades before recommending it to noobs.

You have to replace these lines with something similar to this (change libaacs to libgcrypt everywhere). Then run autoreconf -iv (you must have autoconf installed). It will create a new ./configure script which will work if you did everything correctly.

Refer to documentation.

man jq

It’s just generally faster to use the terminal if you know what you’re doing.

It’s also true for other distros. Not because they have poor GUI tools but because CLI is faster than GUI if you know what you are doing.

Be careful if you buy a Samsung 8x0 SSD. They have long standing bugs that may cause data loss. They are worked around in the kernel, however you have to ensure that the workaround for your particular model exists in the kernel version you use.

Glibc preserves backward compatibility, so if you build against the oldest version you want to support, the resulting binary will work with newer ones.

However that’s definitely not what I recommend to do. Better learn packaging and build native packages for distros you are going to support. OBS can make this a bit easier (if your software is FOSS), but any modern CI will also do the job.

Isn’t that video stream already compressed? Or you want to convert it using another codec/bitrate?

LOL, all Linux vendors = Red Hat.

All generalizations are false.

It is not steganography. It’s just cat original.png trojan > malicious.png.

I don’t know, however this is impossible to understand what’s wrong with your fonts.

What kind of changes? Package installation, removal and configuration? Use apt-mark showmanual to save list of manually installed packages, dpkg --get-selections | grep 'deinstall$' to save list of removed packages, debconf --get-selections to save debconf package settings, backup files that you edited in /etc. This should be enough for restoration, wouldn’t take a long time for backup and avoid risk of filesystem inconsistency.

In what country? There are various national certifications for this purpose.

The standard answer: don’t backup the system, automate its deployment instead. Backup only data.

git config core.sshCommand 'ssh -i <path to desired key>'

The biggest problem that I see on this screenshot is that it is a compressed JPEG.