In the introduction, Scott says: "While man pages are useful, they are often not enough, for one simple reason: They lack examples."
Oh, yeah. Boy does THAT strike a chord. They lack examples, and they lack thorough exploration of the command. I really like the idea of digging in and going beyond the man page (and I've done that here now and then).
So, how did Scott do? Very well, I think: I liked this - a lot.
Scott gives examples and discussion of just about everything you are likely to do at the command line from basics like 'ls' to using package managers. The discussion is reasonably thorough and new Linux users (or even just Linux users new to the command line) will surely learn from it.
Of course I have quibbles. Throughout the book I kept thinking "but why didn't you mention this?" or "I would have been sure to add x". But that's me, isn't it? We old command line folk have all learned a thing or two, and if we wrote all of it down, it sure wouldn't fit in any book you'd want to carry around. For example, Scott did a few paragraphs on "du". I would have also mentioned " du -s * " which is something I use often when searching for missing disk space - it gives the story of the current directory's sub-directories without the detail of a plain "du". With quite a few things, I had things I would have added like that. But so what? That's why I have this web site, right?
Old hands at the Linux command line may find this slightly less valuable than the newbies, but if you are coming to Linux from other Unixes, this is a handy and concise reference that will make you more aware of the Linux differences.
Good job. Good book. I liked it.
Order (or just read more about) Linux phrasebook from
Amazon.com
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Sun Jul 2 12:56:56 2006: Subject: bruceg2004
"Throughout the book I kept thinking "but why didn't you mention this?" or "I would have been sure to add x". But that's me, isn't it? We old command line folk have all learned a thing or two, and if we wrote all of it down, it sure wouldn't fit in any book you'd want to carry around."
I still think you should write a book, Tony. I enjoy your writing style, and you certainly have plenty of experience. So, how about it?
:-)
- Bruce
Sun Jul 2 13:09:47 2006: Subject: TonyLawrence
Pretty much the same answer as for the mistress:
too old, too tired :-)
But seriously: if I were going to write a book, it would be similar to this one, and it would be a tremendous amount of work for a fairly limited audience. I'm not sure it would be worth it: I probably do better with the website than I would with a book.
I have thought about an "e-book" - collecting certain articles from here and editing them into a coherent whole, maybe with some additional material - but there's the problem for me: the way people make money with things like that is to "hold back" good stuff for the thing they sell. That's just not in my nature; I'm not going to hold back - I'm going to publish it freely here always.
So.. I'm just not sure any of it makes sense for me.
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar