HP ProLiant 1600 Migrating from SCO OpenServer 5.0.5 to UnixWare 7.1 Using Com - Page 26
??Restore your NFS filesystem., Migration Tip
View all HP ProLiant 1600 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 26 highlights
Migrating from SCO OpenServer™ 5.0.5 to UnixWare® 7.1 Using Compaq SmartStart v4.23 26 4. Rename your backed up /etc/ftpconv file as /etc/ftpconversions. Change the partname of the conversion utility where appropriate, for example /etc/ftpconv to /ftp/conversions. = Restore your NFS filesystem. Use the information from your backed up files to configure your UnixWare 7.1 system. Do not, however, copy the /etc/default/filesys and /etc/exports files from your OpenServer system to their equivalents in your UnixWare system as the format of these files is not the same. See Table 8 for new filenames. Table 8. UnixWare 7.1 filenames for your NFS filesystem OpenServer 5.0.5 /etc/default/filesys /etc/exports /etc/auto.master /etc/auto.direct; /etc/auto/indirect UnixWare 7.1 /etc/vfstab /etc/dfs/dfstab /etc/auto.master /etc/auto.home Definition Used by clients to define filesystems to be mounted Used by server to define filesystems that client can mount Lists initial automount configurations Lists direct and indirect automount configuration Migration Tip It is recommended that you set up automatic sharing when you first set up your Network File System (NFS) if you need to share the same set of resources on a regular basis. For example, if your server is a server that supports diskless clients, you need to make your client root directories available at all times. If you want to set up your system so that certain files and directories are shared automatically whenever you start NFS operations, you need to edit the file /etc/dfs/dfstab. Note: The following options, which are supported by mount in SCO OpenServer Release 5, are not supported in UnixWare 7.1: exec, noexec, trunc, notrunc, tcp, and spongy. Use the dfstab file to list all the resources that your server shares with its clients and to control which clients may mount a resource. Once a resource has been shared on a server through the NFS, it can be accessed from a client. Mounting can be done automatically when NFS operation begins on the client or when NFS is started using the script /etc/init.d/nfs. Note: A server can be a client of another server on a local network, in which case, your server vfstab file may need to include both local and remote mounts. Table 9 lists the entries (variables) in the /etc/vfstab file. 0413-0799-A