Skip to content

Instantly share code, notes, and snippets.

@alanc

alanc/SRU66-man-page-changes.diff

Created February 24, 2024 01:54
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save alanc/3746d12ed6ee52c37076138c473b202c to your computer and use it in GitHub Desktop.
Save alanc/3746d12ed6ee52c37076138c473b202c to your computer and use it in GitHub Desktop.
Download ZIP
Changes to core OS man pages in Oracle Solaris 11.4 SRU 66
Raw
Solaris-11.4-SRU66-man-page-changes.txt
18458892 ::print, ::if et al should understand casting
34498749 Warning in ipf2pf unit test output
34520457 reflink() preserve parameter should preserve more
35290909 Update libaudit to use libpcre2 instead of obsolete libpcre
35293835 nvlist_add_boolean() should be de-deprecated
35457686 remove ipf2pf from ON
35707792 cp -z overwrite rules differ from the rest of cp
35739061 kldd should support multiple sysroots, _depends_on[], and platform selection
35765436 resolv.conf does not provide an option to enable use-vc by default
35769087 kernel zone NPT configuration needs more information
35797790 Assorted fixes for Section 7 man pages
35799032 log driver does not create fractional time stamps
35813781 memlzr=strict does not work with zonecfg -r
35814102 Would like to be able to map types and names in mdb
35818408 Remove Wireless USB device drivers
35827363 /etc/default/syslogd should be removed
35872581 ::sort is ignoring -A/-a when the address is not part of a structure
35873839 ::sort should be able to be forced to sort signed values.
35875904 incorrect placement of ELF versioning sections in kernel modules
35878107 getfacl(1) man page wrong about ACL usage with chmod(1)
35879230 setrlimit man page should mention RLIMIT_CORE doesn't affect global core dumps
35892244 kldd SONAME mismatch check does not account for multiple interfaces
35895323 mdb_getopts needs to be able to accept options with "+"
35936585 ::if should support ADI addresses
35940199 mdb man page becomes right shifted in the ::typemap section
35965220 signal.h(3HEAD) doesn't list SIGAIOCANCEL
35971427 coreadm man page incorrectly identifies /usr/lib/inet/ntpd as a non-Oracle binary
36017559 ptree(1) should make it easier to determine the processes in a zone have a global zone parent
36078924 Cleanup man page changes from 35395419 & 35435540
PSARC 2023/098 Extend the log_ctl_t message: fractional seconds in log messages
PSARC 2023/123 ptree(1) option -g, list direct global zone parents for -z zone processes
PSARC/2023/063 EOF & Removal of IPFilter to PF conversion tool
PSARC/2023/093 kldd support for multiple sysroots, _depends_on[], and platform selection
PSARC/2023/096 Type and name mapping for mdb
PSARC/2023/101 Wireless USB removal
PSARC/2023/106 Support usevc/use-vc option in resolv.conf
PSARC/2023/107 De-deprecate nvlist boolean interface
PSARC/2023/109 Plus flags for mdb_getopts
Copyright (c) 1983, 2024, Oracle and/or its affiliates.
Raw
SRU66-man-page-changes.diff
diff -NurbBw 11.4.63/man1/cp.1 11.4.66/man1/cp.1
--- 11.4.63/man1/cp.1 2024-02-23 17:45:28.936885164 -0800
+++ 11.4.66/man1/cp.1 2024-02-23 17:51:32.913974558 -0800
@@ -129,8 +129,15 @@
-S Call fsync(2) on the target file's file descriptor.
- -z Fast Copy. cp will reflink the source and destination files. For
- more information, see the reflink(3C) man page.
+ -z Fast Copy. cp will reflink the source and destination files.
+
+ If this option is used, cp will not overwrite the destination
+ file. Additionally, -f and -i are ignored.
+
+ For more information, see the reflink(3C) man page.
+
+ When the -p option is used, the extended file attributes will be
+ copied normally, not using reflink.
-@ Preserves extended attributes. cp attempts to copy all of the
@@ -343,4 +350,4 @@
plicitly, thus allowing cp to recognize filename arguments that begin
with a -.
-Oracle Solaris 11.4 28 Mar 2023 cp(1)
+Oracle Solaris 11.4 24 Aug 2023 cp(1)
diff -NurbBw 11.4.63/man1/getfacl.1 11.4.66/man1/getfacl.1
--- 11.4.63/man1/getfacl.1 2024-02-23 17:45:28.964115922 -0800
+++ 11.4.66/man1/getfacl.1 2024-02-23 17:51:32.940317777 -0800
@@ -12,8 +12,8 @@
These commands are no longer included in Oracle Solaris 11.4 and later
releases. Instead of getfacl, you can use the -v or -V options to the
- ls(1) command to list an ACL. Instead of setfacl, you can use the -A
- option to the chmod(1) command to change an ACL.
+ ls(1) command to list an ACL. Instead of setfacl, you can use the A op-
+ eration to the chmod(1) command to change an ACL.
Unlike getfacl and setfacl, ls and chmod work with all supported ACL
@@ -36,4 +36,4 @@
Setting ACLs on ZFS Files in Securing Files and Verifying File In-
tegrity in Oracle Solaris 11.4
-Oracle Solaris 11.4 15 Nov 2018 getfacl(1)
+Oracle Solaris 11.4 06 Oct 2023 getfacl(1)
diff -NurbBw 11.4.63/man1/kldd.1 11.4.66/man1/kldd.1
--- 11.4.63/man1/kldd.1 2024-02-23 17:45:29.010780357 -0800
+++ 11.4.66/man1/kldd.1 2024-02-23 17:51:33.004298485 -0800
@@ -4,8 +4,8 @@
kldd - list dependencies of kernel modules
SYNOPSIS
- kldd [-bcmprsuUvVw] [-D CPU=cpuname] [-k file | -K] [-R path]
- [-S dir] file...
+ kldd [-bcmprsuUvVw] [-D CPU=cpuname] [-k file | -K] [-P platform,...]
+ [-R path] [-S path] file...
DESCRIPTION
The kldd utility lists the dependencies of kernel modules. kldd emu-
@@ -68,6 +68,18 @@
External Interfaces under USAGE.
+ -P platform,...
+
+ Specify platform directories to be used when searching for kernel
+ modules and the unix kernel. By default, kldd uses the platform of
+ the running system. The -P option can be used to replace this de-
+ fault with one or more platform directories, to be searched in the
+ order specified. Platforms are specified as a comma separated list
+ of platform names. For example: -Pi86pc,i86hvm might be used on an
+ x86 system to analyze certain kernel modules that require both
+ platforms. See Kernel Module Search Path under USAGE.
+
+
-r
Check references. See Interface Verification under USAGE.
@@ -85,19 +97,19 @@
Displays the search path used to locate kernel module dependencies.
- -S dir
+ -S path
- Specify the system root to be applied to the default module search
- path, and to the unix kernel. kldd searches for kernel modules, and
- the unix kernel, in standard locations. By default, this default
- module path is interpreted relative to the system root directory /.
- The -S option can is used to specify an alternative system root, or
- to entirely disable the use of the default module path. If dir is
- set to a non-empty string, the default search path is interpreted
- relative to that directory. If dir is set to an empty string, '',
- then the default search path is not used. In this later case, the
- -R option must be used to supply a path for kldd to use. See Kernel
- Module Search Path under USAGE.
+ Specify system root (sysroot) directories to be used when searching
+ for kernel modules and the unix kernel. By default, kldd uses the
+ system root directory / for this purpose. The -S option can be used
+ to replace this default with one or more sysroot directories to be
+ searched in the given order, or to entirely disable sysroot search-
+ ing. Set path to a colon separated list of sysroot directories, to
+ be searched in the order specified. Alternatively, set path to an
+ empty string, '', to entirely disable sysroot searching. In this
+ later case, the -R and -k options must be used to supply search
+ paths and a kernel for kldd to use. See Kernel Module Search Path
+ under USAGE.
-u
@@ -227,19 +239,66 @@
to be flagged as a relocation error.
Kernel Module Search Path
+ To locate kernel modules, kldd constructs a list of directories to
+ search. Searching consists of checking each directory in this list in
+ turn, stopping at the first one that provides the desired module. This
+ mimics the behavior of the kernel runtime linker, and is designed to
+ yield the same results. kldd displays this search list as part of the
+ information produced when the -s option is specified.
+
+
+ Directories specified with the -R option are placed at the head of the
+ list, in the order specified on the command line. Following that, kldd
+ adds default system defined locations, based on the module search path
+ constructed by the kernel at boot time. This module search path can
+ differ in minor details between system. On a typical sparc system, it
+ appears as follows.
+
+ $ kldd -s genunix | egrep 'search|unix =>'
+ search path=/platform/sun4v/kernel:/kernel:/usr/kernel (default)
+ unix => /platform/sun4v/kernel/sparcv9/unix
+
+
+
+ /kernel and /usr/kernel are always present. In addition, there is al-
+ ways at least one /platform directory, providing support for the spe-
+ cific system hardware, and one of these platform directories provides
+ the unix kernel. There may be additional platform directories, depend-
+ ing on the needs of the specific system. By default, kldd adds the di-
+ rectories from the kernel module search path without modification. The
+ -P and -S options are available to alter this default, allowing kldd to
+ analyze objects not intended for the running system.
+
+
+ The -P option causes kldd to replace any /platform directories supplied
+ by the kernel module list with the platform directories specified by
+ -P. This allows for the analysis of objects intended for use on a dif-
+ ferent platform than the running system. See EXAMPLES.
+
+
+ The -S option is used to specify that the default directories should be
+ interpreted relative to a set of user supplied system root directories,
+ rather than against /, the root of the currently running system. This
+ is useful when testing a complete set of new modules together, indepen-
+ dent of the running system. This can be used to analyze kernel modules
+ from a different platform than the currently running system. For each
+ specified sysroot, in the order given, all the default directories are
+ added to the search list, prepended with the specified sysroot. Alter-
+ natively, the -S option can specify an empty string, '', for the system
+ root. In this case, the effect is to entirely disable the use of the
+ default search path. In this mode, the -R option must be used to spec-
+ ify directories for kldd to search, and the -k option may be necessary
+ to specify a unix kernel to analyze. See EXAMPLES.
+
+
Kernel modules specify dependencies on other kernel modules using a
simple string referred to as an soname. An soname can have one of 2
forms. The first form gives a plain module name, such as genunix. The
- second, more common form uses a slash delimiter to specify a module
+ second, more common, form uses a slash delimiter to specify a module
class as well as a module name, such as sys/doorfs). The soname is not
- a file path, and cannot be used directly to locate the kernel module
- they refer to. Instead, the kernel runtime loader, krtld uses a search
- path to look for the module that matches the soname. The search path
- used is constructed by the kernel at boot time, and can differ in minor
- details between systems. kldd obtains this default module path from the
- kernel, and uses it to mimic the behavior of krtld. kldd will display
- this path as part of the information produced when the -s option is
- specified.
+ a file path, and cannot be used directly to locate a referenced kernel
+ module. Instead, the search list is used to look for a module matching
+ the soname.
Before searching, the kernel rewrites the given soname to insert the
@@ -252,21 +311,13 @@
/usr/kernel/sys/sparcv9/doorfs.
- The -S option alters, or deletes, the default module path. By default,
- the default search path is interpreted relative to the system root di-
- rectory, /. The -S option can be used to alter the location used for
- the system root. This is useful when testing a complete set of new mod-
- ules together, independent of the running system. It can also be used
- to access modules from a different system. This can be used to analyze
- kernel modules from a different platform than the currently running
- system.
-
-
- The -S option can also specify an empty string, '', for the system
- root. In this case, the effect is to discard the default search path
- entirely. In this mode, the -R option must be used to specify the path
- for kldd to use. This mode of operation provides full control over the
- path used.
+ The unix kernel, and its dependencies such as genunix, are implicit de-
+ pendencies of all other kernel modules, and are not listed as dependen-
+ cies by those modules. kldd supplies them implicitly, as needed. If the
+ -k option is used, kldd uses the kernel specified. Failing that, if the
+ -P option is used, kldd looks under each specified platform directory
+ in turn, until a unix kernel is found. If neither -k, nor -P, are spec-
+ ified, the path of the kernel from the running system is used.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -314,6 +365,23 @@
analysis. The -D option can be used to specify a different translation
for $CPU in cases where the generic version is insufficient.
+
+ The kldd command is provided in non-global zones in order to support
+ the analysis of user built kernel objects. However, note that the di-
+ rectories searched for kernel modules and the unix kernel, are not
+ present in a non-global zone. To use kldd in a non-global zone, it is
+ necessary to use the -S option to provide a system root directory con-
+ taining those files.
+
+
+ The kernel runtime linker, krtld, supports an obsolete, deprecated
+ mechanism for defining kernel module dependencies in which the kernel
+ module defined a local string array named _depends_on[] to provide the
+ dependencies. This mechanism, which is only supported for older kernel
+ modules not linked with the ld -ztype=kmod option, is not recommended.
+ However, kldd supports _depends_on[], for older modules only, to allow
+ for the analysis of existing objects.
+
EXAMPLES
Example 1 Displaying module dependencies by file path
@@ -396,6 +464,7 @@
misc/tlimod => /kernel/misc/amd64/tlimod
find kernel=unix; implicit
+ trying path=/platform/i86pc/kernel/amd64/unix
unix => /platform/i86pc/kernel/amd64/unix
find module=genunix; required by /platform/i86pc/kernel/amd64/unix
@@ -452,10 +521,50 @@
/platform/sun4v/kernel/cpu/sparcv9/SPARC-T5
+ Example 7 Specifying a non-default platform
+
+
+
+ On an x86 system, analyzing kernel objects found under /platform/i86hvm
+ requires both the i86pc and i86hvm platforms. The drv/balloon kernel
+ module is an example of such a case.
+
+
+ $ kldd drv/balloon
+ drv/balloon: open: No such file or directory
+
+ $ kldd -Pi86pc,i86hvm drv/balloon
+ drv/xpv => /platform/i86hvm/kernel/drv/amd64/xpv
+ unix (parent) => /platform/i86pc/kernel/amd64/unix
+ genunix (parent dependency) => /kernel/amd64/genunix
+
+
+ Example 8 Using the system root as a backstop
+
+
+
+ A common use of kldd is to analyze kernel objects built and delivered
+ into a local proto directory. Such proto directories may not be com-
+ plete system images, and instead rely in objects found in the system
+ root directory /. The -S option is typically used to point kldd at the
+ local proto. In order to use the system as a backstop for objects not
+ present locally, the system root should be included as well. The fol-
+ lowing illustrates such use, for a module misc/lproduct, residing in a
+ proto area /local/lproduct/proto.
+
+
+ $ kldd -S/local/lproduct/proto:/ misc/lproduct
+
+
HISTORY
+ The -S option was extended to accept a path rather than a single system
+ root, the -P option was added, and support for the deprecated _de-
+ pends_on[] mechanism was added, in Oracle Solaris 11.4.64.
+
+
The -D option was added in Oracle Solaris 11.4.36.
The kldd command was introduced in the Oracle Solaris 11.4.0 release.
-Oracle Solaris 11.4 29 Nov 2022 kldd(1)
+Oracle Solaris 11.4 27 October 2023 kldd(1)
diff -NurbBw 11.4.63/man1/mdb.1 11.4.66/man1/mdb.1
--- 11.4.63/man1/mdb.1 2024-02-23 17:45:29.135083235 -0800
+++ 11.4.66/man1/mdb.1 2024-02-23 17:51:33.127501884 -0800
@@ -1306,6 +1306,24 @@
built-in dcmd can be used to display the value of the symbol for
threads other than the representative thread.
+ Casting
+ When referencing structure members it is possible to cast the member to
+ be a different type. Unlike C casting, the cast comes after the member
+ being cast. So a structure:
+
+ struct bike {
+ char b_name[16];
+ void *b_data;
+ };
+
+
+
+ If b_data points to a structure of type "struct pearson" with member
+ p_custom the following can be used to directly access p_custom:
+
+ struct bike b_data(struct pearson *)->p_custom
+
+
Built-in dcmds
mdb provides a set of built-in dcmds that are always defined. Some of
these dcmds are only applicable to certain targets: if a dcmd is not
@@ -2424,12 +2442,20 @@
signals can be obtained using the ::events dcmd.
- [ address ] ::if [-p] {type member tests | [type] [at off] test}
+ [ address ] ::if [+a|-a][-p] {type member tests | [type] [at off] test}
Evaluate the tests and then print the old value of dot if the tests
are true.
+ +a | -a
+
+ By default, if examines the arguments to determine whether or
+ not to apply ADI normalization. If the member is a pointer the
+ default is to ADI-normalize it, otherwise the default is to not
+ ADI-normalize it. Set -a to require normalization, or +a to
+ disable it. If the platform does not support ADI this has no
+ effect.
-p
@@ -2501,70 +2526,117 @@
...will print the old value of dot if the string pointed to at off-
set 0x34 is foo.
+
+
+
Possible tests are:
+ = The values are equal
- & - The values ANDed together are non zero.
- % - The left value modulus the right is non zero.
- ^ - The values XORed together are non zero.
- streq - The strings exactly match.
- strneq - The strings don't match.
- strcaseeq - The strings match case insensitively.
- strcaseneq - The strings do not match case insensitively.
- strstr - The string contains the string.
- strcasestr - The string contains the case insensitive string.
- strnstr - The string does not contain the string.
- strcasenstr - The string does not contain the case insensitive string.
- strleneq - The string is this length.
- strlenne - The string is not this length.
- strlengt - The string is longer than this.
- strlenlt - The string is shorter than this.
- strlenge - The string is this long or longer.
- strlenle - The string is this long or shorter.
+ <> The values are not equal
- streq accepts the following options:
+ < The value is less than the right hand value
+ <= The value is less than or equal to the right
+ hand value
+ > The value is greater than the right hand value
- -i Test ignoring the case.
+ >= The value is greater than or equal the right
+ hand value
+ & The values ANDed together are non zero.
- -n Return true if there is no match.
+ % The left value modulus the right is non zero.
+ ^ The values XORed together are non zero.
- -o oStart search at offset into string.
+ regex Does the string match the regular expression.
+ streq The strings exactly match.
- -s Search for a substring.
+ strneq The strings do not match.
+ strcaseeq The strings match case insensitively.
- strstr accepts the following options:
+ strcaseneq The strings do not match case insensitively.
+ strstr The string contains the string.
+ strcasestr The string contains the case insensitive string.
- -i Test ignoring the case.
+ strnstr The string does not contain the string.
+ strcasenstr The string does not contain the case insensitive
+ string.
- -n Return true if there is no match.
+ strleneq The string is this length.
+ strlenne The string is not this length.
- -v variable Store the address of the found string in variable.
+ strlengt The string is longer than this.
+
+ strlenlt The string is shorter than this.
+
+ strlenge The string is this long or longer.
+
+ strlenle The string is this long or shorter.
+
+
+
+
+ =, <, <=, >, >=, &, % and ^ accept the following option:
+
+
+ +a | -a By default, if examines the arguments to determine
+ whether or not to apply ADI normalization. If the
+ member is a pointer the default is to ADI-normalize
+ it, otherwise the default is to not ADI-normalize
+ it. Set -a to require normalization, or +a to dis-
+ able it. If the platform does not support ADI this
+ has no effect.
- regex accepts the following options:
+ streq and strneq accept the following options:
+
-i Test ignoring the case.
+ -n Return true if there is no match.
+
+ -o offset Start search at offset into string.
+
+ -s Search for a substring.
+
+
+
+
+ strstr and strnstr accept the following options:
+
+
+ -i Test ignoring the case.
-n Return true if there is no match.
+ -v variable Store the address of the found string in vari-
+ able.
- -v variable Store the address of the found string in variable.
+
+ regex accepts the following options:
+
+
+ -i Test ignoring the case.
+
+ -n Return true if there is no match.
+
+ -v variable Store the address of the found string in vari-
+ able.
+
-x Insist on an exact match.
@@ -2579,11 +2651,16 @@
-o offset Start search at offset into string.
+
+
strstr and strcasestr accept these options:
+ -v variable Store the address of the found string in vari-
+ able.
+
+
- -v variable Store the address of the found string in variable.
The right hand side of a test can be any one of the following:
@@ -3397,8 +3473,8 @@
- ... | ::sort [-u [-c] [-v var]] [type] [-s [-i]] [-r]
- [at] offset|member [[-s [-i]] [-r] [-u] member]... [|::dcmd ...]
+ ... | ::sort [-u [-c] [-v var]] [type] [+a|-a][+S|-S][-s [-i]] [-r]
+ [at] offset|member [[+a|-a][+S|-S][-s [-i]] [-r] [-u] member]... [|::dcmd ...]
Sort the addresses based on the rules given. With no arguments
@@ -3439,24 +3515,39 @@
SORT KEY OPTIONS
+ -a | +a By default, sort examines the arguments to determine
+ whether or not to apply ADI normalization. If the member
+ is a pointer the default is to ADI-normalize it, other-
+ wise the default is to not ADI-normalize it. Set -a to
+ require normalization, or +a to disable it. If the plat-
+ form does not support ADI this has no effect.
+
+
+ -i If sorting strings ignore case.
+
+
+ -l len If sorting pointers dereference the pointer and compare
+ len bytes.
+
+
-r Reverse the order of this test.
-s Treat this item as a string.
- -i If sorting strings ignore case.
+ -S | +S By default, sort examines the arguments to determine
+ whether to sort values as signed or unsigned. If the
+ member being sorted is signed then the sort will be
+ signed otherwise it will be unsigned. Set -S to force
+ signed sorting, or +S for unsigned sorting.
- -u Uniq for this key. Sort using the remaining keys but only
- output the last entry that matches on this key. See
+ -u Uniq for this key. Sort using the remaining keys but
+ only output the last entry that matches on this key. See
::help sort for examples.
- -l len If sorting pointers dereference the pointer and compare
- len bytes.
-
-
[ address ] ::stack [-A][-r][-T][-v][-x] [ count ]
@@ -3738,6 +3829,56 @@
the caches are flushed.
+ [addr]::typemap [-a|-c|-d|-r][-n][ -i id ][ -t type ][ -m type ][ -c
+ expression ][mapped type]
+
+ Type map is used to manage and display type and name mappings. When
+ type mapping is enabled mdb will map types according to the map-
+ pings defined within mdb modules.
+
+ ::typemap takes the following options:
+
+
+
+ -a add a type mapping
+
+
+ -c Expression to test if mapping is to be used
+
+
+ -d disable a mapping
+
+
+ -e enable a mapping
+
+
+ -f force flag (for remove)
+
+
+ -i id of mapping to be printed/disabled/enabled/removed
+
+
+ -m object member for mapping
+
+
+ -n Operate on the name mappings
+
+
+ -r remove a mapping
+
+
+ -t type of object for mapping
+
+
+ -V verbose mode for printing
+
+
+ When no add, remove, enable or disable options are given ::typemap
+ displays the current mappings.
+
+ See ::help typemap for example usage.
+
+
::typeset [ +/-t] variable-name ...
Set attributes for named variables. If one or more variable names
@@ -4311,6 +4452,11 @@
The debugger will not use the type cache.
+ notypemap
+
+ The debugger will not do type or name mapping.
+
+
typecheck=action
Control whether mdb will check the types of addresses passed to
@@ -4845,4 +4991,4 @@
provides source code for an example module in the directory
/usr/demo/mdb.
-Oracle Solaris 11.4 10 Mar 2023 mdb(1)
+Oracle Solaris 11.4 30 November 2023 mdb(1)
diff -NurbBw 11.4.63/man1/ptree.1 11.4.66/man1/ptree.1
--- 11.4.63/man1/ptree.1 2024-02-23 17:45:29.164878935 -0800
+++ 11.4.66/man1/ptree.1 2024-02-23 17:51:33.157519830 -0800
@@ -29,6 +29,13 @@
zone ID.
This option is only useful when executed in the global zone.
+ See also the -g option.
+
+
+ -g Global. In conjuction with -z zone, the output is extended
+ to list the global zone direct parents of processes in the
+ zone. Processes from the global zone are marked with an as-
+ terisk.
-? Print usage message and immediately exit.
@@ -48,7 +55,7 @@
EXAMPLES
- Example 1 Using ptree
+ Example 1 Using ptree on a specific process
@@ -67,6 +74,30 @@
569193 bash
+ Example 2 Using ptree listing processes inside a zone and direct parent
+ processes
+
+
+
+ The following command prints the process in the zone ngz and the
+ process in the global zone which are the parents of the process in the
+ zone:
+
+
+ $ ptree -g -z ngz
+ 762 zsched
+ 820 /usr/sbin/init
+ 829 /lib/svc/bin/svc.startd
+ 1579 /usr/sbin/ttymon -g -d /dev/console -l console -m ldterm,ttcompat -h -p
+ 831 /lib/svc/bin/svc.configd
+ ....
+ 1629* zlogin ngz
+ 1630 <defunct>
+ 4546* zlogin ngz
+ 4547 /usr/bin/login -z global -f root
+ 4548 -bash
+
+
EXIT STATUS
The following exit values are returned:
diff -NurbBw 11.4.63/man2/getrlimit.2 11.4.66/man2/getrlimit.2
--- 11.4.63/man2/getrlimit.2 2024-02-23 17:45:29.210074623 -0800
+++ 11.4.66/man2/getrlimit.2 2024-02-23 17:51:33.197910291 -0800
@@ -53,7 +53,9 @@
RLIMIT_CORE The maximum size of a core file in bytes that may be
created by a process. A limit of 0 will prevent the
creation of a core file. The writing of a core file
- will terminate at this size.
+ will terminate at this size. Setting this resource
+ does not affect system-wide global cores, see core-
+ adm(8).
RLIMIT_CPU The maximum amount of CPU time in seconds used by a
@@ -239,7 +241,7 @@
ulimit(1), brk(2), exec(2), fork(2), open(2), setrctl(2), sigalt-
stack(2), getdtablesize(3C), malloc(3C), signal(3C), sysconf(3C), sig-
nal.h(3HEAD), attributes(7), lf64(7), privileges(7), resource-con-
- trols(7), standards(7), rctladm(8)
+ trols(7), standards(7), coreadm(8), rctladm(8)
Oracle Solaris 11.4 Tunable Parameters Reference Manual
@@ -262,4 +264,4 @@
+--------------------------------------------------+---------+
-Oracle Solaris 11.4 30 Jan 2023 getrlimit(2)
+Oracle Solaris 11.4 30 Oct 2023 getrlimit(2)
diff -NurbBw 11.4.63/man3c/reflink.3c 11.4.66/man3c/reflink.3c
--- 11.4.63/man3c/reflink.3c 2024-02-23 17:45:29.246962307 -0800
+++ 11.4.66/man3c/reflink.3c 2024-02-23 17:51:33.228241615 -0800
@@ -27,12 +27,17 @@
the directory that contain the new entry are marked for update.
- If the reflinkat() function is passed, the special value AT_FDCWD in
- the fd1 or fd2 parameter uses the current working directory for the re-
+ If the reflinkat() function is passed the special value AT_FDCWD in the
+ fd1 or fd2 parameter, it uses the current working directory for the re-
spective path argument. If the AT_SYMLINK_FOLLOW flag is set in the
- flag argument and the path1 argument names a symbolic link, the sym-
+ flags argument and the path1 argument names a symbolic link, the sym-
bolic link path1 is dereferenced to provide the source of the reflink.
+
+ If the preserve parameter is non-zero, as much of the uid, gid, mode,
+ atime, mtime, and system attributes are copied as are allowed by the
+ calling process's privileges. See privileges(7) for more information.
+
RETURN VALUES
Upon successful completion, 0 is returned. Otherwise, -1 is returned,
no link is created, and errno is set to indicate the error.
@@ -70,8 +75,7 @@
flink() function.
- EINVAL The value of the preserve or flag argument is not
- valid.
+ EINVAL The value of the flags argument is not valid.
ELOOP Too many symbolic links were encountered in translating
@@ -132,4 +136,4 @@
SEE ALSO
attributes(7), privileges(7), standards(7)
-Oracle Solaris 11.4 15 Mar 2017 reflink(3C)
+Oracle Solaris 11.4 24 Aug 2023 reflink(3C)
diff -NurbBw 11.4.63/man3c/ucred_get.3c 11.4.66/man3c/ucred_get.3c
--- 11.4.63/man3c/ucred_get.3c 2024-02-23 17:45:29.276883416 -0800
+++ 11.4.66/man3c/ucred_get.3c 2024-02-23 17:51:33.266597514 -0800
@@ -44,6 +44,9 @@
pid_t ucred_getpid(const ucred_t *uc);
+ const char *ucred_getprinc(const ucred_t *uc);
+
+
projid_t ucred_getprojid(const ucred_t *uc);
@@ -96,10 +99,11 @@
ter the original program exited.
- The ucred_getprinc() returns user's kerberos principal associated with
- credential. The returned ASCIZZ remains valid until ucred_free() is
- called on the user credential given as argument. Function returns NULL
- if there is no kerberos principal associated with credential.
+ The ucred_getprinc() function returns a null-terminated string contain-
+ ing the kerberos principal associated with the credential. The returned
+ pointer remains valid until ucred_free() is called on the user creden-
+ tial given as argument. The function returns NULL if there is no ker-
+ beros principal associated with the credential.
The ucred_getprojid() function returns the project ID of the process or
@@ -177,19 +181,14 @@
The ucred_geteuid(), ucred_getruid(), ucred_getsuid(), ucred_getegid(),
- ucred_getrgid(), ucred_getsgid(), ucred_getgroups(), ucred_getpflags(),
- ucred_getprivset(), ucred_getprojid(), ucred_getpid(), and ucred_getla-
- bel() functions will fail if:
+ ucred_getrgid(), ucred_getsgid(), ucred_getgroups(), ucred_getlabel(),
+ ucred_getpflags(), ucred_getpid(), ucred_getprinc(), ucred_get-
+ privset(), and ucred_getprojid() functions will fail if:
EINVAL The requested user credential attribute is not available in
the specified user credential.
-
- The ucred_getprinc() returns NULL if there is no kerberos principal as-
- sociated with credential. Otherwise it returns pointer to ASCIIZ with
- kerbeos principal.
-
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -206,4 +205,26 @@
getpflags(2), getppriv(2), door_ucred(3C), getpeerucred(3C),
priv_set(3C), socket.h(3HEAD), attributes(7), labels(7), privileges(7)
-Oracle Solaris 11.4 16 May 2023 ucred_get(3C)
+HISTORY
+ Support for the following functions is available in Oracle Solaris
+ starting with the listed release:
+
+ +--------------------------------------------+---------------------+
+ | FUNCTION | RELEASE |
+ +--------------------------------------------+---------------------+
+ | ucred_getprinc() | 11.4.63 |
+ +--------------------------------------------+---------------------+
+ | ucred_getlabel() | 10 11/06 (Update 3) |
+ +--------------------------------------------+---------------------+
+ | ucred_get(), ucred_free(), ucred_size(), | 10 3/05 |
+ | ucred_getegid(), ucred_geteuid(), | |
+ | ucred_getgroups(), ucred_getlabel(), | |
+ | ucred_getpflags(), ucred_getpid(), | |
+ | ucred_getprivset(), ucred_getprojid(), | |
+ | ucred_getrgid(), ucred_getruid(), | |
+ | ucred_getsgid(), ucred_getsuid(), | |
+ | ucred_getzoneid() | |
+ +--------------------------------------------+---------------------+
+
+
+Oracle Solaris 11.4 4 Dec 2023 ucred_get(3C)
diff -NurbBw 11.4.63/man3head/signal.h.3head 11.4.66/man3head/signal.h.3head
--- 11.4.63/man3head/signal.h.3head 2024-02-23 17:45:29.316966834 -0800
+++ 11.4.66/man3head/signal.h.3head 2024-02-23 17:51:33.313321330 -0800
@@ -140,7 +140,7 @@
SIGXFSZ 31 Core File size limit exceeded (see getr-
limit(2))
SIGWAITING 32 Ignore Reserved
- SIGLWP 33 Ignore Reserved
+ SIGAIOCANCEL 33 Ignore Reserved
SIGFREEZE 34 Ignore Check point Freeze
SIGTHAW 35 Ignore Check point Thaw
SIGCANCEL 36 Ignore Reserved for threading support
@@ -409,4 +409,4 @@
Signals which are generated synchronously should not be masked. If such
a signal is blocked and delivered, the receiving process is killed.
-Oracle Solaris 11.4 11 May 2021 signal.h(3HEAD)
+Oracle Solaris 11.4 1 Nov 2023 signal.h(3HEAD)
diff -NurbBw 11.4.63/man3nvpair/nvlist_add_boolean.3nvpair 11.4.66/man3nvpair/nvlist_add_boolean.3nvpair
--- 11.4.63/man3nvpair/nvlist_add_boolean.3nvpair 2024-02-23 17:45:29.347211477 -0800
+++ 11.4.66/man3nvpair/nvlist_add_boolean.3nvpair 2024-02-23 17:51:33.343637367 -0800
@@ -192,10 +192,6 @@
(void) nvlist_free(parent_nvl);
-
- The nvlist_add_boolean() function is deprecated. Instead, use the
- nvlist_add_boolean_value() function.
-
RETURN VALUES
These functions return 0 on success and an error value on failure.
@@ -223,4 +219,4 @@
SEE ALSO
libnvpair(3LIB), nvlist_alloc(3NVPAIR), attributes(7)
-Oracle Solaris 11.4 23 Sept 2016 nvlis...olean(3NVPAIR)
+Oracle Solaris 11.4 2 Oct 2023 nvlis...olean(3NVPAIR)
diff -NurbBw 11.4.63/man4d/hwahc.4d 11.4.66/man4d/hwahc.4d
--- 11.4.63/man4d/hwahc.4d 2024-02-23 17:45:29.375190162 -0800
+++ 11.4.66/man4d/hwahc.4d 1969-12-31 16:00:00.000000000 -0800
@@ -1,70 +0,0 @@
-hwahc(4D) Device Drivers & /dev files hwahc(4D)
-
-NAME
- hwahc - Host Wire Adapter Host Controller Driver
-
-DESCRIPTION
- The hwahc driver is a USBA (Solaris USB Architecture) compliant nexus
- driver that supports the Wireless USB 1.0 Host Wire Adapter Host Con-
- troller, an industry standard developed by USB-IF.
-
-
- A Host Wire Adapter (HWA) is a USB device whose upstream connection is
- a USB 2.0 wired interface. The HWA operates as a host to a cluster of
- downstream Wireless USB devices.
-
-
- The hwahc driver supports bulk, interrupt and control transfers.
-
-FILES
- /kernel/drv/sparcv9/hwahc 64-bit SPARC ELF kernel module
-
-
- /kernel/drv/amd64/hwahc 64-bit x86 ELF kernel module
-
-
-ATTRIBUTES
- See attributes(7) for a description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Architecture |SPARC, x86 |
- +------------------------------+-----------------------------+
- | Availability |system/io/usb |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- ehci(4D), hubd(4D), usba(4D), attributes(7), add_drv(8), prtconf(8),
- rem_drv(8), update_drv(8)
-
-
- Writing Device Drivers in Oracle Solaris 11.4
-
-
- Universal Serial Bus Specification 2.0
-
-
- Wireless Universal Serial Bus Specification 1.0
-
-
- https://www.usb.org/
-
-DIAGNOSTICS
- All host controller errors are passed to the client drivers. In addi-
- tion to being logged, the following messages can appear on the system
- console. All messages are formatted in the following way:
-
-
-
- WARNING: device_path hwahc instance_number: Message ...
-
- Connection device on WUSB port port_number fails
-
-
-
- The connecting device fails to connect to the HWA. Make sure the device
- has been associated with the host.
-
-Oracle Solaris 11.4 5 Jan 2012 hwahc(4D)
diff -NurbBw 11.4.63/man4d/hwarc.4d 11.4.66/man4d/hwarc.4d
--- 11.4.63/man4d/hwarc.4d 2024-02-23 17:45:29.404463445 -0800
+++ 11.4.66/man4d/hwarc.4d 1969-12-31 16:00:00.000000000 -0800
@@ -1,55 +0,0 @@
-hwarc(4D) Device Drivers & /dev files hwarc(4D)
-
-NAME
- hwarc - HWA Radio Controller Driver
-
-SYNOPSIS
- hwa-radio@unit-address
-
-DESCRIPTION
- The hwarc driver is a USBA (Solaris USB Architecture) compliant client
- driver that supports Host Wire Adapter Radio Controller, specified in
- Wireless Universal Serial Bus Specification, Version 1.0.
-
-
- The hwarc driver handles the Radio Controller Interface of an HWA de-
- vice and properly controls the UWB (Ultra Wideband) Radio in the de-
- vice. The driver controls an HWA device to Scan, Start/Stop Beacon, Get
- IE, and so forth.
-
-FILES
- /kernel/drv/sparcv9/hwarc 64-bit SPARC ELF kernel module
-
-
- /kernel/drv/amd64/hwarc 64-bit x86 ELF kernel module
-
-
-ATTRIBUTES
- See attributes(7) for a description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Architecture |SPARC, x86 |
- +------------------------------+-----------------------------+
- | Availability |system/io/usb |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- hwahc(4D), usba(4D), uwba(4D), attributes(7), add_drv(8), prtconf(8),
- rem_drv(8), update_drv(8),
-
-
- Writing Device Drivers in Oracle Solaris 11.4
-
-
- Universal Serial Bus Specification 1.0, 1.1 and 2.0 - 1996, 1998, 2000
-
-
- Wireless Universal Serial Bus Specification 1.0
-
-
- https://www.usb.org/
-
-Oracle Solaris 11.4 5 Jan 2012 hwarc(4D)
diff -NurbBw 11.4.63/man4d/usba.4d 11.4.66/man4d/usba.4d
--- 11.4.63/man4d/usba.4d 2024-02-23 17:45:29.440817544 -0800
+++ 11.4.66/man4d/usba.4d 2024-02-23 17:51:33.374062489 -0800
@@ -60,26 +60,6 @@
hub class
- /kernel/drv/sparcv9/hwahc
-
- HWA Host Controller class
-
-
- /kernel/drv/amd64/hwahc
-
- HWA Host Controller class
-
-
- /kernel/drv/sparcv9/hwarc
-
- HWA Radio Controller class
-
-
- /kernel/drv/amd64/hwarc
-
- HWA Radio Controller class
-
-
/kernel/drv/sparcv9/scsa2usb
mass storage class
@@ -200,16 +180,6 @@
generic USB driver
- /kernel/drv/sparcv9/wusb_ca
-
- WUSB Cable Association class
-
-
- /kernel/drv/amd64/wusb_ca
-
- WUSB Cable Association class
-
-
/kernel/drv/sparcv9/ohci
open host controller driver
@@ -320,8 +290,8 @@
libusb(3LIB), ehci(4D), hid(4D), hubd(4D), ohci(4D), scsa2usb(4D),
ugen(4D), uhci(4D), usb_ac(4D), usb_as(4D), usb_ia(4D), usb_mid(4D),
usbprn(4D), usbsacm(4D), usbser_edge(4D), usbsksp(4D), usbsprl(4D), us-
- bvc(4D), wusb_ca(4D), wusb_df(4D), virtualkm(4D), xhci(4D), attrib-
- utes(7), cfgadm_usb(8), wusbadm(8), Intro(9F), Intro(9S)
+ bvc(4D), virtualkm(4D), xhci(4D), attributes(7), cfgadm_usb(8), In-
+ tro(9F), Intro(9S)
Writing Device Drivers in Oracle Solaris 11.4
@@ -365,4 +335,4 @@
Driver is incompatible with USBA framework.
-Oracle Solaris 11.4 10 Feb 2020 usba(4D)
+Oracle Solaris 11.4 25 Sept 2023 usba(4D)
diff -NurbBw 11.4.63/man4d/uwba.4d 11.4.66/man4d/uwba.4d
--- 11.4.63/man4d/uwba.4d 2024-02-23 17:45:29.471757327 -0800
+++ 11.4.66/man4d/uwba.4d 1969-12-31 16:00:00.000000000 -0800
@@ -1,58 +0,0 @@
-uwba(4D) Device Drivers & /dev files uwba(4D)
-
-NAME
- uwba, uwb - Solaris UWB Architecture (UWBA)
-
-DESCRIPTION
- Ultra-WideBand (UWB) radio technology supports high bandwidth for wire-
- less devices. UWBA is a miscellaneous module and it supports radio con-
- troller drivers for UWB based devices like HWA (Host Wire Adapter),
- WHCI (Wireless Host Controller Interface) and so forth. For example,
- both HWA radio controller driver (hwarc) and whci driver register to
- uwba during attach.
-
-
- UWBA provides a series of common interfaces for drivers that support
- UWB radio technology. Each radio controller driver register itself as a
- UWB dev to the uwba model in the attach entry, then other driver or
- module can control this device to perform the UWB functions through a
- list of common interface. For example, a hwahc driver can control the
- hwarc driver to scan in a specific channel, start/stop beacon, manage
- device/MAC address, and so forth.
-
-FILES
- /kernel/misc/amd64/uwba 64-bit x86 ELF kernel module
-
-
- /kernel/misc/sparcv9/uwba 64-bit SPARC ELF kernel module
-
-
-ATTRIBUTES
- See attributes(7) for a description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Architecture |PCI-based systems |
- +------------------------------+-----------------------------+
- | Availability |system/io/ultra-wideband |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- hwahc(4D), hwarc(4D), usba(4D), attributes(7)
-
-
- Writing Device Drivers in Oracle Solaris 11.4
-
-
- ECMA-368 High Rate Ultra Wideband PHY and MAC Standard, 1st Edition
-
-
- Wireless Host Controller Interface Specification for Certified Wireless
- Universal Serial Bus, Version 0.95
-
-
- Wireless Universal Serial Bus Specification 1.0
-
-Oracle Solaris 11.4 5 Jan 2012 uwba(4D)
diff -NurbBw 11.4.63/man4d/wusb_ca.4d 11.4.66/man4d/wusb_ca.4d
--- 11.4.63/man4d/wusb_ca.4d 2024-02-23 17:45:29.501277984 -0800
+++ 11.4.66/man4d/wusb_ca.4d 1969-12-31 16:00:00.000000000 -0800
@@ -1,59 +0,0 @@
-wusb_ca(4D) Device Drivers & /dev files wusb_ca(4D)
-
-NAME
- wusb_ca - WUSB Cable Association Driver
-
-DESCRIPTION
- The wusb_ca driver is a USBA (Solaris USB Architecture) compliant
- client driver that supports the cable association model which is de-
- fined in Association Models Supplement to the Certified WUSB specifica-
- tion.
-
-
- The wireless USB cable association driver is a USB class driver that
- provides interfaces for establishing a first-time connection between
- Wireless USB hosts and devices. This process of establishing a first-
- time connection is called association in WUSB standard. It is a prereq-
- uisite process that must be completed by hosts and devices prior to im-
- plementing the security requirements outlined in Wireless Universal Se-
- rial Bus Specification 1.0.
-
-
- Users should use wusbadm(8) to do cable association for WUSB devices.
-
-FILES
- /kernel/drv/amd64/wusb_ca
-
- 64-bit x86 ELF kernel module
-
-
- /kernel/drv/sparcv9/wusb_ca
-
- 64-bit SPARC ELF kernel module
-
-
-ATTRIBUTES
- See attributes(7) for a description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Architecture |SPARC, x86 |
- +------------------------------+-----------------------------+
- | Availability |system/io/usb |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- hwahc(4D), hwarc(4D), usba(4D), attributes(7), wusbadm(8)
-
-
- Writing Device Drivers in Oracle Solaris 11.4
-
-
- Wireless Universal Serial Bus Specification 1.0
-
-
- https://www.usb.org/
-
-Oracle Solaris 11.4 14 Jun 2023 wusb_ca(4D)
diff -NurbBw 11.4.63/man4d/wusb_df.4d 11.4.66/man4d/wusb_df.4d
--- 11.4.63/man4d/wusb_df.4d 2024-02-23 17:45:29.527891872 -0800
+++ 11.4.66/man4d/wusb_df.4d 1969-12-31 16:00:00.000000000 -0800
@@ -1,69 +0,0 @@
-wusb_df(4D) Device Drivers & /dev files wusb_df(4D)
-
-NAME
- wusb_df, hwa1480_fw - WUSB firmware download driver and firmware module
- for Intel i1480 chipset
-
-DESCRIPTION
- The wusb_df driver is a Solaris USB Architecture (USBA) compliant
- client driver that is used to download firmware for Host Wire Adapter
- (HWA) dongles that use Intel i1480 chipsets.
-
-
- Currently, the wusb_df driver can only download driver for Intel i1480
- based HWA dongles. The hwa1480_fw is a miscellaneous module which is
- transformed from Intel's firmware binary version RC1.3PA2-20070828.
- wusb_df reads firmware data from hwa1480_fw module and downloads it to
- HWA hardware.
-
-
- Users can use elfwrap(1) to transform new firmware binary. Users must
- use the same name as hwa1480_fw, since wusb_df only recognizes this
- symbol.
-
-FILES
- /kernel/drv/sparcv9/wusb_df
-
- 64-bit SPARC ELF kernel module
-
-
- /kernel/drv/amd64/wusb_df
-
- 64-bit x86 ELF kernel module
-
-
- /kernel/misc/sparcv9/hwa_1480
-
- 64-bit SPARC ELF kernel module
-
-
- /kernel/drv/amd64/hwa_1480
-
- 64-bit x86 ELF kernel module
-
-
-ATTRIBUTES
- See attributes(7) for a description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Architecture |SPARC, x86 |
- +------------------------------+-----------------------------+
- | Availability |system/io/usb |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- elfwrap(1), attributes(7), add_drv(8), rem_drv(8), update_drv(8)
-
-
- Writing Device Drivers in Oracle Solaris 11.4
-
-
- Wireless Universal Serial Bus Specification 1.0
-
-
- https://www.usb.org/
-
-Oracle Solaris 11.4 14 Jun 2023 wusb_df(4D)
diff -NurbBw 11.4.63/man5/audit_tags.5 11.4.66/man5/audit_tags.5
--- 11.4.63/man5/audit_tags.5 2024-02-23 17:45:29.560396896 -0800
+++ 11.4.66/man5/audit_tags.5 2024-02-23 17:51:33.406083322 -0800
@@ -40,7 +40,7 @@
value name or other value to be matched in the record. This might
be in the form of a Perl-compatible regular expression (see
- pcresyntax(3)). A value delimited by double quotes is in-
+ pcre2syntax(3)). A value delimited by double quotes is in-
terpreted as a PCRE.
@@ -167,4 +167,4 @@
HISTORY
audit_tags were added in Oracle Solaris 11.4.0.
-Oracle Solaris 11.4 21 Jun 2021 audit_tags(5)
+Oracle Solaris 11.4 20 Oct 2023 audit_tags(5)
diff -NurbBw 11.4.63/man5/audit.log.5 11.4.66/man5/audit.log.5
--- 11.4.63/man5/audit.log.5 2024-02-23 17:45:29.593703754 -0800
+++ 11.4.66/man5/audit.log.5 2024-02-23 17:51:33.442921277 -0800
@@ -461,7 +461,7 @@
port ID 4 bytes/8 bytes (32-bit/64-bit value)
machine address 4 bytes (IPv4 address)
principal length 2 bytes
- principal princiapal legngth bytes (ASCIIZ)
+ principal principal length including terminating NULL byte
@@ -480,7 +480,7 @@
address type/length 4 byte
machine address 16 bytes (IPv6 address)
principal length 2 bytes
- principal princiapal legngth bytes (ASCIIZ)
+ principal principal length including terminating NULL byte
@@ -655,11 +655,11 @@
mitted.
SEE ALSO
- audit_class(5), audit_event(5), audit_binfile(7), audit_syslog(7), au-
- dit(8), auditconfig(8), auditd(8), auditrecord(8), auditreduce(8),
- praudit(8)
+ audit_class(5), audit_event(5), audit_binfile(7), audit_syslog(7),
+ admhist(8), audit(8), auditconfig(8), auditd(8), auditrecord(8), au-
+ ditreduce(8), praudit(8)
Managing Auditing in Oracle Solaris 11.4
-Oracle Solaris 11.4 16 May 2023 audit.log(5)
+Oracle Solaris 11.4 4 Dec 2023 audit.log(5)
diff -NurbBw 11.4.63/man5/resolv.conf.5 11.4.66/man5/resolv.conf.5
--- 11.4.63/man5/resolv.conf.5 2024-02-23 17:45:29.627429879 -0800
+++ 11.4.66/man5/resolv.conf.5 2024-02-23 17:51:33.487143231 -0800
@@ -113,6 +113,18 @@
Sets RES_DEBUG in the _res.options field.
+ usevc
+
+ Sets RES_USEVC in the _res.options field to use TCP instead of
+ UDP for queries.
+
+
+ use-vc
+
+ Sets RES_USEVC in the _res.options field to use TCP instead of
+ UDP for queries. GNU libc alias for usevc.
+
+
ndots:n
Sets a threshold floor for the number of dots which must appear
@@ -283,4 +295,4 @@
Working With Oracle Solaris 11.4 Directory and Naming Services: DNS and
NIS
-Oracle Solaris 11.4 19 Oct 2021 resolv.conf(5)
+Oracle Solaris 11.4 27 Sep 2023 resolv.conf(5)
diff -NurbBw 11.4.63/man7/firewall.7 11.4.66/man7/firewall.7
--- 11.4.63/man7/firewall.7 2024-02-23 17:45:29.657518523 -0800
+++ 11.4.66/man7/firewall.7 2024-02-23 17:51:33.517440199 -0800
@@ -63,13 +63,6 @@
shipped by the package defines no network policy. Accordingly, all
traffic is allowed to and from the host by default.
-
- If the system is being upgraded from S11.3, any existing PF firewall
- configuration will be preserved. The upgrade process also handles a
- conversion from any existing legacy IPF firewall to PF. The IPF to PF
- conversion is handled by the ipf2pf(7) service, which runs during the
- first boot to an upgraded boot environment.
-
SERVICE
The firewall is managed by the svc:/network/firewall transient service.
This service supports the following svcadm(8) subcommands:
diff -NurbBw 11.4.63/man7/ipf2pf.7 11.4.66/man7/ipf2pf.7
--- 11.4.63/man7/ipf2pf.7 2024-02-23 17:45:29.687762223 -0800
+++ 11.4.66/man7/ipf2pf.7 1969-12-31 16:00:00.000000000 -0800
@@ -1,173 +0,0 @@
-ip...f(7Standards, Environments, Macros, Character Sets, and miscellaip...f(7)
-
-NAME
- ipf2pf - migrating from IPF to PF
-
-DESCRIPTION
- Oracle Solaris 11.4 ships with network firewall, which is based on
- OpenBSD Packet Filter. For more information, see the firewall(7) man
- page. To facilitate transition from IPF to PF the system upgrade in-
- stalls ipf2pf (pkg:/network/ipf2pf) package. This package handles the
- system's dependencies on the obsolete IPF package, pkg:/network/ipfil-
- ter.
-
- SERVICE
- The ipf2pf package installs the svc:/network/ipf2pf SMF service. This
- service runs only once, at the first boot into a newly upgraded boot
- environment. The service stores the now obsolete ipfilter configuration
- in the /var/firewall/legacy.ipf/conf directory.
-
-
- The ipf2pf service converts the IPF configuration to a PF configura-
- tion. The conversion is written to /var/fire-
- wall/legacy.ipf/conf/pf.conf. The system administrator should manually
- verify that the result of the conversion still implements the desired
- firewall policy before deploying it on the production system. Also keep
- in mind the upgrade process leaves your system with default firewall
- configuration, which provides no ACL policy or protection.
-
- DIFFERENCES TO IPF
- IPF rule syntax can be seen as a kind of subset of PF grammar. This can
- mislead into assuming that the IPF and PF firewalls are the same. They
- are not same, they are just similar. The first difference to note is PF
- typically uses one configuration file, while IPF uses up to four con-
- figuration files:
-
-
- ipf.conf, ipf6.conf Policy rules for IPv4/IPv6
-
-
- ipnat.conf NAT rules
-
-
- ippool.conf Definitions of radix tables (IP pools), used by
- policy rules at from/to match options
-
-
-
-
- For more information about how PF configuration works in Oracle So-
- laris, see the firewall(7) man page.
-
-
- The following are differences between IPF and PF which might not be im-
- mediately obvious.
-
- STATEFUL INSPECTION
- Unlike IPF the PF pass rules are implicitly stateful. Consider rule:
-
- pass in from any to any
-
-
-
- This rule is syntactically correct in both firewalls, however each
- firewall interprets the rule quite differently. When converting this
- rule from IPF to PF, one needs the 'no state' option to preserve the
- IPF firewall policy in PF:
-
- pass in from any to any no state
-
-
-
- Also in case of state match, IPF does 'state mangling'. Consider an in-
- bound forwarded packet, which matches rule:
-
- pass in from any to any keep state
-
-
-
- The state created by IPF also matches the outbound forwarded packet. PF
- must add a rule for the outbound forwarded packet:
-
-
- pass in from any to any
- pass out from any to any
-
-
-
-
- The impact of this difference is illustrated in the following rule set:
-
-
- block out all
- pass in from any to any keep state
-
-
-
- These rules above, allow IPF host to forward traffic between remote
- endpoints. In case of PF no forwarded packets are allowed to leave the
- PF host, because all outbound packets hit the 'block' rule. No state in
- PF would cover outbound packets, too. To allow a PF host to forward
- traffic, one has to change the rules in PF to:
-
-
- block out all
- pass in from any to any keep state
- pass out from !self to any keep state
-
-
-
- The outbound rule allow the outbound packet to leave PF host (and cre-
- ate state) as long as it comes from a remote source, not PF host it-
- self.
-
- NAT
- Unlike PF, the IPF keeps two session tables.
-
- o Table for states created by rules
-
-
- o Table for NAT sessions created by nat-rules
-
-
-
- In IPF, NAT sessions define how IP addresses and port numbers in pack-
- ets should be altered. States are created by policy rules, while ses-
- sions are created by NAT rules.
-
-
- PF takes a completely different approach here. PF implements NAT as an
- optional action (nat-to/rdr-to) to be taken on a matching packet. The
- information about IP address translation is kept in a state table.
- Therefore, NAT optional actions cannot be used with rules that don't
- create state. If a packet is to be translated, it must create state.
-
- TUNABLES
- IPF uses tunables as parameters to define table sizes and session time-
- outs. To change a parameter value, the ipf -T option is used. To make
- the value persistent requires editing the kernel/drv/ipf.conf file. The
- ipf2pf conversion process does not preserve these tunables as they are
- irrelevant to PF.
-
-
- PF comes with its own parameters. The pfctl command is used to tweak
- those parameters at runtime. To make the change persistent, the parame-
- ters are added to the pf.conf file. For more information, see the
- pfctl(8) and pf.conf(7) man pages.
-
- PACKET LOGGING
- IPF uses the ipmon daemon to read logged packets from kernel to user-
- land using /dev/ipl device. Oracle Solaris provides PF with capture
- links for logging packets. For more information, see the dladm(8) man
- page. The tcpdump command is used to read the packets from kernel.
-
- IPPOOLS
- Consider using PF tables where IPF rules use ippools.
-
-ATTRIBUTES
- See attributes(7) for descriptions of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Volatile |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- firewall(7), pf.conf(7), pfctl(8), smf(7), attributes(7)
-
-
- Securing the Network in Oracle Solaris 11.4
-
-Oracle Solaris 11.4 15 Nov 2017 ip...f(7)
diff -NurbBw 11.4.63/man7/solaris-kz.7 11.4.66/man7/solaris-kz.7
--- 11.4.63/man7/solaris-kz.7 2024-02-23 17:45:29.738531835 -0800
+++ 11.4.66/man7/solaris-kz.7 2024-02-23 17:51:33.592585178 -0800
@@ -419,7 +419,11 @@
can be configured to reserve NPT memory re-
sources by setting value of this property to
the number of kernel zones expected to be
- concurrently running.
+ concurrently running. The default value for
+ this property is 0. If set to a non-zero
+ value, the Kernel Zone MRP service will re-
+ serve four 4M pages for a total of 16M * npt-
+ reservation.
@@ -1050,6 +1054,7 @@
anet (with exceptions stated below)
capped-memory:physical
+ capped-memory:memlzr
device
ib-vhca
ib-vhca:port
@@ -1176,4 +1181,4 @@
this will only succeed if coreadm(8) has configured a location for and
enabled kernel zone core dumps.
-Oracle Solaris 11.4 12 Sep 2023 so...z(7)
+Oracle Solaris 11.4 12 Oct 2023 so...z(7)
diff -NurbBw 11.4.63/man8/coreadm.8 11.4.66/man8/coreadm.8
--- 11.4.63/man8/coreadm.8 2024-02-23 17:45:29.780501545 -0800
+++ 11.4.66/man8/coreadm.8 2024-02-23 17:51:33.635944200 -0800
@@ -837,8 +837,8 @@
- Example 10 Configuring a non-Oracle Binary to Disable Logging for ASRs
- Upon Core Dump
+ Example 10 Configuring an Oracle Binary to Disable Logging of ASRs Upon
+ Core Dump
diff -NurbBw 11.4.63/man8/halt.8 11.4.66/man8/halt.8
--- 11.4.63/man8/halt.8 2024-02-23 17:45:29.808301605 -0800
+++ 11.4.66/man8/halt.8 2024-02-23 17:51:33.664999964 -0800
@@ -62,7 +62,7 @@
SEE ALSO
inittab(5), attributes(7), smf(7), reboot(8), dumpadm(8), init(8),
- shutdown(8), sync(8), syslogd(8) sysadm(8)
+ shutdown(8), sync(8), sysadm(8), syslogd(8)
NOTES
The halt and poweroff utilities do not cleanly shutdown smf(7) ser-
@@ -70,4 +70,4 @@
in inittab(5). To ensure a complete shutdown of system services, use
shutdown(8) or init(8) to reboot a Solaris system.
-Oracle Solaris 11.4 25 Jul 2023 halt(8)
+Oracle Solaris 11.4 4 Dec 2023 halt(8)
diff -NurbBw 11.4.63/man8/syslogd.8 11.4.66/man8/syslogd.8
--- 11.4.63/man8/syslogd.8 2024-02-23 17:45:29.851691717 -0800
+++ 11.4.66/man8/syslogd.8 2024-02-23 17:51:33.696241139 -0800
@@ -57,13 +57,9 @@
file. See EXAMPLES.
- The /etc/default/syslogd file contains the default parameter settings,
- which are in effect if neither the -t nor -T option is selected.
-
-
- The recommended way to allow or disallow message logging is through the
- use of the service management facility (smf(7)) instance svc:/sys-
- tem/system-log:default property:
+ Properties of syslogd can be set through the use of the service manage-
+ ment facility (smf(7)) instance svc:/system/system-log:default proper-
+ ties:
config/log_from_remote
@@ -74,12 +70,14 @@
false is equivalent to the -T command-line option. The default value
for log_from_remote is false. See NOTES.
- LOG_FROM_REMOTE
+ config/time_precision
+
- Specifies whether remote messages are logged. LOG_FROM_REMOTE=NO is
- equivalent to the -t command-line option. The default value for
- LOG_FROM_REMOTE is YES.
+ This property specifies in which precision fractional seconds are
+ logged. The default is 3 (milliseconds) and can set to any value from 0
+ (no fractional seconds, the syslog message will be the same as before)
+ to 9 (nanoseconds). The fractions are rounded down.
OPTIONS
The following options are supported:
@@ -171,7 +169,20 @@
# svccfg -s svc:/system/system-log:default setprop \
config/log_from_remote=true
- # svcadm restart svc:/system/system-log
+ # svcadm restart svc:/system/system-log:default
+
+
+ Example 5 Change the time stamps precision to microseconds
+
+
+
+ The following commands enable syslogd to log time stamps in microsec-
+ onds precision.
+
+
+ # svccfg -s svc:/system/system-log:default setprop \
+ config/time_precision=6
+ # svcadm restart svc:/system/system-log:default
FILES
diff -NurbBw 11.4.63/man8/wusbadm.8 11.4.66/man8/wusbadm.8
--- 11.4.63/man8/wusbadm.8 2024-02-23 17:45:29.885020740 -0800
+++ 11.4.66/man8/wusbadm.8 1969-12-31 16:00:00.000000000 -0800
@@ -1,452 +0,0 @@
-wusbadm(8) System Administration Commands wusbadm(8)
-
-NAME
- wusbadm - administer wireless USB hosts and devices
-
-SYNOPSIS
- wusbadm list [-h | -d] [-o field[,...]]
-
-
- wusbadm associate [-h host-id] [[-c [-f]] | -n] [-o]
-
-
- wusbadm remove-dev [[-d dev-id] | [-h host-id]] [-f]
-
-
- wusbadm remove-host [-h host-id] [-f]
-
-
- wusbadm enable-host [-h host-id]
-
-
- wusbadm disable-host [-h host-id]
-
-DESCRIPTION
- The wusbadm command provides a command line interface to administer
- wireless USB hosts and devices, including listing hosts and devices in-
- formation, associating the host with the device, removing host or de-
- vice information from the system, and enabling or disabling hosts.
-
-
- Before connecting a wireless USB device to a host for the first time, a
- user needs to set up the association information between them by run-
- ning the wusbadm associate subcommand. Following this, the user can
- connect or disconnect the device by simply turning on or off the device
- radio (perhaps a button on the device, depending on the manufacturer).
- The device radio's turning on and off are analogous to the hotplugging
- of wired USB devices.
-
-
- The association information created by the associate subcommand is
- maintained in the non-volatile memory of the device and the host. On
- the host, it can be removed by the remove-dev or remove-host subcom-
- mands. On the device, it can be overwritten by another association. For
- a device is associated with multiple hosts, the way that the device
- prioritizes or updates its multiple records of association depends on
- the manufacturer.
-
-
- Each wusbadm subcommand operates on one of the following objects:
-
- host-id
-
- A two-digit number (in the range from 01 to 99) that uniquely iden-
- tifies a wireless USB host on a system. It is generated when the
- wusb service (see NOTES section) is successfully enabled and finds
- the host instance for the first time. The number is maintained un-
- til removed by remove-host subcommand.
-
-
- dev-id
-
- A five-digit number that uniquely identifies a wireless USB device
- associated with a wireless USB host. The first two digits are the
- host-id of the wireless USB host with which the device is associ-
- ated. The last three-digit number (in the range from 001 to 999) is
- used to differentiate devices associated with the same host. In the
- five-digit number, the first two digits and the last three are sep-
- arated by a dot.
-
- dev-id is generated during the device association process. It is
- maintained for the device until removed by the remove-dev subcom-
- mand or until updated by another association between the same host
- and device.
-
-
-SUB-COMMANDS
- The following subcommands are supported. Except for the list subcom-
- mand, each subcommand displays subcommand-specific usage information if
- you run it without any options or operands.
-
- list [-h | -d] [-o field[,...]]
-
- List wireless USB hosts and devices on a system, displaying the ID,
- state, and type for all hosts and devices. By default, list will
- list all hosts and devices and all fields. Each host and its de-
- vices will be displayed as a group. This subcommand supports the
- following options.
-
- -o field[,...], --output=field[,...]
-
- A case-insensitive, comma-separated list of output fields to
- display. The field name must be one of the fields listed below,
- or the special value all to display all fields. By default
- (without -o), list displays all fields.
-
- ID
-
- The host-id or dev-id.
-
-
- TYPE
-
- The host or device types.
-
- For host, the types include whci (on-board host) and hwa
- (hot-pluggable host).
-
- For device, the types include kbd, mouse, storage, printer,
- dwa (wireless USB hub), audio, video, and so forth.
-
-
- STATE
-
- There are the following states for the host:
-
-
- enabled
-
- The host is ready to work or is already working, in-
- cluding performing association, connecting devices,
- performing data communication, and so forth.
-
-
- disabled
-
- The host is not ready to work with any devices and no
- devices are connected to the host. It might be stopped
- by a disable-host subcommand, or the host might not be
- available because it is physically unplugged or because
- of a driver detach.
-
-
- disconnected
-
- The host is not attached to the system. An hwa device
- is in this state after it is unplugged from the USB
- port on the system.
-
- There are the following states for the device:
-
- connected
-
- The device is connected with a host and ready to be
- opened, or it is already opened and working. By de-
- fault, the device tries to get into this state after
- the association is complete and its radio is turned on.
-
-
- disconnected
-
- The device is not connected to a host or not ready to
- be opened yet. The device might be in this state be-
- cause its radio is out of range, power is off, hardware
- problems, and so forth.
-
-
-
-
- -h, --host
-
- List the wireless USB hosts only.
-
-
- -d, --device
-
- List the wireless USB devices only.
-
-
-
- associate [-h host-id] [[-c [-f]] | -n] [-o]
-
- Designate the host to start an association process. Association is
- the initial step before a wireless USB device can be connected with
- a wireless USB host.
-
- There are two association models:
-
-
- Cable association
-
- A user connects the device and host with a USB cable first, and
- then run this subcommand to designate the host to setup the as-
- sociation information with the device. After the association is
- in effect, the cable is no longer needed in the subsequent con-
- nections between the same host and the device.
-
-
- Numeric association
-
- A user turns on the device radio and runs this subcommand to
- designate the host to talk to the device. A short number is
- then displayed on both host and device. The user compares the
- values of the numbers and confirms on both the host and the de-
- vice.
-
- Following a successful association, the associated USB host and de-
- vice are able to proceed with the wireless connection process. By
- default, the association information will be kept both on the host
- and the device until it is removed or overwritten.
-
- If there are multiple devices available for association, this sub-
- command will list all of them, enabling a user to choose among
- them. This subcommand has the following options.
-
-
- -h host-id, --host host-id
-
- Specify the host for which the association will be done. If
- this option is not specified, this subcommand lists all enabled
- hosts for users to choose.
-
-
- -c, --cable
-
- Start the cable association process. A user plugs the wireless
- USB device to the host and runs the associate subcommand with
- this option.
-
-
- -n, --numeric
-
- Start the numeric association process. This subcommand prompts
- the user to compare the number displayed on the host and the
- device.
-
- If neither of the preceding two association model options (-n or
- -c) is specified, this subcommand prompts the user to specify one
- of the following association model options.
-
- -f, --force
-
- Start the cable association process. A user plugs the wireless
- USB device to the host and runs the associate subcommand with
- this option.
-
-
- -o, --onetime
-
- Indicate that this association is for a one-time connection.
- That is, after the association, if the device is connected and
- then disconnected, the association information for this device
- will be removed from the host system. A user would need to per-
- form another association for the next connection.
-
-
-
- remove-dev [[-d dev-id] | [-h host-id]][-f]
-
- Remove the association information of the wireless USB device from
- the system. After the removal, the device cannot be connected with
- the host until the user runs the associate subcommand again, for
- the host and device. This subcommand has the following options.
-
- -d, --device=dev-id
-
- Remove the association information of the wireless USB device
- specified by dev-id.
-
-
- -h host-id, --host=host-id
-
- Remove the association information of all the wireless USB de-
- vices associated with the host specified by host-id.
-
-
- -f, --force
-
- Perform the removal without asking for confirmation. If the de-
- vice is being connected with the host, then this subcommand
- will force it to disconnect.
-
-
-
- remove-host [-h host-id] [-f]
-
- Remove the host information from the system, including host-id and
- the association information of all the devices associated with the
- host. This subcommand is used most often for removing the temporar-
- ily used hot-pluggable wireless USB host, for example, a hwa don-
- gle. The host can be brought back by being re-enumerated, for exam-
- ple, physically hot-plugging a hwa dongle. The host-id will then be
- updated and no device association information can be restored. It
- is not recommended to remove a on-board host. This subcommand has
- the following options.
-
- -h host-id, --host=host-id
-
- Specifies the host-id to be removed.
-
-
- -f, --force
-
- Perform the removal without asking for confirmation. If there
- are one or more devices connected with the host, then force
- them to disconnect.
-
-
-
- enable-host [-h host-id]
-
- Take the host to the enabled state. By default, the host is in the
- enabled state. This subcommand has the following option.
-
- -h host-id, --host=host-id
-
- Specifies the host-id to be enabled.
-
-
-
- disable-host [-h host-id] [-f]
-
- Take the host to the disabled state. The host-id and all the asso-
- ciation information of the host are maintained. Issuing an enable-
- host subcommand brings the host back to the enabled state. This
- subcommand has the following options.
-
- -h host-id, --host=host-id
-
- Specifies the host-id to be disabled.
-
-
- -f, --force
-
- Perform the disable operation without asking for confirmation.
- If there are one or more devices connected with the host, this
- option forces them to disconnect.
-
-
-
-EXAMPLES
- Example 1 Listing All Hosts and Devices
-
-
-
- The following command lists all wireless USB hosts and devices.
-
-
- # wusbadm list
- 01 enabled hwa
- 01.001 connected mouse
- 01.002 connected kbd
- 02 enabled whci
- 02.001 connected printer
- 02.002 disconnected storage
- 03 disabled hwa
- 03.001 disconnected storage
- 03.002 disconnected dwa
-
-
- Example 2 Associating to a Device Using Cable
-
-
-
- The following command associates a device to a specific host (host-id
- 01), using the cable association approach.
-
-
- # wusbadm associate -h 01 -c
- Associate a device with host (01) via cable.
- Continue (yes/no)?
-
-
- Example 3 Removing a Device's Association
-
-
-
- The following command removes a device's association information from
- the host system.
-
-
- # wusbadm remove-dev -d 01.002
- Remove the information of device (01.002) from system.
- This device can not be connected with the host until it is associated
- again. Continue (yes/no)?
-
-
- Example 4 Removing Associations for All Devices
-
-
-
- The following command removes the association information for all de-
- vices associated with a specific host.
-
-
- # wusbadm remove-dev -h 02
- Remove the information of all the devices associated with host (02)
- from the system.
- All the devices associated with the host cannot be connected with it
- until they are associated again. Continue (yes/no)?
-
-
-EXIT STATUS
- The following exit values are returned:
-
- 0
-
- Successful operation.
-
-
- 1
-
- Error: the operation failed. For example, a device failed to asso-
- ciate with a host.
-
-
- 2
-
- Usage error.
-
-
-ATTRIBUTES
- See attributes(7) for descriptions of the following attributes:
-
-
- /usr/sbin
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Availability |system/io/usb |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- hwahc(4D), usba(4D), attributes(7)
-
-NOTES
- The wusb (wireless USB administration) service is managed by the ser-
- vice management facility, smf(7), under the service identifier:
-
- svc:/system/wusb:default
-
-
-
- Administrative actions on this service, such as enabling, disabling, or
- requesting restart, can be performed using svcadm(8). The service's
- status can be queried using the svcs(1) command.
-
-
- The wusb service is implemented by the wusbd daemon, a private inter-
- face. As with the wusb service, the daemon is started by the SMF. Spec-
- ify the daemon with the service instance:
-
- svc:/system/wusbd:default
-
-
-
- The wusbd daemon should not be invoked directly.
-
-Oracle Solaris 11.4 15 Apr 2019 wusbadm(8)
diff -NurbBw 11.4.63/man8s/memory-reserve.8s 11.4.66/man8s/memory-reserve.8s
--- 11.4.63/man8s/memory-reserve.8s 2024-02-23 17:45:29.912772240 -0800
+++ 11.4.66/man8s/memory-reserve.8s 2024-02-23 17:51:33.726209927 -0800
@@ -1,54 +1,107 @@
memory-reserve(8s) SMF Services memory-reserve(8s)
NAME
- memory-reserve - service to manage memory reservation pools
+ memory-reserve - service to manage Memory Reservation Pools
SYNOPSIS
svc:/system/memory-reserve
DESCRIPTION
- memory-reserve is an SMF service to configure and manage Memory Reser-
- vation Pools (MRPs). A memory-reserve service instance can be config-
- ured with the desired properties of the MRP. The creation, destruction,
- and modification of the MRP can then be managed by enabling, disabling,
- and refreshing the service.
+ memory-reserve is a SMF service for managing Memory Reservation Pools
+ (MRPs). MRPs are used to reserve memory from the system for exclusive
+ use by Kernel Zones solaris-kz(7) or applications which use Optimized
+ Shared Memory (OSM), shmget_osm(2). By default, memory-reserve services
+ are disabled. To enable, an administrator must, at minimum, set the
+ config/size property, specifying the amount of memory the service in-
+ stance is to reserve. Additional properties may be set to shape the
+ memory reservation for platform and instance type requirements.
+
+
+ The creation, destruction, and modification of a MRP service instance
+ is managed by enabling, disabling, and refreshing the service instance
+ using svcadm(8). If the MRP instance fails to transition to the enabled
+ state due to insufficient memory or the lack of a specified page size,
+ the MRP instance will be placed in the maintenance state. Once enabled,
+ a MRP instance may be reconfigured using svccfg(8) to increase or de-
+ crease its memory reservation by modifying the allowed properties and
+ refreshing the service instance. If the system is unable to satisfy the
+ requested configuration the service instance will be placed in the de-
+ graded state.
SMF Configuration
Properties
The following properties can be set:
- config/size
+ config/type
- Size of the reservation to make. A scale (K, M, G, T) can be
- applied to the value.
+ Type of Memory Reservation Pool instance. Supported types are
+ solaris-kz for reserving memory for use by Kernel Zones and so-
+ laris-osm to reserve memory for use by OSM capable applica-
+ tions. This property is automatically set by the default ser-
+ vice instances.
- config/pagesize-policy
+ config/size
- Allowed values are smallest-only, largest-available and
- largest-only. Only used by the Kernel Zones instance, other
- types ignore this value.
+ Size of the memory reservation to make. A scale (K, M, G, T)
+ can be applied to the value. This property is required to be
+ set for all service instance types prior to the service being
+ enabled. Once enabled, this property can be modified and the
+ service instance refreshed to reconfigure the service instance.
- config/type
+ config/pagesize-policy
- Read only. Type of Memory Reservation Pool.
+ Controls how solaris-kz MRPs select the page size when allocat-
+ ing the memory for the MRP. Allowed values are smallest-only,
+ largest-available, largest-only, and fixed. The default is to
+ select the smallest valid page size. See pagesize(1) to deter-
+ mine the available page sizes. Once enabled, the selected page
+ size can be determined by examining the value of the state/pgsz
+ property of the service instance. Once enabled this property
+ cannot be modified. Only used by the solaris-kz MRP service.
config/lgrps
Locality group (LGRP) id(s) to use if desired. The default is
to use the root LGRP, spreading the reservation across avail-
- able LGRPs. See lgrpinfo(1). Only used by the Kernel Zones in-
- stance, other types ignore this value.
+ able LGRPs. See lgrpinfo(1). Once enabled, this property cannot
+ be modified. Only used by the solaris-kz MRP type.
config/granule-size
Size of the OSM granules that are to allocate from the pool. A
- scale (K, M, G, T) can be applied to the value. Only used by
- the OSM instance, other types ignore this value.
+ scale (K, M, G, T) can be applied to the value. Once enabled,
+ this property cannot be modified. Only used by the OSM in-
+ stance, other types ignore this value.
+
+
+ config/pagesize
+
+ If the pagesize-policy property is set to fixed, this property
+ must be set to a page size supported by the host. The size is
+ specified as an integer value with an optional scale suffix (K,
+ M, G). See pagesize(1) on how to determine the supported page
+ sizes for a given kernel zone host. The smallest allowed page
+ size is 256MB on SPARC and 2MB on x86. Once enabled, this prop-
+ erty cannot be modified. Only used by the solaris-kz MRP ser-
+ vice type.
+
+
+ config/npt-reservation
+
+ The npt-reservation property can be set to reserve additional
+ memory for SPARC kernel zones Nested Page Tables. The value of
+ this property should be set to the number of kernel zones ex-
+ pected to be running concurrently. The default value for this
+ property is 0. For each kernel zone specified in the property
+ value, the MRP will reserve four 4M pages for a total of 16M
+ per kernel zone. This property can be modified after the ser-
+ vice has been enabled. This property is only supported on SPARC
+ platforms and only used by the solaris-kz MRP service type.
@@ -58,10 +111,10 @@
svc:/system/memory-reserve:zones
Disabled by default, this service instance is configured for
- direct use by Kernel Zones with a pre-set config/type property
- of solaris-kz. Additional configuration by an administrator, at
- minimum setting the config/size property, is required before
- this instance can be enabled.
+ use by solaris-kz(7) brand zones with a pre-set config/type
+ property of solaris-kz. Additional configuration by an adminis-
+ trator, at minimum setting the config/size property, is re-
+ quired before this service can be enabled.
The config/pagesize-policy and config/size properties provide
kernel zones with the abilities that are provided to other zone
@@ -71,13 +124,12 @@
The config/npt-reservation property can be set to reserve addi-
tional memory for SPARC kernel zones Nested Page Tables. The
value of this property should be set to the number of kernel
- zones expected to be running concurrently. This property is
- only supported on SPARC platforms.
+ zones expected to be running concurrently.
The config/granule-size property is ignored for this instance
type.
- For a worked example, see the solaris-kz(7) page.
+ For a working example, see the solaris-kz(7) page.
@@ -104,4 +156,4 @@
lgrpinfo(1), smf(7), solaris-kz(7), mrpstat(8), svcadm(8), svccfg(8),
zonecfg(8)
-Oracle Solaris 11.4 1 Jan 2023 memory-reserve(8s)
+Oracle Solaris 11.4 12 Sept 2023 memory-reserve(8s)
diff -NurbBw 11.4.63/man9f/nvlist_add_boolean.9f 11.4.66/man9f/nvlist_add_boolean.9f
--- 11.4.63/man9f/nvlist_add_boolean.9f 2024-02-23 17:45:29.943415111 -0800
+++ 11.4.66/man9f/nvlist_add_boolean.9f 2024-02-23 17:51:33.756130047 -0800
@@ -150,10 +150,6 @@
one thread may actively change a given nvlist_t at a time. The caller
is responsible for the synchronization.
-
- The nvlist_add_boolean() function is deprecated. Instead, use the
- nvlist_add_boolean_value() function.
-
RETURN VALUES
0 success
@@ -175,4 +171,4 @@
KM_NOSLEEP. These functions can be called from user or kernel context
in all cases.
-Oracle Solaris 11.4 10 Dec 2013 nvlist_add_boolean(9F)
+Oracle Solaris 11.4 2 Oct 2023 nvlist_add_boolean(9F)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment