OK, so I take half of it back! This is a really slick device, but it was decidely not "done right". Turns out WD didn't format the drive properly on many of these units, resulting in a journal failure which can't be fixed with fsck (which requires some trickery all by itself since 30 MB of RAM isn't enough to fsck 1 TB!), and requires a reformat! Now... that's ok for me... but what about their target audience? Since it's considered a hack just to get ssh going, just how exactly is Joe User supposed to recover from this:

<1>journal_bmap: journal block not found at offset 1036 on md4
<3>Aborting journal on device md4.
<2>EXT3-fs error (device md4) in ext3_new_inode: Journal has aborted
<4>__journal_remove_journal_head: freeing b_frozen_data
<4>__journal_remove_journal_head: freeing b_frozen_data
<2>EXT3-fs error (device md4) in ext3_create: Journal has aborted
<2>ext3_abort called.
<2>EXT3-fs error (device md4): ext3_journal_start_sb: Detected aborted journal
<2>Remounting filesystem read-only

I found a new resource for others looking at Hacking WD MyBook World Ed. Check it out, all you need to know - it will even run CUPS and MediaTomb! So I guess I should thank WD for screwing up the device so bad, otherwise the prices wouldn't have dropped and I'd be stuck with a USB attached dumb-drive :-)