Differences

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

--- how_to_clone_tru64_and_digital_unix [2019/06/25 06:26] – [It Hangs During Boot] sgriggs
+++ how_to_clone_tru64_and_digital_unix [2019/06/25 06:27] – [It Hangs During Boot] sgriggs
@@ Line 254: / Line 254: @@
   - You forgot to edit out some kind of reference to the swap device. Check the post-copy steps again. One of the startup scripts probably tried to activate swap on a device that won't. Remember that you can use single user mode to fix these issues without doing a full re-install. References to swap could be in in the __/etc/fstab__ (usually on 4.x or older systems) and could also be inside of your __/etc/sysconfigtab__ which is usually the case on 5.x systems.
   - You are using UFS and you forgot to fix the reference to the **/etc/fstab** for one of the file systems. You might also have to edit any reference for swap, especially on Digital Unix 4.x. Also pay attention for any other filesystems that might have changed or gone away.
-  - Make sure your copy method preserved all the permissions, especially on **/sbin** and the scripts in **/sbin/init.d** which are critical.
+  - Make sure your copy method preserved all the permissions, especially on **/sbin** and the scripts in **/sbin/init.d** which are critical. Those scripts should be executable and owned by the __root__ or __bin__ users.
-  - Do NOT try to eliminate one of the AdvFS file domains. As mentioned earlier, the startup scripts reference both **root_domain** and **usr_domain** and if you change their names or eliminate one of them the startup scripts will fail.
+  - Do NOT try to eliminate one of the default AdvFS file domains (one for root and another for /usr). As mentioned earlier, the startup scripts reference both **root_domain** and **usr_domain** and if you change their names or eliminate one of them the startup scripts will fail.
 If you have problems beyond the ones documented, then consider contacting PARSEC for some consulting work to help you!