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 revision Previous revision
how_to_clone_tru64_and_digital_unix [2019/06/25 06:35]
sgriggs [It Hangs During Boot]
how_to_clone_tru64_and_digital_unix [2019/06/25 06:40] (current)
sgriggs [It Boots but It's Horked Up]
Line 261: Line 261:
  
   - Double check your swap is pointing to the right place and working (swapon -s)   - Double check your swap is pointing to the right place and working (swapon -s)
-  - Make sure your filesystems are not showing up with weird or generic names. Double check your source and destination device and make sure that your old device name isn't still leftover in a config file somewhere. Most commonly it's the **/​etc/​fstab** or bad disk-symlinks in **/​etc/​fdmns**.+  - Make sure your filesystems are not showing up with weird or generic names. Double check your source and destination device and make sure that your old device name isn't still leftover in a config file somewhere. Most commonly it's the **/​etc/​fstab** or bad disk-symlinks in **/​etc/​fdmns**. Also it's also worth perusing **/​etc/​sysconfigtab** on 5.x for mistakes or old device names.
   - Make sure if you use a new system type that any kernel tuning you do makes sense. Ie.. if you take parameters from a system that has 4GB of RAM and try to use them on a big GS1280 with 64GB of RAM then you are almost certainly going to have some bad tuning in there. Double check your __sysctl__ settings with **sysctl -a**.    - Make sure if you use a new system type that any kernel tuning you do makes sense. Ie.. if you take parameters from a system that has 4GB of RAM and try to use them on a big GS1280 with 64GB of RAM then you are almost certainly going to have some bad tuning in there. Double check your __sysctl__ settings with **sysctl -a**. 
  
how_to_clone_tru64_and_digital_unix.txt ยท Last modified: 2019/06/25 06:40 by sgriggs