Bank clients. Taxi aggregator clients.

There’s one case when you can’t avoid using command line. If you ask someone on Internet to help you, he will say you to type some commands. No window clicking, no screenshots will help. All GUIs are different, but CLI is (almost) always the same, and its output is well searchable. That’s why you see numerous command line listings in each topic discussing problems and could decide it’s impossible to use Linux without coding.

In depends on how dumb the user is. If you want to see drive C:\ and don’t want to learn why there’s no such a thing, forget about Linux (and any other OS except the only one you are familiar with). If you are ready to learn new concepts and just don’t want to remember numerous commands, that’s OK, just pick up a distro with advanced DE and graphical admin tools.

What does an ordinary RHEL admin do when something does not work?

“Easy to use” means that you do less and get more. Learning doesn’t count if you learn something once and then use the skills you obtained many times.

No, some piano plays are still harder than others, mo matter how long you practice. Editing text with vim is easier than with nano after some practice.

Why do you think so?

It is easier after you learn basics. Learning is not easy, but usage is.

Every day in my case, except holidays.

Vim (or emacs, or any other advanced text editor) is much easier to use than nano when you need to do something more complex than type couple of lines.

There are few fdisk options that work non-interactively, like -l (list partitions). It is impossible to create or delete partitions this way.

From the sfdisk man page:

Since version 2.26 sfdisk supports MBR (DOS), GPT, SUN and SGI disk labels

fdisk is completely interactive, not suitable for scripting. sfdisk is a “scriptable fdisk”.

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.

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.