User Tools

Site Tools


how_to_clone_tru64_and_digital_unix

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
how_to_clone_tru64_and_digital_unix [2018/12/11 15:42] sgriggshow_to_clone_tru64_and_digital_unix [2018/12/11 16:02] – [Fix the rc.config] sgriggs
Line 200: Line 200:
  
 So, the bottom line is that you /might/ not have to alter the **/etc/fstab** if you run AdvFS because it abstracts the name of the disk. The system startup scripts refer to **root_domain** and **usr_domain** so __do not rename them__. So, the bottom line is that you /might/ not have to alter the **/etc/fstab** if you run AdvFS because it abstracts the name of the disk. The system startup scripts refer to **root_domain** and **usr_domain** so __do not rename them__.
 +
 +==== Fix the rc.config ====
 +
 +The **/etc/rc.config** file is the main configuration file for Tru64 and Digital Unix systems. This file may contain a reference to swap which may tie the system back to the old disk. This needs to be altered or removed. You should edit the file, but be aware of something else. You don't want to edit the rc.config file if it's the one in use on your booted system. For a running system, you need to use a tool called **rcmgr** to make changes. However, because the cloning process generally has an opportunity to edit the cloned files before they are in use, you don't have to worry about this fact. You can simply make edits to the file and when it's used by the system at the time when you try to boot the clone, your edits will all be baked in. 
 +
 +The main thing you are looking for is any reference to swap on the old disk. It will occur in some kind of variable name and you can simply remove the whole line, or edit the line to point to your new disk's swap slice. The name of the variable will be something like "SWAPDEVICE=/dev/rz0b"
 +
 +Both Tru64 and Digital Unix (but especially Tru64) have a hardware registry which will store the names of disk devices that are seen by the system. In most cases, once a disk is seen, it's name will not change even on the cloned disk (the registry will be copied over at the same time during the file copy steps).  
 +
 +==== Fix the Sysconfigtab ====
 +
 +Another file you //might// have to alter is your **/etc/sysconfigtab**. This isn't always needed. I believe it's a difference between Tru64 and Digital Unix. There are some versions of startup scripts which will refer to the file again, for a swap device. It would be present in the section called **vm:**. If you see a swap device listed in that section, alter it to point to the new disk or remove it. 
 +
  
how_to_clone_tru64_and_digital_unix.txt · Last modified: 2023/09/08 23:04 by sgriggs

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki