Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Fixing a dodgy update' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Fixing a dodgy update
Authored by: Thom on Sep 21, '02 02:18:02AM

Yeah, I have done this too -- most noticeably when trying to get old OS X Servers from 10.1.2 to 10.1.5, or sometimes just when the software update dies halfway through but then claims there's no new updates because it already wrote the new version string in a plist somewhere, or something. Grr, I hate that kind of thing. If OS X's update process has failed on me a number of times like that, I feel entitlted to wish that it'd save a cumulative 'undo' in case it bombs halfway through. Caveat Emptor, I guess...?

But remember: you can't always drag and drop those files where they belong. So you're probably better off doing it from the Terminal. There, you can see who owns them, what the perms are supposed to be, and so forth.

Also, bear in mind that if you use Terminal, some files you'll need to copy to the proper place are going to have resource forks, so use /Developer/Tools/CpMac, etc, or ditto -rsrc or whatever depending on the situation at hand. And if something's owned by root but still needs updating, then just use sudo to be root temporarily to make the command work.

All in all, I like the whole alias to invisible files idea proposed here. It's a very good idea and worth thinking about as preventative maintenance, because when those folders show up next time you're expecting to see brand new apps, you'll kick yourself.



[ Reply to This | # ]