Chapter 1 Update 10/19/1998

The update dated 10/19/1998, part number 805-5766-11, includes late-breaking information that became available after the printed documentation, part number 805-5766-10, was released.

Installation Bugs

Additional Packages Required to Complete Installation of Locales (4177642)

When using Solaris Web Start to install any locale listed in the table below and the workstation option is selected rather than server option, the following packages must be added to complete the installation:

• SUNWploc1

• SUNWplow1

• SUNWpldte

• SUNWisolc

• SUNWarrf

• SUNWeugrf

• SUNWi13rf

• SUNWi15rf

• SUNWi1of

• SUNWi2of

• SUNWi2rf

• SUNWi4of

• SUNWi4rf

• SUNWi5of

• SUNWi5rf

• SUNWi7of

• SUNWi7rf

• SUNWi8rf

• SUNWi9of

• SUNWi9rf

• SUNWkoi8f

Affected locales are listed below.

For more information on adding packages, refer to the pkgadd man page.

CDE Issues and Bugs

Supported Y2K Dates Testing Procedure

CDE and Solaris 7 is Y2K-compliant. Use the date command to modify the system date and clock. If you want the system date and clock to reflect a future date for testing purposes, halt or shut down the system and run in single user mode. You can only modify the system date in single user mode. You can then boot your system and run in multi user mode with the desired test date.

Compiling Motif Programs on Solaris 7 (4172061)

This problem occurs when compiling a Motif program in the Solaris 7 operating environment if you link to an older shared library that has been compiled in the Solaris 2.5 or Solaris 2.6 operating environments and if the older library also uses the Motif API. In this case the Motif program uses Motif version 2.1 and the old shared library uses Motif version 1.2. A core dump occurs. This is not a binary compatibility problem for applications compiled in the Solaris 2.4, 2.5, 2.5.1, 2.6 operating environments. Those applications should run correctly in the Solaris 7 operating environment.

Workaround: When you use either one of the following two workarounds, copy the Solaris 2.6 Motif header file directory Xm located in /usr/dt/include/ to a temporary directory.

1. Modify the compile line that is usually represented as:

   cc m.c -I/usr/openwin/include -I/usr/dt/include -lXm -lXt -lX11

   to be as follows:

   cc m.c -I/usr/openwin/include -I/tmp -I/usr/dt/include /usr/lib/libXm.so.3 -lXt -lX11

   or

1. Alternately, copy /usr/dt/lib/libXm.so.3 to a temporary directory /tmp.

2. Execute the command ln -s libXm.so.3 libXm.so in the directory /tmp.

3. Use a Motif compile line similar to the following:

   cc m.c -I/usr/openwin/include -I/tmp -I/usr/dt/include -L/tmp -lXm -lXt -lX11

System Administration Bugs

Auditing of the Network (nt) audit Class Can Cause System Failure (4172702)

When auditing is enabled, selecting for the network audit events (nt class) can cause the system to fail.

Workaround: Do not enable auditing for the network audit events (nt class) or all audit events (all class) for any user or for the default of all users. The Solaris 7 operating environment has neither of these classes enabled. Individual user audit is controlled in the /etc/security/audit_user file which has the form username:classes:classes. Do not enter either the class allor nt in either of the classes fields.

For example, do not modify an /etc/security/audit_user file with entries like

root:lo,nt:no 	
bill:all:no

dir:/var/audit
flags:nt
minfree:20
naflags:lo

Security Bugs

Solaris 7 praudit and auditreduce Cannot Process Solaris 2.6 Audit Files (4167174 and 4168892)

Solaris 7 audit trails are incompatible with audit trails that have been generated in the Solaris 2.3, 2.4, 2.5, 2.5.1, 2.6 operating environments. You cannot use the praudit and auditreduce commands in the Solaris 7 operating environment to process audit files that have been generated in the Solaris 2.3, 2.4, 2.5, 2.5.1, 2.6 operating environments.

Workaround: Process audit trails only on the same release of Solaris on which they have been generated. This problem is addressed by the following Solaris 7106833 patch.

Documentation Issues

Federated Naming Service Programming Guide

Solaris 7 Software Developer Collection

The Federated Naming Service Programming Guide is not included in the Solaris 7 Software Developer Collection (SUNWabsdk package) on the Solaris 7 Documentation CD. The Guide may be found in the Solaris 7 Software Developer Collection on http://docs.sun.com.