Reply to thread

Message

<blockquote data-quote="Brown Study" data-source="post: 406705" data-attributes="member: 3889">Lots can go wrong. If nothing ever did, there would be no need for the disk utility or fsck -fy.Yesterday I ran Applejack in the AUTO mode, and it found a minor error, an orphaned file that it discarded. Twice it's found corrupted preferences files. Once in a while it otherwise repairs/modifies the system files (it uses fsck -fy) but like fsck -fy, it doesn't say what was fixed.Some software updates wreck the permissions. iTunes updates always do on my machine — not just one or two but a list as long as your arm.I've never had a need for DiskWarrior or anything&nbsp; beyond Onyx and/or MainMenu and running the crons. I run Applejack or the others regularly to keep the small anomalies from snowballing.This ignoring the so-called heavyweight repair utilities and their constant upgrades needed with systems prior to OS X has been successful ever since I went from 9 to 10.2.</blockquote>

[QUOTE="Brown Study, post: 406705, member: 3889"] Lots can go wrong. If nothing ever did, there would be no need for the disk utility or fsck -fy. Yesterday I ran Applejack in the AUTO mode, and it found a minor error, an orphaned file that it discarded. Twice it's found corrupted preferences files. Once in a while it otherwise repairs/modifies the system files (it uses fsck -fy) but like fsck -fy, it doesn't say what was fixed. Some software updates wreck the permissions. iTunes updates always do on my machine — not just one or two but a list as long as your arm. I've never had a need for DiskWarrior or anything beyond Onyx and/or MainMenu and running the crons. I run Applejack or the others regularly to keep the small anomalies from snowballing. This ignoring the so-called heavyweight repair utilities and their constant upgrades needed with systems prior to OS X has been successful ever since I went from 9 to 10.2. [/QUOTE]

Verification

Name this item 🌈