Domain: macosxhints.com
Stories and comments across the archive that link to macosxhints.com.
Stories · 17
-
Windows Vista Beta Running on a PPC Mac
goombah99 writes "Macosxhints is giving a set of tips that let any Mac user boot Windows Vista on a Mac. In this case, it's not a native Intel boot but rather VirtualPC running on a PPC G5 Mac. Thus Vista and Mac OS X can run concurrently. There are no extravagant hacks needed, just a matter of finding the right set of configurations to let VirtualPC present the proper disk images for mounting and BIOS settings to the installer. This bodes well for native installs onto the Intel Mac." Actually, there have been successful (though not glitch-free) installs of beta versions of Vista on Intel Macs for a few months now. Here's a report from Hans Verbeeck (Developer Evangelist for Microsoft EMEA) on putting Vista Beta 2 on a MacBook Pro. -
Apple's First 2005 Mac OS X Security Update Is Out
ollie_ob writes "Security Update 2005-001 has just hit Software Update for Mac OS X users, for those running 10.3.7 and 10.2.8 in both normal and server flavours of the OS. The update includes patches for: at commands, ColorSync, libxml2, Mail, PHP, Safari and SquirrelMail. Details are here. One of these fixes -- a modification to Apple Mail so it stops broadcasting your MAC address in plain text every time you send an email - will come as a welcome relief to those trying to keep their WEP-based wireless networks secure. Other highlights are PHP 4.3.10, and a Safari fix so that pop-up windows can't mislead users as to their apparent origin. The Mac OS X Server version of the patch also includes an update to SquirrelMail that stops browsers from executing scripted content in emails viewed(!). Interesting to note Apple's new naming scheme for the updates (last year, some updates came out dated days into the future - or past.) Also, there's a unified page for all future security updates." -
Review - Mac OS X Server 10.3, Part 2
In yesterday's article, I gave an overview of Mac OS X Server, and described some of the features. Read on for some detail of the specific services that Server offers, and the final verdict.AFP
The first thing I wanted to do was get file serving up, so I selected AFP (Apple Filing Protocol). My files are all on an external 160GB FireWire hard drive. Photos, (legal) MP3s, tons of (legal) file archives, (legal) games, (legal) movies (I swear!). I am usually the only person who needs to connect via AFP, but sometimes other people do, so I want to make sure I set it up the Right Way.
I quickly discovered that Server Admin does not grant control over what is being shared, and with whom. For this, I must venture forth into Workgroup Manager, and set up a Share Point, and define who has access to it. It is fairly intuitive, and a few minutes later, I set it up and am back in Server Admin, where I make sure Rendezvous registration is on, and allow idle clients to sleep for a long time before being disconnected (good for my PowerBook, which is often asleep). I clicked "enable secure connections" and "enable administrator to masquerade as any registered user."
The masquerading is a neat feature: it allows me to type in any user's name and my admin password, and be logged in as that user. It's not something I'd use often, but it could be handy. Some have complained that this is a security hole. If you think it is, then make good use of that checkbox. Note that this is on by default in Client, where there is no apparent way to turn it off.
To turn on the AFP service, like most of the services, I then clicked the green icon with an arrow in it at the top of the window. When it turns into a red button with an X in it, the service has started; to turn it off, I can click the red button.
AFP in Server as the same as what is in Client. The only difference is that in Server, you have many more options for configuration and control of the service. Last I checked, you could do some of this configuration manually in NetInfo, but it is not for the weak-hearted.
And, as mentioned in the last article, the $500, 10-client version of Server is limited to 10 simultaneous clients on AFP. To get around this, pay double for the unlimited version, or use plain old Panther Client.
MP3s
I wish there were a lightweight music server built-in to Server, one that could use less RAM and CPU, that would just serve MP3s. Alas, there is not. So, I set up iTunes for my music sharing. I won't bore you with the details, for more boring details are yet to come.
And heck, now that iPhoto can share too, it'd be nice to have a photo server as well. What I'd really like to see is the ability to modify the photos via sharing, so I can keep them on the server but manage them with my laptop. I'd also like to download MP3s and use shared MP3s from iMovie and iPhoto. But this is not an iLife review, so I shall move on.
Print
To be blunt: Printer Sharing does not work as I need it to -- as it does in Client -- and it is by far the biggest headache with Server, and almost enough, on its own, to make me revert to using plain old Client.
I have two printers to share: a Canon S820 USB inkjet printer, and the internal fax modem. As you may not know, you can share the fax modem in Panther. Just make sure you have printer sharing on, and that you use your fax modem once to "create" the "printer." It will be shared with everyone else on your network just like any other printer, showing up in the "Fax List" in Printer Setup Utility, and in the "Shared Faxes" popup in the Fax dialog box.
That is to say, all this happens if you are using Client to share your fax modem. This does not work if you are using Server.
Nor does the regular USB Printer Sharing work. Server does not use the same mechanism for sharing. The only way to share my printer with the Clients is to go into the Print service, select the printer in Settings -> Queues, and then share it via LPR (optionally turning on Rendezvous discovery as well).
So when I go to use it in the Client, I can see the printer available, but Client doesn't get any driver information for it. It looks to Client like a generic PostScript printer. You can select from a list of CUPS+Gimp-Print drivers, which may or may not work like the original driver, and may or may not be available for your printer.
For some people, print serving in Panther Server might be fine. You can serve printers via LPR (+Rendezvous), Samba, or AppleTalk. You can have quotas, view jobs, cancel or pause jobs, and do cool things. It's a great tool, but I can't use it.
If I want to share my printer I must either use generic drivers, which is unacceptable to me, or use Client or the AirPort Extreme Base Station. I'd never shared a printer with the Base Station before, but I tried it, and it worked. I am sending faxes through my Panther-based MP3 player in the closet (but receiving them through Server). It's a shame that the $500 Server product can't do what Client can do. Maybe Server 10.4 will fix the problem.
FTP
After wasting a lot of time on printing, I picked something simple: FTP. I do backups with Retrospect via FTP, or else I wouldn't even bother. I know, I can do it over AFP too, but I've been using FTP for awhile (I used to do backups to a Linux box), and I just stick with what works. Besides, I need a reason to enable the service for the purposes of the review.
The path setup was a bit awkward at first. I needed access to the file server via FTP, but I didn't want to define it as the FTP server root. I could have set up a symlink to it, of course, but it was already a share point for AFP, so I set FTP to use "Home Directory with Share Points" for authenticated users. This dumped a symbolic link to the FTPRoot in my home directory, and symbolic links to all the share points in the FTPRoot. That'll work.
I turned it on, tested Retrospect with the new path, and it was all good ... unlike printing, which I am still bitter about. Onward and upward. Breathe in, breathe out.
Mail
I often have issues with various SMTP servers, so I decided I should have my own. Server switched over to Postfix from Apple's proprietary server, and Cyrus for POP/IMAP, Mailman for mailing lists ... but I need only SMTP.
I clicked on Settings and selected Enable SMTP, and told it my ISP as relay host. I could send mail directly, but some servers these days don't like mail coming from home boxes. Then I went over to Filters, and to make sure I am not used as a spam relay, I allow only 127.0.0.1/32, 10.0.0.0/22, and 192.168.0.0/24 to send mail.
Now, I just need to add my external hostname to my local host aliases in Advanced, and I am all set. Turn it on, and it works.
This is getting to be fun. Except for printing! (You can't see it, but I am shaking my fist at the sky right now.)
DHCP
Just for fun, I decided to serve DHCP from here too. My hardware router did it before, but I want to have as many services running as I know what to do with. Besides, I'd like more control over IP ranges and such than my little router offers. I do know a little bit about DHCP; I hope it's enough.
I click on Settings, and I add a subnet to the list. Interface en0, start at 10.0.1.200, end at 10.0.1.239. Router -- that which used to distribute IPs -- is 10.0.1.1. Lease time ... a month. Sure, why not? Set up default domain, name server addresses. No LDAP, no WINS. OK, all set turn it on. It works.
I am starting to feel mighty confident, I tell you what. And for the moment, I forget about printing.
DNS
I have a lot of local hostnames on my network. And true, I could use .local to deal with them all, but not all of them are Macs (the horror!), and I like using the same names for my machines when I am outside the LAN. I previously shuffled around hosts files, like we did back in the day. I know not a thing about DNS. Well, now's a chance to learn, right?
Emboldened by recent successes, I bravely clicked on the DNS service and Settings. It asks if I want to allow zone transfers and recursion. Um, I guess so. I feel like a Holiday Inn Express patron.
Then I clicked on Zones, and here's where the real "fun" begins. Again, I know not a thing about DNS. Well, enough that I know what I am looking at, in general. But after playing around a little and reading some online docs about DNS and PTR records and the like, I eventually figured it out. And once I realized what I was doing, the interface made a lot of sense.
OK, I don't feel quite as good about myself as I did before, but still feeling good. Have I the stamina to try Firewall?
Firewall
My router's firewall limitations are more severe than its DHCP limitations. It can only redirect a handful of incoming ports, and set a single default IP. I would like more control than that, so I figured I could set the router to send everything to Server, where Firewall can handle it.
In retrospect, it actually worked well. I have had even less experience with firewalls than with DNS. But I just, for quite awhile, could not get it to work. In Settings, there are default IP address groups, and I selected "10-net" to open all sorts of ports on the local network. But I didn't look closely enough, and it was set up for 10.0.0.x, and all my machines are on 10.0.1.x. Those wasted hours are what I get for using the defaults and not looking at them closely.
Another problem I ran into is that there is a rather handy list of services to allow for the given addresses: merely select an address group, and check the boxes. But the list of services is not configurable, so if I want to do something simple like allow local access for remote Apple events (port 3031), I can't merely hit a checkbox, because it is not already in the list. I need to manually configure that port in the Advanced section.
As it turns out, the Advanced section isn't too bad, even for someone, like me, largely unfamiliar with firewall configuration. Once I figured out my problem with the default 10-net group, the rest went smoothly.
VPN
As I was configuring my firewall I decided to close off everything to the outside world except for a few mostly secure and essential services, and try out VPN for the rest. Most of what I wanted to keep open were for my own sake, when I am away from home with the laptop. So if I just close it all off, then I can use VPN to get access to mail, FTP, even faxing.
I read up a little bit and decided L2TP over IPsec, instead of PPTP, would be best. So I hit a checkbox to enable it, and I restricted access to my personal group ("pudge"). I added a shared secret and added a block of IP addresses.
Then I went into Internet Connect on Client, selected "New VPN Connection" under the File menu, and put in the server address, account name, password, and shared secret. I dialed up on a PPP connection so I could test it, and clicked Connect in the VPN window, and it just worked. Very nice.
Of course, my measly cable modem is slow, so when I was at a coffee house "hot spot" the other day, I could get on the network, but it was excruciating to do anything requiring significant bandwidth. I can't find a way to blame Apple for that, though.
Web
I serve various things from the local web server: MP3s (for downloading MP3 files, since iTunes assumes that is stealing), documentation, books and periodicals, a local CPAN mirror, personal photos, etc.
The web server is serviceable for basic HTML and file serving, but it is a pain to configure. It won't let you put things where you want them in the config files, and sometimes just breaks things.
For example, I want to turn use mod_rendezvous, so I add a couple of RegisterResource directives. They work fine. But the next time I edit my configuration through Server Admin, it removes one of the directives, apparently thinking that I can only have one.
The best thing to do is to use Apache's Include directive and put all the custom configurations in a separate file, wherever possible. Then Server Admin should be less likely to throw its weight around.
And then there's mod_perl, which is severely broken: normal print statements don't work. For some reason, the print() never gets tied properly to $r->print(). Thanks to the always useful macosxhints.com, I found a servicable workaround, though the only proper and decent fix is to get a nonbroken mod_perl build. Once I did this, my custom mod_perl scripts, plus Apache::MP3 and Apache::Pod, seemed to work well.
Also, I set up some directives to Deny services unless the remote address is in 10.0. In the access log, they showed up as 10.0., but in the error log, when denied, the address was 127.0.0.1. I traced this to the Performance Cache, which is turned on by default. I don't need it, so I turned it off.
In figuring this out, I discovered that a side effect of having every client appear to come from 127.0.0.1 is that the mod_status data (at the "server-status" path) was open to the world. The server-status resource is, by default, restricted so that only clients from 127.0.0.1 can access it. I don't think this can be used to directly exploit a system, but it might make private information available, such as client IPs and URLs (which may include session IDs, or other private information). It would be wise to turn off Performance Caching, or lock down your services that may be restricted by IP.
One nice feature is that the Apple-supplied mod_auth_apple uses, in addition to standard htpasswd files, the system user and passwords (if the same user is in both places, with different passwords, either password is acceptable). There's also a mod_sherlock_apple that provides web access to Sherlock content indexes, though I couldn't get this to work, and the documentation wasn't much help.
Hardware Revisited
The initial test machine was the dual G4/1.25 GHz I described earlier, but I also had the opportunity to test it on a dual G5/2 GHz. Man, is that a sweet machine. But my needs are so few, I didn't notice any substantive difference in the serving (though when I was actually working on the machine, or compiling software, or playing games, I noticed huge differences, as one would expect).
I've now got everything set up on a comparatively wimpy PowerBook G3/500. I thought it would squeal and keel over, but it's been stable and plenty fast. The one exception is when I am doing large file transfers: it seems the data moves through the PowerBook pretty slowly. Still, the CPU load stays low all the time, although it sometimes ran out of free memory pretty quickly; once I upped the RAM from 256MB to 640MB, that problem went away.
I guess I shouldn't be too surprised: after all, I used to use a 486 for a server, doing mostly the same sorts of things, and this G3 is faster than that was. I expected it to be slower because of the Mac OS X GUI overhead, I think, but Panther's speed improvements over Jaguar, especially for G3s, are probably helping out here. If I had this in a business environment though, I can't imagine anything less than a dual G4.
Verdict
I like Mac OS X Server, and apart from printing, would rather have it than not have it. Server Admin has its problems, but it is worlds better than the Jaguar Server version, and I expect it to continue to improve: more stability, UI fixes, faster response. Maybe it could even integrate more monitoring features, or make Server Monitor work with non-Xserves. What I really want is ProcessViewer to work with remote machines.
I am well aware Server is not geared toward home use, but I was hoping it might, despite the price, be something a lot of home users could benefit from. Maybe as Server improves in its ease of use and security policies are easier to enforce and audit, through Server or third-party software, it can be such a product.
For now, as much as I like Server, the price tag and knowledge requirements keep me from recommending it for home use. I want to say "if you can't figure out this stuff on your own, then buy Server," but if you really lack that ability, then you shouldn't be configuring Server anyway.
For commercial use, however, Server is an excellent product that I wouldn't hesitate to recommend. It can offer the majority of services any business environment needs, for much less than the cost of Windows alternatives, and the man-hours cost saved with Server Admin is worth the price alone.
-
Review - Mac OS X Server 10.3, Part 1
What is the point of Mac OS X Server? Mac OS X is Unix. I have Apache, bind, sendmail, (and whatever I want) already on here. My Mac OS X box is a server already, right? I have a home network with a half dozen Macs, and have a box that does some serving, and I want it do more. So, I set out to figure out what this Server thing is. (Read on for the rest.)Sure, I can read. I can go to the Mac OS X Server web site and read all the documentation for things related to "standards-based management," "share printers and files," "n-tier" solutions. Yawn. I know all about this stuff, and I know I can do it already. If I am paying good money for this, it better have value I can't already get for free.
First Things First
Essentially, Mac OS X Server is the same thing as Mac OS X (a.k.a. Client). It's the same core OS, it has the same versioning (10.3.2 as of this writing), it runs the same programs. But Server comes with programs and tools and configurations geared toward being a server, rather than a user's workstation.
Server comes in two flavors: a 10-client version for $500, and an unlimited client version for $1000. The only difference between the two is that the 10-client version limits file and windows sharing to 10 simultaneous clients. You can have any number of users, but only 10 can connect to those services at the same time.
With that money, you also get 90 days of "up-and-running" support covering the software that ships with Server. So if you've read the frelling manual and still can't figure out why the firewall doesn't seem to be working, you can get some help. After 90 days, you can still get help -- including more advanced topics -- but it will cost you from $6,000 to $50,000.
Hardware
The Xserve, Apple's rack-mountable computer, comes with the unlimited client version of Server preinstalled; and really, Server is built with Xserve in mind. Server Monitor, included with Server, displays uptime, temperature, drives, power, network usage, fans, and security of Xserve boxes.
You can configure Xserve boxes automatically with Panther Server preinstalled. Design your configuration on one machine, set up an LDAP server and put it in the DHCP server settings, and add your configuration file to the LDAP server. Turn on the other servers for the first time, and each one will find the DHCP server, find the LDAP server, find the configuration file, and configure itself automatically. You can also put the configuration file on a USB key or somesuch, and the machines will configure themselves that way, too.
My test box is a dual G4/1.25 GHz Power Mac; it performs with nary a hiccup. If I had a large network or many users, I can imagine wanting more power: with a Power Mac or Xserve G5, I'd be able to take advantage of an OS that is optimized for the 64-bit CPU. For me, however, this would result in a depressingly, perpetually, low CPU load.
Initial Security Considerations
Out of the box, assuming no one has set up a rogue DHCP server on your network, Mac OS X Server is mostly secure: only SSH is on by default. As other services are turned on, more security concerns are created, because new security holes may be opened.
For the most part, the default configurations of the various services are secure, but that largely depends on your specific environment. Mac OS X Server is excellent at making advanced server configuration easier, but this ease of use comes with a price: you may be opening yourself up to attack. Mac users are often not used to the idea of making themselves vulnerable just by clicking checkboxes.
This may look like a Mac, and may be easy to use, but it is no substitute for having a real live sysadmin on hand to -- at the very least -- audit the security of the system. It'd be nice if Server included audit tools; I envision UI elements that warn you when you have conflicts, or when you've opened up a hole, or when you've violated predefined security policies. On the other hand, it would be more reliable to have a third-party system to do the audit, on basic principle. But that's so un-Mac-like.
Open
Tom Goguen, Director of Marketing for Mac OS X Server, says that Apple is 100% into using open standards and open source in the core operating system.
Mac OS X Server has always been largely based on open standards, but the Panther incarnation has gone even further. Gone are Apple's proprietary mail systems; they are replaced by postfix, mailman, and cyrus. Mostly gone is NetInfo; it is replaced by LDAP. Rendezvous, also an open system that others can plug into, is a bigger part of Server now: FTP, LPR, and web services are all announced via Rendezvous.
Of course, as always, Server -- just like Client -- is based on FreeBSD (now version 4.8, with some of 5.0 stirred in), and most of the Apple core OS itself is under the Apple Public Source License.
A Case for Case
New to Panther is case sensitivity in HFS+. For many years, Mac OS has used the HFS as its file system, which treated "Foo" and "foo" as the same file. Some years ago, HFS+ was introduced to overcome many of the limitations of HFS, but case sensitivity -- seen more as a usability feature than a limitation -- remained.
But in Unix, this certainly is a limitation for many people. "Makefile" vs. "makefile" and "head" vs. "HEAD" have caused many a headache for Mac OS X/Unix users. But now case sensitivity is a formatting option.
Because case insensitivity is still seen as a usability feature, this feature is not available by default on Client, although you could always connect your drive to a Server to format it. It is also possible, in theory, to format a drive with case sensitivity in Client using various tricks.
Setting it Up
My server is connected to my home network via a 100BaseT switch, to which is also connected a cable modem and an AirPort Extreme base station. My PowerBook G4/867 connects to the network via AirPort or the switch. My wife has an iBook G3/600, and I've got a PowerBook G3/400 in my stereo closet for playing MP3s. The PowerBook doesn't have internal AirPort, and instead is connected to another switch and another Extreme base station, configured to do WDS. I've also got the PS2 connected in there. Everything is running Panther Client (except for the PS2, last I checked).
Looking at the various services offered by Server, I can already see many things I want to set up: file sharing (Apple Filing Protocol, or AFP), DHCP for guests, DNS, FTP, SMTP, printing, and web. I have most of those already set up now, but I wouldn't mind if they were easier to configure and manage.
After surveying my situation, I installed Panther Server and took a look around.
The first thing I wanted to see was what my configuration options were. And lo, there in my Dock were not the expected iMovie, iTunes, iPhoto, and the like, but icons that a mouseover revealed to be representative of programs like Workgroup Manager, the aforementioned Server Monitor, and Server Admin.
Workgroup Manager uses a lot of terminology that is completely lost on me, and I am not managing any users, really. My wife doesn't need the file server -- we can exchange files via iChat, or I can copy them to her machine via scp -- and she keeps all her own files on her machine. We won't be using any print quotas. I do use Workgroup Manager to create some basic user accounts for friends, but I don't need any features more advanced than what is in Client.
Server Admin is what I want to sink my greedy little digits into. I opened it up, clicked the "add new server" button, typed in my server name ("Sweeney.local") and password, and started playing.
As I started looking around, I remembered that there was an extra CD in the distribution called Admin Tools. It allows you to install these tools on any Client machine, so you can manage the Server remotely. I want to go hang out in my La-Z-Boy while I configure my server, so I installed the tools on my PowerBook. Nifty.
Server Admin lists each machine and the services available to it, with an icon next to each describing its status. If you select a machine's name, you see several tabs: Overview, Logs, System, Graphs, Update, and Settings. Overview reports the system version, names, and dates. Under Logs, you can view the system log, watchdog log, etc. System reports what network interfaces and volumes are available. Graphs displays CPU and network use in pretty pictures. Update runs Software Update. Settings controls the system names, the date and time and timezone.
This is basic stuff, and each service is laid out in similar fashion. All of them have at least two tabs: Overview and Settings. Most also have a Logs tab. Some have other tabs like Connections, Graphs, Clients, Activity, Accounts, Queues, and Jobs.
The available services are AFP, Application Server, DHCP, DNS, Firewall, FTP, Mail, NAT, NetBoot, NFS, Open Directory, Print, QuickTime Streaming, VPN, Web, and Windows. Somewhat conspicuous in its absence, to me, is MySQL, which is included in Server, but doesn't have an interface in Server Admin.
Server Admin does have its problems. It will crash on occasion, but I see no evidence of my settings being corrupted, or any other lasting ill effects. Some of the lists are not sortable, though they appear to be: for example, the DNS zone listings are not sortable, even though clicking on the column headers indicate otherwise.
Also, it can be slow to update. This is understandable, but annoying. Logs don't refresh immediately, and when you hit reload, the wrong log is selected, instead of the current log being refreshed. When restarting services or viewing logs, I will sometimes use the command line tools, as they are more efficient; it would be nice if Server Admin would display the path to the log you are looking at, so you can easily find and tail it in a shell.
Sharing
Some of these services are available in a minimal form in Client, in Sharing under System Preferences: file sharing, Windows sharing, web, FTP, and printing. In Server, the Sharing preferences are still there, but contain only three items: Remote Login, Apple Remote Desktop, and Remote Apple Events. Remote Login is simple: it allows users to connect with ssh/scp, and can be turned on or off. The other two require, perhaps, a bit more explanation.
Apple Remote Desktop is a way for an admin to control client computers. Previously, the client was distributed only as part of the software package of the same name, but now the client is included with Panther. It is, of course, off by default, and once turned on, each machine must define what users have access to what resources (this can be done via the command line, too). I most commonly use ARD for controlling and viewing the screen of another computer, installing packages, and copying files.
Remote Apple Events has been in Mac OS for many years, since back in version 7-dot-something. It allows controlling "scriptable" Mac applications -- such as with AppleScript -- over the network. It used to run over AppleTalk, but now runs over plain old TCP/IP. Not many people make use of remote Apple events in my experience, but I use them often; for example, I have a Perl script that queries iTunes on a remote box, and sets the current track in iChat.
Windows
I don't use Windows, and therefore can't really test the new Windows integration in Panther Server. But from what I can tell, Apple has added quite a few improvements. Samba has been updated to version 3, and the lists of Unix and Windows users can be united via Directory Services. But I confess to a crippling ignorance and apathy about this small corner of the computing world. Sorry.
To Be Continued
Tomorrow, I'll get into the details of setting up the services I use on my network.
-
Switching from tcsh to bash?
momerath2003 asks: "With the advent of Mac OS X 10.3 Panther, Apple will switch its default shell from tcsh to bash (in order to conform more to the newer Linux trends). A lot of Mac power users will want to know how to make the switch, especially if they use such tcsh-specific extra files as the login/out scripts in the /usr/share/tcsh/examples directory (they automatically set up some aliases and can automatically read aliases from a specific file, among other things). So, how do we all adapt? What are some ways to emulate the behavior of the example files, and what differences are there between the bash and tcsh shells?" -
Turning Your Mac Into a Serial Console Server
chrisbw writes "Want to put that old VT100 terminal to use? Mac OS X Hits has a story on how to make a couple simple changes in OS X to enable login on a serial terminal (even over a USB serial adapter if you're on a newer mac). Cool trick for adding a text-based web surfing or email terminal in another room, or remote iTunes control!" -
Mac OS X Unleashed (2nd Edition)
emmastory writes "Mac OS X Unleashed is not a pocket guide. It's more of a massive tome than anything else - at over 1500 pages, it's probably the heaviest technical book I own. (And that's including Deitel & Deitel's C: How to Program.) Since Mac OS X Unleashed describes itself as 'a complete guide and reference for Mac OS users,' my biggest question when approaching the book was whether this is in fact the case. It seems like if you're going to shell out for an OS X book of this size and price, then it should ideally be the only OS X book you'll have to buy." Mac OS X Unleashed (2nd Edition) author John Ray, William C. Ray pages 1560 publisher Sams rating 7/10 reviewer Emma Story ISBN 0672324652 summary A massive book that aims to be a complete OS X referenceWhat I Liked
There's no shortage of good things about Unleashed, but the best is probably that the authors assume, for the most part,that you already know how to use your computer. Although there are many good books out there for those new to Macs, this is not one of them and does not try to be. That means that if you've already achieved a basic working knowledge of Mac OS, there's still well over a thousand pages of information intended especially for you. A line from another review of Unleashed (posted anonymously on Amazon) that rang particularly true after reading the book: "If you're looking for a book that says 'this is called a mouse' and tells you where to find iTunes in order to click on it, or drops the bombshell that command-p will print in many applications, you don't need this volume, but if you want to get your hands dirty, it's an excellent resource."However, I can understand that many people do want the basics in an OS X book. In fact, another Amazon reviewer makes this very point: "Coverage of the iApps is far less than it should be, and there isn't enough information for a novice user like myself. I thought the author spent far too much time on the UNIX and Terminal side of Jaguar and not enough on the real-world tips that I've found in other books." Still, I personally don't really see that as a problem. There are plenty of real-world tips as long as your real world involves a shell, and if there's one thing I've never needed a book for, it's the iApps. In fact, I've always found it irritating that other OS X books spend so much time on them. But that's me, and I'm not everyone.
There were several sections of the book that surprised me, including the chapter on web programming. It makes sense, though - the book is intended to "unleash" OS X, after all, and OS X does come with an Apache installation (even if System Preferences calls it Personal Web Sharing). Given that every OS X box has a webserver, it makes sense that many OS X users would want to know more about related topics. In fact, the chapters that focus on system and network administration comprise a pretty thorough introduction to the BSD side of OS X, and were fairly impressive. These were my favorite sections of the book, probably because they're topics rarely dealt with - or at least rarely dealt with well - in Mac books.
What I Didn't Like
The book suffers from some minor issues typical of most massive technical volumes - it's informative, but also dry, dense, and not terribly readable. Also, while I appreciate the depth and scope of the book, it is a little unwieldy. This isn't something you'll be reading in bed or on the subway. It's not a cheap book, either - its list price is $50. These problems are neither hugely important nor terribly surprising, but they're also not inevitable - reference texts can be thorough without being dull, it's just that this one happens to be both.Probably the only other real complaint I have with the book is that at times it seems as though it can't decide who its audience is. As I mentioned above, one of the things I liked about Unleashed was that most of the book seems firmly aimed at the intermediate to experienced user. And yet if that's the case, then the chapters that cover things like Desktop Accessories (Calculator, Clock, Key Caps) seem out of place. It doesn't seem like the introductory material offered in the book would really be enough to serve as a tutorial for an absolute beginner (as evidenced by complaints like the one I quoted earlier), but at the same time it's difficult to figure out who else would need it. However, I'm not suggesting they skimped on advanced topics to squeeze in inappropriate Clock coverage - if there's one thing this book has, it's plenty of everything.
The Bottom line
I believe that Unleashed does live up to its title, and does a good job in the process. It's not an introduction to OS X - it's about getting more out of your system after you've already learned the basics. It doesn't (usually) try to be a beginner's book, but a quick-learning novice would probably do fine with it, and any moderately experienced Mac user will probably find that it serves his or her purposes effectively and efficiently. If given the choice (and funding), I'd probably still go with a couple different books, but I think Unleashed has in fact reached its goal of being a complete guide to OS X. You could do just fine with only this book, and at $50 it may be cheaper than buying a couple smaller books separately.And Furthermore
Other reviews and sources of information on the book:- Review at macosxhints (from whence another Mac book, incidentally)
- Review at osnews.com
- Review at mymac.com
- Epinions page for the book, which as it turns out isn't all that useful
- Amazon's page for the book, including many customer reviews
You can purchase the Mac OS X Unleashed from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. -
Mac OS X Unleashed (2nd Edition)
emmastory writes "Mac OS X Unleashed is not a pocket guide. It's more of a massive tome than anything else - at over 1500 pages, it's probably the heaviest technical book I own. (And that's including Deitel & Deitel's C: How to Program.) Since Mac OS X Unleashed describes itself as 'a complete guide and reference for Mac OS users,' my biggest question when approaching the book was whether this is in fact the case. It seems like if you're going to shell out for an OS X book of this size and price, then it should ideally be the only OS X book you'll have to buy." Mac OS X Unleashed (2nd Edition) author John Ray, William C. Ray pages 1560 publisher Sams rating 7/10 reviewer Emma Story ISBN 0672324652 summary A massive book that aims to be a complete OS X referenceWhat I Liked
There's no shortage of good things about Unleashed, but the best is probably that the authors assume, for the most part,that you already know how to use your computer. Although there are many good books out there for those new to Macs, this is not one of them and does not try to be. That means that if you've already achieved a basic working knowledge of Mac OS, there's still well over a thousand pages of information intended especially for you. A line from another review of Unleashed (posted anonymously on Amazon) that rang particularly true after reading the book: "If you're looking for a book that says 'this is called a mouse' and tells you where to find iTunes in order to click on it, or drops the bombshell that command-p will print in many applications, you don't need this volume, but if you want to get your hands dirty, it's an excellent resource."However, I can understand that many people do want the basics in an OS X book. In fact, another Amazon reviewer makes this very point: "Coverage of the iApps is far less than it should be, and there isn't enough information for a novice user like myself. I thought the author spent far too much time on the UNIX and Terminal side of Jaguar and not enough on the real-world tips that I've found in other books." Still, I personally don't really see that as a problem. There are plenty of real-world tips as long as your real world involves a shell, and if there's one thing I've never needed a book for, it's the iApps. In fact, I've always found it irritating that other OS X books spend so much time on them. But that's me, and I'm not everyone.
There were several sections of the book that surprised me, including the chapter on web programming. It makes sense, though - the book is intended to "unleash" OS X, after all, and OS X does come with an Apache installation (even if System Preferences calls it Personal Web Sharing). Given that every OS X box has a webserver, it makes sense that many OS X users would want to know more about related topics. In fact, the chapters that focus on system and network administration comprise a pretty thorough introduction to the BSD side of OS X, and were fairly impressive. These were my favorite sections of the book, probably because they're topics rarely dealt with - or at least rarely dealt with well - in Mac books.
What I Didn't Like
The book suffers from some minor issues typical of most massive technical volumes - it's informative, but also dry, dense, and not terribly readable. Also, while I appreciate the depth and scope of the book, it is a little unwieldy. This isn't something you'll be reading in bed or on the subway. It's not a cheap book, either - its list price is $50. These problems are neither hugely important nor terribly surprising, but they're also not inevitable - reference texts can be thorough without being dull, it's just that this one happens to be both.Probably the only other real complaint I have with the book is that at times it seems as though it can't decide who its audience is. As I mentioned above, one of the things I liked about Unleashed was that most of the book seems firmly aimed at the intermediate to experienced user. And yet if that's the case, then the chapters that cover things like Desktop Accessories (Calculator, Clock, Key Caps) seem out of place. It doesn't seem like the introductory material offered in the book would really be enough to serve as a tutorial for an absolute beginner (as evidenced by complaints like the one I quoted earlier), but at the same time it's difficult to figure out who else would need it. However, I'm not suggesting they skimped on advanced topics to squeeze in inappropriate Clock coverage - if there's one thing this book has, it's plenty of everything.
The Bottom line
I believe that Unleashed does live up to its title, and does a good job in the process. It's not an introduction to OS X - it's about getting more out of your system after you've already learned the basics. It doesn't (usually) try to be a beginner's book, but a quick-learning novice would probably do fine with it, and any moderately experienced Mac user will probably find that it serves his or her purposes effectively and efficiently. If given the choice (and funding), I'd probably still go with a couple different books, but I think Unleashed has in fact reached its goal of being a complete guide to OS X. You could do just fine with only this book, and at $50 it may be cheaper than buying a couple smaller books separately.And Furthermore
Other reviews and sources of information on the book:- Review at macosxhints (from whence another Mac book, incidentally)
- Review at osnews.com
- Review at mymac.com
- Epinions page for the book, which as it turns out isn't all that useful
- Amazon's page for the book, including many customer reviews
You can purchase the Mac OS X Unleashed from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. -
Mac OS X Hints
emmastory writes "Mac OS X Hints is a brand-spanking new O'Reilly book containing over five hundred 'power tips' and tricks for (amazingly enough) Mac OS X. The tips are culled from the website of the same name, written and maintained by Rob Griffiths. The book is edited by David Pogue, of Missing Manual and Pogue Press fame. It's 461 pages, list price is $24.95, and the O'Reilly catalog page (containing samples from the book) is right here." Read on for emmastory's review. Mac OS X Hints author Rob Griffiths pages 461 publisher O'Reilly/Pogue Press rating 8 reviewer Emma Story ISBN 0596004516 summary The perfect sequel to the Missing Manual, this book contains 500 tips for OS X
Addressing the ObviousThe most immediate question I had when I heard that O'Reilly would be publishing a book containing hints from macosxhints.com was, of course, Why I should get the book when the hints are already on the site for free? Both the author and the publisher also thought of this, understandably enough. Here's how Rob Griffiths answered the question in a post on the site, when the book was first announced: "The book isn't just a 'cut and paste' job from the site-to-print form. Every hint was rewritten and retested from scratch, and hundreds of screenshots were added to help clarify and explain the hints. In addition, many of the scripts and programs posted here are included (the author of each program was contacted for approval to include their original work in the book -- thanks to each of you for agreeing!)."
The response included in the O'Reilly press release for the book is along the same lines: "'The 500-plus hints in this book are based on tips published in the Mac OS X Hints web site,' explains Griffiths. 'But it's not just a rehash of what's there. Every hint has been rewritten, expanded, organized, indexed, tested for compatibility with the latest version of Mac OS X 10.2, and in many cases, illustrated, making the book an even better resource than the web site."
So the question then becomes: is this really the case? Are the differences between the hints as posted on the site and as printed in the book really significant enough to merit shelling out $24.95?
The short answer is that, in my opinion, the book is worth its price. The long answer is (predictably) a little more complicated. There are, of course, people who are more than willing to do the extra digging on the web to get the relevant content for free -- they'd rather do without the little perks (increased readability, revision, testing, screenshots) than spend potential beer money for a glossy O'Reilly book. And that's fine -- I'm more than sympathetic with this position, being frequently hard up for beer money, myself. But of course there are also people for whom the convenience is just as important as the cost, and who consider the price of the book well worth it in terms of the time saved. If you fall into the former category, don't bother buying the book -- but then, you weren't going to buy it anyway, were you? As for the latter group, rest assured that your investment will not, in this case, be wasted.
What I LikedI've read several other books on Mac OS X. The one I believe everyone should start with is still David Pogue's Mac OS X: The Missing Manual . If you've already read this book (and enjoyed it) or didn't read it but are confident you've already got the equivalent experience, then Mac OS X Hints is a good next step.
Griffiths assumes you're comfortable using OS X for basic tasks: he doesn't tell you how to log in, or what the Dock is. If you're fuzzy on those kind of basics, you're not quite ready for this book (but you're positively crying out for a copy of the Missing Manual). Additionally, he pushes some not-entirely-obvious processes to the introduction, so you don't have to read the same instructions over and over in the meat of the book itself. After all, once you've been told the first time how to view the contents of a package, you're probably all set in that regard. This is one of the aspects of Mac OS X Hints that I found most appealing, actually - Griffiths just explains in the beginning that he's assuming certain things, and then doesn't bother dumbing anything else down.
I've been a fan of macosxhints.com since I first installed OS X, but it seems like Griffiths's style has really improved for the book -- this may be a function of Pogue's role as editor, as the writing in Hints displays the same familiar, comfortable tone while not skimping on depth or details. Like other books Pogue has been involved in, this one is highly readable but not oversimplified.
It seems like the revision process the hints went through during their transition from site to print has been pretty successful, as well -- despite being familiar with the site, there was a great deal of material in the book that I had never seen, even after reading other OS X books. Additionally, the testing involved in the book's creation removes a great deal of the frustration inherent in the site. As much as I like the site, there have been several hints that have mysteriously declined to function on my own system for whatever reason -- but everything I've tried from the book worked without a hitch.
I also enjoyed the fact that this book, like Mac OS X Hacks , is made for sampling. Each article is short and to the point, and while related hints are grouped by chapter, no single tip depends on the reader having already performed one of the others (unless otherwise specified). You don't have to read the book cover to cover -- you can flip around at will without getting lost.
Incidentally, another plus is that 15% of all Griffiths's profits from this book are being donated to the Doernbecher Children's Hospital. That in itself isn't a reason to buy the book, but it's good to know.
What I Didn't LikeIf I can be nitpicky for a moment, I was bothered by the frequency of purely typographical errors. Little things like "than" being used instead of "then," or the bottom edge of a line in a sidebar getting cut off. It didn't keep me from enjoying the book, and I'm sure it's the sort of thing that will get corrected in future printings, but this sort of error occurred often enough that I noticed it, anyway.
Another little thing: I wish URLS had been included whenever a third-party shareware program was mentioned. Of course I know I can Google for DragThing and find it immediately -- but if I'm paying for a book, it seems to me that I shouldn't have to.
There is also the fact that this book is undeniably a book, and that limits it in certain respects (at least when compared to the site). The index is comprehensive and useful, but it's just not as useful as the ability to search the entire text of the book. It's also inevitably dated to a certain degree -- new hints posted to the site, even if they're infinitely more fabulous than ones already present in the book, just won't show up in print for a long time to come. Similarly, if a new version of the OS breaks one of the hints, you'll be able to find out somewhere on the web, but it won't be immediately obvious when you're just reading the book. Of course, these are problems shared by all print technical books, and not just Hints.
One final note: there's a lot of overlap between this book and Mac OS X Hacks, although each book has a significant amount of unique content. If you own one, you probably don't need to get the other, but it's difficult to say which I'd buy if I had to choose. Hacks contains only 100 articles, but they're more in-depth and the tasks they cover are often trickier or less obvious. Hints contains over 500 tidbits, but they're much shorter and often deal with things like key commands that allow you to increase your efficiency, and things of that ilk.
The Bottom LineIf you're the sort for whom time is at a higher premium than money -- maybe you're the kind of person who would buy a boxed *nix distribution instead of downloading it -- then I'd say go ahead and get this book. It's well worth its price as long as you understand that what you're paying for is ease of use and reliability, as well as content. If, on the other hand, you're living on Top Ramen for the foreseeable future, you're probably better off sticking with the site. If you do buy it, I think you'll find it will make a happy addition to your bookshelf -- stick it next to the Missing Manual and dip into it whenever you're sitting through an install or reboot.
You can purchase the Mac OS X Hints from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. -
Mac OS X Hints
emmastory writes "Mac OS X Hints is a brand-spanking new O'Reilly book containing over five hundred 'power tips' and tricks for (amazingly enough) Mac OS X. The tips are culled from the website of the same name, written and maintained by Rob Griffiths. The book is edited by David Pogue, of Missing Manual and Pogue Press fame. It's 461 pages, list price is $24.95, and the O'Reilly catalog page (containing samples from the book) is right here." Read on for emmastory's review. Mac OS X Hints author Rob Griffiths pages 461 publisher O'Reilly/Pogue Press rating 8 reviewer Emma Story ISBN 0596004516 summary The perfect sequel to the Missing Manual, this book contains 500 tips for OS X
Addressing the ObviousThe most immediate question I had when I heard that O'Reilly would be publishing a book containing hints from macosxhints.com was, of course, Why I should get the book when the hints are already on the site for free? Both the author and the publisher also thought of this, understandably enough. Here's how Rob Griffiths answered the question in a post on the site, when the book was first announced: "The book isn't just a 'cut and paste' job from the site-to-print form. Every hint was rewritten and retested from scratch, and hundreds of screenshots were added to help clarify and explain the hints. In addition, many of the scripts and programs posted here are included (the author of each program was contacted for approval to include their original work in the book -- thanks to each of you for agreeing!)."
The response included in the O'Reilly press release for the book is along the same lines: "'The 500-plus hints in this book are based on tips published in the Mac OS X Hints web site,' explains Griffiths. 'But it's not just a rehash of what's there. Every hint has been rewritten, expanded, organized, indexed, tested for compatibility with the latest version of Mac OS X 10.2, and in many cases, illustrated, making the book an even better resource than the web site."
So the question then becomes: is this really the case? Are the differences between the hints as posted on the site and as printed in the book really significant enough to merit shelling out $24.95?
The short answer is that, in my opinion, the book is worth its price. The long answer is (predictably) a little more complicated. There are, of course, people who are more than willing to do the extra digging on the web to get the relevant content for free -- they'd rather do without the little perks (increased readability, revision, testing, screenshots) than spend potential beer money for a glossy O'Reilly book. And that's fine -- I'm more than sympathetic with this position, being frequently hard up for beer money, myself. But of course there are also people for whom the convenience is just as important as the cost, and who consider the price of the book well worth it in terms of the time saved. If you fall into the former category, don't bother buying the book -- but then, you weren't going to buy it anyway, were you? As for the latter group, rest assured that your investment will not, in this case, be wasted.
What I LikedI've read several other books on Mac OS X. The one I believe everyone should start with is still David Pogue's Mac OS X: The Missing Manual . If you've already read this book (and enjoyed it) or didn't read it but are confident you've already got the equivalent experience, then Mac OS X Hints is a good next step.
Griffiths assumes you're comfortable using OS X for basic tasks: he doesn't tell you how to log in, or what the Dock is. If you're fuzzy on those kind of basics, you're not quite ready for this book (but you're positively crying out for a copy of the Missing Manual). Additionally, he pushes some not-entirely-obvious processes to the introduction, so you don't have to read the same instructions over and over in the meat of the book itself. After all, once you've been told the first time how to view the contents of a package, you're probably all set in that regard. This is one of the aspects of Mac OS X Hints that I found most appealing, actually - Griffiths just explains in the beginning that he's assuming certain things, and then doesn't bother dumbing anything else down.
I've been a fan of macosxhints.com since I first installed OS X, but it seems like Griffiths's style has really improved for the book -- this may be a function of Pogue's role as editor, as the writing in Hints displays the same familiar, comfortable tone while not skimping on depth or details. Like other books Pogue has been involved in, this one is highly readable but not oversimplified.
It seems like the revision process the hints went through during their transition from site to print has been pretty successful, as well -- despite being familiar with the site, there was a great deal of material in the book that I had never seen, even after reading other OS X books. Additionally, the testing involved in the book's creation removes a great deal of the frustration inherent in the site. As much as I like the site, there have been several hints that have mysteriously declined to function on my own system for whatever reason -- but everything I've tried from the book worked without a hitch.
I also enjoyed the fact that this book, like Mac OS X Hacks , is made for sampling. Each article is short and to the point, and while related hints are grouped by chapter, no single tip depends on the reader having already performed one of the others (unless otherwise specified). You don't have to read the book cover to cover -- you can flip around at will without getting lost.
Incidentally, another plus is that 15% of all Griffiths's profits from this book are being donated to the Doernbecher Children's Hospital. That in itself isn't a reason to buy the book, but it's good to know.
What I Didn't LikeIf I can be nitpicky for a moment, I was bothered by the frequency of purely typographical errors. Little things like "than" being used instead of "then," or the bottom edge of a line in a sidebar getting cut off. It didn't keep me from enjoying the book, and I'm sure it's the sort of thing that will get corrected in future printings, but this sort of error occurred often enough that I noticed it, anyway.
Another little thing: I wish URLS had been included whenever a third-party shareware program was mentioned. Of course I know I can Google for DragThing and find it immediately -- but if I'm paying for a book, it seems to me that I shouldn't have to.
There is also the fact that this book is undeniably a book, and that limits it in certain respects (at least when compared to the site). The index is comprehensive and useful, but it's just not as useful as the ability to search the entire text of the book. It's also inevitably dated to a certain degree -- new hints posted to the site, even if they're infinitely more fabulous than ones already present in the book, just won't show up in print for a long time to come. Similarly, if a new version of the OS breaks one of the hints, you'll be able to find out somewhere on the web, but it won't be immediately obvious when you're just reading the book. Of course, these are problems shared by all print technical books, and not just Hints.
One final note: there's a lot of overlap between this book and Mac OS X Hacks, although each book has a significant amount of unique content. If you own one, you probably don't need to get the other, but it's difficult to say which I'd buy if I had to choose. Hacks contains only 100 articles, but they're more in-depth and the tasks they cover are often trickier or less obvious. Hints contains over 500 tidbits, but they're much shorter and often deal with things like key commands that allow you to increase your efficiency, and things of that ilk.
The Bottom LineIf you're the sort for whom time is at a higher premium than money -- maybe you're the kind of person who would buy a boxed *nix distribution instead of downloading it -- then I'd say go ahead and get this book. It's well worth its price as long as you understand that what you're paying for is ease of use and reliability, as well as content. If, on the other hand, you're living on Top Ramen for the foreseeable future, you're probably better off sticking with the site. If you do buy it, I think you'll find it will make a happy addition to your bookshelf -- stick it next to the Missing Manual and dip into it whenever you're sitting through an install or reboot.
You can purchase the Mac OS X Hints from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. -
Mac OS X Hints
emmastory writes "Mac OS X Hints is a brand-spanking new O'Reilly book containing over five hundred 'power tips' and tricks for (amazingly enough) Mac OS X. The tips are culled from the website of the same name, written and maintained by Rob Griffiths. The book is edited by David Pogue, of Missing Manual and Pogue Press fame. It's 461 pages, list price is $24.95, and the O'Reilly catalog page (containing samples from the book) is right here." Read on for emmastory's review. Mac OS X Hints author Rob Griffiths pages 461 publisher O'Reilly/Pogue Press rating 8 reviewer Emma Story ISBN 0596004516 summary The perfect sequel to the Missing Manual, this book contains 500 tips for OS X
Addressing the ObviousThe most immediate question I had when I heard that O'Reilly would be publishing a book containing hints from macosxhints.com was, of course, Why I should get the book when the hints are already on the site for free? Both the author and the publisher also thought of this, understandably enough. Here's how Rob Griffiths answered the question in a post on the site, when the book was first announced: "The book isn't just a 'cut and paste' job from the site-to-print form. Every hint was rewritten and retested from scratch, and hundreds of screenshots were added to help clarify and explain the hints. In addition, many of the scripts and programs posted here are included (the author of each program was contacted for approval to include their original work in the book -- thanks to each of you for agreeing!)."
The response included in the O'Reilly press release for the book is along the same lines: "'The 500-plus hints in this book are based on tips published in the Mac OS X Hints web site,' explains Griffiths. 'But it's not just a rehash of what's there. Every hint has been rewritten, expanded, organized, indexed, tested for compatibility with the latest version of Mac OS X 10.2, and in many cases, illustrated, making the book an even better resource than the web site."
So the question then becomes: is this really the case? Are the differences between the hints as posted on the site and as printed in the book really significant enough to merit shelling out $24.95?
The short answer is that, in my opinion, the book is worth its price. The long answer is (predictably) a little more complicated. There are, of course, people who are more than willing to do the extra digging on the web to get the relevant content for free -- they'd rather do without the little perks (increased readability, revision, testing, screenshots) than spend potential beer money for a glossy O'Reilly book. And that's fine -- I'm more than sympathetic with this position, being frequently hard up for beer money, myself. But of course there are also people for whom the convenience is just as important as the cost, and who consider the price of the book well worth it in terms of the time saved. If you fall into the former category, don't bother buying the book -- but then, you weren't going to buy it anyway, were you? As for the latter group, rest assured that your investment will not, in this case, be wasted.
What I LikedI've read several other books on Mac OS X. The one I believe everyone should start with is still David Pogue's Mac OS X: The Missing Manual . If you've already read this book (and enjoyed it) or didn't read it but are confident you've already got the equivalent experience, then Mac OS X Hints is a good next step.
Griffiths assumes you're comfortable using OS X for basic tasks: he doesn't tell you how to log in, or what the Dock is. If you're fuzzy on those kind of basics, you're not quite ready for this book (but you're positively crying out for a copy of the Missing Manual). Additionally, he pushes some not-entirely-obvious processes to the introduction, so you don't have to read the same instructions over and over in the meat of the book itself. After all, once you've been told the first time how to view the contents of a package, you're probably all set in that regard. This is one of the aspects of Mac OS X Hints that I found most appealing, actually - Griffiths just explains in the beginning that he's assuming certain things, and then doesn't bother dumbing anything else down.
I've been a fan of macosxhints.com since I first installed OS X, but it seems like Griffiths's style has really improved for the book -- this may be a function of Pogue's role as editor, as the writing in Hints displays the same familiar, comfortable tone while not skimping on depth or details. Like other books Pogue has been involved in, this one is highly readable but not oversimplified.
It seems like the revision process the hints went through during their transition from site to print has been pretty successful, as well -- despite being familiar with the site, there was a great deal of material in the book that I had never seen, even after reading other OS X books. Additionally, the testing involved in the book's creation removes a great deal of the frustration inherent in the site. As much as I like the site, there have been several hints that have mysteriously declined to function on my own system for whatever reason -- but everything I've tried from the book worked without a hitch.
I also enjoyed the fact that this book, like Mac OS X Hacks , is made for sampling. Each article is short and to the point, and while related hints are grouped by chapter, no single tip depends on the reader having already performed one of the others (unless otherwise specified). You don't have to read the book cover to cover -- you can flip around at will without getting lost.
Incidentally, another plus is that 15% of all Griffiths's profits from this book are being donated to the Doernbecher Children's Hospital. That in itself isn't a reason to buy the book, but it's good to know.
What I Didn't LikeIf I can be nitpicky for a moment, I was bothered by the frequency of purely typographical errors. Little things like "than" being used instead of "then," or the bottom edge of a line in a sidebar getting cut off. It didn't keep me from enjoying the book, and I'm sure it's the sort of thing that will get corrected in future printings, but this sort of error occurred often enough that I noticed it, anyway.
Another little thing: I wish URLS had been included whenever a third-party shareware program was mentioned. Of course I know I can Google for DragThing and find it immediately -- but if I'm paying for a book, it seems to me that I shouldn't have to.
There is also the fact that this book is undeniably a book, and that limits it in certain respects (at least when compared to the site). The index is comprehensive and useful, but it's just not as useful as the ability to search the entire text of the book. It's also inevitably dated to a certain degree -- new hints posted to the site, even if they're infinitely more fabulous than ones already present in the book, just won't show up in print for a long time to come. Similarly, if a new version of the OS breaks one of the hints, you'll be able to find out somewhere on the web, but it won't be immediately obvious when you're just reading the book. Of course, these are problems shared by all print technical books, and not just Hints.
One final note: there's a lot of overlap between this book and Mac OS X Hacks, although each book has a significant amount of unique content. If you own one, you probably don't need to get the other, but it's difficult to say which I'd buy if I had to choose. Hacks contains only 100 articles, but they're more in-depth and the tasks they cover are often trickier or less obvious. Hints contains over 500 tidbits, but they're much shorter and often deal with things like key commands that allow you to increase your efficiency, and things of that ilk.
The Bottom LineIf you're the sort for whom time is at a higher premium than money -- maybe you're the kind of person who would buy a boxed *nix distribution instead of downloading it -- then I'd say go ahead and get this book. It's well worth its price as long as you understand that what you're paying for is ease of use and reliability, as well as content. If, on the other hand, you're living on Top Ramen for the foreseeable future, you're probably better off sticking with the site. If you do buy it, I think you'll find it will make a happy addition to your bookshelf -- stick it next to the Missing Manual and dip into it whenever you're sitting through an install or reboot.
You can purchase the Mac OS X Hints from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. -
Mac OS X Hints
emmastory writes "Mac OS X Hints is a brand-spanking new O'Reilly book containing over five hundred 'power tips' and tricks for (amazingly enough) Mac OS X. The tips are culled from the website of the same name, written and maintained by Rob Griffiths. The book is edited by David Pogue, of Missing Manual and Pogue Press fame. It's 461 pages, list price is $24.95, and the O'Reilly catalog page (containing samples from the book) is right here." Read on for emmastory's review. Mac OS X Hints author Rob Griffiths pages 461 publisher O'Reilly/Pogue Press rating 8 reviewer Emma Story ISBN 0596004516 summary The perfect sequel to the Missing Manual, this book contains 500 tips for OS X
Addressing the ObviousThe most immediate question I had when I heard that O'Reilly would be publishing a book containing hints from macosxhints.com was, of course, Why I should get the book when the hints are already on the site for free? Both the author and the publisher also thought of this, understandably enough. Here's how Rob Griffiths answered the question in a post on the site, when the book was first announced: "The book isn't just a 'cut and paste' job from the site-to-print form. Every hint was rewritten and retested from scratch, and hundreds of screenshots were added to help clarify and explain the hints. In addition, many of the scripts and programs posted here are included (the author of each program was contacted for approval to include their original work in the book -- thanks to each of you for agreeing!)."
The response included in the O'Reilly press release for the book is along the same lines: "'The 500-plus hints in this book are based on tips published in the Mac OS X Hints web site,' explains Griffiths. 'But it's not just a rehash of what's there. Every hint has been rewritten, expanded, organized, indexed, tested for compatibility with the latest version of Mac OS X 10.2, and in many cases, illustrated, making the book an even better resource than the web site."
So the question then becomes: is this really the case? Are the differences between the hints as posted on the site and as printed in the book really significant enough to merit shelling out $24.95?
The short answer is that, in my opinion, the book is worth its price. The long answer is (predictably) a little more complicated. There are, of course, people who are more than willing to do the extra digging on the web to get the relevant content for free -- they'd rather do without the little perks (increased readability, revision, testing, screenshots) than spend potential beer money for a glossy O'Reilly book. And that's fine -- I'm more than sympathetic with this position, being frequently hard up for beer money, myself. But of course there are also people for whom the convenience is just as important as the cost, and who consider the price of the book well worth it in terms of the time saved. If you fall into the former category, don't bother buying the book -- but then, you weren't going to buy it anyway, were you? As for the latter group, rest assured that your investment will not, in this case, be wasted.
What I LikedI've read several other books on Mac OS X. The one I believe everyone should start with is still David Pogue's Mac OS X: The Missing Manual . If you've already read this book (and enjoyed it) or didn't read it but are confident you've already got the equivalent experience, then Mac OS X Hints is a good next step.
Griffiths assumes you're comfortable using OS X for basic tasks: he doesn't tell you how to log in, or what the Dock is. If you're fuzzy on those kind of basics, you're not quite ready for this book (but you're positively crying out for a copy of the Missing Manual). Additionally, he pushes some not-entirely-obvious processes to the introduction, so you don't have to read the same instructions over and over in the meat of the book itself. After all, once you've been told the first time how to view the contents of a package, you're probably all set in that regard. This is one of the aspects of Mac OS X Hints that I found most appealing, actually - Griffiths just explains in the beginning that he's assuming certain things, and then doesn't bother dumbing anything else down.
I've been a fan of macosxhints.com since I first installed OS X, but it seems like Griffiths's style has really improved for the book -- this may be a function of Pogue's role as editor, as the writing in Hints displays the same familiar, comfortable tone while not skimping on depth or details. Like other books Pogue has been involved in, this one is highly readable but not oversimplified.
It seems like the revision process the hints went through during their transition from site to print has been pretty successful, as well -- despite being familiar with the site, there was a great deal of material in the book that I had never seen, even after reading other OS X books. Additionally, the testing involved in the book's creation removes a great deal of the frustration inherent in the site. As much as I like the site, there have been several hints that have mysteriously declined to function on my own system for whatever reason -- but everything I've tried from the book worked without a hitch.
I also enjoyed the fact that this book, like Mac OS X Hacks , is made for sampling. Each article is short and to the point, and while related hints are grouped by chapter, no single tip depends on the reader having already performed one of the others (unless otherwise specified). You don't have to read the book cover to cover -- you can flip around at will without getting lost.
Incidentally, another plus is that 15% of all Griffiths's profits from this book are being donated to the Doernbecher Children's Hospital. That in itself isn't a reason to buy the book, but it's good to know.
What I Didn't LikeIf I can be nitpicky for a moment, I was bothered by the frequency of purely typographical errors. Little things like "than" being used instead of "then," or the bottom edge of a line in a sidebar getting cut off. It didn't keep me from enjoying the book, and I'm sure it's the sort of thing that will get corrected in future printings, but this sort of error occurred often enough that I noticed it, anyway.
Another little thing: I wish URLS had been included whenever a third-party shareware program was mentioned. Of course I know I can Google for DragThing and find it immediately -- but if I'm paying for a book, it seems to me that I shouldn't have to.
There is also the fact that this book is undeniably a book, and that limits it in certain respects (at least when compared to the site). The index is comprehensive and useful, but it's just not as useful as the ability to search the entire text of the book. It's also inevitably dated to a certain degree -- new hints posted to the site, even if they're infinitely more fabulous than ones already present in the book, just won't show up in print for a long time to come. Similarly, if a new version of the OS breaks one of the hints, you'll be able to find out somewhere on the web, but it won't be immediately obvious when you're just reading the book. Of course, these are problems shared by all print technical books, and not just Hints.
One final note: there's a lot of overlap between this book and Mac OS X Hacks, although each book has a significant amount of unique content. If you own one, you probably don't need to get the other, but it's difficult to say which I'd buy if I had to choose. Hacks contains only 100 articles, but they're more in-depth and the tasks they cover are often trickier or less obvious. Hints contains over 500 tidbits, but they're much shorter and often deal with things like key commands that allow you to increase your efficiency, and things of that ilk.
The Bottom LineIf you're the sort for whom time is at a higher premium than money -- maybe you're the kind of person who would buy a boxed *nix distribution instead of downloading it -- then I'd say go ahead and get this book. It's well worth its price as long as you understand that what you're paying for is ease of use and reliability, as well as content. If, on the other hand, you're living on Top Ramen for the foreseeable future, you're probably better off sticking with the site. If you do buy it, I think you'll find it will make a happy addition to your bookshelf -- stick it next to the Missing Manual and dip into it whenever you're sitting through an install or reboot.
You can purchase the Mac OS X Hints from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. -
ASCII QuickTime Movie Player
EccentricAnomaly writes "Do you wish you had some more CLUI multimedia apps? Well, over at Mac OS X Hints I found this link to Apple's sample code for an ASCII QuickTime movie player. So grab some popcorn, make Terminal full screen, and watch some movie trailers the way ubergeeks were truly meant to." You can watch movies over remote login to another box, too, though the sound will come out of the host computer, not the client ... -
Ogg Support For iTunes
-
Multiple Monitors for iBooks
nevershower writes "I found this while reading MacOSXHints. It's a firmware script for Radeon iBooks that allows them to use monitor spanning! DO NOT run this script if you have a Rage iBook. It might permanently bork your laptop." Borking is bad, especially if it is permanent. -
Learning UNIX for Mac OS X
Spencerian writes "I've become quite accustomed the depth of co-author Dave Taylor's writing on UNIX in previous books such as Teach Yourself UNIX in 24 Hours . As you can note from Dave's recent writing credits, his experience and knowledge of UNIX is vast and varied. That said, I was mildly disappointed with this latest offering that discusses the UNIX underpinnings of Mac OS X." Spencerian explains the logic underlying that conclusion in his complete review, below. Learning UNIX for Mac OS X author Dave Taylor & Jerry Peek pages 139 publisher O'Reilly and Associates, Inc. rating 7.5 reviewer Spencerian ISBN 0596003420 summary A good first-reference for new UNIX users, but steer clear if you're a UNIX vet.For starters, I was annoyed to find that the book's title implied a larger format than the 139 pages it comprises. The book has an audience problem because of its size. UNIX guys like thick books. Is this book mostly for newbies to OS X, to UNIX, or to Mac OS X's implementation of UNIX? Despite this targeting problem, the book's contents are still useful, but I think its audience is more geared to new UNIX users. The book just doesn't have much depth for even a reference title, especially for a topic such as UNIX, and particularly for a new, little-documented UNIX family operating system such as OS X.
While Mac OS X is a BSD variant, it has a few idiosyncrasies that may throw off a veteran UNIX user, and this book manages to address most, if not all of these notable problems. For instance, Dave notes problems in sendmail that prevent it from working from the command line in Mac OS X's Terminal application, and presents a fix for the problem. If you use command lines in UNIX all the time, the book does present good instructions on getting Lynx, IRC, newsgroups, pine, and the like up and running in Terminal. The book shies away (quite appropriately) from any graphic interface items unless required, such as when changing Terminal's preferences.
This book was very recently published (May 2002) but already has fallen behind with the release of Mac OS X 10.2 (Jaguar). Some components of Jaguar, such as CUPS support for stronger printing options, are completely missing from this book. If you have Jaguar installed on your computer, don't dive headlong into the NetInfo Manager steps for LPR printer configuration. Books typically don't age this fast, but in the case of this book, small changes seem to mean a lot to this title's usefulness -- the introduction of CUPS may have made Chapter 5's contents almost irrelevant.
Another small nag involves the lack of information on useful commands for Mac OS X users that weren't available (or were difficult to find) with the old Mac OS 9. One such command, cron, makes my life easier for handling some tasks on my home computer. It's not even mentioned in this book, nor will you find much information on shell scripting or compiling UNIX code you might happen to find. I guess I'm most annoyed at the lack of compile information since the Apple Developer Connection marked this book as a Recommended Title.
Despite our fondness for (and tolerance of the slightly-higher prices of) Macintosh computers, Mac users aren't made of money and don't like to buy a bookstore's worth of tomes for basic information. It would have made a lot of sense to talk more about compiling software since Apple's software or other GUI products don't meet or can configure all UNIX needs. And I won't even talk about the lack of coverage about XDarwin, an application that starts XFree86 within a Mac OS X installation, allowing X Window applications to run atop or in tandem with the OS X interface. XDarwin has become popular enough for it to become part of the stable XFree86 distribution. Given that not every UNIX user is a command-line freak, this is a pretty critical omission in my mind.
So, who should buy this book?
If you are completely new to UNIX and have been a gooey-kiddie who's used almost nothing except Mac OS 9, this is a very good reference to get your toes moist with UNIX. However, as drug dealers say, "the first taste is free." This book will leave you wanting more detailed information. More experienced UNIX users can probably find out what they need about Mac OS X's command line from a few free locations such as Mac OS X Hints.
One last thing: A pox upon Tim O'Reilly for not using the platypus for the animal on the book's cover. Given that the open-source core operating system of Mac OS X is named Darwin and has a nicely-modified take-off on the BSD mascot that depicts both the name of the OS and its BSD origins, I would think that O'Reilly would have jumped on this obvious cover.
You can purchase Learning UNIX for Mac OS X from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page. -
Use Your Mac to Share iCal Calendars
mcwetboy writes "Calendar publishing with iCal requires a .Mac membership or a WebDAV server. Most ISPs and hosting companies don't offer WebDAV -- or at least mine don't -- but you can run WebDAV under Apache on your Mac, and publish calendars and share them among a local network or among multiple users of a single computer. Already two different tutorials explaining how to do this have appeared on the Web: this one at Mac OS X Hints and this one courtesy of Shawn Wall. I'm sure Slashdot readers could offer even more suggestions." I set up mod_dav for the first time within an hour of downloading iCal the other day, with help from this article. Now, if only iCal weren't really slow and buggy ...