It's because Time Machine requires various new features in the
AFP server in order to ensure end-to-end data integrity, and the
AFP server in the firmware of the AEBS doesn't provide those
features. So if you don't really care about whether your data
was actually safely and correctly backed up to the disk
connected to your AEBS, then hack away... but if you care about
the integrity of your data, don't do it.
For those of us who are not savvy about this kind of thing, how
can I know data I copy manually to such a drive is correct and
Time Machine can't?
In other words, he's saying that the AEBS is seriously flawed and
that Apple knows it. Also, it would mean that Apple doesn't care
about people losing there data or having it corrupted, except when
using TimeMachine, however. If the AFP server in the firmware of
the AEBS doesn't ensure data integrity, then they should never have
been sold.
Well, I hate to jump to that conclusion, and it wouldn't make a lot
of sense to me that they'd worry about reliability with Time Machine
if they couldn't guarantee reliability with other data transfers.
Like I said, I'm not savvy about this kind of stuff. It just seems
odd to me that the Finder can verify that data transfers have taken
place reliably when Time Machine can't. Based on what Eric said, I'm
guessing Time Machine uses newer, slicker mechanisms to do those
verifications than the Finder or whatever part of the system does
them with a normal file copy, and the newer, slicker stuff doesn't
work with the AEBS yet. Just my guess, though.
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
