Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!yale!umich!terminator!dabo.ifs.umich.edu!rees
From: rees@dabo.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: disk copy
Message-ID: <1990Mar29.150513.12314@terminator.cc.umich.edu>
Date: 29 Mar 90 15:05:13 GMT
References: <40087@iuvax.cs.indiana.edu>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 25

In article <40087@iuvax.cs.indiana.edu>, houghton@iuvax.cs.indiana.edu
(Ric) writes:
> 
>    Is there anyway to do a complete diskcopy from one disk to another?
>  
>    It doesn't seem possible to do this with wbak/rbak, but I may be 
>    missing something.
> 

"cpt -pdt -sacl" should do it.  Or "tar A |tar A".  Maybe even cpio.  And
wbak/rbak should do it too, but I've never been able to figure out how to
use them.  Or you could do "dd if=/dev/wn0a of=/dev/wn1a" (just kidding; it
will work but it's not what you want).

You'll run into problems if you try to move a bootable volume this way.  Be
particularly careful of /sysboot.  If you accidentally delete it, I don't
know of any way to get it back.  The boot prom doesn't find it by going
through the file system, it's got the block numbers (2-11) hard-wired.
Domain_OS tries to protect you from shooting yourself but I'm not sure
whether it always succeeds -- it may be possible to remove the name even if
you can't delete the blocks.

Then there is a bunch of other stuff, like the hint file, that will confuse
the OS if you just copy it.  If you know what you're doing it's possible,
but I would strongly recommend you re-install.  It doesn't take all that long.