Slashdot Mirror
Learning Unix for Mac OS X Panther
This book focuses on those of us in the Mac OS professional world who have become Unix system admins by default with the introduction of OS X, and could stand to have a handy UNIX reference nearby, particularly if the Finder freezes in Apple's latest version of their BSD/OpenStep blend of a UNIX operating system.
As the authors explain in the book, the best justification for understanding and using the UNIX components present is Mac OS X is the same as in any other UNIX-family operating system: power and control. The Finder (Mac OS X's graphical desktop manager) can't do everything, so this book provides information to help power users and technicians resolve issues, install software, or create an optimized experience, all through the Terminal.
Chapters 1 and 2 provide a very helpful tutorial on the Mac OS X Terminal application, from showing the benefits of customizing the Terminal, the concept of shells, UNIX command syntax, and other obscure but useful settings that strengthen the power of the application when accessing the BSD innards of Mac OS X. Arguably, these two chapters are the strongest guide on Mac OS X's Terminal application (as it relates to its UNIX roots) that I have seen in any Mac OS X book to date.
Chapters 3 and 4 handle understanding of the UNIX filesystem, administration and superuser access, privileges, handling external volumes, file and directory names and the like. Mac OS X, while a BSD at heart, doesn't map out everything in a traditional UNIX-style directory format--at least, not from the Finder's view. Through the Terminal, a user can see the underlying, otherwise-hidden UNIX directories. The authors go through some basic but very helpful situations such as changing file and owner permissions, which can be changed from the Finder with greater ease in Panther, but not with the same finesse as done from a command line.
The file management chapter moves readers through the classic commands for moving, editing, and copying files from the command line, which can be very helpful for administrators of Mac OS X systems who must attempt repairs by SSH, for instance, and don't have access to the usual graphical elements that generally make Mac OS usage so easy. The authors don't pick sides in the vi vs. pico debate, and just offer the basic instructions on how to use either for your editing.
The book continues with the same level of complexity that local system admins or power users require in issues such as printing via CUPS, handling processes that the Finder doesn't show, using the X11 application, using Fink (a Debian-style installation application) installing OpenOffice and GIMP, using FTP and secure shell, using Pine and Lynx, and more.
For a book of just 168 pages, the authors pack quite a bit on making a Mac OS X system work from its Terminal roots. New Mac OS X system administrators will find this book most useful, particularly if their UNIX experience is lacking or radically different from what Mac OS X presents. Experienced *NIX users who bought a new Mac may find the book a good intermediary to demonstrate how Mac OS X Panther differs from the *NIX boxen they've used in the past.
You can purchase Learning Unix for Mac OS X Panther from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
How does that help you if you don't know what command you need to use.
Win a signed Stephen Carpenter ESP Guitar from the Deftones: http://def-tag.com/?r=0008781
Heh, I'm a pico user but I'm not a zealot over it. I use pico when I want to do some simple, quick editing in the command-line environment. For anything more complex I use BBEdit, which does pretty much everything that vi or emacs does except with a nice GUI.
But hey, use whatever works for you. Vi is certainly powerful enough. I just can't be bothered to take the time to learn all the commands, vi has a pretty high learning curve.
Sapere aude!
In the end, the terminal is just another tool on your system. Just because someone works mainly with a GUI doesn't mean that they are not able to comprehend the command-line. Yes, the first couple of times that someone uses the command-line they are going to make some dumb mistakes but if they have a decent guide then those mistakes can be kept to a minimum and have minimal negative impact.
You might as well say that it's not worth if for a person who has never programmed to learn BASIC or C. If they don't take the first steps then how do they learn in the first place? If you are going to do anything on a computer you have to start somewhere, no matter if you are used to a GUI or not.
Sapere aude!
Then how are they suppose to learn if we don't teach them?
52 Weeks, 52 Religions with John Hummel
What is wrong with paying a few bucks to replace a brand new mouse that came with the system you just paid a couple of thousand dollars for?
That statement would ensure the death of the command line wouldn't it? I don't see many schools these days offering anything but Windows and Macs for students to learn on.
Well done, mister tar-everybody-with-the-same-brush. I fucking hate people trying to categorize me based on the fact that I use a Mac.
I don't own one because I want to join some elitist club of "creative professionals", I don't own a Mac because I think that it's somehow screwing Microsoft, I don't own a Mac because it has a candy-coated GUI, I own it because it has a solid and proven operating system derived from openstep and because it came properly set up for the hardware inside. Which for me is a prime consideration when buying a laptop.
Maybe the next laptop I buy will be x86 and Linux based again (this machine has had more than it's share of hardware failures) but OS X has always been rock solid for me, and the drivers and power management have always worked as they should, which is more than you can say for most x86 laptops even when running the OEM setup.
To me, it's just another Unix system on another flavour of hardware. Would you be telling me that I shouldn't be playing with the command line if I'd bought a SPARC laptop?
In my experience I've seen two types of large Mac user communities
(1) Mac users who want a simple OS, that is easy to use. They are not computer savvy and just want to use their machine to get the job done
(2) Unix / Mac users who hated Microsoft Windows for being neither powerful/stable nor simple/elegant to use.
Many of the people in the category (2) probably gravitated towards OSX quickly when it came out. People in category (1) waited for all their essential applications to be ported, before being forced to upgrade.
-Diganta
It's only after years of experience with other operating systems, other computers, that I made the decision to switch to a Mac. Mac users I find can be very technical, just 'differently technical'. Technical doesn't mean "knows *nix". Maybe here, but not in the rest of the big wide world. . .
Curious about other writing I've done? There's some useful free info online at 404 error page, particularly for Apache admins, and another book that slashdotters will appreciate is my Wicked Cool Shell Scripts. And, yes, Virginia, the latter includes specific scripts for Mac OS X too.
I've been using Mac OS since 7, and never really used anything else (natch...I've always been in design or print production). I had to plink around in some VERY basic UNIX commands for a general computer science class in college, so I know some basic navigation and a few commands.
I have no interest in running anything but a Mac system, even just for fun, because I don't find the thought of not knowing how to do anything fun. But I'm not so stupid as to think that I can do everything I need to do in Mac OS. I've read enough tips and cool hacks and neat ways to make things work by using Terminal, that I know it would behoove me to know something beyond to basics.
If they were so inclined, they'd already have some experience on another OS by now.
So, I say BS to this. I'm inclined to learn some rudimentary stuff, but no way in hell do I care to, no imagine I could be productive in, anything else. This book sounds perfect.
You know what?
I think it's important that MAC OS X users learn to use the UNIX command line. Even if they don't like it, they need to respect it. If it wasn't for OS X being powered by UNIX, it would not be anywhere near as stable as it is right now. I'm not "dissing" OS X, because I use it and love it, but any user shouldn't be without the knowledge required to run the UNIX command line.
Why? Why would my parents, who only do application level stuff (web browsing, word processing, email, games), need to learn the "power of Unix"? They're non-technical end-users. They aren't concerned with harnessing the power of their machine, and nor should they have to be.
Just so you know, the convention of /Applilcations and /Users is from NeXT, and makes logical sense when you think about it. All the unix tools are located in their standard directories (/usr/bin etc etc) but a good chunk of users aren't going to use them, they're going to use their GUI apps and such. Why would you want to put all your terminal apps in the same folder that your GUI apps are?
/usr/bin, if I added them to my Applications folder, I'd have 700 items in my folder. Now as a (hypotheticaly) non CLI familiar user, why would I want to have 700 items in my folder where I put my programs when I don't use most of them? I wouldn't. So maybe I might start deleteing them, or maybe I'll make folders to organize them, or move them. And then what? What happens when I install an app that calls those programs?
I have 644 items in
That's why there's a user level set of folders that aren't the standar UNIX convention.
T Money
World Domination with a plastic spoon since 1984
Where does this perverse notion come from that GUI users are inhernetly incapable of using a command-line?
There's a deeper cultural thing going on here. On this site it's not uncommon to see programming-types bash (pardon the pun) users of more graphically-oriented tools (like Flash) with incredible zeal. It's as if there's some sort of Berlin Wall between creative and techinical people, and any attempt to bridge the two is doomed to failure or must be opposed.
This is nonsense.
This seperation of arts & humanities from the sciences is a relatively recent phenomonon. It's when people work with both sides of their brains that beautiful things really start to happen. Look at Leonardo Da Vinci if you want the best example. Look at the power of tools like Flash when you get people working on it to use its more powerful features like XML parsing with ActionScript, remoting, video etc. Look at musicians who can manipulate their creations electronically. Look at the animators who produce beautiful work on the big screen like Finding Nemo, Babylon 5 etc.
A lot of creative Mac people will benefit from having a deeper understanding of the way their command-line works, and if they're approaching it from a different angle than traditional Unix fans then so what? Isn't a fresh persective a good thing? Likewise I think that a lot of Unix fans could do well to visit more art galleries and explore their creative side a bit more. It may make better programmers out of them.
For the record, I work on both sides of the fence and do an equal amount of creative and technical work.
Drill baby drill - on Mars