HP-UX 11i June 2004 Release Notes

Compatibility
Known Compatibility Exceptions from HP-UX 11.0 to 11i
Chapter 14
288
have to use HP_LD_FDP_INIT_NS instead. If the HP_LD_FDP_INIT_NS environment
variable is not set and fdp_init_ns.o is in the default location, the link will fail
with the file not found error message.
• ONC+/NFS Security Correction
This change corrects a security problem in NIS+. However, applications that are
linked to the archived version of the libnsl library may have a compatibility
problem. (Applications linked to the shared version of libnsl will not exhibit these
symptoms.) The symptoms include:
— Daemon registration will fail when UDP/TCP is used instead of the local
loopback transport device.
— In the NIS+ environment, applications will not be able to authenticate
themselves.
— NIS+ performance degradation will occur due to not being able to contact the
nis_cachemgr.
Miscellaneous
• DNS Bind
This change is necessary to conform to the behavior found on other vendor platforms.
Those who try to edit the file, named.boot, could find it missing, or if the file exists,
they may try to edit the file, but will find that their changes have not taken effect.
This is primarily a system administration change, but in the rare instance where
scripts might be written to edit named.boot, the scripts would need to be modified to
edit named.conf instead, both for the new file name and syntax.
• ELF Undocumented Symbol Table Change
To make some tool development easier, the ELF symbol table type of some thirteen
linker-defined symbols has changed from STT_OBJECT to STT_NOTYPE. Although the
names of these symbols have been documented, their types and meaning have not.
However, only applications that are not well-behaved and read 64-bit ELF executable
files are affected.
• Fortran 90 GETARG Intrinsic Function
This change causes the semantics of the index argument to the HP-supplied F90
intrinsic routine, GETARG, to be compatible with older HP F77 and other vendor
implementations of this routine. Those affected will have to change and recompile
their source code to use the industry-standard indexing scheme.
• IOSCAN Usability Enhancement
This change improves the usefulness of the IOSCAN output for PCI interfaces.
However, because the description field for PCI interface cards has been changed to
be more descriptive, scripts that scan for hard-coded values may need modifications.
(The description field for non-PCI devices has remained the same.) See “Improved
ioscan Description Field for PCI Devices” on page 212 for more information.