Discussion on:
View:
Show:
"Linux Administration Handbook" by Evi Nemeth, Garth Snyder and Trent R. Hein (and others). My edition is from 2002 and it is still very relevant today. It's very distro-neutral and covers the fundamental in a very detailed but accessible way.
I have a lot of the books you mention. I also have over 40 of the O'Reilly reference books covering a wide range of topics, eg snort, security topics and a number of "hacks" books.
Almost all have some references to Linux. A few are, of course, all Linux, eg the prior mentioned snort reference. I have found solutions/answers in just about all of them. No one reference stands out among the bunch, with the exception of the ssh guide.
One thing I will say about the pocket guide: it's great to loan to someone using Linux for the first time. For this purpose though, the entries actually could be a bit shorter, more codified rather than explained.
ps - list running processes.
common usage:
-C -list process by name
-A -list all processes
...etc.
Of course you can go to the man page for most commands, but you probably wouldn't sell too many books that pointed that out up front.
I've loaned this to around a dozen people by now, all have found it useful enough. It serves another purpose in that these people get the perception they have exceeded this book's usefulness, they've achieved a level of knowledge that puts an entire book "beneath" them, under their belt or whatever term of accomplishment you might use.
Not sure if I'm getting that point across correctly. Someone is daunted by the task of learning something new. They are given a small, introductory style quick reference. It seems foreign and incomprehensible, 'a lot of work' is in store. But they quickly outgrow this book, an entire 'chapter' is done and behind them now.
Even if false, the sense of achievement is nothing to sneeze at. Most of the new Linux users I see seem to have lost the anxiety they naturally demonstrate when I drive off into the sunset leaving them alone with an unknown operating system between them and their intended use. By the time they hand the pocket guide back to me they're saying things like "that (CLI) was nothing" and "it's really quite straight forward," they've obviously formed a framework for answering their own questions.
So maybe this guide is like handing a diploma to a first grade-bound kindergartener, so be it. The emotional hurdles are usually the larger ones anyway.
Almost all have some references to Linux. A few are, of course, all Linux, eg the prior mentioned snort reference. I have found solutions/answers in just about all of them. No one reference stands out among the bunch, with the exception of the ssh guide.
One thing I will say about the pocket guide: it's great to loan to someone using Linux for the first time. For this purpose though, the entries actually could be a bit shorter, more codified rather than explained.
ps - list running processes.
common usage:
-C -list process by name
-A -list all processes
...etc.
Of course you can go to the man page for most commands, but you probably wouldn't sell too many books that pointed that out up front.
I've loaned this to around a dozen people by now, all have found it useful enough. It serves another purpose in that these people get the perception they have exceeded this book's usefulness, they've achieved a level of knowledge that puts an entire book "beneath" them, under their belt or whatever term of accomplishment you might use.
Not sure if I'm getting that point across correctly. Someone is daunted by the task of learning something new. They are given a small, introductory style quick reference. It seems foreign and incomprehensible, 'a lot of work' is in store. But they quickly outgrow this book, an entire 'chapter' is done and behind them now.
Even if false, the sense of achievement is nothing to sneeze at. Most of the new Linux users I see seem to have lost the anxiety they naturally demonstrate when I drive off into the sunset leaving them alone with an unknown operating system between them and their intended use. By the time they hand the pocket guide back to me they're saying things like "that (CLI) was nothing" and "it's really quite straight forward," they've obviously formed a framework for answering their own questions.
So maybe this guide is like handing a diploma to a first grade-bound kindergartener, so be it. The emotional hurdles are usually the larger ones anyway.
You make a good point about that potential social value of such a book. Unfortunately, the Pocket Guide serves that purpose primarily because it fails at being very useful -- to say nothing of the fact that it's also distro-specific, which further limits its usefulness even within this limited scope. Something actually designed for the purpose you describe would be a nice thing to have.
Maybe I've found the technical book concept I should actually tackle for my first book. Hmm. . . .
Maybe I've found the technical book concept I should actually tackle for my first book. Hmm. . . .
A Que Book. I pulled it from my bookshelf this morning because I wanted to know about something.
Another case of the answers were not there.
I'll put it in a charity bag.
Another case of the answers were not there.
I'll put it in a charity bag.
I have never read that book. Is it this book? If so, maybe you should add a review to that amazon page for it, since so far it has exactly two reviews, both of which give it five stars.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
