I was surprised that this didn't get uncovered sooner, because I was expecting something like this. Apple has had one of these major bugs with every major release since 10.3, except in the past it was a problem in the .0 release that got fixed with a very small (and VERY quickly released) .1 fix. 10.3.0 had the problem of instantly corrupting FireWire 800 drives whenever they were connected and resulted in probably the tiniest update package ever (10.3.1 was something like 650 KB); 10.4.0 had the issue of corrupting a user's entire profile if they had more than 2 GB of data and FileVault was enabled; and 10.5.0 had a bug of similar severity that I can't remember the moment. Sigh...
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
I was surprised that this didn't get uncovered sooner, because I was expecting something like this. Apple has had one of these major bugs with every major release since 10.3, except in the past it was a problem in the .0 release that got fixed with a very small (and VERY quickly released) .1 fix. 10.3.0 had the problem of instantly corrupting FireWire 800 drives whenever they were connected and resulted in probably the tiniest update package ever (10.3.1 was something like 650 KB); 10.4.0 had the issue of corrupting a user's entire profile if they had more than 2 GB of data and FileVault was enabled; and 10.5.0 had a bug of similar severity that I can't remember the moment. Sigh...
Well given all that, I would rather risk a virus that I'm not going to catch vs all my data gone