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.
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.
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.
For more information on the preceding topics, see Solaris 1.x to 2.x Transition Guide.
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 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.
Note that on some disks (xy, xd) there is no target component; such disks have names like c0d0s0.
The SunOS 5.x kernel is dynamic; the user no longer rebuilds or edits the kernel configuration file.
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.
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.
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.
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.
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
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.
Keyboard mapping for IA-based keyboards has changed. For complete key-map table, see Appendix C, Modifying the Keyboard.
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 PostScriptTM 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:
The IA-based lp driver now takes advantage of added ioctls in postio.
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.
The following administration features have been enhanced since the release of Solaris 2.3:
Booting sequence is different on IA-based machines
The following administration features have been enhanced since the release of Solaris 2.1:
Administration Tool is enhanced to simplify terminal and modem setup.
Dynamic kernel and loadable modules simplify:
Kernel management for heterogeneous systems
Adding new devices to running systems
Adding device drivers without rebuilding the kernel