This section describes issues related to restoring SunOS release 4 files and file systems you backed up before installing the Solaris 7 software.
You can restore the SunOS release 4 file systems that you could not, or chose not to, preserve into the new file systems you created during the Solaris 7 installation. For information about backup and restore procedures, see System Administration Guide, Volume I.
Before proceeding make sure that the target slice is large enough to accommodate the file system being restored.
Restore any SunOS release 4 user files that you backed up and copy them to the new system.
First, you must restore the SunOS release 4 system configuration files to a temporary directory on the Solaris 7 system. After the information is back on the system in the temporary directory, you need to make it available in the Solaris 7 operating environment. Some of the data can be merged into the files, while some types of data must be converted to new formats.
The system's configuration defines which files you need to work with. Complete the restore by merging or converting files as follows:
Systems with no name service: If the system has no name service, merge or convert all the relevant system files located in /etc and /var.
Systems that are NIS clients: If the system is a NIS client, merge or convert only the local system configuration files located in /etc and /var that are not provided via the NIS name service.
Systems that are NIS master servers: If the system is a NIS master server, merge or convert all the files that reside in the NIS master directory (for example, /etc). Additionally, update other local configuration files in /etc and /var.
To make data from any of the following files available, merge the changes into the Solaris 7 version of the same file. Note, however, that not all of these files were modified on the SunOS release 4 system. Identify files that were changed on the SunOS release 4 system and merge these only. As you read the list, note that some of the file names are slightly different. For example, /etc/auto.* files are now /etc/auto_*.
The following is an example list of the SunOS release 4 files backed up using the instructions in the first part of this chapter. These files are candidates for merging into the Solaris 7 operating environment. See Appendix D, System Files Reference Table, to examine SunOS release 4 files for changes.
All automounter maps, including /etc/auto.master
/etc/aliases
/etc/bootparams
/etc/ethers
/etc/hosts
/etc/format.dat
/etc/inetd.conf
/etc/netmasks
/etc/networks
/etc/protocols
/etc/publickey
/etc/rpc
/etc/services
/etc/hosts.equiv
/etc/remote
/.cshrc
/.profile
/.login
/.logout
/.rhosts
/var/spool/cron
/var/spool/mail
/var/spool/calendar
Many system files, such as the /etc/fstab file, have been replaced and do not exist under the Solaris 7 operating environment. Information from these files must be extracted and manually converted in the Solaris 7 environment. See Appendix D, System Files Reference Table, to examine SunOS release 4 files for changes.
Do not restore operating system executable files (such as system commands in /usr/bin) from the SunOS release 4 system to your system after installing the Solaris 7 software.
You must change the following files before merging the data onto the Solaris 7 system:
/etc/uucp - There have been some changes to the UUCP system. The Config, Grades, and Limits files are new in the Solaris 7 operating environment. The files Devconfig, Devices, Dialcodes, Dialers, Permissions, Poll, Sysfiles, and systems are the same in the Solaris 7 operating environment as they were in the SunOS release 4 software. These files can be merged together. There are also several SunOS release 4 files that are not used in the Solaris 7 operating environment.
/etc/group - The basic format of this file is the same as it was in the SunOS 4.1 and SunOS 4.1.x releases. However, previous releases used a group entry beginning with a plus sign (+) or minus sign (-) to selectively incorporate entries from NIS maps for group. See the group(4) man page if that compatibility is needed under the Solaris 7 operating environment.
/etc/exports - File systems to be shared on the network under the Solaris 7 operating environment use the /etc/dfs/dfstab file instead of /etc/exports. The format of entries in this file is like the following.
share -F fstype -o options -d "text" pathname resource |
See the dfstab(4) man page for additional information.
/etc/fstab - File systems to be mounted under the Solaris 7 operating environment use the /etc/vfstab file instead of /etc/fstab. The format of entries in the /etc/vfstab file is as follows.
dev raw_dev mnt_pt fs_type fsck_pass auto_mnt mnt_option |
Refer to the vfstab(4) man page for additional information.
/etc/passwd - The format of the passwd file is the same as that under the SunOS release 4 software. However, user passwords are now stored in the /etc/shadow file. Refer to the passwd(4) and shadow(4) man pages for additional information.
/etc/sendmail.cf - The format of sendmail.cf is the same as that under the SunOS release 4 structure. The location of the file is now /etc/mail/sendmail.cf.
/etc/ttytab - Under the SunOS release 4 system, ttytab was used to control serial ports and the characteristics of the terminals on those serial lines. Under the Solaris 7 operating environment, the Service Access Facility is used to configure this capability.
/etc/printcap - Under the Solaris 7 operating environment, printers are configured using the SunOS release 5.7 LP print service. See System Administration Guide, Volume I for additional information.