Books on the concepts of using and administering *nix machines?

Question

linux

Please advise books on the concepts of using and administering * nix machines.
The books that I usually see say this: here is Linux, a very stable system, here is its file system, drivers are in this folder, and user files are in this folder, this is Shell, the script is written like this, which displays something , this is how we configure users, and this is how we configure the firewall. All this with some degree of deepening.
All this is not interesting, I know all this and it flows from one book to another.
Books that answer the questions "why" and "what approach" are interesting.
For example, I can’t understand why sudo is needed, if anyway, in order to install something, you have to issue all permissions to the user, and he stupidly comes under sudo -L and works there as if nothing had happened from under the root (and if they don’t work, then it is necessary to delicately lay out the rights that I somehow can hardly imagine how to do this)
Or you need to install some kind of package. First you need to go add the repository using wget, then execute some specific set of commands that is known in advance. Why not stupidly give the developer a .sh script that will do the same thing (I'm not talking about customization here).
Or is this how provisioning tools (chef, puppet) make life easier? In order to install some thread of a package more complicated than apache there, you need to go to change some .bashrc with your hands, change a couple of lines in the config of this freshly installed tool, change the owner of the third files to the user that the installer creates, something in interactive mode, set up, change something and immediately test it, and if not, then redo it. In short, it is not possible for me to set such a setting simply by a list of commands.
Or, for example, there was a discussion on some foreign forum about where to lay out application files: in /usr/local, /etc/, /opt or in a thin layer across all these directories, depending on the file types.
Well, in general, I would like to comprehend the questions of the universe. Because I can execute commands in the system, but every time I finish doing something (by the way, writing down what I did in a file or hoping for my own memory), there is an irresistible desire to nail the system, put it back clean and repeat _again_ again, but already “everything is correct”, although there is somehow no understanding of this “correct” one.
So what books would you recommend?

Answer 1

about the user and installation - it is enough to give the rights to execute the package manager from root. moreover, it is enough to grant the rights to execute the package manager with the install parameter and only with it.
about automation - without going into details - you are wrong. everything can be described. and edit files with utilities such as sed, awk, vi ... this is just the smallest list.
about the “thin layer” - man 7 hier - will give out a text about how it is “correct” in _given_ system.
in general, you do not need a book, but a familiar guru. who will answer your questions. I personally invite you to the St. Petersburg Linux Users Group. Subscribe to newsletter, ask questions. If you want to communicate live, come to the meetings (they take place every last Wednesday of the month at the Faculty of Geography of the University, 10th line, 35, white door on the ground floor immediately opposite the front door).
Directly answering your question, I recommend this list of references:
1. FreeBSD Handbook www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ (Russian translation: www.freebsd.org/doc/ru_RU.KOI8-R /books/handbook/ )
2. Evi Nemeth “Unix and Linux. System Administrator's Guide. www.ozon.ru/context/detail/id/7607778/ If there is no money, it is easy to find by name

Answer 2

www.ozon.ru/context/detail/id/1404972/ and in general any books by Philip Torchinsky that you like.

Answer 3

Mana, documentation, sources, mailing lists, discussions with colleagues. But the main thing, of course, is practice.
In general, you learn best by what you work with in practice, then by what you discuss in dialogue with other people, and only then do one-sided sources of information come, like books.
Therefore, the best way to learn is to work with a team of good specialists.
I can tell you, by the way, about sudo. The advantage of utilities of this class is that you can track privilege escalation through the log, and the administrator himself can elevate his rights if necessary, so that he works less as root and does not accidentally do something bad there. If we compare sudo and su, then sudo is better in that it allows, in particular, to fine-tune the access rights of individual users and groups to certain programs, for example, allow users from the @room312 group to execute "/usr/sbin/shutdown -h now" with root user rights and nothing more.