how_to_clone_tru64_and_digital_unix
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
how_to_clone_tru64_and_digital_unix [2019/06/25 05:09] – sgriggs | how_to_clone_tru64_and_digital_unix [2019/06/25 06:27] – [It Hangs During Boot] sgriggs | ||
---|---|---|---|
Line 252: | Line 252: | ||
Depends on why and where it hangs. The most common issues are these. | Depends on why and where it hangs. The most common issues are these. | ||
- | - 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' | + | - 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 __/ |
- You are using UFS and you forgot to fix the reference to the **/ | - You are using UFS and you forgot to fix the reference to the **/ | ||
- | - Make sure your copy method preserved all the permissions, | + | - Make sure your copy method preserved all the permissions, |
- | - 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 |
If you have problems beyond the ones documented, then consider contacting PARSEC for some consulting work to help you! | If you have problems beyond the ones documented, then consider contacting PARSEC for some consulting work to help you! |
how_to_clone_tru64_and_digital_unix.txt · Last modified: 2023/09/08 23:04 by sgriggs