Preparing for File System Layout Changes

If you intend to rely on transition links, as described under “Upgrade Options ”, you don't need to make any modifications to code and scripts to prepare for the transition to the 10.0 filesystem. (Remember that transition links will be supported only for the lifetime of 10.x.)
But you should read the HP-UX 10.0 File System Layout White Paper so as to understand how the filesystem layout will change.
In addition, even though you may have decided not to change pathnames in code and scripts, you may need to make some changes to accommodate changes to commands and system calls; see “Preparing for Changes to Commands and Libraries ” later in this chapter.
If you intend to convert pathnames in code and scripts before you upgrade (the "Full Preparation" approach), follow directions in Chapter 5 “Converting Code and Scripts ”.
After the upgrade, you will need to modify system startup and shutdown scripts, and /etc/inittab, to merge custom code from the 9.x versions back into the 10.x files.
See Chapter 7 “After the Upgrade ”.

What Will Happen to Non-System Files?

File systems, directories and files you have created directly under the root (/) directory will not be moved.
For example, a directory/myapps will not be moved or touched during the upgrade.
/users is left intact.
The upgrade software creates an empty directory /home.
After the upgrade, you may want to move and reorganize some directories, including /users, to comply with the 10.0 paradigm (as described in the HP-UX 10.0 File System Layout White Paper), but you do not have to do this.

Directories and files you may have created under HP-UX "system" directories such as /bin will be moved to reside under the new parent directory.

For example, if you have created a directory under /bin (we'll call it /bin/myBinDir), the upgrade software will move this directory, along with the rest of the /bin directory to /usr/bin.

But scripts that look for /bin/myBinDir will continue to find it, because /bin is linked by default to /usr/bin on 10.01.




	NOTE: `snoop` will warn you if there's already a `myBinDir` in `/usr/bin`, If you have not resolved this potential conflict by the time you upgrade, `upgrade` will combine the former `/bin/myBinDir` with the existing `/usr/bin/myBinDir`, resolving name collisions at the file level by appending a suffix to one of the files. (For example, if there is a file `/bin/MyBindir/tcbin` that would overwrite an existing file `/usr/bin/MyBindir/tcbin`, the existing file might be renamed to `/usr/bin/MyBindir/tcbin.save`.)

HP products bundled with the 10.01 release, such as C, will normally be moved in compliance with the 10.0 filesystem layout.
See the product-specific release notes for more information.

Preparing for File System Layout Changes

Technical documentation

» Table of Contents

What Will Happen to Non-System Files?