HP-UX 11i Version 1.5 Release Notes, May 2001
Table Of Contents
- 1 Overview of the Release Notes
- 2 Workstation/Server Specific Information
- 3 HP-UX Features
- 4 File and Disk Management
- 5 Networking
- 6 Commands and System Calls
- 7 Programming
- aC++ Libraries
- Changes to libc
- libcres.a Library
- New libdcekt.sl and libdcecpkt.sl Libraries
- New Linux Compatible API Library
- New locale Libraries
- New Unwind Library
- X11 Libraries
- SNMP
- Machine Dependent Headers
- Threadsafe Documentation
- Obsolescence and Deprecation of APIs
- Linker Toolset
- gprof Multiple Shared Library Profiling
- CXperf Performance Monitoring Support
- HP Caliper
- WDB Debugger Tool
- ADB Debugger Tool
- Fortran
- Packaging for Specific Releases
- 8 Other Functionality
HP-UX Features
HP-UX Kernel Configuration Commands
Chapter 342
kernel is linked. This ID is used to uniquely associate distributed
kernel files on disk with a specific kernel image. KRS uses the
generated KIS to identify its initialization files associated with a
kernel at boot-up. DLKM uses the KIS to identify the location of the
symtab file at boot-up, and to initialize the module load path
associated with the running kernel.
New or Changed Kernel Configuration Command
Options or Features
config (1M) and mk_kernel (1M)
• No change to the command line.
• Configuration of BTL modules is supported.
• config (1M) generates the Kernel ID string (KIS) to associate all
kernel components to a specific main kernel file.
• config (1M) generates module registration information and
kernel-specific persistent information in KRS format.
• The kernel component set goes beyond the main kernel file and the
DLKM directory. The KRS file described above is generated.
• The DLKM directory is re-named /stand/dlkm.KIS (link to old
/stand/dlkm is maintained for backward compatibility)
kmadmin (1M)
• New option (-b) is added to set the Configured Loading Phase of a
registered module.
• Configured Loading Phase is now kept in KRS, and you can get/set it
using kmadmin to one of the following phases:
— BOOT1
— BOOT2
— INIT
— AUTO
The /etc/loadmods file is supported only for backward compatibility,
and can only be used to set Configured Loading Phase to INIT. Users
should migrate to kmadmin interface.