![[Contents]](TOC.GIF){kind=small}
![[Prev. Chapter]](REW.GIF){kind=small}
![[Next Section]](NEXT.GIF){kind=small}
![[Index]](INDEX.GIF){kind=small}
![[Help]](HELP.GIF){kind=small}
This appendix contains brief descriptions of features that are new to the ULTRIX and UWS Version 4.5 operating system, and features that are new to the DIGITAL UNIX Version 4.0B operating system. Each description notes any migration issues between ULTRIX Version 4.5 and DIGITAL UNIX Version 4.0B. Then, this appendix discusses the interfaces that have been retired in DIGITAL UNIX Version 4.0B and whether their retirement affects migration from ULTRIX Version 4.5.
The following new features and changes are in ULTRIX and UWS Version 4.5: none has an effect on the migration of the operating system to DIGITAL UNIX Version 4.0B.
The
candc(8) command is a shell script
that examines the core image of the ULTRIX operating system to extract diagnostic
data.
This command has no effect on migration from ULTRIX to DIGITAL UNIX.
An
usrsms
option to the
param.c
file has been added for shared memory management.
This option has no effect on migration from ULTRIX to DIGITAL UNIX.
A new option,
-l,
has been added to the
ypserv(8yp) command to turn on log messages.
This new option has no effect on migration from ULTRIX to DIGITAL UNIX.
The X11R5
Xws
server now supports both
MX and PX graphic options.
Support for these graphic options has no effect on migration from ULTRIX to DIGITAL UNIX.
A new file,
/etc/securenets,
has been added:
it is required for portmapper operations.
This new file has no effect on migration from ULTRIX to DIGITAL UNIX.
The LinkWorks components have been retired and renamed DEClinks.
The retirement of the LinkWorks components have no affect on migration from ULTRIX to DIGITAL UNIX.
![[Prev. Section]](PREV.GIF){kind=small}
The remainder of this appendix contains the new and changed features in DIGITAL UNIX Version 4.0B. The discussion of each new feature and change concludes with a summary of its affect on the migration of ULTRIX Version 4.5 capabilities to DIGITAL UNIX Version 4.0.
The Common Desktop Environment (CDE) is the new default graphical user interface for DIGITAL UNIX. The CDE environment is designed to provide common services across all UNIX platforms, including a consistent user interface for end users and a consistent development environment for application developers across multiple platforms.
CDE on DIGITAL UNIX is based on the X Window System Release 6 (X11R6) and CDE/Motif 1.0 (OSF/Motif 1.2.4), and supplies the following desktop services and applications:
| Window Management | Workspace Management | Session Management |
| File Manager | Application Manager | Windowing
dtksh |
| Help | Keyboard Customization |
| Calendar | Calculator | MIME-capable Mail |
| Text Editor | Icon Editor | Terminal Emulator |
| Application Builder | Print Queue Manager |
CDE is provided in seven software subsets that require a total of 57.81 MB of free disk space for installation. See the Installation Guide for information on the subset names, contents, and sizes.
The CDE kit contains the following migration tools:
mailcv
mail conversion.
This utility converts
your
dxmail
folders to the conventional mail format used
by CDE
dtmail.
If you plan to use the
mailcv
utility to convert your existing mail folders, back up the folders before
converting them.
Do not use the
-d
option with this version
of the
mailcv
utility.
dxcaltodtcm
calendar conversion.
This utility
converts a DECwindows Calendar,
dxcalendar, database for
use with CDE Calendar,
dtcm.
A brief multimedia tutorial of CDE is located on the DIGITAL UNIX Version 4.0B Associated Products Volume 1 CD-ROM. Once the video tour is installed, you can access it through the application manager in the Information folder by double clicking on the CDE Video Tour icon.
The CDE session manager supports X11R6 screen saver extensions and you can now select animated screen savers instead of a blank screen. This release also enables the automatic locking of screens after a specified idle time. You can modifiy or disable both features from the CDE Style Manager menu. Click on the Screen icon, and select the options you want.
Because ULTRIX V4.5 uses X11R5 and OSF/Motif 1.1.3, there can be migration issues when using the migration tools in the CDE kit. These tools were intended only for migration from earlier versions of DIGITAL UNIX to DIGITAL UNIX Version 4.0B.
Although the mail and calendar conversion tools were designed for migrating from DECwindows on earlier versions of DIGITAL UNIX to DIGITAL UNIX Version 4.0, these same tools also can be used for converting ULTRIX DECwindows versions of the applications to DIGITAL UNIX Version 4.0B.
DECwindows migration issues are described in the manual CDE Companion guide.
The new Curses implementation in DIGITAL UNIX Version 4.0B incorporates the following sets of programming interfaces:
X/Open Curses, Issue 4
System V Multinational Language Supplement (MNLS)
Minicurses
BSD Curses
Because X/Open Compliant Curses, Issue 4, is backward compatible with earlier versions of X/Open Curses, there are no ULTRIX migration issues.
This release of DIGITAL UNIX supports Release 6 of the X Window System, Version 11 (X11R6) patchlevel 12. Prior versions of the operating system supported Release 5 (X11R5) patchlevel 26.
The DIGITAL UNIX port of X11R6 supports all the features and functionality of previous releases of DIGITAL UNIX. It also supports all X Consortium standard features of X11R6.
The following protocol extensions are new features in DIGITAL UNIX Version 4.0B:
BIG-REQUESTS. Gives clients the ability to use requests that are arbitrarily large, rather than being limited to the size restriction of the core protocol. This can result in a significant performance improvement for applications that use large requests.
DOUBLE-BUFFER. Enables double buffering, using the new X Consortium standard.
XIE (updated). Complete implementation of full XIE 5.0 protocol with a few exceptions.
XKEYBOARD (XKB).
The XKB (X Keyboard) server extension is new for X11R6 and for DIGITAL UNIX. XKB enhances control and customization of the keyboard under the X Window System by providing the following:
Support for the ISO9996 standard for keyboard layouts
Compatibility with the core X keyboard handling (no client modifications are required)
Standard methods for handling keyboard LEDs and locking modifiers such as CapsLock and NumLock
Support for keyboard geometry
In addition, the X11R5 AccessX server extension for users with physical impairments has been incorporated into the XKB server extension. X11R5 applied to versions of DIGITAL UNIX that preceded this release. These accessibility features include StickyKeys, SlowKeys, BounceKeys, MouseKeys, and ToggleKeys, and control over the autorepeat delay and rate.
Several applications that make use of XKB features are also new with
DIGITAL UNIX Version 4.0B.
These applications include
Xdec,
xkbcomp,
xkbprint,
xkbdfltmap,
dxkbledpanel,
dxkeyboard, and
accessx.
See the reference pages for more information.
Note that the final revision of the X Keyboard Extension, XKB Version 1.0, will be different from XKB Version 0.65, which is shipping with DIGITAL UNIX Version 4.0B. Avoid creating code that directly references the XKB API and data structures. Any X clients created with direct references must be recompiled and relinked when XKB Version 1.0 is shipped in a future release. You may also have to modify your source code.
There are no ULTRIX migration issues.
The following sections describe new or changed commands and utilities that are available in DIGITAL UNIX Version 4.0 and Version 4.0B.
Mtools
software is included in the
OSFDOCTOOLS410
subset.
In prior
releases, the software was installed by an optional worldwide support subset.
There are no ULTRIX migration issues.
The
sendmail
utility now allows the user to configure the fuzzy logic
for mail delivery.
Previously, if the recipient's address did not precisely
match any of the user names on the host, a best-match algorithm was applied
against the GECOS field in the
passwd
file.
If a unique
best-match was found, the mail was delivered to this user.
This behavior can
now be configured at run time using the
-oG
option on the
command line.
See
sendmail.cf(4)
for more information.
There are no ULTRIX migration issues.
The field width for the
Iused
and
Ifree
fields in the output of the
df
command has been increased to accommodate 12 digits when using
the
-i
switch.
This modification was made to support very
large file systems where the number of inodes could exceed the field width
that was previously set aside for these fields.
There are no ULTRIX migration issues.
To economize on disk space, reference pages are now shipped in
compressed format.
Compressed files were created with the
/usr/bin/gzip
utility.
The
man
and
xman
utilities automatically uncompress the reference pages.
The
catman
command has also been enhanced to work
with compressed
catman
files.
All three commands,
man,
xman
and
catman, still
provide support for uncompressed manpages.
The CDE online help viewer also
automatically uncompresses reference pages when they are accessed via a hyperlink
in a help volume.
For more information, see
man(1)
and
catman(8).
There are no ULTRIX migration issues.
Terminal support has been enhanced to support
non-DIGITAL terminals.
Entries have been added to the
terminfo
databases and the
termcap
file to enable this support.
New tools have also been added to assist users in modifying or porting other
termcap
and
terminfo
entries to DIGITAL UNIX.
These include the following:
captoinfo-Converts
termcap
files to
terminfo
entries.
infocmp-Uncompiles and, if required,
compares
terminfo
entries.
The
tput
and
tic
utilities have
also been enhanced.
There are no ULTRIX migration issues.
GNU Emacs has been updated to Version 19.28.
This
version is not upwardly compatible with GNU Emacs Version 18.5, the previous
version shipped with DIGITAL UNIX.
See the appropriate GNU Emacs documentation
in
/usr/lib/emacs/etc.
See the GNU Emacs documentation.
Performance Manager is a real-time performance monitor that allows users to detect and correct performance problems. Graphs and charts can show hundreds of different system values, including CPU performance, memory usage, disk transfers, file-system capacity, and network efficiency. Thresholds can be set to alert you to correct a problem when it occurs, and commands can be run on multiple nodes from the graphical user interface.
There are no ULTRIX migration issues.
This release introduces the ability to create a standalone bootable tape of the operating system. You can boot from the bootable tape as easily as you can boot from CD-ROM or a RIS area, but without the overhead of selecting or installing subsets. When you restore your system from the bootable tape, you must reconfigure your system using the System Management applications. You will need to adjust system parameters, such as the host name or IP address.
The binaries and shell scripts needed to create and restore a bootable
tape are installed with the base operating system.
The files reside in
OSFBINCOM410
and no other subsets are needed.
OSFBINCOM410
is the Kernel Header and Common Files (Kernel Build Environment)
subset.
Use the
btcreate
utility to create a standalone bootable
tape.
To extract and restore file systems from tape at the single-user level,
you use the
btextract
utility.
For more information, see
btcreate(8)
and
btextract(8).
Bootable tape capabilities do not exist on ULTRIX operating systems: there are no ULTRIX migration issues.
Partition overlap checks have been enhanced or added to the following commands:
newfs |
ufs_fsck |
mount |
The checks ensure that partitions will not be overwritten
if they are marked in use in the
fstype
field on the disk
label.
The overlap checks also ensure that no overlapping partition is marked
in use.
If a partition or an overlapping partition has an in-use
fstype
field in the disk label, the following commands inquire interactively
if a partition can be overwritten or not:
newfs |
mkfdmn |
addvol |
swapon |
voldisk |
voldisksetup |
See the reference pages for more information.
Partition overlap checks have been generalized by creating two library
functions:
check_usage
and
set_usage.
Two new
fstype
values have been added:
FS_RAW
and
FS_DB.
For example, you can use the library
function
set_usage
with database applications to set the
fstype
field of a disk partition that is in use by the database.
Similarly, you can use
check_usage
to determine the usage
of a disk partition or any overlapping partition.
There are no ULTRIX migration issues.
The
scsimgr
utility creates device special files for newly attached disk and
tape devices.
This utility is automatically invoked at system boot time.
You
can execute the command to add device special files for all disk and tape
devices attached to a specified SCSI bus at any time.
See the
scsimgr(8)
reference page for further details.
There are no ULTRIX migration issues.
This release complies with many new and changes standards.
See
standards(5)
for more information.
DIGITAL UNIX Version 4.0 now completes the implementation of the POSIX 1003.1b standard interface as approved by the IEEE standards board in September 1993 (IEEE Std 1003.1b-1993, Realtime Extension). The new features are described in Section G.8.9, Section G.8.10, and Section G.8.11. See the Guide to Realtime Programming for more information.
There are no ULTRIX migration issues.
The DECthreads library
libpthread.so
now implements the POSIX 1003.1c standard interface
as approved by the IEEE standards board in June 1995 (IEEE Std 1003.1c-1995,
POSIX System Application Program Interface).
The new POSIX (pthread) interface
supported with DECthreads is the most portable, efficient, and powerful programming
interface for a multithreaded environment.
These interfaces are defined
by
pthread.h.
See the
Guide to DECthreads
for more information.
There are no ULTRIX migration issues.
DIGITAL UNIX Version 4.0B includes the enhancements to the development environment that are discussed in the following sections.
Tcl/Tk is now available as part of the base operating system. Tcl/Tk is a public domain unencumbered scripting language and graphical tool kit. In addition to Tcl/Tk, a popular extension package, TclX is also included. TclX provides many UNIX extensions to the Tcl command language. Tcl version 7.4, Tk version 4.0, and TclX version 7.4 are included in this release. See the Installation Guide for information on how to identify and install the appropriate software subsets.
The available programs are:
/usr/bin/tcl
A tcl shell with TclX extensions
/usr/bin/tclsh
A hard link to
/usr/bin/tcl
/usr/bin/wishx
A Tcl/Tk/tclX shell
/usr/bin/wish
A hard link to
/usr/bin/wishx
/usr/bin/tclhelp
A graphical help browser for Tcl help
There are no ULTRIX migration issues.
The following changes have been implemented for DEC C++:
DEC C++ Version 5.3 Class Library is now threadsafe. See the DEC C++ Class Library Reference Manual for details on the threadsafe support, including a new Mutex Package.
Complex division catches divide-by-zero errors. The division routines within the Complex Library now catch divide-by-zero errors instead of signaling them.
Iostream assignment operators.
For
iostream
assignment operators, there is no longer a memory leak when you use the
*_withassign
assignment operators to initialize an object for which
you have called
xalloc().
Previously, the memory allocated
for the object by
xalloc()
was lost.
String extraction operator. The String extraction operator now takes care of dynamically allocating the String to accommodate the input.
ios::ate
mode.
When you open
a file specifying
ios::ate
but not
ios::app
to the
filebuf
open()
function, the
file is no longer opened in
O_APPEND
mode.
This incorrect
behavior caused all data to be written to the end of the file, regardless
of the current file position.
Exception handling. Various problems with exception handling have been fixed. Also, support for exception handling in DEC C++ Version 5.3 has been added.
Function
exp()
returns zero for underflow
errors .
When the Complex Library
exp()
function detects
an underflow error, the resulting value is now (0,0) instead of (+/- max-float,
+/- max-float).
Use of
clog()
and C++ Class Library iostream
clog.
A single application is restricted from using both the math library
function
clog()
and the iostream package's
clog
object.
This restriction is due to the fact that
libm
and
libcxx
each contain a definition for the
global symbol
clog
and those definitions are incompatible.
Furthermore, applications which reference one of the
clog
symbols cannot include both
-lcxx
and
-lm
on their
ld
command line.
An error will be generated by
ld
because
clog
is multiply defined.
catch(...)clause.
The
catch(...)
clause now catches C structured exceptions.
fstream
close()
clears
the error state.
The
fstream,
ifstream,
and
ofstream
close()
member functions
now clear the stream's error state when the close succeeds.
Call the
clear()
member function after the call to
close().
There are no ULTRIX migration issues.
The
Software Development Environment (SDE) has been repackaged to ease installation,
simplify licensing, and create a product identity.
The current SDE components
have been repackaged into a single
OSFSDE
subset, and all
of the pieces outside the SDE have been moved into logical subsets, including:
OSFINCLUDE
for all include files
OSFLIBA
for all static libraries
OSFPGMR
for commands outside the scope
of the SDE
Because the compiler is needed at installation time, some
SDE components have remained in the mandatory
OSFCMPLRS
subset.
The Ladebug debugger subsets have been renamed to the
OSF*
subset name prefix and can now be installed during a custom installation
of DIGITAL UNIX.
These changes have been made on the
DIGITAL UNIX
Operating System Volume 1 CD-ROM.
The FUSE Porting Assistant
has been added to the DIGITAL UNIX kit on the
DIGITAL UNIX Associated
Products Volume 1 CD-ROM.
This is a tool to help port code
to DIGITAL UNIX from a variety of platforms and operating systems.
The
OSFSDECDE
subset was also added to theDIGITAL UNIX Operating System Volume 1 CD-ROM.
It contains
the files necessary to access DECladebug and the Porting Assistant from CDE.
There are no ULTRIX migration issues.
The execution order for
init
routines in static executable
files has been modified to more closely match the execution order for
init
routines in dynamic executable files.
The
init
routines loaded from an archive library will be executed prior to any
init
routines loaded from objects and archives occurring earlier
on the linker command line.
Prior to this change,
init
routines were executed in the order they were encountered in processing the
link
command from left to right.
As a result,
init
order for static executable files was much different than the
init
order for equivalent shared executable files.
For existing applications that rely on the static
init
order used in prior releases of DIGITAL UNIX, you can use the new linker option
-old_init_order
to restore the strict left-to-right execution order
for static executable files.
There are no ULTRIX migration issues.
The
prof
command's pc-sampling
mode now supports profiling the shared libraries used by a program.
Linking
a call-shared program with the
cc
command's
-p
switch causes the resulting program to profile both the call-shared
executable file and all the shared libraries.
The following command displays
a combined profile:
# prof -all
New
-all,
-incobj,
-excobj, and
-stride
switches for the
PROFFLAGS
environment variable enable you to request per-procedure profiling
of the shared libraries or to select particular libraries to profile.
The related enhancements are:
Extended application programming interfaces (APIs) to
monitor(),
monstartup(), and
profil()
Use of 32-bit pc-sampling counters instead of 16-bit for
cc
-p
and
cc
-pg
profiling (gprof), except for calls to the traditional
monitor()
API.
Improved reliability in profiling multithreaded programs,
and reference page guidelines for use of
monitor_signal()
with threads.
prof
and
gprof
checking.
Profiling report formats are improved.
See
prof(1) and
monitor(3)
for further information.
There are no ULTRIX migration issues.
Both of the following
atom
and
prof
commands now profile the shared libraries used by a program:
# atom -tool pixie -all
# prof -pixie -all
The
threads
environment for
atom
also makes the
pixie
tool thread-safe, though
per-thread counts are not recorded.
Additionally, there are new file formats for
.Addrs
and
.Counts
files.
See
atom
(1),
prof
(1), and
pixie
(5) for further information.
There are no ULTRIX migration issues.
DIGITAL UNIX Version
4.0B introduces the Thread Independent Services (TIS) application programming
interface in the C run-time library
libc.
TIS provides
services that assist in the development of thread-safe libraries.
Thread synchronization may involve significant run-time cost, which is undesirable in the absence of threads. TIS enables thread-safe libraries to be built that are both efficient in the nonthreaded environment, yet provide the necessary synchronization in the threaded environment.
When DECthreads (pthreads) are not active within the process, TIS executes only the minimum steps necessary. Code running in a nonthreaded environment does not encounter overhead incurred by the run-time synchronization that is necessary when the same code is run in a threaded environment. When DECthreads are active, the TIS functions provide the necessary thread-safe synchronization.
There are no ULTRIX migration issues.
DIGITAL UNIX Version 4.0B has an optional high-resolution clock. To enable this option, add the following line to the kernel configuration file and rebuild the kernel:
options MICRO_TIME
The system clock ( CLOCK_REALTIME) resolution as returned by
clock_getres
will not change.
Timer resolution remains the same.
However, time
as returned by the
clock_gettime
routine will now be extrapolated
between the clock ticks.
The granularity of the time returned will now be
in microseconds.
The time values returned are SMP safe, monotonically increasing,
and have 1 microsecond as the apparent resolution.
There are no ULTRIX migration issues.
Realtime signals have been implemented to conform to the POSIX 1003.1b standard. This new feature includes queued signals with optional data delivery, and 16 user-definable realtime signals.
The following functions to support realtime signals were implemented:
sigqueue
sigtimedwait
sigwaitinfo
timer_getoverrun
There are no ULTRIX migration issues.
Synchronized I/O (file synchronization) has been implemented to conform to the POSIX 1003.1b standard. New functions for synchronized I/O under the UFS and AdvFS file systems include:
aio_fsync
Asynchronously writes changes in a file to permanent storage
fdatasync
Writes data changes in a file to permanent storage
The
open
function now takes the following new flags
for synchronized I/O:
O_DSYNC
Ensures synchronized I/O data integrity of the file accessed
O_RSYNC
Used for synchronized I/O read operations
There are no ULTRIX migration issues.
For applications
conforming to POSIX 1003.1b, the
_POSIX_4SOURCE
macro is
supported for DIGITAL UNIX Version 4.0B, but will be retired with the next
release of DIGITAL UNIX.
The macro
_POSIX_4SOURCE
is part
of an obsolete draft standard and is supported in this release for compatibility
only.
When possible, existing applications that use
_POSIX_4SOURCE
should be modified to use
_POSIX_C_SOURCE
instead.
The
_POSIX_C_SOURCE
macro is associated with a value,
which allows an application to specify the namespace it requires.
However,
as a general rule, avoid explicitly defining standards macros when compiling
your applications.
For most applications, the header file
unistd.h
provides the standards definitions that are needed.
There are no ULTRIX migration issues.
The DIGITAL Porting Assistant is a Motif-based tool to help you port your C, C++, and Fortran source code to DIGITAL UNIX from other UNIX and proprietary platforms, including OpenVMS. The Porting Assistant includes the following features:
Uncovers 32-bit dependencies
Checks your makefile commands and options
Helps find functions that your application needs
Helps develop code segments specific to DIGITAL UNIX
Provides additional information on porting your application
The Porting Assistant is licensed and provided to you with the DIGITAL UNIX Developers' Toolkit but requires separate installation.
To install Version 2.0 of the Porting Assistant, install subsets
PRTBASE200
and
PRTMAN200
(and their dependencies)
from the
DIGITAL UNIX Associated Products Volume 1 CD-ROM.
There are no ULTRIX migration issues.
The following sections describe networking enhancements contained in DIGITAL UNIX Version 4.0B.
This release includes
a new version of the
gated
routing daemon.
The update installation
procedure will detect if your system is configured to run the
gated
routing daemon.
If the DIGITAL supplied
gated
is detected, then the
/etc/gated.conf
file is moved to
/etc/ogated.conf.
Otherwise, if a user-supplied or customized
gated
is detected, then both the
/etc/gated.conf
and the
/usr/sbin/gated
files are saved with the
.PreUPD
suffix.
When the system is installed, the new gated R3.5 is the default version
in
/usr/sbin/gated.
The old
gated
Version
1.9 is supplied in
/usr/sbin/ogated.
Also, corresponding,
older
gated
reference pages are saved with an
o
prefix.
There are no ULTRIX migration issues.
This release contains
both a client and a server Dynamic Host Configuration Protocol (DHCP) daemon.
For DHCP client configuration, use the
netconfig
utility.
For configuration of client parameters on the DHCP server, use the
/usr/bin/X11/xjoin
utility, which provides a graphical user interface
to the
/etc/bootptab
file.
For more information on DHCP, see
joinc(8)
and
joind(8).
There are no ULTRIX migration issues.
This release supports Point-to-Point Protocol
(PPP), including support for BSD-style compression of entire packets.
This
is a negotiated option.
If a foreign peer cannot handle this, it should be
gracefully rejected via the
Protocol-Reject
of the Link
Control Protocol (LCP).
When using PPP with modems doing compression, it may be desirable to
force no BSD-style compression.
To do this, put
-bsdcomp
in either
/etc/ppp/options, or on the
pppd
command line.
PPP now has a configurable (at boot time) number of interfaces.
The
default is 1.
To specify a higher value, add the following line to the
/etc/sysconfigtab
file and reboot the system:
ppp:nppp=x
PPP documentation is available in
pppd(8),
pppstats(8), and
chat(8),
and in the
Network Administration
manual.
There are no ULTRIX migration issues.
A new Simple Network Management Protocol
(SNMP) architecture is present in this release.
The SNMP daemon,
snmpd, is now an extensible master agent.
End-user programmers can
develop subagent programs that communicate with
snmpd
to
implement their management information bases (MIBs) on DIGITAL UNIX systems.
The base operating system MIB support is implemented in a subagent program
called
os_mibs, which is started or stopped automatically
with
snmpd.
There are no ULTRIX migration issues.
This release supports the Host Resources MIB (RFC 1514). The MIB support daemon must query the system's devices to retrieve information required for this MIB. This query occurs when the daemon starts, and subsequently whenever a relevant SNMP request arrives.
This device querying is the default behavior, and may be configured
off.
See
snmpd(8)
for more information about configuring the SNMP agent.
There are no ULTRIX migration issues.
This release provides the following new enhanced security features:
Support for per-user resource limits in user profiles, using
setrlimit.
Nonshadowed passwords are allowed, while using other extended profile features.
The system administrator can control whether the
ttys
database is updated on logins.
Wildcard support for
ttys
has been extended
to X displays.
User profiles and
ttys
information are
stored in database files for faster access and update (resulting in faster
logins).
The new utilities
edauth
and
convuser
are available.
See the
Security
manual and
setrlimit(2),
edauth(8),
and
convuser(8).
ULTRIX has had enhanced security since 1990; now DIGITAL UNIX has it. Differences that affect migration are discussed in the Security manual, in an appendix on migration.
The following sections describe file system enhancements have been implemented in DIGITAL UNIX Version 4.0B.
The following sections describe Advanced File System (AdvFS) enhancements have been implemented in DIGITAL UNIX Version 4.0B.
There is a new mechanism for limiting the amount of kernel memory that AdvFS uses for its access structures. This may be necessary only for systems with 64 MB or less memory, and AdvFS as the default file systems. This is applicable to all hardware configurations.
There are two new kernel parameters relevant to AdvFS that you can modify
using the
sysconfig
or
sysconfigdb
commands.
They are
AdvfsAccessMaxPercent
and
AdvfsAccessCleanupPercent.
Traditionally, AdvFS directories were never truncated, even though many of the files in the directory had been deleted. This created a problem if the directory file became very big. For example, if several hundred thousand files were added to a directory, then the directory file itself grew very large. Even though most of the files in that directory were subsequently deleted, operations that required scanning the directory remained inefficient because the entire directory file still needed to be read.
AdvFS now truncates directory files when all of the entries at the end of the directory have been deleted. This truncation is done on 8 KB boundaries, so the size of a directory is always a multiple of 8192.
One ambiguity of directory truncation is that the truncation is done when files are created and not when they are deleted. This is done because of the efficiency of underlying algorithms, and is the same model used by UFS for directory truncation. For example, after most files in a given directory are deleted, the size of the directory file itself will not decrease until a new file is inserted into that directory.
The AdvFS file system does not exist on ULTRIX systems, so there are no migration issues.
Access Control Lists (ACLs) on files and directories
are a new feature in this release.
They are manipulated with the
getacl
and
setacl
commands.
See the
Security
manual and the reference pages for more information.
The ULTRIX operating system does not support ACLs or property lists (ACLs are implemented as a specific type of property list), so there are no ULTRIX migration issues.
DIGITAL UNIX now provides the following new features for the Logical Storage Manager (LSM):
Two new LSM commands,
volsave
and
volrestore, provide an easy way to back up and restore the LSM configuration
database.
See the reference pages for these commands.
The Basic Operations menu in LSM's graphical interface,
dxlsm, now provides support for disk operations.
For example, how
to add a disk to LSM.
The LSM limits have increased as follows:
The maximum number of LSM volumes on a system has increased from 256 to 4093.
The maximum number of plexes on a system has increased from 256 to 4096.
The maximum number of subdisks in a plex has increased from 256 to 4096.
The maximum number of disks that can be added to LSM has increased from 128 to 256.
The maximum size of an LSM volume has increased from 128 GB to 512 GB.
The functionality and syntax of the LSM commands used for encapsulation, unencapsulation, and mirroring have changed in this release, as follows:
The
volencap
command now supports the following
features and functions.
For details, see
volencap(8).
Allows the initialization of LSM and encapsulation of the system disk in one step. This requires the use of a free partition table entry.
Can be used to encapsulate all partitions on a disk. This requires the temporary use of a free partition table entry if the system disk is being encapsulated.
Can be used to encapsulate only the root and swap partitions.
Automatically creates a new disk group if specified.
Subsumes the functionality of the
voladvdomencap
command.
Takes multiple arguments.
Uses a simple disk instead of a sliced disk for system disk encapsulation.
For disk label characteristics, assumes that partition
c
maps the entire disk, and that an in-use partition has an
fstype
field other than
UNUSED.
(If a partition's
fstype
field is
UNUSED, then
volencap
may allocate that partition table entry for its use.)
The
volrootmir
command now supports the
following features and functions.
For details, see
volrootmir(8).
Can be used to mirror all volumes on the system disk by specifying
the
-a
option.
This option requires the target disk to
be of the same type as the source disk.
Can be used to encapsulate only the root or swap partition
by omitting the
-a
option.
This procedure requires that
the target root and swap partitions are large enough to hold
rootvol
and
swapvol, but the target and source disks
need not be of the same type.
When used with the
-a
option, the
volunroot
command unencapsulates all LSM volumes on the system
disk, not just
rootvol
and
swapvol.
The requirements for unencapsulation are:
The partition associated with the volume must have been initialized
as a
nopriv
disk.
The volume must map directly to the partition (that is, the volume size must be equivalent to the partition size).
The volume must not be mirrored.
For details, see
volunroot(8).
There are no ULTRIX migration issues.
Two new functions,
check_usage
and
set_usage, are available for
use by applications.
These functions check whether a disk partition is marked
for use and set the
fstype
of the partition in the disk
label.
See the reference pages for these functions for more information.
There are no ULTRIX migration issues.
The following sections describe the new features implemented in DIGITAL UNIX Version 4.0B to support internationalization. There are no ULTRIX migration issues.
The Internationalization (I18N) Configuration Tool, available through the CDE Application Manager, is one of the SysMan system administration configuration tools. The I18N Configuration Tool provides a graphical interface that enables you to configure internationalization-specific settings. It also provides a convenient way to see which countries, locales, fonts, and keymaps are currently supported on your system. Use this tool to remove unused fonts and unrequired country support.
This release provides a new set of locales and codeset converters that support the Unicode and ISO 10646 standards. The codeset converter modules enable an application to convert between other supported codesets and UCS-4.
DIGITAL UNIX also provides a function called
fold_string_w()
that maps one Unicode string to another, performing the specified
Unicode character transformations.
For more information, see
fold_string_w(3).
For more information on the Unicode support, see
Unicode(5).
Worldwide
support subsets no longer install internationalized Mail Handler (MH) software
in the
/usr/I18N/bin/mh
directory.
In DIGITAL UNIX Version
4.0B, internationalization features have been merged into the default Mail
Handler (MH) whose files are located in
/usr/bin/mh.
Check
the value for the
mhpath
resource used to find the DECwindows
Mail application.
If necessary, change this value to be
/usr/bin/mh.
The
mule
editor is a multilingual version of GNU Emacs and supports
the following kinds of characters:
ASCII (7-bit)
ISO Latin-1 (8-bit)
Japanese, Chinese, and Korean (16-bit) as specified by the ISO 2022 standard and its variants (EUC, Compound Text, and so on)
Chinese in both GB and Big 5 encodings
Thai as specified by the TIS 620 standard
The
IOSWWMULE400
subset installs Version 2.3 of
the GNU mule editor and associated software.
Corresponding sources are available
in the
IOSWWMULESRC400
subset.
DIGITAL UNIX does not include public domain fonts that you can use with
mule.
See the
mule-2.3/README.Mule
file installed by the
IOSWWMULESRC400
subset to find out how you can obtain public domain
fonts.
The DIGITAL UNIX software is enhanced with
lisp
libraries
that support the
dechanzi
codeset for Simplified Chinese
and the
dechanyu
codeset and tsangchi input method for
Traditional Chinese.
These libraries are included in the IOSWWMULE400 subset
and installed in the
/usr/i18n/mule/lib/mule/site-lisp
directory.
For more information about mule, see
mule(1).
DIGITAL
UNIX Version 4.0B includes support for Catalan, Lithuanian, and Slovene program
localization.
See
Catalan(5),
Lithuanian(5), and
Slovene(5)
for information
about associated codesets, locales, keyboards, and fonts.
The
man
command can automatically
invoke the
iconv
utility to perform codeset conversion
of reference page files.
This allows you to install one set of reference pages
to support locales that have the same language and territory but different
codesets, thereby reducing file redundancy on the system.
For more information,
see
man(1).
Dynamic Device Recognition (DDR) is a framework for describing the operating parameters and characteristics of SCSI devices to the SCSI CAM I/O subsystem. You can use DDR to include new and changed SCSI devices into your environment without having to reboot the operating system. You do not disrupt user services and processes, as happens with static methods of device recognition.
Beginning with DIGITAL UNIX Version 4.0, DDR is preferred over the current,
static method for recognizing SCSI devices.
The current, static method, as
described in
System Administration, is to edit SCSI
device customizations into the
/sys/data/cam_data.c
data
file, reconfigure the kernel, and shut down and reboot the operating system.
Note
Support for the static method of recognizing SCSI devices will be retired in a future release of DIGITAL UNIX.
DIGITAL UNIX Version 4.0 and Version 4.0B support both methods of recognizing SCSI devices. Both methods can be employed on the same system, with the restriction that the devices described by each method are exclusive to that method (nothing is doubly defined).
The information DDR provides about SCSI devices is needed by SCSI drivers.
You can supply this information using DDR when you add new SCSI devices to
the system, or you can use the
/sys/data/cam_data.c
data
file and static configuration methods.
The information provided by DDR and
the
cam_data.c
file have the same objectives.
When compared
to the static method of providing SCSI device information, DDR minimizes the
amount of information that is supplied by the device driver or subsystem to
the operating system, and maximizes the amount of information that is supplied
by the device itself or by defaults specified in the DDR databases.
You can also use DDR capabilities to convert customizations in the
cam_data.c
file to information in the DDR
/etc/ddr.dbase
text database.
For more information about DDR, see
System Administration,
ddr_config(8), and
ddr.dbase(4).
Because dynamic device recognition does not exist on ULTRIX systems, it does not affect migration. However, in a future release of DIGITAL UNIX, the name space for SCSI devices will increase, and that change will affect current versions of both operating systems.
With the release of DIGITAL UNIX Version 4.0, several features of previous versions of the operating system were retired. The documentation for previous versions of DIGITAL UNIX announced that these features would be retired. The retired features and their ULTRIX migration issues (if any) are:
Support for ULTRIX RIS to DIGITAL UNIX client functionality
ULTRIX migration issues: If you have been using ULTRIX systems as RIS servers for DIGITAL UNIX client systems, that capability will not work for a DIGITAL UNIX Version 4.0 client. You will need to serve DIGITAL UNIX Version 4.0 clients from DIGITAL UNIX RIS servers. ULTRIX systems can still RIS serve ULTRIX client systems.
The
oawk
version of the
awk
command
There are no migration issues because the
owak
command
does not exist in ULTRIX.
Routines that were duplicated in thelibc
and
libm
libraries have been removed from the
libc
library.
ULTRIX migration issue: application developers might have to add the
-lm
option to their compiler command line.
The
-n
option from
/usr/bin/echo
and
/bin/echo
There are no ULTRIX migration issues.
Ethernet trailer encapsulation
There are no ULTRIX migration issues.
Linkworks run-time library
There are no ULTRIX migration issues.
Logical Volume Manager
There are no ULTRIX migration issues.
Obsolete POSIX real-time interfaces
There are no ULTRIX migration issues.
XIE V3.0 interface, server support (although run-time support will still be provided transparently through the client)
There are no ULTRIX migration issues.
The POLYCENTER Common Agent (extensions to the SNMP V1.0 agent)
There are no ULTRIX migration issues.
Read the DIGITAL UNIX release notes for information about those features scheduled for retirement in future releases of the operating system. Knowledge of these pending changes will help you determine wise migration tactics.