In fact, the Unix and Linux System Administration Handbook offers a pretty good coverage of this topic.

Get a copy of "UNIX and Linux System Administration Handbook" by Evi Nemeth, et al. to get you up to speed on the basics.

As for development, depends on exactly what kind of development you want to do. You're going to have to be more specific.

On that note, I would like to recommend the most complete book I've encountered on the topic:
"UNIX and Linux System Administration Handbook" by Nemeth et.al.
Just because I wish someone had recommended it to me earlier.

"UNIX and Linux System Administration Handbook" is pretty much The Manual for sys admins. I am very grateful to all the authors of these books and offer my condolences to family and friends of Evi Nemeth.

http://www.barnesandnoble.com/w/unix-and-linux-system-admini...

I found The UNIX and Linux System Administration Handbook (5th Edition), chapters about networking and DNS very instructive, and they list a ton of additional references if you want to dig deeper.

Today I read that the "UNIX and Linux System Administration Handbook", which has become my new favourite technical book, strongly recommends learning Expect. I had to look it up, this was the first time I learned about it, and it made sense straight away (and, for what it's worth, the book starts with pointing out that mastering Vim is the most important sysadmin skill).

The one at your local university. Either one named something like "Introduction to Networking" or "Introduction to Distributed Systems", depending on what you want to learn.

You could also read some books. Rami Rosens "Linux Kernel Networking - Implementation and Theory" is quite detailed.

The "UNIX and Linux System Administration Handbook" (Nemeth et al.) covers a lot superficially and will point you in the right direction to continue studying. It's very practical-minded.

For low-level socket programming, you can probably read "Advanced Programming in the UNIX environment". It might be more detail than you need though.

At the other extreme, if you want to study distributed systems, you could read Steen & Tanembaums "Distributed Systems"

Grab Nemeth, et al's "UNIX and Linux System Administration Handbook" from your favorite online bookseller and work through each chapter. That'll get you basic fluency with the Unix command line and common administration tasks.

Beyond that, what you need to know really depends on the tech stack of the company you're planning to work for. I'd suggest at least working through the tutorials on how to set up and configure Apache, Tomcat, MySQL and the JRE enough to get a simple web site up and running.

Good luck.

Well, pleasant surprise people are finding this book. Heads up, it'll be getting a little update soon so that it matches the version that is now an appendix in Learn Python The Hard Way. I stripped out a few commands that weren't as useful and also added some more help on what to do when you get stuck (what I call the "reset"). Check out http://learnpythonthehardway.org/book/appendixa.html for the newer streamlined content.

In general I found these 14 commands end up being the smallest number anyone really needs to do basic CLI work, but keep in mind that the goal of the book is to give someone just enough experience to be able to go through my other books. There are plenty of more in-depth books on managing a server, so I don't bother to duplicate their work.

If you really want to learn how to manage servers and work the CLI, then check out "UNIX and Linux System Administration Handbook (4th Edition)" by Evi Nemeth and friends. My recommendation to people is to get a crappy computer you don't want, put OpenBSD on it following their http://www.openbsd.org/faq/faq4.html guide exactly, use the Nemeth book to configure every service you can and then point a security scanner at your box (like Nessus, or whatever they use today).

Once you can setup an OpenBSD box, get services running on them, and secure those services based on known attacks, then you can pretty much do anything. More importantly, OpenBSD is very bare bones so you learn the core of how a Unix system works and how to configure it, but their docs are very thorough and complete so you can do it if you follow them accurately.

Hope that all helps.

I remember Ed Kroll's books from the early-mid 1990s when I first started getting online.

Clearly they didn't date well, but his books along with the "Unix and Linux System Administration Handbook" (I had the red one, not sure which edition), set down the foundation for me.

Off the back of those I ended up going down a path as a Senior Engineer at one of the UK's largest ISPs and then getting back into development in the Internet industry ever since.

I owe a lot to Ed Kroll, amongst many others. Great to see this released through PG.

There are definitely several options, but I would recommend Pandoc to compile an epub from LaTeX source — off the top of my head.

Images are not problematic at all on an e-reader. Here’s an example of how an illustration looks like on my old Kindle:

https://i.imgur.com/zfqbnOO.jpg

Tables and such are also usually just raster images embedded in the epub’s XML:

https://i.imgur.com/SHYUrNL.jpg

https://i.imgur.com/u0tZ2TO.jpg

…and so are code blocks, usually displayed in a monospaced but condensed font and converted to raster image as well to avoid wrapping:

https://i.imgur.com/d7ly8GH.jpg

https://i.imgur.com/g0lIPpj.jpg

Long story short: Images are not an issue, and there’s a way to ensure code blocks will look good by converting them to images. That would indeed require some work, but maybe there's a tool to automate that?

Edit: All examples are from UNIX and Linux System Administration Handbook by Garth Snyder et al., Addison-Wesley Professional; 5th edition (2017)