Appendix B Making the Transition to Solaris 2.5

This appendix briefly introduces the changes that users and system administrators can expect when making the transition from SunOS 4.x for SPARC systems and Solaris 2.1 for IA-based systems.

The Solaris 2.5 upgrade option is available if at least one disk attached to the system has a Solaris 2.1 or later root file system. The upgrade option is not available for systems with SunOS 4.1.

The Solaris upgrade option is not available from Solaris 2.1 to 2.5.

For more detailed information about the transition from SunOS 4.x to Solaris 2.5, and for information about the differences between these two software environments, see Solaris 1.x to 2.x Transition Guide and Source Compatibility Guide.

For a look at some of the changes between Solaris 2.5 and your previous version, see Solaris 1.x to 2.x Transition Guide.

B.1 Making the Transition from SunOS 4.x

The Solaris 2.5 environment includes SunOS 5.x system software. The following sections present a brief description of the differences between SunOS 4.x and SunOS 5.x for both users and system administrators.

B.1.1 SPARC: Changes Affecting SunOS 4.x Users

Some of the more obvious differences between SunOS 4.x releases and the SunOS 5.x releases are:

• Many UNIX commands have changed. For a detailed list, see Solaris 1.x to 2.x Transition Guide.

• The printing subsystem has changed. For example:

  • lp(1) replaces lpr.

  • lpstat(1) replaces lpq.

  • cancel(1) replaces lprm.

  • troff(1) requires a printer name.

• The mail programs have changed. The SunOS 4.x mailboxes and folders are completely compatible with any of the three Solaris 2.3 mail programs:

  • mailtool, the DeskSet environment Multimedia Mail Tool

  • mail(1), a command-line utility

  • mailx(1), a command-line utility

• The location or name of some system files has changed. For example:

  • /etc/vfstab replaces /etc/fstab.

  • /var/mail replaces /var/spool/mail.

  • /platform/*/kernel/unix replaces /vmunix.

For more information on the preceding topics, see Solaris 1.x to 2.x Transition Guide.

B.1.2 SPARC: Changes Affecting SunOS 4.x System Administrators

Some of the differences you will find in migrating to the SunOS 5.x environment from a SunOS 4.x environment are:

• Solaris 2.5 software can be installed on SPARC systems only from a local or remote CD-ROM drive or from a network.

• Solaris 2.5 software media is distributed in software groups, made up of packages and clusters, which facilitates installation. For the most up-to-date information on Solaris 2.5 packages use pkginfo(1) or swmtool.

• Device-naming conventions have changed; disks, for example, are now named as follows:

Figure B-1 Device-naming Convention

Note that on some disks (xy, xd) there is no target component; such disks have names like c0d0s0.

• The file system directory structure has changed. For example:

  • The kernel, called unix, and its related modules are stored in the /kernel directory.

  • The /opt directory is a new directory. It is created during installation for storing or mounting optional software applications.

  • The /devices directory is a hierarchy of device files, with symbolic links into the /dev directory for compatibility with the SunOS 4.x device naming conventions.

  • The /usr directory has been restructured.

  • The terminfo database replaces /etc/termcap.

  • The /etc/vfstab file replaces /etc/fstab.

  • The /var/mail directory replaces /var/spool/mail.

  • The /etc/lp directory replaces /etc/printcap.

  • The Remote File Sharing service (RFS) optional software package has been discontinued since Solaris 2.2.

• The SunOS 5.x kernel is dynamic; the user no longer rebuilds or edits the kernel configuration file.

• The kernel can automatically load necessary drivers for new devices added to the system.

• The Solaris 2.5 startup and shutdown procedures have changed:

  • The init(1M)command uses different scripts for each run level.

  • The shutdown command does not support any of the options available in SunOS 4.1 systems.

  • The fastboot(1B) and fasthalt(1b) commands are only available using the SunOS/BSD Source Compatibility Package.

• Many commands have changed, as well as the output from commands. Scripts may need to be rewritten. For more information, see Solaris 1.x to 2.x Transition Guide.

• NIS+ replaces the NIS, the Network Information Service name service; however, NIS+ uses NIS data, which makes it easier to transition to NIS+.

• Administration Tool (admintool), Motif application that allows you to administer your local system, provides management of system database and host information, printers, serial ports, user accounts, and software.

• The print management commands have changed. For a detailed list, see Solaris 1.x to 2.x Transition Guide.

• Terminals and modems are controlled through the Service Access Facility (SAF) and System Access Controller (SAC); the /etc/ttytab file is gone.

B.1.3 SPARC: Compatibility with SunOS 4.x Releases for SPARC Systems

The Solaris 2.5 environment provides two packages to ease the transition and migration to the SunOS 5.x system software for SPARC systems:

• The SunOS/BSD Source Compatibility Package

• The SunOS Binary Compatibility Package

If you use these packages, remember that they are a temporary transition aid only for

• Developers who want to compile SunOS 4.x application source code to run in the Solaris 2.5 environment.

• Users who want to run SunOS 4.x-based application binaries that have not yet been ported to run in a SVID-compliant environment such as the Solaris 2.5 environment.

B.1.3.1 SPARC: The SunOS/BSD Source Compatibility Package

If this software package is installed, it supports some of the SunOS/BSD commands that are not included in, or have changed in, the SunOS 5.x system software. Application source code that is compliant with the SunOS 4.x environment will compile and run under the Solaris 2.5 environment by using the SunOS/BSD Source Compatibility package.

For specific details, see Binary Compatibility Guide and Source Installation and Media Preparation Guide.

B.1.3.2 SPARC: The SunOS Binary Compatibility Package

OpenWindows and other executable applications that are either dynamically linked or statically linked and written under SunOS 4.1.x [References to the "SunOS 4.1.x" release/environment include the SunOS 4.1 release and all subsequent 4.1 releases: 4.1.1, 4.1.1 RevB, 4.1.2, 4.1.3, and 4.1.3c.] are supported in the Solaris 2.5 environment through the SunOS Binary Compatibility Package and the OpenWindows Binary Compatibility Package.

To use these packages, applications written under SunOS 4.x must not:

• Trap directly to the kernel

• Write directly to system files

• Use /dev/kmem or libkvm routines

• Use unpublished SunOS interfaces

• Rely on non-SunOS drivers

  The SunOS/BSD Source Compatibility package must be installed to use the SunOS Binary Compatibility Package.

B.2 IA: Making the Transition from Solaris 2.1 for IA

Some differences exist for users and administrators moving to a Solaris 2.5 system environment from the Solaris 2.1 release. For example, installation procedures follow a different order, there are changes in the way disks are formatted, and printing commands are different.

B.2.1 IA: Changes affecting Users

Keyboard mapping for IA-based keyboards has changed. For complete key-map table, see Appendix C, Modifying the Keyboard.

B.2.2 IA: Changes affecting System Administrators

There are differences in installation of Solaris 2.5 software on a networked IA-based system:

• kdmconfig is called by sysidconfig and replaces devconfig during installation.

• When bootparams database server is queried, if the ethernet and hosts maps are set correctly, installation proceeds without questions. If there are discrepancies, or the system is stand-alone, a series of screens appear asking you to define the keyboard, mouse, and display attached to the system. See kdmconfig(1M).

  There are differences in formatting SCSI and IDE disks for IA-based systems.

• The format(1M) utility is now available to format, label, analyze, and repair SCSI disks. This utility is included with the addbadsec(1M), diskscan(1M), fdisk(1M), and fmthard(1M) commands available in the Solaris 2.1 for IA-based release. To format IDE disks use the DOS format utility; however to label, analyze and repair IDE disks on IA-based systems use the Solaris format(1M) utility.

  There is a change in the support for parallel PostScript^TM printers on IA-based systems:

• The lp driver has been modified, so that setup for a parallel PostScript printer in IA-based systems is now identical to the setup of a serial printer. The only difference is when you need to specify the device name of the port.

• The following files are no longer part of Solaris 2.5:

  • /etc/lp/fd/ppostio.fd

  • /etc/lp/fd/ppostior.fd

  • /usr/share/lib/terminfo/P/PPS

  • /usr/share/lib/terminfo/P/PPSR

• The IA-based lp driver now takes advantage of added ioctls in postio.

B.2.3 IA: Solaris 2.5 System Administration Tools

System administration benefits of the Solaris 2.5 release are the result of enhancements to the Solaris system software and the ONC networking protocols and administration applications. For the benefit of IA users who may not have seen intervening releases, these enhancements are described in the following sections.

B.2.3.1 IA: Since the Solaris 2.3 Release

The following administration features have been enhanced since the release of Solaris 2.3:

• Keyboard, mouse, and display configurations are updated with kdmconfig

• Bootparams names the keyboard, display, and mouse

• Booting sequence is different on IA-based machines

B.2.3.2 IA: Since the Solaris 2.1 Release

The following administration features have been enhanced since the release of Solaris 2.1:

• Administration Tool is enhanced to simplify terminal and modem setup.

• Automated Security Enhancement Tool (ASET) enables administrators to easily increase a system`s security.

• Dynamic kernel and loadable modules simplify:

  • Kernel management for heterogeneous systems

  • Adding new devices to running systems

  • Adding device drivers without rebuilding the kernel

• NIS+ name service creates subdomains and assigns security to network resources.