Mac OS X: 10.3.4 update

Posted by Pierre Igot in: Macintosh
May 28th, 2004 • 5:10 am

After waiting for a couple of days in order to make sure that the update was not too risky to install, I did my usual little routine:

  1. restart from DiskWarrior CD
  2. rebuild directory on startup volume with DiskWarrior CD
  3. restart from startup volume with Shift key down (in order to prevent start up items from launching)
  4. launch Disk Utility
  5. repair permissions on startup volume
  6. quit Disk Utility
  7. apply Mac OS X 10.3.4 Combo updater
  8. restart
  9. repair permissions on startup volume one more time

Everything went smoothly and I am now back in business. All told, it takes about half an hour, but it’s better than experiencing nasty surprises due to some obscure bug related to some kind of invisible directory/permission damage.

The only thing of note is that the permissions repair process produced the following both before and after installing 10.3.4:

Repairing permissions for “Core”
Determining correct file permissions.
We are using special permissions for the file or directory ./System/Library/Filesystems/cd9660.fs/cd9660.util. New permissions are 33261
The privileges have been verified or repaired on the selected volume

Permissions repair complete

If I am not mistaken, this particular “problem” has been with us for a while. I don’t know what’s wrong with this particular “cd9660.util” file, but obviously something doesn’t agree with the permissions repair process. Surely Apple is aware of this. A search for “cd9660.util Mac OS X” on Google returns all kinds of stuff.

It’s just sloppy that it hasn’t been fixed yet. Oh well. If that’s all the trouble I am going to get from the update, I am not complaining.

2 Responses to “Mac OS X: 10.3.4 update”

  1. Josh says:

    I noticed that one of the fixes in 10.3.4 is for — it no longer launches multiple instances of the app. Huzzah!

  2. Pierre Igot says:

    Yes, this fix has been pointed out to me, since I was one of those people experiencing the multiple instances of Backup. Interestingly, however, the reason given by Apple for the bug (failed backups) was not, as far as I could tell, the reason for the bug in my setup. In addition, I frequently had 3 or even 4 copies of Backup launching at the same time.

    I even got an e-mail from Bug Reporter asking me to confirm that the bug is gone in 10.3.4.

    The thing is, after I replaced my internal hard drive, the problem disappeared for me, even in 10.3.3. So I have no way of confirming that it’s gone in 10.3.4.

Leave a Reply

Comments are closed.