Pants Full of Unix

Is this even English?

The first thing you'll probably want to to is get the source to build cleanly without using RPM. To do this, unpack the sources, and change the directory name to $NAME.orig. Then unpack the source again. Use this source to build from.

Wait, what? I mean, I'm even letting the complete Fail at 5th grade grammar go, but I'm supposed to unpack the sources, then change to a directory dependent on a shell variable I haven't set, and then… unpack the sources that are off somewhere else? Again? (So why'd I do it the first time?) I guess, targeting my current working directory?

Really, I'm not asking for proper technical documentation here: I know that you're working from your step-mother's basement, but you could at least try to be clear. This isn't your fucking blog. This is, ostensibly, Official Documentation.

Jesus mother Christ fucking a pogo stick.

Mac OS X 10.5 (Leopard)'s Spaces is conscious of multiple monitors. To the extent that if you hit its “preview all desktops” button with more than one monitor, it shows you the content of all of those monitors for all desktops.

Until I noticed this, I figured Apple was just playing catchup to Microsoft's deskman.exe XP powertoy (possibly by incorporating their user community's product, see below), but clearly this is a leapfrog, if an obvious one.

Before 10.5 I was using Virtue for this. It remains more extensible than Spaces, but it doesn't actually do anything extra I need, and it absolutely doesn't let me see everything on all desktops at the same time, so it's kicked to the curb.

While Time Machine has been much-ballyhooed, it is not exactly a backup product (it provides continuous data protection—provided you keep the extra hard drive that you MUST use for Time Machine to work at all connected at all times), nor is it a host imaging product. It's good for “damn, I didn't mean to change that file that way”, but it's not clear that it's all that hot for “restore this system to a default image” (like you'd want in a lab environment) nor for “the system is completely fragged” (say, from an OS upgrade gone wrong).

In those cases, one wants something more like what described a couple of months ago, except that he's missing a few steps necessary to make the resulting disk bootable that Brad Bergeron includes in his description of how to make a bootable USB key with Mac OS X (possibly a handy tool).

First, when you format a new HFS+ drive, it's easy to not enable the “owners enabled” setting. I'm hazy on exactly what that setting really means (thanks for acting like MS, Apple), but I have the impression it means that any user on the host can read all files on the attached disk, rather like mapping anonymous users to root for NFS. I'm taking Brad's word for it that this needs to be changed for Mac OS X to boot from the volume, but it stands to reason. You fix that with the /usr/sbin/vsdbutil command (which, apparently, doesn't have a man page). You probably only need to do this once per volume, but it doesn't take any time or hurt to explicitly activate each time, so whatever.

Second, after copying data to the volume, one must bless(8) the CoreServices directory in the System Library, which enables the BootX application in that directory on that volume and puts the EFI appropriate for booting the OS based in the CoreServices directory on the disk in question.

So, now my backup script for my two Mac laptops (one already upgraded to 10.5, since if the upgrade fragged it I'd just reinstall—its primary use is to run the stereo, one on which I'm making sure I've got a bootable fallback before I do the same) looks like this (modulo actually having most of this in shell variables):

target=/Volumes/whatever
vsdbutil -a $target
rsync -avxE –delete –ignore-errors / $target
bless –folder “${target}/System/Library/CoreServices” –bootinfo –verbose

recommends rsyncing to a hard drive that you can physically swap into your system. That's perfectly sensible advice, but it's not totally necessary. With Intel Macs, you should be able to choose an exernal disk (FireWire or USB) in the “Startup Disk” System Preference or by holding down option as the system boots (these are the same ways you switch into BootCamp, of course). With a PowerPC Mac, Brad believes you need to do the normal OpenFirmware thing that should be old hat if you've run a BSD or Linux distribution on a PowerPC Mac before. Essentially, boot into OF (apple-option-O-F), locate the device from which you want to boot in the devalias output (it may be easier to find this path if you've previously looked at the device list in System Profiler), and ether setenv boot-device to it or just boot the path directly. Brad points to this article, which does an adequate job explaining (though it does get the OpenFirmware key combo wrong, in a rather obvious way: you can't hold the F key down twice). I didn't actually check before the 10.5 upgrade on my Powerbook, but it sure seems like the “Startup Disk” System Preference exists and lets me choose my properly formatted (FireWire 400-connected) external drive with a 10.4 backup of the MacBook Pro's installation on it…

Yes, there is a “recover from Time Machine” choice somewhere (in the 10.5 install media, I think?), and maybe it works, but I'm certain this works and I actually know what it's doing under the covers. It's simple. Simple is good for backups of last resort.

And yes, , I just tested this and it's what you needed to do when you couldn't get your just-rsync backup disk to work.

Update: At some point, tacked on the bit about needing to not ignore owners at the bottom of his post; I'd only gone back to it and skimmed down to compare notes on rsync(1) flags since my initial reading, so I missed that. Also, bless(8) is apparently not necessary for him or most of the people doing what he suggests, but I still think it's a Good Idea, after reading the documentation. It can't hurt and it might help.

On Hallowe'en or the day before (I don't quite recall, and I'm not positive I sync'ed the photos–only one is necessary to show everything here, really–off the iPhone the same day), I saw this parked outside my employer's office building:

That's the corner of 9th and Market streets (and yes, it's a legal parking space, though it's kind of in the way during rush hours; yes, the meter had plenty of time left). There are some gaps in the Philly streetview (my street for example, which only fits one car and is often blocked, but also some streets it's difficult to turn into if you're just driving around, and then huge swaths of the greater Philadelphia area, while others are pretty well covered–here look), including some area right nearby that parking space. Here's the parking spot in question, but note all the streets without blue lines nearby.

There is, of course, no camera actually mounted on the roof rack on the car pictured here, but the car was also unattended, so it only makes sense that they took it down. (It wasn't in the front or back seat, I'd presume in the trunk or taken along.) But it fits the descriptions I've read of Google cars in the past and it's got Mass plates (not something one sees all that frequently in Center City Philadelphia, though they're more common in University City where there are more students).

So what's the deal? Is Google back filling in the holes? They've certainly been adding more cities with Streetview pretty regularly lately.

Does this picture look familiar? That's right, I marked it mislabeled, sent it back, they received it, I went in and re-added it, bumped it to the top of my queue (the same day they received it, before anything shipped)… and I got exactly (I expect, but maybe they're just duplicating the wrong grey disk for the 1988 version) the same wrong DVD.

This time I called. We'll see.

Update: I'd already re-reported the “wrong disc, right sleeve” thing in the way I have in the past before I called. The operator took down the dates of the previous problems and said she'd ship out a replacement right away. How do you suppose that replacement shows up in my queue? Yep, you guessed it: damaged. So, clearly, if you don't want the hassle of having to wait and then re-add a movie when this happens, you should just claim it was damaged. Great example.