Sun and OracleChannel SunHow to BuyLog In日本語

Solaris Transition Guide Update
この本のみを検索
検索のヘルプ
この本を見る:
内に含ま
その他のドキュメント
サポート リソース
 PDF 文書ファイルをダウンロードする (151 KB)

Part I Transition Information for Users and System Administrators

Use this part of the update to find current information for users and system administrators on the transition from SunOS release 4 to a SunOS release 5.8 computing environment.

Chapter 1 Introduction

The Solaris operating environment enhances your system's capabilities with powerful tools and features. The chapter in the Solaris Transition Guide discusses the benefits of migrating to the Solaris operating environment. It also summarizes the principal differences between SVR4 and the Solaris operating environment.

Advantages of Migrating to the Solaris Operating Environment

See the Solaris Transition Guide.

Comparison of SVR4 and the Solaris Operating Environment

See the Solaris Transition Guide.

Chapter 2 Overview of Major Changes

This following sections of this update describe changes and enhancements made to SunOS release 5.8 following the publication of the Solaris Transition Guide.

For information on earlier changes from SunOS release 4 to SunOS release 5, see the Solaris Transition Guide.

Chapter 3 Converting a SunOS 4.x System to the Solaris 8 Environment

This chapter updates information in the Solaris Transition Guide on the three-phase process involved in converting a SunOS release 4 system.

The chapter contains:

What's New About Installing

See What's New in the Solaris 8 Operating Environment.

What to Do Before You Install Solaris Software

Read "What to Do Before You Install Solaris Software" in Solaris Transition Guide. Then carefully review "Getting Started" in Solaris 8 (SPARC Platform Edition) Installation Guide.

Backing Up Files and File Systems Before You Install

Read this section in the Solaris Transition Guide and carefully review "Backing Up and Restoring File Systems (Overview)" in System Administration Guide, Volume 1.

Installing Solaris Software

Install the Solaris 8 software using the software installation procedures given in "Getting Started" in Solaris 8 (SPARC Platform Edition) Installation Guide.

Preserve Option

The Solaris Transition Guide mentions a preserve option in the interactive installation program that allows you to save existing SunOS release 4 file systems during installation. For procedures on using the interactive installation program to preserve data on the disk, see "Using the Solaris 8 Interactive Installation Program" in Solaris 8 Advanced Installation Guide.

Restoring Files and File Systems After You Install

Read this section in the Solaris Transition Guide and carefully review "Backing Up and Restoring File Systems (Overview)" in System Administration Guide, Volume 1.

Chapter 4 Using the Compatibility Packages

The Solaris 8 software is neither source nor binary compatible with the SunOS release 4 software. This means that SunOS release 4 programs and user applications based on those releases may not run correctly under the Solaris 8 operating environment. Compatibility packages make it possible for these programs to run on a Solaris 8 system.

This chapter replaces the corresponding chapter in the Solaris Transition Guide. It briefly discusses two compatibility packages: the Source Compatibility Package and the Binary Compatibility Package. These packages make the transition easier by enabling you to use SunOS release 4 commands and applications as you migrate to the SunOS release 5 computing environment.

Source Compatibility Package

For detailed information about the Source Compatibility Package, see the Source Compatibility Guide

Binary Compatibility Package

See the Binary Compatibility Guide for procedures about setting up your environment to access this package. This guide also details the limitations of the Binary Compatibility Package.

Chapter 5 Security

This chapter updates information in the Solaris Transition Guide on changes to security features made after SunOS release 4.

The chapter contains:

What's New in the Solaris 8 Operating Environment

See these sections for information on security features and options implemented for the Solaris 8 release:

Solaris 8 Security Features

Most of the SunOS release 4 security features are available in the current release. The following sections describe changes and enhancements implemented for Solaris 8 release.

Default File System and Directory Permissions

Many system files and directories in the Solaris 8 release have different default ownership and stricter permissions than in previous releases. For complete information, see "Managing System Security (Overview)" in System Administration Guide, Volume 2

Note -

Before you create packages for the Solaris 8 operating environment, refer to "Managing System Security (Overview)" in System Administration Guide, Volume 2.

Solaris 8 Role-Based Access Control

In previous releases, full superuser powers were granted to anyone with the superuser password. In the Solaris 8 operating environment, role-based access control (RBAC) enables administrators to assign limited superuser capabilities to normal users. This is achieved through three new features:

  • Authorization--access granted to a restricted function.

  • Execution profile--a grouping of authorizations and commands with special attributes. For example, uid, gid, and egid.

  • Role--special types of user accounts assigned for the purpose of performing a particular set of administrative tasks.

The next sections describe databases that support the use of roles, authorizations, and profiles. For further information, see "Managing User Accounts and Groups (Overview)" in System Administration Guide, Volume 1.

/etc/user_attr

The user_attr database is used to store extended security attributes related to users and roles (a special type of user account). Specifically, the database associates users with authorizations, profiles, roles, and account type.

/etc/security/auth_attr

The auth_attr database lists and describes authorizations. It identifies associated help files and includes any additional authorization attributes.

/etc/security/prof_attr

The prof_attr database lists the available execution profiles and identifies the authorizations and help file associated with each profile.

/etc/security/exec_attr

The exec_attr database associates execution attributes with execution profiles. Each entry consists of the security policy in force, a command, and the values for any special attributes, such as real or effective UIDs or GIDs. Note that currently the only valid security policy is suser (superuser).

/etc/security/audit_user

The audit_user database stores preselection data for auditing.

Solaris 8 Security Related Documentation

This documentation provides up-to-date information on managing security at the file, system, and network level.

Table 5-1 Security Related Documentation

Subject

Book Title

Where to Find it

Managing System Security

System Administration Guide, Volume 2

Solaris 8 System Administrator Collection

NIS+ Name Service Authorization, Authentication

Solaris Naming Administration Guide

Solaris 8 System Administrator Collection

NIS+ Security

NIS+ Transition Guide

Solaris 8 System Administrator Collection

Secure NFS

System Administration Guide, Volume 3

Solaris 8 System Administrator Collection

Secure RPC

System Administration Guide, Volume 3

Solaris 8 System Administrator Collection

TCP/IP

System Administration Guide, Volume 3

Solaris 8 System Administrator Collection

Other Security Features

The following sections reference documentation that supersedes information in the Solaris Transition Guide.

Password Aging Changes

See "Managing User Accounts and Groups (Overview)" in System Administration Guide, Volume 1 for current information about setting up and maintaining passwords.

Access Control Lists (ACLs)

See "Managing System Security (Overview)" in System Administration Guide, Volume 2 for current information on ACLs.

Automated Security Enhancement Tool (ASET)

See "Managing System Security (Overview)" in System Administration Guide, Volume 2 for current information on ASET.

Security Options

The following sections reference documentation that supersedes information in the Solaris Transition Guide.

Kerberos 4.0 Security

"Using Authentication Services (Tasks)" in System Administration Guide, Volume 2 provides step-by-step instructions for setting up Kerberos login authentication.

Sun EnterpriseTM Authentication Mechanism (Kerberos V5) Client Support

This feature provides the Kerberos V5 client-side infrastructure, an addition to the Pluggable Authentication Module (PAM), and utility programs that can be used to secure RPC based applications, such as the NFS service. Kerberos provides selectable strong user or server level authentication, integrity, or privacy support. The Kerberos clients can be used in conjunction with Sun Enterprise Authentication Mechanism (SEAM) (a part of SEAS 3.0) or other Kerberos V5 software (for instance, the MIT distribution) to create a complete single network sign-on solution. The section on the "Solaris NFS Environment" in System Administration Guide, Volume 3 describes Kerberos support for the NFS environment.

Other Security Options

The following sections reference documentation that supersedes information in the Solaris Transition Guide.

SunSHIELD Package

For information on the SunSHIELDTM Basic Security Module (BSM) package, see Trusted Solaris Administration Overview in the Trusted Solaris 7 AnswerBook.

PAM

See "Using Authentication Services (Tasks)" in System Administration Guide, Volume 2 for step-by-step instructions on administering the Pluggable Authentication Module (PAM).

Chapter 6 User Environment Administration

This chapter updates information in the Solaris Transition Guide on setting up the local user environment after installing the Solaris 8 operating environment.

The chapter contains:

What's New in the Solaris 8 Operating Environment

New options and utilities have been added to sendmail and the Solaris 8 Reference Manual Collection has been reorganized.

See these sections for more information:

Selecting a Default Shell

For information on the login shell that runs when you are logged in, see the Solaris Transition Guide.

Customizing User Environments

For current information on customizing the user environment, see "Customizing a User's Work Environment" in System Administration Guide, Volume 1

For information recreating the look and feel of your SunOS release 4 work environment, see the Solaris Transition Guide.

Window Systems

For information on changes previously made in the SunOS release 5 environment, see the Solaris Transition Guide.

For current information on using CDE as your Solaris 8 desktop, see:

User and Group Administration

For information on adding, modifying or removing users and groups, see:

Using Mail

See the Solaris Transition Guide for information on changes previously made in the SunOS release 5 environment.

In the Solaris 8 operating environment, sendmail 8.10 includes new a option, MaxHeadersLength, that limits the length of the sum of all header lines in any given message, which can prevent a denial-of-service attack. Also included is a new version of mail.local that implements the Local Mail Transfer Protocol, RFC 2033. This change allows for re-queuing of mail to the recipients that did not receive a message, rather than re-sending the message to all of the recipients if an error occurs. A new file called /etc/default/sendmail can be used to store options to start sendmail with, so that the options are not touched during a upgrade. In addition, a new utility called smrsh increases security by reducing the number of commands that can be run using the |program syntax of sendmail.

For detailed and current information, see "Mail Services Reference" in System Administration Guide, Volume 3.

Using Document Tools

See the Solaris Transition Guide for information on differences in:

  • Solaris PostScriptTM filters and SunOS release 4TransScript filters (TEX filter pscat raster image).

  • Solaris and SunOS release 4 troff output.

Man Page Organization Differences

Man pages have been changed to be compatible with SVR4 organization. As a result, some sections of the SunOS release 4 man pages have been renamed. For example, man(8) is now man(1).

The Solaris 8 Reference Manual Collection has been reorganized. The following table describes the current sections of the Solaris 8 Reference Manual Collection.

Table 6-1 Man Page Documentation

Solaris 8 Reference Manual Section

Content

man pages section 1

User commands

man pages section 1M

System administration commands

man pages section 2

System calls

man pages section 3

Basic library functions

Curses library functions

Extended library functions

Library interfaces and headers

Networking library functions

Threads and realtime library functions

man pages section 4

File formats

man pages section 5

Standards, environments, and macros

man pages section 6

Demos

man pages section 7

Device network interfaces

man pages section 9

DDI and DKI overview

man pages section 9E

DDI and DKI entry points

man pages section 9F

DDI and DKI kernel functions

man pages section 9S

DDI and DKI data structures

Chapter 7 Device Administration

This chapter updates information in the Solaris Transition Guide on device administration.

The chapter contains:

What's New in the Solaris 8 Operating Environment

The devfsadm command provides an improved mechanism for managing special device files in the /dev and /devices directories, including support for dynamic reconfiguration events. For more information, see "Device Naming From a Developer's Perspective".

The cfgadm command is updated in this release to provide SCSI and PCI hot-plugging for supported SCSI and PCI controllers. For more information, see "Dynamic Reconfiguration".

Device Naming Conventions

For information on changes made prior to SunOS release 5.8, see the Solaris Transition Guide.

For current information, see "What's New in Disk Management?" in System Administration Guide, Volume 1.

Obtaining Disk Information

The commands that report disk information changed in the SunOS release 5.7. df(1M) and du(1M) are still available, but have changed. dkinfo(8), and devinfo(1M) are replaced by prtvtoc and sysdef-d.

See the Solaris Transition Guide for detailed information on these changes.

See the following documentation for current information on these commands:

Adding Devices to the System

For current information on adding devices to a system, see "Device Management (Overview)" in System Administration Guide, Volume 1.

Note -

The reconfiguration boot -r command, described in the Solaris Transition Guide, does not currently remove file system entries for devices that are physically removed from the system. For more information, see boot(1M).

Dynamic Reconfiguration

The cfgadm command is updated in this release to provide SCSI and PCI hot-plugging for supported SCSI and PCI controllers.

Hot-plugging is the ability to physically add, remove, or replace system components while the system is running. Dynamic reconfiguration, available on certain SPARC servers, allows a service provider to remove and replace hot-pluggable system I/O boards in a running system, eliminating the time lost in rebooting. Also, if a replacement board is not immediately available, the system administrator can use dynamic reconfiguration to shut down a failing board while allowing the system to continue operation.

For more information, see "What's New in Device Management?" in System Administration Guide, Volume 1.

Using Volume Management

Volume Management, released with the Solaris 2.2 operating environment, mounts all removable media to provide access to CD-ROM and diskette drives under /vol/dev.

For more information, see "How Volume Management Works (Reference)" in System Administration Guide, Volume 1.

Chapter 8 Startup and Shutdown

This chapter updates information in the Solaris Transition Guide on changes to booting and shutting down a system.

It contains:

What's New in the Solaris 8 Operating Environment

In this release, dynamic host configuration protocol (DHCP) functionality has been added to boot a system over the network. See "Dynamic Host Configuration Protocol (DHCP)" for more information.

Booting

See the Solaris Transition Guide for information on changes to SunOS release 4 boot commands and processes.

Note -

The reconfiguration boot -r command, described in the Solaris Transition Guide, does not currently remove filesystem entries for devices that physically removed from the system. For more information, see boot(1M).

See the System Administration Guide, Volume 1 and Volume 3 for current information.

Dynamic Host Configuration Protocol (DHCP)

Dynamic Host Configuration Protocol enables you to boot a DHCP server over the network. Network boot technology based on RARP/bootparams is still available. For information on setting up a DHCP server, see "Configuring DHCP Service" in System Administration Guide, Volume 3.

init

See the Solaris Transition Guide.

Using the init Command

See "Shutting Down and Booting a System (Overview)" in System Administration Guide, Volume 1 for current information on the init command.

init Command Changes

See the Solaris Transition Guide for changes to SunOS release 4 run levels.

Changing System Run Levels

For previous information on different run levels, see the Solaris Transition Guide. For current information, see "Run Levels and Boot Files (Tasks)" in System Administration Guide, Volume 1.

Shutting Down

For previous information on fasthalt, halt, and shutdown, see the Solaris Transition Guide. For current information, see "Shutting Down a System" in System Administration Guide, Volume 1.

Chapter 9 File System Administration

This chapter updates information in the Solaris Transition Guide on changes to file system administration.

The chapter contains:

What's New in the Solaris 8 Operating Environment

New features added to the Solaris 8 Operating Environment include:

  • The Universal Disk Format (UDF) file system that enables users to exchange data stored on CD-ROMs, disks, diskettes, DVDs, and other optical media. See "Universal Disk Format (UDF) file system".

  • A new TMPFS-mounted file system, /var/run, which provides a repository for temporary system files not needed across system reboots. See "/var Directory".

  • The coreadm command that provides flexible core file naming conventions and better core file retention. See "Debuggers".

File System Changes

This section gives you information on the Universal Disk Format file system. It also provides an updated reference to current documentation on virtual file systems.

Universal Disk Format (UDF) file system

The Universal Disk Format (UDF) file system is supported in the Solaris 8 Operating Environment. UDF is the industry-standard format for storing information on optical media. It can be used to exchange data between UDF file systems on the following components: CD-ROMs, Disks and diskettes, Digital versatile disc or digital video disc (DVD) -- DVD-ROM on supported platforms. The UDF file system is provided as dynamically loadable 32-bit and 64-bit modules. It contains system administration utilities for creating, mounting, and checking the file system. When a UDF file system is mounted, users can read, write, or list files from the device and applications can access UDF file and directories with standard system calls. See the "Using the Universal Disk Format (UDF) File System" in System Administration Guide, Volume 1 for more information.

Pseudo File Systems

See the "Managing File Systems (Overview)" in System Administration Guide, Volume 1 for current information on virtual file systems.

Added File Systems

See the Solaris Transition Guide for SunOS release 5 changes to /kernel, /opt and /vol directories.

Default File Systems and Directories

See "UFS File System Reference" in System Administration Guide, Volume 1 which supersedes information in the Solaris Transition Guide.

Virtual File System Architecture

For current information on virtual file systems, see "Managing File Systems (Overview)" in System Administration Guide, Volume 1.

Supported File System Types

For SunOS release 5 information on file system types, see the Solaris Transition Guide.

For current information, see "Managing File Systems (Overview)" in System Administration Guide, Volume 1.

Cache File System (CACHEFS)

For current information on CacheFS "The Cache File System (Tasks)" in System Administration Guide, Volume 1.

Swap File Changes

For SunOS release 5 swap file information, see the Solaris Transition Guide.

For current information, see "Configuring Additional Swap Space (Tasks)" in System Administration Guide, Volume 1.

Unsupported SVR4 File System Types

See the Solaris Transition Guide for SVR4 file system types that are not supported.

Generic File System Commands

For current information on file system commands, see "Managing File Systems (Overview)" in System Administration Guide, Volume 1.

Directory and File Changes

This section describes the changes to directories and files between the SunOS release 4 and SunOS release 5.8.

/dev Directory

See "UFS File System Reference" in System Administration Guide, Volume 1 which supersedes information in the Solaris Transition Guide on /dev directory structure.

/etc Directory

See Solaris Transition Guide for changes to the /etc directory and files, including the SunOS release 5 files /etc/vfstab and /etc/shadow.

See "Run Levels" in System Administration Guide, Volume 1 for information on run control scripts such as rc0 that replace rc, rc.boot, rc.local, and rc.single in SunOS release 5.8.

See "UFS File System Reference" in System Administration Guide, Volume 1 which supersedes information in the Solaris Transition Guide on /etc directory structure.

/sbin Directory

See "UFS File System Reference" in System Administration Guide, Volume 1 which supersedes information in the Solaris Transition Guide on /sbin directory structure.

/usr Directory

See the Solaris Transition Guide for SunOS release 5 changes made to the /usr directory.

See "UFS File System Reference" in System Administration Guide, Volume 1 which supersedes information in the Solaris Transition Guide on /usr directory structure.

/var Directory

See the Solaris Transition Guide for SunOS release 5 information on the /var directory structure.

In SunOS release 5.8, the /var/run directory has been added as a repository for temporary system files that are not needed across system reboots. The /tmp directory continues to be repository for non-system temporary files.

For current information on /var directory, see "Managing File Systems (Overview)" in System Administration Guide, Volume 1.

/kernel Directory

See the Solaris Transition Guide for SunOS release 5 changes to the /kernel directory .

See "UFS File System Reference" in System Administration Guide, Volume 1 which supersedes information in the Solaris Transition Guide on /kernel directory structure.

/opt Directory

See the Solaris Transition Guide for SunOS release 5 changes to the /opt directory.

/sys Directory

See the Solaris Transition Guide for SunOS release 5 changes to the /sys directory.

Using File System Administration Commands

The following file system operations changed in SunOS release 5.7. See the System Administration Guide, Volume 1 for current information on SunOS release 5.8 file system administration.

  • Mounting file systems

  • Monitoring file systems

  • Sharing file systems

  • Creating a new file system

  • Checking a file system

  • Backing up and restoring files

    When you are ready to administer file systems on , see for detailed information and procedures.

Mounting File Systems and autofs

See the Solaris Transition Guide for SunOS release 5 changes on mounting file systems.

See "Managing File Systems (Overview)" in System Administration Guide, Volume 1 for current information.

See "Mounting and Unmounting File Systems (Tasks)" in System Administration Guide, Volume 1 for current procedures.

Monitoring File Systems

See Solaris Transition Guide for SunOS release 5 changes to the information on monitoring file systems.

See "Managing Disk Use (Tasks)" in System Administration Guide, Volume 2 for current information.

Sharing File Systems

See the Solaris Transition Guide for SunOS release 5 changes to the information on exported (shared) file systems.

See "Remote File System Administration" in System Administration Guide, Volume 3 for current information.

Creating New File Systems

See the Solaris Transition Guide for SunOS release 5 changes to the information related to the mkfs(1M) command.

See "UFS File System Reference" in System Administration Guide, Volume 1 for current information on the newfs(1M) and mkfs(1M) commands.

Checking File Systems

See the Solaris Transition Guide for SunOS release 5 changes to the information related to the fsck(1M) command.

See "Checking File System Integrity" in System Administration Guide, Volume 1 for current information on the fsck(1M) command.

Backing Up and Restoring Files

See the Solaris Transition Guide for SunOS release 5 changes to the information related to backup and restore commands.

See "Backing Up and Restoring Data Topics" in System Administration Guide, Volume 1 for references to information on backing up and restoring data and for current information on the commands:usfsdump, usfsrestore, dd, tar, and cpio.

UFS Logging

See "Managing File Systems (Overview)" in System Administration Guide, Volume 1 for current information on UFS logging.

Chapter 10 Setting Up a Solaris 8 Server to Support SunOS Release 4.x Diskless Clients

See the section called "Setting Up a Solaris 7 Server to Support SunOS Release 4 Diskless Clients" in Solaris Transition Guide for information on adding SunOS release 4 support to a SunOS release 5 server. The section tells you how to use discover4x, install4x, and convert4x programs available in the SUNWhinst package.

Note -

For Solaris 8 release, the SUNWhinst package is available on the CD.

Chapter 11 Managing Printers, Terminals, and Modems

This chapter updates information in the Solaris Transition Guide on changes to print, terminal, modem and SAF administration.

The chapter contains:

What's New in the Solaris 8 Operating Environment

Solaris Print Manager is a JavaTM-based graphical user interface that enables you to manage local and remote printer access. This tool can be used in the following name service environments: NIS, NIS+, NIS+ with Federated Naming Service (xfn), and files. You must be logged in as superuser to use this tool.

Solaris Printer Manager is the preferred method for managing printer access rather than Admintool. Solaris Print Manager centralizes printer information in a name service environment.

Adding printer information to a name service makes access to printers available to all systems on the network and generally makes printer administration easier because all the information about printers is centralized.

In this release, you can manage printer configuration information in the NIS+ name service without the underlying xfn application layer with Solaris Printer Manager. This provides better performance when accessing printer configuration information.

Printing

This section provides updated references to documentation on printer set up and administration.

Summary of Printing Differences

See the Solaris Transition Guide for information on the SunOS release 5.7 LP print service commands that replaced the SunOS release 4 lpd daemon and the lpr, lpq, lprm, and lpc commands.

The Solaris 8 printing software provides an environment for setting up and managing client access to printers on a network. The Solaris printing software contains these components:

  • Solaris Print Manager, a graphic user interface, provides the ability to make printers available to print clients via a name service.

  • Admintool, a graphical user interface, manages printing on a local system.

  • The LP print service commands, a command line interface used to set up and manage printers that also provides functionality above and beyond the other print management tools. Even if you do use Solaris Print Manager to set up printing, you will have to use some of the LP commands to completely manage printing in the Solaris environment. See "Administering Printers (Tasks)" in System Administration Guide, Volume 2 for more information.

Print Commands and the Compatibility Package

See the Solaris Transition Guide for information using the SunOS/BSD Source Compatibility Package to run SunOS release 4 print commands on a SunOS release 5 system.

For current information, see the Source Compatibility Guide.

See the Solaris Transition Guide for information on SunOS release 5 changes to printer administration and troff printing.

Serial Port Management

This section describes serial port management (which enables terminal and modem connections) through Admintool or the Service Access Facility (SAF).

System Administration Guide, Volume 2 describes current setup and installation procedures for serial devices.

Terminal and Modem Management

For current information on setting up and modifying serial port software on terminals and modems, see "Managing Terminals and Modems (Overview)" in System Administration Guide, Volume 2.

Service Access Facility (SAF)

For current information, see "Managing Terminals and Modems (Overview)" in System Administration Guide, Volume 2.

Chapter 12 Network Service Administration

This chapter updates information in the Solaris Transition Guide on TCP/IP, NFS changes, PPP, and UUCP.

The chapter contains:

What's New in the Solaris 8 Operating Environment

NFS server logging and the new 8.9.3 version of sendmail have been added to SunOS release 5.8.

NFS Server Logging

NFS server logging allows an NFS server to provide a record of file operations performed on its file systems. The record includes information to keep track of what is accessed, when it is accessed and who accessed it. The location of the logs that contain this information can be specified through a set of configuration options. These options also can be used to select the operations that should be logged. This feature is particularly useful for sites that make anonymous FTP archives available to NFS and WebNFSTM clients.

For instructions on how to enable NFS server logging, see "Automatic File-System Sharing" in System Administration Guide, Volume 3

sendmail, Version 8.9.3

Version 8.9.3 of sendmail includes the following changes:

  • A new configuration file option, called MaxHeadersLength, limits the length of the sum of all header lines in a given message. The default value is 32768 bytes. Incoming messages with headers that exceed this value are rejected.

  • A new file called /etc/default/sendmail can be used to store options to start sendmail with, rather than adding these options to the init script. The file makes it easier to upgrade systems, since the init scripts do not need to change.

  • The mail.local program has been extended to use the Local Mail Transfer Protocol. The protocol allows error codes to be returned for each recipient, so that the message is resent to just the recipients that did not receive the message rather than having to re-queue the message to all of the recipients. This protocol was added to sendmail in the Solaris 7 release.

  • A new command, named /usr/bin/praliases, can be used to turn the data in the alias database into plain text. If an argument is included on the command line, the command prints out a key:value pair, if the argument matches a key.

  • A new program called smrsh can be used to limit the number of commands that can be run using the "|program" syntax of sendmail. Only programs included in /var/adm/sm.bin can be run if this feature is enabled. Adding FEATURE(`smrsh') in the main configuration file enables this feature (see /usr/lib/mail/README for details.)

  • New options have been added to the vacation program: -f can be used to select an alternate database instead of ~/.vacation.ext; -m can be used to select an alternate message file instead of ~/.vacation.msg; and -s can be used to specify the reply address instead of the UNIX From line in the incoming message.

  • A change to the mailx program, allows for the From: header to be used as the basis of the sender instead of the envelope sender. This change makes mailx work like mailtool and dtmail.

For further information, see "What's New for the Solaris 8 Release?" in System Administration Guide, Volume 3.

Changes to TCP/IP

See "Overview of TCP/IP" in System Administration Guide, Volume 3 for current information on TCP/IP.

Changes to NFS

See "Accessing Remote File Systems Reference" in System Administration Guide, Volume 3 for information on:

  • share shareall, and /etc/dfs/dfstab which replace exportfs and /etc/exports.

  • lockd, and mountd which replace SunOS release 4 daemons rpc.statd, rpc.lockd, and rpc.mountd.

  • a modified version of nfsd which no longer spawns multiple copies to handle concurrent requests. Checking the process table with ps shows only one copy of the daemon running.

PPP

See "Overview of Solaris PPP" in System Administration Guide, Volume 3 for current information on PPP.

LDAP

See "FNS and Global Naming Systems" in Solaris Naming Administration Guide for current information on LDAP (Lightweight Directory Access Protocol).

IIIMP

See the Solaris Transition Guide.

UUCP

See the Solaris Transition Guide for a description of UUCP (UNIX-to-UNIX Copy) related to HoneyDanBer UUCP available with SunOS release 4 systems.

See "Overview of UUCP" in System Administration Guide, Volume 3 for current information.

Chapter 13 Using Name Services

This chapter updates information in the Solaris Transition Guide on NIS, NIS+ and DNS name services.

The chapter contains:

What's New in the Solaris 8 Operating Environment

Features added for Solaris 8 release include:

  • Native LDAP Native Lightweight Directory Access Protocol (LDAP) that provides the Naming Service switch back-end support for LDAP based directory service. See "SunOS release 4 and NIS-Compatibility Mode".

  • Support for domain name system (DNS) in system identification utilities. See "DNS".

Name Service Switch

See "The Name Service Switch" in Solaris Naming Administration Guide for current information.

SunOS release 4 and NIS-Compatibility Mode

NIS+ can be used on SunOS release 4 or SunOS release 5 workstations running NIS. In other words, machines within an NIS+ domain can have their nsswitch.conf files set to nisrather than nisplus. To access NIS+ service on machines running NIS, you must run the NIS+ servers in NIS-compatibility mode.

NIS-compatibility mode enables an NIS+ server running Solaris operating environment to answer requests from NIS clients while continuing to answer requests from NIS+ clients. NIS+ does this by providing two service interfaces. One responds to NIS+ client requests, while the other responds to NIS client requests.

This mode does not require any additional setup or changes to NIS clients. In fact, NIS clients are not even aware that the server that is responding isn't an NIS server--except that an NIS+ server running in NIS-compatibility mode does not support the ypupdate and ypxfr protocols and thus it cannot be used as a replica or master NIS server. For more information on NIS-compatibility mode, see the NIS+ Transition Guide.

Two additional differences are:

  • The instructions for setting up a server in NIS-compatibility mode differ slightly from those used to set up a standard NIS+ server. For details, see Solaris Naming Setup and Configuration Guide.

  • NIS-compatibility mode has security implications for tables in the NIS+ namespace. The NIS client software does not have the capability to provide the credentials that NIS+ servers expect from NIS+ clients. Consequently, NIS client requests are classified as unauthenticated. To enable NIS client access, NIS+ tables must provide access rights to unauthenticated requests. To understand more about the authentication process and NIS-compatibility mode, see "Security Overview" in Solaris Naming Administration Guide.

NIS+

See "Introduction to NIS+" in Solaris Naming Administration Guide for current information on NIS+ which has significant advantages over NIS in the areas of security, performance, scalability, and administration.

NIS and NIS+ Comparison

See "Differences Between NIS and NIS+" in Solaris Naming Administration Guide

Planning an NIS+ Upgrade

See NIS+ Transition Guide.

DNS

Domain name system (DNS) has been added to the list of name services that can be configured through the system identification utilities. See "Introduction to DNS" in Solaris Naming Administration Guide for current information on DNS.

Chapter 14 Solaris Common Desktop Environment

See the following documentation for current information on the Solaris Common Desktop Environment (CDE):