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 06:35] – [It Hangs During Boot] sgriggs | how_to_clone_tru64_and_digital_unix [2021/06/01 19:34] – [Creating File Systems] sgriggs | ||
---|---|---|---|
Line 148: | Line 148: | ||
In general, if you are cloning a UFS based system, then be very careful that your disklabel is going to give you enough space for the **/** and **/usr** file systems. If you are using AdvFS make sure that the total slices you set aside can be used to add up to the sizes you need (ie.. remember that AdvFS can do concatination, | In general, if you are cloning a UFS based system, then be very careful that your disklabel is going to give you enough space for the **/** and **/usr** file systems. If you are using AdvFS make sure that the total slices you set aside can be used to add up to the sizes you need (ie.. remember that AdvFS can do concatination, | ||
+ | |||
+ | ==== Creating File Systems ==== | ||
+ | |||
+ | Once you have your disk label setup on the clone, what you have is a essentially a partition table with no file systems. It's now up to us to actually create file systems inside of those extents we just defined. Obviously, this is a different process depending on if you use UFS or AdvFS. For UFS users the process is much more simple. You simply need to run the **newfs** command on each UFS partition. It's no more complicated than that. Here is an example, in this case we have three filesystems, | ||
+ | |||
+ | < | ||
+ | # newfs / | ||
+ | # newfs / | ||
+ | # newfs / | ||
+ | </ | ||
+ | |||
+ | That puts down all the superblocks and metadata information the filesystem uses internally to operate. It doesn' | ||
==== File Copy Steps ==== | ==== File Copy Steps ==== | ||
Line 261: | Line 273: | ||
- 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 **/ | + | - 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 **/ |
- 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: 2023/09/08 23:04 by sgriggs