Skip to content

Instantly share code, notes, and snippets.

@alanc

alanc/SRU75-man-page-changes.diff

Created November 26, 2024 17:10
Show Gist options
  • Save alanc/ccba899914be359af234159520a5fe55 to your computer and use it in GitHub Desktop.
Save alanc/ccba899914be359af234159520a5fe55 to your computer and use it in GitHub Desktop.
Download ZIP
Changes to core OS man pages in Oracle Solaris 11.4 SRU 75
Raw
Solaris-11.4-SRU75-man-page-changes.txt
36426621 pgrep (and maybe others) could use an option to look up group siblings of a specified PID
36619541 mdb needs to cope with filter symbols, specifically dlopen
36647516 mdb needs to cope with capability symbols
36647654 mdb(1) claims you can use obj`file`name to specify a symbol. There is no support for `file
36650566 making CTF public
36671274 (un)mount -r would be beneficial
36675615 ctf strip class for ld and strip
36717952 sys/hdio.h should be removed
36740603 zfs_share.8 has numerous syntactic errors in command synopses
36765455 add IKEv1 DPD counters
36769431 nscfg and man page nscfg.8 do not document -n option well
36801449 ldapclient.8 should be clearer with regards to credential level
36813261 ld -zguidance should diagnose poor capability identifier names
36827583 ctfdump should handle multiple arguments and archives
36834258 mailx could suggest using a modern MUA
36847015 ctfconvert/ctfmerge should not unlink input files on error by default
36862010 Remove the -R switch from dladm
36862022 Remove the -R switch from flowadm
36901947 nscd.conf.5: document the "svccfg describe" command in full
36951744 Issues with list-bindings and list-services subcommands
37010511 Assorted fixes for Section 3head man pages
37040431 incorrect prefix markup in 9e manpages is widespread
37045389 chmod(1) still says setgid bit cannot be set on dirs in absolute mode
37062175 man page history additions for SRU 75
PSARC 2024/073 pgrep(1) options -Z and -r pidlist options
PSARC/2024/077 ctf strip class for ld and strip
PSARC/2024/078 making CTF public
PSARC/2024/085 ZFS mount/unmount -r
PSARC/2024/090 ctfdump support for multiple files and archives
PSARC/2024/092 Removal of the -R root-dir option from dladm and flowadm.
PSARC/2024/097 ctfconvert and ctfmerge -r option
Copyright (c) 1983, 2024, Oracle and/or its affiliates.
Raw
SRU75-man-page-changes.diff
diff -NurbBw 11.4.72/man1/chmod.1 11.4.75/man1/chmod.1
--- 11.4.72/man1/chmod.1 2024-11-22 11:50:40.289422590 -0800
+++ 11.4.75/man1/chmod.1 2024-11-22 11:52:06.709568034 -0800
@@ -58,9 +58,7 @@
For directories, files are created with BSD semantics for prop-
agation of the group ID. With this option, files and subdirec-
tories created in the directory inherit the group ID of the di-
- rectory, rather than of the current process. For directories,
- the setgid bit can only be set or cleared by using either ab-
- solute or symbolic mode.
+ rectory, rather than of the current process.
1000
@@ -129,11 +127,6 @@
-
- For directories, the setgid bit cannot be set (or cleared) in absolute
- or symbolic mode; setting (or clearing) the setgid bit in symbolic mode
- must be done using g+s (or g-s).
-
Symbolic Mode
A symbolic mode command line has the following format:
@@ -1878,10 +1871,6 @@
Managing ZFS File Systems in Oracle Solaris 11.4
NOTES
- Absolute changes do not work for the set-group-ID bit of a directory.
- You must use g+s or g-s.
-
-
chmod permits you to produce useless modes so long as they are not il-
legal (for instance, making a text file executable). chmod does not
check the file type to see if mandatory locking is meaningful.
@@ -1904,4 +1893,32 @@
and groups who have ACL entries on the file. Use the ls(1) command to
make sure the appropriate permissions are set for all ACL entries.
-Oracle Solaris 11.4 11 April 2022 chmod(1)
+HISTORY
+ For directories, the setgid bit could only be set or cleared using g+s
+ or g-s on releases prior to Oracle Solaris 11.4. In Oracle Solaris
+ 11.4.0 and later, it may be set or cleared in absolute mode, as with
+ all other bits.
+
+
+ Support for the -c, --changes, --no-preserve-root, --preserve-root,
+ --silent, --quiet, --reference, --recursive, -v, --verbose, and --help
+ options was added in Oracle Solaris 11.4.0.
+
+
+ Support for the -H, -L, and -P options was added in Oracle Solaris
+ 11.3.12.
+
+
+ Support for the -@ option and specifying system attributes was added in
+ the Oracle Solaris 11.0.0 release. See sysattr(7) for details on when
+ support was added for each individual system attribute.
+
+
+ Support for ACL operations was added in the Solaris 10 6/06 (Update 2)
+ release.
+
+
+ The chown command, with support for the -f and -R options has been
+ present in all Sun and Oracle releases of Solaris.
+
+Oracle Solaris 11.4 10 Sep 2024 chmod(1)
diff -NurbBw 11.4.72/man1/ctfconvert.1 11.4.75/man1/ctfconvert.1
--- 11.4.72/man1/ctfconvert.1 1969-12-31 16:00:00.000000000 -0800
+++ 11.4.75/man1/ctfconvert.1 2024-11-22 11:52:06.748203191 -0800
@@ -0,0 +1,146 @@
+ctfconvert(1) User Commands ctfconvert(1)
+
+NAME
+ ctfconvert - convert debug sections to CTF
+
+SYNOPSIS
+ ctfconvert [-irsS] [-l label] [-L labelenv] [-o outfile] file
+
+DESCRIPTION
+ The ctfconvert utility reads debug sections from an ELF object file,
+ and uses that information to produce CTF (Compact C Type Format) data,
+ which is added to the object as a new section named .SUNW_ctf.
+
+
+ Compilers produce debug sections for the objects they create. These de-
+ bug sections are valuable for debuggers, and particularly for source
+ level debuggers, but they can be very large, and are often omitted from
+ production software used in non-debug environments. In constrast, CTF
+ data is generally small enough to be kept in almost any object, while
+ providing basic type information valuable to low level observability
+ tools. The mdb(1) and kmdb(1) debuggers, dtrace(8), and the proc(1)
+ tools, all make use of CTF, when present, to enhance their operation.
+
+OPTIONS
+ The following options are supported:
+
+ -i
+
+ Silently ignore, and leave unmodified, object files built from lan-
+ guages other than C. While CTF can be used with any language, the
+ information it captures corresponds directly to C level language
+ concepts, making CTF particularly useful with code written in C.
+
+
+ -l label
+
+ Specifies a label to be associated with the generated CTF. Labels
+ are of use when employing uniquification to share definitions be-
+ tween parent and children objects as a space saving measure. See
+ ctfmerge(1).
+
+
+ -L labelenv
+
+ Specifies a label to be associated with the generated CTF. The
+ value of the environment variable specified by labelenv provides
+ the label to be used. If the environment variable is not defined,
+ no label is set, and the behavior is as if no label were specified.
+
+
+ -o outfile
+
+ By default, ctfconvert modifies the input object in place. When the
+ -o option is specified, the input object is not modified, and the
+ updated object contents are instead written to the file given by
+ outfile.
+
+
+ -r
+
+ Remove file on error. This facilitates the use of ctfconvert as
+ part of a series of commands executed by a makefile rule. The re-
+ moval of the input file on error forces a subsequent execution of
+ the make utility to rerun the full set of commands required to
+ build the target, and ensures that CTF data is added.
+
+
+ -s
+
+ Associate the generated CTF section with the dynamic .dynsym symbol
+ table rather than the default .symtab.
+
+
+ -S
+
+ Strip compiler generated debug sections from the resulting object.
+
+
+ -v
+
+ Enable verbose mode.
+
+
+ -?
+ --help
+
+ Print usage message and immediately exit.
+
+
+
+OPERANDS
+ The following operands are supported.
+
+ file
+
+ The ELF file for which CTF data should be produced.
+
+
+NOTES
+ Historically, the ctfconvert utility defaulted to the removal of stabs
+ and dwarf sections after processing them. The -g option was used to
+ prevent this removal. In the current implementation, the behavior has
+ been reversed to retain stabs and dwarf sections by default. The -S op-
+ tion is provided to remove them in cases where removal is desired. The
+ -g option continues to be accepted for backward compatibility with old
+ makefiles, but no longer has any effect.
+
+EXAMPLES
+ Example 1 Apply ctfconvert to an object file and dump the result.
+
+
+ % cc -c -g main.c
+ % ctfconvert main.o
+ % ctfdump main.o
+
+
+EXIT STATUS
+ The following exit values are returned:
+
+ 0 Successful completion.
+
+
+ > 0 An error occurred.
+
+
+ATTRIBUTES
+ See attributes(7) for descriptions of the following attributes:
+
+ +------------------------------+-----------------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------------+
+ | Availability |developer/base-developer-utilities |
+ +------------------------------+-----------------------------------+
+ | Interface Stability |Committed |
+ +------------------------------+-----------------------------------+
+
+
+HISTORY
+ The CTF utilities, including ctfconvert, have been used in the con-
+ struction of Solaris since Sun Solaris 9. They were added as system
+ utilities in Oracle Solaris 11.4.72.
+
+SEE ALSO
+ ctfdump(1), ctfmerge(1)
+
+Oracle Solaris 11.4 6 August 2024 ctfconvert(1)
diff -NurbBw 11.4.72/man1/ctfdump.1 11.4.75/man1/ctfdump.1
--- 11.4.72/man1/ctfdump.1 1969-12-31 16:00:00.000000000 -0800
+++ 11.4.75/man1/ctfdump.1 2024-11-22 11:52:06.797690558 -0800
@@ -0,0 +1,82 @@
+ctfdump(1) User Commands ctfdump(1)
+
+NAME
+ ctfdump - dumps CTF content
+
+SYNOPSIS
+ ctfdump [-dfhlsSt] [-u ctffile] file...
+
+DESCRIPTION
+ The ctfdump utility symbolically dumps the contents of the CTF (Compact
+ C Type Format) data from the specified file(s). The options allow spe-
+ cific portions of the file to be displayed.
+
+
+ Archive files, produced by ar(1), can also be inspected with ctfdump.
+ In this case, each object within the archive is processed using the op-
+ tions supplied.
+
+OPTIONS
+ The following options are supported:
+
+ -d Display CTF data definitions.
+
+
+ -f Display CTF function definitions.
+
+
+ -h Display contents of CTF header.
+
+
+ -l Display CTF label definitions.
+
+
+ -s Display CTF string table.
+
+
+ -S Display CTF statistics.
+
+
+ -t Display CTF type definitions.
+
+
+ -u ctffile Copy the uncompressed CTF data to the file given by ctf-
+ file.
+
+
+OPERANDS
+ The following operands are supported.
+
+ file The file for which the CTF data symbolically displayed.
+
+
+EXIT STATUS
+ The following exit values are returned:
+
+ 0 Successful completion.
+
+
+ > 0 An error occurred.
+
+
+ATTRIBUTES
+ See attributes(7) for descriptions of the following attributes:
+
+ +------------------------------+-----------------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------------+
+ | Availability |developer/base-developer-utilities |
+ +------------------------------+-----------------------------------+
+ | Interface Stability |Committed |
+ +------------------------------+-----------------------------------+
+
+
+HISTORY
+ The CTF utilities, including ctfdump, have been used in the construc-
+ tion of Solaris since Sun Solaris 9. They were added as system utili-
+ ties in Oracle Solaris 11.4.72.
+
+SEE ALSO
+ ar(1), ctfconvert(1), ctfmerge(1)
+
+Oracle Solaris 11.4 10 July 2024 ctfdump(1)
diff -NurbBw 11.4.72/man1/ctfmerge.1 11.4.75/man1/ctfmerge.1
--- 11.4.72/man1/ctfmerge.1 1969-12-31 16:00:00.000000000 -0800
+++ 11.4.75/man1/ctfmerge.1 2024-11-22 11:52:06.846918180 -0800
@@ -0,0 +1,280 @@
+ctfmerge(1) User Commands ctfmerge(1)
+
+NAME
+ ctfmerge - merge multiple input CTF
+
+SYNOPSIS
+ ctfmerge [-irsSv] [-a | -t] [-l label] [-L label] -o outfile file...
+
+
+ ctfmerge [-irsSv] [-a | -t] [-l label] [-L labelenv] -o outfile
+ -d uniqfile [-D uniqlabel] file...
+
+
+ ctfmerge [-irsSv] [-a | -t] [-l label] [-L labelenv] -o outfile
+ -w withfile file...
+
+
+ ctfmerge [-rS] -c srcfile destfile
+
+DESCRIPTION
+ The ctfmerge utility reads CTF (Compact C Type Format) data from input
+ ELF object files, merges that data into a single CTF section named
+ .SUNW_ctf, and adds that section to the output file. The resulting CTF
+ data is used by debuggers and other observability tools.
+
+
+ ctfmerge is typically used in conjunction with ctfconvert. The ctfcon-
+ vert utility is used to add CTF data to ELF objects produced by compil-
+ ers and assemblers. After those objects are linked into a final object,
+ the ctfmerge utility is applied to the final object to augment it with
+ the merged CTF data from all the input objects.
+
+
+ The ctfmerge -a option can be used to simplify this process by elimi-
+ nating the need to use ctfconvert. When the -a option is specified,
+ ctfmerge runs the convert process on each input object internally in
+ order to obtain CTF data for each input. This can be simpler to use,
+ but at the cost of repeating the conversion operation for every input
+ object every time the final object is built.
+
+OPTIONS
+ The following options are supported:
+
+ -a
+
+ Automatically run the ctfconvert operation on any input object that
+ does not already have a .SUNW_ctf section, and merge the CTF data
+ produced into the output. Unlike using the ctfconvert command,
+ which adds CTF to the input object, the -a option does not modify
+ the input object.
+
+
+ -c srcfile destfile
+
+ Copy CTF data from srcfile into destfile.
+
+
+ -D uniqlabel
+
+ Uniquify against the label given by uniqlabel.
+
+
+ -d uniqfile
+
+ Uniquify against the file given by uniqfile.
+
+
+ -i
+
+ When the -a option is specified, the -i option causes ctfmerge to
+ silently ignore input object files built from languages other than
+ C. While CTF can be used with any language, the information it cap-
+ tures corresponds directly to C level language concepts, making CTF
+ particularly useful with code written in C.
+
+ In the same sense that the -a option corresponds to the operation
+ normally performed by the ctfconvert utility, the -i option corre-
+ sponds to specifying the -i option to ctfconvert.
+
+
+ -l label
+
+ Specifies a label to be associated with the generated CTF. Labels
+ are of use when employing uniquification to share definitions be-
+ tween parent and children objects as a space saving measure. See
+ NOTES.
+
+
+ -L labelenv
+
+ Specifies a label to be associated with the generated CTF. The
+ value of the environment variable specified by labelenv provides
+ the label to be used. If the environment variable is not defined,
+ no label is set, and the behavior is as if no label were specified.
+
+
+ -o outfile
+
+ By default, ctfmerge modifies the input object in place. When the
+ -o option is specified, the input object is not modified, and the
+ updated object contents are instead written to the file given by
+ outfile.
+
+
+ -r
+
+ Remove outfile on error. This facilitates the use of ctfmerge as
+ part of a series of commands executed by a makefile rule. The re-
+ moval of the file on error forces a subsequent execution of the
+ make utility to rerun the full set of commands required to build
+ the target, and ensures that CTF data is added.
+
+
+ -s
+
+ Associate the generated CTF section with the dynamic .dynsym symbol
+ table rather than the default .symtab.
+
+
+ -S
+
+ Strip compiler generated debug sections from the resulting object.
+
+
+ -t
+
+ Require each input file to have a CTF section.
+
+
+ -v
+
+ Enable verbose mode.
+
+
+ -w withfile
+
+ Additive merge against the file given by withfile. See NOTES.
+
+
+ -?
+ --help
+
+ Print usage message and immediately exit.
+
+
+
+OPERANDS
+ The following operands are supported.
+
+ file...
+
+ Input ELF objects from which merged CTF data will be constructed.
+
+
+NOTES
+ Labels
+ Labels can be associated with CTF data, using the -l, or -L options.
+ Labels can be useful for identification purposes, but are optional, un-
+ less uniquification is desired, in which case labels must be provided.
+
+ Uniquification
+ When multiple objects share common type definitions provided by a cen-
+ tral core object, the size of the overall CTF data can be greatly re-
+ duced through the process of uniquification. Uniquification removes de-
+ finitions found the core object from other objects, leaving those other
+ objects with only the additional definitions that are unique to them.
+ The core object is usually referred to as the parent, and the other ob-
+ ject as the child. A given child can only have one parent, and the par-
+ ent/child relationship is only one level deep, with no further descen-
+ dants. The CTF data in the parent and child objects to be uniquified
+ should define a common label, identifying them as sharing common type
+ definitions.
+
+
+ Uniquification is specified using the -d and -D options. Uniquification
+ is typically applied only to kernel modules. In the kernel environment,
+ the genunix kernel module is the parent, and the other kernel modules
+ delivered with the system are uniquified against it.
+
+ Additive Merges
+ There are cases where it is desired to issue a new version of an object
+ that has an existing uniquification relationship to another object. A
+ common example occurs when operating system kernel modules are patched.
+ For this to work smoothly, it is necessary to preserve all preexisting
+ CTF data, unchanged, while adding any necessary additional definitions
+ needed by the replacement object. This operation is known as an addi-
+ tive merge. An additive merge is done using the -w option. In this
+ case, a final uniquification is performed against the CTF data in the
+ previous version of the module. The result is the placement of new and
+ changed data after the existing data, thus preserving the existing type
+ definitions.
+
+ Deprecated Historical Options
+ The ctfmerge utility silently accepts -f and -g options for backward
+ compatibility with old makefiles. These options have no effect, and may
+ be removed.
+
+
+ Historical versions of ctfmerge required the -f option to be specified
+ in order to properly handle global symbols in the CTF data that subse-
+ quently have their scope reduced to local by the link-editor. Scope re-
+ duction can be requested from a mapfile, or through the use of link-ed-
+ itor command line options. ctfmerge now handles this case automati-
+ cally, and the use of -f is unnecessary. See ld(1), and Oracle Solaris
+ 11.4 Linkers and Libraries Guide.
+
+
+ Historically, the ctfmerge utility defaulted to the removal of stabs
+ and dwarf sections from the output object, and the -g option could be
+ specified to prevent their removal. In current implementations, the be-
+ havior has been reversed. Stabs and dwarf sections are retained by de-
+ fault, and the -S option is provided to remove them when needed. While
+ still accepted, the -g option no longer has any effect.
+
+EXAMPLES
+ Example 1 Use ctfconvert and ctfmerge to add CTF to a program
+
+
+
+ Add CTF to a program built from three source files.
+
+
+ % cc -g -c main.c a.c b.c
+ main.c:
+ a.c:
+ b.c:
+ % ctfconvert main.o
+ % ctfconvert a.o
+ % ctfconvert b.o
+ % cc -o prog main.o a.o b.o
+ % ctfmerge -o prog main.o a.o b.o
+
+
+ Example 2 Use ctfmerge -a to add CTF to a program
+
+
+
+ Repeat the previous example, using the -a option to eliminate the need
+ to run ctfconvert on each individual input object.
+
+
+ % cc -g -c main.c a.c b.c
+ main.c:
+ a.c:
+ b.c:
+ % cc -o prog main.o a.o b.o
+ % ctfmerge -a -o prog main.o a.o b.o
+
+
+EXIT STATUS
+ The following exit values are returned:
+
+ 0 Successful completion.
+
+
+ > 0 An error occurred.
+
+
+ATTRIBUTES
+ See attributes(7) for descriptions of the following attributes:
+
+ +------------------------------+-----------------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------------+
+ | Availability |developer/base-developer-utilities |
+ +------------------------------+-----------------------------------+
+ | Interface Stability |Committed |
+ +------------------------------+-----------------------------------+
+
+
+HISTORY
+ The CTF utilities, including ctfmerge, have been used in the construc-
+ tion of Solaris since Sun Solaris 9. They were added as system utili-
+ ties in Oracle Solaris 11.4.72.
+
+SEE ALSO
+ ctfconvert(1), ctfdump(1), ld(1), and Oracle Solaris 11.4 Linkers and
+ Libraries Guide
+
+Oracle Solaris 11.4 6 August 2024 ctfmerge(1)
diff -NurbBw 11.4.72/man1/elfdump.1 11.4.75/man1/elfdump.1
--- 11.4.72/man1/elfdump.1 2024-11-22 11:50:40.354199871 -0800
+++ 11.4.75/man1/elfdump.1 2024-11-22 11:52:06.892550444 -0800
@@ -535,4 +535,36 @@
this information. Section names are augmented with the name of the ob-
ject to which they apply.
-Oracle Solaris 11.4 29 February 2024 elfdump(1)
+HISTORY
+ The -L option was added in Oracle Solaris 11.4.72.
+
+
+ The -?, --help, -V, and --version options were added in Oracle Solaris
+ 11.4.0.
+
+
+ The -F option was added in Oracle Solaris 11.2.0.
+
+
+ The -I, -O, -P, -S, and -T options were added in Solaris 10 8/11 (Up-
+ date 10).
+
+
+ The -u option was added in Solaris 10 3/05.
+
+
+ The -H and -l options were added in Solaris 9 9/04 (Update 7).
+
+
+ The -g option was added in Solaris 9.
+
+
+ The -C option was added in Solaris 8 7/01 (Update 5).
+
+
+ The -k option was added in Solaris 8.
+
+
+ The elfdump command was introduced in Solaris 7.
+
+Oracle Solaris 11.4 13 Sep 2024 elfdump(1)
diff -NurbBw 11.4.72/man1/ld.1 11.4.75/man1/ld.1
--- 11.4.72/man1/ld.1 2024-11-22 11:50:40.453224975 -0800
+++ 11.4.75/man1/ld.1 2024-11-22 11:52:06.976572505 -0800
@@ -806,9 +806,9 @@
Compress sections commonly used to contain debugging data. De-
bug sections are identified by having a .debug*, .line, .stab*,
.SUNW_ctf, or .zdebug* section name. These sections are also
- identified by having an SHT_PROGBITS, SHT_SUNW_DEBUG, or
- SHT_SUNW_DEBUGSTR section type. This class also encapsulates
- the compcom class.
+ identified by having a section type of SHT_PROGBITS,
+ SHT_SUNW_DEBUG, or SHT_SUNW_DEBUGSTR. This class also encapsu-
+ lates the compcom class.
shstrtab
@@ -1209,6 +1209,15 @@
be disabled with -z guidance=nomapfile-symbol-match.
+ Mapfile Capability Name
+
+ To allow debuggers such as mdb(1) to operate with the resulting
+ object, the name specified for mapfile CAPABILITY directives
+ should avoid characters that may be interpreted by debuggers as
+ operators. This guidance can be disabled with -z guid-
+ ance=nomapfile-capid.
+
+
Library Search Path
Inappropriate dependencies that are encountered by the link-ed-
@@ -1504,13 +1513,20 @@
tified by having a .compcom section name.
+ ctf
+
+ Strip CTF (Compact C Type Format) sections. These sections are
+ identified by having a .SUNW_ctf section name, and also by hav-
+ ing a SHT_SUNW_ctf section type.
+
+
debug
Strip sections commonly used to contain debugging data. These
sections are identified by having a .line, .stab*, .debug*, or
.zdebug* section name. These sections are also identified by
- having a SHT_SUNW_DEBUG* section type. This class also encapsu-
- lates the compcom class.
+ having a section type of SHT_SUNW_DEBUG or SHT_SUNW_DEBUGSTR.
+ This class also encapsulates the compcom class.
exclude
@@ -1579,8 +1595,8 @@
Strip any non-allocatable symbol table, providing the output
file is not a relocatable object. These sections are identified
by having a SHT_SYMTAB section type. This class encapsulates
- the sort_sym classes. Any associated string table or symbol
- sort sections are also removed.
+ the sort_sym classes. Any associated string table, symbol sort
+ sections, or CTF section are also removed.
@@ -2450,4 +2466,4 @@
hard links to linker output files should explicitly remove and relink
the other file names.
-Oracle Solaris 11.4 2 December 2021 ld(1)
+Oracle Solaris 11.4 9 July 2024 ld(1)
diff -NurbBw 11.4.72/man1/mailx.1 11.4.75/man1/mailx.1
--- 11.4.72/man1/mailx.1 2024-11-22 11:50:40.511202282 -0800
+++ 11.4.75/man1/mailx.1 2024-11-22 11:52:07.033508199 -0800
@@ -19,6 +19,12 @@
ronment for sending and receiving mail messages electronically.
+ Note that mail and mailx are antiquated tools that support only basic
+ e-mail messaging. For more modern features, such as MIME support, take
+ a look at other available Mail User Agents such as mutt(1). mutt is
+ provide in package mail/mutt.
+
+
When reading mail, the mail utilities provide commands to facilitate
saving, deleting, and responding to messages. When sending mail, the
mail utilities allow editing, reviewing and other modification of the
@@ -1642,9 +1648,9 @@
SEE ALSO
- echo(1), ed(1), ex(1), fmt(1), ls(1), mail(1), more(1), pg(1), sh(1),
- vacation(1), vi(1), aliases(5), passwd(5), attributes(7), environ(7),
- standards(7), newaliases(8), sendmail(8)
+ echo(1), ed(1), ex(1), fmt(1), ls(1), mail(1), more(1), mutt(1), pg(1),
+ sh(1), vacation(1), vi(1), aliases(5), passwd(5), attributes(7), envi-
+ ron(7), standards(7), newaliases(8), sendmail(8)
NOTES
mailx only supports reading mail from local files, not IMAP or POP
@@ -1672,4 +1678,4 @@
ents, while the format for an alias in either the .forward or
/etc/aliases is a comma-separated list.
-Oracle Solaris 11.4 29 Nov 2022 mailx(1)
+Oracle Solaris 11.4 12 Jul 2024 mailx(1)
diff -NurbBw 11.4.72/man1/mdb.1 11.4.75/man1/mdb.1
--- 11.4.72/man1/mdb.1 2024-11-22 11:50:40.638650594 -0800
+++ 11.4.75/man1/mdb.1 2024-11-22 11:52:07.172918963 -0800
@@ -692,17 +692,55 @@
dress, or an address to the nearest symbol.
- As targets contain multiple symbol tables, and each symbol table can
- include symbols from multiple object files, different symbols with the
- same name can exist. mdb uses the backquote (`) character as a symbol
- name scoping operator to allow the programmer to obtain the value of
- the desired symbol in this situation. The programmer can specify the
- scope used to resolve a symbol name as either: object`name, or
- file`name, or object`file`name. The object identifier refers to the
- name of a load object. The file identifier refers to the basename of a
- source file that has a symbol of type STT_FILE in the specified ob-
- ject's symbol table. The object identifier's interpretation depends on
- the target type.
+ In some circumstances (file scope declarations, capability symbols, ELF
+ filter symbols, ... ), a given name may match more than one symbol
+ within the target. In such cases, the mdb backquote (`) symbol name
+ scoping operator can be used to unambiguously specify a specific de-
+ sired symbol. The user can specify the scope as one of: object`name,
+ object`file`name, or object`file`index`name. The object identifier
+ refers to the name of a load object. The file identifier refers to the
+ basename of the source file that defined the symbol. The index identi-
+ fier is a unique number assigned by mdb when object and file are not
+ sufficient to uniquely identify a symbol. When mdb encounters an am-
+ biguous name, it lists all the possibilities, using this symbol scoping
+ syntax. The user can then use that list to refine their request.
+
+
+ If the option symname_index is not set to off and a symbol name does
+ not uniquely identify a symbol, mdb will report the uniquely qualified
+ names and values of all the symbols that match, the user can then pick
+ the one they want. The user can choose to have mdb ignore modules when
+ checking for ambiguous symbol names by adding them to the search_de-
+ fer_mods list.
+
+
+ When capability symbols are present, a reference to a generic capabil-
+ ity symbol is ambiguous, as it can be a reference to the actual generic
+ function, or to any of the associated capability variants. For example:
+
+
+ bike> memcpy::dis
+ mdb: memcpy: not a unique symbol name
+ mdb: libc.so.1``memcpy : 0x7fe6efb410e0
+ mdb: libc.so.1`memcpy%avx2 : 0x7fe6efca9680
+ bike>
+
+ If given an unqualified capability symbol the ::bp dcmd will internally
+ set break points on all the symbols. For example:
+
+
+ bike> memcpy::bp
+ bike> <MDB_LAST_EVENT::events
+ ID S TAS HT LM Description Action
+ ----- - --- -- -- ------------------------------------------------- ------
+ [ 13] - --- 0 0 stop at libc.so.1``memcpy, libc.so.1`_memcpy%avx2 -
+ bike>
+
+
+
+
+ For details of capability symbols see the Oracle Solaris 11.4 Linkers
+ and Libraries Guide.
The mdb kernel target expects object to specify the basename of a
@@ -2273,7 +2311,10 @@
Description
A description of the type of software event that is matched by
- the given specifier.
+ the given specifier. For break points on capability symbols all
+ the symbols are listed, if the target program is stopped on one
+ of the symbols then the symbol that is stopped on is shown in
+ angle brackets < >.
Action
@@ -2975,7 +3016,8 @@
- [ address ] ::nm [ -DPdghnopuvx ] [ -t types ] [ -f format ] [ object ]
+ [ address ] ::nm [ -DPTUdghnopuvx ] [ +/-S ] [ -N names ] [ -s keys ] [
+ -t types ] [ -f format ] [ object ]
Print the symbol tables associated with the current target. If an
optional address preceding the dcmd is specified, only the symbol
@@ -2987,12 +3029,39 @@
-D
- Prints .dynsym (dynamic symbol table) instead of .symtab.
+ Prints .dynsym dynamic symbol
+
+
+ -N name[,name ... ]
+
+ Only print symbols listed
-P
- Prints the private symbol table instead of .symtab.
+ Prints the private symbol
+
+
+ -S
+
+ When using -U compare [value,value+size) and only display if
+ they are identical
+
+
+ -T
+
+ Prints .symtab symbol table
+
+
+ +S
+
+ When using -U compare [value,value+size) and only display if
+ they are not identical
+
+
+ -U
+
+ Only print symbols that have names that are not unique
-d
@@ -3010,11 +3079,6 @@
Suppresses the header line.
- -n
-
- Sorts symbols by name.
-
-
-o
Prints value and size fields in octal.
@@ -3027,19 +3091,51 @@
quently read into the debugger with $<.
- -u
+ -s key[,key ... ]
- Prints only undefined symbols.
+ Sort using the comma separated list of keys. The valid key ar-
+ gument strings are:
- -v
- Sorts symbols by value.
+ bind binding
+
+
+ ctype C type for symbol (if known)
+
+ data The contents of a symbol, reading from the address
+ given by the value for a length defined by the size
- -x
- Prints value and size fields in hexadecimal.
+ file file that defines the local symbol
+
+
+ name symbol name
+
+
+ obj object which defines symbol
+
+
+ type symbol type
+
+
+ size size in bytes
+
+
+ uqn Uniquely qualified name
+
+
+ val symbol value
+
+
+ If any key is prefixed with (^) the direction of the sort for
+ that key is reversed
+
+
+ -u
+
+ Prints only undefined symbols.
-t type[,type ... ]
@@ -3080,36 +3176,59 @@
argument strings are:
- ndx symbol table index
+ all display all categories of information contained in
+ this list
- val symbol value
+ bind binding
- size size in bytes
+ ctfid ctf id
- type symbol type
+ ctype C type for symbol (if known)
- bind binding
+ default the default fields (val, size, type, bind, other,
+ shndx, name)
- oth other
+ file file that defines the local symbol
- shndx section index
+ filebase basename of file that defines the local symbol
name symbol name
- ctype C type for symbol (if known)
+ ndx symbol table index
obj object which defines symbol
+ objbase basename of the object which defines symbol
+
+
+ oth other
+
+
+ size size in bytes
+
+
+ shndx section index
+
+
+ type symbol type
+
+
+ uqn Uniquely qualified name
+
+
+ val symbol value
+
+
@@ -4731,6 +4850,20 @@
file when mdb exits.
+ search_defer_mods
+
+ A colon separated list of modules to defer searching when per-
+ forming a symbol name look up. Symbols from these modules are
+ only used if no non-zero sized symbols are found in other mod-
+ ules with the name given. When updating this option, if the
+ list begins with +, the entries are added to the existing list.
+ If the list begins with -, the entries are removed from the
+ list, otherwise the new list replaces the existing list.
+
+ When debugging user applications ld.so.1 is added to this list
+ by default.
+
+
showlmid
mdb provides support for symbol naming and identification in
@@ -4747,6 +4880,30 @@
$m, and ::objects.
+ symname_index
+
+ Control checking for ambiguous symbol names.
+
+ ambiguous Only ambiguous symbols are indexed. This uses less
+ memory but means that the fully qualified ob-
+ ject`file`name naming can only be used for symbol
+ names that are ambiguous. This is the default in
+ kmdb(4D).
+
+
+ full A full index is maintained. This is the default in
+ mdb.
+
+
+ off No index is maintained and do no ambiguous symbol
+ name checking is done. This uses no memory and has
+ no performance impact. If you know you do not have
+ ambiguous symbol names in your debugging and are
+ using conditional breakpoints this reduces the
+ performance impact of mdb.
+
+
+
zero_alloc
Allow mdb modules to have memory allocations of zero size.
@@ -5205,4 +5362,4 @@
provides source code for an example module in the directory
/usr/demo/mdb.
-Oracle Solaris 11.4 14 March 2024 mdb(1)
+Oracle Solaris 11.4 29 July 2024 mdb(1)
diff -NurbBw 11.4.72/man1/pgrep.1 11.4.75/man1/pgrep.1
--- 11.4.72/man1/pgrep.1 2024-11-22 11:50:40.671195278 -0800
+++ 11.4.75/man1/pgrep.1 2024-11-22 11:52:07.207171658 -0800
@@ -4,18 +4,18 @@
pgrep, pkill - find or signal processes by name and other attributes
SYNOPSIS
- pgrep [-flvx] [-n | -o] [-d delim] [-P ppidlist]
+ pgrep [-flvxZ] [-n | -o] [-d delim] [-P ppidlist]
[-g pgrplist] [-s sidlist] [-u euidlist] [-U uidlist]
[-G gidlist] [-J projidlist] [-t termlist]
[-T taskidlist] [-c ctidlist] [-z zoneidlist]
- [pattern]
+ [-r pidlist] [pattern]
- pkill [-signal] [-fvx] [-n | -o] [-P ppidlist]
+ pkill [-signal] [-fvxZ] [-n | -o] [-P ppidlist]
[-g pgrplist] [-s sidlist] [-u euidlist] [-U uidlist]
[-G gidlist] [-J projidlist] [-t termlist]
[-T taskidlist] [-c ctidlist] [-z zoneidlist]
- [pattern]
+ [-r pidlist] [pattern]
DESCRIPTION
The pgrep utility examines the active processes on the system and re-
@@ -107,6 +107,10 @@
the given list.
+ -r pidlist Matches only processes whose process ID is in the
+ process tree rooted in the specified processes.
+
+
-s sidlist Matches only processes whose process session ID is in
in the given list. If ID 0 is included in the list,
this is interpreted as the session ID of the pgrep or
@@ -156,6 +160,11 @@
{PRIV_PROC_ZONE} privilege (see privileges(7)).
+ -Z Matches only processes whose zone ID matches the cur-
+ rent process' zone ID. This option is a no-op when not
+ executed in the global zone.
+
+
-signal Specifies the signal to send to each matched process.
If no signal is specified, SIGTERM is sent by default.
The value of signal can be one of the symbolic names
@@ -215,6 +224,12 @@
/proc/nnnnn/psinfo Process information files
+ /proc/nnnnn/cmdline Process full command line
+
+
+ /proc/nnnnn/execname Process full executable name
+
+
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -231,7 +246,7 @@
NOTES
The pgrep and pkill utilities match the ERE pattern against fields de-
- fined within the proc(4) structure. The two elements used are as fol-
+ fined within the proc(5) structure. The two elements used are as fol-
lows:
pr_fname Name of the executed file
@@ -252,4 +267,24 @@
The current pgrep or pkill process will never consider itself a poten-
tial match.
-Oracle Solaris 11.4 24 Mar 2020 pgrep(1)
+HISTORY
+ The -r and -Z options were added to pgrep and pkill in Oracle Solaris
+ 11.4.75.
+
+
+ The -V opton was removed from pgrep and pkill in Oracle Solaris 11.0.0.
+
+
+ The -c and -z options were added to pgrep and pkill in Solaris 10 3/05.
+
+
+ The -o option was added to pgrep and pkill in Solaris 9.
+
+
+ The -J, -T, and -V options were added to pgrep and pkill in Solaris 8
+ 6/00 (Update 1).
+
+
+ The pgrep and pkill commands were introduced in Solaris 7.
+
+Oracle Solaris 11.4 13 Sep 2024 pgrep(1)
diff -NurbBw 11.4.72/man1/ptree.1 11.4.75/man1/ptree.1
--- 11.4.72/man1/ptree.1 2024-11-22 11:50:40.703566750 -0800
+++ 11.4.75/man1/ptree.1 2024-11-22 11:52:07.236951973 -0800
@@ -133,6 +133,9 @@
proc(5), process(5), attributes(7), zones(7), prstat(8)
HISTORY
+ Support for the -g option was added in Oracle Solaris 11.4.66.
+
+
Support for the -? and --help options was added in Oracle Solaris
11.4.42.
@@ -148,4 +151,4 @@
The ptree command, including support for the -a option, was introduced
in Solaris 2.5.
-Oracle Solaris 11.4 29 Nov 2022 ptree(1)
+Oracle Solaris 11.4 13 Sep 2024 ptree(1)
diff -NurbBw 11.4.72/man1/strip.1 11.4.75/man1/strip.1
--- 11.4.72/man1/strip.1 2024-11-22 11:50:40.735580740 -0800
+++ 11.4.75/man1/strip.1 2024-11-22 11:52:07.270667723 -0800
@@ -51,8 +51,8 @@
class should not be removed. This definition can be useful to pre-
vent a class from including another normally encapsulated class.
For example, while the nonalloc class encapsulates all non-alloca-
- ble sections, -z strip-class=nonalloc,!note removes all non-allo-
- catable sections except for the note section.
+ ble sections, -c nonalloc,!note removes all non-allocatable sec-
+ tions except for the note section.
Stripped sections are completely removed from the output object.
@@ -88,12 +88,19 @@
tified by having a .compcom section name.
+ ctf
+
+ Strip CTF (Compact C Type Format) sections. These sections are
+ identified by having a .SUNW_ctf section name, and also by hav-
+ ing a SHT_SUNW_ctf section type.
+
+
debug
Strip sections commonly used to contain debugging data. These
- sections are identified by having a .debug*, .stab*, .SUNW_ctf,
- or .zdebug* section name. These sections are also identified by
- having a SHT_SUNW_DEBUG or SHT_SUNW_DEBUGSTR section type. This
+ sections are identified by having a .debug*, .stab*, or .zde-
+ bug* section name. These sections are also identified by having
+ a section type of SHT_SUNW_DEBUG or SHT_SUNW_DEBUGSTR. This
class also encapsulates the compcom, and line classes.
@@ -153,8 +160,8 @@
Strip any non-allocatable symbol table, providing the file is
not a relocatable object. These sections are identified by hav-
ing a SHT_SYMTAB section type. This class also encapsulates the
- sort_sym classes. Any associated string table or symbol sort
- sections are also removed.
+ sort_sym classes. Any associated string table, symbol sort sec-
+ tions, or CTF section are also removed.
@@ -240,4 +247,4 @@
post process objects is more efficient, but otherwise equivalent. See
ld(1).
-Oracle Solaris 11.4 2 December 2021 strip(1)
+Oracle Solaris 11.4 28 May 2024 strip(1)
diff -NurbBw 11.4.72/man3c/clock_getcpuclockid.3c 11.4.75/man3c/clock_getcpuclockid.3c
--- 11.4.72/man3c/clock_getcpuclockid.3c 2024-11-22 11:50:40.764608191 -0800
+++ 11.4.75/man3c/clock_getcpuclockid.3c 2024-11-22 11:52:07.299714950 -0800
@@ -53,4 +53,7 @@
SEE ALSO
clock_getres(3C), timer_create(3C), attributes(7), standards(7)
-Oracle Solaris 11.4 17 Jan 2019 clock_getcpuclockid(3C)
+HISTORY
+ The clock_getcpuclockid() function was added in Oracle Solaris 11.4.7.
+
+Oracle Solaris 11.4 13 Sep 2024 clock_getcpuclockid(3C)
diff -NurbBw 11.4.72/man3c/closefrom.3c 11.4.75/man3c/closefrom.3c
--- 11.4.72/man3c/closefrom.3c 2024-11-22 11:50:40.795962932 -0800
+++ 11.4.75/man3c/closefrom.3c 2024-11-22 11:52:07.329750810 -0800
@@ -120,4 +120,16 @@
close(2), fcntl(2), getrlimit(2), posix_spawn_file_actions_addclose-
from_np(3C), proc(5), attributes(7)
-Oracle Solaris 11.4 9 May 2024 closefrom(3C)
+HISTORY
+ A function prototype for closefrom() was added to <unistd.h> in Oracle
+ Solaris 11.4.72.
+
+
+ The closefrom() function was made Async-Signal-Safe in Oracle Solaris
+ 11.3.31. Prior to that it had an MT-Level of Unsafe.
+
+
+ The closefrom() function and fdwalk() functions were introduced in So-
+ laris 9, with function prototypes in <stdlib.h> for both.
+
+Oracle Solaris 11.4 13 Sep 2024 closefrom(3C)
diff -NurbBw 11.4.72/man3c/fopen.3c 11.4.75/man3c/fopen.3c
--- 11.4.72/man3c/fopen.3c 2024-11-22 11:50:40.829007799 -0800
+++ 11.4.75/man3c/fopen.3c 2024-11-22 11:52:07.362841742 -0800
@@ -272,8 +272,24 @@
the runtime_constraint_handler(3C) man page.
SEE ALSO
- fclose(3C), fdopen(3C), fflush(3C), freopen(3C), freopen_s(3C), fset-
- pos(3C), rewind(3C), attributes(7), lf64(7), standards(7), runtime_con-
+ open(2), fclose(3C), fdopen(3C), fflush(3C), freopen(3C), fsetpos(3C),
+ rewind(3C), attributes(7), lf64(7), standards(7), runtime_con-
straint_handler(3C)
-Oracle Solaris 11.4 11 June 2020 fopen(3C)
+HISTORY
+ Support for the "f" (O_CLOFORK) character in the mode argument was
+ added to Oracle Solaris in the 11.4.24 release.
+
+
+ Support for the "e" (O_CLOEXEC) and "x" (O_EXCL) characters in the mode
+ argument was added to Oracle Solaris in the 11.4.0 release.
+
+
+ The fopen_s() function was added to Oracle Solaris in the 11.4.0 re-
+ lease.
+
+
+ The fopen() function has been included in all Sun and Oracle releases
+ of Solaris.
+
+Oracle Solaris 11.4 13 Sep 2024 fopen(3C)
diff -NurbBw 11.4.72/man3c/popen.3c 11.4.75/man3c/popen.3c
--- 11.4.72/man3c/popen.3c 2024-11-22 11:50:40.860363254 -0800
+++ 11.4.75/man3c/popen.3c 2024-11-22 11:52:07.393823054 -0800
@@ -18,7 +18,7 @@
line. The mode argument is an I/O mode, either starting with r for
reading or w for writing. The value returned is a stream pointer such
that one can write to the standard input of the command, if the I/O
- mode starts with w, by writing to the file stream (see intro(3)); and
+ mode starts with w, by writing to the file stream (see Intro(3)); and
one can read from the standard output of the command, if the I/O mode
starts with r, by reading from the file stream. Because open files are
shared, a type r command may be used as an input filter and a type w as
@@ -170,4 +170,16 @@
system(3C), wait(3C), waitpid(3C), wait.h(3HEAD), attributes(7), stan-
dards(7)
-Oracle Solaris 11.4 08 May 2020 popen(3C)
+HISTORY
+ Support for the "f" (FD_CLOFORK) character in the mode argument was
+ added to Oracle Solaris in the 11.4.24 release.
+
+
+ Support for the "e" (FD_CLOEXEC) character in the mode argument was
+ added to Oracle Solaris in the 11.4.0 release.
+
+
+ The popen() and pclose() functions have been included in all Sun and
+ Oracle releases of Solaris.
+
+Oracle Solaris 11.4 13 Sep 2024 popen(3C)
diff -NurbBw 11.4.72/man3c/posix_spawn_file_actions_addchdir_np.3c 11.4.75/man3c/posix_spawn_file_actions_addchdir_np.3c
--- 11.4.72/man3c/posix_spawn_file_actions_addchdir_np.3c 2024-11-22 11:50:40.893342830 -0800
+++ 11.4.75/man3c/posix_spawn_file_actions_addchdir_np.3c 2024-11-22 11:52:07.423647493 -0800
@@ -86,4 +86,13 @@
close(3C), posix_spawn_file_actions_addopen(3C), posix_spawn_file_ac-
tions_destroy(3C), spawn.h(3HEAD), attributes(7), standards(7)
-Oracle Solaris 11.4 24 Jul 2020 posix_sp...chdir_np(3C)
+HISTORY
+ The posix_spawn_file_actions_addchdir() and
+ posix_spawn_file_actions_addfchdir() functions were added in Oracle So-
+ laris 11.4.27.
+
+
+ The posix_spawn_file_actions_addchdir_np() function was added in Oracle
+ Solaris 11.3.0.
+
+Oracle Solaris 11.4 13 Sep 2024 posix_sp...chdir_np(3C)
diff -NurbBw 11.4.72/man3c/pthread_getcpuclockid.3c 11.4.75/man3c/pthread_getcpuclockid.3c
--- 11.4.72/man3c/pthread_getcpuclockid.3c 2024-11-22 11:50:40.926598984 -0800
+++ 11.4.75/man3c/pthread_getcpuclockid.3c 2024-11-22 11:52:07.452378011 -0800
@@ -42,4 +42,8 @@
clock_getcpuclockid(3C), clock_getres(3C), timer_create(3C), attrib-
utes(7), standards(7)
-Oracle Solaris 11.4 17 Jan 2019 pthread_...puclockid(3C)
+HISTORY
+ The pthread_getcpuclockid() function was added in Oracle Solaris
+ 11.4.7.
+
+Oracle Solaris 11.4 13 Sep 2024 pthread_...puclockid(3C)
diff -NurbBw 11.4.72/man3c/qsort.3c 11.4.75/man3c/qsort.3c
--- 11.4.72/man3c/qsort.3c 2024-11-22 11:50:40.958415592 -0800
+++ 11.4.75/man3c/qsort.3c 2024-11-22 11:52:07.483067385 -0800
@@ -1,8 +1,7 @@
qsort(3C) Standard C Library Functions qsort(3C)
NAME
- qsort, qsort_r - quick sort
- qsort_s - quick sort with additional safety checks
+ qsort, qsort_r, qsort_s - quick sort
SYNOPSIS
#include <stdlib.h>
@@ -146,8 +145,9 @@
the runtime_constraint_handler(3C) man page.
SEE ALSO
- sort(1), bsearch(3C), bsearch_s(3C), lsearch(3C), string(3C), attrib-
- utes(7), standards(7), runtime_constraint_handler(3C)
+ sort(1), bsearch(3C), bsearch_s(3C), lsearch(3C), strcmp(3C),
+ strxfrm(3C), attributes(7), standards(7),
+ runtime_constraint_handler(3C)
NOTES
The comparison function need not compare every byte, so arbitrary data
@@ -165,4 +165,14 @@
data, avoiding the need for global data, and is preferred in such situ-
ations.
-Oracle Solaris 11.4 23 May 2019 qsort(3C)
+HISTORY
+ The qsort_r() function was added in Oracle Solaris 11.4.12.
+
+
+ The qsort_s() function was added in Oracle Solaris 11.4.0.
+
+
+ The qsort() function has been included in all Sun and Oracle releases
+ of Solaris.
+
+Oracle Solaris 11.4 13 Sep 2024 qsort(3C)
diff -NurbBw 11.4.72/man3c/recv.3c 11.4.75/man3c/recv.3c
--- 11.4.72/man3c/recv.3c 2024-11-22 11:50:40.989576528 -0800
+++ 11.4.75/man3c/recv.3c 2024-11-22 11:52:07.516058699 -0800
@@ -199,4 +199,21 @@
HISTORY
These functions have been present since the initial release of Solaris.
-Oracle Solaris 11.4 2 Feb 2021 recv(3C)
+
+ Support for the following flags is available in Oracle Solaris starting
+ with the listed release:
+
+ +--------------------------------------------------+---------+
+ | FLAG |RELEASE |
+ +--------------------------------------------------+---------+
+ | MSG_CMSG_CLOFORK |11.4.24 |
+ +--------------------------------------------------+---------+
+ | MSG_CMSG_CLOEXEC |11.4.17 |
+ +--------------------------------------------------+---------+
+ | MSG_WAITALL, MSG_DONTWAIT |2.6 |
+ +--------------------------------------------------+---------+
+ | MSG_OOB, MSG_PEEK |1.0 |
+ +--------------------------------------------------+---------+
+
+
+Oracle Solaris 11.4 13 Sep 2024 recv(3C)
diff -NurbBw 11.4.72/man3head/ar.h.3head 11.4.75/man3head/ar.h.3head
--- 11.4.72/man3head/ar.h.3head 2024-11-22 11:50:41.023239645 -0800
+++ 11.4.75/man3head/ar.h.3head 2024-11-22 11:52:07.549111839 -0800
@@ -7,9 +7,10 @@
#include <ar.h>
DESCRIPTION
- The archive command ar is used to combine several files into one.
- Archives are used mainly as libraries to be searched by the link editor
- ld.
+ The archive command ar(1) is used to combine several files into one
+ archive file. Archives are used mainly as static libraries to be
+ searched by the link editor ld(1). The <ar.h> header file defines the
+ structure of these archives.
Each archive begins with the archive magic string.
@@ -54,9 +53,9 @@
The ar_date field is the modification date of the file at the time of
- its insertion into the archive. Common format archives can be moved
- from system to system as long as the portable archive command ar is
- used.
+ its insertion into the archive, represented as the number of seconds
+ since 00:00:00 UTC, January 1, 1970. The 12 character length allows
+ dates up until the year 33658.
Each archive file member begins on an even byte boundary; a newline is
@@ -80,7 +79,7 @@
ber of symbols and offsets into the archive. The 32-bit format can be
used with archives smaller than 4GB, while the 64-bit format is re-
quired for larger archives. The ar command selects the symbol table
- format to used based on the size of the archive it is creating, and
+ format to be used based on the size of the archive it is creating, and
will use the smaller format when possible.
@@ -263,4 +255,21 @@
Any file with a group ID greater than 999999 is set to group ID "no-
body" (60001).
-Oracle Solaris 11.4 22 Jun 2010 ar.h(3HEAD)
+
+ Oracle Solaris uses the archive format from the SVR4 operating system,
+ which included the 32-bit symbol table format described above. The
+ 64-bit symbol table format is an extension to the original SVR4 format,
+ originally implemented in SGI Irix. Other systems may use their own
+ variations or extensions to the archive format. For transporting col-
+ lections of files to other systems, a more portable archive format is
+ recommended, such as tar(1) or pax(1).
+
+HISTORY
+ Support for the 64-bit symbol table was added in Solaris 10 8/11 (Up-
+ date 10) and Solaris 11.0.
+
+
+ The <ar.h> header file has been included in all Sun and Oracle releases
+ of Solaris.
+
+Oracle Solaris 11.4 30 Aug 2024 ar.h(3HEAD)
diff -NurbBw 11.4.72/man3head/archives.h.3head 11.4.75/man3head/archives.h.3head
--- 11.4.72/man3head/archives.h.3head 2024-11-22 11:50:41.053664858 -0800
+++ 11.4.75/man3head/archives.h.3head 2024-11-22 11:52:07.580362914 -0800
@@ -1,9 +1,15 @@
archives.h(3HEAD) Headers archives.h(3HEAD)
NAME
- archives.h, archives - device header
+ archives.h, archives - archive file formats header
DESCRIPTION
+ The <archives.h> header file provides defintions for several archive
+ file formats, including those used by cpio(1), tar(1), and volcopy(8).
+
+
+ Definitions provided in this header include:
+
/* Magic numbers */
#define CMN_ASC 0x070701 /* Cpio Magic Number for -c header */
#define CMN_BIN 070707 /* Cpio Magic Number for Binary header */
@@ -111,7 +124,7 @@
v_volume[VVOLLEN],
v_reels,
v_reel;
- long v_time,
+ int v_time,
v_length,
v_dens,
v_reelblks, /* u370 added field */
@@ -233,4 +246,14 @@
-Oracle Solaris 11.4 1 Aug 2011 archives.h(3HEAD)
+SEE ALSO
+ cpio(1), tar(1), cpio.h(3HEAD), tar.h(3HEAD), fsattr(7), volcopy(8).
+
+HISTORY
+ Support for extended file attributes was added to the <archives.h>
+ header file in Solaris 9.
+
+
+ The <archives.h> header file was added in the Solaris 2.0 release.
+
+Oracle Solaris 11.4 30 Aug 2024 archives.h(3HEAD)
diff -NurbBw 11.4.72/man3head/assert.h.3head 11.4.75/man3head/assert.h.3head
--- 11.4.72/man3head/assert.h.3head 2024-11-22 11:50:41.081333582 -0800
+++ 11.4.75/man3head/assert.h.3head 2024-11-22 11:52:07.609086461 -0800
@@ -19,14 +19,19 @@
Otherwise, the macro behaves as described in assert(3C).
- The assert() macro is redefined according to the current state of NDE-
- BUG each time <assert.h> is included.
+ The assert() macro is redefined according to the current state of
+ NDEBUG each time <assert.h> is included.
The assert() macro is implemented as a macro, not as a function. If the
macro definition is suppressed in order to access an actual function,
the behavior is undefined.
+
+ When compiling for the C11 or later versions of the ISO C standard,
+ <assert.h> also defines the static_assert() macro for making assertions
+ that are checked at compilation time instead of runtime.
+
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -42,4 +47,11 @@
SEE ALSO
assert(3C), attributes(7), standards(7)
-Oracle Solaris 11.4 10 Sep 2004 assert.h(3HEAD)
+HISTORY
+ The static_assert() macro was added in Oracle Solaris 11.4.
+
+
+ The <assert.h> header file, including the assert() macro, has been in-
+ cluded in all Sun and Oracle releases of Solaris.
+
+Oracle Solaris 11.4 30 Aug 2024 assert.h(3HEAD)
diff -NurbBw 11.4.72/man3head/fcntl.h.3head 11.4.75/man3head/fcntl.h.3head
--- 11.4.72/man3head/fcntl.h.3head 2024-11-22 11:50:41.116575911 -0800
+++ 11.4.75/man3head/fcntl.h.3head 2024-11-22 11:52:07.645524756 -0800
@@ -35,7 +35,7 @@
flag FD_CLOFORK set.
- F_DUP3FD Similar to F_DUP2FD but allows a fourth argument.
+ F_DUP3FD Similar to F_DUP2FD, but allows a fourth argument.
F_GETFD Get file descriptor flags.
@@ -50,6 +50,10 @@
F_SETFL Set file status flags.
+ F_GETXFL Get the file status flags, file access modes, and
+ file creation and assignment flags.
+
+
F_GETOWN Get process or process group ID to receive SIGURG
signals.
@@ -58,6 +62,15 @@
signals.
+ F_GETTPD Returns whether the file is owned by the Trusted
+ Path. For more information, see the tpd(7) man
+ page.
+
+
+ F_SETTPD Sets whether the file is owned by a process in the
+ Trusted Path Domain (TPD).
+
+
F_FREESP Free storage space associated with a section of the
ordinary file fildes.
@@ -285,9 +298,29 @@
O_DIRECTORY Fail if not a directory.
+ O_LARGEFILE If set in a 32-bit process, the offset maximum in the
+ open file description is the largest value that can be
+ represented correctly in an object of type off64_t. Has
+ no effect in a 64-bit process.
+
+
O_NOFOLLOW Do not follow symbolic links.
+ O_NOLINKS Fail if link count is greater than 1.
+
+
+ O_NOSTDFD Do not use STDIN_FILENO, STDOUT_FILENO, or STDERR_FILENO
+ for the new file descriptor.
+
+
+ O_TPDSAFE Allow opening a file for reading that is not MWAC-pro-
+ tected even if the process is part of the TPD.
+
+ Allow opening STREAM devices or FIFO special files when
+ the peer is not a TPD process.
+
+
The following constant is a value to be used for the flag passed to un-
linkat():
@@ -329,8 +362,9 @@
SEE ALSO
- creat(2), exec(2), fcntl(2), open(2), fdatasync(3C), fsync(3C), attrib-
- utes(7), fsattr(7), standards(7)
+ creat(2), exec(2), fcntl(2), open(2), fdatasync(3C), fsync(3C),
+ posix_fadvise(3C), posix_fallocate(3C), attributes(7), fsattr(7), stan-
+ dards(7), tpd(7)
NOTES
Data is successfully transferred for a write operation to a regular
@@ -377,4 +411,9 @@
to returning to the calling process.
-Oracle Solaris 11.4 22 Jan 2018 fcntl.h(3HEAD)
+HISTORY
+ The <fcntl.h> header has been included in all Sun and Oracle releases
+ of Solaris. See the manual pages for each function for the history of
+ when support for the function and each flag was added to Solaris.
+
+Oracle Solaris 11.4 30 Aug 2024 fcntl.h(3HEAD)
diff -NurbBw 11.4.72/man3head/fenv.h.3head 11.4.75/man3head/fenv.h.3head
--- 11.4.72/man3head/fenv.h.3head 2024-11-22 11:50:41.146943180 -0800
+++ 11.4.75/man3head/fenv.h.3head 2024-11-22 11:52:07.678846619 -0800
@@ -29,10 +29,10 @@
The <fenv.h> header defines the following constants if and only if the
implementation supports the floating-point exception by means of the
- floating-point functions feclearexcept(), fegetexceptflag(), feraiseex-
- cept(), fesetexceptflag(), and fetestexcept(). Each expands to an inte-
- ger constant expression with values such that bitwise-inclusive ORs of
- all combinations of the constants result in distinct values.
+ floating-point functions feclearexcept(), fegetexceptflag(),
+ feraiseexcept(), fesetexceptflag(), and fetestexcept(). Each expands to
+ an integer constant expression with values such that bitwise-inclusive
+ ORs of all combinations of the constants result in distinct values.
FE_DIVBYZERO
FE_INEXACT
@@ -166,9 +166,9 @@
SEE ALSO
- feraiseexcept(3M), feclearexcept(3M), fegetenv(3M), fegetexcept-
- flag(3M), fegetround(3M), feholdexcept(3M), fesetenv(3M), fesetexcept-
- flag(3M), fesetround(3M), fetestexcept(3M), feupdateenv(3M), attrib-
- utes(7), standards(7)
+ feraiseexcept(3M), feclearexcept(3M), fegetenv(3M),
+ fegetexceptflag(3M), fegetround(3M), feholdexcept(3M), fesetenv(3M),
+ fesetexceptflag(3M), fesetround(3M), fetestexcept(3M), feupdateenv(3M),
+ attributes(7), standards(7)
-Oracle Solaris 11.4 15 Dec 2003 fenv.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 fenv.h(3HEAD)
diff -NurbBw 11.4.72/man3head/float.h.3head 11.4.75/man3head/float.h.3head
--- 11.4.72/man3head/float.h.3head 2024-11-22 11:50:41.178207018 -0800
+++ 11.4.75/man3head/float.h.3head 2024-11-22 11:52:07.710941770 -0800
@@ -226,4 +226,4 @@
SEE ALSO
complex.h(3HEAD), math.h(3HEAD), attributes(7), standards(7)
-Oracle Solaris 11.4 17 Dec 2003 float.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 float.h(3HEAD)
diff -NurbBw 11.4.72/man3head/glob.h.3head 11.4.75/man3head/glob.h.3head
--- 11.4.72/man3head/glob.h.3head 2024-11-22 11:50:41.207178703 -0800
+++ 11.4.75/man3head/glob.h.3head 2024-11-22 11:52:07.742220815 -0800
@@ -8,7 +8,7 @@
DESCRIPTION
The <glob.h> header defines the structures and symbolic constants used
- by the glob(3C).
+ by the glob(3C) function.
The structure type glob_t contains the following members:
@@ -34,6 +34,11 @@
GLOB_ERR Cause glob() to return on error.
+ GLOB_LIMIT Limit total number of returned pathnames to 65536, and
+ limit number of system calls to prevent high CPU us-
+ age.
+
+
GLOB_MARK Each pathname that is a directory that matches pattern
has a slash appended.
@@ -80,4 +85,4 @@
SEE ALSO
glob(3C), attributes(7), standards(7)
-Oracle Solaris 11.4 10 Sep 2004 glob.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 glob.h(3HEAD)
diff -NurbBw 11.4.72/man3head/in.h.3head 11.4.75/man3head/in.h.3head
--- 11.4.72/man3head/in.h.3head 2024-11-22 11:50:41.254129770 -0800
+++ 11.4.75/man3head/in.h.3head 2024-11-22 11:52:07.774175433 -0800
@@ -7,14 +7,12 @@
#include <netinet/in.h>
DESCRIPTION
- The <netinet/in.h> header defines the following types through typedef:
+ The <netinet/in.h> header defines the following types:
in_port_t An unsigned integral type of exactly 16 bits.
- in_addr_t An unsigned integral type of exactly 32 bits. The
- <netinet/in.h> header defines the in_addr structure that
- includes the following member:
+ in_addr_t An unsigned integral type of exactly 32 bits.
@@ -25,6 +23,13 @@
+ The <netinet/in.h> header defines the in6_addr structure that includes
+ the following member:
+
+ uint8_t s6_addr[16]
+
+
+
The <netinet/in.h> header defines the type sa_family_t as described in
socket.h(3HEAD).
@@ -32,38 +37,51 @@
The <netinet/in.h> header defines the following macros for use as val-
ues of the level argument of getsockopt() and setsockopt():
- IPPROTO_IP Dummy for IP
+ IPPROTO_IP IPv4
+
+
+ IPPROTO_IPV6 IPv6
+
+ IPPROTO_ICMP Control message protocol for IPv4
- IPPROTO_ICMP Control message protocol
+
+ IPPROTO_ICMPV6 Control message protocol for IPv6
IPPROTO_TCP TCP
- IPPROTO_UDP User datagram protocol The <netinet/in.h> header
- defines the following macros for use as destination
- addresses for connect(), sendmsg(), and sendto():
+ IPPROTO_UDP User datagram protocol
+
+
+ IPPROTO_RAW Raw IP packets
+
+
+
+ The <netinet/in.h> header defines the following macro for use as a lo-
+ cal address for bind(3C):
+
+ INADDR_ANY IPv4 Local host address
- INADDR_ANY Local host address
+ The <netinet/in.h> header defines the following macro for use as a des-
+ tination address for connect(3C), sendmsg(3C), and sendto(3C):
- INADDR_BROADCAST Broadcast address
+ INADDR_BROADCAST IPv4 Broadcast address
- The <netinet/in.h> header defines the sockaddr_in structure that is
- used to store addresses for the Internet protocol family. Values of
- this type must be cast to struct sockaddr for use with the socket in-
- terfaces.
+ The <netinet/in.h> header defines the sockaddr_in and sockaddr_in6
+ structures that are used to store addresses for the IPv4 and IPv6 fami-
+ lies, respectively. Values of these types must be cast to
+ struct sockaddr for use with the socket interfaces.
Default
- For applications that do not require standard-conforming behavior
- (those that use the socket interfaces described in section (3SOCKET) of
- the reference manual; see intro(3) and standards(7)), the
- <netinet/in.h> header defines the sockaddr_in structure that includes
- the following members:
+ For applications that do not require standard-conforming behavior (see
+ standards(7)), the <netinet/in.h> header defines the sockaddr_in struc-
+ ture that includes the following members:
sa_family_t sin_family
in_port_t sin_port
@@ -72,10 +90,9 @@
Standard conforming
- For applications that require standard-conforming behavior (those that
- use the socket interfaces described in section (3XNET) of the reference
- manual; see intro(3) and standards(7)), the <netinet/in.h> header de-
- fines the sockaddr_in structure that includes the following members:
+ For applications that require standard-conforming behavior (see stan-
+ dards(7)), the <netinet/in.h> header defines the sockaddr_in structure
+ that includes the following members:
sa_family_t sin_family
in_port_t sin_port
@@ -96,7 +113,8 @@
SEE ALSO
- connect(3C), getsockopt(3C), sendmsg(3C), sendto(3C), setsockopt(3C),
- socket.h(3HEAD), intro(3), standards(7), attributes(7)
+ bind(3C), connect(3C), getsockopt(3C), sendmsg(3C), sendto(3C), set-
+ sockopt(3C), socket.h(3HEAD), Intro(3), inet(4P), inet6(4P), stan-
+ dards(7), attributes(7)
-Oracle Solaris 11.4 30 Aug 2002 in.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 in.h(3HEAD)
diff -NurbBw 11.4.72/man3head/inet.h.3head 11.4.75/man3head/inet.h.3head
--- 11.4.72/man3head/inet.h.3head 2024-11-22 11:50:41.283993446 -0800
+++ 11.4.75/man3head/inet.h.3head 2024-11-22 11:52:07.803810029 -0800
@@ -12,7 +12,7 @@
Inclusion of the <arpa/inet.h> header may also make visible all symbols
- from in.h(3HEAD).
+ from in.h(3HEAD) and inttypes.h(3HEAD).
The following are declared as functions, and may also be defined as
@@ -24,13 +24,16 @@
in_addr_t inet_netof(struct in_addr);
in_addr_t inet_network(const char *);
char *inet_ntoa(struct in_addr);
+ const char *inet_ntop(int, const void *restrict, char *restrict,
+ socklen_t);
+ int inet_pton(int, const char *restrict, void *restrict);
Default
- For applications that do not require standard-conforming behavior
- (those that use the socket interfaces described in section 3N of the
- reference manual; see intro(3) and standards(7)), the following may be
- declared as functions, or defined as macros, or both:
+ For applications that do not require XPG4v2-conforming behavior, in-
+ cluding those that require conformance with later standards (see stan-
+ dards(7)), the following may be declared as functions, or defined as
+ macros, or both:
uint32_t htonl(uint32_t);
uint16_t htons(uint16_t);
@@ -38,11 +41,10 @@
uint16_t ntohs(uint16_t);
- Standard conforming
- For applications that require standard-conforming behavior (those that
- use the socket interfaces described in section 3XN of the reference
- manual; see intro(3) and standards(7)), the following may be declared
- as functions, or defined as macros, or both:
+ SUS (XPG4v2) conforming
+ For applications that require XPG4v2-conforming behavior (see stan-
+ dards(7)), the following may be declared as functions, or defined as
+ macros, or both:
in_addr_t htonl(in_addr_t);
in_port_t htons(in_port_t);
@@ -63,7 +65,6 @@
SEE ALSO
- htonl(3C), htonl(3C), inet_addr(3C), inet_addr(3C), in.h(3HEAD), in-
- tro(3), attributes(7), standards(7)
+ htonl(3C), inet(3C), in.h(3HEAD), Intro(3), attributes(7), standards(7)
-Oracle Solaris 11.4 30 Aug 2002 inet.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 inet.h(3HEAD)
diff -NurbBw 11.4.72/man3head/inttypes.h.3head 11.4.75/man3head/inttypes.h.3head
--- 11.4.72/man3head/inttypes.h.3head 2024-11-22 11:50:41.317263938 -0800
+++ 11.4.75/man3head/inttypes.h.3head 2024-11-22 11:52:07.840097693 -0800
@@ -26,9 +26,9 @@
(character string literals for the fscanf() and fwscanf() family of
functions), followed by the conversion specifier, followed by a name
corresponding to a similar type name in <stdint.h>. In these names, N
- represents the width of the type as described in <stdint.h>. For exam-
- ple, PRIdFAST32 can be used in a format string to print the value of an
- integer of type int_fast32_t.
+ represents the width of the type as described in stdint.h(3HEAD). For
+ example, PRIdFAST32 can be used in a format string to print the value
+ of an integer of type int_fast32_t.
The fprintf() macros for signed integers are:
@@ -66,6 +62,11 @@
+ Additional macro names beginning with PRI or SCN followed by any lower-
+ case letter or 'X' may be defined in the <inttypes.h> header now or
+ added in the future.
+
+
For each type that the implementation provides in <stdint.h>, the cor-
responding fprintf() and fwprintf() macros must be defined. The corre-
sponding fscanf() and fwscanf() macros must be defined as well, unless
@@ -113,6 +114,7 @@
SEE ALSO
- imaxdiv(3C), attributes(7), standards(7)
+ imaxabs(3C), imaxdiv(3C), strtoimax(3C), wcstoimax(3C),
+ stdint.h(3HEAD), attributes(7), standards(7)
-Oracle Solaris 11.4 10 Sep 2004 inttypes.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 inttypes.h(3HEAD)
diff -NurbBw 11.4.72/man3head/ipc.h.3head 11.4.75/man3head/ipc.h.3head
--- 11.4.72/man3head/ipc.h.3head 2024-11-22 11:50:41.346952324 -0800
+++ 11.4.75/man3head/ipc.h.3head 2024-11-22 11:52:07.869397567 -0800
@@ -19,12 +19,12 @@
gid_t gid /* owner's group ID */
uid_t cuid /* creator's user ID */
gid_t cgid /* creator's group ID */
- mode_t mode /* read/write permission
+ mode_t mode /* read/write permission */
The uid_t, gid_t, mode_t, and key_t types are defined as described in
- <sys/types.h>. See types.h(3HEAD).
+ types.h(3HEAD).
Definitions are provided for the constants listed below.
@@ -74,4 +74,4 @@
SEE ALSO
ftok(3C), types.h(3HEAD), attributes(7), standards(7)
-Oracle Solaris 11.4 10 Sep 2004 ipc.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 ipc.h(3HEAD)
diff -NurbBw 11.4.72/man3head/langinfo.h.3head 11.4.75/man3head/langinfo.h.3head
--- 11.4.72/man3head/langinfo.h.3head 2024-11-22 11:50:41.384000379 -0800
+++ 11.4.75/man3head/langinfo.h.3head 2024-11-22 11:52:07.903572965 -0800
@@ -9,7 +9,7 @@
DESCRIPTION
The <langinfo.h> header contains the constants used to identify items
of langinfo data (see nl_langinfo(3C)). The type of the constant,
- nl_item, is defined as described in <nl_types.h>.
+ nl_item, is defined as described in nl_types.h(3HEAD).
The <langinfo.h> header defines the locale_t type as described in <lo-
@@ -145,16 +145,22 @@
--------------------------------------------------------------------------
YESSTR LC_MESSAGES affirmative response for yes/no queries
--------------------------------------------------------------------------
- NOSTR LC_MESSAGES negative response ro yes/no queries
+ NOSTR LC_MESSAGES negative response for yes/no queries
--------------------------------------------------------------------------
CRNCYSTR LC_MONETARY local currency symbol, preceded by '-'
if the symbol should appear before the
value, '+' if the symbol should appear
after the value, or '.' if the symbol
- should replace the radix character
+ should replace the radix character. May
+ be an empty string.
+ The constants YESSTR and NOSTR were marked LEGACY in the XPG5 standard
+ and removed in the XPG6 standard. They are not defined for standards-
+ conforming applications for the XPG6 and later standards.
+
+
If the locale's values for p_cs_precedes and n_cs_precedes do not
match, the value of nl_langinfo(CRNCYSTR) is unspecified.
@@ -195,4 +201,4 @@
time(3C), locale.h(3HEAD), nl_types.h(3HEAD), attributes(7), stan-
dards(7)
-Oracle Solaris 11.4 13 Nov 2020 langinfo.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 langinfo.h(3HEAD)
diff -NurbBw 11.4.72/man3head/limits.h.3head 11.4.75/man3head/limits.h.3head
--- 11.4.72/man3head/limits.h.3head 2024-11-22 11:50:41.427934177 -0800
+++ 11.4.75/man3head/limits.h.3head 2024-11-22 11:52:07.946631809 -0800
@@ -30,10 +30,14 @@
o The limit differs between the compile and runtime machines.
+ o The limit has been changed at runtime, such as by
+ setrlimit(2), or in the system configuration.
- For these reasons, an application can use the fpathconf(2), path-
- conf(2), and sysconf(3C) functions to determine the actual value of a
- limit at runtime.
+
+
+ For these reasons, an application can use the fpathconf(2),
+ getrlimit(2), pathconf(2), and sysconf(3C) functions to determine the
+ actual value of a limit at runtime.
Runtime Invariant Values (Possibly Indeterminate)
A definition of one of the symbolic names in the following list is
@@ -100,7 +104,7 @@
IOV_MAX
Maximum number of iovec structures that one process has available
- for use with read(2) or write(2).
+ for use with readv(2) or writev(2).
LOGIN_NAME_MAX
@@ -123,7 +127,8 @@
OPEN_MAX
Maximum number of files that one process can have open at any one
- time.
+ time. May be changed at runtime by the RLIMIT_NOFILE set by setr-
+ limit(2).
PAGESIZE
@@ -342,48 +347,60 @@
value supported by a specific instance is provided by the sysconf(3C)
function.
- BC_BASE_MAX Maximum obase values allowed by the bc(1) util-
- ity.
+ BC_BASE_MAX
+ Maximum obase values allowed by the bc(1) utility.
- BC_DIM_MAX Maximum number of elements permitted in an array
- by the bc utility.
+ BC_DIM_MAX
- BC_SCALE_MAX Maximum scale value allowed by the bc utility.
+ Maximum number of elements permitted in an array by the bc utility.
- BC_STRING_MAX Maximum length of a string constant accepted by
- the bc utility.
+ BC_SCALE_MAX
+ Maximum scale value allowed by the bc utility.
- CHARCLASS_NAME_MAX Maximum number of bytes in a character class
- name.
+ BC_STRING_MAX
- COLL_WEIGHTS_MAX Maximum number of weights that can be assigned to
- an entry of the LC_COLLATE order keyword in the
- locale definition file.
+ Maximum length of a string constant accepted by the bc utility.
- EXPR_NEST_MAX Maximum number of expressions that can be nested
- within parentheses by the expr(1) utility.
+ CHARCLASS_NAME_MAX
+ Maximum number of bytes in a character class name.
- LINE_MAX Unless otherwise noted, the maximum length, in
- bytes, of a utility's input line (either standard
- input or another file), when the utility is de-
- scribed as processing text files. The length in-
- cludes room for the trailing <newline>.
+ COLL_WEIGHTS_MAX
- NGROUPS_MAX Maximum number of simultaneous supplementary
- group IDs per process.
+ Maximum number of weights that can be assigned to an entry of the
+ LC_COLLATE order keyword in the locale definition file.
- RE_DUP_MAX Maximum number of repeated occurrences of a regu-
- lar expression permitted when using the interval
- notation \{m,n\}.
+ EXPR_NEST_MAX
+
+ Maximum number of expressions that can be nested within parentheses
+ by the expr(1) utility.
+
+
+ LINE_MAX
+
+ Unless otherwise noted, the maximum length, in bytes, of a util-
+ ity's input line (either standard input or another file), when the
+ utility is described as processing text files. The length includes
+ room for the trailing <newline>.
+
+
+ NGROUPS_MAX
+
+ Maximum number of simultaneous supplementary group IDs per process.
+
+
+ RE_DUP_MAX
+
+ Maximum number of repeated occurrences of a regular expression per-
+ mitted when using the interval notation \{m,n\}.
Minimum Values
@@ -660,7 +677,7 @@
_XOPEN_IOV_MAX
Maximum number of iovec structures that one process has available
- for use with read(2) or write(2).
+ for use with readv(2) or writev(2).
_XOPEN_NAME_MAX
@@ -813,6 +830,48 @@
SEE ALSO
- fpathconf(2), pathconf(2), sysconf(3C), standards(7)
+ getconf(1), getrlimit(2), fpathconf(2), pathconf(2), setrlimit(2),
+ sysconf(3C), resource-controls(7), standards(7)
+
+HISTORY
+ The value defined in <limits.h> for IOV_MAX was raised to 1024 in the
+ Oracle Solaris 11.4.72 release. In prior releases it was defined to be
+ 16.
+
+
+ The value defined in <limits.h> for OPEN_MAX was raised to 4095 in the
+ Oracle Solaris 11.4.27 release. In prior releases it was defined to be
+ 256.
+
+
+ The value defined in <limits.h> for LOGNAME_MAX was raised to 32 in the
+ Oracle Solaris 11.4.0 release. In prior releases it was defined to be
+ 8.
+
+
+ The value defined in <limits.h> for NGROUPS_MAX was raised to 1024 in
+ the Oracle Solaris 11.4.0 release. In prior releases it was defined to
+ be 16.
+
+
+ The definition in <limits.h> for LINK_MAX was removed in the Solaris 10
+ 3/05 release, as the limit on Solaris varies by filesystem type, so
+ needs to be found via fpathconf(2). In prior releases it was defined to
+ be 32767.
+
+
+ The value defined in <limits.h> for PASS_MAX was raised to 256 in the
+ Solaris 10 3/05 release, unless the application is compiled to conform
+ with a standard earlier than XPG6. In prior releases, or when compiling
+ for strict conformance to older standards, it is defined to be 8.
+
+
+ The value defined in <limits.h> for UID_MAX was raised to 2147483647 in
+ the Solaris 2.6 release. In prior releases it was defined to be 60002.
+
+
+ The <limits.h> header file was added to Solaris in the Solaris 2.0 re-
+ lease. In prior releases a similar header was provided as <sys/lim-
+ its.h>.
-Oracle Solaris 11.4 10 Jan 2024 limits.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 limits.h(3HEAD)
diff -NurbBw 11.4.72/man3head/math.h.3head 11.4.75/man3head/math.h.3head
--- 11.4.72/man3head/math.h.3head 2024-11-22 11:50:41.460437810 -0800
+++ 11.4.75/man3head/math.h.3head 2024-11-22 11:52:07.980253134 -0800
@@ -182,7 +172,7 @@
SEE ALSO
- fenv.h(3HEAD), limits.h(3HEAD), libm(3LIB), matherr(3M), intro(3), at-
+ fenv.h(3HEAD), limits.h(3HEAD), libm(3LIB), matherr(3M), Intro(3), at-
tributes(7), standards(7)
-Oracle Solaris 11.4 11 May 2021 math.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 math.h(3HEAD)
diff -NurbBw 11.4.72/man3head/mman.h.3head 11.4.75/man3head/mman.h.3head
--- 11.4.72/man3head/mman.h.3head 2024-11-22 11:50:41.490115276 -0800
+++ 11.4.75/man3head/mman.h.3head 2024-11-22 11:52:08.010368082 -0800
@@ -7,7 +7,8 @@
#include <sys/mman.h>
DESCRIPTION
- The <sys/mman.h> header supports the following options:
+ The <sys/mman.h> header supports the following options of the POSIX and
+ SUS standards:
o the Memory Mapped Files option
@@ -41,9 +42,9 @@
- The following flag options are defined:
+ The following flag options are defined for mmap(2):
- MAP_SHARED Share changes.
+ MAP_SHARED Changes are shared.
MAP_PRIVATE Changes are private.
@@ -52,6 +53,30 @@
MAP_FIXED Interpret addr exactly.
+ MAP_NORESERVE Do not reserve swap space.
+
+
+ MAP_ANONYMOUS Map anonymous memory.
+
+
+ MAP_ANON Alternate name for MAP_ANONYMOUS.
+
+
+ MAP_ALIGN Interpret addr as required alignment.
+
+
+ MAP_TEXT Map text.
+
+
+ MAP_INITDATA Map initialized data segment.
+
+
+ MAP_LOW32 Constrain pa to be below 4g.
+
+
+ MAP_ADI Enable ADI. See adi(3C) and adi(7).
+
+
The flags immediately following are defined for msync(). See msync(3C).
@@ -80,7 +105,7 @@
The mode_t, off_t, and size_t types are be defined as described in
- <sys/types.h>. See types(3HEAD).
+ types.h(3HEAD).
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -98,4 +123,4 @@
mmap(2), mprotect(2), munmap(2), madvise(3C), mlock(3C), mlockall(3C),
msync(3C), shm_open(3C), shm_unlink(3C), attributes(7), standards(7)
-Oracle Solaris 11.4 5 Feb 2008 mman.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 mman.h(3HEAD)
diff -NurbBw 11.4.72/man3head/netdb.h.3head 11.4.75/man3head/netdb.h.3head
--- 11.4.72/man3head/netdb.h.3head 2024-11-22 11:50:41.523103493 -0800
+++ 11.4.75/man3head/netdb.h.3head 2024-11-22 11:52:08.044447720 -0800
@@ -30,7 +30,7 @@
The <netdb.h> header defines the following symbolic constants that
- evaluate to bitwise-distinct integer constants for use in the flags
+ evaluate to bitwise-distinct integer constants for use in the ai_flags
field of the addrinfo structure:
AI_PASSIVE
@@ -115,6 +115,11 @@
tion translates these values to error message strings for user presen-
tation.
+ EAI_ADDRFAMILY
+
+ The address family is not supported.
+
+
EAI_AGAIN
The name could not be resolved at this time. Future attempts may
@@ -270,10 +275,10 @@
gethostent(3C), getnameinfo(3C), getnetent(3C), getprotoent(3C),
getservbyname(3C), getservent(3C), sethostent(3C), setnetent(3C),
setprotoent(3C), setservent(3C), in.h(3HEAD), socket.h(3HEAD),
- intro(3), attributes(7), standards(7)
+ Intro(3), attributes(7), standards(7)
Gilligan, R. RFC 3493, Basic Socket Interface Extensions for IPv6. Net-
work Working Group. February 2003. https://tools.ietf.org/html/rfc3493
-Oracle Solaris 11.4 2 Feb 2021 netdb.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 netdb.h(3HEAD)
diff -NurbBw 11.4.72/man3head/paths.h.3head 11.4.75/man3head/paths.h.3head
--- 11.4.72/man3head/paths.h.3head 2024-11-22 11:50:41.552744398 -0800
+++ 11.4.75/man3head/paths.h.3head 2024-11-22 11:52:08.076540493 -0800
@@ -12,10 +12,10 @@
laris.
Pathname Macros
- _PATH_BSHELL The pathname of the Bourne Shell.
+ _PATH_BSHELL The pathname of a Bourne-style Shell.
- _PATH_CONSOLE The pathname of the console device.
+ _PATH_CONSOLE The pathname of the console(4D) device.
_PATH_CONSOLE_USER_LINK The link to the current (virtual) console
@@ -28,86 +28,89 @@
_PATH_CSHELL The pathname of the C-shell.
- _PATH_DEFAULT_LOGIN The pathname of the default login file.
+ _PATH_DEFAULT_LOGIN The pathname of the default configuration
+ file for login(1).
- _PATH_DEVNULL The pathname of the device null(4D).
+ _PATH_DEVNULL The pathname of the null(4D) device.
- _PATH_ED The pathname of the text editor (ed(1)).
+ _PATH_ED The pathname of the ed(1) text editor.
_PATH_ETHERS The pathname of the Ethernet address to
- hostname mapping table (ethers(5)).
+ hostname mapping table, ethers(5).
- _PATH_GROUP The pathname of the group file.
+ _PATH_GROUP The pathname of the group(5) file.
- _PATH_HEQUIV The pathname of the hosts.equiv file.
+ _PATH_HEQUIV The pathname of the hosts.equiv(5) file.
_PATH_HESIOD_CONF The pathname of the hesiod.conf file.
- _PATH_HOSTS The pathname of the hosts file.
+ _PATH_HOSTS The pathname of the hosts(5) file.
- _PATH_IPNODES The pathname of the ipnodes file.
+ _PATH_IPNODES The pathname of the ipnodes(5) file.
- _PATH_IPSECALGS The pathname of the ipsecalgs file.
+ _PATH_IPSECALGS The pathname of the ipsecalgs file. See
+ ipsecalgs(8).
_PATH_IRS_CONF The pathname of the irs.conf file.
- _PATH_KMEM The pathname of the device kmem (mem(4D)).
+ _PATH_KMEM The pathname of the kmem(4D) file.
- _PATH_LASTLOG The pathname of the lastlog file.
+ _PATH_LASTLOG The pathname of the lastlog file. See
+ pam_unix_session(7).
_PATH_MAILDIR The pathname of the mail spool directory.
- _PATH_NETGROUP The pathname of the netgroup file.
+ _PATH_NETGROUP The pathname of the netgroup(5) file.
- _PATH_NETMASKS The pathname of the netmasks file.
+ _PATH_NETMASKS The pathname of the netmasks(5) file.
- _PATH_NETWORKS The pathname of the networks file.
+ _PATH_NETWORKS The pathname of the networks(5) file.
- _PATH_NOLOGIN The pathname of the nologin file.
+ _PATH_NOLOGIN The pathname of the nologin(5) file.
_PATH_OPENPROM The pathname of the openprom(4D) device.
- _PATH_POWER_MGMT The pathname of the power management driver
- (pm(4D)).
+ _PATH_POWER_MGMT The pathname of the power management driver,
+ pm(4D).
- _PATH_PROTOCOLS The pathname of the protocols file.
+ _PATH_PROTOCOLS The pathname of the protocols(5) file.
_PATH_RANDOM The pathname of the random(4D) device.
- _PATH_RESCONF The pathname of the resolv.conf file.
+ _PATH_RESCONF The pathname of the resolv.conf(5) file.
- _PATH_RSH The pathname of the remote shell command
- (rsh(1)).
+ _PATH_RSH The pathname of the remote shell command,
+ rsh(1).
- _PATH_SERVICES The pathname of the services file.
+ _PATH_SERVICES The pathname of the services(5) file.
- _PATH_SHELLS The pathname of the shell database
- (shells(5)).
+ _PATH_SHELLS The pathname of the shell database,
+ shells(5).
_PATH_SYSCON The pathname of the syscon device.
@@ -116,44 +119,45 @@
_PATH_SYSEVENT The pathname of the sysevent device.
- _PATH_SYSMSG The pathname of the sysmsg device.
+ _PATH_SYSMSG The pathname of the sysmsg(4D) device.
_PATH_SYSTTY The pathname of the system tty.
_PATH_TMP The pathname of the temporary file system.
+ See filesystem(7).
- _PATH_TTY The pathname of the tty device.
+ _PATH_TTY The pathname of the tty(4D) device.
- _PATH_UNIX The pathname of the kernel namelist
- (ksyms(4D)).
+ _PATH_UNIX The pathname of the kernel namelist,
+ ksyms(4D).
_PATH_URANDOM The pathname of the urandom(4D) device.
_PATH_USRTMP The pathname of the user temporary direc-
- tory.
+ tory, the same as _PATH_VARTMP.
- _PATH_UTMPX The pathname of the UTMPX file.
+ _PATH_UTMPX The pathname of the utmpx(5) file.
- _PATH_VARRUN The pathname of the systems temporary file
- directory.
+ _PATH_VARRUN The pathname of the system temporary file
+ directory. See filesystem(7).
_PATH_VARTMP The pathname of the user temporary file di-
- rectory.
+ rectory. See filesystem(7).
_PATH_VI The pathname of the vi(1) editor.
- _PATH_WTMPX The pathname of the WTMPX file.
+ _PATH_WTMPX The pathname of the wtmpx(5) file.
ATTRIBUTES
@@ -167,8 +171,15 @@
SEE ALSO
- cp(1), ed(1), rsh(1), vi(1), ksyms(4D), mem(4D), null(4D), open-
- prom(4D), pm(4D), random(4D), urandom(4D), ethers(5), shells(5), at-
- tributes(7)
+ cp(1), ed(1), login(1), rsh(1), vi(1), console(4D), kmem(4D),
+ ksyms(4D), null(4D), openprom(4D), pm(4D), random(4D), sysmsg(4D),
+ tty(4D), urandom(4D), ethers(5), group(5), hosts(5), hosts.equiv(5),
+ ipnodes(5), netmasks(5), networks(5), nologin(5), protocols(5),
+ resolv.conf(5), services(5), shells(5), utmpx(5), wtmpx(5),
+ attributes(7), filesystem(7), pam_unix_session(7), ipsecalgs(8)
+
+HISTORY
+ The <paths.h> header file was first included in the Solaris 11.0 re-
+ lease.
-Oracle Solaris 11.4 11 May 2021 paths.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 paths.h(3HEAD)
diff -NurbBw 11.4.72/man3head/procset.h.3head 11.4.75/man3head/procset.h.3head
--- 11.4.72/man3head/procset.h.3head 2024-11-22 11:50:41.582255994 -0800
+++ 11.4.75/man3head/procset.h.3head 2024-11-22 11:52:08.135610938 -0800
@@ -87,7 +86,7 @@
- #include <procset.h>
+ #include <sys/procset.h>
procset_t ps;
setprocset(&PS, POP_AND, P_PID, P_MYID, P_ALL, 0);
@@ -99,7 +98,7 @@
#include <thread.h>
- #include <procset.h>
+ #include <sys/procset.h>
procset_t ps;
setprocset(&PS, POP_AND, P_PID, P_MYID, P_LWPID, thr_self());
@@ -110,7 +109,7 @@
#include <thread.h>
- #include <procset.h>
+ #include <sys/procset.h>
procset_t ps;
setprocset(&PS, POP_AND, P_UID, P_MYID, P_ALL, 0);
@@ -123,7 +122,7 @@
#include <thread.h>
- #include <procset.h>
+ #include <sys/procset.h>
procset_t ps;
setprocset(&PS, POP_AND, P_UID, 323, P_ZONEID, 7);
@@ -141,4 +140,18 @@
+------------------------------+-----------------------------+
-Oracle Solaris 11.4 22 Feb 2021 procset.h(3HEAD)
+SEE ALSO
+ priocntlset(2), processor_affinity(2), sigsendset(2)
+
+HISTORY
+ P_CPUID, P_CTID, P_POOLID, P_PSETID, and P_ZONEID were added in Solaris
+ 10 3/05.
+
+
+ P_PROJID and P_TASKID were added in Solaris 9.
+
+
+ The <procset.h> header file was first included in the Solaris 2.0 re-
+ lease.
+
+Oracle Solaris 11.4 30 Aug 2024 procset.h(3HEAD)
diff -NurbBw 11.4.72/man3head/pwd.h.3head 11.4.75/man3head/pwd.h.3head
--- 11.4.72/man3head/pwd.h.3head 2024-11-22 11:50:41.611482575 -0800
+++ 11.4.75/man3head/pwd.h.3head 2024-11-22 11:52:08.166532467 -0800
@@ -10,16 +10,16 @@
The <pwd.h> header provides a definition for struct passwd, which in-
cludes the following members:
- char *pw_name user's login name
- uid_t pw_uid numerical user ID
- gid_t pw_gid numerical group ID
- char *pw_dir initial working di rectory
- char *pw_shell program to use as shell
+ char *pw_name; /* user's login name */
+ uid_t pw_uid; /* user's uid */
+ gid_t pw_gid; /* user's gid */
+ char *pw_gecos; /* typically user's full name */
+ char *pw_dir; /* user's home dir */
+ char *pw_shell; /* user's login shell */
- The gid_t and uid_t types are defined as described in <sys/types.h>.
- See types.h(3HEAD).
+ The gid_t and uid_t types are defined as described in types.h(3HEAD).
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -34,6 +34,10 @@
SEE ALSO
- getpwnam(3C), types.h(3HEAD), attributes(7), standards(7)
+ getpwnam(3C), types.h(3HEAD), passwd(5), attributes(7), standards(7)
-Oracle Solaris 11.4 10 Sep 2004 pwd.h(3HEAD)
+HISTORY
+ The <pwd.h> header file has been included in all Sun and Oracle re-
+ leases of Solaris.
+
+Oracle Solaris 11.4 30 Aug 2024 pwd.h(3HEAD)
diff -NurbBw 11.4.72/man3head/siginfo.h.3head 11.4.75/man3head/siginfo.h.3head
--- 11.4.72/man3head/siginfo.h.3head 2024-11-22 11:50:41.647796528 -0800
+++ 11.4.75/man3head/siginfo.h.3head 2024-11-22 11:52:08.205579207 -0800
@@ -26,7 +26,7 @@
If si_errno is non-zero, it contains an error number associated with
- this signal, as defined in <errno.h>.
+ this signal, as defined in errno.h(3HEAD).
si_code contains a code identifying the cause of the signal.
@@ -49,7 +49,7 @@
pid_t si_pid /* sending process ID */
uid_t si_uid /* sending user ID */
ctid_t si_ctid /* sending contract ID */
- zoneid_t si_zoneid /* sending zone ID */S
+ zoneid_t si_zoneid /* sending zone ID */
@@ -57,7 +57,7 @@
defined for si_code:
SI_USER The implementation sets si_code to SI_USER if the signal
- was sent by kill(2), sigsend(2), raise(3C) or abort(3C).
+ was sent by kill(2), sigsend(2), raise(3C), or abort(3C).
SI_LWP The signal was sent by _lwp_kill(2).
@@ -91,7 +91,7 @@
why the system generated the signal:
Signal Code Reason
- ----------------------------------------------------------------------------
+ ---------------------------------------------------------------------
SIGILL ILL_ILLOPC illegal opcode
ILL_ILLOPN illegal operand
ILL_ILLADR illegal addressing mode
@@ -100,7 +100,7 @@
ILL_PRVREG privileged register
ILL_COPROC co-processor error
ILL_BADSTK internal stack error
- ----------------------------------------------------------------------------
+ ---------------------------------------------------------------------
SIGFPE FPE_INTDIV integer divide by zero
FPE_INTOVF integer overflow
FPE_FLTDIV floating point divide by zero
@@ -109,29 +109,29 @@
FPE_FLTRES floating point inexact result
FPE_FLTINV invalid floating point operation
FPE_FLTSUB subscript out of range
- ----------------------------------------------------------------------------
+ ---------------------------------------------------------------------
SIGSEGV SEGV_MAPERR address not mapped to object
SEGV_ACCERR invalid permissions for mapped object
SEGV_ACCADI ADI not enabled for mapped object
SEGV_ADIDERR ADI mismatch exception disrupting
SEGV_ADIPERR ADI mismatch exception precise
SEGV_CMI exception in mapped CMI object
- ----------------------------------------------------------------------------
+ ---------------------------------------------------------------------
SIGBUS BUS_ADRALN invalid address alignment
BUS_ADRERR non-existent physical address
BUS_OBJERR object specific hardware error
BUS_MEM_UE user process uncorrectable memory error
- ----------------------------------------------------------------------------
+ ---------------------------------------------------------------------
SIGTRAP TRAP_BRKPT process breakpoint
TRAP_TRACE process trace trap
- ----------------------------------------------------------------------------
+ ---------------------------------------------------------------------
SIGCHLD CLD_EXITED child has exited
CLD_KILLED child was killed
CLD_DUMPED child terminated abnormally
CLD_TRAPPED traced child has trapped
CLD_STOPPED child has stopped
CLD_CONTINUED stopped child had continued
- ----------------------------------------------------------------------------
+ ---------------------------------------------------------------------
SIGPOLL POLL_IN data input available
POLL_OUT output buffers available
POLL_MSG input message available
@@ -147,9 +147,9 @@
generated signal from an established resource control value.
Signal Code Reason
- --------------------------------------------------------------------
+ ---------------------------------------------------------------
SIGXRES SI_RCTL resource-control generated signal
- --------------------------------------------------------------------
+ ---------------------------------------------------------------
SIGHUP
SIGTERM
@@ -163,7 +163,7 @@
formation for kernel-generated signals:
Code Field Value
- -------------------------------------------------------------------
+ ------------------------------------------------------------------
SI_RCTL hr_time si_entity process-model entity of control
@@ -172,17 +172,17 @@
for kernel-generated signals:
Signal Field Value
- ------------------------------------------------------------------------
+ --------------------------------------------------------------------
SIGILL caddr_t si_addr address of faulting instruction
- ------------------------------------------------------------------------
+ --------------------------------------------------------------------
SIGFPE
- ------------------------------------------------------------------------
+ --------------------------------------------------------------------
SIGSEGV caddr_t si_addr address of faulting memory reference
SIGBUS
- ------------------------------------------------------------------------
+ --------------------------------------------------------------------
SIGCHLD pid_t si_pid child process ID
int si_status exit value or signal
- ------------------------------------------------------------------------
+ --------------------------------------------------------------------
SIGPOLL long si_band band event for POLL_IN, POLL_OUT, or
POLL_MSG
@@ -192,14 +192,12 @@
tain signal-dependent information for kernel-generated SIGSEGV signals:
Code Field Value
- --------------------------------------------------------------------------
+ ------------------------------------------------------------------------
SEGV_ADIPERR caddr_t si_addr address of mismatched memory reference
- --------------------------------------------------------------------------
caddr_t si_pc address of instruction that executed
mismatched memory reference
- --------------------------------------------------------------------------
int si_adivers current ADI version of si_addr
- --------------------------------------------------------------------------
+ ------------------------------------------------------------------------
SEGV_ADIDERR caddr_t si_addr instruction address of first store
where mismatch was detected
caddr_t si_pc -1
@@ -207,21 +205,26 @@
+ See the adi(7) man page.
+
+
Signals sent with a siginfo code of SEGV_CMI contain signal-dependent
information for kernel-generated SIGSEGV signals:
Code Field Value
--------------------------------------------------------------
- SEGV_CMI int si_trapno CMI segment id of the
- mapped CMI + object that
- contains si_addr
+ SEGV_CMI int si_trapno CMI segment id of the mapped CMI
+ + object that contains si_addr
+
+
+ See the Delivering CMI Exceptions section of the cmi(7) man page.
SEE ALSO
_lwp_kill(2), adi_version_max(2), kill(2), setrctl(2), sigaction(2),
- sigsend(2), waitid(2), abort(3C), aio_read(3C), mq_notify(3C), psig-
- info(3C), raise(3C), sigqueue(3C), timer_create(3C), timer_settime(3C),
- signal.h(3HEAD)
+ sigsend(2), waitid(2), abort(3C), aio_read(3C), mq_notify(3C),
+ psiginfo(3C), raise(3C), sigqueue(3C), timer_create(3C),
+ timer_settime(3C), signal.h(3HEAD), adi(7), cmi(7)
NOTES
For SIGCHLD signals, if si_code is equal to CLD_EXITED, then si_status
@@ -259,4 +262,4 @@
the store and before the trap is taken due to the nature of a disrupt-
ing trap.
-Oracle Solaris 11.4 9 Jul 2018 siginfo.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 siginfo.h(3HEAD)
diff -NurbBw 11.4.72/man3head/stat.h.3head 11.4.75/man3head/stat.h.3head
--- 11.4.72/man3head/stat.h.3head 2024-11-22 11:50:41.678994969 -0800
+++ 11.4.75/man3head/stat.h.3head 2024-11-22 11:52:08.237338072 -0800
@@ -8,68 +8,131 @@
#include <sys/stat.h>
DESCRIPTION
- The system calls stat(), lstat() and fstat() return data in a stat
- structure, which is defined in <stat.h>.
+ The system calls stat(), lstat(), fstat(), and fstatat() return data in
+ a stat structure, which is defined in <sys/stat.h>.
- The constants used in the st_mode field are also defined in this file:
+ The following constants are also defined in this file. They may be used
+ to decode the data provided in the st_mode field of a stat structure,
+ or to form mode_t arguments to system calls such as chmod(2) or
+ mknod(2).
+
+
+ These constants are used as bitmasks to separate the bits representing
+ the file type from those representing the permissions or access mode:
+
+ S_IFMT type of file
+ S_IAMB access mode bits
+
+
+
+ The following constants are used as values to compare against the bits
+ representing the file type. They are not to be used as bitmasks them-
+ selves when making comparisons, but as values for a range of bits.
+
+ S_IFIFO fifo
+ S_IFCHR character special
+ S_IFDIR directory
+ S_IFNAM XENIX special named file
+ S_INSEM XENIX semaphore subtype of IFNAM
+ S_INSHD XENIX shared data subtype of IFNAM
+ S_IFBLK block special
+ S_IFREG regular
+ S_IFLNK symbolic link
+ S_IFSOCK socket
+ S_IFDOOR door
+ S_IFPORT event port
+
+
+
+ The following constants are used as values to compare against the bits
+ representing the access mode. They may be combined using the | ("or")
+ operator to form bitmasks. See chmod(2) for the effects of setting or
+ unsetting each bit.
+
+ S_ISUID set user id on execution
+ S_ISGID set group id on execution
+ S_ISVTX sticky bit
+ S_IREAD read permission, owner
+ S_IWRITE write permission, owner
+ S_IEXEC execute/search permission, owner
+ S_ENFMT mandatory file/record locking enforcement flag
+ S_IRWXU read, write, execute: owner
+ S_IRUSR read permission: owner
+ S_IWUSR write permission: owner
+ S_IXUSR execute permission: owner
+ S_IRWXG read, write, execute: group
+ S_IRGRP read permission: group
+ S_IWGRP write permission: group
+ S_IXGRP execute permission: group
+ S_IRWXO read, write, execute: other
+ S_IROTH read permission: other
+ S_IWOTH write permission: other
+ S_IXOTH execute permission: other
+
+
+
+ The following macros are provided for convenience to compare the file
+ type bits of st_mode values against the constant values for those file
+ types.
+
+ S_ISBLK(mode) block special file
+ S_ISCHR(mode) character special file
+ S_ISDIR(mode) directory
+ S_ISDOOR(mode) door
+ S_ISFIFO(mode) pipe or fifo file
+ S_ISLNK(mode) symbolic link
+ S_ISPORT(mode) event port
+ S_ISREG(mode) regular file
+ S_ISSOCK(mode) socket
- #define S_IFMT /* type of file */
- #define S_IAMB /* access mode bits */
- #define S_IFIFO /* fifo */
- #define S_IFCHR /* character special */
- #define S_IFDIR /* directory */
- #define S_IFNAM /* XENIX special named file */
- #define S_INSEM /* XENIX semaphore subtype of IFNAM */
- #define S_INSHD /* XENIX shared data subtype of IFNAM */
- #define S_IFBLK /* block special */
- #define S_IFREG /* regular */
- #define S_IFLNK /* symbolic link */
- #define S_IFSOCK /* socket */
- #define S_IFDOOR /* door */
- #define S_ISUID /* set user id on execution */
- #define S_ISGID /* set group id on execution */
- #define S_ISVTX /* save swapped text even after use */
- #define S_IREAD /* read permission, owner */
- #define S_IWRITE /* write permission, owner */
- #define S_IEXEC /* execute/search permission, owner */
- #define S_ENFMT /* record locking enforcement flag */
- #define S_IRWXU /* read, write, execute: owner */
- #define S_IRUSR /* read permission: owner */
- #define S_IWUSR /* write permission: owner */
- #define S_IXUSR /* execute permission: owner */
- #define S_IRWXG /* read, write, execute: group */
- #define S_IRGRP /* read permission: group */
- #define S_IWGRP /* write permission: group */
- #define S_IXGRP /* execute permission: group */
- #define S_IRWXO /* read, write, execute: other */
- #define S_IROTH /* read permission: other */
- #define S_IWOTH /* write permission: other */
- #define S_IXOTH /* execute permission: other */
+ The following symbolic constants are defined as distinct integer values
+ outside of the range [0, 999 999 999], for use with the futimens() and
+ utimensat() functions:
- The following macros are for POSIX conformance. For more information,
- see the standards(7) man page.
-
- #define S_ISBLK(mode) block special file
- #define S_ISCHR(mode) character special file
- #define S_ISDIR(mode) directory file
- #define S_ISFIFO(mode) pipe or fifo file
- #define S_ISREG(mode) regular file
- #define S_ISSOCK(mode) socket file
+ UTIME_NOW use the current time
+ UTIME_OMIT no time change
+EXAMPLES
+ Example 1 Determine type of file from stat() structure information.
+
+
+
+ The following example shows how to determine if a file path refers to a
+ directory or not.
+
+
+ #include <sys/types.h>
+ #include <sys/stat.h>
+ #include <fcntl.h>
+ #include <fcntl.h>
+
+ struct stat buffer;
+ int status;
+ ...
+ status = stat("/home/cnd/mod1", &buffer);
+ if (S_ISDIR(buffer.st_mode)) {
+ puts("/home is a directory");
+ } else {
+ puts("/home is not a directory");
+ }
+
+
+
+
+ The if statement could also be written as:
- The following symbolic constants are defined as distinct integer values
- outside of the range [0, 999 999 999], for use with the futimens() and
- utimensat() functions:
- #define UTIME_NOW use the current time
- #define UTIME_OMIT no time change
+ if ((buffer.st_mode & S_IFMT) == S_IFDIR) {
+ Checking for buffer.st_mode & S_IFDIR will cause the code to fail to
+ distinguish between directories and other file types which have over-
+ lapping bit patterns in their file format values.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -84,6 +147,7 @@
SEE ALSO
- futimens(2), stat(2), types.h(3HEAD), attributes(7), standards(7)
+ chmod(2), futimens(2), mknod(2), stat(2), types.h(3HEAD), attrib-
+ utes(7), standards(7)
-Oracle Solaris 11.4 11 Apr 2016 stat.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 stat.h(3HEAD)
diff -NurbBw 11.4.72/man3head/stdalign.h.3head 11.4.75/man3head/stdalign.h.3head
--- 11.4.72/man3head/stdalign.h.3head 2024-11-22 11:50:41.709943480 -0800
+++ 11.4.75/man3head/stdalign.h.3head 2024-11-22 11:52:08.265881130 -0800
@@ -1,16 +1,14 @@
stdalign.h(3HEAD) Headers stdalign.h(3HEAD)
NAME
- stdalign.h, stdalign - provides four convenient macros for dealing with
- alignments of objects. The
- header was added in C11
+ stdalign.h, stdalign - macros for dealing with alignments of objects
SYNOPSIS
#include <stdalign.h>
DESCRIPTION
- The stdalign.h header defines the following macros:
-
+ The stdalign.h header defines the following macros when compiling with
+ the C11 or later versions of the C standard:
alignas Expands to _Alignas.
@@ -33,11 +30,15 @@
+------------------------------+-----------------------------+
| Interface Stability |Committed |
+------------------------------+-----------------------------+
- | Standard |See standards(7) man page. |
+ | Standard |C11 |
+------------------------------+-----------------------------+
SEE ALSO
attributes(7), standards(7)
-Oracle Solaris 11.4 16 Jan 2017 stdalign.h(3HEAD)
+HISTORY
+ The <stdalign.h> header file was added to Oracle Solaris in the 11.4.0
+ release.
+
+Oracle Solaris 11.4 30 Aug 2024 stdalign.h(3HEAD)
diff -NurbBw 11.4.72/man3head/stddef.h.3head 11.4.75/man3head/stddef.h.3head
--- 11.4.72/man3head/stddef.h.3head 2024-11-22 11:50:41.740126663 -0800
+++ 11.4.75/man3head/stddef.h.3head 2024-11-22 11:52:08.295164467 -0800
@@ -24,17 +24,24 @@
The <stddef.h> header defines the following types:
+ max_align_t Type whose alignment has the largest alignment of any
+ fundamental type in the compilation environment. (Only
+ defined when compiling in C11 or later or C++11 or later
+ modes.)
+
+
ptrdiff_t Signed integer type of the result of subtracting two
pointers.
- wchar_t Integer type whose range of values can represent distinct
- wide-character codes for all members of the largest char-
- acter set specified among the locales supported by the
- compilation environment: the null character has the code
- value 0 and each member of the portable character set has
- a code value equal to its value when used as the lone
- character in an integer character constant.
+ wchar_t Integer type whose range of values can represent dis-
+ tinct wide-character codes for all members of the
+ largest character set specified among the locales sup-
+ ported by the compilation environment; the null charac-
+ ter has the code value 0 and each member of the portable
+ character set has a code value equal to its value when
+ used as the lone character in an integer character con-
+ stant.
size_t Unsigned integer type of the result of the sizeof opera-
@@ -63,4 +70,11 @@
getconf(1), confstr(3C), types.h(3HEAD), wchar.h(3HEAD), attributes(7),
standards(7)
-Oracle Solaris 11.4 10 Sep 2004 stddef.h(3HEAD)
+HISTORY
+ The max_align_t definition was added in Oracle Solaris 11.4.0.
+
+
+ The <stddef.h> header file has been included in all Sun and Oracle re-
+ leases of Solaris.
+
+Oracle Solaris 11.4 30 Aug 2024 stddef.h(3HEAD)
diff -NurbBw 11.4.72/man3head/stdint.h.3head 11.4.75/man3head/stdint.h.3head
--- 11.4.72/man3head/stdint.h.3head 2024-11-22 11:50:41.777427890 -0800
+++ 11.4.75/man3head/stdint.h.3head 2024-11-22 11:52:08.339519923 -0800
@@ -100,9 +100,9 @@
o The implementation supports the _POSIX_V6_ILP32_OFFBIG
programming environment and the application is being
- built in the _POSI X_V6_ILP32_OFFBIG programming envi-
- ronment (see the Shell and Utilities volume of IEEE Std
- 1003.1-200x, c99, Programming Environments).
+ built in the _POSIX_V6_ILP32_OFFBIG programming environ-
+ ment (see the Shell and Utilities volume of IEEE Std
+ 1003.1-2008, c99, Programming Environments).
o The implementation supports the _POSIX_V6_LP64_OFF64
@@ -158,9 +158,9 @@
the signedness and width requirements.
The typedef name int_fastN_t designates the fastest signed integer
- type with a width of at least N. The typedef name uint_fastN_ t
- designates the fastest unsigned integer type with a width of at
- least N.
+ type with a width of at least N. The typedef name uint_fastN_t des-
+ ignates the fastest unsigned integer type with a width of at least
+ N.
The following types are required:
@@ -497,4 +497,4 @@
wchar.h(3HEAD), inttypes.h(3HEAD), signal.h(3HEAD), stddef.h(3HEAD),
attributes(7), standards(7)
-Oracle Solaris 11.4 10 Sep 2004 stdint.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 stdint.h(3HEAD)
diff -NurbBw 11.4.72/man3head/termios.h.3head 11.4.75/man3head/termios.h.3head
--- 11.4.72/man3head/termios.h.3head 2024-11-22 11:50:41.812423443 -0800
+++ 11.4.75/man3head/termios.h.3head 2024-11-22 11:52:08.377951409 -0800
@@ -209,51 +189,29 @@
derlying hardware.
B0 Hang up
-
-
B50 50 baud
-
-
B75 75 baud
-
-
B110 110 baud
-
-
B134 134.5 baud
-
-
B150 150 baud
-
-
B200 200 baud
-
-
B300 300 baud
-
-
B600 600 baud
-
-
B1200 1 200 baud
-
-
B1800 1 800 baud
-
-
B2400 2 400 baud
-
-
B4800 4 800 baud
-
-
B9600 9 600 baud
-
-
B19200 19 200 baud
-
-
B38400 38 400 baud
+ B57600 57600 baud
+ B76800 76800 baud
+ B115200 115200 baud
+ B153600 153600 baud
+ B230400 230400 baud
+ B307200 307200 baud
+ B460800 460800 baud
+ B921600 921600 baud
Control Modes
@@ -386,4 +338,4 @@
tcflow(3C), tcflush(3C), tcgetattr(3C), tcgetsid(3C), tcsendbreak(3C),
tcsetattr(3C), attributes(7), standards(7)
-Oracle Solaris 11.4 10 Sep 2004 termios.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 termios.h(3HEAD)
diff -NurbBw 11.4.72/man3head/types.h.3head 11.4.75/man3head/types.h.3head
--- 11.4.72/man3head/types.h.3head 2024-11-22 11:50:41.848498304 -0800
+++ 11.4.75/man3head/types.h.3head 2024-11-22 11:52:08.412913288 -0800
@@ -7,71 +7,98 @@
#include <sys/types.h>
DESCRIPTION
- The data types defined in <sys/types.h> are as follows:
+ The following data types are always defined by <sys/types.h>:
- 32-bit Solaris
- The data types listed below are defined in <sys/types.h> for 32-bit So-
- laris.
+ typedef unsigned char uchar_t;
+ typedef unsigned short ushort_t;
+ typedef unsigned int uint_t;
+ typedef unsigned long ulong_t;
+ typedef long long longlong_t;
+ typedef unsigned long long u_longlong_t;
- typedef struct { int r[1]; } *physadr;
+ typedef char * caddr_t;
typedef long clock_t;
+ typedef short cnt_t;
typedef long daddr_t;
- typedef char * caddr_t;
+ typedef ulong_t dev_t;
+ typedef unsigned int gid_t;
+ typedef short index_t;
+ typedef int key_t;
+ typedef struct { long val[]; } label_t;
+ typedef unsigned int lock_t;
+ typedef short sysid_t;
+ typedef long time_t;
+ typedef unsigned int uid_t;
+ typedef unsigned char use_t;
+
+
+
+ These data types are defined in <sys/types.h> for historical compati-
+ bility, but they are deprecated in favor of the types listed above with
+ _t suffixes:
+
typedef unsigned char unchar;
typedef unsigned short ushort;
typedef unsigned int uint;
- typedef unsigned long ulong_t;
- typedef unsigned long ino_t;
- typedef long uid_t;
- typedef long gid_t;
- typedef ulong_t nlink_t;
+ typedef unsigned long ulong;
+
+
+ 32-bit Software
+ The data types listed below are defined in <sys/types.h> when compiling
+ in 32-bit mode (-m32).
+
+ typedef long id_t;
+ typedef ulong_t major_t;
+ typedef ulong_t minor_t;
typedef ulong_t mode_t;
- typedef short cnt_t;
- typedef long time_t;
- typedef int label_t[10];
- typedef ulong_t dev_t;
- typedef long off_t;
+ typedef ulong_t nlink_t;
typedef long pid_t;
- typedef long paddr_t;
- typedef int key_t;
- typedef unsigned char use_t;
- typedef short sysid_t;
- typedef short index_t;
- typedef short lock_t;
typedef unsigned int size_t;
- typedef long clock_t;
- typedef long pid_t;
+ typedef int ssize_t;
+ typedef long suseconds_t;
+
- 64-bit Solaris
- The data types listed below are defined in <sys/types.h> for 64-bit So-
- laris.
-
- typedef long blkcnt_t
- typedef long clock_t
- typedef long daddr_t
- typedef ulong_t dev_t
- typedef ulong_t fsblkcnt_t
- typedef ulong_t fsfilcnt_t
- typedef int gid_t
- typedef int id_t
- typedef long ino_t
- typedef int key_t
- typedef uint_t major_t
- typedef uint_t minor_t
- typedef uint_t mode_t
- typedef uint_t nlink_t
- typedef int pid_t
- typedef ptrdiff_t intptr_t
- typedef ulong_t rlim_t
- typedef ulong_t size_t
- typedef uint_t speed_t
- typedef long ssize_t
- typedef long suseconds_t
- typedef uint_t tcflag_t
- typedef long time_t
- typedef int uid_t
- typedef int wchar_t
+ The data types listed below are defined in <sys/types.h> when compiling
+ in 32-bit mode (-m32) and not compiling for large file support as de-
+ fined in lfcompile(7).
+
+ typedef ulong_t blkcnt_t;
+ typedef ulong_t fsblkcnt_t;
+ typedef ulong_t fsfilcnt_t;
+ typedef ulong_t ino_t;
+ typedef long off_t;
+
+
+
+ The data types listed below are defined in <sys/types.h> when compiling
+ in 32-bit mode (-m32) and compiling with large file support enabled as
+ defined in lfcompile(7).
+
+ typedef u_longlong_t blkcnt_t;
+ typedef u_longlong_t fsblkcnt_t;
+ typedef u_longlong_t fsfilcnt_t;
+ typedef u_longlong_t ino_t;
+ typedef longlong_t off_t;
+
+
+ 64-bit Software
+ The data types listed below are defined in <sys/types.h> when compiling
+ in 64-bit mode (-m64).
+
+ typedef ulong_t blkcnt_t;
+ typedef ulong_t fsblkcnt_t;
+ typedef ulong_t fsfilcnt_t;
+ typedef int id_t;
+ typedef ulong_t ino_t;
+ typedef uint_t major_t;
+ typedef uint_t minor_t;
+ typedef uint_t mode_t;
+ typedef uint_t nlink_t;
+ typedef long off_t;
+ typedef int pid_t;
+ typedef ulong_t size_t;
+ typedef long ssize_t;
Preprocessor Symbols
@@ -188,6 +215,7 @@
SEE ALSO
- types32.h(3HEAD), attributes(7), standards(7)
+ inttypes.h(3HEAD), stdint.h(3HEAD), types32.h(3HEAD), attributes(7),
+ lfcompile(7), standards(7)
-Oracle Solaris 11.4 6 Oct 2004 types.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 types.h(3HEAD)
diff -NurbBw 11.4.72/man3head/types32.h.3head 11.4.75/man3head/types32.h.3head
--- 11.4.72/man3head/types32.h.3head 2024-11-22 11:50:41.877159605 -0800
+++ 11.4.75/man3head/types32.h.3head 2024-11-22 11:52:08.443356785 -0800
@@ -31,8 +31,11 @@
typedef uint32_t rlim32_t
typedef uint32_t size32_t
typedef int32_t ssize32_t
- typedef time32_t int32_t
- typedef uid32_t int32_t
+ typedef int32_t time32_t
+ typedef int32_t uid32_t
-Oracle Solaris 11.4 30 Oct 1997 types32.h(3HEAD)
+SEE ALSO
+ types.h(3HEAD)
+
+Oracle Solaris 11.4 30 Aug 2024 types32.h(3HEAD)
diff -NurbBw 11.4.72/man3head/un.h.3head 11.4.75/man3head/un.h.3head
--- 11.4.72/man3head/un.h.3head 2024-11-22 11:50:41.905902672 -0800
+++ 11.4.75/man3head/un.h.3head 2024-11-22 11:52:08.474690240 -0800
@@ -17,7 +17,8 @@
The sockaddr_un structure is used to store addresses for UNIX domain
sockets. Values of this type must be cast to struct sockaddr for use
- with the socket interfaces.
+ with the socket interfaces. The sun_family member should be set to
+ AF_UNIX or its synonym AF_LOCAL.
The <sys/un.h> header defines the type sa_family_t as described in
@@ -36,7 +37,7 @@
SEE ALSO
- bind(3C), socket(3C), socketpair(3C), socket.h(3HEAD), attributes(7),
- standards(7)
+ bind(3C), connect(3C), getpeername(3C), getsockname(3C), socket(3C),
+ socketpair(3C), socket.h(3HEAD), attributes(7), standards(7)
-Oracle Solaris 11.4 30 Aug 2002 un.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 un.h(3HEAD)
diff -NurbBw 11.4.72/man3head/unistd.h.3head 11.4.75/man3head/unistd.h.3head
--- 11.4.72/man3head/unistd.h.3head 2024-11-22 11:50:41.947943670 -0800
+++ 11.4.75/man3head/unistd.h.3head 2024-11-22 11:52:08.521244375 -0800
@@ -7,15 +7,16 @@
#include <unistd.h>
DESCRIPTION
- The <unistd.h> header defines the symbolic constants and structures
- which are not already defined or declared in some other header. The
- contents of this header are shown below.
+ The <unistd.h> header defines a number of symbolic constants and struc-
+ tures which are not already defined or declared in some other header,
+ especially those required by the POSIX, SUS, and XPG standards. See
+ standards(7).
Version Test Macros
The following symbolic constants are defined (with fixed values):
_POSIX_VERSION Integer value indicating version of the POSIX
- standard (C language binding). See standards(7).
+ standard (C language binding).
_POSIX2_VERSION Integer value indicating version of the POSIX.2
@@ -474,8 +475,8 @@
- The following symbolic constants are defined for the access(2) func-
- tion:
+ The following symbolic constants are defined for the access(2) family
+ of functions:
R_OK Test for read permission.
@@ -524,35 +525,40 @@
The following symbolic constants are defined for the confstr(3C) func-
- tion for both SPARC and x86:
+ tion:
- _CS_LFS64_CFLAGS _CS_LFS64_LDFLAGS
- _CS_LFS64_LIBS _CS_LFS64_LINTFLAGS
_CS_LFS_CFLAGS _CS_LFS_LDFLAGS
_CS_LFS_LIBS _CS_LFS_LINTFLAGS
+ _CS_LFS64_CFLAGS _CS_LFS64_LDFLAGS
+ _CS_LFS64_LIBS _CS_LFS64_LINTFLAGS
_CS_PATH _CS_POSIX_V6_ILP32_OFF32_CFLAGS
_CS_POSIX_V6_ILP32_OFF32_LDFLAGS _CS_POSIX_V6_ILP32_OFF32_LIBS
_CS_POSIX_V6_ILP32_OFF32_LINTFLAGS _CS_POSIX_V6_ILP32_OFFBIG_CFLAGS
_CS_POSIX_V6_ILP32_OFFBIG_LDFLAGS _CS_POSIX_V6_ILP32_OFFBIG_LIBS
- _CS_POSIX_V6_ILP32_OFFBIG_LINTFLAGS _CS_POSIX_V6_WIDTH_RESTRICTED_ENV
- _CS_XBS5_ILP32_OFF32_CFLAGS _CS_XBS5_ILP32_OFF32_LDFLAGS
- _CS_XBS5_ILP32_OFF32_LIBS _CS_XBS5_ILP32_OFF32_LINTFLAGS
- _CS_XBS5_ILP32_OFFBIG_CFLAGS _CS_XBS5_ILP32_OFFBIG_LDFLAGS
- _CS_XBS5_ILP32_OFFBIG_LIBS _CS_XBS5_ILP32_OFFBIG_LINTFLAGS
-
-
-
- The following symbolic constants are defined for the confstr() function
- for SPARC only:
-
- _CS_POSIX_V6_LP64_OFF64_CFLAGS _CS_POSIX_V6_LP64_OFF64_LDFLAGS
- _CS_POSIX_V6_LP64_OFF64_LIBS _CS_POSIX_V6_LP64_OFF64_LINTFLAGS
- _CS_POSIX_V6_LPBIG_OFFBIG_CFLAGS _CS_POSIX_V6_LPBIG_OFFBIG_LDFLAGS
- _CS_POSIX_V6_LPBIG_OFFBIG_LIBS _CS_POSIX_V6_LPBIG_OFFBIG_LINTFLAGS
- _CS_XBS5_LP64_OFF64_CFLAGS _CS_XBS5_LP64_OFF64_LDFLAGS
- _CS_XBS5_LP64_OFF64_LIBS _CS_XBS5_LP64_OFF64_LINTFLAGS
- _CS_XBS5_LPBIG_OFFBIG_CFLAGS _CS_XBS5_LPBIG_OFFBIG_LDFLAGS
- _CS_XBS5_LPBIG_OFFBIG_LIBS _CS_XBS5_LPBIG_OFFBIG_LINTFLAGS
+ _CS_POSIX_V6_ILP32_OFFBIG_LINTFLAGS _CS_POSIX_V6_LP64_OFF64_CFLAGS
+ _CS_POSIX_V6_LP64_OFF64_LDFLAGS _CS_POSIX_V6_LP64_OFF64_LIBS
+ _CS_POSIX_V6_LP64_OFF64_LINTFLAGS _CS_POSIX_V6_LPBIG_OFFBIG_CFLAGS
+ _CS_POSIX_V6_LPBIG_OFFBIG_LDFLAGS _CS_POSIX_V6_LPBIG_OFFBIG_LIBS
+ _CS_POSIX_V6_LPBIG_OFFBIG_LINTFLAGS _CS_POSIX_V6_WIDTH_RESTRICTED_ENVS
+ _CS_POSIX_V7_ILP32_OFF32_CFLAGS _CS_POSIX_V7_ILP32_OFF32_LDFLAGS
+ _CS_POSIX_V7_ILP32_OFF32_LIBS _CS_POSIX_V7_ILP32_OFF32_LINTFLAGS
+ _CS_POSIX_V7_ILP32_OFFBIG_CFLAGS _CS_POSIX_V7_ILP32_OFFBIG_LDFLAGS
+ _CS_POSIX_V7_ILP32_OFFBIG_LIBS _CS_POSIX_V7_ILP32_OFFBIG_LINTFLAGS
+ _CS_POSIX_V7_LP64_OFF64_CFLAGS _CS_POSIX_V7_LP64_OFF64_LDFLAGS
+ _CS_POSIX_V7_LP64_OFF64_LIBS _CS_POSIX_V7_LP64_OFF64_LINTFLAGS
+ _CS_POSIX_V7_LPBIG_OFFBIG_CFLAGS _CS_POSIX_V7_LPBIG_OFFBIG_LDFLAGS
+ _CS_POSIX_V7_LPBIG_OFFBIG_LIBS _CS_POSIX_V7_LPBIG_OFFBIG_LINTFLAGS
+ _CS_POSIX_V7_THREADS_CFLAGS _CS_POSIX_V7_THREADS_LDFLAGS
+ _CS_POSIX_V7_WIDTH_RESTRICTED_ENVS _CS_V6_ENV
+ _CS_V7_ENV _CS_XBS5_ILP32_OFF32_CFLAGS
+ _CS_XBS5_ILP32_OFF32_LDFLAGS _CS_XBS5_ILP32_OFF32_LIBS
+ _CS_XBS5_ILP32_OFF32_LINTFLAGS _CS_XBS5_ILP32_OFFBIG_CFLAGS
+ _CS_XBS5_ILP32_OFFBIG_LDFLAGS _CS_XBS5_ILP32_OFFBIG_LIBS
+ _CS_XBS5_ILP32_OFFBIG_LINTFLAGS _CS_XBS5_LP64_OFF64_CFLAGS
+ _CS_XBS5_LP64_OFF64_LDFLAGS _CS_XBS5_LP64_OFF64_LIBS
+ _CS_XBS5_LP64_OFF64_LINTFLAGS _CS_XBS5_LPBIG_OFFBIG_CFLAGS
+ _CS_XBS5_LPBIG_OFFBIG_LDFLAGS _CS_XBS5_LPBIG_OFFBIG_LIBS
+ _CS_XBS5_LPBIG_OFFBIG_LINTFLAGS
@@ -560,68 +566,92 @@
tion:
_SC_2_C_BIND _SC_2_C_DEV
- _SC_2_C_VERSION _SC_2_FORT_DEV
- _SC_2_FORT_RUN _SC_2_LOCALEDEF
- _SC_2_PBS _SC_2_PBS_ACCOUNTING
- _SC_2_PBS_CHECKPOINT _SC_2_PBS_LOCATE
- _SC_2_PBS_MESSAGE _SC_2_PBS_TRACK
- _SC_2_SW_DEV _SC_2_UPE
- _SC_2_VERSION _SC_ADVISORY_INFO
+ _SC_2_C_VERSION _SC_2_CHAR_TERM
+ _SC_2_FORT_DEV _SC_2_FORT_RUN
+ _SC_2_LOCALEDEF _SC_2_PBS
+ _SC_2_PBS_ACCOUNTING _SC_2_PBS_CHECKPOINT
+ _SC_2_PBS_LOCATE _SC_2_PBS_MESSAGE
+ _SC_2_PBS_TRACK _SC_2_SW_DEV
+ _SC_2_UPE _SC_2_VERSION
+ _SC_ADI_METADATA_MAX _SC_ADVISORY_INFO
_SC_AIO_LISTIO_MAX _SC_AIO_MAX
- _SC_AIO_PRIO_DELTA_MAX _SC_ARG_MAX
- _SC_ASYNCHRONOUS_IO _SC_ATEXIT_MAX
- _SC_AVPHYS_PAGES _SC_BARRIERS
- _SC_BC_BASE_MAX _SC_BC_DIM_MAX
- _SC_BC_SCALE_MAX _SC_BC_STRING_MAX
- _SC_CHILD_MAX _SC_CLK_TCK
- _SC_CLOCK_SELECTION _SC_COLL_WEIGHTS_MAX
- _SC_CPUTIME _SC_DELAYTIMER_MAX
- _SC_EXPR_NEST_MAX _SC_FSYNC
- _SC_GETGR_R_SIZE_MAX _SC_GETPW_R_SIZE_MAX
- _SC_HOST_NAME_MAX _SC_IOV_MAX
- _SC_IPV6 _SC_JOB_CONTROL
- _SC_LINE_MAX _SC_LOGIN_NAME_MAX
- _SC_LOGNAME_MAX _SC_MAPPED_FILES
+ _SC_AIO_PRIO_DELTA_MAX _SC_AIO_VERSION
+ _SC_ARG_MAX _SC_ASYNCHRONOUS_IO
+ _SC_ATEXIT_MAX _SC_AVPHYS_PAGES
+ _SC_BARRIERS _SC_BC_BASE_MAX
+ _SC_BC_DIM_MAX _SC_BC_SCALE_MAX
+ _SC_BC_STRING_MAX _SC_CHILD_MAX
+ _SC_CLK_TCK _SC_CLOCK_SELECTION
+ _SC_COHER_BLKSZ _SC_COLL_WEIGHTS_MAX
+ _SC_CPUID_MAX _SC_CPUID_SEQ_MAX
+ _SC_CPUTIME _SC_DCACHE_ASSOC
+ _SC_DCACHE_BLKSZ _SC_DCACHE_LINESZ
+ _SC_DCACHE_SZ _SC_DCACHE_TBLKSZ
+ _SC_DELAYTIMER_MAX _SC_DEVT_VERSION
+ _SC_EPHID_MAX _SC_EXPR_NEST_MAX
+ _SC_FSYNC _SC_GETGR_R_SIZE_MAX
+ _SC_GETPW_R_SIZE_MAX _SC_HOST_NAME_MAX
+ _SC_ICACHE_ASSOC _SC_ICACHE_BLKSZ
+ _SC_ICACHE_LINESZ _SC_ICACHE_SZ
+ _SC_IOV_MAX _SC_IPV6
+ _SC_JOB_CONTROL _SC_L2CACHE_ASSOC
+ _SC_L2CACHE_LINESZ _SC_L2CACHE_SZ
+ _SC_L3CACHE_ASSOC _SC_L3CACHE_LINESZ
+ _SC_L3CACHE_SZ _SC_LINE_MAX
+ _SC_LOGIN_NAME_MAX _SC_LOGNAME_MAX
+ _SC_MAPPED_FILES _SC_MAX_CONCURRENCY
+ _SC_MAXPID _SC_MC_VERSION
_SC_MEMLOCK _SC_MEMLOCK_RANGE
- _SC_MEMORY_PROTECTION _SC_MESSAGE_PASSING
- _SC_MONOTONIC_CLOCK _SC_MQ_OPEN_MAX
- _SC_MQ_PRIO_MAX _SC_NGROUPS_MAX
- _SC_NPROCESSORS_CONF _SC_NPROCESSORS_ONLN
- _SC_OPEN_MAX _SC_PAGESIZE
- _SC_PAGE_SIZE _SC_PASS_MAX
- _SC_PHYS_PAGES _SC_PRIORITIZED_IO
- _SC_PRIORITY_SCHEDULING _SC_RAW_SOCKETS
- _SC_READER_WRITER_LOCKS _SC_REALTIME_SIGNALS
- _SC_REGEXP _SC_RE_DUP_MAX
+ _SC_MEMORY_PROTECTION _SC_MEMTYPE_VERSION
+ _SC_MESSAGE_PASSING _SC_MONOTONIC_CLOCK
+ _SC_MQ_OPEN_MAX _SC_MQ_PRIO_MAX
+ _SC_MRP_VERSION _SC_NGROUPS_MAX
+ _SC_NPROCESSORS_CONF _SC_NPROCESSORS_MAX
+ _SC_NPROCESSORS_ONLN _SC_OPEN_MAX
+ _SC_OSM_PAGESIZE_MIN _SC_OSM_VERSION
+ _SC_PAGE_SIZE _SC_PAGESIZE
+ _SC_PASS_MAX _SC_PHYS_PAGES
+ _SC_PRIORITIZED_IO _SC_PRIORITY_SCHEDULING
+ _SC_RAW_SOCKETS _SC_RCTL_VAL_MAX_NUM
+ _SC_RE_DUP_MAX _SC_READER_WRITER_LOCKS
+ _SC_REALTIME_SIGNALS _SC_REGEXP
_SC_RTSIG_MAX _SC_SAVED_IDS
- _SC_SEMAPHORES _SC_SEM_NSEMS_MAX
- _SC_SEM_VALUE_MAX _SC_SHARED_MEMORY_OBJECTS
+ _SC_SEM_NSEMS_MAX _SC_SEM_VALUE_MAX
+ _SC_SEMAPHORES _SC_SHARED_MEMORY_OBJECTS
_SC_SHELL _SC_SIGQUEUE_MAX
+ _SC_SIGRT_MAX _SC_SIGRT_MIN
_SC_SPAWN _SC_SPIN_LOCKS
- _SC_SPORADIC_SERVER _SC_SS_REPL_MAX
+ _SC_SPLIT_CACHE _SC_SPORADIC_SERVER
+ _SC_SS_REPL_MAX _SC_STACK_PROT
_SC_STREAM_MAX _SC_SYMLOOP_MAX
- _SC_SYNCHRONIZED_IO _SC_THREAD_ATTR_STACKADDR
- _SC_THREAD_ATTR_STACKSIZE _SC_THREAD_CPUTIME
- _SC_THREAD_DESTRUCTOR_ITERATIONS _SC_THREAD_KEYS_MAX
- _SC_THREAD_PRIO_INHERIT _SC_THREAD_PRIO_PROTECT
- _SC_THREAD_PRIORITY_SCHEDULING _SC_THREAD_PROCESS_SHARED
- _SC_THREAD_SPORADIC_SERVER _SC_THREADS
- _SC_THREAD_SAFE_FUNCTIONS _SC_THREAD_STACK_MIN
- _SC_THREAD_THREADS_MAX _SC_TIMEOUTS
- _SC_TIMER_MAX _SC_TIMERS
- _SC_TRACE _SC_TRACE_EVENT_FILTER
- _SC_TRACE_EVENT_NAME_MAX _SC_TRACE_INHERIT
- _SC_TRACE_LOG _SC_TRACE_NAME_MAX
- _SC_TRACE_SYS_MAX _SC_TRACE_USER_EVENT_MAX
- _SC_TTY_NAME_MAX _SC_TYPED_MEMORY_OBJECTS
- _SC_TZNAME_MAX _SC_V6_ILP32_OFF32
- _SC_V6_ILP32_OFFBIG _SC_V6_LP64_OFF64
- _SC_V6_LPBIG_OFFBIG _SC_VERSION
- _SC_XBS5_ILP32_OFF32 _SC_XBS5_ILP32_OFFBIG
- _SC_XBS5_LP64_OFF64 _SC_XBS5_LPBIG_OFFBIG
+ _SC_SYNCHRONIZED_IO _SC_T_IOV_MAX
+ _SC_THREAD_ATTR_STACKADDR _SC_THREAD_ATTR_STACKSIZE
+ _SC_THREAD_CPUTIME _SC_THREAD_DESTRUCTOR_ITERATIONS
+ _SC_THREAD_KEYS_MAX _SC_THREAD_PRIO_INHERIT
+ _SC_THREAD_PRIO_PROTECT _SC_THREAD_PRIORITY_SCHEDULING
+ _SC_THREAD_PROCESS_SHARED _SC_THREAD_ROBUST_PRIO_INHERIT
+ _SC_THREAD_ROBUST_PRIO_PROTECT _SC_THREAD_SAFE_FUNCTIONS
+ _SC_THREAD_SPORADIC_SERVER _SC_THREAD_STACK_MIN
+ _SC_THREAD_THREADS_MAX _SC_THREADS
+ _SC_TIMEOUTS _SC_TIMER_MAX
+ _SC_TIMERS _SC_TRACE
+ _SC_TRACE_EVENT_FILTER _SC_TRACE_EVENT_NAME_MAX
+ _SC_TRACE_INHERIT _SC_TRACE_LOG
+ _SC_TRACE_NAME_MAX _SC_TRACE_SYS_MAX
+ _SC_TRACE_USER_EVENT_MAX _SC_TTY_NAME_MAX
+ _SC_TYPED_MEMORY_OBJECTS _SC_TZNAME_MAX
+ _SC_V6_ILP32_OFF32 _SC_V6_ILP32_OFFBIG
+ _SC_V6_LP64_OFF64 _SC_V6_LPBIG_OFFBIG
+ _SC_V7_ILP32_OFF32 _SC_V7_ILP32_OFFBIG
+ _SC_V7_LP64_OFF64 _SC_V7_LPBIG_OFFBIG
+ _SC_VERSION _SC_XBS5_ILP32_OFF32
+ _SC_XBS5_ILP32_OFFBIG _SC_XBS5_LP64_OFF64
+ _SC_XBS5_LPBIG_OFFBIG _SC_XOPEN_ARMOR
_SC_XOPEN_CRYPT _SC_XOPEN_ENH_I18N
- _SC_XOPEN_SHM _SC_XOPEN_STREAMS
- _SC_XOPEN_UNIX _SC_XOPEN_VERSION
+ _SC_XOPEN_LEGACY _SC_XOPEN_REALTIME
+ _SC_XOPEN_REALTIME_THREADS _SC_XOPEN_SHM
+ _SC_XOPEN_STREAMS _SC_XOPEN_UNIX
+ _SC_XOPEN_UUCP _SC_XOPEN_VERSION
_SC_XOPEN_XCU_VERSION
@@ -633,15 +663,19 @@
The following symbolic constants are defined for the fpathconf(2) func-
tion:
- _PC_2_SYMLINKS _PC_ALLOC_SIZE_MIN
- _PC_ASYNC_IO _PC_CHOWN_RESTRICTED
- _PC_FILESIZEBITS _PC_LINK_MAX
+ _PC_2_SYMLINKS _PC_ACCESS_FILTERING
+ _PC_ACL_ENABLED _PC_ALLOC_SIZE_MIN
+ _PC_ASYNC_IO _PC_CASE_BEHAVIOR
+ _PC_CHOWN_RESTRICTED _PC_FILESIZEBITS
+ _PC_LAST _PC_LINK_MAX
_PC_MAX_CANON _PC_MAX_INPUT
- _PC_NAME_MAX _PC_NO_TRUNC
- _PC_PATH_MAX _PC_PIPE_BUF
- _PC_PRIO_IO _PC_REC_INCR_XFER_SIZE
- _PC_REC_MAX_XFER_SIZE _PC_REC_MIN_XFER_SIZE
- _PC_REC_XFER_ALIGN _PC_SYMLINK_MAX
+ _PC_MIN_HOLE_SIZE _PC_NAME_MAX
+ _PC_NO_TRUNC _PC_PATH_MAX
+ _PC_PIPE_BUF _PC_PRIO_IO
+ _PC_REC_INCR_XFER_SIZE _PC_REC_MAX_XFER_SIZE
+ _PC_REC_MIN_XFER_SIZE _PC_REC_XFER_ALIGN
+ _PC_REFLINK_ENABLED _PC_SATTR_ENABLED
+ _PC_SATTR_EXISTS _PC_SYMLINK_MAX
_PC_SYNC_IO _PC_TIMESTAMP_RESOLUTION
_PC_VDISABLE _PC_XATTR_ENABLED
_PC_XATTR_EXISTS
@@ -685,4 +719,4 @@
lockf(3C), sysconf(3C), termios(3C), termio(4I), group(5), passwd(5),
attributes(7), standards(7)
-Oracle Solaris 11.4 1 Sep 2009 unistd.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 unistd.h(3HEAD)
diff -NurbBw 11.4.72/man3head/values.h.3head 11.4.75/man3head/values.h.3head
--- 11.4.72/man3head/values.h.3head 2024-11-22 11:50:41.978859162 -0800
+++ 11.4.75/man3head/values.h.3head 2024-11-22 11:52:08.553154248 -0800
@@ -72,6 +72,6 @@
SEE ALSO
- math.h(3HEAD) intro(3)
+ limits.h(3HEAD), math.h(3HEAD), Intro(3)
-Oracle Solaris 11.4 2 Mar 1993 values.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 values.h(3HEAD)
diff -NurbBw 11.4.72/man3head/wait.h.3head 11.4.75/man3head/wait.h.3head
--- 11.4.72/man3head/wait.h.3head 2024-11-22 11:50:42.011410571 -0800
+++ 11.4.75/man3head/wait.h.3head 2024-11-22 11:52:08.584738304 -0800
@@ -22,7 +22,7 @@
macro evaluates to the exit code that the child
process passed to _exit() (see exit(2)) or
exit(3C), or the value that the child process re-
- turned from main.
+ turned from main().
WIFCONTINUED(stat) Evaluates to a non-zero value if status was re-
@@ -89,22 +89,18 @@
The type idtype_t is defined as an enumeration type whose possible val-
ues include the following:
-
P_ALL
P_PID
P_PGID
+ The id_t and pid_t types are defined as described in types.h(3HEAD).
-
- The id_t and pid_t types are defined as described in <sys/types.h>.
-
-
- The siginfo_t type is defined as described in <signal.h>.
+ The siginfo_t type is defined as described in signal.h(3HEAD).
- The rusage structure is defined as described in <sys/resource.h>.
+ The rusage structure is defined as described in resource.h(3HEAD).
Inclusion of the <sys/wait.h> header can also make visible all symbols
@@ -123,7 +119,7 @@
SEE ALSO
- exit(2), waitid(2), exit(3C), wait(3C), waitpid(3C), attributes(7),
- standards(7)
+ exit(2), waitid(2), exit(3C), wait(3C), waitpid(3C), resource.h(3HEAD),
+ signal.h(3HEAD), types.h(3HEAD), attributes(7), standards(7)
-Oracle Solaris 11.4 14 May 2018 wait.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 wait.h(3HEAD)
diff -NurbBw 11.4.72/man3head/wchar.h.3head 11.4.75/man3head/wchar.h.3head
--- 11.4.72/man3head/wchar.h.3head 2024-11-22 11:50:42.045678870 -0800
+++ 11.4.75/man3head/wchar.h.3head 2024-11-22 11:52:08.616767722 -0800
@@ -9,7 +9,7 @@
DESCRIPTION
The <wchar.h> header defines the following types:
- wchar_t As described in <stddef.h>.
+ wchar_t As described in stddef.h(3HEAD).
wint_t An integer type capable of storing any valid value of
@@ -28,16 +28,16 @@
state, the results are unspecified.
- FILE As described in <stdio.h>.
+ FILE As described in stdio.h(3HEAD).
- size_t As described in <stddef.h>.
+ size_t As described in stddef.h(3HEAD).
- va_list As described in <stdarg.h>.
+ va_list As described in stdarg(3EXT).
- locale_t As described in <locale.h>.
+ locale_t As described in locale.h(3HEAD).
@@ -61,12 +61,12 @@
several WP functions to indicate end-of-file.
- NULL As described in <stddef.h>.
+ NULL As described in stddef.h(3HEAD).
The tag tm is declared as naming an incomplete structure type, the con-
- tents of which are described in the header <time.h>.
+ tents of which are described in the header time.h(3HEAD).
Inclusion of the <wchar.h> header can make visible all symbols from the
@@ -88,14 +88,14 @@
SEE ALSO
getconf(1), btowc(3C), confstr(3C), fgetwc(3C), fputwc(3C), fputws(3C),
fwide(3C), fwprintf(3C), fwscanf(3C), getwc(3C), getwchar(3C),
- getws(3C), iswalpha(3C), iswctype(3C), mbrlen(3C), mbrtowc(3C), mb-
- sinit(3C), mbsrtowcs(3C), towlower(3C), towupper(3C), ungetwc(3C), vfw-
- printf(3C), wcrtomb(3C), wcscoll(3C), wcsftime(3C), wcsrtombs(3C), wc-
- sstr(3C), wcstod(3C), wcstol(3C), wcstoul(3C), wcstring(3C), wc-
- swidth(3C), wcsxfrm(3C), wctob(3C), wctype(3C), wcwidth(3C), wmem-
- chr(3C), wmemcmp(3C), wmemcpy(3C), wmemmove(3C), wmemset(3C),
+ getws(3C), iswalpha(3C), iswctype(3C), mbrlen(3C), mbrtowc(3C),
+ mbsinit(3C), mbsrtowcs(3C), towlower(3C), towupper(3C), ungetwc(3C),
+ vfwprintf(3C), wcrtomb(3C), wcscoll(3C), wcsftime(3C), wcsrtombs(3C),
+ wcsstr(3C), wcstod(3C), wcstol(3C), wcstoul(3C), wcstring(3C),
+ wcswidth(3C), wcsxfrm(3C), wctob(3C), wctype(3C), wcwidth(3C),
+ wmemchr(3C), wmemcmp(3C), wmemcpy(3C), wmemmove(3C), wmemset(3C),
stdarg(3EXT), locale.h(3HEAD), stddef.h(3HEAD), stdio.h(3HEAD),
- stdlib.h(3HEAD), string.h(3HEAD), time.h(3HEAD), wctype.h(3HEAD), at-
- tributes(7), standards(7)
+ stdlib.h(3HEAD), string.h(3HEAD), time.h(3HEAD), uchar.h(3HEAD),
+ wctype.h(3HEAD), attributes(7), standards(7)
-Oracle Solaris 11.4 11 May 2021 wchar.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 wchar.h(3HEAD)
diff -NurbBw 11.4.72/man3head/wctype.h.3head 11.4.75/man3head/wctype.h.3head
--- 11.4.72/man3head/wctype.h.3head 2024-11-22 11:50:42.074563446 -0800
+++ 11.4.75/man3head/wctype.h.3head 2024-11-22 11:52:08.648251817 -0800
@@ -9,14 +9,14 @@
DESCRIPTION
The <wctype.h> header defines the following types:
- wint_t As described in <wchar.h>.
+ wint_t As described in wchar.h(3HEAD).
wctrans_t A scalar type that can hold values that represent locale-
specific character mappings.
- wctype_t As described in <wchar.h>.
+ wctype_t As described in wchar.h(3HEAD).
@@ -57,6 +57,6 @@
setlocale(3C), iswalpha(3C), iswctype(3C), towctrans(3C), towlower(3C),
towupper(3C), wctrans(3C), wctype(3C), stdarg(3EXT), locale.h(3HEAD),
stddef.h(3HEAD), stdio.h(3HEAD), stdlib.h(3HEAD), string.h(3HEAD),
- time.h(3HEAD), attributes(7), standards(7)
+ time.h(3HEAD), wchar.h(3HEAD), attributes(7), standards(7)
-Oracle Solaris 11.4 10 Sep 2004 wctype.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 wctype.h(3HEAD)
diff -NurbBw 11.4.72/man3head/wordexp.h.3head 11.4.75/man3head/wordexp.h.3head
--- 11.4.72/man3head/wordexp.h.3head 2024-11-22 11:50:42.104821211 -0800
+++ 11.4.75/man3head/wordexp.h.3head 2024-11-22 11:52:08.680075443 -0800
@@ -49,9 +49,9 @@
The following constants are defined as error return values:
- WRDE_BADCHAR One of the unquoted characters--<newline>, '|', '&',
- ';', '<', '>', '(', ')', '{', '}'--appears in words in
- an inappropriate context.
+ WRDE_BADCHAR One of the unquoted characters <newline>, '|', '&',
+ ';', '<', '>', '(', ')', '{', or '}' appears in words
+ in an inappropriate context.
WRDE_BADVAL Reference to undefined shell variable when WRDE_UNDEF
@@ -75,7 +75,7 @@
The <wordexp.h> header defines the following type:
- size_t As described in <stddef.h>.
+ size_t As described in stddef.h(3HEAD).
ATTRIBUTES
@@ -93,4 +93,4 @@
SEE ALSO
wordexp(3C), attributes(7), standards(7)
-Oracle Solaris 11.4 10 Sep 2004 wordexp.h(3HEAD)
+Oracle Solaris 11.4 30 Aug 2024 wordexp.h(3HEAD)
diff -NurbBw 11.4.72/man4i/hdio.4i 11.4.75/man4i/hdio.4i
--- 11.4.72/man4i/hdio.4i 2024-11-22 11:50:42.137361448 -0800
+++ 11.4.75/man4i/hdio.4i 1969-12-31 16:00:00.000000000 -0800
@@ -1,93 +0,0 @@
-hdio(4I) Ioctls for a class of drivers or subsystems hdio(4I)
-
-NAME
- hdio - SMD and IPI disk control operations
-
-SYNOPSIS
- #include <sys/hdio.h>
-
-DESCRIPTION
- Note -
-
-
-
- The SMD and IPI drivers have been discontinued. dkio(4I) is now the
- preferred method for retrieving disk information.
-
-
-
- The SMD and IPI disk drivers supplied with previous releases supported
- a set of ioctl(2) requests for diagnostics and bad sector information.
- Basic to these ioctl() requests are the definitions in <sys/hdio.h>.
-
-IOCTLS
- HDKIOCGTYPE The argument is a pointer to a hdk_type structure (de-
- scribed below). This ioctl() gets specific information
- from the hard disk.
-
-
- HDKIOCSTYPE The argument is a pointer to a hdk_type structure (de-
- scribed below). This ioctl() sets specific information
- about the hard disk.
-
-
- /*
- * Used for drive info
- */
- struct hdk_type {
- ushort_t hdkt_hsect; /* hard sector count (read only) */
- ushort_t hdkt_promrev; /* prom revision (read only) */
- uchar_t hdkt_drtype; /* drive type (ctlr specific) */
- uchar_t hdkt_drstat; /* drive status (ctlr specific, ro) */
- };
-
-
- HDKIOCGBAD The argument is a pointer to a hdk_badmap structure (de-
- scribed below). This ioctl() is used to get the bad sec-
- tor map from the disk.
-
-
- HDKIOCSBAD The argument is a pointer to a hdk_badmap structure (de-
- scribed below). This ioctl() is used to set the bad sec-
- tor map on the disk.
-
-
- /*
- * Used for bad sector map
- */
- struct hdk_badmap {
- caddr_t hdkb_bufaddr; /* address of user's map buffer */
- };
-
-
- HDKIOCGDIAG The argument is a pointer to a hdk_diag structure (de-
- scribed below). This ioctl() gets the most recent com-
- mand that failed along with the sector and error number
- from the hard disk.
-
-
- /*
- * Used for disk diagnostics
- */
- struct hdk_diag {
- ushort_t hdkd_errcmd; /* most recent command in error */
- daddr_t hdkd_errsect; /* most recent sector in error */
- uchar_t hdkd_errno; /* most recent error number */
- uchar_t hdkd_severe; /* severity of most recent error */
- };
-
-
-ATTRIBUTES
- See attributes(7) for a description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Obsolete |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- ioctl(2), dkio(4I)
-
-Oracle Solaris 11.4 14 Jun 2024 hdio(4I)
diff -NurbBw 11.4.72/man5/nscd.conf.5 11.4.75/man5/nscd.conf.5
--- 11.4.72/man5/nscd.conf.5 2024-11-22 11:50:42.172811159 -0800
+++ 11.4.75/man5/nscd.conf.5 2024-11-22 11:52:08.719195022 -0800
@@ -90,18 +90,21 @@
debug_level value
Specifies the desired debug level. The default value is "None". Use
- the svccfg describe command to list available levels. Note that the
- configuration values and the debug level output can change at any
- time, so do not depend upon this information in scripts.
+ the svccfg -s name-service/cache describe -tv config/debug_level
+ command to list available levels. Note that the configuration val-
+ ues and the debug level output can change at any time, so do not
+ depend upon this information in scripts.
debug_components value
Specifies the nscd components that should generate debug messages.
- The default value is "None". Use the svccfg describe command to
- view the available components and a brief description of each. Note
- that the configuration values and the component output can change
- at any time, so do not depend upon this information in scripts.
+ The default value is "None". Use the
+ svccfg -s name-service/cache describe -tv config/debug_components
+ command to view the available components and a brief description of
+ each. Note that the configuration values and the component output
+ can change at any time, so do not depend upon this information in
+ scripts.
Cache Configuration Groups
@@ -376,4 +379,4 @@
Starting with Oracle Solaris 11.4.57, the obsolete svc:/system/name-
service-cache was removed.
-Oracle Solaris 11.4 11 Apr 2024 nscd.conf(5)
+Oracle Solaris 11.4 29 Jul 2024 nscd.conf(5)
diff -NurbBw 11.4.72/man7/audit_syslog.7 11.4.75/man7/audit_syslog.7
--- 11.4.72/man7/audit_syslog.7 2024-11-22 11:50:42.207511138 -0800
+++ 11.4.75/man7/audit_syslog.7 2024-11-22 11:52:08.756037478 -0800
@@ -26,7 +26,7 @@
The syslog header contains the date and time the message was processed
- by syslog (this may be different to the actual audit event time) the
+ by syslog (this may be different to the actual audit event time), the
host name from which it was sent, auditd to indicate that it was gener-
ated by the audit daemon, an ID field used internally by the syslog
daemon, and audit.notice indicating the syslog facility and severity
@@ -131,9 +131,9 @@
OBJECT ATTRIBUTES
- The p_flag attribute is used to further filter audit data being sent to
- the rsyslog daemon beyond the classes specified through the flags and
- naflags (see auditconfig(8)) and through the user-specific lines of
+ The p_flags attribute is used to further filter audit data being sent
+ to the rsyslog daemon beyond the classes specified through the flags
+ and naflags (see auditconfig(8)) and through the user-specific lines of
user_attr(5). The parameter is a comma-separated list; each item repre-
sents an audit class (see audit_class(5)) and is specified using the
syntax described in audit_flags(7). The default (empty p_flags listed)
@@ -260,6 +260,14 @@
field shows the same whole second or at most a few seconds difference.
HISTORY
+ The access and proto fields, and the p_event_ts attribute, were added
+ in Oracle Solaris 11.4.72.
+
+
+ The optional event timestamp field, and the p_cache_ttl attribute to
+ enable it, were added in Oracle Solaris 11.4.16.
+
+
The audit_syslog module was introduced in Solaris 10 3/05.
-Oracle Solaris 11.4 12 Mar 2024 au...g(7)
+Oracle Solaris 11.4 13 Sep 2024 au...g(7)
diff -NurbBw 11.4.72/man7/pam_krb5.7 11.4.75/man7/pam_krb5.7
--- 11.4.72/man7/pam_krb5.7 2024-11-22 11:50:42.250365018 -0800
+++ 11.4.75/man7/pam_krb5.7 2024-11-22 11:52:08.801783264 -0800
@@ -808,6 +808,9 @@
credentials are about to expire.
HISTORY
+ The warndays option was added in Oracle Solaris 11.4.72.
+
+
The pam_krb5 module was introduced in Solaris 8.
-Oracle Solaris 11.4 27 Mar 2024 pa...5(7)
+Oracle Solaris 11.4 13 Sep 2024 pa...5(7)
diff -NurbBw 11.4.72/man7/pam_unix_session.7 11.4.75/man7/pam_unix_session.7
--- 11.4.72/man7/pam_unix_session.7 2024-11-22 11:50:42.279626760 -0800
+++ 11.4.75/man7/pam_unix_session.7 2024-11-22 11:52:08.837175709 -0800
@@ -83,4 +83,8 @@
bug option. Prior to that, this work was performed in the pam_unix mod-
ule.
-Oracle Solaris 11.4 12 Sep 2023 pa...n(7)
+HISTORY
+ The display of last login time was moved from the individual programs
+ to the pam_unix_session module in Oracle Solaris 11.3.0.
+
+Oracle Solaris 11.4 13 Sep 2024 pa...n(7)
diff -NurbBw 11.4.72/man8/admhist.8 11.4.75/man8/admhist.8
--- 11.4.72/man8/admhist.8 2024-11-22 11:50:42.314956644 -0800
+++ 11.4.75/man8/admhist.8 2024-11-22 11:52:08.872910631 -0800
@@ -193,6 +193,9 @@
Managing Auditing in Oracle Solaris 11.4
HISTORY
+ The -u option was added in Oracle Solaris 11.4.36.
+
+
The admhist command was added in Oracle Solaris 11.4.0.
-Oracle Solaris 11.4 16 Feb 2023 admhist(8)
+Oracle Solaris 11.4 13 Sep 2024 admhist(8)
diff -NurbBw 11.4.72/man8/beadm.8 11.4.75/man8/beadm.8
--- 11.4.72/man8/beadm.8 2024-11-22 11:50:42.362395920 -0800
+++ 11.4.75/man8/beadm.8 2024-11-22 11:52:08.922493348 -0800
@@ -1137,4 +1137,30 @@
SEE ALSO
zpool(8), zfs(8), fmri(7), attributes(7)
-Oracle Solaris 11.4 18 August 2020 beadm(8)
+HISTORY
+ The pool_version property was added in Oracle Solaris 11.4.30.
+
+
+ The auto policy was added in Oracle Solaris 11.4.20.
+
+
+ Support for using FMRIs to name BEs, and for managing non-global zone
+ BEs from the global zone, including the -o, -z, and -Z options to the
+ list subcommand, was added in Oracle Solaris 11.4.0. The -p option to
+ the create subcommand was removed in Oracle Solaris 11.4.0.
+
+
+ Support for handling orphaned BEs, including the -O option to the
+ destroy subcommand, and the O flag in the output of the list subcom-
+ mand, was added in Oracle Solaris 11.3.0.
+
+
+ Support for VersaBoot, including the -b to the mount subcommand, the B
+ flag in the output of the list subcommand, and the set-policy subcom-
+ mand with the noevict and static policies was added in Oracle Solaris
+ 11.2.8.
+
+
+ The beadm command was introduced in Oracle Solaris 11.0.0.
+
+Oracle Solaris 11.4 13 Sep 2024 beadm(8)
diff -NurbBw 11.4.72/man8/df.8 11.4.75/man8/df.8
--- 11.4.72/man8/df.8 2024-11-22 11:50:42.403430852 -0800
+++ 11.4.75/man8/df.8 2024-11-22 11:52:08.958840122 -0800
@@ -356,12 +356,47 @@
to a maximum of 512 Mbytes) depending on the number of cylinder groups
present in the file system.
+HISTORY
+ Support for the --scale and -H options was added to the df command in
+ Oracle Solaris 11.4.30.
- In previous releases of Solaris, there was a /usr/ucb/df command which
- had some differences from the df command described here. There are se-
- mantic differences with the -t and -i options. The -t option of
- /usr/ucb/df refers to the file system type, while the -t option for the
- df described here prints full listings with totals. The -i option of
- /usr/ucb/df is equivalent to the -o i option of df.
-Oracle Solaris 11.4 23 August 2022 df(8)
+ The /usr/xpg4/bin/df command was merged into the /usr/bin/df command in
+ the Solaris 11.0.0 release. This enabled use of the -v option with
+ /usr/bin/df, and the use of -P with /usr/xpg4/bin/df.
+
+
+ Support for the -Z option was added in Solaris 10 3/05.
+
+
+ Support for the -h option was added in Solaris 9.
+
+
+ Support for the -v option was added to the /usr/bin/df command in So-
+ laris 2.6.
+
+
+ The /usr/xpg4/bin/df command, including support for all previous op-
+ tions and the added -P option was added in Solaris 2.5.
+
+
+ Support for the -b, -e, -g, -k, -l, -n, -o, -t (for totals), -F, and -V
+ options was added to /usr/bin/df in Solaris 2.0.
+
+
+ In the Solaris 2.0 through 11.3 releases, there was a /usr/ucb/df com-
+ mand which had some differences from the df command described here, for
+ compatibility with the SunOS 4.x/Solaris 1.x version of /usr/bin/df.
+ The -t option of /usr/ucb/df specified the file system type, as does
+ the -F option of /usr/bin/df, while the -t option for /usr/bin/df
+ prints full listings with totals. The -i option of /usr/ucb/df was
+ equivalent to the -o i option of /usr/bin/df. /usr/ucb/df enabled the
+ -k option by default.
+
+
+ The /usr/bin/df command, including support for the -a option has been
+ included in all Sun and Oracle releases of Solaris. The Solaris 1.x
+ version of the command also supported different functionality for the
+ -i and -t options, as described above.
+
+Oracle Solaris 11.4 13 Sep 2024 df(8)
diff -NurbBw 11.4.72/man8/dladm.8 11.4.75/man8/dladm.8
--- 11.4.72/man8/dladm.8 2024-11-22 11:50:42.536890342 -0800
+++ 11.4.75/man8/dladm.8 2024-11-22 11:52:09.096231767 -0800
@@ -8,7 +8,7 @@
dladm show-link [-PZ] [[-p] -o field[,...]] [-z zone[,...]] [link]
- dladm rename-link [-R root-dir] link new-link
+ dladm rename-link link new-link
dladm delete-phys phys-link
@@ -16,45 +16,45 @@
[-z zone[,...]] [[-D [dcb-feature]] [-lr]] [-G] [phys-link]
- dladm create-aggr [-t] [-R root-dir] [-m mode] [-P policy] [-L lacpmode]
+ dladm create-aggr [-t] [-m mode] [-P policy] [-L lacpmode]
[-T time] [-u address] -l ether-link1 [-l ether-link2...] aggr-link
- dladm modify-aggr [-t] [-R root-dir] [-P policy] [-L lacpmode]
+ dladm modify-aggr [-t] [-P policy] [-L lacpmode]
[-T time] [-u address] aggr-link
- dladm delete-aggr [-t] [-R root-dir] aggr-link
- dladm add-aggr [-t] [-R root-dir] -l ether-link1 [-l ether-link2...]
+ dladm delete-aggr [-t] aggr-link
+ dladm add-aggr [-t] -l ether-link1 [-l ether-link2...]
aggr-link
- dladm remove-aggr [-t] [-R root-dir] -l ether-link1 [-l ether-link2...]
+ dladm remove-aggr [-t] -l ether-link1 [-l ether-link2...]
aggr-link
dladm show-aggr [-PLxZSCv] [[-p] -o field[,...]] [-z zone[,...]]
[aggr-link]
- dladm create-bridge [-P protect] [-R root-dir] [-p priority]
+ dladm create-bridge [-P protect] [-p priority]
[-m max-age] [-h hello-time] [-d forward-delay]
[-f force-protocol] [-l link...] bridge-name
- dladm modify-bridge [-P protect] [-R root-dir] [-p priority]
+ dladm modify-bridge [-P protect] [-p priority]
[-m max-age] [-h hello-time] [-d forward-delay]
[-f force-protocol] bridge-name
- dladm delete-bridge [-R root-dir] bridge-name
- dladm add-bridge [-R root-dir] -l link [-l link...] bridge-name
- dladm remove-bridge [-R root-dir] -l link [-l link...] bridge-name
+ dladm delete-bridge bridge-name
+ dladm add-bridge -l link [-l link...] bridge-name
+ dladm remove-bridge -l link [-l link...] bridge-name
dladm show-bridge [-flt] [[-p] -o field,...]
[bridge-name]
- dladm create-vlan [-ft] [-R root-dir] -l ether-link
+ dladm create-vlan [-ft] -l ether-link
-v vid[,pvlan-svid[,pvlan-type]] [vlan-link]
- dladm modify-vlan [-t] [-R root-dir] [-l ether-link]
+ dladm modify-vlan [-t] [-l ether-link]
[-v vid[,pvlan-svid[,pvlan-type]] [-f]]
{vlan-link,[vlan-link,...] | -L ether-link}
- dladm delete-vlan [-t] [-R root-dir] vlan-link
+ dladm delete-vlan [-t] vlan-link
dladm show-vlan [-PZ] [[-p] -o field[,...]] [-z zone[,...]] [vlan-link]
- dladm create-wlan [-R root-dir] [-p prop=value[,...]] <wlan-name>
- dladm delete-wlan [-R root-dir] <wlan-name>
- dladm set-wlan [-R root-dir] -p prop=value[,...] <wlan-name>
- dladm reset-wlan [-R root-dir] -p prop=value[,...] <wlan-name>
+ dladm create-wlan [-p prop=value[,...]] <wlan-name>
+ dladm delete-wlan <wlan-name>
+ dladm set-wlan -p prop=value[,...] <wlan-name>
+ dladm reset-wlan -p prop=value[,...] <wlan-name>
dladm show-wlan [[-p] [-o field[,...]] [wlan-name]
@@ -70,71 +70,71 @@
[-P protocol] [ether-link]
- dladm set-linkprop [-t] [-R root-dir] -p prop=value[,...] link
- dladm reset-linkprop [-t] [-R root-dir] [-p prop[,...]] link
+ dladm set-linkprop [-t] -p prop=value[,...] link
+ dladm reset-linkprop [-t] [-p prop[,...]] link
dladm show-linkprop [-HPZ] [[-c] -o field[,...]] [-p prop[,...]]
[-z zone[,...]] [link]
- dladm create-secobj [-t] [-R root-dir] [-f file] -c class secobj
- dladm delete-secobj [-t] [-R root-dir] secobj[,...]
+ dladm create-secobj [-t] [-f file] -c class secobj
+ dladm delete-secobj [-t] secobj[,...]
dladm show-secobj [-P] [[-p] -o field[,...]] [secobj,...]
- dladm create-vnic [-t] [-f] -l link [-R root-dir] [-m value | auto |
+ dladm create-vnic [-t] [-f] -l link [-m value | auto |
{factory [-n slot-identifier]} | {vrrp -A {inet | inet6} -V vrid}
| {random [-r prefix]}] [-v vlan-id][,pvlan-svid[,pvlan-type]]
[-P pkey] [-p prop=value[,...]] vnic-link
dladm create-vnic -t -c <evsname>[/<vportname>] [-T <tenant>] <vnic-link>
- dladm modify-vnic [-t] [-R root-dir] [-l link] [-m value | auto |
+ dladm modify-vnic [-t] [-l link] [-m value | auto |
{factory [-n slot-identifier]} | {vrrp -A {inet | inet6} -V vrid}
| {random [-r prefix]}] [-v vlan-id[,pvlan-svid[,pvlan-type]]]
{vnic-link,[vnic-link,...] | -L link}
- dladm delete-vnic [-t] [-R root-dir] vnic-link
+ dladm delete-vnic [-t] vnic-link
dladm show-vnic [-P | {-z zone[,..]}] [[-p] -o field[,..]] [-l link]
[vnic-link]
dladm show-vnic [-Zmv] [-l link] [vnic-link]
- dladm create-etherstub [-t] [-R root-dir] etherstub
- dladm delete-etherstub [-t] [-R root-dir] etherstub
+ dladm create-etherstub [-t] etherstub
+ dladm delete-etherstub [-t] etherstub
dladm show-etherstub [-Z] [-z zone[,...]] [etherstub]
- dladm create-iptun [-t] [-R root-dir] -T type
+ dladm create-iptun [-t] -T type
[-a {local|remote}=addr,...] iptun-link
- dladm modify-iptun [-t] [-R root-dir] -a {local|remote}=addr,...
+ dladm modify-iptun [-t] -a {local|remote}=addr,...
iptun-link
- dladm delete-iptun [-t] [-R root-dir] iptun-link
+ dladm delete-iptun [-t] iptun-link
dladm show-iptun [-PZ] [[-p] -o field[,...]] [-z zone[,...]] [iptun-link]
- dladm create-part [-t] [-f] -l ib-link [-R root-dir] -P pkey
+ dladm create-part [-t] [-f] -l ib-link -P pkey
[-p prop=value[,...]] part-link
- dladm delete-part [-t] [-R root-dir] part-link
+ dladm delete-part [-t] part-link
dladm show-part [-pP] [-o field[,...]] [-l ib-link] [part-link]
- dladm create-eoib [-t] [-R root-dir] -l ib-link -g gw-system-name
+ dladm create-eoib [-t] -l ib-link -g gw-system-name
-c gw-eth-port eoib-link
- dladm delete-eoib [-t] [-R root-dir] eoib-link
+ dladm delete-eoib [-t] eoib-link
dladm show-eoib [-PZ] [-g gw-system-name] [-l ib-link] [[-p]
-o field[,...]] [-z zone [,...]] [eoib-link]
dladm show-ib [-pP] [-o field[,...]] [ib-link]
- dladm create-vxlan [-t] [-R root-dir]
+ dladm create-vxlan [-t]
-p vni=<vxlan-id>,addr=<ip_address>[,prop=value[,...]] vxlan-link
- dladm create-vxlan [-t] [-R root-dir]
+ dladm create-vxlan [-t]
-p vni=<vxlan-id>,interface=<interface_name>[,prop=value[,...]]
vxlan-link
dladm show-vxlan [-pP] [-o field[,...]] [vxlan-link]
- dladm delete-vxlan [-t] [-R root-dir] vxlan-link
+ dladm delete-vxlan [-t] vxlan-link
- dladm create-cap [-t] [-R root-dir] cap-link
+ dladm create-cap [-t] cap-link
dladm show-cap [-pP] [-o field[,...]] [cap-link]
- dladm delete-cap [-t] [-R root-dir] cap-link
+ dladm delete-cap [-t] cap-link
dladm create-veth [-t] [-p {<prop>=<val>[,...]}[,...]]
@@ -311,14 +311,7 @@
dladm is implemented as a set of subcommands with corresponding op-
- tions. Options are described in the context of each subcommand. Many of
- the subcommands have the following as a common option:
-
- -R root-dir, --root-dir=root-dir
-
- Specifies an alternate root directory where the operation-such as
- creation, deletion, or renaming-should apply.
-
+ tions. Options are described in the context of each subcommand.
dladm also supports a command form with no arguments. When invoked this
@@ -485,18 +478,13 @@
- dladm rename-link [-R root-dir] link new-link
+ dladm rename-link link new-link
Rename link to new-link. This is used to give a link a meaningful
name, or to associate existing link configuration such as link
properties of a removed device with a new device. See the EXAMPLES
section for specific examples of how this subcommand is used.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
dladm delete-phys phys-link
@@ -917,7 +905,7 @@
- dladm create-aggr [-t] [-R root-dir] [-m mode] [-P policy] [-L lacpmode]
+ dladm create-aggr [-t] [-m mode] [-P policy] [-L lacpmode]
[-T time] [-u address] -l ether-link1 [-l ether-link2...] aggr-link
@@ -954,11 +942,6 @@
tions last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-m mode
Mode must be set to one of the following:
@@ -1055,7 +1038,7 @@
- dladm modify-aggr [-t] [-R root-dir] [-P policy] [-L lacpmode]
+ dladm modify-aggr [-t] [-P policy] [-L lacpmode]
[-T time] [-u address] aggr-link
@@ -1067,11 +1050,6 @@
gations last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-m mode
This option is Obsolete. One can delete the aggregation of one
@@ -1111,7 +1089,7 @@
- dladm delete-aggr [-t] [-R root-dir] aggr-link
+ dladm delete-aggr [-t] aggr-link
Deletes the specified aggregation.
@@ -1121,15 +1099,10 @@
last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
- dladm add-aggr [-t] [-R root-dir] -l ether-link1 [-l ether-link2...]
+ dladm add-aggr [-t] -l ether-link1 [-l ether-link2...]
aggr-link
@@ -1147,15 +1120,10 @@
last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
- dladm remove-aggr [-t] [-R root-dir] -l ether-link1 [-l ether-link2...]
+ dladm remove-aggr [-t] -l ether-link1 [-l ether-link2...]
aggr-link
@@ -1173,11 +1141,6 @@
last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
@@ -1478,7 +1441,7 @@
- dladm create-bridge [-P protect] [-R root-dir] [-p priority]
+ dladm create-bridge [-P protect] [-p priority]
[-m max-age] [-h hello-time] [-d forward-delay]
[-f force-protocol] [-l link...] bridge-name
@@ -1505,11 +1468,6 @@
which is used on RBridges. The default value is stp.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-p priority, --priority=priority
Specifies the Bridge Priority. This sets the IEEE STP priority
@@ -1592,7 +1550,7 @@
- dladm modify-bridge [-P protect] [-R root-dir] [-p priority]
+ dladm modify-bridge [-P protect] [-p priority]
[-m max-age] [-h hello-time] [-d forward-delay]
[-f force-protocol] bridge-name
@@ -1606,7 +1564,7 @@
ilege.
- dladm delete-bridge [-R root-dir] bridge-name
+ dladm delete-bridge bridge-name
Delete a bridge instance. The bridge being deleted must not have
any attached links. Use the remove-bridge subcommand to deactivate
@@ -1614,11 +1572,8 @@
Bridge deletion requires the PRIV_SYS_DL_CONFIG privilege.
- The -R (--root-dir) option is the same as for the create-bridge
- subcommand.
-
- dladm add-bridge [-R root-dir] -l link [-l link...] bridge-name
+ dladm add-bridge -l link [-l link...] bridge-name
Add one or more links to an existing bridge. If multiple links are
specified, and adding any one of them results in an error, the com-
@@ -1647,7 +1602,7 @@
The options are the same as for the create-bridge subcommand.
- dladm remove-bridge [-R root-dir] -l link [-l link...] bridge-name
+ dladm remove-bridge -l link [-l link...] bridge-name
Remove one or more links from a bridge instance. If multiple links
are specified, and removing any one of them would result in an er-
@@ -1784,7 +1739,7 @@
- dladm create-vlan [-ft] [-R root-dir] -l ether-link
+ dladm create-vlan [-ft] -l ether-link
-v vid[,pvlan-svid[,pvlan-type]] [vlan-link]
@@ -1822,15 +1777,10 @@
the VLAN is created in a non-global zone's namespace.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
- dladm modify-vlan [-t] [-R root-dir] [-l ether-link]
+ dladm modify-vlan [-t] [-l ether-link]
[-v vid[,pvlan-svid[,pvlan-type]] [-f]]
{vlan-link,[vlan-link,...] | -L ether-link}
@@ -1845,11 +1795,6 @@
Specifies that the VLAN modification is temporary.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-l ether-link
Specifies the Ethernet link to which to move the VLAN(s). The
@@ -1865,7 +1810,7 @@
- dladm delete-vlan [-t] [-R root-dir] vlan-link
+ dladm delete-vlan [-t] vlan-link
Delete the VLAN link specified.
@@ -1877,11 +1822,6 @@
last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
dladm show-vlan [-PZ] [[-p] -o field[,...]] [-z zone[,...]] [vlan-link]
@@ -1970,18 +1910,13 @@
- dladm create-wlan [-R root-dir] [-p prop=value[,...]] <wlan-name>
+ dladm create-wlan [-p prop=value[,...]] <wlan-name>
Creates a Known WLAN with the given name wlan-name. The wlan-name
represents the ESSID of the WiFi network whose properties can be
saved in this object.
- -R root-dir, --root-dir=root-dir
-
- See Options section above.
-
-
-p prop=value,..., --prop prop=value,...
A comma-separated list of properties to set to the specified
@@ -1990,29 +1925,19 @@
- dladm delete-wlan [-R root-dir] <wlan-name>
+ dladm delete-wlan <wlan-name>
Deletes the specified Known WLAN.
- -R root-dir, --root-dir=root-dir
-
- See Options section above.
-
-
- dladm set-wlan [-R root-dir] -p prop=value[,...] <wlan-name>
+ dladm set-wlan -p prop=value[,...] <wlan-name>
Sets the value of one of more properties on the Known WLAN speci-
fied.
- -R root-dir, --root-dir=root-dir
-
- See Options section above.
-
-
-p prop=value,..., --prop prop=value,...
A comma-separated list of properties to set to the specified
@@ -2021,17 +1946,12 @@
- dladm reset-wlan [-R root-dir] -p prop=value[,...] <wlan-name>
+ dladm reset-wlan -p prop=value[,...] <wlan-name>
Resets the value of one or more properties on the Known WLAN speci-
fied.
- -R root-dir, --root-dir=root-dir
-
- See Options section above.
-
-
-p prop=value,..., --prop prop=value,...
A comma-separated list of properties to set to the specified
@@ -2607,7 +2527,7 @@
- dladm set-linkprop [-t] [-R root-dir] -p prop=value[,...] link
+ dladm set-linkprop [-t] -p prop=value[,...] link
Sets the values of one or more properties on the link specified.
The list of properties and their possible values depend on the link
@@ -2621,11 +2541,6 @@
last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-p prop=value[,...], --prop prop=value[,...]
A comma-separated list of properties to set to the specified
@@ -2635,7 +2550,7 @@
changes to the same value.
- dladm reset-linkprop [-t] [-R root-dir] [-p prop,...] link
+ dladm reset-linkprop [-t] [-p prop,...] link
Resets one or more properties to their values on the link speci-
fied. Properties are reset to the values they had at startup. If no
@@ -2649,11 +2564,6 @@
default values. Temporary resets last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-p prop, ..., --prop=prop, ...
A comma-separated list of properties to reset.
@@ -2810,13 +2720,13 @@
- dladm create-secobj [-t] [-R root-dir] [-f file] -c class secobj
+ dladm create-secobj [-t] [-f file] -c class secobj
Create a secure object named secobj in the specified class to be
- later used as a WEP or WPA key in connecting to an encrypted net-
- work. The value of the secure object can either be provided inter-
- actively or read from a file. The sequence of interactive prompts
- and the file format depends on the class of the secure object.
+ later used as a WPA key in connecting to an encrypted network. The
+ value of the secure object can either be provided interactively or
+ read from a file. The sequence of interactive prompts and the file
+ format depends on the class of the secure object.
Currently, the class wpa is supported. The WEP (Wired Equivalent
Privacy) was deprecated because of security issues. The WPA (Wi-Fi
@@ -2837,21 +2747,16 @@
last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-f file, --file=file
Specifies a file that should be used to obtain the secure ob-
ject's value. The format of this file depends on the secure ob-
ject class. See the EXAMPLES section for an example of using
- this option to set a WEP key.
+ this option to set a WPA key.
- dladm delete-secobj [-t] [-R root-dir] secobj[,...]
+ dladm delete-secobj [-t] secobj[,...]
Delete one or more specified secure objects. This subcommand is
only usable by users or roles that belong to the "Network Link Se-
@@ -2863,11 +2768,6 @@
last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
dladm show-secobj [-P] [[-p] -o field[,...]] [secobj,...]
@@ -2914,7 +2814,7 @@
- dladm create-vnic [-t] [-f] -l link [-R root-dir] [-m value | auto |
+ dladm create-vnic [-t] [-f] -l link [-m value | auto |
{factory [-n slot-identifier]} | {vrrp -A {inet | inet6} -V vrid}
| {random [-r prefix]}] [-v vlan-id][,pvlan-svid[,pvlan-type]]
[-P pkey] [-p prop=value[,...]] vnic-link
@@ -2938,11 +2838,6 @@
sent, or the port is down.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-l link, --link=link
link can be a physical link, an etherstub, or an aggregation
@@ -3113,7 +3008,7 @@
- dladm modify-vnic [-t] [-R root-dir] [-l link] [-m value | auto |
+ dladm modify-vnic [-t] [-l link] [-m value | auto |
{factory [-n slot-identifier]} | {vrrp -A {inet | inet6} -V vrid}
| {random [-r prefix]}] [-v vlan-id[,pvlan-svid[,pvlan-type]]]
{vnic-link,[vnic-link,...] | -L link}
@@ -3129,11 +3024,6 @@
Specifies that the VNIC modification is temporary.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-l link, --link=link
Specifies the link to which to move the VNIC(s). link can be of
@@ -3154,7 +3044,7 @@
- dladm delete-vnic [-t] [-R root-dir] vnic-link
+ dladm delete-vnic [-t] vnic-link
Deletes the specified VNIC.
@@ -3164,11 +3054,6 @@
last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
@@ -3363,7 +3248,7 @@
- dladm create-part [-t] [-f] -l ib-link [-R root-dir] -P pkey
+ dladm create-part [-t] [-f] -l ib-link -P pkey
[-p prop=value[,...]] part-link
@@ -3400,11 +3285,6 @@
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-t, --temporary
Specifies that the partition link creation is temporary. Tempo-
@@ -3414,15 +3294,10 @@
- dladm delete-part [-R root-dir] part-link
+ dladm delete-part part-link
Delete the specified partition link.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-t, --temporary
Specifies that the partition link deletion is temporary. Tempo-
@@ -3606,7 +3481,7 @@
- dladm create-eoib [-t] [-R root-dir] -l ib-link -g gw-system-name
+ dladm create-eoib [-t] -l ib-link -g gw-system-name
-c gw-eth-port eoib-link
@@ -3620,11 +3495,6 @@
links will last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options" above.
-
-
-l ib-link,--link=ib-link
InfiniBand physical link name.
@@ -3642,7 +3512,7 @@
- dladm delete-eoib [-t] [-R root-dir] eoib-link
+ dladm delete-eoib [-t] eoib-link
Delete the specified EoIB link.
@@ -3652,11 +3522,6 @@
links will last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options" above.
-
-
@@ -3773,7 +3638,7 @@
- dladm create-etherstub [-t] [-R root-dir] etherstub
+ dladm create-etherstub [-t] etherstub
Create an etherstub with the specified name.
@@ -3783,18 +3648,13 @@
Specifies that the etherstub is temporary. Temporary etherstubs
do not persist across reboots.
-
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
VNICs can be created on top of etherstubs instead of physical NICs.
As with physical NICs, such a creation causes the stack to implic-
itly create a virtual switch between the VNICs created on top of
the same etherstub.
- dladm delete-etherstub [-t] [-R root-dir] etherstub
+ dladm delete-etherstub [-t] etherstub
Delete the specified etherstub.
@@ -3804,11 +3664,6 @@
last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
dladm show-etherstub [-Z] [-z zone[,...]] [etherstub]
@@ -3828,7 +3683,7 @@
- dladm create-iptun [-t] [-R root-dir] -T type
+ dladm create-iptun [-t] -T type
[-a {local|remote}=addr,...] iptun-link
@@ -3848,11 +3703,6 @@
nels last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-T type, --tunnel-type=type
Specifies the type of tunnel to be created. The type must be
@@ -3899,7 +3749,7 @@
- dladm modify-iptun [-t] [-R root-dir] -a {local|remote}=addr,...
+ dladm modify-iptun [-t] -a {local|remote}=addr,...
iptun-link
@@ -3911,11 +3761,6 @@
cations last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-a {local|remote}=addr,...
--address {local|remote}=addr,...
@@ -3925,7 +3770,7 @@
- dladm delete-iptun [-t] [-R root-dir] iptun-link
+ dladm delete-iptun [-t] iptun-link
Delete the specified IP tunnel link.
@@ -3935,11 +3780,6 @@
last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
@@ -4030,9 +3870,9 @@
- dladm create-vxlan [-t] [-R root-dir]
+ dladm create-vxlan [-t]
-p vni=<vxlan-id>,addr=<ip_address>[,prop=value[,...]] vxlan-link
- dladm create-vxlan [-t] [-R root-dir]
+ dladm create-vxlan [-t]
-p vni=<vxlan-id>,interface=<interface_name>[,prop=value[,...]]
vxlan-link
@@ -4047,11 +3887,6 @@
cations last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
-p prop=value[,...]
The properties of the VXLAN link to be created. See "General
@@ -4059,7 +3894,7 @@
- dladm delete-vxlan [-t] [-R root-dir] vxlan-link
+ dladm delete-vxlan [-t] vxlan-link
Deletes the specified VXLAN link.
@@ -4069,11 +3904,6 @@
cations last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options," above.
-
-
dladm show-vxlan [-P] [[-p] -o field[,...]] [vxlan-link]
@@ -4117,7 +3947,7 @@
- dladm create-cap [-t] [-R root-dir] cap-link
+ dladm create-cap [-t] cap-link
Creates a capture datalink with name cap-link. The cap-link must be
unique in given zone namespace, where dladm command is running.
@@ -4129,14 +3959,9 @@
capture last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options" above.
-
-
- dladm delete-cap [-t] [-R root-dir] cap-link
+ dladm delete-cap [-t] cap-link
Deletes the specified capture datalink.
@@ -4147,11 +3972,6 @@
last until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- See "Options" above.
-
-
dladm show-cap [-P] [[-p] -o <field>,...] [cap-link]
@@ -6678,7 +6498,7 @@
create-vnic [-t] -l link [-m value | auto |
{factory [-n slot-id]} | {random [-r prefix]} |
{vrrp -V vrid -A {inet | inet6}} [-v vid [-f]]
- [-p prop=value[,...]] [-R root-dir] vnic-link
+ [-p prop=value[,...]] vnic-link
create-vnic -t -c <evsname>[/<vportname>] [-T <tenant>] vnic-link>
@@ -7018,4 +6838,103 @@
link name, the aggregation's link name will be automatically generated
by dladm as aggrkey.
-Oracle Solaris 11.4 31 January 2023 dladm(8)
+HISTORY
+ The -R and --root-dir options were removed in Oracle Solaris 11.4.75.
+
+
+ The -w option was added to connect-wifi, the -C and -v options were
+ added to show-aggr, and the -G and -i options were added to show-phys,
+ in Oracle Solaris 11.4.0.
+
+
+ The wep argument was removed from the -s option to connect-wifi and the
+ -c & --class options to create-secobj in Oracle Solaris 11.4.0.
+
+
+ The -v option to show-phys was added in Oracle Solaris 11.3.6.
+
+
+ The -f and -P options were added to create-vnic, and the -H option was
+ added to show-linkprop in Oracle Solaris 11.2.8.
+
+
+ Support for pvlan-svid and pvlan-type arguments was added for the -v
+ option of create-vlan, create-vnic, modify-vlan, and modify-vnic; and
+ the -v was added to show-vnic in Oracle Solaris 11.2.4.
+
+
+ The -c and -T options were added to create-vnic, the -S option was
+ added to show-aggr, the -l, -r, and -V options were added to show-phys,
+ and the -c, -m, and -V options were added to show-vnic, in Oracle So-
+ laris 11.2.0.
+
+
+ The -s and -i options were removed from show-aggr, show-link, and
+ show-vnic, and the show-usage subcommand was removed, in Oracle Solaris
+ 11.2.0. Replacement functionality is available in dlstat(8).
+
+
+ The -m option was added to create-aggr and modify-aggr, the -P option
+ was added to show-ether, and the -D option was added to show-phys, in
+ Oracle Solaris 11.1.0.
+
+
+ The default output when no subcommands are given was changed from a us-
+ age message to a basic configuration display in Oracle Solaris 11.1.0.
+
+
+ The default interface names changed from driver-based names to "net#"
+ style names in Oracle Solaris 11.0.0.
+
+
+ The -z and -Z options were added to show-aggr, show-ether,
+ show-etherstub, show-iptun, show-link, show-linkprop, show-phys,
+ show-vlan, show-vnic, and show-wifi; the -o option was added to
+ show-dev and show-linkprop; the show-dev subcommmand was removed; and
+ the parsable output format was modified to use colons as separators and
+ to require -o to specify the values to list; in Oracle Solaris 11.0.0.
+
+
+ The dladm command was introduced in Solaris 10 1/06 (Update 1).
+
+ Subcommands
+ Support for the following subcommands was added to Oracle Solaris in
+ the listed release:
+
+ +------------------------------------------------+-----------+
+ | SUBCOMMAND | RELEASE |
+ +------------------------------------------------+-----------+
+ | create-wlan, delete-wlan, reset-wlan, | 11.4.0 |
+ | set-wlan, show-wlan | |
+ +------------------------------------------------+-----------+
+ | create-veth, delete-veth, show-veth | 11.3.11 |
+ +------------------------------------------------+-----------+
+ | create-cap, delete-cap, show-cap | 11.3.0 |
+ +------------------------------------------------+-----------+
+ | create-eoib, delete-eoib, show-eoib, | 11.2.0 |
+ | create-vxlan, delete-vxlan, show-vxlan | |
+ +------------------------------------------------+-----------+
+ | help, modify-vlan, modify-vnic | 11.1.0 |
+ +------------------------------------------------+-----------+
+ | add-bridge, create-bridge, delete-bridge, | 11.0.0 |
+ | modify-bridge, remove-bridge, show-bridge, | |
+ | show-ether, create-etherstub, | |
+ | delete-etherstub, show-etherstub, show-ib, | |
+ | create-iptun, delete-iptun, modify-iptun, | |
+ | show-iptun, rename-link, create-part, | |
+ | delete-part, show-part, delete-phys, | |
+ | show-phys, create-secobj, delete-secobj, | |
+ | show-secobj, show-usage, create-vlan, | |
+ | delete-vlan, show-vlan, create-vnic, | |
+ | delete-vnic, show-vnic, connect-wifi, | |
+ | disconnect-wifi, scan-wifi, show-wifi | |
+ +------------------------------------------------+-----------+
+ | reset-linkprop, set-linkprop, show-linkprop | 10 8/07 |
+ +------------------------------------------------+-----------+
+ | add-aggr, create-aggr, delete-aggr, | 10 1/06 |
+ | modify-aggr, remove-aggr, show-aggr, show-dev, | |
+ | show-link | |
+ +------------------------------------------------+-----------+
+
+
+Oracle Solaris 11.4 13 Sep 2024 dladm(8)
diff -NurbBw 11.4.72/man8/flowadm.8 11.4.75/man8/flowadm.8
--- 11.4.72/man8/flowadm.8 2024-11-22 11:50:42.582450320 -0800
+++ 11.4.75/man8/flowadm.8 2024-11-22 11:52:09.148760770 -0800
@@ -15,9 +15,9 @@
-a attr=value[,...]
- flowadm add-flow [-t] [-R root-dir] -l link -a attr=value[,...]
+ flowadm add-flow [-t] -l link -a attr=value[,...]
[-p prop=value[,...]] flow
- flowadm remove-flow [-t] [-R root-dir] {-l link | flow}
+ flowadm remove-flow [-t] {-l link | flow}
flowadm show-filter [-P] [[-p] -o <field>,...] [{-l <link> | <flow>}]
@@ -27,8 +27,8 @@
flowadm remove-filter [-t] {<filter> | -a <attr>=<value>[,...] <flow>}
- flowadm set-flowprop [-t] [-R root-dir] -p prop=value[,...] flow
- flowadm reset-flowprop [-t] [-R root-dir] [-p prop[,...]] flow
+ flowadm set-flowprop [-t] -p prop=value[,...] flow
+ flowadm reset-flowprop [-t] [-p prop[,...]] flow
flowadm show-flowprop [-P] [[-c] -o field[,...]] [-l link]
[-p prop[,...]] [flow]
@@ -271,8 +271,8 @@
- flowadm add-flow [-t] [-R root-dir] -l link -a attr=value[,...] -p
- prop=value[,...] flow
+ flowadm add-flow [-t] -l link -a attr=value[,...] -p prop=value[,...]
+ flow
Adds a flow to the system. The flow is identified by its flow at-
tributes and properties.
@@ -286,12 +286,6 @@
Persistence is the default.
- -R root-dir, --root-dir=root-dir
-
- Specifies an alternate root directory where flowadm should ap-
- ply persistent creation.
-
-
-l link, --link=link
Specify the link to which the flow will be added.
@@ -310,7 +304,7 @@
- flowadm remove-flow [-t] [-R root-dir] {-l link | flow}
+ flowadm remove-flow [-t] {-l link | flow}
Remove an existing flow identified by its link or name.
@@ -320,12 +314,6 @@
Persistence is the default.
- -R root-dir, --root-dir=root-dir
-
- Specifies an alternate root directory where flowadm should ap-
- ply persistent removal.
-
-
-l link | flow, --link=link | flow
If a link is specified, remove all flows from that link. If a
@@ -431,7 +419,7 @@
- flowadm set-flowprop [-t] [-R root-dir] -p prop=value[,...] flow
+ flowadm set-flowprop [-t] -p prop=value[,...] flow
Set values of one or more properties on the flow specified by name.
The complete list of properties can be retrieved using the show-
@@ -443,12 +431,6 @@
Persistence is the default.
- -R root-dir, --root-dir=root-dir
-
- Specifies an alternate root directory where flowadm should ap-
- ply persistent setting of properties.
-
-
-p prop=value[,...], --prop=value[,...]
A comma-separated list of properties to be set to the specified
@@ -456,7 +438,7 @@
- flowadm reset-flowprop [-t] [-R root-dir] [-p prop=value[,...]] flow
+ flowadm reset-flowprop [-t] [-p prop=value[,...]] flow
Resets one or more properties to their default values on the speci-
fied flow. If no properties are specified, all properties are re-
@@ -469,12 +451,6 @@
until the next reboot.
- -R root-dir, --root-dir=root-dir
-
- Specifies an alternate root directory where flowadm should ap-
- ply persistent setting of properties.
-
-
-p prop[,...]
A comma-separated list of properties to be reset.
@@ -1114,4 +1090,37 @@
The show-usage subcommand, present in previous releases of flowadm, has
been replaced by the flowstat(8) -h command.
-Oracle Solaris 11.4 27 Nov 2017 flowadm(8)
+HISTORY
+ The -R and --root-dir options were removed in Oracle Solaris 11.4.75.
+
+
+ The -v option was added to match-flow and show-flow in Oracle Solaris
+ 11.4.0.
+
+
+ The default output when no subcommands are given was changed from a us-
+ age message to a basic configuration display in Oracle Solaris 11.1.0.
+
+
+ The flowadm command was introduced in Oracle Solaris 11.0.0.
+
+ Subcommands
+ Support for the following subcommands was added to Oracle Solaris in
+ the listed release:
+
+ +------------------------------------------------+-----------+
+ | SUBCOMMAND | RELEASE |
+ +------------------------------------------------+-----------+
+ | add-filter, match-filter, remove-filter, | 11.4.0 |
+ | show-filter | |
+ +------------------------------------------------+-----------+
+ | match-flow | 11.3.0 |
+ +------------------------------------------------+-----------+
+ | help | 11.1.0 |
+ +------------------------------------------------+-----------+
+ | add-flow, remove-flow, show-flow, | 11.0.0 |
+ | reset-flowprop, set-flowprop, show-flowprop | |
+ +------------------------------------------------+-----------+
+
+
+Oracle Solaris 11.4 13 Sep 2024 flowadm(8)
diff -NurbBw 11.4.72/man8/fsstat.8 11.4.75/man8/fsstat.8
--- 11.4.72/man8/fsstat.8 2024-11-22 11:50:42.622818616 -0800
+++ 11.4.75/man8/fsstat.8 2024-11-22 11:52:09.218771181 -0800
@@ -627,4 +627,18 @@
tion of higher level software tools depend on either the command-line
options or the output of fsstat is not recommended.
-Oracle Solaris 11.4 22 Aug 2019 fsstat(8)
+HISTORY
+ The -b, -h, and -p options were added in Oracle Solaris 11.4.16.
+
+
+ The -l option, the start_time argument, and support for retrieving his-
+ torical statistics from the Stats Store, were added in Oracle Solaris
+ 11.4.0.
+
+
+ The -A, -Z, and -z options were added in Oracle Solaris 11.1.0.
+
+
+ The fsstat command was introduced in Solaris 10 11/06 (Update 3).
+
+Oracle Solaris 11.4 13 Sep 2024 fsstat(8)
diff -NurbBw 11.4.72/man8/gssd.8 11.4.75/man8/gssd.8
--- 11.4.72/man8/gssd.8 2024-11-22 11:50:42.652260830 -0800
+++ 11.4.75/man8/gssd.8 2024-11-22 11:52:09.251555953 -0800
@@ -70,4 +70,15 @@
requesting restart, can be performed using svcadm(8). The service's
status can be queried using the svcs(1) command.
-Oracle Solaris 11.4 21 Jun 2021 gssd(8)
+HISTORY
+ The config/ccache_patterns SMF property was added in Oracle Solaris
+ 11.4.24.
+
+
+ The SMF service svc:/network/rcp/gss:default was added in Solaris 10
+ 3/05.
+
+
+ The gssd daemon was added in Solaris 7.
+
+Oracle Solaris 11.4 13 Sep 2024 gssd(8)
diff -NurbBw 11.4.72/man8/idmap.8 11.4.75/man8/idmap.8
--- 11.4.72/man8/idmap.8 2024-11-22 11:50:42.698777341 -0800
+++ 11.4.75/man8/idmap.8 2024-11-22 11:52:09.302548899 -0800
@@ -1020,4 +1020,14 @@
and Display Specifiers, which you can find at their technet website,
https://technet.microsoft.com/ .
-Oracle Solaris 11.4 20 July 2023 idmap(8)
+HISTORY
+ The idmu mapping was renamed to rfc2307 in Oracle Solaris 11.4.42.
+
+
+ The -t option to the show subcommand was added in Oracle Solaris
+ 11.4.27.
+
+
+ The idmap command was introduced in Oracle Solaris 11.0.0.
+
+Oracle Solaris 11.4 13 Sep 2024 idmap(8)
diff -NurbBw 11.4.72/man8/ikeadm.8 11.4.75/man8/ikeadm.8
--- 11.4.72/man8/ikeadm.8 2024-11-22 11:50:42.740477347 -0800
+++ 11.4.75/man8/ikeadm.8 2024-11-22 11:52:09.348225829 -0800
@@ -311,6 +311,24 @@
tiator
+ o Count of all started DPD checks of a peer
+
+
+ o Count of all successful DPD interactions, i.e. when the
+ peer replied with R-U-THERE-ACK to any of the R-U-THERE
+ requests
+
+
+ o Count of all failed DPD interactions due to lack of R-U-
+ THERE-ACK message from the peer for the specified number
+ of retires or due to failing to send R-U-THERE to the
+ peer
+
+
+ o Count of all cancelled DPD interactions, e.g. due to re-
+ lated P1 SA timing out
+
+
o Whether a PKCS#11 library is in use, and if applicable,
the PKCS#11 library that is loaded. See ike.config(5).
diff -NurbBw 11.4.72/man8/iostat.8 11.4.75/man8/iostat.8
--- 11.4.72/man8/iostat.8 2024-11-22 11:50:42.778245177 -0800
+++ 11.4.75/man8/iostat.8 2024-11-22 11:52:09.389993565 -0800
@@ -545,4 +545,35 @@
application I/Os. A large value does not necessarily indicate a perfor-
mance problem.
-Oracle Solaris 11.4 14 March 2023 iostat(8)
+HISTORY
+ The -N and -S options were added in Oracle Solaris 11.4.60.
+
+
+ The -w option was added in Oracle Solaris 11.4.33.
+
+
+ The -u option was added in Oracle Solaris 11.4.16.
+
+
+ The -L option was added in Oracle Solaris 11.4.0.
+
+
+ The -Y option was added in Solaris 10 8/07 (Update 4).
+
+
+ The -X option was added in Solaris 9.
+
+
+ The -C, -m, -r, -s, -T, and -z options were added in Solaris 8.
+
+
+ The -E, -e, -M, -n, -P, and -p options were added in Solaris 2.6.
+
+
+ The -x option was added in Solaris 2.0.
+
+
+ The iostat command, including support for the -c, -D, -d, -I, and -t
+ options, has been included in all Sun and Oracle releases of Solaris.
+
+Oracle Solaris 11.4 13 Sep 2024 iostat(8)
diff -NurbBw 11.4.72/man8/kmipcfg.8 11.4.75/man8/kmipcfg.8
--- 11.4.72/man8/kmipcfg.8 2024-11-22 11:50:42.819945258 -0800
+++ 11.4.75/man8/kmipcfg.8 2024-11-22 11:52:09.435906214 -0800
@@ -807,4 +807,18 @@
the default CA certificates, the respective CA certificate must be in-
cluded.
-Oracle Solaris 11.4 14 Sep 2021 kmipcfg(8)
+HISTORY
+ The version property was added in Oracle Solaris 11.4.42.
+
+
+ The kmipcfg info subcommand was added in Oracle Solaris 11.4.33.
+
+
+ KMIP configuration was moved from a file to SMF properties in Oracle
+ Solaris 11.4.0. This included the addition of the kmipcfg extract sub-
+ command.
+
+
+ The kmipcfg command was introduced in Oracle Solaris 11.3.17.
+
+Oracle Solaris 11.4 13 Sep 2024 kmipcfg(8)
diff -NurbBw 11.4.72/man8/ldapclient.8 11.4.75/man8/ldapclient.8
--- 11.4.72/man8/ldapclient.8 2024-11-22 11:50:42.865720855 -0800
+++ 11.4.75/man8/ldapclient.8 2024-11-22 11:52:09.492706847 -0800
@@ -5,22 +5,80 @@
profile in LDIF format
SYNOPSIS
- /usr/sbin/ldapclient [-v | -q] init [-a profileName=profileName]
- [-a domainName=domain] [-a proxyDN=proxyDN]
- [-a proxyPassword=password]
- [-a authenticationMethod=authenticationMethod]
- [-a enableShadowUpdate=true | false]
+ /usr/sbin/ldapclient [-v | -q] init
[-a adminDN=adminDN]
[-a adminPassword=adminPassword]
- [-a certificatePath=path] [-d bindDN] [-w bindPassword]
- [-j passwdFile] [-y passwdFile]
- [-z adminPasswdFile] LDAP_server[:port_number]
+ [-a authenticationMethod=authenticationMethod]
+ [-a certificatePath=path]
+ [-a credentialLevel=[anonymous | proxy | self]]
+ [-a debugLevel=[0-6]]
+ [-a defaultServerList=serverList]
+ [-a domainName=domain]
+ [-a enableShadowUpdate=[true | false]]
+ [-a profileName=profileName]
+ [-a proxyDN=proxyDN]
+ [-a proxyPassword=password]
+ [-d bindDN]
+ [-j passwdFile]
+ [-w bindPassword]
+ [-y proxyPasswdFile]
+ [-z adminPasswdFile]
+ LDAP_server[:port_number]
- /usr/sbin/ldapclient [-v | -q] manual [-a attrName=attrVal]
+ /usr/sbin/ldapclient [-v | -q] manual
+ [-a adminDN=adminDN]
+ [-a adminPassword=adminPassword]
+ [-a attributeMap=attributeMap]
+ [-a authenticationMethod=authenticationMethod]
+ [-a bindTimeLimit=seconds]
+ [-a certificatePath=path]
+ [-a credentialLevel=credentialLevel]
+ [-a debugLevel=[0-6]]
+ [-a defaultSearchBase=DN]
+ [-a defaultSearchScope=[one | sub]]
+ [-a defaultServerList=serverList]
+ [-a domainName=domain]
+ [-a enableShadowUpdate=[true | false]]
+ [-a followReferrals=[true | false]]
+ [-a objectClassMap=objectclassMap]
+ [-a preferredServerList=serverList]
+ [-a proxyDN=proxyDN]
+ [-a proxyPassword=password]
+ [-a searchTimeLimit=seconds]
+ [-a serviceAuthenticationMethod=attrValue]
+ [-a serviceCredentialLevel=attrValue]
+ [-a serviceSearchDescriptor=attrValue]
+ [-d bindDN]
+ [-j passwdFile]
+ [-w bindPassword]
+ [-y proxyPasswdFile]
+ [-z adminPasswdFile]
- /usr/sbin/ldapclient [-v | -q] mod [-a attrName=attrVal]
+ /usr/sbin/ldapclient [-v | -q] mod
+ [-a adminDN=adminDN]
+ [-a adminPassword=adminPassword]
+ [-a authenticationMethod=authenticationMethod]
+ [-a bindTimeLimit=seconds]
+ [-a certificatePath=path]
+ [-a credentialLevel=credentialLevel]
+ [-a debugLevel=[0-6]]
+ [-a defaultSearchBase=DN]
+ [-a defaultSearchScope=[one | sub]]
+ [-a defaultServerList=serverList]
+ [-a domainName=domain]
+ [-a enableShadowUpdate=[true | false]]
+ [-a followReferrals=[true | false]]
+ [-a preferredServerList=serverList]
+ [-a proxyDN=proxyDN]
+ [-a proxyPassword=password]
+ [-a searchTimeLimit=seconds]
+ [-d bindDN]
+ [-j passwdFile]
+ [-w bindPassword]
+ [-y proxyPasswdFile]
+ [-z adminPasswdFile]
/usr/sbin/ldapclient [-v | -q] list
@@ -29,165 +87,147 @@
/usr/sbin/ldapclient [-v | -q] uninit
- /usr/sbin/ldapclient [-v | -q] genprofile -a profileName=profileName
- [-a attrName=attrVal]
+ /usr/sbin/ldapclient [-v | -q] genprofile
+ [-a attributeMap=attributeMap]
+ [-a authenticationMethod=authenticationMethod]
+ [-a bindTimeLimit=seconds]
+ [-a credentialLevel=credentialLevel]
+ [-a defaultSearchBase=DN]
+ [-a defaultSearchScope=[one | sub]]
+ [-a defaultServerList=serverList]
+ [-a followReferrals=[true | false]]
+ [-a objectClassMap=objectClassMap]
+ [-a preferredServerList=serverList]
+ [-a profileName=profileName]
+ [-a profileTTL=integer]
+ [-a searchTimeLimit=seconds]
+ [-a serviceAuthenticationMethod=attrValue]
+ [-a serviceCredentialLevel=attrValue]
+ [-a serviceSearchDescriptor=attrValue]
DESCRIPTION
- The ldapclient utility can be used to:
+ The ldapclient utility can be used to perform a number of tasks based
+ on given subcommand:
- o initialize LDAP client machines
+ o init: initialize LDAP client machines from a profile stored
+ on a directory server.
- o restore the network service environment on LDAP clients
+ o uninit: restore the previous network service environment on
+ this LDAP client.
- o list the contents of the LDAP client cache in human readable
- format.
+ o list: Display the contents of the LDAP client cache in human
+ readable format.
+ o mod: Modify a previously manually configured config.
- The init form of the ldapclient utility initializes an LDAP client ma-
- chine by using a profile that is stored on the specified LDAP server
- (LDAP_server). The LDAP client uses the attributes in the specified
- profile to determine the configuration of the LDAP client. Using a con-
- figuration profile enables you to easily install the LDAP client and
- propagate the configuration changes to LDAP clients. The ldap_cachemgr
- daemon updates the LDAP client configuration when its cache expires by
- reading the profile. For more information about the configuration pro-
- file, see IETF's A Configuration Schema for LDAP Based Directory User
- Agents.
+ o genprofile: Generate a profile for a server.
- The manual form of the ldapclient utility is used to initialize an LDAP
- client machine manually. The LDAP client will use the attributes speci-
- fied on the command line. Any unspecified attributes will be assigned
- their default values. At least one server must be specified in the de-
- faultServerList or the preferredServerList attributes. The domainName
- attribute must be specified if the client's domainName is not set.
- The mod form of the ldapclient utility is used to modify the configura-
- tion of an LDAP client machine that was setup manually. This option
- modifies only those LDAP client configuration attributes specified on
- the command line. The mod option should only be used on LDAP clients
- that were initialized using the manual option.
+ See SUBCOMMANDS section for more details.
+OPTIONS
+ The following options are supported:
- Regardless of which method is used for initialization, if a client is
- to be configured to use a proxy credentialLevel, proxy credentials must
- be provided using -a proxyDN=proxyDN and -a proxyPassword=proxyPass-
- word options. However, if -a proxyPassword=proxyPassword is not speci-
- fied, ldapclient will prompt for it. Note that NULL passwords are not
- allowed in LDAP. If a self credentialLevel is configured, authentica-
- tionMethod must be sasl/GSSAPI.
+ -a attrName=attrValue
- Similarly, if a client is to be configured to enable shadow information
- update and use a proxy credentialLevel, administrator credentials must
- be provided using -a adminDN=adminDN and -a adminPassword=adminPass-
- word. However, the shadow information update does not need the adminis-
- trator credentials if a self credentialLevel is configured.
+ Specify attrName and its value. Refer to the SYNOPSIS for where
+ specific attrName's can be used and LDAP Attributes for a complete
+ list of attribute names and values.
- The naming service-specific configuration properties are stored in the
- svc:/network/ldap/client SMF service. Modifying the SMF properties di-
- rectly is not advised. Use this tool instead.
+ -D bindDN
+ bindDN specifies the Distinguished Name used to bind to the LDAP
+ directory. It must have read permission for the requested database.
- Other configuration might be modified during installation. It will be
- backed up to /var/ldap/restore. The files that are typically modified
- during initialization are:
- o /etc/nsswitch.conf
+ -j passwdFile
+ Specify a file containing the password for the bindDN or the pass-
+ word for the SSL client's key database. To protect the password,
+ use this option in scripts and place the password in a secure file.
+ This option is mutually exclusive of the -w option.
- o /etc/defaultdomain (if it exists)
+ -q
- o /var/yp/binding/`domainname` (for a NIS [YP] client)
+ Quiet mode. No output is generated.
+ -v
- ldapclient does not set up a client to resolve hostnames using DNS. It
- simply copies /etc/nsswitch.ldap to /etc/nsswitch.conf. If you prefer
- to use DNS for host resolution, please refer to the DNS documentation
- for information on setting up DNS. See resolv.conf(5). If you want to
- use sasl/GSSAPI as the authentication method, you have to use DNS for
- hosts and ipnodes resolution.
-
-
- The list form of the ldapclient utility is used to list the LDAP client
- configuration. The output will be human readable. LDAP configuration
- files are not guaranteed to be human readable. Note that for security
- reason, the values for adminDN and adminPassword will not be displayed.
-
-
- The uninit form of the ldapclient utility is used to uninitialize the
- network service environment, restoring it to the state it was in prior
- to the last execution of ldapclient using init or manual. The restora-
- tion will succeed only if the machine was initialized with the init or
- manual form of ldapclient, as it uses the backup files created by these
- options.
-
-
- The genprofile option is used to write an LDIF formatted configuration
- profile based on the attributes specified on the command line to stan-
- dard output. This profile can then be loaded into an LDAP server to be
- used as the client profile, which can be downloaded by means of the
- ldapclient init command. Loading the LDIF formatted profile to the di-
- rectory server can be done through ldapadd, or through any server spe-
- cific import tool. Note that the attributes proxyDN, proxyPassword,
- certificatePath, domainName, enableShadowUpdate, adminDN, and admin-
- Password are not part of the configuration profile and thus are not
- permitted.
+ Verbose output. Specifying additional -v options displays more de-
+ tailed information.
- You must have the Name Service Management rights profile to run the
- ldapclient command, except with the genprofile option.
+ -w bindPassword
+ Password to be used for authenticating the bindDN.
- To access the information stored in the directory, clients can either
- authenticate to the directory, or use an unauthenticated connection.
- The LDAP client is configured to have a credential level of either
- anonymous or proxy. In the first case, the client does not authenticate
- to the directory. In the second case, client authenticates to the di-
- rectory using a proxy identity for read access, and using a administra-
- tor identity for write access if enableShadowUpdate is configured. In
- the third case, client authenticates to the directory using a Kerberos
- principal that is mapped to an LDAP identity by the LDAP server.
+ Warning: use of this option is discouraged, see SECURITY section,
+ use -j passwdFileinstead.
+ If bindPassword is not set or if you supply "-" (hyphen) as a
+ password, the command will prompt for a password.
- If a client is configured to use an identity, you can configure which
- authentication method the client will use. The LDAP client supports the
- following authentication methods:
- none
- simple
- sasl/CRAM-MD5
- sasl/DIGEST-MD5
- sasl/GSSAPI
- tls:simple
- tls:sasl/CRAM-MD5
- tls:sasl/DIGEST-MD5
+ -y proxyPasswdFile
- Note that some directory servers may not support all of these authenti-
- cation methods. For example, be aware that the bind password will be
- sent in the clear to the LDAP server. For those authentication methods
- using TLS (transport layer security), the entire session is encrypted.
- You will need to install the appropriate PEM certificate files to use
- TLS.
+ Specify a file containing the password for the proxyDN. To protect
+ the password, use this option in scripts and place the password in
+ a secure file. This option is mutually exclusive of the
+ -a proxyPassword option.
+
+
+ -z adminPasswdFile
+
+ Specify a file containing the password for the adminDN. To protect
+ the password, use this option in scripts and place the password in
+ a secure file. This option is mutually exclusive of the
+ -a adminPassword option.
- Commands
- The following commands are supported:
- init
+SUBCOMMANDS
+ The following subcommands are supported:
- Initialize client from a profile on a server.
+ init LDAP_server
+
+ Initializes an LDAP client machine from a profile that is stored on
+ the specified LDAP_server; a single address or name with optional
+ port as described in Server
+ List.
+
+ Once the profile is loaded, the preferredServerList and
+ defaultServerList specified in the profile are used; LDAP_server
+ becomes irrelevant
+
+ The LDAP client uses the attributes in the specified profile to de-
+ termine the configuration of the LDAP client. Using a configuration
+ profile enables you to easily install the LDAP client and propagate
+ the configuration changes to LDAP clients. The ldap_cachemgr daemon
+ updates the LDAP client configuration when its cache expires by
+ reading the profile. For more information about the configuration
+ profile, see IETF RFC4876 A Configuration Schema for LDAP Based
+ Directory User Agents.
manual
- Manually initialize client with the specified attribute values.
+ Manually initialize client with the specified attribute values;
+ known also as Manual Mode.
+
+ The LDAP client will use the attributes specified on the command
+ line. Any unspecified attributes will be assigned their default
+ values. At least one server must be specified in the
+ defaultServerList or the preferredServerList attributes. The
+ domainName attribute must be specified if the client's domain name
+ is not set; sysinfo(2) SI_SRPC_DOMAIN
mod
@@ -195,17 +235,26 @@
Modify attribute values in the configuration file after a manual
initialization of the client.
+ This option modifies only those LDAP client configuration attrib-
+ utes specified on the command line. The mod option should only be
+ used on LDAP clients that were initialized using the manual option.
+
list
Write the contents of the LDAP client cache to standard output in
- human readable form.
+ human readable form. LDAP configuration files are not guaranteed to
+ be human readable.
+
+ Note that the values for adminDN, proxyDN, adminPassword and
+ proxyPassword are not displayed for security reasons.
uninit
- Uninitialize an LDAP client, assuming that ldapclient was used to
- initialize the client.
+ Uninitialize an LDAP client, restoring it to the state it was in
+ prior to the last execution of ldapclient using init or manual. It
+ uses the backup files created by those options.
genprofile
@@ -214,9 +263,23 @@
stored in the directory for clients to use, with the init form of
this command.
-
- Attributes
- The following attributes are supported:
+ The formatted configuration profile is written to standard output
+ based on the attributes specified on the command line. This profile
+ can then be loaded into an LDAP server to be used as the client
+ profile, which can be downloaded by means of the ldapclient init
+ command. Loading the LDIF formatted profile to the directory server
+ can be done through ldapadd, or through any server specific import
+ tool.
+
+ Note that the attributes proxyDN, proxyPassword, certificatePath,
+ domainName, enableShadowUpdate, adminDN, and adminPassword are not
+ part of the configuration profile and thus are not permitted.
+
+
+ LDAP Attributes
+ ldapclient attribute pairs are made up of attribute=value pairs as per
+ RFC4876. The following attributes are supported by ldapclient, though
+ some subcommands limit what can be specified; see SYNOPSIS:
adminDN
@@ -228,9 +291,14 @@
adminPassword
- Specify the administrator password. This option is required if the
- credential level is proxy, and enableShadowUpdate is set to true.
- There is no default value.
+ Specify the administrator password.
+
+ Warning: The setting of this attribute on the command line is dis-
+ couraged, see SECURITY section, use -z adminPasswdFile option in-
+ stead.
+
+ A adminPassword is required if the credential level is proxy, and
+ enableShadowUpdate is set to true. There is no default value.
attributeMap
@@ -246,25 +314,24 @@
attributeMap: passwd:uid=employeeNumber
the LDAP client would use the LDAP attribute employeeNumber rather
- than uid for the passwd service. This is a multivalued attribute.
+ than uid for the passwd service. This is a multi-valued attribute.
authenticationMethod
Specify the default authentication method used by all services un-
- less overridden by the serviceAuthenticationMethod attribute. Mul-
- tiple values can be specified by using a semicolon-separated list.
- The default value is none. For those services that use credential-
- Level and credentialLevel is anonymous, this attribute is ignored.
- Services such as pam_ldap will use this attribute, even if creden-
- tialLevel is anonymous. The supported authentication methods are
- described above. If the authenticationMethod is sasl/GSSAPI, the
- hosts and ipnodes of /etc/nsswitch.conf must be configured with DNS
- support, for example:
+ less overridden by the serviceAuthenticationMethod attribute.
- hosts: dns files
- ipnodes: dns files
+ Multiple values can be specified by using a semicolon-separated
+ list. The default value is none.
+ For those services that use credentialLevel and credentialLevel is
+ anonymous, this attribute is ignored.
+
+ Services such as pam_ldap(7) will use this attribute, even if
+ credentialLevel is anonymous.
+
+ The supported Authentication Methods are described below.
bindTimeLimit
@@ -285,47 +352,25 @@
The certificate path for the location of the certificate files. The
value is the path where PEM format certificate files reside. This
- is used for TLS support, which is specified in the authentication-
- Method and serviceAuthenticationMethod attributes. The default is
- /var/ldap.
+ is used for TLS support, which is specified in the
+ authenticationMethod and serviceAuthenticationMethod attributes.
+ The default is /var/ldap.
credentialLevel
Specify the credential level the client should use to contact the
directory. The credential levels supported are anonymous, proxy,
- and self. If a proxy credential level is specified, then the au-
- thenticationMethod attribute must be specified to determine the au-
- thentication mechanism. Also, if the credential level is proxy and
- at least one of the authentication methods require a bind DN, the
- proxyDN and proxyPassword attribute values must be set. In addi-
- tion, if enableShadowUpdate is set to true, the adminDN and admin-
- Password values must be set. If a self credential level is speci-
- fied, the authenticationMethod must be sasl/GSSAPI.
-
- When the credentialLevel property is set to proxy and the authenti-
- cationMethod property is set to sasl/GSSAPI, all lookups use the
- host's Kerberos principal.
-
- When the credentialLevel property is set to self, the authentica-
- tionMethod property is set to sasl/GSSAPI, and nscd is in per-user
- mode, a separate nscd process runs for each user who performs all
- the user's lookups. These lookups all use the user's Kerberos prin-
- cipal. See the enable_per_user_lookup property of nscd.conf(5).
-
- Note that in self mode, users with a UID of 0 use the host princi-
- pal. All other users must define and initialize their respective
- Kerberos principal. Defining and initializing the Kerberos princi-
- pal applies to every user that is defined in any of the configured
- naming repositories, including /etc/passwd, if those users perform
- naming lookups.
+ and self.
+
+ Refer to Credential Level below for details.
defaultSearchBase
- Specify the default search base DN. There is no default. The ser-
- viceSearchDescriptor attribute can be used to override the default-
- SearchBase for given services.
+ Specify the default search base DN. There is no default. The
+ serviceSearchDescriptor attribute can be used to override the
+ defaultSearchBase for given services.
defaultSearchScope=one | sub
@@ -337,39 +382,13 @@
defaultServerList
- A space separated list of server names or server addresses, either
- IPv4 or IPv6. If you specify server names, be sure that the LDAP
- client can resolve the name without the LDAP name service. You must
- resolve the LDAP servers' names by using either files or dns. If
- the LDAP server name cannot be resolved, your naming service will
- fail.
-
- The port number is optional. If not specified, the default LDAP
- server port number 389 is used, except when TLS is specified in the
- authentication method. In this case, the default LDAP server port
- number is 636.
+ A Server List (defined below) that is used after any server listed
+ in the preferredServerList. Priority is not given to the order,
+ whichever one works is used and not overridden except when a pre-
+ ferred server becomes available.
- The format to specify the port number for an IPv6 address is:
-
-
- [ipv6_addr]:port
-
- To specify the port number for an IPv4 address, use the following
- format:
-
-
- ipv4_addr:port
-
- If the host name is specified, use the format:
-
-
- host_name:port
-
- If you use TLS, the LDAP server's hostname must match the hostname
- in the TLS certificate. Typically, the hostname in the TLS certifi-
- cate is a fully qualified domain name. With TLS, the LDAP server
- host addresses must resolve to the hostnames in the TLS certifi-
- cate. You must use files or dns to resolve the host address.
+ At least one server must be listed in either preferredServerList or
+ defaultServerList.
domainName
@@ -381,9 +400,9 @@
enableShadowUpdate=true | false
- Specify whether the client is allowed to update shadow information.
- If set to true and the credential level is proxy, adminDN and ad-
- minPassword must be specified.
+ Specify whether the client is allowed to update Shadow Data (de-
+ fined below) . If set to true and the credential level is proxy
+ then adminDN and adminPassword must be specified.
followReferrals=true | false
@@ -396,75 +415,63 @@
objectclassMap
Specify a mapping from an objectclass defined by a service to an
- objectclass in an alternative schema. This can be used to change
- the default schema used for a given service. The syntax of object-
- classMap is defined in the profile IETF draft. This option can be
- specified multiple times. The default value for all services is
- NULL. In the example,
+ objectclass in an alternative schema.
+
+ This can be used to change the default schema used for a given ser-
+ vice. The syntax of objectclassMap is defined in the profile IETF
+ draft. This option can be specified multiple times. The default
+ value for all services is NULL. In the example,
objectclassMap=passwd:posixAccount=unixAccount
- the LDAP client would use the LDAP objectclass of unixAccount
- rather than the posixAccount for the passwd service. This is a mul-
- tivalued attribute.
+ The LDAP client would use the LDAP objectclass of unixAccount
+ rather than the posixAccount for the passwd service. This is a
+ multi-valued attribute.
preferredServerList
- Specify the space separated list of server names or server ad-
- dresses, either IPv4 or IPv6, to be contacted before servers speci-
- fied by the defaultServerList attribute. If you specify server
- names, be sure that the LDAP client can resolve the name without
- the LDAP name service. You must resolve the LDAP servers' names by
- using either files or dns. If the LDAP server name cannot be re-
- solved, your naming service will fail.
-
- The port number is optional. If not specified, the default LDAP
- server port number 389 is used, except when TLS is specified in the
- authentication method. In this case, the default LDAP server port
- number is 636.
-
- The format to specify the port number for an IPv6 address is:
-
-
- [ipv6_addr]:port
-
- To specify the port number for an IPv4 address, use the following
- format:
-
-
- ipv4_addr:port
-
- If the host name is specified, use the format:
-
+ A Server List (defined below) of servers to be contacted before
+ servers specified by the defaultServerList attribute.
- host_name:port
+ Entries are in priority order, highest priority first. For example
+ if three servers were listed, the first will be used unless that
+ connection fails (goes offline). Only then is the second in the
+ list used, and if that connection goes offline then the third would
+ be used; and so on. When a higher priority server comes back online
+ it will used again and replace any connection to a lower priority
+ server even when that is still online.
- If you use TLS, the LDAP server's hostname must match the hostname
- in the TLS certificate. Typically, the hostname in the TLS certifi-
- cate is a fully qualified domain name. With TLS, the LDAP server
- host addresses must resolve to the hostnames in the TLS certifi-
- cate. You must use files or dns to resolve the host address.
+ At least one server must be listed in either preferredServerList or
+ defaultServerList.
profileName
Specify the profile name. For ldapclient init, this attribute is
the name of an existing profile which may be downloaded periodi-
- cally depending on the value of the profileTTL attribute. For ldap-
- client genprofile, this is the name of the profile to be generated.
- The default value is default.
+ cally depending on the value of the profileTTL attribute. The de-
+ fault value is default.
+
+ For ldapclient genprofile, this is the name of the profile to be
+ generated.
profileTTL
- Specify the TTL value in seconds for the client information. This
- is only relevant if the machine was initialized with a client pro-
- file. If you do not want ldap_cachemgr to attempt to refresh the
- LDAP client configuration from the LDAP server, set profileTTL to 0
- (zero). Valid values are either zero 0 (for no expiration) or a
- positive integer in seconds. The default value is 12 hours.
+ Specify the Time To Live value in seconds for the client profile
+ information. ldap_cachemgr uses this value to determine when to
+ check, and if necessary download, its profile.
+
+ Valid values are either 0 (zero) for no expiration, or a positive
+ integer in seconds. The default value is 547200 (12 hours) or 0 for
+ manual configurations.
+
+ Note that setting svc:network/ldap/client:default property manually
+ to config/profileTTL = 0 after a profile has been downloaded is the
+ equivalent of setting manual mode. No further updates will be taken
+ from the server.
proxyDN
@@ -477,9 +484,15 @@
proxyPassword
- Specify client proxy password. This option is required if the cre-
- dential level is proxy, and at least one of the authentication
- methods requires a bind DN. There is no default.
+ Specify client proxy password.
+
+ Warning: The setting of this attribute on the command line is dis-
+ couraged, see SECURITY section, use -y proxyPasswdFile option in-
+ stead.
+
+ A proxyPassword is required if the credential level is proxy, and
+ at least one of the authentication methods requires a bind DN.
+ There is no default.
searchTimeLimit
@@ -492,7 +505,7 @@
serviceAuthenticationMethod
Specify authentication methods to be used by a service in the form
- servicename:authenticationmethod, for example:
+ service:authenticationMethod, for example:
pam_ldap:tls:simple
@@ -509,28 +522,33 @@
authentication method to be used by the chkey(1) and newkey(8)
utilities. The pam_ldap service defines the authentication method
to be used for authenticating users when pam_ldap(7) is configured.
- If this attribute is not set for any of these services, the authen-
- ticationMethod attribute is used to define the authentication
- method. This is a multivalued attribute.
+ If this attribute is not set for any of these services, the
+ authenticationMethod attribute is used to define the authentication
+ method. This is a multi-valued attribute.
serviceCredentialLevel
Specify credential level to be used by a service. Multiple values
can be specified in a space-separated list. The default value for
- all services is NULL. The supported credential levels are: anony-
- mous or proxy. At present, no service uses this attribute. This is
- a multivalued attribute.
+ all services is NULL.
+
+ The supported credential levels are: anonymous or proxy. At
+ present, no service uses this attribute. This is a multi-valued at-
+ tribute.
serviceSearchDescriptor
Override the default base DN for LDAP searches for a given service.
The format of the descriptors also allow overriding the default
- search scope and search filter for each service. The syntax of ser-
- viceSearchDescriptor is defined in the profile IETF draft. The de-
- fault value for all services is NULL. This is a multivalued at-
- tribute. In the example,
+ search scope and search filter for each service.
+
+ The syntax of serviceSearchDescriptor is defined in the profile
+ IETF draft. The default value for all services is NULL. This is a
+ multi-valued attribute.
+
+ In the example,
serviceSearchDescriptor=passwd:ou=people,dc=a1,dc=example,dc=com?one
@@ -540,82 +558,293 @@
for the passwd service.
-OPTIONS
- The following options are supported:
+ Server List
+ Both serverList and preferredServerList attributes take a space sepa-
+ rated list of server names or server addresses, either IPv4 or IPv6,
+ optionally appended with port number. When a port number is not speci-
+ fied it defaults to LDAP server port number 389 unless a TLS Authenti-
+ cation Method is specified.
- -a attrName=attrValue
- Specify attrName and its value. See SYNOPSIS for a complete list of
- possible attribute names and values.
+ Where TLS authentication is used and no port is specified both port 389
+ with STARTTLS and 636 for raw TLS will be tried, and which ever one
+ works first will be the port used. When a port is specified for TLS
+ then STARTTLS and raw TLS on that port will be tried and the first that
+ works will be used.
- -D bindDN
+ The format to specify the port number for an IPv6 address is:
- Specifies an entry that has read permission for the requested data-
- base.
+ [ipv6_addr]:port
- -j passwdFile
- Specify a file containing the password for the bind DN or the pass-
- word for the SSL client's key database. To protect the password,
- use this option in scripts and place the password in a secure file.
- This option is mutually exclusive of the -w option.
+ To specify the port number for an IPv4 address, use the following for-
+ mat:
+ ipv4_addr:port
- -q
- Quiet mode. No output is generated.
+ If the host name is specified, use the format:
- -v
+ host_name:port
- Verbose output. Specifying additional -v options displays more de-
- tailed information.
- -w bindPassword
+ If you specify server names, be sure that the LDAP client can resolve
+ them without the LDAP name service. They must resolve from either
+ nsswitch.conf(5)'s files (hosts(5)) or dns (resolv.conf(5)) backends.
- Password to be used for authenticating the bind DN. If this parame-
- ter is missing, the command will prompt for a password. NULL pass-
- words are not supported in LDAP.
- When you use -w bindPassword to specify the password to be used
- for authentication, the password is visible to other users of the
- system by means of the ps command, in script files, or in shell
- history.
+ Note that ldapclient initialization copies /etc/nsswitch.ldap to
+ /etc/nsswitch.conf and updates SMF accordingly, for example:
- If you supply "-" (hyphen) as a password, the command will prompt
- for a password.
+ $ svccfg -s name-service/switch listprop config/host
+ config/host astring "files dns"
- -y passwdFile
- Specify a file containing the password for the proxy DN. To protect
- the password, use this option in scripts and place the password in
- a secure file. This option is mutually exclusive of the -a proxy-
- Password option.
+ It does not set up the client to resolve hostnames using DNS. Refer to
+ the DNS documentation for information on setting up DNS in re-
+ solv.conf(5)
- -z adminPasswdFile
+ Note that for sasl/GSSAPI DNS should be used.
+
+
+ Certificates used with TLS should include fully qualified domain names
+ and not just a host name or IP address. The FQDN must resolve cor-
+ rectly. This is a common problem particularly with self-signed certifi-
+ cates, the LDAP server's hostname must match the CN or a DNS record
+ within the X509v3 Subject Alternative Name.
+
+
+ To see the certificates being offered by your LDAP server use the
+ s_client(1openssl) command:
+
+ $ /usr/openssl/3/bin/openssl s_client -starttls ldap \
+ -servername ldap.example.com -connect ldap.example.com
+
+
+
+ If the LDAP server name cannot be resolved or TLS is configured using
+ self-signed certificates and FQDN does not match the names provided in
+ the certificate the LDAP naming service will fail.
+
+ Credential Level
+ Specify the credential level the client should use to contact the di-
+ rectory. The credential levels supported are
+
+ anonymous The client does not authenticate to the directory. No LDAP
+ bind operation occurs.
+
+ When credentialLevel is anonymous the following warning is
+ produced
- Specify a file containing the password for the adminDN. To protect
- the password, use this option in scripts and place the password in
- a secure file. This option is mutually exclusive of the -a admin-
- Password option.
+ Warning: Using anonymous credential level
+ (non-integrity-protected)!
-OPERANDS
- The following operand is supported:
+ Use an alternative credentialLevel to protect the in-
+ tegrity of data passed to the directory server.
- LDAP_server
- An address or a name for the LDAP server from which the profile
- will be loaded. The current naming service specified in the nss-
- witch.conf file is used. Once the profile is loaded, the preferred-
- ServerList and defaultServerList specified in the profile are used.
+ proxy A proxy configuration refers to using an account setup on
+ the directory server for lookups, such as that provided by
+ ldapservercfg(8). A client can only have one proxy ac-
+ count. Different clients or groups of clients, can have
+ their own proxy account.
+
+ The authenticationMethod attribute must be specified to
+ determine the Authentication
+ Mechanism.
+
+ When authenticationMethod property is set to sasl/GSSAPI,
+ all lookups use the host's Kerberos principal.
+
+ If at least one of the authentication methods require a
+ bind DN, the proxyDN and proxyPassword attribute values
+ need to be provided or ldapclient will prompt for their
+ values.
+
+ Note that NULL passwords are not allowed in LDAP.
+
+
+ self A self configuration refers to the users own account mak-
+ ing the lookups. The authenticationMethod must be
+ sasl/GSSAPI.
+
+
+
+ A summary of Credential Levels and Authentication Methods is provided
+ below.
+
+ Authentication Methods
+ To access the information stored in the directory, clients can either
+ authenticate to the directory, or use an unauthenticated connection.
+ Values for attribute authenticationMethod and
+ serviceAuthenticationMethod are further explained here.
+
+ none
+
+ The client does not authenticate to the directory. No LDAP bind op-
+ eration occurs. This method is equivalent to the anonymous Creden-
+ tial Level (credentialLevel attribute)>.
+ simple
+
+ The client system sends the users password in the clear to bind to
+ the LDAP server. The password is subject to snooping unless the
+ session is protected by IPsec such as tls:simple provides.
+
+ This method is easy to set up and all directory servers support it.
+ It should not be used in production environments.
+
+ Note that Oracle does not recommend using the none authentication
+ method in combination with the simple credential level.
+
+ Using tls:simple or sasl/GSSAPI with encryption enabled is recom-
+ mended.
+
+
+ sasl/CRAM-MD5
+
+ Do not use this obsolete authentication method.
+
+ The primary advantage of sasl/CRAM-MD5 (Challenge Response Authen-
+ tication Mechanism) over the simple Authentication Method is that
+ the password is not sent in clear text during authentication. Refer
+ to RFC 2195 for information on CRAM-MD5.
+
+
+ sasl/DIGEST-MD5
+
+ Do not use this obsolete authentication method.
+
+ The primary advantage of sasl/DIGEST-MD5 over the simple Authenti-
+ cation Method is that the password is not sent in clear text during
+ authentication. Refer to RFC 2831 for information on digest-MD5.
+
+
+ sasl/GSSAPI
+
+ This authentication method is used in conjunction with nscd per-
+ user mode to enable per-user lookups. In per-user mode a separate
+ nscd process runs for each user which binds to the server using the
+ sasl/GSSAPI method and the users Kerberos(7) credentials. The per-
+ user nscd process then performs all the user's lookups using the
+ user's Kerberos principal. Access can be controlled in the direc-
+ tory server on a per-user basis. See the enable_per_user_lookup
+ property of nscd.conf(5).
+
+ Note that users with a UID of 0 use the host's Kerberos principal.
+ All other users must define and initialize their respective Ker-
+ beros principal. Defining and initializing the Kerberos principal
+ applies to every user that is defined in any of the configured nam-
+ ing repositories, including /etc/passwd, if those users perform
+ naming lookups.
+
+ Note that for sasl/GSSAPI nsswitch.conf(5) should use DNS. Refer
+ to Server List definition.
+
+
+ tls:simple
+
+ The client establishes a TLS connection and then binds using the
+ simple method. The whole session is encrypted. The password is pro-
+ tected.
+
+
+ tls:sasl/CRAM-MD5
+
+ The LDAP session is encrypted and the client authenticates to the
+ directory server using sasl/cram-MD5.
+
+
+ tls:sasl/DIGEST-MD5
+
+ The LDAP session is encrypted and the client authenticates to the
+ directory server using sasl/digest-MD5.
+
+
+
+ A summary of Credential Levels and Authentication Methods is provided
+ below.
+
+ Shadow Update
+ Shadow update / shadow data is a feature by which certain information
+ can be updated on the LDAP server. For example password aging and ac-
+ count locking (shadow(5)), adding users with useradd(8), etc.
+
+
+ An administrator's credentials with write access to necessary data on
+ the LDAP server must be provided using attributes adminDN and
+ adminPassword.
+
+ Summary of Credential Levels and Authentication Methods
+ A summary of the various Credential (Cred) levels with the Authentica-
+ tion (Auth) Methods provides a clear status as to the security of login
+ and data on the wire, whether a bind occurs, and if Shadow Data is
+ available. Refer to the sections above for further details and also the
+ SECURITY and CAUTION sections below.
+
+ Table 1 Summary of Credential Levels and Authentication Methods
+
+ | | | | |
+ Cred Level | Auth Method | Bind | Shadow |Secure | Notes
+ --------------+-----------------+------+-----------+----------+----------
+ anonymous | none | No | |No | [1][2]
+ --------------+-----------------+------+-----------+----------+----------
+ anonymous | simple | No | |No | [1][2]
+ --------------+-----------------+------+-----------+----------+----------
+ anonymous | tls:simple | No | |No | [1][2]
+ --------------+-----------------+------+-----------+----------+----------
+ proxy | simple | Yes | Yes |No | [2][3]
+ --------------+-----------------+------+-----------+----------+----------
+ proxy | sasl/CRAM-MD5 | Yes | Yes |No | [4]
+ --------------+-----------------+------+-----------+----------+----------
+ proxy | sasl/DIGEST-MD5 | Yes | Yes |No | [4]
+ --------------+-----------------+------+-----------+----------+----------
+ proxy | tls:* | Yes | Yes |Yes | [3][5]
+ --------------+-----------------+------+-----------+----------+----------
+ self | sasl/GSSAPI | Yes | Yes |Yes | [6][7]
+
+
+
+ Note that some directory servers may not support all of these authenti-
+ cation methods.
+
+ 1. The anonymous Credential Level causes Authentication Method
+ to be ignored.
+
+
+ 2. Login passwords and all other data is clearly visible!
+
+
+ 3. A bind occurs using proxyDN
+
+
+ 4. As an authentication method these are considered weak. Use
+ an alternative method or use with TLS.
+
+
+ 5. Using TLS causes the bind and all data to be encrypted.
+
+
+ 6. Users Kerberos credentials are used.
+
+
+ 7. The level of encryption is dependent on the servers configu-
+ ration.
+
+
+
+SECURITY
+ You must have the Name Service Management rights profile to run the
+ ldapclient command, except with the genprofile option.
+
EXAMPLES
Example 1 Setting Up a Client By Using the Default Profile Stored on a
Specified LDAP Server
@@ -625,7 +854,8 @@
The following example shows how to set up a client using the default
profile stored on the specified LDAP server. This command will only be
successful if either the credential level in the profile is set to
- anonymous or the authentication method is set to none.
+ anonymous or the authentication method is set to none as no credential
+ information is given.
example# ldapclient init 172.16.100.1
@@ -637,7 +867,7 @@
The following example shows how to set up a client using the simple
- profile stored on the specified LDAP server. The domainname is set to
+ profile stored on the specified LDAP server. The domainName is set to
xyz.example.com and the proxyPassword is secret.
@@ -754,6 +983,13 @@
FILES
+ svc:/network/ldap/client
+
+ The naming service-specific configuration properties are stored in
+ the SMF service. Modifying the SMF properties directly is not ad-
+ vised. Use ldapclient instead.
+
+
/var/ldap/ldap_client_cred
/var/ldap/ldap_client_file
@@ -763,6 +999,21 @@
+ /var/ldap/restore
+
+ Backup directory for previous configuration files modified during
+ init or manual installation.
+
+ o /etc/nsswitch.conf
+
+
+ o /etc/defaultdomain (if it exists)
+
+
+ o /var/yp/binding/`domainname` (for a NIS [YP] client)
+
+
+
/etc/defaultdomain
System default domain name, matching the domain name of the data in
@@ -778,7 +1029,7 @@
/etc/nsswitch.ldap
Sample configuration file for the name-service switch configured
- with LDAP and files.
+ with LDAP, files and DNS.
ATTRIBUTES
@@ -794,15 +1045,44 @@
SEE ALSO
- chkey(1), ldaplist(1), defaultdomain(5), nscd.conf(5), nss-
- witch.conf(5), resolv.conf(5), attributes(7), kerberos(7), ldap(7), id-
- sconfig(8), ldap_cachemgr(8), ldapaddent(8), nscd(8)
+ chkey(1), ldaplist(1), passwd(1), sysinfo(2), defaultdomain(5),
+ hosts(5), nscd.conf(5), nsswitch.conf(5), resolv.conf(5), attrib-
+ utes(7), kerberos(7), ldap(7), pam_ldap(7), idsconfig(8),
+ ldap_cachemgr(8), ldapaddent(8), newkey(8), nscd(8)
+
+
+ RFC 4876: A Configuration Schema for LDAP Based Directory User Agents:
+
+ https://datatracker.ietf.org/doc/rfc4876/
+
CAUTION
The CRAM-MD5 and DIGEST-MD5 mechanisms are considered weak, obsolete,
and insecure. They should not be used without an encrypted TLS connec-
tion.
+
+ Specifying passwords on the command line with attributes adminPassword,
+ proxyPassword or option -w is not recommended. Usage of these exposes
+ the password, making them visible through commands such as ps(1), in
+ shell history and or in scripts.
+
+
+ The simple method causes the user's bind password to be sent in the
+ clear, unencrypted, to the LDAP server, meaning that the users identity
+ and password could be captured from the network using tools such as
+ snoop or tshark. To protect the authentication and session data use the
+ proxy Credential Level and an Authentication Method that uses Trans-
+ port Layer Security (TLS) to encrypt the entire session. The appropri-
+ ate PEM certificate files used on the server will need to be installed
+ on the client to use TLS (see certificatePath attribute). When an
+ authenticationMethod would cause passwords to be exposed in network
+ traffic ldapclient displays (and ldap_cachemgr(8) logs) a warning iden-
+ tifying the faulty method, for example:
+
+ "Warning: Using non-integrity-protected authentication method: simple
+
+
NOTES
Both StartTLS and raw TLS are supported. A StartTLS request will be
used on any connection not specifying port 636.
@@ -873,10 +1152,8 @@
-
-
Processing group members which are Distinguished Name values can be ex-
- pense as each Distinguished Name value can require a further LDAP
+ pensive as each Distinguished Name value can require a further LDAP
lookup to find the user name. The Distinguished Name values can also be
other LDAP groups which need to be processed to find all the group mem-
bers.
@@ -903,4 +1180,4 @@
Starting with Oracle Solaris 11.4, nscd daemon must be running for
ldap(7) services to function correctly.
-Oracle Solaris 11.4 9 Mar 2022 ldapclient(8)
+Oracle Solaris 11.4 31 Jul 2024 ldapclient(8)
diff -NurbBw 11.4.72/man8/ldm.8 11.4.75/man8/ldm.8
--- 11.4.72/man8/ldm.8 2024-11-22 11:50:43.124760708 -0800
+++ 11.4.75/man8/ldm.8 2024-11-22 11:52:09.711316503 -0800
@@ -4699,7 +4699,7 @@
o memory - Output shows memory.
- o network - Output shows the media access control (mac)
+ o network - Output shows the Media Access Control (MAC)
address, virtual network switch (vsw), and virtual net-
work (vnet) device.
@@ -4852,7 +4852,7 @@
Syntax:
- ldm list-bindings [-e] [-o [network|net]] [-p] [domain-name...]
+ ldm list-bindings [-e] [-o format] [-p] [domain-name...]
@@ -4863,9 +4863,36 @@
control.
- o -o [network|net] generates output for the virtual network
- configuration, including virtual switches and virtual net-
- works.
+ o -o limits the output format to one or more of the following
+ subsets. If you specify more than one format, delimit each
+ format by a comma with no spaces.
+
+ o console - Output shows the virtual console (vcons) and
+ virtual console concentrator (vcc) service.
+
+
+ o disk - Output shows the virtual disk (vdisk) and virtual
+ disk server (vds).
+
+
+ o hba - Output shows the virtual SCSI HBA, the virtual SAN
+ (vSAN), and the domain of the virtual SAN.
+
+
+ o network - Output shows the Media Access Control (MAC)
+ address, virtual network switch (vsw), and virtual net-
+ work (vnet) device.
+
+
+ o san - Output shows the name of the virtual SAN and the
+ device path of the SCSI HBA initiator port with which
+ the virtual SAN is associated.
+
+
+ o serial - Output shows the virtual logical domain channel
+ (vldc) service, virtual logical domain channel client
+ (vldcc).
+
o -p generates the list in a parseable, machine-readable for-
@@ -4884,7 +4911,7 @@
Syntax:
- ldm list-services [-e] [-p] [domain-name...]
+ ldm list-services [-e] [-o format] [-p] [domain-name...]
@@ -4895,6 +4922,38 @@
control.
+ o -o limits the output format to one or more of the following
+ subsets. If you specify more than one format, delimit each
+ format by a comma with no spaces.
+
+ o console - Output shows the virtual console (vcons) and
+ virtual console concentrator (vcc) service.
+
+
+ o disk - Output shows the virtual disk (vdisk) and virtual
+ disk server (vds).
+
+
+ o hba - Output shows the virtual SCSI HBA, the virtual SAN
+ (vSAN), and the domain of the virtual SAN.
+
+
+ o network - Output shows the Media Access Control (MAC)
+ address, virtual network switch (vsw), and virtual net-
+ work (vnet) device.
+
+
+ o san - Output shows the name of the virtual SAN and the
+ device path of the SCSI HBA initiator port with which
+ the virtual SAN is associated.
+
+
+ o serial - Output shows the virtual logical domain channel
+ (vldc) service, virtual logical domain channel client
+ (vldcc).
+
+
+
o -p generates the list in a parseable, machine-readable for-
mat.
@@ -7155,4 +7214,4 @@
Oracle VM Server for SPARC 3.6 Administration Guide
-Oracle Solaris 11.4 14 Jun 2023 ldm(8)
+Oracle Solaris 11.4 14 Aug 2024 ldm(8)
diff -NurbBw 11.4.72/man8/ldmd.8 11.4.75/man8/ldmd.8
--- 11.4.72/man8/ldmd.8 2024-11-22 11:50:43.167828077 -0800
+++ 11.4.75/man8/ldmd.8 2024-11-22 11:52:09.749931935 -0800
@@ -463,4 +463,16 @@
For more information about the ldmd SMF properties, see the Oracle VM
Server for SPARC 3.6 Administration Guide.
-Oracle Solaris 11.4 29 May 2024 ldmd(8)
+HISTORY
+ The ldmd/sstore_mapping_enabled SMF property was added in Oracle So-
+ laris 11.4.72.
+
+
+ The ldmd/tls_certificate, ldmd/tls_host_match, and ldmd/tls_privatekey
+ SMF properties were added in Oracle Solaris 11.4.48.
+
+
+ The ldmd/migration_mem_iterations SMF property was added in Oracle So-
+ laris 11.4.33.
+
+Oracle Solaris 11.4 13 Sep 2024 ldmd(8)
diff -NurbBw 11.4.72/man8/modinfo.8 11.4.75/man8/modinfo.8
--- 11.4.72/man8/modinfo.8 2024-11-22 11:50:43.199447559 -0800
+++ 11.4.75/man8/modinfo.8 2024-11-22 11:52:09.782046054 -0800
@@ -283,4 +283,16 @@
SEE ALSO
attributes(7), scale(7), modload(8), modunload(8)
-Oracle Solaris 11.4 14 February 2024 modinfo(8)
+HISTORY
+ The -h, -x, -?, --scale, and --help options, and the sys field, were
+ added in Oracle Solaris 11.4.69.
+
+
+ The -a, -o, -p, and -P options, and the ability to pass module names to
+ the -i option, were added in Oracle Solaris 11.4.0.
+
+
+ The modinfo command, with the -c, -i, and -w options, was introduced in
+ Solaris 2.0.
+
+Oracle Solaris 11.4 13 Sep 2024 modinfo(8)
diff -NurbBw 11.4.72/man8/mount_nfs.8 11.4.75/man8/mount_nfs.8
--- 11.4.72/man8/mount_nfs.8 2024-11-22 11:50:43.241726869 -0800
+++ 11.4.75/man8/mount_nfs.8 2024-11-22 11:52:09.830198666 -0800
@@ -748,4 +748,49 @@
used in conjunction with remount) affect the root (/) entry in the
/etc/vfstab file.
-Oracle Solaris 11.4 1 Feb 2022 mount_nfs(8)
+HISTORY
+ The noresvport mount option was added in Oracle Solaris 11.4.72.
+
+
+ The acl and noacl mount options were added in Oracle Solaris 11.4.39.
+
+
+ The nommaplockcheck mount option was added in Oracle Solaris 11.4.24.
+
+
+ The idmap mount option was added in Oracle Solaris 11.4.0.
+
+
+ Support for NFS version 4.1 was added to the vers option in Oracle So-
+ laris 11.4.0.
+
+
+ Support for NFS version 4.0 was added to the vers option in Solaris 10
+ 3/05.
+
+
+ The attr and noattr mount options were added in Solaris 9.
+
+
+ The forcedirectio and noforcedirectio mount options were added in So-
+ laris 8.
+
+
+ Support for Kerberos version 4, including the kerberos mount option,
+ was removed in Solaris 8.
+
+
+ The public mount option was added in Solaris 7.
+
+
+ Support for NFS version 3, including the proto, sec, and vers mount op-
+ tions, was added in Solaris 2.6.
+
+
+ The posix mount option was added in Solaris 2.1.
+
+
+ Support for NFS mounts, using NFS version 2, has been included in all
+ Sun and Oracle releases of Solaris.
+
+Oracle Solaris 11.4 13 Sep 2024 mount_nfs(8)
diff -NurbBw 11.4.72/man8/nscfg.8 11.4.75/man8/nscfg.8
--- 11.4.72/man8/nscfg.8 2024-11-22 11:50:43.276167389 -0800
+++ 11.4.75/man8/nscfg.8 2024-11-22 11:52:09.868220076 -0800
@@ -106,7 +106,7 @@
The nscfg utility supports the subcommands described below. Options are
described in the context of the subcommands.
- import [-fvq] FMRI
+ import [-fnvq] FMRI
If none of the SMF repository properties for the specified FMRI are
currently populated, import the legacy configuration files associ-
@@ -119,16 +119,22 @@
ation. With -q, issue no error or other messages during the re-
quested operation.
+ The -n causes the command to not actually perform any changes, the
+ legacy files are not imported.
- export [-vq] FMRI
+
+ export [-nvq] FMRI
Export the SMF configuration for the specified FMRI to legacy con-
figuration files. This operation removes any existing affected
legacy file(s) and generates new one(s) using the SMF configura-
tion.
+ The -n causes the command to not actually perform any changes, no
+ legacy files are updated.
+
- unconfig [-vq] FMRI
+ unconfig [-nvq] FMRI
Unconfigure the SMF configuration for the specified FMRI. This op-
eration resets the specified FMRI and any existing legacy file(s)
@@ -138,6 +144,8 @@
ation. With -q, issue no error or other messages during the re-
quested operation.
+ The -n causes the command to not actually perform any changes.
+
validate [-vq] FMRI
diff -NurbBw 11.4.72/man8/smbadm.8 11.4.75/man8/smbadm.8
--- 11.4.72/man8/smbadm.8 2024-11-22 11:50:43.315840254 -0800
+++ 11.4.75/man8/smbadm.8 2024-11-22 11:52:09.907126125 -0800
@@ -61,7 +61,7 @@
server
- smbadm show-dcs
+ smbadm show-dcs [-u]
smbadm show-domains
@@ -493,7 +493,7 @@
- show-dcs
+ show-dcs [-u]
Shows information about the Active Directory Domain Controllers
that have been discovered. This option is only available in domain
@@ -502,7 +502,9 @@
state, the Preferred Domain Controller if configured, and a list of
Domain Controllers that have been found. If an AD site has been
configured then any Domain Controllers that are members of the site
- are indicated as such.
+ are indicated as such. If the -u option is specified, the AD user
+ accounts that are used for establishing connections with the Domain
+ Controllers are also shown.
show-domains
@@ -613,4 +615,22 @@
smf(7), groupadd(8), idmap(8), idmapd(8), kclient(8), mount_smbfs(8),
share(8), sharectl(8), smbd(8), smbstat(8)
-Oracle Solaris 11.4 20 July 2023 smbadm(8)
+HISTORY
+ The -u option was added to the smbadm show-dcs subcommand in Oracle So-
+ laris 11.4.75.
+
+
+ The smbadm change-dc and smbadm show-dcs subcommands were added in Ora-
+ cle Solaris 11.4.30.
+
+
+ The smbadm print subcommand was removed in Oracle Solaris 11.4.0.
+
+
+ The -o option was added to the smbadm join subcommand in Oracle Solaris
+ 11.1.0.
+
+
+ The smbadm command was introduced in Oracle Solaris 11.0.0.
+
+Oracle Solaris 11.4 13 Sep 2024 smbadm(8)
diff -NurbBw 11.4.72/man8/statd.8 11.4.75/man8/statd.8
--- 11.4.72/man8/statd.8 2024-11-22 11:50:43.355926851 -0800
+++ 11.4.75/man8/statd.8 2024-11-22 11:52:09.938356201 -0800
@@ -109,4 +105,14 @@
and automountd(8) unless its application/auto_enable property is set to
false.
-Oracle Solaris 11.4 24 March 2021 statd(8)
+HISTORY
+ The statd_servers SMF property was added in Oracle Solaris 11.4.36.
+
+
+ The svc:/network/nfs/status SMF service was added in Solaris 10 3/05.
+
+
+ The statd daemon has been included in all Sun and Oracle releases of
+ Solaris.
+
+Oracle Solaris 11.4 13 Sep 2024 statd(8)
diff -NurbBw 11.4.72/man8/svcbundle.8 11.4.75/man8/svcbundle.8
--- 11.4.72/man8/svcbundle.8 2024-11-22 11:50:43.393272750 -0800
+++ 11.4.75/man8/svcbundle.8 2024-11-22 11:52:09.976442280 -0800
@@ -552,4 +552,21 @@
smf_security(7), smf_template(7), init(8), svc.startd(8), svccfg(8),
svc.periodicd(8)
-Oracle Solaris 11.4 13 October 2020 svcbundle(8)
+HISTORY
+ The timeout, start-timeout, stop-timeout, refresh-timeout, delay, and
+ jitter attributes were added to svcbundle in Oracle Solaris 11.4.27.
+
+
+ The user, group, and privileges attributes were added to svcbundle in
+ Oracle Solaris 11.4.19.
+
+
+ Support for periodic and scheduled services, including the day,
+ day_of_month, frequency, hour, interval, minute, month, period, time-
+ zone, weekday_of_month, week_of_year, and year attributes were added to
+ svcbundle in Oracle Solaris 11.3.0.
+
+
+ The svcbundle command was introduced in Oracle Solaris 11.1.0.
+
+Oracle Solaris 11.4 13 Sep 2024 svcbundle(8)
diff -NurbBw 11.4.72/man8/sysadm.8 11.4.75/man8/sysadm.8
--- 11.4.72/man8/sysadm.8 2024-11-22 11:50:43.427601335 -0800
+++ 11.4.75/man8/sysadm.8 2024-11-22 11:52:10.015523558 -0800
@@ -394,4 +394,27 @@
SEE ALSO
solaris(7), solaris-kz(7), zones(7), beadm(8), rad(8), svc.zones(8)
-Oracle Solaris 11.4 25 Jul 2023 sysadm(8)
+HISTORY
+ The noreboot argument to the -t option to the sysadm maintain subcom-
+ mand was added in Oracle Solaris 11.4.63.
+
+
+ The -t option to the sysadm maintain subcommand, including support for
+ the admin and software arguments, was added in Oracle Solaris 11.4.60.
+
+
+ Support for increased verbosity by providing the -v option a second
+ time was added in Oracle Solaris 11.4.42.
+
+
+ The -w option to the sysadm evacuate subcommand was added in Oracle So-
+ laris 11.4.30.
+
+
+ Support for migration and evacuation of Solaris 10 branded zones was
+ added in Oracle Solaris 11.4.16.
+
+
+ The sysadm command was introduced in Oracle Solaris 11.4.0.
+
+Oracle Solaris 11.4 13 Sep 2024 sysadm(8)
diff -NurbBw 11.4.72/man8/useradd.8 11.4.75/man8/useradd.8
--- 11.4.72/man8/useradd.8 2024-11-22 11:50:43.470797367 -0800
+++ 11.4.75/man8/useradd.8 2024-11-22 11:52:10.059256760 -0800
@@ -806,4 +806,44 @@
and the existence of any group names specified against the external
name service.
-Oracle Solaris 11.4 14 Apr 2023 useradd(8)
+HISTORY
+ The -z option and the zfshome default value setting were added in Ora-
+ cle Solaris 11.4.30.
+
+
+ The -q option was added in Oracle Solaris 11.2.0.
+
+
+ The -S option and support for LDAP repositories were added in Oracle
+ Solaris 11.0.0. Support was also added for using the -k and -s options
+ with -D to set default values, and for using the -b option without -D.
+
+
+ The default value for group was changed from other (GID of 1) to staff
+ (GID of 10) in Oracle Solaris 11.0.0.
+
+
+ Prior to Oracle Solaris 11.0 and Solaris 10 1/13 (Update 11), the sys-
+ tem file entries created with this command had a limit of 2048 charac-
+ ters per line.
+
+
+ The -K option was added in Solaris 10 3/05.
+
+
+ The -p option was added in Solaris 9.
+
+
+ The -A, -P, and -R options were added in Solaris 8.
+
+
+ The roleadd and rolemod commands were introduced in Solaris 8.
+
+
+ Support for uid and gid values larger than 60000 was added in Solaris
+ 2.5.1.
+
+
+ The useradd and usermod commands were introduced in Solaris 2.0.
+
+Oracle Solaris 11.4 13 Sep 2024 useradd(8)
diff -NurbBw 11.4.72/man8/vmstat.8 11.4.75/man8/vmstat.8
--- 11.4.72/man8/vmstat.8 2024-11-22 11:50:43.507852192 -0800
+++ 11.4.75/man8/vmstat.8 2024-11-22 11:52:10.105431559 -0800
@@ -327,4 +327,33 @@
stolen by the host system. The mpstat(8) command can be used to report
stolen time.
-Oracle Solaris 11.4 14 Jul 2022 vmstat(8)
+HISTORY
+ The -w option was added in Oracle Solaris 11.4.33.
+
+
+ The -Q option was added in Oracle Solaris 11.4.16.
+
+
+ The "wait cpu" line in vmstat -s output was replaced by "stolen time"
+ in Oracle Solaris 11.2.0.
+
+
+ The -c option was removed in Oracle Solaris 11.0.0.
+
+
+ The -T option was added in Oracle Solaris 11.0.0.
+
+
+ The -q option was added in Solaris 10 3/05.
+
+
+ The -p option was added in Solaris 8.
+
+
+ The -f option was removed in Solaris 2.0.
+
+
+ The vmstat command, including support for the -i, -s, and -S options,
+ has been included in all Sun and Oracle releases of Solaris.
+
+Oracle Solaris 11.4 13 Sep 2024 vmstat(8)
diff -NurbBw 11.4.72/man8/vscanadm.8 11.4.75/man8/vscanadm.8
--- 11.4.72/man8/vscanadm.8 2024-11-22 11:50:43.546110474 -0800
+++ 11.4.75/man8/vscanadm.8 2024-11-22 11:52:10.141301908 -0800
@@ -486,4 +486,11 @@
All of these authorizations are included in the "VSCAN Management" pro-
file.
-Oracle Solaris 11.4 30 Jan 2024 vscanadm(8)
+HISTORY
+ Support for TLS connections, including the use-tls, host-match, and
+ trusted-certs-path properties, was added in Oracle Solaris 11.4.72.
+
+
+ The vscanadm command was introduced in Oracle Solaris 11.0.0.
+
+Oracle Solaris 11.4 13 Sep 2024 vscanadm(8)
diff -NurbBw 11.4.72/man8/zfs_share.8 11.4.75/man8/zfs_share.8
--- 11.4.72/man8/zfs_share.8 2024-11-22 11:50:43.598098712 -0800
+++ 11.4.75/man8/zfs_share.8 2024-11-22 11:52:10.190878117 -0800
@@ -10,6 +10,9 @@
zfs help -l properties
+ zfs create [-p] [-o share.nfs=on | share.smb=on [-o ...]] filesystem
+
+
zfs destroy share
@@ -20,28 +23,31 @@
zfs get share [filesystem]
- zfs [-r] set [-r | -c] filesystem|volume|snapshot|share ...
+ zfs set [-r] share.nfs=<on | off> filesystem
+
+ zfs set [-r] share.smb=<on | off> filesystem
- zfs [-r] set share.nfs=on | off filesystem
+ zfs set [-r] property=value filesystem|volume|snapshot|share ...
- zfs [-r] set share.smb=on | off filesystem
+ zfs set -c [-r] share=name=value filesystem|volume|snapshot|share ...
- zfs share -u [-o property=value]... filesystem%share
+
+ zfs share [-u] [-o property=value] ... filesystem%share
zfs share filesystem|mountpoint|filesystem%share
- zfs share -a | -r filesystem
+ zfs share -a | [-r] filesystem
zfs unshare filesystem|mountpoint|filesystem%share
- zfs unshare -a | -r filesystem
+ zfs unshare -a | [-r] filesystem
DESCRIPTION
You can create an NFS share or an SMB share of a ZFS file system by
@@ -803,7 +809,7 @@
value is editable and inheritable, and their possible values.
- zfs create [-p] [-o share.nfs=on | share.smb=on -o ... filesystem
+ zfs create [-p] [-o share.nfs=on | share.smb=on [-o ...]] filesystem
Creates a new ZFS file system. The file system is automatically
mounted according to the mountpoint property inherited from the
@@ -824,8 +830,8 @@
The specified file system share is destroyed.
- zfs get [-r|-d depth] [-Hp] [-o all | field[,...] [-s source[,...]] all
- | property[,...] dataset| dataset%namedshare ...
+ zfs get [-r|-d depth] [-Hp] [-o all | field[,...]] [-s source[,...]]
+ all | property[,...] dataset|dataset%namedshare ...
Displays properties for the given datasets. If no datasets are
specified, then the command displays properties for all datasets on
@@ -900,20 +906,21 @@
- zfs get share [filesystem]
+ zfs get share filesystem
Displays all defined shares or the defined shares for a specified
file system.
- zfs set share.nfs=on | share.smb=on [desc=description], filesystem |
- filesystem%share
+ zfs set [-r] share.nfs=<on | off> filesystem
+ zfs set [-r] share.smb=<on | off> filesystem
Defines an NFS or SMB file sharing properties for a ZFS dataset by
- setting the share.nfs or share.smb property to on.
+ setting the share.nfs or share.smb property to on or off.
+
- zfs set [-r] [-c] property=value filesystem|volume|snapshot|share ...
+ zfs set [-r] property=value filesystem|volume|snapshot|share ...
Sets the property to the given value for each file system or file
system share or clears the file system share. Only some properties
@@ -922,12 +929,18 @@
NFS Share Property Descriptions section or the SMB Share Property
Descriptions section.
+ -r
+
+ Recursively applies the effective value of the setting through-
+ out the subtree of child datasets. The effective value may be
+ set or inherited, depending on the property.
+
- -c
- Clears the file system share properties by specifying a share
- argument in the share=name=value pool/filesystem format.
+ zfs set -c [-r] share=name=value filesystem|volume|snapshot|share ...
+ Clears the file system share properties by specifying a share argu-
+ ment in the share=name=value format.
-r
@@ -937,9 +950,9 @@
- zfs share [-u] -o property=value ... filesystem%share
+ zfs share [-u] [-o property=value] ... filesystem%share
zfs share filesystem|mountpoint|filesystem%share
- zfs share -a -r | filesystem
+ zfs share -a | [-r] filesystem
Creates and publishes an NFS or SMB share of a ZFS dataset accord-
ing to the share properties values.
@@ -982,7 +995,7 @@
zfs unshare filesystem|mountpoint|filesystem%share
- zfs unshare -a | -r |filesystem
+ zfs unshare -a | [-r] filesystem
Unshares all ZFS datasets that have the share.nfs or share.smb
property set.
@@ -1167,4 +1180,4 @@
The Unicode Standard (https://www.unicode.org/standard/standard.html)
-Oracle Solaris 11.4 16 Aug 2023 zfs_share(8)
+Oracle Solaris 11.4 15 Jun 2024 zfs_share(8)
diff -NurbBw 11.4.72/man8/zfs.8 11.4.75/man8/zfs.8
--- 11.4.72/man8/zfs.8 2024-11-22 11:50:43.699967746 -0800
+++ 11.4.75/man8/zfs.8 2024-11-22 11:52:10.293206670 -0800
@@ -94,7 +94,10 @@
zfs mount
- zfs mount [-vO] [-o options] -a | filesystem
+ zfs mount [-vO] [-o options] -a | filesystem[ ...]
+
+
+ zfs mount -r [-vO] [-o options] filesystem|mountpoint[ ...]
zfs promote clone-filesystem
@@ -141,13 +144,16 @@
zfs set [-f|-r] property=value filesystem|volume|snapshot ...
+ zfs set -c [-r] share=name=value filesystem|volume|snapshot|share ...
+
+
zfs share -u [-o property=value] filesystem%share
zfs share filesystem|mountpoint|filesystem%share
- zfs share -a| -r | filesystem
+ zfs share -a | [-r] filesystem
zfs snapshot [-r] [-o property=value]...
@@ -167,13 +173,16 @@
zfs unallow [-r] -s @setname [perm|@setname[,... ]] filesystem|volume
- zfs unmount [-f] -a | filesystem|mountpoint
+ zfs unmount [-rf] filesystem|mountpoint[ ...]
+
+
+ zfs unmount [-f] -a
zfs unshare filesystem|mountpoint|filesystem%share
- zfs unshare -a | -r filesystem
+ zfs unshare -a | [-r] filesystem
zfs upgrade
@@ -2290,7 +2299,8 @@
Displays all ZFS file systems currently mounted.
- zfs mount [-vOS] [-o options] -a | filesystem
+ zfs mount [-vO] [-o options] -a | filesystem[ ...]
+ zfs mount -r [-vO] [-o options] filesystem|mountpoint[ ...]
Mounts ZFS file systems. Invoked automatically as part of the boot
process.
@@ -2308,6 +2318,13 @@
Perform an overlay mount. See mount(8) for more information.
+ -r
+
+ Mounts all descendent file systems of the specified filesystem
+ or ZFS file systems which are mounted at or beneath the speci-
+ fied mountpoint.
+
+
-v
Report mount progress.
@@ -2898,6 +2916,7 @@
zfs set [-f|-r] property=value filesystem|volume|snapshot ...
+ zfs set -c [-r] share=name=value filesystem|volume|snapshot|share ...
Sets the property to the given value for each dataset. Only some
properties can be edited. See the "Properties" section for more in-
@@ -2927,10 +2946,18 @@
inheritable, or delegatable.
+ -c
+
+ Clears the file system share properties by specifying a share
+ argument in the share=name=value format.
+
+
+
+
zfs share [-u] -o property=value ... filesystem%share
zfs share filesystem|mountpoint|filesystem%share
- zfs share -a | filesystem
+ zfs share -a | [-r] filesystem
For a full description of zfs share syntax and examples and setting
the share.nfs or share.smb property, see zfs_share(8).
@@ -2976,7 +3003,8 @@
- zfs unmount [-f] -a | filesystem|mountpoint
+ zfs unmount [-rf] filesystem|mountpoint[ ...]
+ zfs unmount [-f] -a
Unmounts currently mounted ZFS file systems. Invoked automatically
as part of the shutdown process.
@@ -2991,7 +3019,14 @@
-a
Unmounts all available ZFS file systems. Invoked automatically
- as part of the boot process.
+ as part of the shutdown process.
+
+
+ -r
+
+ Unmounts all descendent file systems of the specified filesys-
+ tem or ZFS file systems which are mounted at or beneath the
+ specified mountpoint.
filesystem|mountpoint
@@ -3003,8 +3038,9 @@
system is unmounted. To unload the key, see zfs key.
+
zfs unshare filesystem|mountpoint|filesystem%share
- zfs unshare -a | -r filesystem
+ zfs unshare -a | [-r] filesystem
For a full description of zfs unshare syntax and examples, see
zfs_share(8).
@@ -3608,4 +3644,4 @@
modified in multiple ways. Any action that causes a change in the
st_ctim (see stat(2)) is a basis for reporting a modification.
-Oracle Solaris 11.4 13 Mar 2024 zfs(8)
+Oracle Solaris 11.4 26 Jun 2024 zfs(8)
diff -NurbBw 11.4.72/man8/zonecfg.8 11.4.75/man8/zonecfg.8
--- 11.4.72/man8/zonecfg.8 2024-11-22 11:50:43.806404721 -0800
+++ 11.4.75/man8/zonecfg.8 2024-11-22 11:52:10.393157479 -0800
@@ -407,7 +407,7 @@
maxbw, bwshare, priority, vlan-id, vsi-typeid, vsi-vers, vsi-mgrid,
rxfanout, rxrings, txrings, link-protection, allowed-dhcp-cids,
pkey, linkmode, etsbw-lcl, cos, id, evs, vport, iov, vlan, ring-
- group, autopush
+ group, autopush, lro
mac
@@ -1020,9 +1020,9 @@
Specify a name for the automatically created VNIC or IPoIB
datalink. By default, this property will be automatically set
to the first available name (for the zone) of the form netN,
- where N is a non-negative integer. For example: net0, net1,
- and so on. The info subcommand displays the automatically se-
- lected linkname.
+ where N is a non-negative integer. For example: net0, net1, and
+ so on. The info subcommand displays the automatically selected
+ linkname.
Multiple zones, including the global zone, can have links with
the same name at the same time.
@@ -3860,4 +3860,220 @@
cannot be a descendant of any dataset delegated to the zone, including
the zone's top-level delegated dataset.
-Oracle Solaris 11.4 9 Feb 2024 zonecfg(8)
+HISTORY
+ Support on x86 platforms for the level2 and native values for the host-
+ compatible property was added in Oracle Solaris 11.4.51.
+
+
+ Support on SPARC platforms for the level2 value for the host-compatible
+ property was added in Oracle Solaris 11.4.45.
+
+
+ The -r option to the create subcommand, the -r option to the export
+ subcommand, the -a option to the info subcommand, and support for the
+ none value for the link-protection property of anet resources, were
+ added in Oracle Solaris 11.4.0.
+
+
+ Support on SPARC platforms for the adi and native values for the host-
+ compatible property was added in Oracle Solaris 11.3.8.
+
+
+ The -x storage-create-missing option, the -i and -I options to the info
+ subcommand, and support for specifying resources by identifier numbers
+ were added in Oracle Solaris 11.3.0.
+
+
+ Support for live zone reconfiguration, including the -r to the zonecfg
+ command, the -n and -q options to the commit subcommand, and the reload
+ subcommand; and support for configuring a zone from a Unified Archive,
+ including the -x and -z options for the create subcommand, were added
+ in Oracle Solaris 11.2.0. The revert subcommand was removed and re-
+ placed by the reload subcommand at the same time.
+
+
+ The default value for the ip-type global property was changed from
+ "shared" to "exclusive" in Oracle Solaris 11.0.0.
+
+
+ The clear subcommand, the -F opton to the remove subcommand, and sup-
+ port for configuring selected resources/properties of the global zone,
+ were added in Solaris 10 8/07 (Update 4).
+
+
+ Support for zone migration, including the -a option to the create sub-
+ command, was added in Solaris 10 11/06 (Update 3).
+
+
+ The zonecfg command was introduced in Solaris 10 3/05.
+
+ Resources
+ Support for the following resource types is available in Oracle Solaris
+ starting with the listed release:
+
+ +------------------------------------------------+-----------+
+ | RESOURCE TYPE | RELEASE |
+ +------------------------------------------------+-----------+
+ | smf-dependency | 11.4.0 |
+ +------------------------------------------------+-----------+
+ | vlan | 11.3.6 |
+ +------------------------------------------------+-----------+
+ | ib-vhca, npiv, port, verified-boot | 11.3.0 |
+ +------------------------------------------------+-----------+
+ | keysource, mac, suspend, virtual-cpu | 11.2.0 |
+ +------------------------------------------------+-----------+
+ | rootzpool, zpool | 11.1.0 |
+ +------------------------------------------------+-----------+
+ | admin, anet | 11.0.0 |
+ +------------------------------------------------+-----------+
+ | capped-cpu | 10 4/08 |
+ +------------------------------------------------+-----------+
+ | capped-memory, dedicated-cpu | 10 8/07 |
+ +------------------------------------------------+-----------+
+ | dataset | 10 6/06 |
+ +------------------------------------------------+-----------+
+ | attr, device, fs, inherit-pkg-dir, net, rctl | 10 3/05 |
+ +------------------------------------------------+-----------+
+
+
+
+ Support for the inherit-pkg-dir resource type was removed in Oracle So-
+ laris 11.0.0.
+
+ Properties
+ Support for the following properties is available in Oracle Solaris
+ starting with the listed release:
+
+ +------------------+-------------------------------------+----------+
+ | RESOURCE TYPE | PROPERTY | RELEASE |
+ +------------------+-------------------------------------+----------+
+ | capped-memory | memlzr | 11.4.63 |
+ +------------------+-------------------------------------+----------+
+ | (global) | host-compatible [x86] | 11.4.51 |
+ +------------------+-------------------------------------+----------+
+ | capped-memory | pagesize [x86] | 11.4.51 |
+ +------------------+-------------------------------------+----------+
+ | capped-memory | pagesize [SPARC] | 11.4.45 |
+ +------------------+-------------------------------------+----------+
+ | (global) | description | 11.4.36 |
+ +------------------+-------------------------------------+----------+
+ | device | removable | 11.4.21 |
+ +------------------+-------------------------------------+----------+
+ | (global) | hwprovider | 11.4.12 |
+ +------------------+-------------------------------------+----------+
+ | capped-memory | memory-reserve | 11.4.1 |
+ +------------------+-------------------------------------+----------+
+ | (global) | boot-disk-protection, boot-priority | 11.4.0 |
+ +------------------+-------------------------------------+----------+
+ | anet | autopush, ring-group | 11.4.0 |
+ +------------------+-------------------------------------+----------+
+ | device | allow-mhd | 11.4.0 |
+ +------------------+-------------------------------------+----------+
+ | smf-dependency | fmri, grouping, name | 11.4.0 |
+ +------------------+-------------------------------------+----------+
+ | (global) | max-adi-metadata-memory | 11.3.11 |
+ +------------------+-------------------------------------+----------+
+ | ib-vhca | smi-enabled | 11.3.9 |
+ +------------------+-------------------------------------+----------+
+ | capped-memory | pagesize-policy | 11.3.9 |
+ +------------------+-------------------------------------+----------+
+ | (global) | host-compatible [SPARC] | 11.3.8 |
+ +------------------+-------------------------------------+----------+
+ | mac | allowed-mac-address | 11.3.6 |
+ +------------------+-------------------------------------+----------+
+ | vlan | allowed-vlan-ids, vlan-id | 11.3.6 |
+ +------------------+-------------------------------------+----------+
+ | (global) | cpu-arch, global-time | 11.3.0 |
+ +------------------+-------------------------------------+----------+
+ | device | create-size | 11.3.0 |
+ +------------------+-------------------------------------+----------+
+ | ib-vhca | id, over-hca | 11.3.0 |
+ +------------------+-------------------------------------+----------+
+ | npiv | over-hba, virtual-port-wwn | 11.3.0 |
+ +------------------+-------------------------------------+----------+
+ | port | id, pkey | 11.3.0 |
+ +------------------+-------------------------------------+----------+
+ | verified-boot | cert, policy | 11.3.0 |
+ +------------------+-------------------------------------+----------+
+ | anet | bwshare, iov, lro | 11.2.8 |
+ +------------------+-------------------------------------+----------+
+ | (global) | autoshutdown, tenant | 11.2.0 |
+ +------------------+-------------------------------------+----------+
+ | anet | evs, id, vport | 11.2.0 |
+ +------------------+-------------------------------------+----------+
+ | dedicated-cpu | cpus, cores, sockets | 11.2.0 |
+ +------------------+-------------------------------------+----------+
+ | device | bootpri, id, storage | 11.2.0 |
+ +------------------+-------------------------------------+----------+
+ | mac | mac-address, mac-prefix | 11.2.0 |
+ +------------------+-------------------------------------+----------+
+ | net | id | 11.2.0 |
+ +------------------+-------------------------------------+----------+
+ | suspend | path, storage | 11.2.0 |
+ +------------------+-------------------------------------+----------+
+ | virtual-cpu | ncpus | 11.2.0 |
+ +------------------+-------------------------------------+----------+
+ | anet | cos, etsbw-lcl, linkmode, pkey, | 11.1.0 |
+ | | vsi-mgrid, vsi-typeid, vsi-vers | |
+ +------------------+-------------------------------------+----------+
+ | rootzpool | storage | 11.1.0 |
+ +------------------+-------------------------------------+----------+
+ | zpool | name, storage | 11.1.0 |
+ +------------------+-------------------------------------+----------+
+ | (global) | file-mac-profile, fs-allowed, | 11.0.0 |
+ | | max-processes | |
+ +------------------+-------------------------------------+----------+
+ | admin | auths, user | 11.0.0 |
+ +------------------+-------------------------------------+----------+
+ | anet | allowed-address, allowed-dhcp-cids, | 11.0.0 |
+ | | auto-mac-address, | |
+ | | configure-allowed-address, | |
+ | | defrouter, link-protection, | |
+ | | linkname, lower-link, mac-address, | |
+ | | mac-prefix, mac-slot, maxbw, mtu, | |
+ | | priority, rxfanout, rxrings, | |
+ | | txrings, vlan-id | |
+ +------------------+-------------------------------------+----------+
+ | dataset | alias | 11.0.0 |
+ +------------------+-------------------------------------+----------+
+ | device | allow-partition, allow-raw-io | 11.0.0 |
+ +------------------+-------------------------------------+----------+
+ | net | allowed-address, | 11.0.0 |
+ | | configure-allowed-address | |
+ +------------------+-------------------------------------+----------+
+ | (global) | hostid | 10 9/10 |
+ +------------------+-------------------------------------+----------+
+ | net | defrouter | 10 8/08 |
+ +------------------+-------------------------------------+----------+
+ | capped-cpu | ncpus | 10 4/08 |
+ +------------------+-------------------------------------+----------+
+ | (global) | brand, bootargs, cpu-shares, | 10 8/07 |
+ | | ip-type, max-lwps, max-msg-ids, | |
+ | | max-sem-ids, max-shm-ids, | |
+ | | max-shm-memory, scheduling-class | |
+ +------------------+-------------------------------------+----------+
+ | capped-memory | locked, physical, swap | 10 8/07 |
+ +------------------+-------------------------------------+----------+
+ | dedicated-cpu | importance, ncpus | 10 8/07 |
+ +------------------+-------------------------------------+----------+
+ | (global) | limitpriv, zonename | 10 11/06 |
+ +------------------+-------------------------------------+----------+
+ | dataset | name | 10 6/06 |
+ +------------------+-------------------------------------+----------+
+ | (global) | autoboot, pool, zonepath | 10 3/05 |
+ +------------------+-------------------------------------+----------+
+ | attr | name, type, value | 10 3/05 |
+ +------------------+-------------------------------------+----------+
+ | device | match | 10 3/05 |
+ +------------------+-------------------------------------+----------+
+ | fs | dir, options, raw, special, type | 10 3/05 |
+ +------------------+-------------------------------------+----------+
+ | inherit-pkg-dir | dir | 10 3/05 |
+ +------------------+-------------------------------------+----------+
+ | net | address, physical | 10 3/05 |
+ +------------------+-------------------------------------+----------+
+ | rctl | name, value | 10 3/05 |
+ +------------------+-------------------------------------+----------+
+
+
+Oracle Solaris 11.4 13 Sep 2024 zonecfg(8)
diff -NurbBw 11.4.72/man8s/identity.8s 11.4.75/man8s/identity.8s
--- 11.4.72/man8s/identity.8s 2024-11-22 11:50:43.836804342 -0800
+++ 11.4.75/man8s/identity.8s 2024-11-22 11:52:10.431528177 -0800
@@ -110,15 +109,13 @@
97:30:b0:7c:63:05:19:78:55:d4:12:81:5f:e3:2c:5d:00:d1:31:b6
-
Example 3 Specifying a certificate DN
For the case where the host can not determine its own fully qualified
- domain name its self, maybe because it is behind NAT or uses a differ-
- ent DNS to the clients, the value of the DN can be provided:
-
+ domain name itself, maybe because it is behind NAT or uses a different
+ DNS to the clients, the value of the DN can be provided:
# svccfg -s system/identity:cert delcust
@@ -177,7 +172,20 @@
SEE ALSO
- uname(1), hostname(1), webui-service(7), domainname(8), ldapserver-
- cfg(8), slapd(8)
+ hostname(1), pktool(1), uname(1), webui-service(7), domainname(8),
+ ldapservercfg(8), slapd(8), svcadm(8), svccfg(8)
+
+HISTORY
+ The certificate/add_ip_subject_altname property was added in the Oracle
+ Solaris 11.4.33 release.
+
+
+ The svc:/system/identity:cert, svc:/system/identity:cert-expiry, and
+ svc:/system/identity:version instances were added in the Oracle Solaris
+ 11.4.0 release.
+
+
+ The svc:/system/identity:domain and svc:/system/identity:node instances
+ were introduced in the Solaris 10 3/05 release.
-Oracle Solaris 11.4 02 Feb 2024 identity(8s)
+Oracle Solaris 11.4 13 Sep 2024 identity(8s)
diff -NurbBw 11.4.72/man9e/_fini.9e 11.4.75/man9e/_fini.9e
--- 11.4.72/man9e/_fini.9e 2024-11-22 11:50:43.872076158 -0800
+++ 11.4.75/man9e/_fini.9e 2024-11-22 11:52:10.464009719 -0800
@@ -71,8 +71,8 @@
- The following example demonstrates how to initialize and free a mu-
- tex(9F).
+ The following example demonstrates how to initialize and free a
+ mutex(9F).
#include <sys/modctl.h>
@@ -134,9 +134,9 @@
SEE ALSO
- add_drv(8), modinfo(8), ddi_soft_state(9F), mod_info(9F), mod_in-
- stall(9F), mod_remove(9F), mutex(9F), modldrv(9S), modlinkage(9S),
- modlstrmod(9S)
+ add_drv(8), modinfo(8), ddi_soft_state(9F), mod_info(9F),
+ mod_install(9F), mod_remove(9F), mutex(9F), modldrv(9S),
+ modlinkage(9S), modlstrmod(9S)
Writing Device Drivers in Oracle Solaris 11.4
@@ -150,4 +150,4 @@
declared as globals, their scope is restricted by the kernel to the
module that they are defined in.
-Oracle Solaris 11.4 9 Mar 2018 _fini(9E)
+Oracle Solaris 11.4 9 September 2024 _fini(9E)
diff -NurbBw 11.4.72/man9e/aread.9e 11.4.75/man9e/aread.9e
--- 11.4.72/man9e/aread.9e 2024-11-22 11:50:43.903915980 -0800
+++ 11.4.75/man9e/aread.9e 2024-11-22 11:52:10.494584224 -0800
@@ -10,7 +10,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixaread(dev_t dev, struct aio_req *aio_reqp, cred_t *cred_p);
+ int prefix_aread(dev_t dev, struct aio_req *aio_reqp, cred_t *cred_p);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is optional. Dri-
@@ -68,8 +68,8 @@
SEE ALSO
read(2), aioread(3C), awrite(9E), read(9E), strategy(9E), write(9E),
- anocancel(9F), aphysio(9F), ddi_get_soft_state(9F), drv_priv(9F), get-
- minor(9F), minphys(9F), nodev(9F), cb_ops(9S), aio_req(9S), uio(9S)
+ anocancel(9F), aphysio(9F), ddi_get_soft_state(9F), drv_priv(9F),
+ getminor(9F), minphys(9F), nodev(9F), cb_ops(9S), aio_req(9S), uio(9S)
Writing Device Drivers in Oracle Solaris 11.4
@@ -78,4 +78,4 @@
There is no way other than calling aphysio(9F) to accomplish an asyn-
chronous read.
-Oracle Solaris 11.4 3 Nov 2021 aread(9E)
+Oracle Solaris 11.4 9 September 2024 aread(9E)
diff -NurbBw 11.4.72/man9e/attach.9e 11.4.75/man9e/attach.9e
--- 11.4.72/man9e/attach.9e 2024-11-22 11:50:43.935985025 -0800
+++ 11.4.75/man9e/attach.9e 2024-11-22 11:52:10.533959212 -0800
@@ -7,7 +7,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixattach(dev_info_t *dip, ddi_attach_cmd_t cmd);
+ int prefix_attach(dev_info_t *dip, ddi_attach_cmd_t cmd);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI)
@@ -124,4 +124,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 7 Jan 2004 attach(9E)
+Oracle Solaris 11.4 9 September 2024 attach(9E)
diff -NurbBw 11.4.72/man9e/audio_engine_channels.9e 11.4.75/man9e/audio_engine_channels.9e
--- 11.4.72/man9e/audio_engine_channels.9e 2024-11-22 11:50:43.965205168 -0800
+++ 11.4.75/man9e/audio_engine_channels.9e 2024-11-22 11:52:10.563043913 -0800
@@ -52,4 +52,4 @@
SEE ALSO
audio(4D), attributes(7), audio_engine_ops(9S)
-Oracle Solaris 11.4 16 Apr 2010 audio_engine_channels(9E)
+Oracle Solaris 11.4 9 September 2024 audio_engine_channels(9E)
diff -NurbBw 11.4.72/man9e/audio_engine_chinfo.9e 11.4.75/man9e/audio_engine_chinfo.9e
--- 11.4.72/man9e/audio_engine_chinfo.9e 2024-11-22 11:50:43.994341356 -0800
+++ 11.4.75/man9e/audio_engine_chinfo.9e 2024-11-22 11:52:10.592562923 -0800
@@ -81,4 +81,4 @@
SEE ALSO
audio(4D), attributes(7), audio_engine_ops(9S)
-Oracle Solaris 11.4 16 Apr 2010 audio_engine_chinfo(9E)
+Oracle Solaris 11.4 9 September 2024 audio_engine_chinfo(9E)
diff -NurbBw 11.4.72/man9e/audio_engine_count.9e 11.4.75/man9e/audio_engine_count.9e
--- 11.4.72/man9e/audio_engine_count.9e 2024-11-22 11:50:44.023317866 -0800
+++ 11.4.75/man9e/audio_engine_count.9e 2024-11-22 11:52:10.621318108 -0800
@@ -34,8 +34,8 @@
The frame count for the engine is related to the offset of the data in
the buffer. Both normally increase as the engine makes progress, but
the engine index wraps when it reaches the end of the buffer or when
- the device is stopped and restarted with audio_engine_stop(9E) and au-
- dio_engine_start(9E).
+ the device is stopped and restarted with audio_engine_stop(9E) and
+ audio_engine_start(9E).
RETURN VALUES
The audio_engine_count() function returns the number of frames trans-
@@ -55,7 +55,7 @@
SEE ALSO
- audio(4D), attributes(7), audio_engine_open(9E), audio_en-
- gine_start(9E), audio_engine_stop(9E), audio_engine_ops(9S)
+ audio(4D), attributes(7), audio_engine_open(9E),
+ audio_engine_start(9E), audio_engine_stop(9E), audio_engine_ops(9S)
-Oracle Solaris 11.4 16 Apr 2010 audio_engine_count(9E)
+Oracle Solaris 11.4 9 September 2024 audio_engine_count(9E)
diff -NurbBw 11.4.72/man9e/audio_engine_format.9e 11.4.75/man9e/audio_engine_format.9e
--- 11.4.72/man9e/audio_engine_format.9e 2024-11-22 11:50:44.052262794 -0800
+++ 11.4.75/man9e/audio_engine_format.9e 2024-11-22 11:52:10.652550833 -0800
@@ -66,4 +66,4 @@
SEE ALSO
audio(4D), attributes(7), audio_engine_ops(9S)
-Oracle Solaris 11.4 16 Apr 2010 audio_engine_format(9E)
+Oracle Solaris 11.4 9 September 2024 audio_engine_format(9E)
diff -NurbBw 11.4.72/man9e/audio_engine_open.9e 11.4.75/man9e/audio_engine_open.9e
--- 11.4.72/man9e/audio_engine_open.9e 2024-11-22 11:50:44.082819775 -0800
+++ 11.4.75/man9e/audio_engine_open.9e 2024-11-22 11:52:10.687601014 -0800
@@ -92,4 +92,4 @@
SEE ALSO
open(2), attributes(7), ddi_dma_mem_alloc(9F), audio_engine_ops(9S)
-Oracle Solaris 11.4 16 Apr 2010 audio_engine_open(9E)
+Oracle Solaris 11.4 9 September 2024 audio_engine_open(9E)
diff -NurbBw 11.4.72/man9e/audio_engine_playahead.9e 11.4.75/man9e/audio_engine_playahead.9e
--- 11.4.72/man9e/audio_engine_playahead.9e 2024-11-22 11:50:44.112597375 -0800
+++ 11.4.75/man9e/audio_engine_playahead.9e 2024-11-22 11:52:10.715812458 -0800
@@ -53,4 +53,4 @@
SEE ALSO
audio(4D), attributes(7), audio_engine_ops(9S)
-Oracle Solaris 11.4 16 Apr 2010 audio_engine_playahead(9E)
+Oracle Solaris 11.4 9 September 2024 audio_engine_playahead(9E)
diff -NurbBw 11.4.72/man9e/audio_engine_qlen.9e 11.4.75/man9e/audio_engine_qlen.9e
--- 11.4.72/man9e/audio_engine_qlen.9e 2024-11-22 11:50:44.141495057 -0800
+++ 11.4.75/man9e/audio_engine_qlen.9e 2024-11-22 11:52:10.748103098 -0800
@@ -41,4 +41,4 @@
SEE ALSO
audio(4D), attributes(7), audio_engine_ops(9S)
-Oracle Solaris 11.4 16 Apr 2010 audio_engine_qlen(9E)
+Oracle Solaris 11.4 9 September 2024 audio_engine_qlen(9E)
diff -NurbBw 11.4.72/man9e/audio_engine_rate.9e 11.4.75/man9e/audio_engine_rate.9e
--- 11.4.72/man9e/audio_engine_rate.9e 2024-11-22 11:50:44.170291627 -0800
+++ 11.4.75/man9e/audio_engine_rate.9e 2024-11-22 11:52:10.784871115 -0800
@@ -39,4 +39,4 @@
SEE ALSO
audio(4D), attributes(7), audio_engine_ops(9S)
-Oracle Solaris 11.4 16 Apr 2010 audio_engine_rate(9E)
+Oracle Solaris 11.4 9 September 2024 audio_engine_rate(9E)
diff -NurbBw 11.4.72/man9e/audio_engine_start.9e 11.4.75/man9e/audio_engine_start.9e
--- 11.4.72/man9e/audio_engine_start.9e 2024-11-22 11:50:44.200023834 -0800
+++ 11.4.75/man9e/audio_engine_start.9e 2024-11-22 11:52:10.814027996 -0800
@@ -55,4 +55,4 @@
SEE ALSO
audio(4D), attributes(7), audio_engine_open(9E), audio_engine_ops(9S)
-Oracle Solaris 11.4 16 Apr 2010 audio_engine_start(9E)
+Oracle Solaris 11.4 9 September 2024 audio_engine_start(9E)
diff -NurbBw 11.4.72/man9e/audio_engine_sync.9e 11.4.75/man9e/audio_engine_sync.9e
--- 11.4.72/man9e/audio_engine_sync.9e 2024-11-22 11:50:44.230245760 -0800
+++ 11.4.75/man9e/audio_engine_sync.9e 2024-11-22 11:52:10.845126183 -0800
@@ -6,7 +6,7 @@
SYNOPSIS
#include <sys/audio/audio_driver.h>
- void prefix_sync(void *state, unsigned nframes)
+ void prefix_sync(void *state, unsigned nframes);
PARAMETERS
state pointer to driver supplied soft state
@@ -55,7 +55,7 @@
SEE ALSO
- audio(4D), attributes(7), audio_engine_start(9E), ddi_dma_sync(9F), au-
- dio_engine_ops(9S)
+ audio(4D), attributes(7), audio_engine_start(9E), ddi_dma_sync(9F),
+ audio_engine_ops(9S)
-Oracle Solaris 11.4 16 Apr 2010 audio_engine_sync(9E)
+Oracle Solaris 11.4 9 September 2024 audio_engine_sync(9E)
diff -NurbBw 11.4.72/man9e/awrite.9e 11.4.75/man9e/awrite.9e
--- 11.4.72/man9e/awrite.9e 2024-11-22 11:50:44.263251183 -0800
+++ 11.4.75/man9e/awrite.9e 2024-11-22 11:52:10.875386260 -0800
@@ -10,7 +10,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixawrite(dev_t dev, struct aio_req *aio_reqp,
+ int prefix_awrite(dev_t dev, struct aio_req *aio_reqp,
cred_t *cred_p);
INTERFACE LEVEL
@@ -75,8 +75,8 @@
SEE ALSO
write(2), aiowrite(3C), aread(9E), read(9E), strategy(9E), write(9E),
- anocancel(9F), aphysio(9F), ddi_get_soft_state(9F), drv_priv(9F), get-
- minor(9F), minphys(9F), nodev(9F), aio_req(9S), cb_ops(9S), uio(9S)
+ anocancel(9F), aphysio(9F), ddi_get_soft_state(9F), drv_priv(9F),
+ getminor(9F), minphys(9F), nodev(9F), aio_req(9S), cb_ops(9S), uio(9S)
Writing Device Drivers in Oracle Solaris 11.4
@@ -85,4 +85,4 @@
There is no way other than calling aphysio(9F) to accomplish an asyn-
chronous write.
-Oracle Solaris 11.4 3 Nov 2021 awrite(9E)
+Oracle Solaris 11.4 9 September 2024 awrite(9E)
diff -NurbBw 11.4.72/man9e/chpoll.9e 11.4.75/man9e/chpoll.9e
--- 11.4.72/man9e/chpoll.9e 2024-11-22 11:50:44.305785844 -0800
+++ 11.4.75/man9e/chpoll.9e 2024-11-22 11:52:10.905215429 -0800
@@ -9,7 +9,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixchpoll(dev_t dev, short events, int anyyet,
+ int prefix_chpoll(dev_t dev, short events, int anyyet,
short *reventsp, struct pollhead **phpp);
INTERFACE LEVEL
@@ -117,4 +117,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 7 May 2008 chpoll(9E)
+Oracle Solaris 11.4 9 September 2024 chpoll(9E)
diff -NurbBw 11.4.72/man9e/close.9e 11.4.75/man9e/close.9e
--- 11.4.72/man9e/close.9e 2024-11-22 11:50:44.337564279 -0800
+++ 11.4.75/man9e/close.9e 2024-11-22 11:52:10.937776277 -0800
@@ -13,7 +13,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixclose(dev_t dev, int flag, int otyp, cred_t *cred_p);
+ int prefix_close(dev_t dev, int flag, int otyp, cred_t *cred_p);
STREAMS
#include <sys/types.h>
@@ -25,7 +25,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixclose(queue_t *q, int flag, cred_t *cred_p);
+ int prefix_close(queue_t *q, int flag, cred_t *cred_p);
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI). This entry point is re-
@@ -206,4 +206,4 @@
STREAMS Programming Guide
-Oracle Solaris 11.4 24 Apr 2008 close(9E)
+Oracle Solaris 11.4 9 September 2024 close(9E)
diff -NurbBw 11.4.72/man9e/detach.9e 11.4.75/man9e/detach.9e
--- 11.4.72/man9e/detach.9e 2024-11-22 11:50:44.369470976 -0800
+++ 11.4.75/man9e/detach.9e 2024-11-22 11:52:10.969856002 -0800
@@ -7,7 +7,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefix detach(dev_info_t dip, ddi_detach_cmd_t cmd);
+ int prefix_detach(dev_info_t dip, ddi_detach_cmd_t cmd);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI)
@@ -129,4 +129,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 28 Jun 2011 detach(9E)
+Oracle Solaris 11.4 9 September 2024 detach(9E)
diff -NurbBw 11.4.72/man9e/devmap_access.9e 11.4.75/man9e/devmap_access.9e
--- 11.4.72/man9e/devmap_access.9e 2024-11-22 11:50:44.398972091 -0800
+++ 11.4.75/man9e/devmap_access.9e 2024-11-22 11:52:11.000745045 -0800
@@ -7,7 +7,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixdevmap_access(devmap_cookie_t dhp, void *pvtp,
+ int prefix_devmap_access(devmap_cookie_t dhp, void *pvtp,
offset_t off, size_t len, uint_t type, uint_t rw);
INTERFACE LEVEL
@@ -56,11 +56,11 @@
The devmap_access() entry point is an optional routine. It notifies
drivers whenever an access is made to a mapping described by dhp that
has not been validated or does not have sufficient protection for the
- access. The system expects devmap_access() to call either de-
- vmap_do_ctxmgt(9F) or devmap_default_access(9F) to load the memory ad-
- dress translations before it returns. For mappings that support context
- switching, device drivers should call devmap_do_ctxmgt(9F). For map-
- pings that do not support context switching, the drivers should call
+ access. The system expects devmap_access() to call either
+ devmap_do_ctxmgt(9F) or devmap_default_access(9F) to load the memory
+ address translations before it returns. For mappings that support con-
+ text switching, device drivers should call devmap_do_ctxmgt(9F). For
+ mappings that do not support context switching, the drivers should call
devmap_default_access(9F).
@@ -78,9 +78,9 @@
off and len define the range to be affected by the operations in de-
vmap_access(). type defines the type of operation that device drivers
should perform on the memory object. If type is either DEVMAP_LOCK or
- DEVMAP_UNLOCK, the length passed to either devmap_do_ctxmgt(9F) or de-
- vmap_default_access(9F) must be same as len. rw specifies the direction
- of access on the memory object.
+ DEVMAP_UNLOCK, the length passed to either devmap_do_ctxmgt(9F) or
+ devmap_default_access(9F) must be same as len. rw specifies the direc-
+ tion of access on the memory object.
A non-zero return value from devmap_access() may result in a SIGSEGV or
@@ -92,8 +92,8 @@
0 Successful completion.
- Non-zero An error occurred. The return value from de-
- vmap_do_ctxmgt(9F) or devmap_default_access(9F) should be
+ Non-zero An error occurred. The return value from
+ devmap_do_ctxmgt(9F) or devmap_default_access(9F) should be
returned.
@@ -103,9 +103,9 @@
The following is an example of the devmap_access() entry point. If the
- mapping supports context switching, devmap_access() calls de-
- vmap_do_ctxmgt(9F). Otherwise, devmap_access() calls devmap_default_ac-
- cess(9F).
+ mapping supports context switching, devmap_access() calls
+ devmap_do_ctxmgt(9F). Otherwise, devmap_access() calls
+ devmap_default_access(9F).
...
@@ -169,10 +169,10 @@
SEE ALSO
- devmap_map(9E), devmap_default_access(9F), devmap_do_ctxmgt(9F), de-
- vmap_callback_ctl(9S)
+ devmap_map(9E), devmap_default_access(9F), devmap_do_ctxmgt(9F),
+ devmap_callback_ctl(9S)
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 17 Jan 1997 devmap_access(9E)
+Oracle Solaris 11.4 9 September 2024 devmap_access(9E)
diff -NurbBw 11.4.72/man9e/devmap_contextmgt.9e 11.4.75/man9e/devmap_contextmgt.9e
--- 11.4.72/man9e/devmap_contextmgt.9e 2024-11-22 11:50:44.430111435 -0800
+++ 11.4.75/man9e/devmap_contextmgt.9e 2024-11-22 11:52:11.032118276 -0800
@@ -59,15 +59,15 @@
turning.
- dhp uniquely identifies the mapping and is used as an argument to de-
- vmap_load(9F) to validate the mapping. off and len define the range to
- be affected by the operations in devmap_contextmgt().
+ dhp uniquely identifies the mapping and is used as an argument to
+ devmap_load(9F) to validate the mapping. off and len define the range
+ to be affected by the operations in devmap_contextmgt().
The driver must check if there is already a mapping established at off
that needs to be unloaded. If a mapping exists at off, devmap_con-
- textmgt() must call devmap_unload(9F) on the current mapping. de-
- vmap_unload(9F) must be followed by devmap_load() on the mapping that
+ textmgt() must call devmap_unload(9F) on the current mapping.
+ devmap_unload(9F) must be followed by devmap_load() on the mapping that
generated this call to devmap_contextmgt(). devmap_unload(9F) unloads
the current mapping so that a call to devmap_access(9E), which causes
the system to call devmap_contextmgt(), will be generated the next time
@@ -143,10 +143,10 @@
SEE ALSO
- devmap_access(9E), devmap_do_ctxmgt(9F) devmap_load(9F), devmap_un-
- load(9F)
+ devmap_access(9E), devmap_do_ctxmgt(9F) devmap_load(9F),
+ devmap_unload(9F)
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 16 Jan 1997 devmap_contextmgt(9E)
+Oracle Solaris 11.4 9 September 2024 devmap_contextmgt(9E)
diff -NurbBw 11.4.72/man9e/devmap_dup.9e 11.4.75/man9e/devmap_dup.9e
--- 11.4.72/man9e/devmap_dup.9e 2024-11-22 11:50:44.458234443 -0800
+++ 11.4.75/man9e/devmap_dup.9e 2024-11-22 11:52:11.066523888 -0800
@@ -5,9 +5,9 @@
SYNOPSIS
#include <sys/ddi.h>
- #include <sys/sunddi.h
+ #include <sys/sunddi.h>
- int prefixdevmap_dup(devmap_cookie_t dhp, void *pvtp,
+ int prefix_devmap_dup(devmap_cookie_t dhp, void *pvtp,
devmap_cookie_t new_dhp, void **new_pvtp);
INTERFACE LEVEL
@@ -80,4 +80,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 21 Jan 1997 devmap_dup(9E)
+Oracle Solaris 11.4 9 September 2024 devmap_dup(9E)
diff -NurbBw 11.4.72/man9e/devmap_map.9e 11.4.75/man9e/devmap_map.9e
--- 11.4.72/man9e/devmap_map.9e 2024-11-22 11:50:44.486899494 -0800
+++ 11.4.75/man9e/devmap_map.9e 2024-11-22 11:52:11.097715277 -0800
@@ -7,7 +7,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixdevmap_map(devmap_cookie_t dhp, dev_t dev,
+ int prefix_devmap_map(devmap_cookie_t dhp, dev_t dev,
uint_t flags, offset_t off, size_t len, void **pvtp);
INTERFACE LEVEL
@@ -68,8 +68,8 @@
If the driver support context switching, it should store the mapping
- handle dhp in its private data *pvtp for later use in devmap_un-
- load(9F).
+ handle dhp in its private data *pvtp for later use in
+ devmap_unload(9F).
For a driver that supports context switching, flags indicates whether
@@ -123,4 +123,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 7 Jan 1997 devmap_map(9E)
+Oracle Solaris 11.4 9 September 2024 devmap_map(9E)
diff -NurbBw 11.4.72/man9e/devmap_unmap.9e 11.4.75/man9e/devmap_unmap.9e
--- 11.4.72/man9e/devmap_unmap.9e 2024-11-22 11:50:44.518476595 -0800
+++ 11.4.75/man9e/devmap_unmap.9e 2024-11-22 11:52:11.128797271 -0800
@@ -7,7 +7,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- void prefixdevmap_unmap(devmap_cookie_t dhp, void *pvtp,
+ void prefix_devmap_unmap(devmap_cookie_t dhp, void *pvtp,
offset_t off, size_tlen, devmap_cookie_t new_dhp1,
void **new_pvtp1, devmap_cookie_tnew_dhp2, void **new_pvtp2);
@@ -140,4 +140,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 21 Jan 1997 devmap_unmap(9E)
+Oracle Solaris 11.4 9 September 2024 devmap_unmap(9E)
diff -NurbBw 11.4.72/man9e/devmap.9e 11.4.75/man9e/devmap.9e
--- 11.4.72/man9e/devmap.9e 2024-11-22 11:50:44.551638042 -0800
+++ 11.4.75/man9e/devmap.9e 2024-11-22 11:52:11.174685635 -0800
@@ -8,7 +8,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixdevmap(dev_t dev, devmap_cookie_t dhp, offset_t off,
+ int prefix_devmap(dev_t dev, devmap_cookie_t dhp, offset_t off,
size_t len, size_t *maplen, uint_t model);
INTERFACE LEVEL
@@ -108,15 +108,15 @@
initializes the mapping parameters by mapping the control callback
structure (see devmap_callback_ctl(9S)), the device access attributes,
mapping length, maximum protection possible for the mapping, and op-
- tional mapping flags. See devmap_devmem_setup(9F) and de-
- vmap_umem_setup(9F) for further information on initializing the mapping
- parameters.
+ tional mapping flags. See devmap_devmem_setup(9F) and
+ devmap_umem_setup(9F) for further information on initializing the map-
+ ping parameters.
The system will copy the driver's devmap_callback_ctl(9S) data into its
private memory so the drivers do not need to keep the data structure
- after the return from either devmap_devmem_setup(9F) or de-
- vmap_umem_setup(9F).
+ after the return from either devmap_devmem_setup(9F) or
+ devmap_umem_setup(9F).
For device mappings, the system establishes the mapping to the physical
@@ -141,13 +141,13 @@
The following is an example of the implementation for the devmap() en-
- try point. For mapping device memory, devmap() calls devmap_de-
- vmem_setup(9F) with the register number, rnumber, and the offset within
- the register, roff. For mapping kernel memory, the driver must first
- allocate the kernel memory using ddi_umem_alloc(9F). For example,
- ddi_umem_alloc(9F) can be called in the attach(9E) routine. The result-
- ing kernel memory cookie is stored in the driver soft state structure,
- which is accessible from the devmap() entry point. See
+ try point. For mapping device memory, devmap() calls
+ devmap_devmem_setup(9F) with the register number, rnumber, and the off-
+ set within the register, roff. For mapping kernel memory, the driver
+ must first allocate the kernel memory using ddi_umem_alloc(9F). For ex-
+ ample, ddi_umem_alloc(9F) can be called in the attach(9E) routine. The
+ resulting kernel memory cookie is stored in the driver soft state
+ structure, which is accessible from the devmap() entry point. See
ddi_soft_state(9F). devmap() passes the cookie obtained from
ddi_umem_alloc(9F) and the offset within the allocated kernel memory to
devmap_umem_setup(9F). The corresponding ddi_umem_free(9F) can be made
@@ -237,13 +237,13 @@
SEE ALSO
- mmap(2), attach(9E), detach(9E), mmap(9E), segmap(9E), ddi_de-
- vmap_segmap(9F), ddi_model_convert_from(9F), ddi_soft_state(9F),
- ddi_umem_alloc(9F), ddi_umem_free(9F), devmap_devmem_setup(9F), de-
- vmap_setup(9F), devmap_umem_setup(9F), cb_ops(9S), devmap_call-
- back_ctl(9S)
+ mmap(2), attach(9E), detach(9E), mmap(9E), segmap(9E),
+ ddi_devmap_segmap(9F), ddi_model_convert_from(9F), ddi_soft_state(9F),
+ ddi_umem_alloc(9F), ddi_umem_free(9F), devmap_devmem_setup(9F),
+ devmap_setup(9F), devmap_umem_setup(9F), cb_ops(9S),
+ devmap_callback_ctl(9S)
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 04 July 2017 devmap(9E)
+Oracle Solaris 11.4 9 September 2024 devmap(9E)
diff -NurbBw 11.4.72/man9e/dump.9e 11.4.75/man9e/dump.9e
--- 11.4.72/man9e/dump.9e 2024-11-22 11:50:44.579704129 -0800
+++ 11.4.75/man9e/dump.9e 2024-11-22 11:52:11.220062032 -0800
@@ -36,9 +36,9 @@
completion dump() returns the status of the transfer.
- When the system is panicking, the calls of functions scheduled by time-
- out(9F) and ddi_trigger_softintr(9F) will never occur. Neither can de-
- lay(9F) be relied upon, since it is implemented via timeout(). See
+ When the system is panicking, the calls of functions scheduled by
+ timeout(9F) and ddi_trigger_softintr(9F) will never occur. Neither can
+ delay(9F) be relied upon, since it is implemented via timeout(). See
ddi_in_panic(9F).
@@ -53,4 +53,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 9 Oct 2001 dump(9E)
+Oracle Solaris 11.4 9 September 2024 dump(9E)
diff -NurbBw 11.4.72/man9e/getinfo.9e 11.4.75/man9e/getinfo.9e
--- 11.4.72/man9e/getinfo.9e 2024-11-22 11:50:44.609379621 -0800
+++ 11.4.75/man9e/getinfo.9e 2024-11-22 11:52:11.249957227 -0800
@@ -7,7 +7,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixgetinfo(dev_info_t *dip, ddi_info_cmd_t cmd,
+ int prefix_getinfo(dev_info_t *dip, ddi_info_cmd_t cmd,
void *arg, void **resultp);
INTERFACE LEVEL
@@ -103,10 +103,11 @@
nodes and use qassociate(9F). A driver that supports both style-1 and
style-2 minor nodes should return DDI_FAILURE for DDI_INFO_DEVT2IN-
STANCE and DDI_INFO_DEVT2DEVINFO getinfo() calls to style-2 minor
- nodes. (The correct association is already established by qassoci-
- ate(9F)). A driver that only supports style-2 minor nodes can use
- ddi_no_info(9F) for its getinfo() implementation. For drivers that do
- not follow these rules, the results of a modunload(8) of the driver or
- a cfgadm(8) remove of hardware controlled by the driver are undefined.
+ nodes. (The correct association is already established by
+ qassociate(9F)). A driver that only supports style-2 minor nodes can
+ use ddi_no_info(9F) for its getinfo() implementation. For drivers that
+ do not follow these rules, the results of a modunload(8) of the driver
+ or a cfgadm(8) remove of hardware controlled by the driver are unde-
+ fined.
-Oracle Solaris 11.4 16 Jan 2008 getinfo(9E)
+Oracle Solaris 11.4 9 September 2024 getinfo(9E)
diff -NurbBw 11.4.72/man9e/gld.9e 11.4.75/man9e/gld.9e
--- 11.4.72/man9e/gld.9e 2024-11-22 11:50:44.643205907 -0800
+++ 11.4.75/man9e/gld.9e 2024-11-22 11:52:11.284600034 -0800
@@ -14,25 +14,22 @@
int prefix_start(gld_mac_info_t *macinfo);
- int prefix_stop(gld_mac_info_t *
- macinfo);
+ int prefix_stop(gld_mac_info_t *macinfo);
- int prefix_set_mac_addr(gld_mac_info_t *
- macinfo, unsigned char *macaddr);
+ int prefix_set_mac_addr(gld_mac_info_t *macinfo,
+ unsigned char *macaddr);
- int prefix_set_multicast(gld_mac_info_t *
- macinfo, unsigned char *multicastaddr,
- int multiflag);
+ int prefix_set_multicast(gld_mac_info_t *macinfo,
+ unsigned char *multicastaddr, int multiflag);
int prefix_set_promiscuous(gld_mac_info_t *macinfo,
int promiscflag);
- int prefix_send(gld_mac_info_t *macinfo,
- mblk_t *mp);
+ int prefix_send(gld_mac_info_t *macinfo, mblk_t *mp);
uint_t prefix_intr(gld_mac_info_t *macinfo);
@@ -42,8 +39,8 @@
struct gld_stats *stats);
- int prefix_ioctl(gld_mac_info_t *macinfo,
- queue_t *q, mblk_t *mp);
+ int prefix_ioctl(gld_mac_info_t *macinfo, queue_t *q,
+ mblk_t *mp);
INTERFACE LEVEL
Solaris architecture specific (Solaris DDI).
@@ -305,4 +302,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 3 Jan 2001 gld(9E)
+Oracle Solaris 11.4 9 September 2024 gld(9E)
diff -NurbBw 11.4.72/man9e/identify.9e 11.4.75/man9e/identify.9e
--- 11.4.72/man9e/identify.9e 2024-11-22 11:50:44.671334509 -0800
+++ 11.4.75/man9e/identify.9e 2024-11-22 11:52:11.312788242 -0800
@@ -25,4 +25,4 @@
implementation to recompile. Otherwise, the compiler generates errors
about DDI_IDENTIFIED and DDI_NOT_IDENTIFIED.
-Oracle Solaris 11.4 11 Apr 2003 identify(9E)
+Oracle Solaris 11.4 9 September 2024 identify(9E)
diff -NurbBw 11.4.72/man9e/Intro.9e 11.4.75/man9e/Intro.9e
--- 11.4.72/man9e/Intro.9e 2024-11-22 11:50:44.711822081 -0800
+++ 11.4.75/man9e/Intro.9e 2024-11-22 11:52:11.351198504 -0800
@@ -219,11 +219,10 @@
Overview of Driver Entry-Point Routines and Naming Conventions
- By convention, a prefix string is added to the driver routine names.
- For a driver with the prefix prefix, the driver code may contain rou-
- tines named prefixopen, prefixclose, prefixread, prefixwrite, and so
- forth. All global variables associated with the driver should also use
- the same prefix.
+ By convention, driver routines use the name of the driver as a prefix.
+ For example, a driver named test will contain routines named test_open,
+ test_close, test_read, test_write, and so forth. All global variables
+ associated with the driver should also use the same prefix.
All routines and data should be declared as static.
@@ -383,4 +382,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 11 Dec 2020 Intro(9E)
+Oracle Solaris 11.4 9 September 2024 Intro(9E)
diff -NurbBw 11.4.72/man9e/ioctl.9e 11.4.75/man9e/ioctl.9e
--- 11.4.72/man9e/ioctl.9e 2024-11-22 11:50:44.745226419 -0800
+++ 11.4.75/man9e/ioctl.9e 2024-11-22 11:52:11.385301990 -0800
@@ -11,7 +11,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixioctl(dev_t dev, int cmd, intptr_t arg, int mode,
+ int prefix_ioctl(dev_t dev, int cmd, intptr_t arg, int mode,
cred_t *cred_p, int *rval_p);
INTERFACE LEVEL
@@ -234,4 +234,4 @@
I/O control commands to M_IOCTL messages, which are handled by the dri-
ver's put(9E) or srv(9E) routine.
-Oracle Solaris 11.4 3 Dec 1996 ioctl(9E)
+Oracle Solaris 11.4 9 September 2024 ioctl(9E)
diff -NurbBw 11.4.72/man9e/ks_snapshot.9e 11.4.75/man9e/ks_snapshot.9e
--- 11.4.72/man9e/ks_snapshot.9e 2024-11-22 11:50:44.776240173 -0800
+++ 11.4.75/man9e/ks_snapshot.9e 2024-11-22 11:52:11.414838668 -0800
@@ -37,8 +37,8 @@
kstat data to be copied to user-land. A driver can opt to use a custom
snapshot routine rather than the default snapshot routine; to take ad-
vantage of this feature, set the ks_snapshot field before calling the
- kstat_install() function. For more information, see the kstat_in-
- stall(9F) man page.
+ kstat_install() function. For more information, see the
+ kstat_install(9F) man page.
The ks_snapshot() function must have the following structure:
@@ -70,8 +70,8 @@
tent data) and will prevent the kstat from being removed.
1. ks_snaptime must be set through the gethrtime() function to
- timestamp the data. For more information, see the geth-
- rtime(9F) man page.
+ timestamp the data. For more information, see the
+ gethrtime(9F) man page.
2. Data gets copied from the kstat to the buffer on KSTAT_READ,
@@ -138,4 +138,4 @@
With the introduction of kstats v2, the ks_snapshot() function is dep-
recated. It may be removed in a future release of Oracle Solaris.
-Oracle Solaris 11.4 4 Dec 2002 ks_snapshot(9E)
+Oracle Solaris 11.4 9 September 2024 ks_snapshot(9E)
diff -NurbBw 11.4.72/man9e/ks_update.9e 11.4.75/man9e/ks_update.9e
--- 11.4.72/man9e/ks_update.9e 2024-11-22 11:50:44.805204007 -0800
+++ 11.4.75/man9e/ks_update.9e 2024-11-22 11:52:11.445473751 -0800
@@ -92,4 +92,4 @@
ate a kstat and set the ks2_update field to point to the update func-
tion. For more information, see the kstat2_create(9F) man page.
-Oracle Solaris 11.4 19 Aug 2016 ks_update(9E)
+Oracle Solaris 11.4 9 September 2024 ks_update(9E)
diff -NurbBw 11.4.72/man9e/mac_capab_rings.9e 11.4.75/man9e/mac_capab_rings.9e
--- 11.4.72/man9e/mac_capab_rings.9e 2024-11-22 11:50:44.837869395 -0800
+++ 11.4.75/man9e/mac_capab_rings.9e 2024-11-22 11:52:11.480076936 -0800
@@ -22,7 +22,7 @@
void prefix_group_remove_ring(mac_group_driver_t group_handle,
- mac_ring_driver_t ring_handle, mac_ring_type_t, rtype);
+ mac_ring_driver_t ring_handle, mac_ring_type_t rtype);
PARAMETERS
driver_handle Pointer to the driver-private handle which was speci-
@@ -95,8 +95,8 @@
The mr_gremring() function removes the specified ring from the speci-
fied ring group. This action should be implemented only in MAC drivers
- that implement dynamic ring grouping as described in mac_ca-
- pab_rings(9S).
+ that implement dynamic ring grouping as described in
+ mac_capab_rings(9S).
RETURN VALUES
None of these entry points have return values.
@@ -114,7 +114,7 @@
SEE ALSO
- attributes(7), mac_capab_rings(9S), mac_group_info(9S), mac_regis-
- ter(9S), mac_ring_info(9S)
+ attributes(7), mac_capab_rings(9S), mac_group_info(9S),
+ mac_register(9S), mac_ring_info(9S)
-Oracle Solaris 11.4 14 Nov 2011 mac_capab_rings(9E)
+Oracle Solaris 11.4 9 September 2024 mac_capab_rings(9E)
diff -NurbBw 11.4.72/man9e/mac_group_info.9e 11.4.75/man9e/mac_group_info.9e
--- 11.4.72/man9e/mac_group_info.9e 2024-11-22 11:50:44.870044718 -0800
+++ 11.4.75/man9e/mac_group_info.9e 2024-11-22 11:52:11.512125821 -0800
@@ -161,7 +161,7 @@
SEE ALSO
- attributes(7), mac_capab_rings(9S), mac_group_info(9S), mac_regis-
- ter(9S)
+ attributes(7), mac_capab_rings(9S), mac_group_info(9S),
+ mac_register(9S)
-Oracle Solaris 11.4 16 Jun 2011 mac_group_info(9E)
+Oracle Solaris 11.4 9 September 2024 mac_group_info(9E)
diff -NurbBw 11.4.72/man9e/mac_ring_info.9e 11.4.75/man9e/mac_ring_info.9e
--- 11.4.72/man9e/mac_ring_info.9e 2024-11-22 11:50:44.903929213 -0800
+++ 11.4.75/man9e/mac_ring_info.9e 2024-11-22 11:52:11.544791397 -0800
@@ -137,7 +137,7 @@
SEE ALSO
- attributes(7), mac_capab_rings(9E), mac_group_info(9E), mac_ca-
- pab_rings(9S), mac_register(9S)
+ attributes(7), mac_capab_rings(9E), mac_group_info(9E),
+ mac_capab_rings(9S), mac_register(9S)
-Oracle Solaris 11.4 27 Nov 2017 mac_ring_info(9E)
+Oracle Solaris 11.4 9 September 2024 mac_ring_info(9E)
diff -NurbBw 11.4.72/man9e/mac.9e 11.4.75/man9e/mac.9e
--- 11.4.72/man9e/mac.9e 2024-11-22 11:50:44.939957020 -0800
+++ 11.4.75/man9e/mac.9e 2024-11-22 11:52:11.583373038 -0800
@@ -272,8 +272,8 @@
The mc_start(), mc_setpromisc(), mc_multicst(), and mc_unicst() entry
- points return 0 on success and one of the error values specified by In-
- tro(2) on failure.
+ points return 0 on success and one of the error values specified by
+ Intro(2) on failure.
The mc_getcapab() entry point returns B_TRUE if the capability is sup-
@@ -425,4 +425,4 @@
mac_prop_info_set_perm(9F), mac_register(9F), mac_tx_update(9F),
mac_capab_lso(9S), mac_capab_rings(9S), mac_register(9S)
-Oracle Solaris 11.4 26 Apr 2016 mac(9E)
+Oracle Solaris 11.4 9 September 2024 mac(9E)
diff -NurbBw 11.4.72/man9e/mmap.9e 11.4.75/man9e/mmap.9e
--- 11.4.72/man9e/mmap.9e 2024-11-22 11:50:44.983170873 -0800
+++ 11.4.75/man9e/mmap.9e 2024-11-22 11:52:11.618871832 -0800
@@ -9,7 +9,7 @@
#include <sys/mman.h>
#include <sys/ddi.h>
- int prefixmmap(dev_t dev, off_t off, int prot);
+ int prefix_mmap(dev_t dev, off_t off, int prot);
INTERFACE LEVEL
This interface is obsolete. devmap(9E) should be used instead.
@@ -42,8 +42,8 @@
DESCRIPTION
Future releases of Solaris will provide this function for binary and
- source compatibility. However, for increased functionality, use de-
- vmap(9E) instead. See devmap(9E) for details.
+ source compatibility. However, for increased functionality, use
+ devmap(9E) instead. See devmap(9E) for details.
The mmap() entry point is a required entry point for character drivers
@@ -72,9 +72,9 @@
hat_getkpfnum(9F) accepts a kernel virtual address as an argument. A
kernel virtual address can be obtained by calling
ddi_regs_map_setup(9F) in the driver's attach(9E) routine. The corre-
- sponding ddi_regs_map_free(9F) call can be made in the driver's de-
- tach(9E) routine. Refer to the example below mmap Entry Point for more
- information.
+ sponding ddi_regs_map_free(9F) call can be made in the driver's
+ detach(9E) routine. Refer to the example below mmap Entry Point for
+ more information.
mmap() should only be supported for memory-mapped devices. See
@@ -88,12 +88,12 @@
or pointers. The driver needs to know whether there is a model mismatch
between the current thread and the kernel and take necessary action.
ddi_mmap_get_model(9F) can be use to get the C Language Type Model
- which the current thread expects. In combination with ddi_model_con-
- vert_from(9F) the driver can determine whether there is a data model
- mismatch between the current thread and the device driver. The device
- driver might have to adjust the shape of data structures before export-
- ing them to a user thread which supports a different data model. See
- ddi_mmap_get_model(9F) for an example.
+ which the current thread expects. In combination with
+ ddi_model_convert_from(9F) the driver can determine whether there is a
+ data model mismatch between the current thread and the device driver.
+ The device driver might have to adjust the shape of data structures be-
+ fore exporting them to a user thread which supports a different data
+ model. See ddi_mmap_get_model(9F) for an example.
RETURN VALUES
If the protection and offset are valid for the device, the driver
@@ -168,8 +168,8 @@
mmap(2), attributes(7), devmap(9E), attach(9E), detach(9E), segmap(9E),
ddi_btop(9F), ddi_get_soft_state(9F), ddi_mmap_get_model(9F),
ddi_model_convert_from(9F), ddi_regs_map_free(9F),
- ddi_regs_map_setup(9F), ddi_soft_state(9F), devmap_setup(9F), getmi-
- nor(9F), hat_getkpfnum(9F)
+ ddi_regs_map_setup(9F), ddi_soft_state(9F), devmap_setup(9F),
+ getminor(9F), hat_getkpfnum(9F)
Writing Device Drivers in Oracle Solaris 11.4
@@ -199,4 +199,4 @@
translation resources that are not locked down may cause unexpected and
undefined behavior.
-Oracle Solaris 11.4 11 May 2021 mmap(9E)
+Oracle Solaris 11.4 9 September 2024 mmap(9E)
diff -NurbBw 11.4.72/man9e/open.9e 11.4.75/man9e/open.9e
--- 11.4.72/man9e/open.9e 2024-11-22 11:50:45.027405568 -0800
+++ 11.4.75/man9e/open.9e 2024-11-22 11:52:11.652621944 -0800
@@ -13,7 +13,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixopen(dev_t *devp, int flag, int otyp,
+ int prefix_open(dev_t *devp, int flag, int otyp,
cred_t *cred_p);
STREAMS
@@ -22,7 +22,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixopen(queue_t *q, dev_t *devp, int oflag, int sflag,
+ int prefix_open(queue_t *q, dev_t *devp, int oflag, int sflag,
cred_t *cred_p);
INTERFACE LEVEL
@@ -159,13 +159,13 @@
create minor instances of the device. An example of this might be a
pseudo-terminal driver that creates a new pseudo-terminal whenever it
is opened. A driver that chooses the minor number dynamically, normally
- creates only one minor device node in attach(9E) with ddi_create_mi-
- nor_node(9F). It then changes the minor number component of *devp using
- makedevice(9F) and getmajor(9F). The driver needs to keep track of
- available minor numbers internally. A driver that dynamically creates
- minor numbers might want to avoid returning the original minor number
- since returning the original minor will result in postponed dynamic
- opens when original minor close() call occurs.
+ creates only one minor device node in attach(9E) with
+ ddi_create_minor_node(9F). It then changes the minor number component
+ of *devp using makedevice(9F) and getmajor(9F). The driver needs to
+ keep track of available minor numbers internally. A driver that dynami-
+ cally creates minor numbers might want to avoid returning the original
+ minor number since returning the original minor will result in post-
+ poned dynamic opens when original minor close() call occurs.
*devp = makedevice(getmajor(*devp), new_minor);
@@ -176,8 +176,8 @@
SEE ALSO
close(2), exit(2), mmap(2), mount(2), munmap(2), open(2), attach(9E),
- close(9E), Intro(9E), ddi_create_minor_node(9F), getmajor(9F), getmi-
- nor(9F), makedevice(9F), nulldev(9F), cb_ops(9S)
+ close(9E), Intro(9E), ddi_create_minor_node(9F), getmajor(9F),
+ getminor(9F), makedevice(9F), nulldev(9F), cb_ops(9S)
Writing Device Drivers in Oracle Solaris 11.4
@@ -198,4 +198,4 @@
driver specified in CLONE_DEV in ddi_create_minor_node(9F) is not sup-
ported.
-Oracle Solaris 11.4 24 Apr 2008 open(9E)
+Oracle Solaris 11.4 9 September 2024 open(9E)
diff -NurbBw 11.4.72/man9e/power.9e 11.4.75/man9e/power.9e
--- 11.4.72/man9e/power.9e 2024-11-22 11:50:45.057430191 -0800
+++ 11.4.75/man9e/power.9e 2024-11-22 11:52:11.685460615 -0800
@@ -7,7 +7,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixpower(dev_info_t *dip, int component, int level);
+ int prefix_power(dev_info_t *dip, int component, int level);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required. If
@@ -89,4 +89,4 @@
Using Power Management
-Oracle Solaris 11.4 12 Dec 2003 power(9E)
+Oracle Solaris 11.4 9 September 2024 power(9E)
diff -NurbBw 11.4.72/man9e/print.9e 11.4.75/man9e/print.9e
--- 11.4.72/man9e/print.9e 2024-11-22 11:50:45.085803242 -0800
+++ 11.4.75/man9e/print.9e 2024-11-22 11:52:11.714534913 -0800
@@ -9,7 +9,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixprint(dev_t dev, char *str);
+ int prefix_print(dev_t dev, char *str);
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI). This entry point is re-
@@ -41,4 +41,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 15 Sep 1992 print(9E)
+Oracle Solaris 11.4 9 September 2024 print(9E)
diff -NurbBw 11.4.72/man9e/probe.9e 11.4.75/man9e/probe.9e
--- 11.4.72/man9e/probe.9e 2024-11-22 11:50:45.116174064 -0800
+++ 11.4.75/man9e/probe.9e 2024-11-22 11:52:11.744997277 -0800
@@ -8,7 +8,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- static int prefixprobe(dev_info_t *dip);
+ int prefix_probe(dev_info_t *dip);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required for
@@ -72,4 +72,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 13 Sep 2019 probe(9E)
+Oracle Solaris 11.4 9 September 2024 probe(9E)
diff -NurbBw 11.4.72/man9e/prop_op.9e 11.4.75/man9e/prop_op.9e
--- 11.4.72/man9e/prop_op.9e 2024-11-22 11:50:45.148634059 -0800
+++ 11.4.75/man9e/prop_op.9e 2024-11-22 11:52:11.774797748 -0800
@@ -8,7 +8,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixprop_op(dev_t dev, dev_info_t *dip,
+ int prefix_prop_op(dev_t dev, dev_info_t *dip,
ddi_prop_op_t prop_op, int flags, char *name, caddr_t valuep,
int *lengthp);
@@ -65,8 +65,8 @@
DESCRIPTION
prop_op() is an entry point which reports the values of certain proper-
ties of the driver or device to the system. Each driver must have a
- prefix prop_op entry point, but most drivers that do not need to cre-
- ate or manage their own properties can use ddi_prop_op() for this entry
+ prefix_prop_op entry point, but most drivers that do not need to create
+ or manage their own properties can use ddi_prop_op() for this entry
point. Then the driver can use ddi_prop_update(9F) to create properties
for its device.
@@ -141,4 +141,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 8 Jul 1996 prop_op(9E)
+Oracle Solaris 11.4 9 September 2024 prop_op(9E)
diff -NurbBw 11.4.72/man9e/put.9e 11.4.75/man9e/put.9e
--- 11.4.72/man9e/put.9e 2024-11-22 11:50:45.178410241 -0800
+++ 11.4.75/man9e/put.9e 2024-11-22 11:52:11.803916540 -0800
@@ -10,10 +10,10 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixrput(queue_t *q, mblk_t *mp); /* read side */
+ int prefix_rput(queue_t *q, mblk_t *mp); /* read side */
- int prefixwput(queue_t *q, mblk_t *mp); /* write side */
+ int prefix_wput(queue_t *q, mblk_t *mp); /* write side */
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI). This entry point is re-
@@ -78,8 +78,8 @@
put() routines do not have user context.
SEE ALSO
- srv(9E), putctl(9F), putctl1(9F), putnext(9F), putnextctl(9F), put-
- nextctl1(9F), putq(9F), qreply(9F), queue(9S), streamtab(9S)
+ srv(9E), putctl(9F), putctl1(9F), putnext(9F), putnextctl(9F),
+ putnextctl1(9F), putq(9F), qreply(9F), queue(9S), streamtab(9S)
Writing Device Drivers in Oracle Solaris 11.4
@@ -87,4 +87,4 @@
STREAMS Programming Guide
-Oracle Solaris 11.4 11 May 2021 put(9E)
+Oracle Solaris 11.4 9 September 2024 put(9E)
diff -NurbBw 11.4.72/man9e/quiesce.9e 11.4.75/man9e/quiesce.9e
--- 11.4.72/man9e/quiesce.9e 2024-11-22 11:50:45.208501900 -0800
+++ 11.4.75/man9e/quiesce.9e 2024-11-22 11:52:11.833156349 -0800
@@ -7,7 +7,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixquiesce(dev_info_t *dip);
+ int prefix_quiesce(dev_info_t *dip);
int ddi_quiesce_not_needed(dev_info_t *dip);
@@ -86,4 +86,4 @@
implementation must not create or tear down mappings, call FMA func-
tions, or create or cancel callbacks.
-Oracle Solaris 11.4 16 Sep 2008 quiesce(9E)
+Oracle Solaris 11.4 9 September 2024 quiesce(9E)
diff -NurbBw 11.4.72/man9e/read.9e 11.4.75/man9e/read.9e
--- 11.4.72/man9e/read.9e 2024-11-22 11:50:45.251313158 -0800
+++ 11.4.75/man9e/read.9e 2024-11-22 11:52:11.864357293 -0800
@@ -12,7 +12,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixread(dev_t dev, struct uio *uio_p, cred_t *cred_p);
+ int prefix_read(dev_t dev, struct uio *uio_p, cred_t *cred_p);
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI). This entry point is op-
@@ -78,4 +78,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 19 Nov 1997 read(9E)
+Oracle Solaris 11.4 9 September 2024 read(9E)
diff -NurbBw 11.4.72/man9e/segmap.9e 11.4.75/man9e/segmap.9e
--- 11.4.72/man9e/segmap.9e 2024-11-22 11:50:45.301648895 -0800
+++ 11.4.75/man9e/segmap.9e 2024-11-22 11:52:11.896642731 -0800
@@ -11,7 +11,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixsegmap(dev_t dev, off_t off, struct as *asp, caddr_t *addrp,
+ int prefix_segmap(dev_t dev, off_t off, struct as *asp, caddr_t *addrp,
off_t len, unsigned int prot, unsigned int maxprot, unsigned int flags,
cred_t *cred_p);
@@ -111,8 +111,9 @@
for you to validate the range to be mapped.
- o Assign device access attributes to the mapping. See ddi_de-
- vmap_segmap(9F), and ddi_device_acc_attr(9S) for details.
+ o Assign device access attributes to the mapping. See
+ ddi_devmap_segmap(9F), and ddi_device_acc_attr(9S) for de-
+ tails.
o Set up device contexts for the user mapping if your device
@@ -120,8 +121,8 @@
tails.
- o Perform the mapping with ddi_devmap_segmap(9F), or de-
- vmap_setup(9F) and return the status if it fails.
+ o Perform the mapping with ddi_devmap_segmap(9F), or
+ devmap_setup(9F) and return the status if it fails.
RETURN VALUES
@@ -141,10 +142,10 @@
spective routine.
SEE ALSO
- mmap(2), devmap(9E), ddi_devmap_segmap(9F), devmap_setup(9F), ddi_de-
- vice_acc_attr(9S)
+ mmap(2), devmap(9E), ddi_devmap_segmap(9F), devmap_setup(9F),
+ ddi_device_acc_attr(9S)
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 14 Jan 1997 segmap(9E)
+Oracle Solaris 11.4 9 September 2024 segmap(9E)
diff -NurbBw 11.4.72/man9e/sofop_attach_active.9e 11.4.75/man9e/sofop_attach_active.9e
--- 11.4.72/man9e/sofop_attach_active.9e 2024-11-22 11:50:45.336049403 -0800
+++ 11.4.75/man9e/sofop_attach_active.9e 2024-11-22 11:52:11.928275092 -0800
@@ -91,8 +91,8 @@
the new connection by returning SOF_RVAL_DEFER . The connection is un-
available to socket(3C) while it is deferred, but data and other proto-
col events can still call into entry points. The deferred connection is
- made available using sof_newconn_ready(9F), or discarded using sof_new-
- conn_close(9F).
+ made available using sof_newconn_ready(9F), or discarded using
+ sof_newconn_close(9F).
The sofop_detach() entry point is called when the filter is being de-
@@ -151,7 +151,7 @@
SEE ALSO
accept(3C), socket(3C), attributes(7), soconfig(8), sofop_notify(9E),
- sof_bypass(9F), sof_inject_data_in(9F), sof_newconn_close(9F), sof_new-
- conn_ready(9F), sof_ops(9S)
+ sof_bypass(9F), sof_inject_data_in(9F), sof_newconn_close(9F),
+ sof_newconn_ready(9F), sof_ops(9S)
-Oracle Solaris 11.4 9 May 2012 sofop_attach_active(9E)
+Oracle Solaris 11.4 9 September 2024 sofop_attach_active(9E)
diff -NurbBw 11.4.72/man9e/sofop_bind.9e 11.4.75/man9e/sofop_bind.9e
--- 11.4.72/man9e/sofop_bind.9e 2024-11-22 11:50:45.367896107 -0800
+++ 11.4.75/man9e/sofop_bind.9e 2024-11-22 11:52:11.960783666 -0800
@@ -179,8 +179,8 @@
SEE ALSO
accept(3C), bind(3C), connect(3C), getpeername(3C), getsockname(3C),
- getsockopt(3C), listen(3C), setsockopt(3C), shutdown(3C), attrib-
- utes(7), sof_bypass(9F), sof_flowctrl_data_in(9F), sof_in-
- ject_data_in(9F), sof_ops(9S)
+ getsockopt(3C), listen(3C), setsockopt(3C), shutdown(3C),
+ attributes(7), sof_bypass(9F), sof_flowctrl_data_in(9F),
+ sof_inject_data_in(9F), sof_ops(9S)
-Oracle Solaris 11.4 9 May 2012 sofop_bind(9E)
+Oracle Solaris 11.4 9 September 2024 sofop_bind(9E)
diff -NurbBw 11.4.72/man9e/sofop_data_in.9e 11.4.75/man9e/sofop_data_in.9e
--- 11.4.72/man9e/sofop_data_in.9e 2024-11-22 11:50:45.403083351 -0800
+++ 11.4.75/man9e/sofop_data_in.9e 2024-11-22 11:52:11.992723234 -0800
@@ -116,4 +116,4 @@
sof_mblk_create(9F), sof_mblk_msghdr(9F), datab(9S), msgb(9S),
sof_ops(9S)
-Oracle Solaris 11.4 24 Nov 2014 sofop_data_in(9E)
+Oracle Solaris 11.4 9 September 2024 sofop_data_in(9E)
diff -NurbBw 11.4.72/man9e/sofop_notify.9e 11.4.75/man9e/sofop_notify.9e
--- 11.4.72/man9e/sofop_notify.9e 2024-11-22 11:50:45.434496451 -0800
+++ 11.4.75/man9e/sofop_notify.9e 2024-11-22 11:52:12.027948905 -0800
@@ -100,4 +100,4 @@
SEE ALSO
Intro(2), attributes(7), sof_ops(9S)
-Oracle Solaris 11.4 9 May 2012 sofop_notify(9E)
+Oracle Solaris 11.4 9 September 2024 sofop_notify(9E)
diff -NurbBw 11.4.72/man9e/srv.9e 11.4.75/man9e/srv.9e
--- 11.4.72/man9e/srv.9e 2024-11-22 11:50:45.465439061 -0800
+++ 11.4.75/man9e/srv.9e 2024-11-22 11:52:12.059543988 -0800
@@ -10,10 +10,10 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixrsrv(queue_t *q); /* read side */
+ int prefix_rsrv(queue_t *q); /* read side */
- int prefixwsrv(queue_t *q); /* write side */
+ int prefix_wsrv(queue_t *q); /* write side */
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI). This entry point is re-
@@ -49,8 +49,8 @@
A message is first passed to a module's or driver's put(9E) routine,
which may or may not do some processing. It must then either:
- o Pass the message to the next stream component with put-
- next(9F).
+ o Pass the message to the next stream component with
+ putnext(9F).
o If a srv() routine has been included, it may call putq(9F)
@@ -132,4 +132,4 @@
pointer. Use of nulldev(9F) for a srv() routine can result in flow con-
trol errors.
-Oracle Solaris 11.4 20 Aug 2019 srv(9E)
+Oracle Solaris 11.4 9 September 2024 srv(9E)
diff -NurbBw 11.4.72/man9e/strategy.9e 11.4.75/man9e/strategy.9e
--- 11.4.72/man9e/strategy.9e 2024-11-22 11:50:45.494485059 -0800
+++ 11.4.75/man9e/strategy.9e 2024-11-22 11:52:12.088114285 -0800
@@ -9,7 +9,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixstrategy(struct buf *bp);
+ int prefix_strategy(struct buf *bp);
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI). This entry point is re-
@@ -45,4 +45,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 6 Nov 2003 strategy(9E)
+Oracle Solaris 11.4 9 September 2024 strategy(9E)
diff -NurbBw 11.4.72/man9e/tran_abort.9e 11.4.75/man9e/tran_abort.9e
--- 11.4.72/man9e/tran_abort.9e 2024-11-22 11:50:45.524199070 -0800
+++ 11.4.75/man9e/tran_abort.9e 2024-11-22 11:52:12.118302554 -0800
@@ -6,7 +6,7 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- int prefixtran_abort(struct scsi_address *ap,
+ int prefix_tran_abort(struct scsi_address *ap,
struct scsi_pkt *pkt);
INTERFACE LEVEL
@@ -67,4 +67,4 @@
If pkt_reason already indicates that an earlier error had occurred,
tran_abort() should not overwrite pkt_reason with CMD_ABORTED.
-Oracle Solaris 11.4 17 Aug 2005 tran_abort(9E)
+Oracle Solaris 11.4 9 September 2024 tran_abort(9E)
diff -NurbBw 11.4.72/man9e/tran_bus_reset.9e 11.4.75/man9e/tran_bus_reset.9e
--- 11.4.72/man9e/tran_bus_reset.9e 2024-11-22 11:50:45.566669561 -0800
+++ 11.4.75/man9e/tran_bus_reset.9e 2024-11-22 11:52:12.147521267 -0800
@@ -4,9 +4,9 @@
tran_bus_reset - reset a SCSI bus
SYNOPSIS
- #include <sys/scsi/scsi.h> int prefix
+ #include <sys/scsi/scsi.h>
- tran_bus_reset(dev_info_t *hba_dip, int level);
+ int prefix_tran_bus_reset(dev_info_t *hba_dip, int level);
INTERFACE LEVEL
Solaris DDI
@@ -60,4 +60,4 @@
SEE ALSO
attributes(7), tran_quiesce(9E), scsi_hba_tran(9S)
-Oracle Solaris 11.4 17 Mar 1999 tran_bus_reset(9E)
+Oracle Solaris 11.4 9 September 2024 tran_bus_reset(9E)
diff -NurbBw 11.4.72/man9e/tran_dmafree.9e 11.4.75/man9e/tran_dmafree.9e
--- 11.4.72/man9e/tran_dmafree.9e 2024-11-22 11:50:45.594362606 -0800
+++ 11.4.75/man9e/tran_dmafree.9e 2024-11-22 11:52:12.179042524 -0800
@@ -6,7 +6,7 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- void prefixtran_dmafree(struct scsi_address *ap, struct scsi_pkt *pkt);
+ void prefix_tran_dmafree(struct scsi_address *ap, struct scsi_pkt *pkt);
INTERFACE LEVEL
Solaris architecture specific (Solaris DDI).
@@ -21,8 +21,8 @@
DESCRIPTION
The tran_dmafree() vector in the scsi_hba_tran structure must be ini-
tialized during the HBA driver's attach() to point to an HBA entry
- point to be called when a target driver calls scsi_dmafree(9F). See at-
- tach(9E) and scsi_hba_tran(9S).
+ point to be called when a target driver calls scsi_dmafree(9F). See
+ attach(9E) and scsi_hba_tran(9S).
tran_dmafree() must deallocate any DMA resources previously allocated
@@ -34,8 +34,8 @@
SEE ALSO
attach(9E), tran_destroy_pkt(9E), tran_init_pkt(9E), scsi_dmafree(9F),
- scsi_dmaget(9F), scsi_hba_attach(9F), scsi_init_pkt(9F), scsi_ad-
- dress(9S), scsi_hba_tran(9S), scsi_pkt(9S)
+ scsi_dmaget(9F), scsi_hba_attach(9F), scsi_init_pkt(9F),
+ scsi_address(9S), scsi_hba_tran(9S), scsi_pkt(9S)
Writing Device Drivers in Oracle Solaris 11.4
@@ -44,4 +44,4 @@
A target driver may call tran_dmafree() on packets for which no DMA re-
sources were allocated.
-Oracle Solaris 11.4 30 Aug 1995 tran_dmafree(9E)
+Oracle Solaris 11.4 9 September 2024 tran_dmafree(9E)
diff -NurbBw 11.4.72/man9e/tran_getcap.9e 11.4.75/man9e/tran_getcap.9e
--- 11.4.72/man9e/tran_getcap.9e 2024-11-22 11:50:45.625332799 -0800
+++ 11.4.75/man9e/tran_getcap.9e 2024-11-22 11:52:12.212037749 -0800
@@ -6,10 +6,10 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- int prefixtran_getcap(struct scsi_address *ap, char *cap, int whom);
+ int prefix_tran_getcap(struct scsi_address *ap, char *cap, int whom);
- int prefixtran_setcap(struct scsi_address *ap, char *cap, int value,
+ int prefix_tran_setcap(struct scsi_address *ap, char *cap, int value,
int whom);
INTERFACE LEVEL
@@ -82,4 +82,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 30 Aug 1995 tran_getcap(9E)
+Oracle Solaris 11.4 9 September 2024 tran_getcap(9E)
diff -NurbBw 11.4.72/man9e/tran_init_pkt.9e 11.4.75/man9e/tran_init_pkt.9e
--- 11.4.72/man9e/tran_init_pkt.9e 2024-11-22 11:50:45.656071263 -0800
+++ 11.4.75/man9e/tran_init_pkt.9e 2024-11-22 11:52:12.244411449 -0800
@@ -7,13 +7,13 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- struct scsi_pkt *prefixtran_init_pkt(struct scsi_address *ap,
+ struct scsi_pkt *prefix_tran_init_pkt(struct scsi_address *ap,
struct scsi_pkt *pkt, struct buf *bp, int cmdlen,
int statuslen, int tgtlen, intflags, int (*callback)(caddr_t),
caddr_t arg);
- void prefixtran_destroy_pkt(struct scsi_address *ap,
+ void prefix_tran_destroy_pkt(struct scsi_address *ap,
struct scsi_pkt *pkt);
INTERFACE LEVEL
@@ -150,10 +150,10 @@
fore returning NULL.
SEE ALSO
- attach(9E), tran_setup_pkt(9E), tran_sync_pkt(9E), biodone(9F), bioer-
- ror(9F), ddi_dma_buf_bind_handle(9F), ddi_dma_buf_setup(9F),
- kmem_cache_create(9F), scsi_alloc_consistent_buf(9F), scsi_de-
- stroy_pkt(9F), scsi_hba_attach(9F), scsi_hba_pkt_alloc(9F),
+ attach(9E), tran_setup_pkt(9E), tran_sync_pkt(9E), biodone(9F),
+ bioerror(9F), ddi_dma_buf_bind_handle(9F), ddi_dma_buf_setup(9F),
+ kmem_cache_create(9F), scsi_alloc_consistent_buf(9F),
+ scsi_destroy_pkt(9F), scsi_hba_attach(9F), scsi_hba_pkt_alloc(9F),
scsi_hba_pkt_free(9F), scsi_init_pkt(9F), buf(9S), scsi_address(9S),
scsi_hba_tran(9S), scsi_pkt(9S)
@@ -175,4 +175,4 @@
this cache by direct use of kmem_cache_create(9F) adds a compile-time
dependency on scsi_pkt() size, which is illegal.
-Oracle Solaris 11.4 7 Apr 2020 tran_init_pkt(9E)
+Oracle Solaris 11.4 9 September 2024 tran_init_pkt(9E)
diff -NurbBw 11.4.72/man9e/tran_quiesce.9e 11.4.75/man9e/tran_quiesce.9e
--- 11.4.72/man9e/tran_quiesce.9e 2024-11-22 11:50:45.691664811 -0800
+++ 11.4.75/man9e/tran_quiesce.9e 2024-11-22 11:52:12.273042867 -0800
@@ -6,10 +6,10 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- int prefixtran_quiesce(dev_info_t *hba_dip);
+ int prefix_tran_quiesce(dev_info_t *hba_dip);
- int prefixtran_unquiesce(dev_info_t *hba_dip);
+ int prefix_tran_unquiesce(dev_info_t *hba_dip);
INTERFACE LEVEL
Solaris DDI
@@ -55,4 +55,4 @@
SEE ALSO
attributes(7), tran_bus_reset(9E), scsi_hba_tran(9S)
-Oracle Solaris 11.4 31 Jan 1999 tran_quiesce(9E)
+Oracle Solaris 11.4 9 September 2024 tran_quiesce(9E)
diff -NurbBw 11.4.72/man9e/tran_reset_notify.9e 11.4.75/man9e/tran_reset_notify.9e
--- 11.4.72/man9e/tran_reset_notify.9e 2024-11-22 11:50:45.719687302 -0800
+++ 11.4.75/man9e/tran_reset_notify.9e 2024-11-22 11:52:12.307934849 -0800
@@ -6,7 +6,7 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- int prefixtran_reset_notify(struct scsi_address *ap, int flag,
+ int prefix_tran_reset_notify(struct scsi_address *ap, int flag,
void (*callback)(caddr_t), caddr_t arg);
INTERFACE LEVEL
@@ -34,8 +34,8 @@
The tran_reset_notify() vector in the scsi_hba_tran(9S) structure may
be initialized in the HBA driver's attach(9E) routine to point to the
- HBA entry point to be called when a target driver calls scsi_reset_no-
- tify(9F).
+ HBA entry point to be called when a target driver calls
+ scsi_reset_notify(9F).
The argument flag is used to register or cancel the notification. The
@@ -72,4 +72,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 7 Apr 2020 tran_reset_notify(9E)
+Oracle Solaris 11.4 9 September 2024 tran_reset_notify(9E)
diff -NurbBw 11.4.72/man9e/tran_reset.9e 11.4.75/man9e/tran_reset.9e
--- 11.4.72/man9e/tran_reset.9e 2024-11-22 11:50:45.749815387 -0800
+++ 11.4.75/man9e/tran_reset.9e 2024-11-22 11:52:12.337453324 -0800
@@ -6,7 +6,7 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- int prefixtran_reset(struct scsi_address *ap, int level);
+ int prefix_tran_reset(struct scsi_address *ap, int level);
INTERFACE LEVEL
Solaris architecture specific (Solaris DDI).
@@ -91,4 +91,4 @@
a particular pkt, tran_reset() should not overwrite pkt_reason with
CMD_RESET.
-Oracle Solaris 11.4 17 Aug 2005 tran_reset(9E)
+Oracle Solaris 11.4 9 September 2024 tran_reset(9E)
diff -NurbBw 11.4.72/man9e/tran_setup_pkt.9e 11.4.75/man9e/tran_setup_pkt.9e
--- 11.4.72/man9e/tran_setup_pkt.9e 2024-11-22 11:50:45.781001596 -0800
+++ 11.4.75/man9e/tran_setup_pkt.9e 2024-11-22 11:52:12.367560771 -0800
@@ -131,9 +131,9 @@
Allocating and freeing a DMA handle are examples of something that
- could be done in the constructor and destructor. See kmem_cache_cre-
- ate(9F) for additional restrictions on what actions can be performed in
- a constructor and destructor.
+ could be done in the constructor and destructor. See
+ kmem_cache_create(9F) for additional restrictions on what actions can
+ be performed in a constructor and destructor.
HBA drivers that implement tran_setup_pkt() must signal scsi_pkt(9S)
@@ -144,11 +144,12 @@
tran_setup_pkt() must return zero on success, and -1 on failure.
SEE ALSO
- attach(9E), tran_sync_pkt(9E), bioerror(9F), ddi_dma_buf_bind_han-
- dle(9F), kmem_cache_create(9F), scsi_alloc_consistent_buf(9F), scsi_de-
- stroy_pkt(9F), scsi_hba_attach(9F), scsi_hba_pkt_alloc(9F),
- scsi_hba_pkt_comp(9F), scsi_hba_pkt_free(9F), scsi_init_pkt(9F),
- buf(9S), scsi_address(9S), scsi_hba_tran(9S), scsi_pkt(9S)
+ attach(9E), tran_sync_pkt(9E), bioerror(9F),
+ ddi_dma_buf_bind_handle(9F), kmem_cache_create(9F),
+ scsi_alloc_consistent_buf(9F), scsi_destroy_pkt(9F),
+ scsi_hba_attach(9F), scsi_hba_pkt_alloc(9F), scsi_hba_pkt_comp(9F),
+ scsi_hba_pkt_free(9F), scsi_init_pkt(9F), buf(9S), scsi_address(9S),
+ scsi_hba_tran(9S), scsi_pkt(9S)
Writing Device Drivers in Oracle Solaris 11.4
@@ -157,4 +158,4 @@
pkt_scblen > sizeof(struct scsi_arq_status) implies the equivalent of
the PKT_XARQ flag passed to scsi_init_pkt(9F).
-Oracle Solaris 11.4 7 Apr 2020 tran_setup_pkt(9E)
+Oracle Solaris 11.4 9 September 2024 tran_setup_pkt(9E)
diff -NurbBw 11.4.72/man9e/tran_start.9e 11.4.75/man9e/tran_start.9e
--- 11.4.72/man9e/tran_start.9e 2024-11-22 11:50:45.814608589 -0800
+++ 11.4.75/man9e/tran_start.9e 2024-11-22 11:52:12.399962782 -0800
@@ -6,7 +6,7 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- int prefixtran_start(struct scsi_address *ap,
+ int prefix_tran_start(struct scsi_address *ap,
struct scsi_pkt *pkt);
INTERFACE LEVEL
@@ -173,4 +173,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 17 Aug 2005 tran_start(9E)
+Oracle Solaris 11.4 9 September 2024 tran_start(9E)
diff -NurbBw 11.4.72/man9e/tran_sync_pkt.9e 11.4.75/man9e/tran_sync_pkt.9e
--- 11.4.72/man9e/tran_sync_pkt.9e 2024-11-22 11:50:45.842510960 -0800
+++ 11.4.75/man9e/tran_sync_pkt.9e 2024-11-22 11:52:12.429365273 -0800
@@ -6,7 +6,7 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- void prefixtran_sync_pkt(struct scsi_address *ap,
+ void prefix_tran_sync_pkt(struct scsi_address *ap,
struct scsi_pkt *pkt);
INTERFACE LEVEL
@@ -43,4 +43,4 @@
A target driver may call tran_sync_pkt() on packets for which no DMA
resources were allocated.
-Oracle Solaris 11.4 1 Nov 1993 tran_sync_pkt(9E)
+Oracle Solaris 11.4 9 September 2024 tran_sync_pkt(9E)
diff -NurbBw 11.4.72/man9e/tran_tgt_free.9e 11.4.75/man9e/tran_tgt_free.9e
--- 11.4.72/man9e/tran_tgt_free.9e 2024-11-22 11:50:45.874886409 -0800
+++ 11.4.75/man9e/tran_tgt_free.9e 2024-11-22 11:52:12.457580304 -0800
@@ -7,7 +7,7 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- void prefixtran_tgt_free(dev_info_t *hba_dip, dev_info_t *tgt_dip,
+ void prefix_tran_tgt_free(dev_info_t *hba_dip, dev_info_t *tgt_dip,
scsi_hba_tran_t *hba_tran, struct scsi_device *sd);
INTERFACE LEVEL
@@ -42,10 +42,10 @@
performed for this target device instance.
SEE ALSO
- attach(9E), detach(9E), tran_tgt_init(9E), tran_tgt_probe(9E), scsi_de-
- vice(9S), scsi_hba_tran(9S)
+ attach(9E), detach(9E), tran_tgt_init(9E), tran_tgt_probe(9E),
+ scsi_device(9S), scsi_hba_tran(9S)
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 1 Nov 1993 tran_tgt_free(9E)
+Oracle Solaris 11.4 9 September 2024 tran_tgt_free(9E)
diff -NurbBw 11.4.72/man9e/tran_tgt_init.9e 11.4.75/man9e/tran_tgt_init.9e
--- 11.4.72/man9e/tran_tgt_init.9e 2024-11-22 11:50:45.904950673 -0800
+++ 11.4.75/man9e/tran_tgt_init.9e 2024-11-22 11:52:12.490140467 -0800
@@ -7,7 +7,7 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- int prefixtran_tgt_init(dev_info_t *hba_dip, dev_info_t *tgt_dip,
+ int prefix_tran_tgt_init(dev_info_t *hba_dip, dev_info_t *tgt_dip,
scsi_hba_tran_t *hba_tran, struct scsi_device *sd);
INTERFACE LEVEL
@@ -71,4 +71,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 23 Jan 2012 tran_tgt_init(9E)
+Oracle Solaris 11.4 9 September 2024 tran_tgt_init(9E)
diff -NurbBw 11.4.72/man9e/tran_tgt_probe.9e 11.4.75/man9e/tran_tgt_probe.9e
--- 11.4.72/man9e/tran_tgt_probe.9e 2024-11-22 11:50:45.937665456 -0800
+++ 11.4.75/man9e/tran_tgt_probe.9e 2024-11-22 11:52:12.522623483 -0800
@@ -6,8 +6,8 @@
SYNOPSIS
#include <sys/scsi/scsi.h>
- int prefixtran_tgt_probe(struct scsi_device *sd, int (*waitfunc,
- void)););
+ int prefix_tran_tgt_probe(struct scsi_device *sd,
+ int (*waitfunc)(void));
INTERFACE LEVEL
Solaris architecture specific (Solaris DDI).
@@ -59,4 +59,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 1 Nov 1993 tran_tgt_probe(9E)
+Oracle Solaris 11.4 9 September 2024 tran_tgt_probe(9E)
diff -NurbBw 11.4.72/man9e/write.9e 11.4.75/man9e/write.9e
--- 11.4.72/man9e/write.9e 2024-11-22 11:50:45.976871081 -0800
+++ 11.4.75/man9e/write.9e 2024-11-22 11:52:12.556261458 -0800
@@ -11,7 +11,7 @@
#include <sys/ddi.h>
#include <sys/sunddi.h>
- int prefixwrite(dev_t dev, struct uio *uio_p, cred_t *cred_p);
+ int prefix_write(dev_t dev, struct uio *uio_p, cred_t *cred_p);
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI). This entry point is op-
@@ -71,4 +71,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 28 Mar 1997 write(9E)
+Oracle Solaris 11.4 9 September 2024 write(9E)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment