Installation guide

■
bsmconv(1M)
■
bsmrecord(1M)
■
bsmunconv(1M)
■
audit_control(4)
xorgcfg and xorgconfig Utilities
The xorgcfg and xorgconfig utilities for generating xorg.conf les might no longer be
available in a future Solaris release.
The Xorg(1) server does not require an xorg.conf(4) le in many cases and will autocongure
itself if the le is not present. Users should use one of the following alternative methods to
generate an xorg.conf le for customization if the default conguration does not meet their
needs:
■
When the server is not already running, /usr/X11/bin/Xorg -configure, provides a
sample conguration le for the currently detected hardware in the system.
■
When Xorg is started without a conguration le, the xorg.conf data that Xorg
automatically generates is logged in the /var/log/Xorg.0.log log le. The xorg.conf data
might also be copied to an xorg.conf le for customization.
■
Users of NVidia graphics devices should use the provided nvidia-settings(1) and
nvidia-xconfig(1) utilities to generate or update device-specic congurations.
■
Users of Sun graphics devices for the SPARC platform should use the fbconfig(1) utility to
generate or update device-specic congurations.
Auditing File Size Statistics and File Size Restriction
Interfaces
The auditing le size statistics and le size restriction interfaces getfsize and setfsize,
consisting of the similarly named sub-commands within the auditon(2) system call and the
options to the auditconfig(1M) command, might not be supported in a future Solaris release.
Berkeley DB 4.2
Oracle Berkeley DB (BDB) 4.2 might not be supported in a future Solaris release.
Features That Might Be Removed in a Future Release
Solaris 10 10/09 Release Notes • October 2009122