When bad things happen to good Mac's [OT]

[Joseph E. Sacco, PhD]

Thank you, Clint.

I have been working with MAC's for a very long time so I have a
understanding [read lots of scar tissue...] of Apple's failings.  

It is because of this sort of "voodoo" [B-Tree corruption that Apple
cannot repair, but a third party can???] that I run YDL.

There is a set of desktop applications that I need to do day-to-day
stuff. Slowly, but surely, Linux has been filling out that set with
"acceptable" alternatives.  Once the Linux desktop set is complete to my
satisfaction,  I would need a really good reason to run anything else.


-Joseph
===============================================================================


On Wed, 2005-07-20 at 14:47 -0500, Clinton MacDonald wrote:
> Dr. Sacco:
> 
> That's a nice story with a happy ending (fortunately).
> 
> Joseph E. Sacco, PhD wrote:
> > Had an OS X 10.3.9 disaster the other day. OS X was no longer
> > able to boot.
> > [...]
> > (4) purchase copy of "Disk Warrior" 3.0.3.
> > 
> > (5) run Disk Warrior.
> > 
> > ==> all is  well once more.
> 
> I have heard or read dozens and dozens of anecdotal stories in which 
> DiskWarrior saved someone's bacon. In fact, I have heard so many 
> stories, that I have never had an instance of needing DiskWarrior: I run 
> "fsck -fy" (or Apple's Disk Utility) followed by DiskWarrior on all my 
> Macs about once a month as a preventative maintenance measure.
> 
> (For what it is worth, versions of Mac OS X prior to 10.3 used to report 
> multiple errors with fsck *and* DiskWarrior on every run, even after 
> just a few days. With more recent versions of Mac OS X, these errors are 
> increasingly rare.)
> 
> Good luck with your computing, both Mac OS and Linux!
> 
> Best wishes,
> Clint
> 
-- 
joseph_sacco [at] comcast [dot] net