Late last night my MacBook attempted to install and update itself to the most recent version 10.4.11. After downloading the file a scary message about ‘failed install’ and ‘remove package from trash and try again’ appeared. Then applications started not launching, and a normal reboot resulted in the spinning spinny-thing of despair. Booting to single-user mode showed the process stalling midway with the following.
Load of /sbin/launchd, errno 88, trying /sbin/mach_init
Load of /sbin/launchd failed, errno 88
Fortunately searching for ‘launchd, errno 88′ took me to the blog of Igor Minar, who dealt with the same issue on 10.4.9. I am thankful that the iPod Touch has a fully fledged browser built in which I could read it from while doing the deed1.
The first try or two I must have had typos as it did not work, but eventually I got to the installer GUI which allowed me to apply the update. Incase anyone else tries this, it took a long time to boot first time after the fix.
The more user friendly solution which I didn’t think of at the time would have been to boot from my SuperDuper backup, and download and apply the combo update to the laptop drive from there. One to remember for next time as 4:30am is not a good time to be typing complex things into Terminal2.








Hmmm. Interesting. I clicked on the update button absentmindedly too, as you do. The pooter eventually froze and I was presented with the beachball of death. However being a luddite (but admittedly after trying a couple of things) I merely switched it off and switched it on again. It took an unconscionably long time to boot up causing small flutters of anxiety but eventually all reappeared. I checked for software updates in case the update hadn’t “taken” but was told there was nothing new available. So I just assumed it was a problem with my laptop (which has a couple of annoying idiosyncrasies anyway) and went on my merry way. I’m glad I hadn’t read your post before I upgraded otherwise I wouldn’t have done so at all. Talk of the command line makes me feel faint
PS Why does it tell me, when I post a comment, that it’s 37 years and 10 months later? Later than *what*?
37 Years 10 months has got to be about the time the UNIX date system came into use, so it might be doing something based off that (AKA I have no idea but reloading the page makes things ok
)
Bit more research: UNIX takes the time from 1970-01-01 00:00:00 and since the page is not fully refreshed (only via AJAX), I am guessing my ‘time_since’ function does not have WPs ‘the_date’ to work from, so defaults to working from 1970-01-01.