Slashdot Mirror


Mac OS X Update 10.2.4 Resets

Oculus Habent writes "It may just be me, but 10.2.4 reset a number of settings on my computer, including icon sizes, window positions, and dock size and contents. Minor annoyances, but completely unnecessary. Is anyone else experiencing this?" As for me, Apple re-added some apps to my Dock and overwrote all my changes to httpd.conf (though it did back it up first) to add mod_rendezvous_apple. But those problems pale in comparison to some others: Anonymous Coward writes "If you upgraded your Mac desktop to 10.2.4 last weekend, check your date and time. Many users have suddenly found it to be 4:00 PM, December 31, 1969 again. Apparently, this happens whenever they are shut down or restarted, and resetting the motherboard and/or the PRAM doesn't fix it. Complaints have been piling up at Apple.com and prices for batteries have been skyrocketing - but relax. It's not your battery!"

2 of 135 comments (clear)

  1. zero problems for me by Anonymous Coward · · Score: 5, Informative

    Everything worked fine for me. Nothing reset, no changes to the Dock. I don't know if it makes a difference but I downloaded the tar file directly and ran the update later, rather than using Software Update.

    Haven't seen any time/date changes, but my clock is set by NTP anyway.

    PS: One thing I like to do before any major update is run something like "find -s / > /tmp/filelist" to get a list of all files and dates. Then run it again after the update and diff the two lists. That will show you httpd.conf changed, for instance. Also it's just interesting to see what files change on the machine as I learn about the OS. You can also get lists of files from the archive itself or from the "bill of materials" file ("man lsbom") after installation.

    PPS: does anybody know what the file /iNode12022737 is for? I keep seeing files like that in the root dir...

  2. Re:Protecting your OS from changes by Visigothe · · Score: 4, Informative
    I'm guessing the installer/updater plays along with the *NIX user system, right? So what about "chmod a-w httpd.conf" for protecting your httpd settings? If you don't want your settings modified by Apple, use the power of *NIX against it!

    That won't work, as in order to update the system, you must supply the admin password. The admin [root, but not exactly] can do anything.