Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Unix Books Media Operating Systems Software Book Reviews

Teach Yourself UNIX System Administration In 24 Hours 361

Spencerian writes "UNIX guru and writer Dave Taylor's Teach Yourself Unix System Administration in 24 Hours is a strong "rosetta stone" reference and tutorial for beginning and intermediate Mac OS X, Linux and UNIX system administrators. The book covers fundamental and specialized UNIX sysadmin tasks for three UNIX flavors: Red Hat Linux 7.2, Solaris 8, and Mac OS X, version 10.1.2. Although Mac OS X and Red Hat have advanced in versions since this book was published, it doesn't appear to affect the book's usefulness since many of the tasks involve the venerable UNIX command line." The rest of Kevin's review is below -- read on to see if this book might help you.
Teach Yourself Unix System Administration in 24 Hours
author Dave Taylor
pages 508
publisher Sams Publishing
rating 8
reviewer Kevin Spencer
ISBN 0672323982
summary Teach Yourself Unix System Administration in 24 Hours makes an excellent rosetta stone for beginning or intermediate UNIX sysadmins.

The Big Picture

As you might get from the title, Sams Publishing's "24 Hours" book series attempts to teach specific tasks or steps within 1 chapter per hour. UNIX can get pretty complex, so it would seem that this format would limit the effectiveness of this book. Not so.

Topics from the book include:

  • Unix Installation
  • Documentation
  • File Ownership
  • Disk Usage
  • Account Management
  • Package Management (including the Fink system for Darwin)
  • Process and System Controls
  • Network configuration
  • Web Server Management and shell scripting

Almost every chapter views how a particular task is handled with Linux as its normal focus, where many commands are shared between Solaris and Mac OS X. When functionality differs, Taylor downshifts to show how matters are handled in each respective operating system. As someone very experienced with Mac OS X, I found Dave Taylor's discussions on Mac OS X idiosyncrasies in contrast to Red Hat and Solaris very useful, particularly where Darwin overrides the traditional dotfile preference configuration, substituting the convoluted NetInfo services.

What to Expect

Dave provides a Q & A section after each chapter. In an early chapter, Dave answers a typical geek question, "What Unix distributions do you run on your own systems?" Dave provides a very geeky answer--his Apple PowerBook G4 is running Mac OS X (with Darwin as its core, of course), along with a PC running Windows 2000, Linux Mandrake 8.1, and a web server running Red Hat Linux 7.2--a varied assortment that shows Dave puts the author in authority. In a later chapter, Dave touches on emulators such as WINE and Virtual PC as options for additional operating system support.

What makes the book work is that Dave provides a very conversational tone throughout the book, almost as if you're sitting with him in front of a system, talking while you do your thing. Humorous moments are scattered in appropriate moments to make things less dry (this is UNIX, after all).

Questions that weren't answered for me as a beginning UNIX sysadmin in another book by Dave Taylor, Learning UNIX for Mac OS X , were available in droves in this book. Topics such as scripting with perl or from the shell, disk quotas, crontabs, rlogin, managing system logs, and the like--all answered. Ever wondered how Mac OS X handles system init states? You'll discover that its a tad different from other UNIX systems, but not too much.

The Bad and the Upshot

I ran into several layout problems in the book that were somewhat annoying, such as where tables or notes were sliced between pages, making them difficult to read. It wasn't a showstopper at all, but I hope that a later reprint will pass muster.

If you're still getting your feet wet with a few basics, or have a really mixed environment of UNIX flavors, this book may be very useful to you. I'd recommend this book to any Mac OS X technician who wants to take advantage of its UNIX underpinnings. Beginning Linux users should also find this a strong general reference. The book's cost ($25) is very reasonable, even a bargain for a book of this depth. Overall, Teach Yourself Unix System Administration in 24 Hours makes for a very well rounded reference, as well as a tutorial book. Perhaps the title should be shorter--it's quite a tongue twister.


You can purchase Teach Yourself UNIX System Administration 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.

This discussion has been archived. No new comments can be posted.

Teach Yourself UNIX System Administration In 24 Hours

Comments Filter:
  • UNIX rosetta stone (Score:5, Informative)

    by Plutor ( 2994 ) on Tuesday November 12, 2002 @10:44AM (#4650983) Homepage
    I'm sure its not nearly as comprehensive as this [bhami.com] UNIX rosetta stone.
    • by Anonymous Coward
      Why this supposed "Rosetta" stone was made for a Microsoft browser is a mystery. (Requires IE 5)?
    • by imac.usr ( 58845 ) on Tuesday November 12, 2002 @11:11AM (#4651244) Homepage
      I'm sure its not nearly as comprehensive as this UNIX rosetta stone.


      Well, it certainly isn't as slashdotted as that one is....

    • I'm sure its not nearly as comprehensive as this [bhami.com] UNIX rosetta stone.

      I hope it is. I used the Rosetta stone when I was first learning AIX. I bumped into a number of discrepancies and omissions.
    • by nachoman ( 87476 )
      Learn how to be an Rocket scientist in 24 hours.

      You can't get experience in a book. In my opinion you can learn way more from an experienced sysadmin then you can from a book.
      • Many more of us will have access to a book than an experienced sysadmin. Besides, self-learning is a valuable and viable process, after all, who taught all the guru's?
      • by walt-sjc ( 145127 )
        Well, I don't know about that. I took a job YEARS ago as a Novell network admin. I had Never worked novell before. Before I started the job, I read a Novell book cover to cover. First day I was productive. Other than peeking at the book every now and then, I was able to get my job done.

        What DOES kinda irritate me is the "24 Hours" part. Sorry, you can't even scratch the surface in 24 hours - especially with UNIX. While I WAS productive right off the bat with Novell, my prior experience with UNIX and other networking systems allowed me to figure things out quickly. Without a good solid background, I would have been toast. I really was a "junior" novell admin. Over the next several months at that job, I felt totally comfortable doing quite advanced tasks with novell.

        While you can pick up some simplistic skills in 24 hours, there is a LOT more to UNIX system administration that you just can't learn from a book, or even another administrator. You have to do things for yourself. You have to understand the concepts. You have to play with things, look around, compile some apps, install some systems, run into problems and solve them, learn scripting, regular expressions, read TONS of man pages, etc. This takes MONTHS. Most of your true learning comes from problem solving.

        I do take some exception to the "learn more from a sysadmin" comment. The problem with this approach is that sysadmins FREQUENTLY are not good teachers. In fact, I find sysadmins in general to be among the WORST teachers of any profession. Working side by side with one, you will learn small little snipits of valuable stuff, but rarely will you understand the WHY of things. S/He probably isn't going to present info to you in any organized manor, and the info will most likely be very incomplete. Hey, that's just been my experience working with / managing dozens of admins - many of them VERY good at what they do.
  • The book covers fundamental and specialized UNIX sysadmin tasks for three UNIX flavors: Red Hat Linux 7.2, Solaris 8, and Mac OS X, version 10.1.2. Although Mac OS X and Red Hat have advanced in versions since this book was published,

    Solaris 9, anybody?
    • It's probably not possible that you can get a book out like this out without some operating system having an upgrade between finishing the writing and it hitting the shelves.

      Like the Unix System Administrator's Handbook, the best you can do is teach a general philosophy, with some examples for each of a few representative systems, then *maybe* have an updates page on a website somewhere.

      I've always found that, once you know in principle how to do something, doing it on a different flavour of Unix is just a matter of reading the man pages for different options to the various commands. (Or in the case of solaris, swearing a lot and saying things like "mount /floppy wasn't good enough for ya, ya had to make a new command for it?!?!?")

      dave
  • by Dot.Com.CEO ( 624226 ) on Tuesday November 12, 2002 @10:45AM (#4650993)
    Teach yourself open heart surgery in 24 hours.

  • by goodhell ( 227411 ) on Tuesday November 12, 2002 @10:46AM (#4651004)
    I hope my sys admin isn't really reading this book.

    (I hope he's already obtained these skills)
    • Re:For some reason (Score:3, Insightful)

      by liquidsin ( 398151 )
      I hope he's already got those skills too. But for those of us who dabble in *nix systems as a hobby rather than as a profession / religion, books like this are quite nice.
    • Re:For some reason (Score:3, Interesting)

      by Dukebytes ( 525932 )
      Actually i am not a big fan of the 24 hours/7 days/dummys book. The idiot and dummy books just insult you right on the cover - i refuse to buy any of those. But some of the others can be pretty good.

      I taught a network troubleshooting class once and had to pick between a $75 book and a $20 book. the $20 one was Teach Yourself Network Troubleshooting in 24 hours. I picked it because of price mostly (thinking of the students) and it looked pretty good. Not as much material as the $75 book - but still had a good bit in it.

      It worked out very well and the students actually liked it a lot becuase it was a little funny and had good basic concepts in it.

      Not trying to be an ass or anything. But you might want to hope that you sys admin is reading this book - along with others im sure - becuase if he isnt - some fellow employee in the company could be surfing thru your files right now....

      Duke

  • backups (Score:2, Insightful)

    by Gizzmonic ( 412910 )
    Does it have anything in it about making backups? I'm learning UNIX (AIX, actually) in a "trial-by-fire" sort of way, and it's different enough from Linux for me to have problems finding good info on backups. Luckily I'm not the main guy running this machine (yet) but I like to learn all I can. Does anyone know of a crazy straw?
    • Re:backups (Score:2, Informative)

      by Anonymous Coward
      Try http://www.oreilly.com/catalog/unixbr/ by Curtis Preston. It is a great resource.
  • by Stir ( 446728 )

    Does it come with a musical workout montage when the blonde popular admin challenges you to a ski off?

  • but.. (Score:5, Funny)

    by kin_korn_karn ( 466864 ) on Tuesday November 12, 2002 @10:47AM (#4651011) Homepage
    but does it teach you these things?

    • how to worship your uptime?
    • why you the machines are 'yours' (never mind the company that your work for who paid for the things, with a hundred other depts besides IT)
    • how to be arrogant beyond belief about the abilities of users to do their own management of [files|directories|disk space|processes]
    • how to use being on call as a blanket excuse for everything?
    • how to revel in your asshole nature ala BOFH?


    Until then, it's not teaching you jack shit about sysadmin'ing.
    • Re:but.. (Score:2, Funny)

      by Russ Steffen ( 263 )

      I don't see how it could. All these things must come from experience.

    • [gir/180] % ssh sysadm@rhein uptime
      sysadm@rhein's password:
      8:35am up 620 day(s), 20:04, 1 user, load average: 0.05, 0.02, 0.02

      Who wants to bring it? That system is constantly running a number of apache based proxies, Solaris based of course.

      • You mean that there have been no remotely exploitable bugs that at least required daemon restarts in that time? It really doesn't matter if the kernel is up for 620 days if the services have had to go down once a month for patching.

        Or do you not apply the security patches?

        • It runs an apache proxy as I stated earlier. That is it, yes apache has restarted many times in that window. In addition the ssh daemon has been restarted with new version at least six times.

          What do you take services down for hours while you update them?

  • by pigeon ( 909 ) on Tuesday November 12, 2002 @10:47AM (#4651020) Homepage
    Essential System administration by Aeleen Frisch. Covers Solaris, Aix, Linux, HPUX, SCO etc. Alas no OS X.
  • great book (Score:4, Interesting)

    by tps12 ( 105590 ) on Tuesday November 12, 2002 @10:48AM (#4651026) Homepage Journal
    As a Unix sysadmin for seven years, I'd have to agree with the reviewer that this book is a lifesaver. I find that information tends to dissipate from my head after I absorb it (sort of like Mother Nature's swapping algorithm LOL), so I spend the first day of each month rereading it, and this keeps my skills charged for the rest of the month! I've even gotten pretty good at scheduling major projects for early in the month, when things are fresher in my head.
    • I find that information tends to dissipate from my head after I absorb it

      That's a good thing. Permanent memory should hold more sublime things.
  • by Orlando ( 12257 ) on Tuesday November 12, 2002 @10:48AM (#4651035) Homepage
    Damn, I knew all those years experience were a waste of time...
  • 24 Hour miracle (Score:2, Insightful)

    by kryonD ( 163018 )
    Learning UNIX administration in 24 hours is like learning how to secure a Microsoft server in 24 hours.

    Well, I guess since it's actually possible to administer UNIX, there's a difference.
  • Rosetta stone (Score:2, Informative)

    by dnoyeb ( 547705 )
    aka Rashida stone is an Egyptian relic which contained some text written in Heiroglyphics, Greec, and Demotic. It contained the same text written in 3 different languages thus allowing people to understand a great deal about how to translate between the 3 languages.

    The rosetta stone reference Is supposed to imply this book will help you understand UNIX and make what appears foreign, understandable.

    I assume this is what the reference is supposed to mean.
    • Close. The stone had three languages saying the same thing. This book tells you how to do the same/similar things in different flavours of *nix, so the Rosetta stone theme matches nicely. Find what you want in the flavour you know, and then see what the other flavours look like.
    • Re:Rosetta stone (Score:3, Informative)

      by SN74S181 ( 581549 )
      As an aside, Sun just published [sun.com] what should be considered the 'Rosetta Stone' for Solaris. If you get into wrestling matches with Sun systems and need a good comprehensive introduction, you need to download this one RIGHT NOW.
  • Teach Yourself... (Score:4, Insightful)

    by ThrasherTT ( 87841 ) <thrasher@deathma[ ].net ['tch' in gap]> on Tuesday November 12, 2002 @10:50AM (#4651046) Homepage Journal
    I've read a couple of the "Teach Yourself X in N [days|hours]" books. I have not read this one, but my experience with the others is that they can be best considered an "entry point" into the subject, and a reference for only the most basic questions. Anyone who thinks they will acquire even an intermediate level of skill (starting from an unskilled base) by reading these books are, IMHO, mistaken.

    • These aren't "Become the Master of UNIX in 24 hours", or "Become a Astrophysicist in 24 hours"

      The books basically are a catalyst for you to learn more, explore, buy more books, etc etc
    • I would go a bit further... all the "Teach Yourself X in N [days|hours]" books I've tried sucked monkey bollocks. It was that Perl one, and the ASP one and a few more that I can't recall offhand. I only bought the Perl one myself, luckily.

      Granted, last time I tried it was quite some time ago (funny what wasting money on useless stuff teaches you to avoid) and they might have gotten a review process instead of beer party and authors instead of monkeys nowadays. I sure hope so, for all the poor sods that buys their books.
    • I love books that say 24 hours and are 508 pages long. Come on! You couldn't even read that in 24 hours. There are some books out there '31 days to teach yourself C++' or whatever. Then you realize - it's 31 days for each chapter.
  • Seriously... (Score:4, Interesting)

    by ekephart ( 256467 ) on Tuesday November 12, 2002 @10:52AM (#4651070) Homepage
    How many of these books can one own? I have plenty of books, but the mile-wide-but-foot-deep-overview books get old. I have Glass and Ables' "Unix for Programmers and Users" and Oreilly's "Running Linux". I reference there every so often (in fact just yesterday while installing VOCAL [vovida.org]), but I'm not sure there is much more I could get out of a book that wasn't specifically about some library or application.

    Most of the quick reference stuff anyone needs is on various websites and discussion boards.
  • by delta407 ( 518868 ) <`slashdot' `at' `lerfjhax.com'> on Tuesday November 12, 2002 @10:53AM (#4651075) Homepage
    "What Unix distributions do you run on your own systems?" Dave provides a very geeky answer--his Apple PowerBook G4 is running Mac OS X (with Darwin as its core, of course), along with a PC running Windows 2000, Linux Mandrake 8.1, and a web server running Red Hat Linux 7.2--a varied assortment that shows Dave puts the author in authority.
    Since when does Windows 2000 count as a Unix distribution, and how does running an assortment of operating systems make him an authority?
  • by Plutor ( 2994 ) on Tuesday November 12, 2002 @10:53AM (#4651079) Homepage
    > In an early chapter, Dave answers a typical geek question, "What Unix distributions do you run on your own systems?" Dave provides a very geeky answer--his Apple PowerBook G4 is running Mac OS X (with Darwin as its core, of course), along with a PC running Windows 2000, Linux Mandrake 8.1, and a web server running Red Hat Linux 7.2--a varied assortment that shows Dave puts the author in authority.

    I would argue that running Linux and OS X does not (necessarily) make someone an "authority" on UNIX. Where's his Solaris, SUNOS, HPUX, IRIX, and BSD experience? Has he ever installed cross-platform software? Only using a few machines, I would doubt he's using NIS or NFS. Has he ever?
  • Could it be this book was secretly published by Microsoft to try and produce a glut of sloppy sysadmins and therefore diminish the security and credibility of Unix, much as inventing the C programming language was actually a backfired cold war plot to set back Soviet computer science?

    Note for the humor impaired: It's a joke, not a troll...
  • Disclaimer (Score:2, Interesting)

    http://www.google.com/search?hl=en&lr=&ie=UTF-8&oe =UTF-8&safe=off&q=%22Dave+Taylor%22+%22Kevin+Spenc er%22 [google.com]

    The question is, at what point does slashdot have to start adhering to standard ethics of journalism? Which is to say: the person who wrote the glowing review -- located conveniently over a link to purchase the book at bn.com -- should at least tell us he's an author of published works on the same subject... whose books are listed alongside those of the author he's lauding.
    • by aborchers ( 471342 ) on Tuesday November 12, 2002 @10:57AM (#4651108) Homepage Journal
      Ummm... It's called peer review. Would you rather have a pastry chef reviewing Unix books?

      • Re:Disclaimer (Score:3, Insightful)

        No. But, for all I knew before I googled him, Kevin Spencer WAS a pastry chef.

        If you're going to review a book, tell us who you are. An average Joe? The author's peer? Did you share a room with him at a UNIX conference in Toledo? Do your daughters play soccer together?

        Slashdot readers are intelligent people who don't like to waste their time or be told half-truths. Any information about the identity of the reviewer that might allow us to form a more informed opinion of the book should be divulged. This isn't amateur hour. Lots of professionls use this site and as such upholding some basic journalistic tenets is a sound idea.

        • Slashdot readers are intelligent people who don't like to waste their time or be told half-truths

          Somethingwicked started to choke violently on his drink.

          "What a wonderful exciting cough," said the little man, quite startled
          by it, "do you mind if I join you?"

          And with that he launched into the most extraordinary and spectacular
          fit of coughing which caught Somethingwicked so much by surprise that he started
          to choke violently, discovered he was already doing it and got thoroughly
          confused.

          Together they performed a lung-busting duet which went on for fully
          two minutes before Somethingwicked managed to cough and splutter to a halt.

          "So invigorating," said the little man, panting and wiping tears from his
          eyes. "What an exciting life you must lead. Thank you very much."

          He shook Somethingwicked warmly by the hand and walked off into the crowd.
          Somethingwicked shook his head in astonishment.


          Slashdot readers are what??? *grin*

      • Re:Disclaimer (Score:3, Interesting)

        by macdaddy ( 38372 )
        Would you rather have a pastry chef reviewing Unix books?

        No, I'd rather have someone in the target audience review the book.

    • Disclaimer My Ass! (Score:5, Informative)

      by Spencerian ( 465343 ) on Tuesday November 12, 2002 @12:53PM (#4652130) Homepage Journal
      I am not the "Kevin Spencer" you reference.

      I am Kevin H. Spencer, author of one modest, now-somewhat-antiquated book on getting started with Mac OS X programming. [amazon.com]

      I am a technical editor and occasional contributing writer for a few Mac-oriented computer books from the old Dummies Press, Pearson Education, and Premier Press publishers. I make my living by supporting Macs and PCs, and have probably done so for longer than you have lived.

      Aside from receiving a copy from which to make this review, I don't get a thing from this.

      And, if I didn't find it more useful to explain who I am for benefit of the article, I would've used my mod points to hack your karma for making such bad presumptions. There's also a "South Park"-ish Canadian cartoon [kevinspencer.com] with my name in it, but I doubt he's a UNIX expert, either.

      No book is a perfect reference, but this is a good one if you are getting started with system administration across various platforms. Don't knock a book due to the title. It's actually quite detailed and deeper than what the title implies.

      For a relatively new system admin for Mac OS X systems, this worked for me, and it might work for others with similar skill levels.
  • by painehope ( 580569 ) on Tuesday November 12, 2002 @10:56AM (#4651102)
    those "Teach Yourself ${whateverThing} in 24 Hours" books aren't worth the paper they're printed on...the 30 days ones aren't bad for just learning the nuances of a language ( like GTK+ ), but you can get more sysadmin knowledge from buying your sysadmin 8 pints, listen to him rant and rave, and then take him back to the computer room hell-bent on vengeance w/ a screwdriver in hand...actually, you might have his job if you can talk him into a little cathode ray tube repair ( those suckers pack a lot of voltage )
  • Only half a joke (Score:4, Interesting)

    by drinkypoo ( 153816 ) <drink@hyperlogos.org> on Tuesday November 12, 2002 @10:57AM (#4651109) Homepage Journal
    The number of places you need to know to look for things on a Unix system and the way you troubleshoot is usually fairly simple and you do not look in a lot of places, thus a cookbook approach is reasonable. Teaching you a few major gotchas and how to use a couple utilities (like lsof, fuser, or the local equivalent) will take you VERY far.

    On the other hand, a book like this can never make you a GOOD systems administrator as the secret there lies in years of experience, knowing what kind of odd, twitchy little things to look for; and also knowing how to use all these neat little utilities and chain them together in the shell (of your choice) to make them do large, complicated, magical things.

    A book like this might very well be the beginning of a beautiful career. The worry is that people will read it and think they're ready to tackle the world. Of course that's why we have certifications, but they only prove one's ability to regurgitate knowledge on command. Handy, but a book like this can give you just about everything non-vendor-specific that shows up on most Unix certs, I'm guessing -- and some of that, too.

    On the gripping hand, it used to be matter of course that the sexretary or similar ended up being the one to maintain the mainframe, being sent to Armonk for classes... you know what I'm talking about. Maybe someday some of Unix's quirkiness will be ironed out and that sort of thing will be feasible in Unixland. I'm not holding my breath, though.

  • I wasted 29 extra days reading another book! Damnit!

    Does anyone really buy books from the 'dummies' 'in 24 hours' or 'in 30 days' series? Do you keep these books on your desk as reference? I bet that distills confidence in coworkers.
    • Yeah, actually I have "Teach yourself PHP4 in 24 hours" on my desk, it's been there since I first bought the book...generally books on desks at my job are more used by others that may not be at the same level you are at in a particular skill-set or are interested in learning about it, kinda like an internal library...

      now books like "The SQL Programmers Reference" on my desk, yes that I use for reference :)

    • I've actually purchased a couple of "for dummies" books...

      The truth is, they can be a great intro to a subject that you don't know anything about. That said, however, they seem to be one-off books. That is, you read them once, and then never use them again. (The possible exception would be the "cheat-sheets" that some of the books include inside the back flap.)

      So I would certainly consider getting, say, PHP for Dummies if I was looking for a quick intro into the basics of PHP, after which I would sell it again and by myself a good look-up reference for when I start getting into the details.
  • by grub ( 11606 ) <slashdot@grub.net> on Tuesday November 12, 2002 @10:58AM (#4651117) Homepage Journal

    sooo.. this is the UNIX equivent of an MCSE?

    • So learning to click I Accept/OK to every dialog box and rebooting the machine whenever something goes wrong takes 5 minutes ...

      What are they doing for the remaining 23'55" ?

  • by curtisk ( 191737 ) on Tuesday November 12, 2002 @10:58AM (#4651120) Homepage Journal
    This book is just a lead in to the rest of the series....
    • Teach Yourself UNIX server restoration in 24 hours or else.
    • Teach Yourself Office Diplomacy in 12 Hours or less.
    • Teach Yourself Creative IT resume writing in 2 Hours.


    *Disclaimer* I have not read the book in question and the above is simply a joke, but the thought of teaching UNIX system administration in 24 hours seems unlikely....covering basics, maybe...most of these books seem to serve that purpose and are great as a reference in alot of cases.

    • but the thought of teaching UNIX system administration in 24 hours seems unlikely

      Yeah, but think of the backlash if they had called it "UNIX System Administration for Dummies" ;)
  • by Silas ( 35023 ) on Tuesday November 12, 2002 @10:59AM (#4651132) Homepage
    I can see it now:
    Objective: to obtain a system administration position in a large IT department.

    ...

    Experience: started learning System Administration about this time yesterday.
    "Yeah, sure buddy, you're hired. Here's the root password and here's some old user accounts we need cleaned up. And would you mind replacing our sendmail install with qmail, we've been getting a bunch of calls lately from wackjobs screaming about some sort of "open relay" problem. Who knows...I'm sure you'll get that all figured out."
  • by Mr2cents ( 323101 ) on Tuesday November 12, 2002 @11:05AM (#4651193)
    If you ever get stuck in a text editor and you can't quit, type [ESC]:q[Enter]
    After this first encounter, you'll hate that editor. But you will change... slowly...
    • by odaiwai ( 31983 ) on Tuesday November 12, 2002 @11:20AM (#4651323) Homepage
      > If you ever get stuck in a text editor and you can't quit, type [ESC]:q[Enter]
      > After this first encounter, you'll hate that editor. But you will change...
      > slowly...

      and after a week or two setting up servers, you'll reflexively type :wq whenver you finish something.

      dave :wq
    • by macdaddy ( 38372 ) on Tuesday November 12, 2002 @11:59AM (#4651665) Homepage Journal
      The only thing you need to remember:

      export EDITOR=pico

      or for you tcsh-challenged people

      setenv EDITOR=pico

      vi scares people, even old timers and especially newbies. IMHO vi should *never* be the defauly editor on any distribution. If a power user wants it, let them change it. Give the newbies (the ones that don't know how to change it) something they can use like pico or joe. If we really want to make our OS user-friendly (read: newbie-friendly) we're going to have to start making some compromises on the default settings. The default editor should be easy to use; by default the firewall shouldn't allow local services; daemons and all their friends and relatives should NOT be running by default. Until we make concessions such as these, we can not expect Linux (or any other *nix except for OS X) to be easy for newbies to grasp. We're skilled enough to be able to turn on advanced features and change the defaults to suit our needs. Newbies are usually barely competent enough to get the install right. Lets think about our next Linux generations for a while.

    • by jayed_99 ( 267003 ) on Tuesday November 12, 2002 @12:35PM (#4651977)
      The first time I used vi, I used CTRL-Z to make it go away. It said "[stopped]", right? Someone came over to my machine and said, "Why in the hell are these (20 or 30) editors running in the background on the server?" Definitely one of my most embarrasing computer memories.

      I often wonder how fledgling sysadmins manage to survive.
  • For the impatient there is 'How to screw-up your system in 5 minutes'.
  • Does it have "Don't Panic!" written on it, in large, friendly letters?
  • by ACK!! ( 10229 ) on Tuesday November 12, 2002 @11:12AM (#4651258) Journal
    I read book on system administration and find them often times helpful in terms of putting together ideas of different ways to do things that maybe I had not thought of before seeing as I am the only big unix person in my org at the moment.

    However, I despise the title of these sorts of books. I know that other people have said it but you cannot learn something that is in and of itself a profession within simply 24 hours and the title itself is just silly.

    I feel that these sorts of books are almost a put-down to people that have spent years honing their craft only to find some dipstick book-maker claims that within a day someone starting from scratch could do the things I do.

    The hell they can.

    Note to the PFY of the world. Find a crusty old BOFH, be patient with them and learn slowly from them. No book, or certfication comes close to haing a good mentor when learning the craft of system administration. Not even close.

    ________________________________________________ _

  • by TTL0 ( 546351 ) on Tuesday November 12, 2002 @11:12AM (#4651264)
    The purple book [amazon.com] is all you will ever need.

    If you remember when it was a different color, consider yourself the BOFH.

  • by pizza_milkshake ( 580452 ) on Tuesday November 12, 2002 @11:13AM (#4651271)
    UNIX System Administration Handbook 3rd ed. [amazon.com] doesn't cover OS X, but it does cover Solaris, HP-UX, FreeBSD, and RedHat Linux. I believe the 2nd edition (1995) cover Solaris, HP-UX, IRIX, SunOS, OSF/1, and BSDI
  • by travdaddy ( 527149 ) <travo@@@linuxmail...org> on Tuesday November 12, 2002 @11:14AM (#4651278)
    Hm, I think I'll pass on reading this book, I'm waiting for Teach Yourself UNIX System Administration In 23 Hours.
  • by GodOfHellfire ( 113081 ) on Tuesday November 12, 2002 @11:17AM (#4651305)
    The job market is bad enough as it is - I, for one, don't want any extra competition out there.

    The last thing I need is my developers reading this book, then thinking they don't need me around any more!!
  • by Anonymous Coward
    Teach Yourself How To Stay Up For 24 Hours in 24 Hours
  • by emptybody ( 12341 ) on Tuesday November 12, 2002 @11:23AM (#4651348) Homepage Journal
    You can learn basic unix operator skills in 24 hours. You will not get real knowledge without spending considerable time in the trenches. More lessons have been learned working with real systems in real use than in the books.

    Want to learn fast?

    read ALL comp.sys.blah postings. Try to resolve them on your own.

    get some second hand UNIX gear (HP,DEC,SGI,SUN...) or some cheap PC gear (SolarisX86,RedHat,debian,freebsd,MacOSX...),build a LAN.

    make NFS/NIS/LDAP/DNS/SMTP/NNTP/etc. work on your new LAN.

    Read the documentation for each of your platforms.

    Compile and use all the opensource packages you can find. Start with GCC and the major gnu packages. Do not go the easy out pre-compiled route (compiler for first compiler excluded.)

    Make a NFS /usr/local to install all variants into. Make them work on each of your platforms.

    Add printers/scanners/disk/peripherals to each platform. Add any bit and piece that you can find.

    try to find EMC/compaq/netapp storage gear. make that all interoperate.

    make everything work with everything else

    Get on the help desk at a LARGE company or university and answer/resolve as many questions as possible.

    never stop learning.

    • Ummmmm (Score:3, Insightful)

      by Sycraft-fu ( 314770 )
      It sounds more like you are talking about "how to become an expert at UNIX sysadmining". Now if you are going to be an admin you should of course endevor for this BUT we all have to start somewhere. Being elitest about it gets people nowehere, we were all newbies at one point. the idea of a 24 hour book like this is to try and learn the basics.

      Of course experience is the real teacher, but it's hard to start from zero and get experience. You have to know SOMETHING to do anything, and a book is a great starting point. Initally, you know so little you don't even know what questions to ask and what to learn. Something like this can start you out.
    • An excellent list I must say and quite useful, however I think there is one important item that is missing...

      <sarcasm>

      • Head to your nearest merchant and pick up a case of your preferred adult beverage - this will be necessary for dealing with the endless number of frustrations you will encounter when learning to become a UNIX admin using this 'learn-by-doing' methodology

      </sarcasm>

      Truly, the list in the parent post is a good way to pick up these skills. But believe you me, it will cause some grief fumbling around trying to figure out the nuances of all the various types of systems and getting them to interoperate.

    • by bogie ( 31020 ) on Tuesday November 12, 2002 @12:04PM (#4651695) Journal
      That's one thing that absolutely kicks ass about the opensource nix's. Everything you need to learn about nix you can learn at home for free and run them on the oldest pc's you can find.

      I mean try learning windows 2000/exchange/SQL server on a P90 with 32MB ram. Not only is the software timebombed(You don't get to keep that now useful file/print/dns/proxy/firewall/blah server up running forever)but the hardware requirements are much higher.

      Plus these days even though everyone wants to talk about TCO, there is something to be said for being able to provide File/Print/DNS/Web/Proxy/Database/Directory software to your company for Free. Unless your working for the most diehard of diehard MS shops employers take note of that sort of thing.
  • 24hrs is good. (Score:3, Informative)

    by Inda ( 580031 ) <slash.20.inda@spamgourmet.com> on Tuesday November 12, 2002 @11:25AM (#4651363) Journal
    This sort of book does not try and teach you everything in 24hrs. It is expecting too much to think otherwise.

    I love the SAMS Teach Yourself stuff. The JavaScript and ASP books have been invalueble to me over the last few years. They are not reference books, although I have refered back to them many times. They are a starting point, a cheap starting point.

  • by macdaddy ( 38372 ) on Tuesday November 12, 2002 @11:38AM (#4651439) Homepage Journal
    ... the book " Teach Yourself Women in 24 Hours "? That's what we really want to know.
  • at least not in Canada [theregister.co.uk] (and kudos to them).
  • by techstar25 ( 556988 ) <techstar25@gmail.AUDENcom minus poet> on Tuesday November 12, 2002 @11:41AM (#4651462) Journal
    I have read several of these, and I have found that they offer a nice introduction to a topic that I'm not sure how deep I want to get into yet. So now I know a little bit about everything(operating systems, programming languages, etc) but I'm not an expert in any of them. Those books, plus a little creativity on my resume makes me look like the perfect guy for the job -every job(well at least entry level).
  • by Lumpish Scholar ( 17107 ) on Tuesday November 12, 2002 @12:19PM (#4651837) Homepage Journal
    When it comes to technical books, I look for a good publisher first, and a good author second.

    A good publisher can help a so-so author (by, for example, good editing, technical and otherwise). A really good publisher can return a rotten manuscript as unpublishable and refuse to distribute the darned thing. The publisher can only do so much, of course, but I wouldn't lightly underestimate how much.

    Any author, good or bad, gets a lot of value from the publisher. No book is perfect in the early drafts. A so-so publisher may often put out a very imperfect book.

    I've had a little experience (from both sides of the keyboard) with Sams at one point in its history. I don't feel they were a publisher that added a lot of value once the author's work is done. They may have gotten some good authors who put out some good books, but not as consistently as (say) O'Reilly. (I don't know how Sams is doing these days.)

    A couple of replies to earlier comments:

    "... In 24 Hours" doesn't mean "start at 9 a.m. Monday, be done 9 a.m. Tuesday." It means, "put in a couple of hours a day, be done in about a couple of weeks."

    Some people have complained this is an introductory book that's not very deep. Fine; it's not for gurus. It might well be a good book to read before reading the "purple book" [admin.com]; and that's not a bad thing.
  • In 24 Hours? Yes. (Score:3, Informative)

    by d1taylor ( 613599 ) on Tuesday November 12, 2002 @12:44PM (#4652060)
    Hi slashdotters. Just a quick note that those of you who are asking "is this book really sufficient for you to become an expert sysadmin": the answer is, of course, no. I'll quote the introduction:
    What This Book Isn't

    I'd like to state my intent with this book up front, while you're still browsing in the bookstore: This book is not intended to be the only system administration material you ever study. Indeed, this book grew out of a course I have taught, an introduction to Unix system administration. The reason for this distinction is because there are a number of very good reference works on administration (that typically run 800-1,100 pages) that offer a cookbook approach of "if this is wrong, do this to fix it." That's very helpful, and I have these titles on my reference shelf, but they don't teach you how to approach, diagnose, and solve problems the Unix way. That's a major goal for this book.

    When you finish exploring this book, you will know how to think like a good system administrator, regardless of what variation of Unix you encounter. You'll learn how to hypothesize about problems, dig through man pages and configuration files, postulate solutions, then test and verify that they've worked. And have fun in the process too!

    In the same vein, this book isn't 1,001 ways to fine-tune your Unix installation. In fact, we're going to gloss over the question of installation, because for most users the system is either already installed (like Mac OS X or Solaris), or has very good installation and configuration documentation. (Red Hat and Mandrake Linux distributions are standouts in this regard.)

    I hope that clarifies things. Other questions? Send me email, or, of course, post them here at off-topic chaos central, um, /.
  • Unix in 24 hours? (Score:3, Insightful)

    by kenp2002 ( 545495 ) on Tuesday November 12, 2002 @12:46PM (#4652078) Homepage Journal
    Great, just what I need, anohter 24 hours book. I remember once when a manager under me hired someone who learned programming from a QUE 24 hour book. He could code, but he sure as hell couldn't think. Just because I tell you how to do something doesn't mean you've LEARNED anything. Any kid can memorize how to DO sysadmin tasks, it takes an EDUCATION on how to IMPLEMENT AND USE what you've learned. Sorry but the DOT.COM area has ended and the BLOT.COM (Copyright 2003) era has begun. Time to go back to 4 year degrees (or 10 years of experience, I'll accept either) and suits. God I miss the days when computer professionals used to wear lab coats and could actually think instead of quote a useless text book.... sob....

    REAL QUOTE FROM A RECENT MCSE HIRE
    While working with a lacky on fixing an Exchange server we had to disable several features in the registry. When I ask him why he didn't disable the keys himself he said,

    "It never mentioned in the textbook how to do that."

    I would gladly take a smart recently converted AMISH FARMER over ANY MCSE that has been certified in the last 2 years. I can always teach a smart person what I need them to do (and hire them at a lower pay rate initially to boot! :) )

    Here is a simple quiz on how to find a SMART person. Use this!

    "A deaf and dumb (mute) man walks into a hardware store and wants to buy some nails. He approaches the store owner and places his left hand on the counter and starts pounding with his right hand, as if holding a hammer.

    The store owner gets him a hammer.

    The deaf man shakes his head and uses two fingers on his left hand and does the same pounding motion with his right hand.

    The store owner nods and gets several nails for the man to pick from. He picks two nails and buy a couple of boxes.

    The next day a blind man comes in. How does he ask for a pair of scissors? (What is you guess, think about it then read on.)

    Now if your employee makes a scissors motion with his hands I would move him (or her) to the bottom of the stack. Why? The man is blind, not mute, he would simple ask for a pair of scissors. It's this kind of INTELLIGENCE that is needed in the work place that isn't being taught in most schools. I did this test to several instructors at universities to see what kind of staff they had. Most fail. To give credit where credit is due I discovered this test in Issac Asimov's book "The Realativity of Wrong" when Asimov was presented with this same test from... his automechanic. Asimov failed also it seems (in his younger years). This test show that there is more to intelligence than simply memorizing and regurgitating information, it's listening and applying what you've memorized, something a Blah in 24 hours book cannot teach.

    P.S. No time for spell check. Later.
    • by Arandir ( 19206 )
      You're wrong about intelligence. Your story of the blind man is a *trick* question. Questions like these have been tricking geniuses for centuries. They prove nothing.

      The reason it is a trick question is because you spent four paragraphs talking about a deaf mute and impromptu sign language. You've prepared the listener to think "mute" when he hears "blind".
  • by Andrewkov ( 140579 ) on Tuesday November 12, 2002 @01:56PM (#4652783)
    Thank God for this book! I've been learning UNIX system administration for years on my own, but now in just 24 hours I can learn to be a UNIX guru! Where was this book all my life?!
  • by Wintermancer ( 134128 ) on Tuesday November 12, 2002 @03:49PM (#4653807)
    Honestly, my bookshelf is ready to collapse with number of administrative related books.But if I was trying to get someone up to speed realtively quickly, I'd recommend the following:

    Linux Administration: A Beginners Guide 2nd Ed. [amazon.com]
    Author: Shaw, Steve

    Really, the best migration book for Windows users to the Linux world that I've seen to date. Wide, but shallow, but that does not need to be bad. It's a good primer, but it does tend towards "cookbook" solutions. Get a deeper book once you've read through this. (3rd edition is due out in November, BTW. Makes a good Christmas gift to a Windows user that you know is trying to "covert")

    Linux Administration Handbook [amazon.com]
    Author: Nemeth et al.

    Opinionated. Polemic. A touch of arrogance, even. But this book and read it cover-to-cover. They obviously are biased against Windows servers. So will you after using *nix as well. Mine's dog-eared and highlighted to hell.

    Essential System Administration [amazon.com]
    Author: Frisch, Aeleen

    Dear God, if you don't own this, please go and buy it. Honestly, a definitive book on *nix. Twice as dog-eared and worn as Nemeth. You'll get this book when you pry it from my cold, dead fingers.

    Add a few specialty books to the mix, and you're more than set. Just read BOFH and develop the neccessary arrogant, anti-social attitude as you go ;-)

    Cheers.

  • Cool! (Score:3, Funny)

    by Col. Panic ( 90528 ) on Tuesday November 12, 2002 @11:34PM (#4656872) Homepage Journal
    I have a week off coming up during the holidays. I think I will buy a few of these and learn:

    Unix Administration in 24 hours

    Programming C++ in 24 hours

    Programming Perl in 24 hours

    Administering Oracle Databases in 24 hours

    SQL in 24 hours

    Then I'll take off the weekend. Maybe go sailing - yeah, that's it - I'll sail from Florida to California on Saturday and back home on Sunday.

The relative importance of files depends on their cost in terms of the human effort needed to regenerate them. -- T.A. Dolotta

Working...