Teach Yourself Unix in 24 Hours 250
Spencerian writes "The surge of Unix-derived operating systems such as Mac OS X, Linux, and the now-free Solaris is not slowing against the fortified but embattled breakwaters of the Microsoft operating system family. But new power users of other operating systems, including those just starting with Unix as well as the graphical interface of the operating system (such as the Mac OS Finder, or the navigators of KDE or Gnome), remain in need of a comprehensive primer for Unix that complements their previous knowledge. The fourth edition of Dave Taylor's "Teach Yourself Unix in 24 Hours" should remain on the top of the buy list for computer users in need of a strong Unix reference where they may find themselves managing or using the subtle variants of Unix flavors." Read the rest of Spencerians' review.
| Sams Teach Yourself Unix in 24 Hours, 4th Edition | |
| author | Dave Taylor |
| pages | 518 |
| publisher | Sams Publishing |
| rating | 7.5 of 10 |
| reviewer | Kevin H Spencer |
| ISBN | 0-672-32814-3 |
| summary | The fourth edition of Dave Taylor's "Teach Yourself Unix in 24 Hours" should remain on the top of the buy list for computer users in need of a strong Unix reference where they may find themselves managing or using the subtle variants of Unix flavors. |
The format of this Sams book, as with other books in this "Teach Yourself...In 24 Hours" series has not changed. The book content does favor Windows or Macintosh users when describing, comparisons and contrasts of Unix tasks to those popular operating systems. Unless the reader has been a fan of very little-used operating systems in their past and somehow managed to avoid Mac OS, Windows or Linux, absorption of what is needed for each chapter shouldn't be difficult.
Each chapter is technically noted as a one-hour lesson, although the author acknowledges that many may need more than one hour to absorb some material and should take as much time as they need to understand what they need to know. Chapters include the Unix basics such as using text editors such as vi, moving and copying files, viewing file contents and locating files in the operating system, and topics scale upward to advanced shell programming and even Perl programming. Generally, most readers need not read from beginning to end, chapter to chapter. Despite the lesson-like mode of the book, "Teach Yourself Unix" is a reference.
The "Teach Yourself" books are not advanced reference books, however, and "Teach Yourself Unix in 24 Hours" is no exception. As someone that's used more and more Unix commands in the background of Mac OS X to make things easier or to circumvent limitations or flaws of the Mac OS X Finder, the previous editions of "Teach Yourself Unix" were handy references when I needed a quick and certain process to accomplish a task. Sometimes it's too easy for graphical interface users to moan and while when the Windows Explorer or Mac OS X desktops stick and slows to a crawl when managing something as simple as copying a file, forgetting that there is another way. This book contains the basics to manage these tasks without being too basic of a reference.
The author's breadth of knowledge in many Unix-derived systems such as BSD, Solaris, and Linux continue to extend themselves well in the lessons. Each chapter contains explanations and examples to aid those that need more information. Most Slashdot readers might find this level of detail a bit plodding, but some newbies to Unix may need this since Unix is not inherently a graphical operating system that's easy to understand by sight, so things need to be literally spelled out. Peppered throughout the book are sidenotes that keep the reader apprised of exceptions or proper etiquette when handling, discussing or pronouncing Unix tasks and terminology.
There's a marginally useful amount of back matter on the book, consisting of two appendices, one on frequently-asked Unix questions, and another more useful appendix on managing the Apache web server from a command line. The back cover has a simple command-line reference that's not bad, however, being Unix, the amount of commands and versatility seem a bit limited, so the command-line reference lacks a bit of punch. Some chapters seem a bit archaic and probably need to be reconsidered in a future edition--very few of us may have a need to send mail from the command line in this age of Yahoo Mail and the sheer number of mail services available on computers in schools, businesses, homes, and even from cell phones for jotting off a quick note to a comrade for quick answers. Full-time conversing by mail in Unix isn't something I feel anyone but the most hardcore Unix user will relish--and those users aren't the audience of this book.
This book is designed for new Unix users, but intermediate users will find "Teach Yourself Unix in 24 Hours" a handy reference when having to workaround GUI pitfalls or failures. This book's previous versions have saved my bacon in reinforcing my previous experience and skills at the command line when the Mac OS Finder seizes, leaving no graphical way to complete a task. Unfortunately, given the volume of information I must remember in using both Mac OS X and Windows XP, I, for one, can't remember every nuance of Unix needed, particularly since it's not as easily remembered as icons or menus. Perhaps the author may find that a fifth edition will need information on the long-awaited Windows Vista in the event it contains Unix parts and pieces."
You can purchase Sams Teach Yourself Unix in 24 Hours from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
The best way is to solve a problem (Score:5, Interesting)
I've found that the best way is to solve some particular problem. Example: add these four new disks from the JBOD enclosure to your linux system. This teaches about the physical device drivers, device files, volume mgmt, filesystem mgmt, and mounting them upon boot (which touches many important aspects of UNIX).
Working with someone else who can help point you in the right direction and solving a problem by yourself is much much better than a book.
I quit Sam's years ago (Score:4, Interesting)
I'm afraid I can't pull any punches on this one: any "teach yourself X in 24 hours" book is snake oil to get your money. It's there to take advantage of people with the wrong attitude - Unix (and most of IT along with it) evolves so continuously, it practically re-invents itself every five years (through BSD, Linux, Solaris, etc). Get it in your head that it's a "learn-it-once" thing and you end up ten years later still able to babble Apple 2 Basic and remembering that SIMM = "single inline memory module" and DIMM = "dual inline memory module", but having to scurry back to the docs every time you edit your Python script.
Re:insulting? (Score:1, Interesting)
Nor do I think people can learn C or C++ or Java in 24 hours.
Lots of people think they can, looking and interviewing people out there you would think they at least know how to cut'n'paste the key words, but upon questioning them it shows right away.
A sure sign I will not hire them.
My problem with "learning Unix" (Score:5, Interesting)
I've only played with HP-UX and a couple of Linux flavors - and not long or thorough enough to know what's going on under the hood.
Some examples:
How does **nix boot? How does it interact with hardware? Is there a general hint to what all the directories are about or any memory aids for knowing what's in them? Permissions - any chance of an overview of what the bits mean, why they might be used and how they're actually used?
The books I've seem go right from a brief history of Unix to either installing it or talking about commands. I've got no problem learning the "how", but I really need to know the "why" before I will spend the valuable time re-learning my way around an OS. Until then, I'll be sticking with Windows.
Does anyone know any books that address the "how it all works together" part? I'll be happy to read man pages and cryptic HOWTOs once I know why I'm doing it.
Re:Good start... (Score:3, Interesting)
I have a UNIX cert, and know what I'm doing on many flavors of *nix. I'm proud to say (as I push my glasses up the bridge of my nose) that I have vi skillz.
I have not opened the command prompt on any of my OS X systems in over a year.
When I was doing it, over a year ago, it was to ssh to a Linux web server that I used to have.
Once you get used to harnessing the full potential of OS X, bash becomes as redundant as... well... vi.
Re:Step #1 (Score:4, Interesting)
*nix has a weird learning curve. At first, the CLI-centered approach is intimidating. Then you learn the FHS (or BSD's hier); some basic commands like man, apropos, ls, cd, cp, mv, rm, and eventually find, grep, and a couple of other things; and it's not so scary. Then you try to figure out how to add a kernel module, and you either have people hold your hand through it without actually teaching you anything, or you have to try to dig this out from man and co. yourself.
I've found it very difficult to get beyond knowing the basics to actually being comfortable with the system. It doesn't sound like this book would help much...
Re:Good start... (Score:3, Interesting)
Funny, I had this same issue on my server at home, my solution eventually was to buy a Netgear wireless router/print server. I tried with CUPS, I really did, for a few years as I thought it was a cool solution, but upgrading would *always* break it. I'm at work, phone rings, my wife says, "I can't print". As a client, CUPS is fine, but on a server? No thanks.
CUPS = Can't Usually Print Stuff.
Re:Good start... (Score:2, Interesting)