I "finished" my Linux and Unix Troubleshooting E-Book today. Of course it's not really finished: I'll probably be adding and revising for months (and yes, all buyers get free updates), but at 45,000+ words, there was enough to let 'er go.
I have been wanting to do this book for a long time. This is NOT a list of common problems you'd run into on Unix and Linux systems. What would be the point of that? You can look up specific problems on Google for free - why would you need to pay for a book?
No, this is about what you do when the answer isn't on Google. It's hints, tips, advice, scripts.. sure, I do take specific examples but those are presented to show how they were solved, not just "here's the answer".
I do have specific chapters on printing, networking, performance and so on, but again: it's not a listing of the common problems and solutions. Go to Google for that; this is much more.
Right now it's 93 pages and more than 45,000 words - not your typical junky 15 page e-book. As I noted above, I'm sure I'll be adding to it regularly but this is a good beginning.
I really enjoyed writing this. If you work with Unix or Linux, I think you'd enjoy reading it.
Partial table of contents:
- Are you a good Troubleshooter?
- What skills do you need?
- Identifying the problem
- Rule #1: one variable at a time
- Logging and trapping
- Installation Problems
- Booting Problems and Other Hangs
- Networking Problems
- Disk space
- Why is my system slow?
- Miscellaneous Troubleshooting Cases
Got something to add? Send me email.
(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version
Increase ad revenue 50-250% with Ezoic