HP-UX 11i September 2001 Release Notes

Compatibility
Known Compatibility Exceptions from HP-UX 11.0 to 11i
Chapter 12
181
Non-Executable Stack
This change improves system security. The majority of your programs should be
unaffected by execute protecting program stacks. Only those that execute instructions
from their stack (typically interpreters, simulators and debuggers) are affected.
When enabled, the new functionality causes the termination of any program attempting
to execute code located on its stack. If this occurs, you will be given an error message
pointing to relevant documentation that explains the reason for the process termination
and how to remedy the situation.
See “Execute Protected Stacks (new at 11i original release)” on page 171 for more
information.
128 CPU Support
This change enables support for 128 CPUs. The kernel macro "MAX_PROCS" has changed
from 32 to 128 in the LP64 kernel and changed the ABI for the undocumented system
calls ki_call() and ktest_ioctl().
The MAX_PROCS change will cause an ABI incompatibility for kernel intrusive
applications or drivers which access internal kernel arrays sized by the MAX_PROCS
macro.
strftime() Support for Week Number
This change fixes a defect in strftime(). Applications that use the %V option of
strftime() to obtain the week number will find that the return value is 52 instead of
53 when:
• December 31 falls on a Friday, in a non-leap year, when the date passed in is January
1 or January 2 of that week. Some years affected include 1999, 2004, and 2032.
• December 31 falls on a Saturday, when the date passed in is January 1 of that week.
Some years affected include 2005, 2011, 2016, 2022, 2033 and 2039.
Linker Support for PBO of 64-bit Shared Libraries
This change enables 64-bit PBO to function with shared libraries. Only those who link
-noshared instrumented applications and use HP_LD_FDP_INIT to specify an
alternative version of fdp_init.o will be affected. If this is the case, you will 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.
DNS Bind
This change is necessary to conform to the behavior found on other vendor platforms.
Those who have tried to edit named.boot could find the file missing, or if the file exists,
they could edit the file and then not have their changes take effect. This is primarily a
system administration change, but in the rareinstance where scripts might be written to
edit named.boot, the scripts would need to be modified to edit named.conf, both for the
new file name and syntax.