A Book on Linux
1–10 of 22 posts
Re: A Book on Linux
#2Re: A Book on Linux
#3Re: A Book on Linux
#4For me, it was Linux in a Nutshell (942 pages in the current edition) because I wanted a reference made of paper instead of pixels.
Later for deep background, Design of the Linux Operating System https://archive.org/details/DesignUNIXOperatingSystem but I picked up an used print copy for Those were the best books for me. You are not me. Good luck.
Re: A Book on Linux
#5Re: A Book on Linux
#6The modern editions of this book are primarily focused on Linux with some side notes for the BSDs.
Re: A Book on Linux
#7The Linux kernel doesn't matter. What matters is understanding the history, philosophy, and purpose of the unix environment.
You needn't become a religious zealot committed to the unix philosophy, but if you don't take the time to understand it, you'll never get the most out of the environment.
Re: A Book on Linux
#8Re: A Book on Linux
#9Unix Power Tools The Linux kernel doesn't matter. What matters is understanding the history, philosophy, and purpose of the unix environment. You needn't become a religious zealot committed to the unix philosophy, but if you don't take the time to understand it, you'll never get the most out of the environment.
Re: A Book on Linux
#10Also, a "book on linux" is going to look very different if it's based on Debian as opposed to e.g. NixOS. Linux distros come in all shapes and sizes and no matter what level you're operating on (just using the GUI, light sysadmin, deep systems programming, down to kernel hacking), they may appear as totally different paradigms.
I would recommend simply daily driving Linux. If you're still using another operating system, ween yourself off of that. Additionally, there are a bunch of obvious projects that are low hanging fruit for just getting to grips with Linux. Want a personal website? Spin up a VPS or a cheap laptop and build it from scratch. Set up your own personal email. Get certbot running. Write a simple server in C that can do request/response of TCP. Write an i2c driver for some random micro you have lying around. Whatever you are interested in making/doing, just go do it.
Resist the urge to google everything. `man` has more information than you think it does.