|
|
10.5: Solve a repair permissions issue after 10.5.8 update
This is yet another example of the misuse of repair permissions. For reasons unknown, many users believe they should repair permissions immediately before, immediately after, and sometimes during (by intercepting the restart) system updates. These mistaken beliefs are often accompanied by the beliefs that you should restart the Mac in Safe Boot mode before updating the OS, and that you should force a Safe Boot for the first restart after updating.
10.5: Solve a repair permissions issue after 10.5.8 update
In your opening you say,
10.5: Solve a repair permissions issue after 10.5.8 update
No kidding. Here's how I do it:
Agree
I also just install updates via Software Update. I only run permissions repair when I get bored or when I have reason to believe it might be necessary (as in after the last Flash update, which as reported by others did screw up a couple of permissions).
10.5: Solve a repair permissions issue after 10.5.8 update
I don't use Software Update because it has too many problems. The biggest one is attempting to update from an incomplete install file.Apple's Software Update will never attempt an install of an incomplete install file. The first step after downloading the file is to check the checksum of the file. An incomplete file will always fail and will be rejected. I have only once had a problem with an update from the automated update system and the problem was that the update failed to download every time. Manually downloading and installing that update solved the problem.
10.5: Solve a repair permissions issue after 10.5.8 update
"My cargo cult is better than yours!"
10.5: Solve a repair permissions issue after 10.5.8 update
There is some contradiction there, DrT. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|