Catch up on stories from the past week (and beyond) at the Slashdot story archive

 


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

Teach Yourself Unix in 24 Hours 250

Posted by samzenpus from the in-the-fine-tradition-of-home-dentistry dept.
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.
This discussion has been archived. No new comments can be posted.

Teach Yourself Unix in 24 Hours More

Teach Yourself Unix in 24 Hours

Comments Filter:

  • Good start... (Score:4, Insightful)

    by fak3r ( 917687 ) on Monday November 14, 2005 @01:46PM (#14028080) Homepage
    Sounds like a good start, but know that it'll only be a base to build on. As someone that has used Linux/*BSD/Unix for over 10 years, it's something that will provide a lifetime of learning. The challenge is what I love about it; think about it this way if you want to start with a book like this.

    • Re:Good start... (Score:5, Insightful)

      by ergo98 ( 9391 ) on Monday November 14, 2005 @01:51PM (#14028137) Homepage Journal
      Sounds like a good start, but know that it'll only be a base to build on. As someone that has used Linux/*BSD/Unix for over 10 years, it's something that will provide a lifetime of learning.

      Using and learning are very different things. There are people out there, right now - probably millions of them - doing software development the wrong way. They're implementing their small set of knowledge over and over again, for years at a time, not realizing how redundantly and incorrectly they're doing things (a great example would be the millions of developers squeezing out terrible database designs year after year - a particular vice of mine. Perhaps they'll imagine that they're expert database designers after a few years, but that couldn't be further from the truth). If they took a moment and actually learned for a few hours, it would make the implementation part much more effective, but people shun learning when they can just use what they already know as their hammer.

    • Re:Good start... (Score:5, Insightful)

      by Otter ( 3800 ) on Monday November 14, 2005 @02:08PM (#14028267) Journal
      The challenge is what I love about it...

      See, one day I was wrestling with a CUPS upgrade that broke printing and telling myself I was learning something in the process, when it dawned on me -- there are more rewarding challenges in life than fighting with a computer.

      To the degree that Unix makes my life easier, it's worth using. (There's a VNC window open now saving me from something that would be excruciating in Windows.) But using it to make life more difficult has lost its luster.

      • Re:Good start... (Score:3, Interesting)

        by fak3r ( 917687 )
        See, one day I was wrestling with a CUPS upgrade that broke printing

        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)

        by anicca ( 819551 )
        I've hit that a few times. My main computer is a bit of a challenge, getting hardware to work is a pain sometimes. I have found that windows may be easier to get things working, linux is better at keeping things working. I am in the process of switching away from MS...I'll be opening that virtual machine to do the odd windows tasks I cannot quite do in linux. I have been comparing them for years and I definately like my linux experience better. Best practice is to pick what works best for the task at hand b

    • Re:Good start... (Score:3, Interesting)

      by Golias ( 176380 )
      The funny thing is, yeah OS X has expanded *nix use, but not in a way that people will need this book.

      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 redun
    • As someone that has used Linux/*BSD/Unix for over 10 years, it's something that will provide a lifetime of learning.

      I recommend "Teach yourself Unix in 24 years", by the University of Life press...

  • work with someone knowledgable... (Score:5, Informative)

    by SlashSquatch ( 928150 ) on Monday November 14, 2005 @01:48PM (#14028110) Homepage
    ...if you can. There's no substitute.

  • It's on my bookshelf next to... (Score:5, Funny)

    by toupsie ( 88295 ) on Monday November 14, 2005 @02:00PM (#14028211) Homepage
    It's on my bookshelf next to Nuclear Powerplant Management for Dummies and Learn to Navigate Alaskan Bound Oil Tankers in 24 Hours. I hate these cheat your way to understanding book titles.
    • OK. So you are comparing Unix to nuclear power plants and oil tanker navigation?

      Jeesh, usually people on /. point out how anyone can learn *nix. Makes me long for differential calculus.

    • Marketing Titles Rejected By Publishers (Score:5, Funny)

      by Dystopian Rebel ( 714995 ) on Monday November 14, 2005 @02:11PM (#14028289) Journal
      The Hopeless Moron's Guide To

      The Shallow Unteachable Twit's Manual For

      Become Dangerous With Too Little Knowledge Of In 24 Hours

        For The Brainless

        For Assholes

    • Re:It's on my bookshelf next to... (Score:4, Insightful)

      by Overzeetop ( 214511 ) on Monday November 14, 2005 @02:18PM (#14028349) Journal
      You must not have see these 'Sams" series books before. I picked up a C++ version about 6 ot 7 years ago. 24 hours? Try 24 lessons which can be read and completed by the author in just over an hour each. They're freakin texts. I must say I haven't seen this one in particular, but if it's like the others I've seen, a good user without some prior understanding of the subject can figure that it will take an evening - 2-3 solid hours - to thoroghly digest each chapter...longer if you work most or all of the examples. It's only the title which makes it appear quick...a more apt title would be "Teach yourself Unix in less than a month if you don't have a life".

      • That being said, they are quite good texts.
        Its pretty well thought and explained to be able to teach yourself .

        In 24-hours? Not unless your a crazed, methampthetamine monkey with an IQ of 180 and a degree in speed reading, not too mention the ability to type ~200 wpm.

        More realistic would be 1-3 hours per lesson, 3-5 lessons per week.

        Each 'hour' in the book is one 'lesson', and there really is no reason to try and complete each lesson in one hour; far better to go over it and make sure you grasp it, and to just generally take it at a relaxed pace.
      • Just don't assume that it's good just because it's from Sam's; All the reviews for the Crystal Reports book say that it's awful, so I got something else. (Well, ordered. A week later and Amazon still hasn't seen fit to get it to me.)
    • My favorite actual, reall-and-truly existing, one is Catholicism for Dummies. I have a hard time imagining anyone taking that title seriously--it's either highly offensive or hilariously redundant, depending on your point of view.

  • time (Score:3, Funny)

    by karvind ( 833059 ) <karvind@[ ]il.com ['gma' in gap]> on Monday November 14, 2005 @02:02PM (#14028221) Journal
    I wonder if the book tells the reader not to use his watch and use unix command time [wlv.ac.uk] before he/she starts reading the book. That 24 hours may not be real or user time but sys instead.

    Just kidding :P

  • screw that book (Score:4, Insightful)

    by Anonymous Coward on Monday November 14, 2005 @02:03PM (#14028232)
    If you really want to understand unix you shouldn't get this book

    Some time ago I found an old text book for sysadmins written in 94.

    It skipped all that about guis and actually explained how to manage the OS via commandline.

    I had been using gnome for some time, but after reading that book I finally understood what all those scary commands meant when I configured my wifi card.

  • Step #1 (Score:4, Informative)

    by GillBates0 ( 664202 ) on Monday November 14, 2005 @02:03PM (#14028236) Homepage Journal
    % man man
    • Or better yet, the rather risque 'man woman'. ;)
    • "Dude, dude!"
    • When I got my first linux 1.x distro on floppy, thats what I did, I man'ed every command to understand what they did. After awhile you figure out what each is for, and read a few scripts, things just click. Looking around, poking your nose around the system, reading the man pages is the most important thing someone knew to unix can do.

      Couple things I hated about man pages.

      groff -Tascii -man
      Then you can read all those man files directly! (check /etc/man.conf for directories)

      Also, use man -a when you read,

    • Re:Step #1 (Score:4, Interesting)

      by DeafByBeheading ( 881815 ) on Monday November 14, 2005 @03:28PM (#14028950) Journal
      The thing is, as a novice *nix user who is very interested in learning more, I find this approach very limiting. Sure, it'll give you info on commands, but it won't tell you anything about how the system is organized. For example, my system has a nic that's unsupported by the default kernel. There is an open source driver available, but I was only able to get an old version to work by following a step-by-step guide that had you type in commands verbatim (using backticks where necessary), explaining very little of what was actually going on. The newer version doesn't work if I just follow the same steps. The forums have not been of much help. Learning enough to do this by manning would take ages.

      *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...
    • % man man

      Back in the old days, when men were men, and info was man...

  • Teach Yourself Programming in Ten Years (Score:5, Insightful)

    by Janek Kozicki ( 722688 ) on Monday November 14, 2005 @02:05PM (#14028246) Journal
    When people talk about books titled "ten yourself something in NN hours/days" it always reminds me about this [norvig.com] webpage.

    And in fact that's the truth - you can't learn that something in few days. Progamming? unix administration? sailing? playing chess? Man... that takes years to master.

    • Re:Teach Yourself Programming in Ten Years (Score:4, Insightful)

      by Petrini ( 49261 ) on Monday November 14, 2005 @02:15PM (#14028318)
      Sure, those things take years to master. But that's mastery. Does it take years to learn how to play chess? No. Does it take years to become a master of chess? Yes.

      Learning how to accomplish tasks like adding a user and its options is simpler and takes far less time than learning how to write 'adduser.' Evaluate the book on the standard it sets for itself: learning how to do things. Don't judge it wanting because it doesn't teach the entire universe of how unix works.
    • At the totally awesome BudUglly web design page: http://budugllydesign.com/archivebud/bud9609/bud.h tml/ [budugllydesign.com]

      Seriously check it out, I laughed for an hour at this site.
    • As you said it takes years to master something. Let me point out; to learn something to get the basic idea/rules is different than mastering something. For example: I for one learned how to play chess in a couple hours. Does that mean I mastered playing chess in a couple of hours? NO of course not, but I do have the basic rules down to allow me to play chess.

      Your sentence should read more like this: "And in fact that's the truth - you CAN learn that something in few days. Programming? UNIX administration? s
    • What if you just want a functional knowledge? There's nothing wrong with that, nobody can be a master at everything, in fact most people can't master more than one thing. However that doesn't mean that they want to have NO knowledge.

      Or what about if you work in a very related discipline and want to get some introductory knowledge? For example a Windows admin that is good with computers, troubleshooting, and so on but only has done it in a Windows domain. What they need is a primer to UNIX so they know where

  • insulting? (Score:4, Insightful)

    by tomstdenis ( 446163 ) <tomstdenis@gmai l . com> on Monday November 14, 2005 @02:07PM (#14028262) Homepage
    I find all these "$THING for $PEOPLE" and "$THING in $QUANTITY of time" books insulting.

    Sure you can learn how to type "cd /usr/bin ; sudo rm -rf *" in 20 minutes. Can you learn to develop and debug shell scripts in 24 hours? I think not.

    Nor do I think people can learn C or C++ or Java in 24 hours. It's just insulting. Now I know they don't literally mean one day, but even college classes run longer than 24 hours. In college you'll have a 50-60 hour class on "intro to C" followed by FIVE MORE SEMESTERS of classes that build on it.

    I hate these books because they're retarded. I learned C primarily from "type and learn C" [I think by Sams] when I was 12. Then I proceeded to actually write programs [lots of them, 1000s of them]. I learned by doing and it took a long time. I wasn't half-way decent at "coding" until I was 19 and I'm just getting solid at proper development [well I'd say the last year has been really smooth].

    For all of us who do take it serious and have been through a lot of training I find these books insulting. And no, it isn't because I sunk a boatload of cash into the courses like a MCSE. I think people are quite capable of teaching themselves how to use UNIX shells or C programming. I just don't think it's the sort of thing you can do over a weekend or two.

    So fuck off already with the books that serve no purpose but to flood the market with a lot of "smart" people who turn out to be useless as the day is long.

    Tom

    • Re:insulting? (Score:5, Insightful)

      by skribble ( 98873 ) on Monday November 14, 2005 @03:10PM (#14028800) Homepage

      dude, lighten up...

      "Can you learn to develop and debug shell scripts in 24 hours? I think not."

      What does this have to do with a book designed to get new users familiar with using Unix? (which BTW the book in question is designed to do?) I would add, that yes you could learn to develop and debug scripts in 24 hours if you were so inclined, you might not be any good at it, but you could learn the basics.

      The purpose of this book and other like it are to teach the reader the basics of doing something, and overall they tend to do this fairly well. Nowhere do they say that you will gain 10 years of experience in a book.

      "In college you'll have a 50-60 hour class on "intro to C" followed by FIVE MORE SEMESTERS of classes that build on it."

      That statement seems to reflect more about your ignorance and some of the problems with higher education then actually making a valid point. The main text on the C language is "The C Programming Language" by Kernighan and Ritchie. I quote from the book "C is not a big language, and it is not served well by a big book." The book in question is less then 300 pages... easily worked through in a week or so (and could possibly be absorbed in 24 hours as well). And while this book isn't going to teach you every library and algorithm necessarily to create many outstanding applications, This book will in fact teach you the C language pretty much in it's entirety. (After all all the extensions and libraries are essentially built out of the these very basics taught in this book).

      So if you must, be insulted. I don't think too many people on Slashdot really care (and seriously who hasn't been insulted by something on Slashdot at one time or another). But you arguments just point out what are apparently your own shortcoming and misunderstandings about anything. I mean anyone who states "I hate everything that ..." without exploring everything you supposedly hate represents the height of ignorance.

      • If you're calling me a degree-snob you're way off base there. First off I went to COMMUNITY COLLEGE. Second, I'm largely self-taught in all of my prefessional endeavours [though I did take a 3 yr comp.sci program to ensure I have some formalism behind what I'm doing and I have had experience with subjects I may not have taken a liking too on my own].

        My point about bringing college into this is sometimes you have to be told what you don't know you don't know so you can later know what you don't know and th

    • I don't think anyone is trying to fool himself that after 24 hours of study he can be an expert in UNIX, or anything else for that matter. What these books do offer, however, is a kind of boot camp for autodidacts. The "24 Hours" are more a measurement of the minimum time that one would have to devote to study in order to get even the most elementary concepts.

      Once you've gotten your head around the basics, the hope is that you can go on to more complicated and satisfying tasks. But the main thing is to e

    • Type and Learn C (Score:2, Insightful)

      by a1ok ( 250188 )
      'Type and Learn C' (iirc, by Tom Swan) was a really good book, it helped me a lot too when I was initially exploring the language. That and the online help in Borland's Turbo C++, which imho was highly impressive. OTOH, I also bought 'Type and Learn C++', but that was quite a disappointment - the entire book was an ongoing exercise in making an editor, so I couldn't jump from chapter to chapter as I wished, and due to several other things didn't get utilized remotely as much as the C book.

      I do like the '24

  • Hit TV series on the way? (Score:5, Funny)

    by saskboy ( 600063 ) on Monday November 14, 2005 @02:09PM (#14028277) Homepage Journal
    24 Unix!

    It would be modeled after the hit American TV series with Mr. Sutherland in it. He'd have just 24 hours to learn Unix, or a bomb goes off yadda yadda. Each hour of the show would show him at the command line, or trying to get X Windows running, and about hour 15 someone should show him a Linux Live CD and nearly save the day.

    It could be shot under the BSD license, and run on either a Mac or Intel processor, depending on what they'd think would get better ratings.

    Any TV producers out there want to buy the rights to my idea?

  • "Teach Yourself UNIX in a week" - by same author (Score:5, Funny)

    by Animats ( 122034 ) on Monday November 14, 2005 @02:13PM (#14028306) Homepage
    The same author also wrote "Teach Yourself UNIX in a Week" [amazon.com].

    But he's way behind on speed. The current record holder is "Teach Yourself UNIX in 10 minutes". [amazon.com]

    You may also need "Advanced Speed Typing" [letterchase.com] and Carpal Tunnel Syndrome Treatment [nih.gov].

  • The Difficulty (Score:5, Informative)

    by miyako ( 632510 ) <miyako@gm a i l . com> on Monday November 14, 2005 @02:16PM (#14028334) Homepage Journal
    I think that the biggest difficulty that a lot of users have when transitioning from working with the GUI to working with the command line is the fundamental difference in the way that the two operate. The biggest difference as I see it is that the GUI is good at performing 1 operation at a time on an arbitrary set of files. The command line on the other hand seems to be most useful when you want to perform many tasks on a single file, or a group of files like *.txt or foo*. For many things on the command line there is no real anlagous way to perform the task with a GUI.
    The problem is that many people who first start out with the command line seem to view it as more of them having to simply type in obscure commands to correspond to the same steps they would take were they using a GUI. I've seen many people type:
    cd /home/myusername/foo
    ls
    cp foo.txt /home/myusername
    cd /home/myusername/
    mv foo.txt bar.txt
    cd foo
    rm foo.txt
    instead of simply typing mv ~/foo/foo.txt ~/bar.txt Of course this is a simple example, but I think that it illustrates my point that people are often locked into the GUI mindset. As such, even if they understand in the abstrace the use of piping and output redirection, etc, the difficulty is in understanding how to use those tools efficiently.
  • the only command someone who needs this book should know is shutdown -g0 -y.

  • I quit Sam's years ago (Score:4, Interesting)

    by Hosiah ( 849792 ) on Monday November 14, 2005 @02:19PM (#14028356)
    As the well-known tech author Peter Norvig noted, you won't learn but diddly in 24 hours (my wording). In fact, I daresay that Unix is not a topic one expects to learn completely in *any* finite length of time. Instead, one must stroll to the heftier material (like "Unix: the Complete Reference" that McGraw-Hill publishes) and take it home for a few dollars more. You keep it on hand as an on-going reference source.

    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.

  • Step 1: rm vwls -r (Score:5, Funny)

    by G4from128k ( 686170 ) on Monday November 14, 2005 @02:29PM (#14028447)
    When trying to remember commands, step one is to remove all the vowels.

    I don't even want to think what Unix would have been like if it had been created by Finns or Hawaiians.


    • > I don't even want to think what Unix would have been like if it had been created by Finns or Hawaiians.

      I recall hearing something about a Finnish student dabbling in creating his own Unix back in the early 90's... named Linos or something... anyone know if he had any success with that? He could call it "Finnux" or something...
    • When trying to remember commands, step one is to remove all the vowels.

      Riiiight.


      lst -l | glbllysrchfrrglrxprssnsndprnt -i budget | srt | mr

      Yeah, that worked well. Yes, there are vowels missing in several, but like english, there seems to be more exceptions than rules...

  • My problem with "learning Unix" (Score:5, Interesting)

    by TheReckoning ( 638253 ) on Monday November 14, 2005 @02:34PM (#14028490) Journal
    ... whatever that means, is this. I need a high-level description of how Unix works. I have a reasonable handle on how Windows works (at least on a conceptual basis), so if I run into a problem or would like to get something done, I have an idea the kind of tools I need.

    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.

    • There are many books about UNIX internals. (Score:4, Informative)

      by CyricZ ( 887944 ) on Monday November 14, 2005 @02:50PM (#14028638)
      You need a book such as "The Design and Implementation of the 4.4BSD Operating System". I believe there is a more recent edition which focuses on FreeBSD. There are many other books out there, too, focusing on the internals of systems like Linux, Solaris and OpenServer.

      They explain how each portion of the system works, in addition to how they work together. And then they explain exactly why.

      You should be able to find such books at a university bookstore.

    • I'd recommend a book from O'Reilly Publishing entitled "Running Linux". Another good book is "Linux Power Tools" by Roderick W. Smith.
    • I do Windows support as a major part of my job and at this point I'm pretty good at it. I find that when a problem happens, I know how to troubleshoot it, what to look for, what to try and change, and so on. It's rare I encounter a Windows problem I can't solve pretty quickly, and I never seem to get perminantly stuck.

      Not the case with UNIX. Now it's ok, I suppose, UNIX isn't my job, but I won't necessiraly have this job all my life and it'd be good to learn. However I know the basics, I don't have any trou
    • Well, if no-one recommends a good title, maybe I should work on one. I think it's actually pretty simple. I can give you the highest level outline in two sentences:

      The BIOS (also called "boot prom" on some systems like Suns) loads a bootloader (one of GRUB, LILO, SILO, etc.) which loads the kernel which runs a special program called init. Depending on the flavor of Unix (System V vs BSD types), it either reads /etc/inittab and executes scripts found in there, or starts executing the script /etc/rc.

      So, once

      • So, once you can read shell scripts, you can follow the whole chain of system startup from there.

        I second this; after you learn some of the hows and whats, it's quite straightforward to learn about the whys if you need to. I started to use Linux out of pure geek interest, plus a frustration with Microsoft products, and I rarely think about the grand design philosophies.

        I find it interesting that the grandparent asked about the "deep" things in unix, because I've always thought Windows is all about hid

        • Well, I think part of it comes form what you are used to. I do not find Linux easy to use, I find I do not know how to fix it when something goes wrong. Unless it's a fundimentally different kind of problem solving, the problem is a lack of understanding. I have a real understanding of Windows, partly developed through using it, but the deeper understanding was developed through some good books. "Windows Internals" will give you a wonderful rundown of how Windows actually works. I think I need something lik
    • 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.

      Wow! You're a born Unix person. Really. Windows was made for people who don't care how it works, Unix was made for people who do. You're a perfect fit.

      Unfortunately, the current crop of Unix advocates are too busy trying to shield the potential newbie from the "why" to realize how important it really is. If the "why" scares the newbie, then they're not a good fit
      • First of all, it's tldp.*org* [tldp.org]. Second of all, many, many HOWTOs are absurdly out of date. Sure, there is good stuff there, but, for example, a search for dual-boot first turns up results on how to dual boot Linux with Win95/98/ME, complete with instructions for the complicated partitioning needed to get around LBA boot limitations (presented not as "oh, and this is what you need to do *if* you happen to have a bajillion-year-old machine," but as "oh, and this is what you need to do because it's a limitation

    • Re:My problem with "learning Unix" (Score:5, Informative)

      by multipartmixed ( 163409 ) on Monday November 14, 2005 @04:10PM (#14029358) Homepage
      > How does **nix boot?

      The hardware runs a program. That program loads the kernel and executes it. Any more specific, and you're now talking platform-specifics which don't have to with UNIX.

      For example, Linux on a DEC Alpha might boot like this:
      - Windows NT ARC loader configured to spawn program MILO.EXE on FAT-formatted disk in Drive A:
      - MILO.EXE understands Linux ext2fs, and launches the kernel wherever the Windows NT ARC loader's environment variables tell it to find it. (Hint - it's faster if you point it at a harddisk). The kernel is generally called /vmlinuz is a gzip-compressed Alpha ELF binary. (Or is it COFF?)

      Another example, Solaris on a SPARC box might boot like this:
      - The EEPROM stores the identity of the boot partition
      - The PROM loader goes looking for the boot blocks (installboot (1M)) on that partition, and executes the code it finds there
      - The software just executed understands the Unix Filesystem (UFS), goes looking for the kernel where it belongs (set by the installer, I forget where it's written down). Traditionally, it was /vmunix, now it's somewhere else.
      - The kernel looks in /etc/path_to_inst to figure out what device drivers to load, and loads them.

      Solaris on an x86 box boots pretty much like windows.
      - The BIOS goes looking for the first "active" partition, as marked by the disk partitioning utility. Generally on the first IDE controller's master disk.
      - The BIOS executes the code in the master boot record (MBR), which somehow winds up loading the boot blocks.
      - The software just executed understands the Unix Filesystem (UFS), goes looking for the kernel where it belongs (set by the installer, I forget where it's written down). Traditionally, it was /vmunix, now it's somewhere else.
      - The kernel looks in /etc/path_to_inst to figure out what device drivers to load, and loads them.

      > How does it interact with hardware?

      Same as any other operating system; through the PCI/ISA/etc bus and the API implemented by the hardware.

      > Is there a general hint to what all the directories are
      > about or any memory aids for knowing what's in them?

      Keep in mind, UNIX is not Windows. Generally speaking, you can put anything anywhere you want, as long as you change everything which cares about it. Which is usually possible!

      Keep in mind also, that nothing is absolute. /etc - misc OS crap that doesn't have a defined place. Generally config files /etc/inet - Like etc, but for networking stuff in SYSV. Generally linked to same-named files in /etc to be compatible with BSD. /var - Theoretically, for VARs. Nothing much officially lives here, except log files (/var/log, /var/adm on Solaris). Oh, and also spools (/var/spool/mail, /var/spool/lp, etc. Lp stands for "line printer") /opt - OEM or Third party packages on SYSV boxes, esp Solaris. /usr - Apps and stuff that came with the OS /usr/bin - Binaries for anybody to run (executable prorgrams) that should be available all the time. /bin - Like /usr/bin, but more OS-centric/important /sbin - Like /usr/sbin, " " "/" /usr/sbin - Binaries for super users /usr/local - Addons which are local to that box /usr/local/bin, sbin, etc -- Local to that box, but have /bin, /sbin, /etc functionality

      > Permissions - any chance of an overview of what the bits mean,

      Permissions are most useful to examine as four-digit octal numbers. Assign each octal digit as such: SOGW

      S - Special stuff, like sticky bits. Almost always 0
      O - Permissions for the file owne
    • Well, a lot of it is culture--you absorb this stuff over time.

      I'm not sure what you mean by asking 'how does Unix boot?'; on a PC the BIOS boots Linux or FreeBSD essentially the same way that it boots Windows: searches the known drives for a boot loader and runs the first one it finds. Of course, the Unix boot loaders typically offer more features than the Windows boot loader.

      Likewise with most of the other questions, actually. Perhaps if I grokked what you're asking better I would have a better idea

    • How does **nix boot?

      I only really know how Linux boots at an overview, but other *NIX systems may be very similar. There is something called a "boot loader" that sits at the beginning of the boot disk and points to the Linux kernel. The linux kernel then takes over the machine in terms of getting an inventory of the hardware attached on the computer and initializing the device drivers and the devices. It then looks for /sbin/init which then brings up userland processes (GUI shell, bring up network, login

    • Some others have given some really good explanations on most of these questions, I'll try explaining a little more about the way the system deals with hardware.

      The operating system kernel is this part of it that runs all the time and takes care of the scheduling of the various processes and of servicing the requests that these have for access to disks, keyboard, mouse, screen, serial ports, network ports, printers and so on. Since there is a lot of different varieties of these, the operating system uses

  • 24 hours is nonsense. I'd say 24 days for the basics and 24 months for a better mastery of the basics is a more reasonable estimate. Unix is *not* KDE and how to burn a CD or play a game in KDE. Unix is posix, bash, sed, awk, perl, vim, and so on.

  • Who Needs a Book?! (Score:4, Funny)

    by Comatose51 ( 687974 ) on Monday November 14, 2005 @02:41PM (#14028546) Homepage
    Conversation between me and friend:
    Me: What else should I put on my resume?
    Friend: Can you use grep?
    Me: Yeah kind of
    Friend: Bam! Instant Unix admin!
  • ...had it been titled "Unix: Dummy to Diletante in 24 Hours."
  • ...is free on the Net. Introduction to Linux: A Hands-On Guide [tldp.org] at the Linux Documentation Project. Print the PDF, save a trip to the bookstore. Doesn't assume (much) prior knowledge, yet omits all the trivial "Here's how to burn a CD in K3B" nonsense.

  • Sometimes all people need is a little push to get them started. If all that book does is to effectively intro some commands and some ideas into the head of someone who never used unix, I think it is sucessful.

  • Most of the replies to this article go something like "You can't learn anything in 24 hours" or "If you use this book you shouldn't use Unix". The first type of reply is valid, but this review points out in several places that this book is useful as a reference guide, not just as a lesson-based learning method. And "Learn $THING$ in $TIME$" is a whole lot catchier and more profitable than "Figure It Out Yourself". Everybody needs to start somewhere, and for some folks, getting a book that will get them t
  • 24 hours? Meh. I think everyone should wait and buy my upcoming book "Teach Yourself UNIX in 23 Hours". I mean, when you see both of them on the shelf, right next to each other, you're definitely going to buy the 23-hour book. Why waste that extra hour?!?! Right? *

    * theme of this joke shamelessly stolen from the 8-Minute Abs vs. 7-Minute Abs scene in "There's Something About Mary"
  • I'm holding out for "Teach yourself neurosurgery in 24 hours".

  • I found the third ed. useful. (Score:3, Informative)

    by spasticus74 ( 859477 ) on Monday November 14, 2005 @04:17PM (#14029413)
    I bought the third edition in January 2004 when I started a new job with a Unix/Linux company. I found it very easy to get up to speed quickly, which is a testament to the quality of the book as my previous *nix experience was measured in minutes. I particularly appreciated the way it compared and contrasted *nix with Windows as that's my background. It won't teach you everything but it covers the basics and will get you working pretty well straight away. As noted above to become really effective you should get help from someone with a lot more experience, but this book will introduce most *nix concepts.
  • ...maybe he should be reviewing "Teach yourself mixed metaphors in 24 seconds"

  • learn %s in %d days (Score:3, Insightful)

    by sohp ( 22984 ) <snewton@iCHICAGOo.com minus city> on Monday November 14, 2005 @09:20PM (#14031526) Homepage
    From "Teach Yourself Programming in Ten Years" [norvig.com]
    "I did the following power search at Amazon.com:

              pubdate: after 1992 and title: days and
                (title: learn or title: teach yourself) ...
    The conclusion is that either people are in a big rush to learn about computers, or that computers are somehow fabulously easier to learn than anything else. There are no books on how to learn Beethoven, or Quantum Physics, or even Dog Grooming in a few days."

Slashdot Top Deals

He who has but four and spends five has no need for a wallet.

Close