OK, I'm frustrated. I want to use OSX, badly. But I can't put it into production until I can do the following:
1) copy my entire production disk to a firewire image, hopefully without copying already existing files to save time 2) erase my main disk (simulating a total disk failure, or a repartitioning) 3) copy it back 4) boot using the new copy I've been using Retrospect to do this. Of course, the copy when it comes back has bad aliases, but at least I was able to boot and get to the stage of fixing the aliases (using FileBuddy, usually). Now OSX comes along, and aliases are used from the moment of boot! /etc is an alias to /private/etc. I can't even wake up! I can't use rsync, because unix tools don't see the resource fork, and I will still have many Classic apps for a long time to come (like Framemaker) that are mission critical. So what are other people doing? Do I continue using retrospect, and figure out some way to relink all the broken links? Perhaps using macperl? I can't be the ONLY one who is messed up on a complete restore after a repartitioning or catastrophic failure. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[EMAIL PROTECTED]> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
