Differences

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

--- how_to_clone_tru64_and_digital_unix [2025/05/29 22:58] – sgriggs
+++ how_to_clone_tru64_and_digital_unix [2025/05/30 03:42] (current) – sgriggs
@@ Line 303: / Line 303: @@
 If you are building a cloned disk for the same system you are doing the cloning on, you can be pretty sure the disk name will remain constant with whatever you booted with, now.
-I do not know how Tru64 tracks disk devices. It might be by WWN or some other identifier. However, it takes very little to "invalidate" the hardware database entry for a disk and thus make it appear "new". In this instance Tru64 gives the disk a different name. What might have originally been dsk0 may now become dsk3, for example. This is a downside of the way Tru64 5.x was designed and frankly, I'd rather work with disks in Digital Unix anyday just for it's simple determinism.
+I do not know how Tru64 tracks disk devices. It might be by WWN or some other identifier. However, it takes very little to "invalidate" the hardware database entry for a disk and thus make it appear "new". In this instance Tru64 gives the disk a different name. What might have originally been dsk0 may now become dsk3, for example. This is a downside of the way Tru64 5.x was designed and frankly, I'd rather work with disks in Digital Unix any day just for it's simple determinism.
 I can give you detail on the process, of fixing this, at least. Start with a session like this one in my example.
@@ Line 396: / Line 396: @@
 /dev/disk/dsk3c       /usr/users ufs rw 1 2
 </code>
-==== Fix the rc.config ====
+==== Fix the /etc/sysconfigtab (now, while you have the chance) ====
-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 **/etc/sysconfigtab** file one of three the main configuration files 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 sysconfigtab 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/disk/dsk2b" (or whatever your actual swap slice is).
+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/disk/dsk2b" (or whatever your actual swap slice is). It would be present in the section called **vm:** usually near the bottom of the file.
 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). However, in the event your disk name changes, don't forget to change the swap device, too. The system can hang if you specify a bogus device.
-==== 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.