SiliconAddict said:
Must...avoid...temptation....to leap....through....screen
ARRRRGH. Who gives a crap about uptime.
I had the same reaction, but it's possible she's running a server where it's not just the little "uptime" number she's interested in as a novelty, but the true uptime of her server and the services on it.
It if it a server, then reboot it twice and play it safe...
bigmc6000 said:
My point is that I didn't need to EVER take it on long trip, disk utility made it do something that I never do. Regardless of it there was a pre-existing condition it made my HD perform irregullarly and thus exposed an otherwise unknown error.
To use a better analogy, it took my car that I will never take above 90 to about 110 and ran it there for a while. Mechanically speaking you are going to see a lot more stress and maintenance issues running at 110 than you are at 90..
You'll see the stress and maintenance issues sooner at 110, but you'll see them eventually at 90. If you never take the long trip, then it will fail after many short trips to the grocery store.
I don't know whether disk repair FUBAR'd your disk or not, maybe it did, but don't go on thinking that ignoring little bits of disk damage is fine as long as you don't push it real hard... The longer your disk is at risk, the more data it collects and the more you loose when the whole house of cards collapses because of a mechanical or logical failure.
FoxyKaye said:
LOL - you say that, but I'm always surprised by how many people simply don't. Apple certainly doesn't tell the everyday user that repairing permissions is a regular part of system maintenance.
Repair permissions is meant as a cleanup tool for badly behaved, third party applications. John's Killer Tetris sets global permissions on your home directory so it can write it's high score file, and repair permissions sets it back.
Personally, my take is that if running repair permissions before or after an update makes any difference at all, then Apple messed up their installer.
They are either overwriting files, deleting files, or adding files. In any of those cases, they have control over the files' permissions and should get it right the first time.
If Apple really thought this was a necessary, or even advisable, step they'd include it in the install script themselves-- like they do for prebinding optimization.
That said, if you find that you have less problems by running it than you do by not running it, by all means do so...
