Differences

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

--- how_to_clone_tru64_and_digital_unix [2019/06/25 06:27] – [It Hangs During Boot] sgriggs
+++ how_to_clone_tru64_and_digital_unix [2019/06/25 06:30] – [It Hangs During Boot] sgriggs
@@ Line 256: / Line 256: @@
   - 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 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.
+  - Make sure your SRM variables for __boot_file__ and or __boot_flags__ may be incorrect and have old VMS data in there or some other garbage. Your boot file should be your kernel, which is usually __/vmunix__ or __/genvmunix__. Your boot flags should be **A** or **S** but not a number, if it's a number it came from VMS and it's wrong. People who re-use VMS systems for Tru64 will run into these problems often.
 If you have problems beyond the ones documented, then consider contacting PARSEC for some consulting work to help you!