This chapter lists features of Tru64 UNIX scheduled to be removed
from, or changed in, future functional releases.
Users and developers should
plan to migrate away from or accomodate changes in these features in the near
future.
8.1 DECwindows Applications
The following DECwindows utilities and tools have been retired from Tru64 UNIX.
These dx* tools and utilities, commonly known as DECwindows, have been replaced
by the dt* tools in Common Desktop Environment (CDE) that were introduced
in Version 4.0.
The replacement applications are listed in
Table 8-1.
Not all of the dx* applications that have been retired have a replacement
due to the limited use or capability of that specific tool or utility.
Table 8-1: Retired DECwindows Applications
| Retired Tools/Utilities | Replacement Option(s) |
| dxmail | dtmail |
| dxprint | dtlp |
| dxcalendar | dtcm |
| dxcalc | dtcalc, xcalc |
| dxclock | Front Panel, xclock |
| dxpaint | dticon/dtstyle, bitmap |
| dxnotepad | dtpad |
| dxbook | dthelpview, Netscape |
| dxcardfiler | None |
| dxsession | xdm, dtsession |
| dxvdoc | ghostview |
| libids | None |
It is recommended that you migrate to the dt* tools and utilities or other options as soon as possible.
The CDA applications in
Table 8-2
have also been
retired.
Table 8-2: Retired CDA Applications
| caspar | cdoc | ctod |
| ddifanls | ddifps | ddiftext |
| dtifanls | dtifddif | dtoc |
| textddif | vdoc | libcapsar |
| libcda | libcda_be | libcda_fe |
| libddif | libddif_be | libddif_fe |
| libimg | libdvs | libids_nox |
8.2 Adobe Display PostScript, Client Libraries, and X Server Extension
Ÿ
Adobe Systems Incorporated has retired its Display PostScript (DPS) product, which includes the client libraries, X server extension, and various applications and examples. Therefore, the Adobe DPS product has been retired from Tru64 UNIX. No replacements will be available. Customers who have used the Adobe DPS libraries to develop their own applications will not have a migration path.
The following Adobe applications have been retired and are no longer included with the Tru64 UNIX operating system:
dpsclock
dpsexec
draw
fontview
libdps.a
and
libdps.so
libdpstk.a
and
libdpstk.so
libpsres.a
and
libpsres.so
lib_adobe_dps.so
makepsres
pswrap
scratchpad
showps
texteroids
wonderland
xepsf
All Adobe fonts under
/usr/lib/X11/fonts/Type1Adobe
The following applications, which use Adobe DPS, have been retired and are no longer included with the Tru64 UNIX operating system:
dxvdoc
dxbook
dxnotepad
(internationalized version in WorldWide Language Support software on the Associated Products CD-ROM)
During an update installation from Version 4.0D or Version 4.0F to Version 5.0, the DPS commands, libraries, and documentation noted above are marked by the installation update procedure as obsolete inventory and then removed from the system later in the procedure.
Because these obsolete components have been retired from the operating system, they are no longer distributed, and they may not be compatible with a future release. They are not supported as part of the Tru64 UNIX product beginning with this release.
If you have applications or procedures that depend on the DPS software that has become obsolete, you may wish to have the obsolete DPS software remain on your system, yet remove the other obsolete software at this time.
To do this, you can edit the file
/var/adm/smlogs/upd_obsolete_files
so that the DPS software components are not listed, before you perform the
updadmin
procedure.
If you remove the DPS components from your system using the
updadmin
utility, you will have the opportunity to archive all of the obsolete
components.
If you prepare an archive copy, and later discover a dependency
on the obsolete DPS components, you can restore them to the system from the
archive copy.
If you remove the obsolete DPS components without making an archive copy, there is no way to restore them from the product distribution media for the current release.
The freeware application
gv
may be a suitable replacement for
showps.
It has a different user interface than
showps
but has no dependency on the obsolete DPS software libraries.
Some of the freeware applications delivered with Version 4.0D had dependencies
on the DPS client libraries.
Those applications have been rebuilt using the
GhostScript libraries available on the freeware distribution media.
8.3 Nonconforming Curses Library
Version 4.0 of the operating system included a new X/Open Compliant
Internationalized Curses library.
This library was not binary
compatible with previous versions of the Curses
library, so compatible binaries (named
libcurses.a
and
libcurses.so)
were shipped in separate directories for Version 4.0.
These compatible binaries have been retired and
removed from this release of Tru64 UNIX.
8.4 The -oldc C Compiler
The C compiler for DIGITAL UNIX has been officially replaced by Compaq C
for Tru64 UNIX.
The older compiler is no longer distributed
in this release of Tru64 UNIX.
The
-oldc
switch, which was used to request
the old C compiler from the
cc
command in previous versions, is
no longer supported.
The
cc
command now issues an error if the
-oldc
switch is specified.
8.5 The dbx Debugger
The
dbx
symbolic debugger will be retired in a future release of Tru64 UNIX.
The
dbx
debugger will be replaced by the
ladebug
debugger, which is a superset of the
dbx
functionality.
The
ladebug
debugger is command line compatible with
dbx
and also supports a graphical user interface.
It is recommended that you begin using the
ladebug
debugger now and report any problems.
This
will provide a higher quality replacement when
dbx
is finally retired.
8.6 Tru64 C Compiler Default Change from -std0 to -std
The default language mode for the Tru64 UNIX C compiler has
changed from
-std0
to
-std.
You can revert back to the previous default language mode by adding the
-std0
flag to the
cc
command line, the
/usr/ccs/lib/cmplrs/cc/comp.config
file or the
$DECC_CC
or
$COMP_HOST_ROOT
environment variable definitions.
8.7 Change in struct utmp, struct utmpx, and struct lastlog
To bring them
into compliance with several UNIX and Internet standards, the
struct
utmp,
struct utmpx, and
struct lastlog
structures have been changed.
These changes affect the
/usr/include/utmp.h,
/usr/include/utmpx.h, and
/usr/include/lastlog.h
files :
The time field in the
struct utmp
structure
has changed from a
time_t
structure to a
struct
__ut_timeval
structure (to be consistent with the
/usr/include/utmpx.h
file).
The
ut_host
field size (in the
struct utmp
and
struct utmpx
structures) has
been increased to comply with relevant Internet RFCs.
The
ll_line
and
ll_host
manifest constants in the/usr/include/lastlog.h
file have
changed to allow their sizes to correspond to the
ut_line
and
ut_host
fields in
struct utmp
and
struct utmpx
structures.
These changes also affect the format of the
/var/adm/utmp,
/var/adm/wtmp, and
/var/adm/lastlog
files.
The following conversion programs are supplied:
/usr/lbin/wtmpconvert
/usr/lbin/llconvert
The programs enable you to convert your existing
/var/adm/wtmp
and
/var/adm/lastlog
files to the new format
or convert new format files to the old format for use by existing programs.
See the corresponding reference pages for more information.
8.8 C Language long double Type Changing to 128 Bits
As of Tru64 UNIX Version 5.0 the default size of the C language long double type changed from 64 bits to 128 bits. This allows applications to perform mathematical calculations on larger numbers and with more precision than was possible with the previous long double type. Prior to Version 5.0, the long double type was the same size as the double type (64 bits).
If an application was linked using an earlier version than Tru64 UNIX
Version 5.0, there is one binary incompatibility that may affect
the application.
If the application was linked using the
-call_shared
switch, it can experience an incompatibility with the new default
related to the input and output of long double types.
Previously,
printf,
scanf, and similar functions interpreted
the format code
%Lf
(capital L followed by f) as a 64-bit
long double type.
Now, the format code
%Lf
specifies a
128-bit long double type.
8.9 C Library Functions and POSIX P1003.1C
As of Version 4.0 of the operating system, the following C library functions
exist in two versions due to conflicts between previous versions of
Tru64 UNIX and the recent IEEE POSIX P1003.1C standard (these new
interfaces are in effect by default).
The old interfaces are
currently accessible by defining the C preprocessor symbol
_POSIX_C_SOURCE
to
199309L.
asctime_r getgrnam_r getpwuid_r localtime_r readdir_r ctime_r getlogin_r gmtime_r rand_r ttyname_r getgrgid_r getpwnam_r
Binary compatibility is maintained in Version 4.0G;
however, these routines will be retired in a future release of
the operating system.
The obsolete versions should not be used in new
designs.
These routines formerly resided in
libc_r.a
and
libc_r.so,
but were merged into the standard C runtime library.
8.10 POSIX 1003.4a (draft 4) pthread Routines in DECthreads
The POSIX 1003.4a, Draft 4 interface of
POSIX Threads (formerly DECthreads) will be retired in a future release of Tru64 UNIX.
Applications that were written using the POSIX 1003.4a, Draft 4 API should
be migrated to the IEEE Std.
1003.1-1996, POSIX System Application Program
Interface provided by POSIX Threads.
The POSIX 1003.1c standard interface
is the most portable, efficient, and powerful programming interface offered
by POSIX Threads.
A compatibility mode for the Draft 4 POSIX 1003.4a API
has been provided to ease migration.
This compatibility mode will be removed
in a future release.
8.11 DECthreads CMA Interface
The CMA interface
of POSIX Threads (formerly DECthreads) is obsolete beginning with this release.
Obsolescence means that while the CMA API continues to exist and is supported
in Tru64 UNIX, CMA routines are no longer documented or enhanced.
It is
recommended that you port your CMA-based application to the IEEE Std 1003.1-1996,
POSIX System Application Program Interface provided by POSIX Threads Library.
8.12 Asynchronous I/O Binary Compatibility
Data structures for asynchronous I/O, like
aio_read()
and
aio_write(), changed between Version 3.2
and Version 4.0 of the operating system.
The kernel currently handles these
differences so that applications built under Version 3.2 continue to run when
executed on Version 4.0x.
In the next major release of the operating system, support for applications
built under Version 3.2x using asynchronous I/O will be discontinued.
You
will need to recompile and relink these applications to run under Tru64 UNIX
Version 4.0D or higher.
8.13 Nemacs
Nemacs Version 3.3.2, a public domain Japanese implementation
of Emacs, has been removed from this release of Tru64 UNIX.
Mule, a public domain multilingual implementation of Emacs,
has been carried forward as the replacement functionality for Nemacs.
The Nemacs subsets
IOSJPNEMACS500
and
IOSJPNEMACSSRC500
will be removed from the system.
For more information on
Mule, refer to the
mule(1)
reference page.
8.14 Berkeley Software Distribution TTY-NAME
The intent to retire the BSD
TTY-NAME
namespace was announced in DEC OSF/1 Version 3.0.
This functionality will be retired in a future release.
8.15 SCSI Device Names
Support for rz and tz SCSI device names will be retired in a future release of Tru64 UNIX. Any code that derives knowledge about a device from the ASCII name or minor number may be impacted.
All code that uses the current namespace will be compatible until the
change occurs because a mechanism that ensures binary compatibility has been
provided.
8.16 The -x and -p Options in addvol and mkfdmn
The
-x
and
-p
options to the
addvol
and
mkfdmn
commands
allow you to set the per-volume bitfile metadata table (BMT) when you create
a new volume or file domain.
Users typically set the BMT to prevent an extent
exhaustion problem.
In Version 4.0D and later, the limitations in the operating system that
caused the extent exhaustion problem were removed, hence the
-x
and
-p
options are no longer needed and will be retired
in a future release.
8.17 LSM Block Change Logging (BCL)
The Logical Storage Manager Block Change Logging (BCL) feature has been retired. It has been replaced with Dirty Region Logging (DRL). DRL logs regions instead of blocks for writes to LSM mirrored volumes. For most environments, DRL provides the same ability as BCL to quickly resynchronize mirrors after a failure, but with considerably less logging overhead.
The logging format and configuration for DRL is not compatible
with BCL.
Therefore, this release provides support to automatically
migrate and reconfigure mirrored volumes from BCL to DRL where possible.
However, some existing mirrored volume configurations with BCL may require
manual reconfiguration to continue to exploit logging for
faster mirror recovery.
8.18 LSM volassist Command Syntax
In Version 5.0 of Tru64 UNIX, the syntax of the
volassist
changed.
It no longer supports the following
constructs:
[!]medianame,offset
You will still be able to use
[!]medianame,offset
construct but you cannot specify an offset.
If you need to
specify an offset, you will have to use the low-level commands
to create subdisks, plexes, and volumes exactly as required.
alloc=size
A new construct,
alloc=storage-spec[,storage-spec,...],
replaces
alloc=size.
However, the new construct does not allow you to specify sizes for all
allocations.
You need to use the low-level commands to create
subdisks, plexes, and volumes exactly as required.
align=size
Two new constructs,
diskalign
and
nodiskalign,
replace
align=size,
allowing you to specify whether subdisks should be created on cylinder
boundaries.
If you require the ability to specify alignments for all
allocations, you need to use the low-level commands to create
subdisks, plexes, and volumes exactly as required.
The Motif Version 1.1.3 libraries have been provided as run-time services for compatibility with applications that have not yet converted to Motif 1.2. Development support was retired in DEC OSF/1 Version 2.0.
In Version 4.0 of the operating system, the Motif 1.1.3 libraries were
moved to an optional subset.
Applications requiring the libraries will see
an error from the loader, requiring you to install the optional
subset.
This optional subset will be removed from the product in a future
release.
8.20 XIE Version 3.0 X Client Extension
Tru64 UNIX Version 4.0G supports XIE Version 5.0.
Support for XIE Version 3.0 server extensions was removed in Version 4.0.
Client support will be removed in a future release.
8.21 Microsoft Sound Board Driver
In Version 4.0 of the operating system, the device driver for the base audio on
the AlphaStations and AlphaServers was removed from
the base operating system.
This device driver supported the Microsoft
Sound Board (MSB), the AlphaStation Sound Card, and the built-in audio
hardware shipped with certain AlphaStation systems.
The driver binaries are now available as part of the
Multimedia Services for Tru64 UNIX kit on the
Tru64 UNIX Associated Products, Volume 1
CD-ROM in the
MMEDRVMSB
subset.
The following files will be removed from the base operating system:
/usr/sys/BINARY/msb.o
/usr/sys/include/io/dec/eisa/msb.h
/usr/sys/include/io/dec/eisa/msb_reg.h
You can also obtain support for this device from the Multimedia Services
for Tru64 UNIX kit that is located on the Software Products
Library CD-ROM.
Support is also factory-installed on all
AlphaStation Tru64 UNIX packaged systems.
The license for this
product is bundled with AlphaStations so that you can use it at
no additional cost.
8.22 Graph Utility
The
/usr/bin/graph
utility will be removed in the next major release of Tru64 UNIX.
8.23 The atmsetup Script
The
atmsetup
script introduced in Version 4.0D has been superceded by a new application.
The new application is
part of the SysMan suite, and provides
a full graphical user interface.
The
atmsetup
command now invokes this new SysMan application.
You can access the
atmsetup
script by including the
-old
flag with the
atmsetup
command.
The
atmsetup
script will be retired in a future release of Tru64 UNIX.
For more information on how to use the new
atmsetup, application
see the
atmsetup(8)
reference page and the
Asynchronous Transfer Mode
guide.
8.24 Remote Prestoserve Support
Prestoserve support for remote operations has been retired.
This means that the
-h
option of the
presto
command
is no longer supported.
Users who require the ability to perform
presto
operations remotely can do so by using
telnet,
rlogin,
or
rsh
to gain access to a shell on the remote system and then performing the
operation locally.
8.25 Installupdate -i Option
The
-i
option to the
/sbin/installupdate
command
will be retired in a future release of the operating system.
The
-i
option currently allows you to interactively
select kernel components after the new software subsets have been
installed.
Starting with the next major release, this flag will be unnecessary
because you will be able to interactively select optional kernel components
at the beginning of the update installation process, prior to software installation.
These kernel components will be built into the kernel automatically during
the kernel build phase at the end of the update installation; therefore, you
need not be present at that time.
8.26 Different awk Versions
The
gawk
and
oawk
versions of the
awk
command have been retired.
Only the XPG4-compliant version of the
awk
command is
supported in this release.
Scripts
that use variations of the
awk
command should access the
/usr/bin/awk
version.
8.27 The secsetup Script
The
/usr/sbin/secsetup
script, used to configure
Enhanced Security authentication support, has been retired in this release
of Tru64 UNIX.
It has been moved to the
OSFOBSOLETE
subset.
The script has been replaced by the
secconfig
application.
The
secconfig
application is a graphical user
interface and is integrated with the SysMan utilities.
8.28 Open3D TURBOchannel and PVpci Device Support
The following Open3D devices have been retired in this release of Tru64 UNIX:
PV-L
PV-M
PV-P
These devices are also known as:
ZLX-L1, L2
ZLX-M1, M2
ZLXp-L1, L2
Open3D Version 4.4 is the last version of Open3D that supports the PV-L and PV-M cards. Open3D Version 4.9 is the last version of Open3D to support the PV-P graphic adapters.
Additionally, 3D support for the HX+ and TGA has been retired. These are also known as the ZLX-E1, E2, E3; and ZLXp-E1, E2, E3. DIGITAL UNIX 2D support will continue for the initial release of Tru64 UNIX Version 5.0 for these cards. The initial release of Tru64 UNIX Version 5.0 will also be the last release to support the HX and TX graphics adapters.
The replacement functionality is PCI-based systems and graphics devices
supported on those systems.
8.29 System Management Utilities
The following setup scripts have been retired in this release:
bindsetup
netsetup
nfssetup
ntpsetup
These scripts have been replaced by tasks that you can perform by running the SysMan Menu and navigating to the desired item, or directly from the command line by using the appropriate menu accelerator. The following table maps the replacement functionality and accelerator:
| Retired Script | SysMan Menu Item | SysMan Command |
bindsetup |
Domain Name Service (DNS(BIND)) | sysman dns |
netsetup |
Network Setup Wizard | sysman net_wizard |
nfssetup |
Network File System (NFS) | sysman nfs |
ntpsetup |
Network Time Protocol (NTP) | sysman ntp |
Do not use these scripts to configure systems in a TruCluster environment.
For more information, see the reference pages for the
retired scripts or the
Network Administration
guide.
8.30 Changed Protected Password Database Format
The enhanced security user authentication profiles, originally stored in the
protected password files
/tcb/files/auth/<a..z>/<username>,
are now stored by default in a database format.
The
convauth
program, run for an update
installation, will convert existing files into the new format.
Support for
the original format will be removed in a future release of
Tru64 UNIX.
8.31 Audit_setup Script
The
/usr/sbin/audit_setup
script, used to configure auditing
support, will be retired in a future release of the operating
system.
It will be replaced by the
audit_config, which
is a SysMan application that provides a full graphical user interface.
8.32 VM Subsystem ubc_nfsloopback Variable Is Obsolete
The
/etc/sysconfigtab
ubc_nfsloopback
Virtual Memory (VM) subsystem kernel configuration variable is unnecessary, and
has been removed.
This configuration variable was needed in some TruCluster configurations with
previous versions of Tru64 UNIX to avoid a recursion deadlock with NFS
loopback-mounted file systems.
In those configurations, setting the
ubc_nfsloopback
VM subsystem variable to 1 prevented the deadlock.
The file system code in Tru64 UNIX Version 4.0G has been modified to
prevent the deadlock, which removes the need for the
ubc-nfsloopback
variable.
If the variable is not removed from
/etc/sysconfigtab,
it will not cause a problem.
However, after the kernel is loaded by the
firmware, the console generates the following message to indicate that the
variable is still present in
/etc/sysconfigtab:
sysconfigtab: attribute ubc_nfsloopback not in subsystem VM
The archive form of the enhanced security library
(libsecurity.a)
has been retired.
If you want to link against
libsecurity
use the shareable form,
libsecurity.so.
8.34 XPG3 ctab Locales
The XPG3 ctab
locales in the obsolete
OSFCTABLOC
subset will be retired
in a future release.
These locales were superseded by the XPG4 locales distributed
in
OSFEURLOC
and various subsets in the Worldwide Language
Support software on the Associated Products CD-ROM (APCD).
8.35 Security Interfaces
Table 8-3
provides a list of interfaces that have
been retired from the
libsecurity
library.
Other, undocumented
interfaces, have been retired as well.
These interfaces are not capable of
supporting new functionality offered in Tru64 UNIX 5.0.
Table 8-3: Retired libsecurity Interfaces
|
|
|
getprtcent() |
getprtcnam() |
putprtcnam() |
getprdfent() |
getprdfnam() |
putprdfnam() |
getprfient() |
getprfinam() |
putprfinam() |
getprlpent() |
getprlpnam() |
putprlpnam() |
getdvagent() |
getdvagnam() |
putdvagnam() |
getprpwent() |
getprpwnam() |
getprpwuid() |
putprpwnam() |
|
|
time_lock |
get_seed |
auth_for_terminal |
locked_out |
copydvent |
|
read_pw_fields |
store_pw_fields |
|
read_tc_fields |
store_tc_fields |
|
The associated data structures listed in
Table 8-4
have been retired as well.
Table 8-4: Retired libsecurity Interfaces Associated Data Structures
|
|
struct pr_field |
struct pr_flag |
struct t_field |
struct t_flag |
struct l_field |
struct l_flag |
struct dev_field |
struct dev_flag |
struct pr_passwd |
struct pr_term |
struct pr_file |
struct pr_lp |
struct pr_default |
struct dev_asg |
struct system_default_fields |
struct system_default_flags |
8.36 The ogated Routing Daemon
The
ogated
daemon (the old version of the
gated
routing daemon) will be retired in a future release of
Tru64 UNIX.
If you use the
ogated
routing daemon, you should migrate to the
gated
routing daemon, which supports a superset of functionality in the
ogated
daemon.
8.37 PEX Extensions
Starting with Open3D Version 4.8, support for the PEX extension to the X Server
has been retired.
The extension libraries still ship on the Open3D
product, but no support is available for them.
8.38 NL* and NL* libc Interfaces
A Worldwide Portability
Interface (WPI) for internationalization based on the XPG4 standard was introduced
in Version 2.0 of the operating system.
Because the WPI interfaces supersede
the
libc
OSF/1 proprietary interfaces, all
libc
interfaces that begin with the letters
NL
or
NC
will be removed in a future release of the operating system.
8.39 DEC Ada RTL
DEC Ada (UPI - 0HM) and DEC Ada PDO (UPI - 0VS) will be retired in a
future release of Tru64 UNIX.
8.40 System V Environment
Tru64 UNIX provides 80 percent of the System V Interface Definition (SVID) standard, as verified by the SVVS 3 and SVVS 4 test suites. As a result, Tru64 UNIX contains a substantial number of System V Release 4 (SVR4) features and delivers the highest composite SVR4 conformance of any implementation. SVR4 functionality will be further expanded in the base operating system when the System V Environment re-engineering is complete, eliminating the need for the layered product. A migration plan for upgrading to the appropriate version of the Tru64 UNIX base operating system has been developed to assist customers who currently use the System V Environment layered product. The System V Environment (SVE) product is not available as a separately licensed layered product with the Tru64 UNIX Version 5.0 family. Instead, many of its features are being re-engineered and will be merged into the Tru64 UNIX operating system in future releases.