Skip to content

Instantly share code, notes, and snippets.

@alanc

alanc/SRU69-man-page-changes.diff

Last active May 25, 2024 20:42
Show Gist options
  • Save alanc/8f56b6ce962378bf8306cd1dd1f34b57 to your computer and use it in GitHub Desktop.
Save alanc/8f56b6ce962378bf8306cd1dd1f34b57 to your computer and use it in GitHub Desktop.
Download ZIP
Changes to core OS man pages in Oracle Solaris 11.4 SRU 69
Raw
Solaris-11.4-SRU69-man-page-changes.txt
14880338 Add support for preadv(2) and pwritev(2)
19509664 libsuri create/destroy support for dev:zvol URI with optional lofi layer
22045440 mdb -k could try harder to find kernel crash dumps
22364430 zpool status information about remaining time for resilvering is confusing
32591921 ldapservercfg.8 specifies incorrect TLS certificate file
33028982 ldapservercfg default cert should be from identity:cert
33224904 nfs getattr kernel call doesn't return xvattrs
33816766 Apply new RFC values to ipaddrsel(8) defaults table
33857908 Implement RFC6724 rule to prefer temp source addresses over public
33866564 Implement RFC6724 address selection rule changes
34704147 modinfo should have a field for ELF signature state
35284827 problem in KERNEL/ARCH-X86
35565009 Need per thread variables
35796558 reflink's preserve should cause extended (file) attributes to be reflinked
35808514 Update nss-mdns to query avahi-daemon directly. Remove mdnsd.
35811619 zoneadm log subcommand for viewing messages and console logs
35895154 XML characters table is garbled when viewing in Grok
35993356 direct support for non-global zones on ZVOL based URIs
36009344 process(5) man page typos
36031544 ps(1) ISO 8601 format for process start time
36040445 want examples to stop DHCP rewriting /etc/resolv.conf with DNS info
36066883 add a grace period property for the automatic deletion of expired retained files
36103197 mdb should support breakpoints when functions return
36104039 passwd(1) does not list newer exit codes
36119418 Assorted fixes for Section 5 man pages
36119468 cp(1), fsync(1), and mv(1) should reference fsync(3C) instead of fsync(2)
36122801 kstat2(3KSTAT2) kstat2_open example is missing a parameter
36158785 mdb should support breakpoints that only fire below a frame
36159112 Man page syslogd(1M) and syslogd(8) has incorrect description for command-line switch in use
36164461 zonecfg man page literals do not need quotes
36172938 Would like to be able to write to stderr with ::printf
36175096 Duplicate text in limits.h(3HEAD)
36201042 Address an error in fix for ER 36040445
36225745 suriadm man page incorrect URI type info for lookup-uri subcommand
36281937 libsuri incorrect error messages for ZVOL based dev URIs with rdsk
36354133 cp -p and -/ really shouldn't preserve retention time
36377324 mkstemp(3c) does not specify the permission of the created file
36416832 Assorted fixes for Section 4d man pages
36416863 Move avahi-daemon(8) to alphabetical order in See Also lists in man pages
PSARC/2023/048 xvattr support for NFSv4
PSARC/2023/117 Replace mDNS with Avahi
PSARC/2023/122 ldapservercfg(8) to use Default System TLS Certificate
PSARC/2023/132 zoneadm(8) log subcommand
PSARC/2024/003 System calls preadv(2) and pwritev(2)
PSARC/2024/004 ZFS Filesystem Retention Onexpiry Delete Grace Period
PSARC/2024/010 ps(1) ISO start time field
PSARC/2024/016 Optional lofi layer support for dev:zvol/* storage URIs
PSARC/2024/017 Non-global Zones on ZVOLs
PSARC/2024/031 sxadm(1m) update for Intel Gather Data Sampling Vulnerabilities
PSARC/2024/033 modinfo additions: SYS field, -x -h/--scale, -?/--help options
PSARC/2024/034 mdb searching for kernel crash dumps
Copyright (c) 1983, 2024, Oracle and/or its affiliates.
Raw
SRU69-man-page-changes.diff
diff -NurbBw 11.4.66/man1/cp.1 11.4.69/man1/cp.1
--- 11.4.66/man1/cp.1 2024-05-25 09:57:46.925657970 -0700
+++ 11.4.69/man1/cp.1 2024-05-25 09:58:10.649742762 -0700
@@ -95,7 +95,9 @@
-p Preserve. The cp utility duplicates not only the contents of
source_file, but also attempts to preserve its ACL, access and
modification times, extended attributes, extended system attrib-
- utes, file mode, and owner and group ids.
+ utes, file mode, and owner and group ids. This includes all the
+ same things for any extended attributes. Retention time is ex-
+ cluded from the extended system attributes.
If cp is unable to preserve the access and modification times,
extended attributes, or the file mode, cp does not consider it a
@@ -126,18 +128,20 @@
-R Same as -r, except pipes are replicated, not read from.
- -S Call fsync(2) on the target file's file descriptor.
+ -S Call fsync(3C) on the target file's file descriptor.
-z Fast Copy. cp will reflink the source and destination files.
- If this option is used, cp will not overwrite the destination
- file. Additionally, -f and -i are ignored.
+ If this option is used, cp will not overwrite an existing desti-
+ nation file. Additionally, -f and -i are ignored.
- For more information, see the reflink(3C) man page.
+ When the -p option is used with -z, -@ and -/ are ignored and
+ system attributes will be copied. Any extended attributes will be
+ copied using reflink as well, including any of the extended at-
+ tributes' extended system attributes.
- When the -p option is used, the extended file attributes will be
- copied normally, not using reflink.
+ For more information, see the reflink(3C) man page.
-@ Preserves extended attributes. cp attempts to copy all of the
@@ -149,10 +153,13 @@
Along with the file's data, the cp utility attempts to copy ex-
tended attributes and extended system attributes from each source
file, and extended system attributes associated with extended at-
- tributes to the destination file. If cp is unable to copy ex-
- tended attributes or extended system attributes, then a diagnos-
- tic message is written to stderr and (after processing any re-
- maining operands) exits with a non-zero exit status.
+ tributes to the destination file. Retention time is excluded from
+ the extended system attributes.
+
+ If cp is unable to copy extended attributes or extended system
+ attributes, then a diagnostic message is written to stderr and
+ (after processing any remaining operands) exits with a non-zero
+ exit status.
@@ -255,7 +262,7 @@
- The following example copies extended file system attributes:
+ The following example copies extended system attributes:
$ ls -/ c file1
@@ -339,8 +346,9 @@
SEE ALSO
- chmod(1), chown(1), fsync(1), fsync(2), utime(2), fgetattr(3C), attrib-
- utes(7), environ(7), fsattr(7), locale(7), privileges(7), standards(7)
+ chmod(1), chown(1), fsync(1), utime(2), fgetattr(3C), fsync(3C), at-
+ tributes(7), environ(7), fsattr(7), locale(7), privileges(7), stan-
+ dards(7)
NOTES
The permission modes of the source file are preserved in the copy.
@@ -350,4 +358,37 @@
plicitly, thus allowing cp to recognize filename arguments that begin
with a -.
-Oracle Solaris 11.4 24 Aug 2023 cp(1)
+HISTORY
+ Support for the -S option was added in the Oracle Solaris 11.4.60 re-
+ lease.
+
+
+ Support for the -z option was added in the Oracle Solaris 11.4.0 re-
+ lease.
+
+
+ Support for the -/ option was added in the Oracle Solaris 11.0.0 re-
+ lease.
+
+
+ Support for the -H, -L, and -P options was added in the Solaris 10 3/05
+ release.
+
+
+ Support for the -@ option was added in the Solaris 9 release.
+
+
+ Support for the -R option was restored, and support for the -f option
+ was added in the Solaris 2.5 release.
+
+
+ The /usr/xpg4/bin/cp command was added in the Solaris 2.5 release.
+
+
+ The /usr/bin/cp command, with support for the -i, -p, and -r options,
+ has been included in all Sun and Oracle releases of Solaris. The
+ /usr/bin/cp command in Solaris 1.x releases also included support for
+ the -R option, which was not included in the Solaris 2.0 through 2.4
+ releases.
+
+Oracle Solaris 11.4 1 Mar 2024 cp(1)
diff -NurbBw 11.4.66/man1/fsync.1 11.4.69/man1/fsync.1
--- 11.4.66/man1/fsync.1 2024-05-25 09:57:46.957786312 -0700
+++ 11.4.69/man1/fsync.1 2024-05-25 09:58:10.681161265 -0700
@@ -7,22 +7,38 @@
/usr/bin/fsync [path ...]
DESCRIPTION
- For each path listed open the file and call fsync(2) on the file de-
+ For each path listed open the file and call fsync(3C) on the file de-
scriptor.
- If no path is specified then fsync(2) is called on standard output.
+ If no path is specified then fsync(3C) is called on standard output.
EXIT STATUS
The following exit values are returned:
- 0 fsync(2) succeeded for every path.
+ 0 fsync(3C) succeeded for every path.
>0 An error occurred.
+ATTRIBUTES
+ See attributes(7) for descriptions of the following attributes:
+
+ +------------------------------+-----------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------+
+ | Availability |system/core-os |
+ +------------------------------+-----------------------------+
+ | Interface Stability |Committed |
+ +------------------------------+-----------------------------+
+
+
SEE ALSO
- mv(1),fsync(2)
+ mv(1), fsync(3C)
+
+HISTORY
+ The fsync command was introduced in FreeBSD 4.3. It was added to So-
+ laris in Oracle Solaris 11.4.60.
-Oracle Solaris 11.4 8 March 2023 fsync(1)
+Oracle Solaris 11.4 18 Dec 2023 fsync(1)
diff -NurbBw 11.4.66/man1/mdb.1 11.4.69/man1/mdb.1
--- 11.4.66/man1/mdb.1 2024-05-25 09:57:47.092870318 -0700
+++ 11.4.69/man1/mdb.1 2024-05-25 09:58:10.805869214 -0700
@@ -6,7 +6,7 @@
SYNOPSIS
mdb [-fkmuwyAFMS][-a path] [+-o option] [-p pid][-s distance]
[-I path] [-L path] [-P prompt] [-R root]
- [-V dis-version] [object [core...] | core... | suffix]
+ [-V dis-version] [object [core...] | core... | suffix | latest ]
mdb -K [-F] --stop-entire-system
mdb -K [-F] --stop-entire-cluster-node
mdb -K [-F] --load-debugger
@@ -451,11 +451,21 @@
A variable is a variable name, a corresponding integer value, and a set
of attributes. A variable name is a sequence of letters, digits, under-
scores, or periods. A variable can be assigned a value using the > dcmd
- or ::typeset dcmd, and its attributes can be manipulated using the
- ::typeset dcmd. Each variable's value is represented as a 64-bit un-
- signed integer. A variable can have one or more of the following at-
- tributes: read-only (cannot be modified by the user), persistent (can-
- not be unset by the user), and tagged (user-defined indicator).
+ or ::typeset dcmd, or ::save dcmd and its attributes can be manipulated
+ using the ::typeset dcmd.
+
+
+ If a variable created by using the ::typeset then by default the vari-
+ able will be context local. Context local variables by default have the
+ value assigned when they were created by ::typeset otherwise they take
+ the value that was last assigned to them within the target's current
+ context (thread).
+
+
+ Each variable's value is represented as a 64-bit unsigned integer. A
+ variable can have one or more of the following attributes: read-only
+ (cannot be modified by the user), persistent (cannot be unset by the
+ user), and tagged (user-defined indicator).
Variables names with the string MDB_ and _MDB should not be used. These
@@ -524,6 +534,12 @@
created while mdb was attached.
+ MDB_THIS_EVENT
+
+ The event ID of the current event. This is only valid during an
+ event's callback.
+
+
MDB_SYSTOD
The number of seconds since the epoch on the system running mdb.
@@ -626,6 +642,23 @@
The id of the last software event to have been added to the target.
+ MDB_retaddr
+
+ The address to which the current function will return.
+
+
+ MDB_retbp
+
+ After an out breakpoint has been hit the address of function re-
+ turned from.
+
+
+ MDB_retval
+
+ The value returned by the previous function. This is only valid im-
+ mediately after a function returns.
+
+
In addition, the mdb kernel and process targets export the current val-
ues of the representative thread's register set as named variables. The
@@ -1779,7 +1812,8 @@
- [address] ::bp [ +/-dDeisT] [-c cmd] [-n count] sym[+offset] ...
+ [address] ::bp [ +/-BCdDeiosT] [-b function] [-c cmd] [-n count]
+ sym[+offset] ...
address :b [cmd ...]
The ::bp dcmd sets a breakpoint at each address or symbol plus off-
@@ -1789,6 +1823,42 @@
options have the same meaning as they do for the ::evset dcmd, as
described below.
+
+
+ -b function
+
+ Set the breakpoint to only fire below function in the call
+ stack. This option implies -C
+
+
+ -B
+
+ Set the breakpoint to only fire in or below the current stack
+ frame. This option implies -C
+
+
+ -C
+
+ Set the breakpoint to fire in the same thread (context) as the
+ current thread.
+
+
+ +C
+
+ Set the breakpoint to fire in the any thread. This is the de-
+ fault unless the context_events option is set.
+
+
+ -o
+
+ Set an out breakpoint. This breakpoint will fire when the func-
+ tion returns. This must be set before the function is entered.
+ When this event is hit the MDB_retbp variable will contain addr
+ or the symbol+offset used to declare the breakpoint.
+
+
+
+
The :b dcmd sets a breakpoint at the virtual address specified by
the expression preceding the dcmd. The arguments following the :b
dcmd are concatenated together to form the callback string. If this
@@ -1813,7 +1883,7 @@
it is able to identify a symbol plus offset that describes the
given address. This behavior can be disabled by specifying the -i
flag to the ::bp dcmd, or by setting the immediate_breakpoints op-
- tion. See -o.
+ tion. See ::set -o.
Breakpoints on symbols defined in a shared library should always be
set using a symbol name, rather than as an address expression. Such
@@ -1824,7 +1894,7 @@
lost. To protect from this mdb will convert breakpoints set in the
PLT to symbolic breakpoints. This behavior can be disabled by spec-
ifying the -i flag to the ::bp dcmd, or by setting the immedi-
- ate_breakpoints option. See -o.
+ ate_breakpoints option. See ::set -o.
@@ -2315,7 +2385,7 @@
- [flt] ::fltbp [ +/-dDehstT] [-c cmd] [-n count] flt ...
+ [flt] ::fltbp [ +/-BCdDehstT] [-b function] [-c cmd] [-n count] flt ...
Trace the specified machine faults. The faults are identified using
an optional fault number preceding the dcmd, or a list of fault
@@ -2325,6 +2395,34 @@
have the same meaning as they do for the ::evset dcmd.
+
+ -b function
+
+ Set the breakpoint to only fire below function in the call
+ stack. This option implies -C
+
+
+ -B
+
+ Set the breakpoint to only fire in or below the current stack
+ frame. This option implies -C
+
+
+ -C
+
+ Set the breakpoint to fire in the same thread (context) as the
+ current thread.
+
+
+ +C
+
+ Set the breakpoint to fire in the any thread. This is the de-
+ fault unless the context_events option is set.
+
+
+
+
+
[ thread ] ::fpregs
[ thread ] $x, $X, $y, $Y
@@ -3125,7 +3223,7 @@
- address ::printf [ -c lim ] [ -t format ... ] format [type] ...
+ address ::printf [ -e ] [ -c lim ] [ -t format ... ] format [type] ...
Print the data structure using the printf format command. Arguments
to the format can be:
@@ -3147,8 +3245,9 @@
If the value given is none no limit is applied.
The optional -t argument is used to specify a title which is
- printed once before any other output is produced. For possible ex-
- pansions in the format string, see the ::help printf command.
+ printed once before any other output is produced. If the -e is
+ given then write subsequent output to standard error. For possible
+ expansions in the format string, see the ::help printf command.
address ::poke[ -AnFfS ][ type ][ member ][ operator ][ -AnFfS ][ -v
@@ -3421,7 +3520,8 @@
output for the -v option.
- [signal] ::sigbp [+/-dDehstT] [-c cmd] [-n count] SIG ...
+ [signal] ::sigbp [+/-BCdDehstT] [-b function] [-c cmd] [-n count] SIG
+ ...
[signal] :t [+/-dDehstT] [-c cmd] [-n count] SIG ...
Trace delivery of the specified signals. The signals are identified
@@ -3435,6 +3535,34 @@
+ -b function
+
+ Set the breakpoint to only fire below function in the call
+ stack. This option implies -C
+
+
+ -B
+
+ Set the breakpoint to only fire in or below the current stack
+ frame. This option implies -C
+
+
+ -C
+
+ Set the breakpoint to fire in the same thread (context) as the
+ current thread.
+
+
+ +C
+
+ Set the breakpoint to fire in the any thread. This is the de-
+ fault unless the context_events option is set.
+
+
+
+
+
+
::sizeof [-s size] [-r min max] [type [member ...]]
Options are as follows:
@@ -3615,7 +3743,7 @@
Print the length of a string.
- [ syscall ] ::sysbp [ +/-dDehstT ] [ -io ] [ -c cmd ]
+ [ syscall ] ::sysbp [ +/-BCdDehstT ] [ -io ] [ -b function ] [ -c cmd ]
[ -n count ] syscall...
Trace entry to or exit from the specified system calls. The system
@@ -3631,6 +3759,34 @@
+ -b function
+
+ Set the breakpoint to only fire below function in the call
+ stack. This option implies -C
+
+
+ -B
+
+ Set the breakpoint to only fire in or below the current stack
+ frame. This option implies -C
+
+
+ -C
+
+ Set the breakpoint to fire in the same thread (context) as the
+ current thread.
+
+
+ +C
+
+ Set the breakpoint to fire in the any thread. This is the de-
+ fault unless the context_events option is set.
+
+
+
+
+
+
[addr] ::time [-abdhlsux] [-o opt,...] [|::dcmd ...]
@@ -3879,12 +4035,16 @@
See ::help typemap for example usage.
- ::typeset [ +/-t] variable-name ...
+ ::typeset [+/-C][+/-t] variable-name ...
Set attributes for named variables. If one or more variable names
are specified, they are defined and set to the value of dot. If the
-t option is present, the user-defined tag associated with each
- variable is set. If the -t option is present, the tag is cleared.
+ variable is set. If the +t option is present, the tag is cleared.
+ If the -C option is present any variables that are created will be
+ context variables, this is the default unless the typeset_global
+ option is set with ::set. If the +C is set any variables created
+ will be global. This is the default if typeset_global is not set.
If no variable names are specified, the list of variables and their
values is printed.
@@ -3909,7 +4069,7 @@
Until expr evaluates to set dot non-zero, run expr1 ....
- ::vars [-anpt]
+ ::vars [-Canpt]
Print a listing of named variables. If the -n option is present,
the output is restricted to variables that currently have non-zero
@@ -3919,7 +4079,9 @@
using the $< dcmd. This option can be used to record the variables
to a macro file and then restore these values later. If the -t op-
tion is present, only the tagged variables are printed. Variables
- can be tagged using the -t option of the ::typeset dcmd.
+ can be tagged using the -t option of the ::typeset dcmd. If the -C
+ option is given then only context variables are displayed and the
+ values for all contexts are displayed.
::version
@@ -4001,7 +4163,8 @@
While expr evaluates to set dot non-zero, run expr1 ....
- addr [ ,len ] ::wp [ +/-dDestT ] [ -rwx ] [ -c cmd ] [ -n count ]
+ addr [ ,len ] ::wp [ +/-dDestT ] [ -rwx ] [ -b function ] [ -c cmd ] [
+ -n count ]
addr [ ,len ] :a [ cmd ... ]
addr [ ,len ] :p [ cmd ... ]
addr [ ,len ] :w [ cmd ... ]
@@ -4022,6 +4185,16 @@
+ -b function
+
+ Set the breakpoint to only fire below function in the call
+ stack. This option implies -C
+
+
+
+
+
+
addr ::array [-t member_type|-s member_size|-S array_size]
@@ -4281,12 +4454,6 @@
members are displayed by default.
- editor=editor
-
- Choose the command line editor style. This can take the values
- "emacs" or "vi".
-
-
array_str_limit=limit
Sets the default limit on the number of characters that ::print
@@ -4295,6 +4462,19 @@
is displayed as a string by default.
+ context_events
+
+ Set the default for new events to be per context (thread). To
+ get per process events use the +C option when specifying the
+ event.
+
+
+ editor=editor
+
+ Choose the command line editor style. This can take the values
+ "emacs" or "vi".
+
+
follow_exec_mode=mode
Sets the debugger behavior for following an exec() and spawn()
@@ -4474,6 +4654,12 @@
+ typeset_global
+
+ Variables created with the ::typeset command will default to
+ being global.
+
+
other_fork_branch_mode=mode
When the target makes a fork(), vfork(), fork1() or spawn()
@@ -4716,10 +4902,31 @@
dump file. If vmcore.3 exists and some of the vmcore-<section>.3
files referenced by vmcore.3 do not exist, mdb loads the files and
issues warning that the virtual memory image will not be complete.
+
+ If a system crash dump with this suffix can not be found in the
+ current directory then the current directory is searched for a sub-
+ directory called suffix and then the system crash dump with this
+ suffix is opened. If no system crash dump can be found in there,
+ then dumpadm(8) is consulted to find where savecore(8) will write
+ system crash dumps and the suffix subdirectory is then searched.
+
The string of digits are not interpreted as a suffix if an actual
file of the same name is present in the current directory.
+ latest
+
+ Specifies that mdb should find the latest system crash dump. The
+ current directory is searched for a subdirectory called latest and
+ then the newest system crash dump in that directory is opened. If
+ no system crash dump can be found in there, then dumpadm(8) is con-
+ sulted to find where savecore(8) will save system crash dumps and
+ the latest subdirectory is then searched.
+
+ If there is a file called latest in the current directory then no
+ search is done.
+
+
EXIT STATUS
The following exit values are returned:
@@ -4991,4 +5198,4 @@
provides source code for an example module in the directory
/usr/demo/mdb.
-Oracle Solaris 11.4 30 November 2023 mdb(1)
+Oracle Solaris 11.4 22 February 2024 mdb(1)
diff -NurbBw 11.4.66/man1/mv.1 11.4.69/man1/mv.1
--- 11.4.66/man1/mv.1 2024-05-25 09:57:47.129916733 -0700
+++ 11.4.69/man1/mv.1 2024-05-25 09:58:10.837174665 -0700
@@ -105,13 +105,13 @@
-S When moving within a file system mv opens each regular file and
- calls fsync(2) on the file descriptor before renaming the file.
+ calls fsync(3C) on the file descriptor before renaming the file.
After the rename has been completed open the target directory and
- run fsync(2) on that file descriptor.
+ run fsync(3C) on that file descriptor.
- When moving between file systems mv calls fsync(2) on the target
+ When moving between file systems mv calls fsync(3C) on the target
file's file descriptor and opens the target directory and runs
- fsync(2) on that file descriptor before unlinking the source
+ fsync(3C) on that file descriptor before unlinking the source
file.
@@ -189,7 +189,7 @@
SEE ALSO
- cp(1), cpio(1), fsync(1), ln(1), rm(1), chmod(2), fsync(2), attrib-
+ cp(1), cpio(1), fsync(1), ln(1), rm(1), chmod(2), fsync(3C), attrib-
utes(7), environ(7), fsattr(7), privileges(7), standards(7)
NOTES
@@ -199,6 +199,10 @@
migration aid might disappear in a future release.
HISTORY
+ Support for the -S option was added in the Oracle Solaris 11.4.60 re-
+ lease.
+
+
Support for the -n and -u options was added to the mv command in Oracle
Solaris 11.4.30.
@@ -206,7 +210,7 @@
The /usr/xpg4/bin/mv command was added in the Solaris 2.5 release.
- The mv command, with support for the -f and -i options, has been
- present in all Sun and Oracle releases of Solaris.
+ The /usr/bin/mv command, with support for the -f and -i options, has
+ been present in all Sun and Oracle releases of Solaris.
-Oracle Solaris 11.4 28 Mar 2023 mv(1)
+Oracle Solaris 11.4 18 Dec 2023 mv(1)
diff -NurbBw 11.4.66/man1/passwd.1 11.4.69/man1/passwd.1
--- 11.4.66/man1/passwd.1 2024-05-25 09:57:47.183879959 -0700
+++ 11.4.69/man1/passwd.1 2024-05-25 09:58:10.889954280 -0700
@@ -515,6 +515,15 @@
11 Password information unchanged.
+ 12 Permission denied: Missing authorization.
+
+
+ 13 User unknown.
+
+
+ 14 Change abandoned. Password file/table unchanged.
+
+
FILES
/etc/default/passwd
@@ -853,4 +862,4 @@
The passwd command has been included in all releases of SunOS and So-
laris.
-Oracle Solaris 11.4 15 Mar 2023 passwd(1)
+Oracle Solaris 11.4 1 Feb 2024 passwd(1)
diff -NurbBw 11.4.66/man1/ps.1 11.4.69/man1/ps.1
--- 11.4.66/man1/ps.1 2024-05-25 09:57:47.258371047 -0700
+++ 11.4.69/man1/ps.1 2024-05-25 09:58:10.969856407 -0700
@@ -4,7 +4,7 @@
ps - report process status
SYNOPSIS
- ps [-aAcdefHjlLPwWyZ] [-C cmdlist] [-g pgrplist|grouplist]
+ ps [-aAcdefHIjlLPwWyZ] [-C cmdlist] [-g pgrplist|grouplist]
[-h|--lgroup lgrplist] [-n namelist] [-o|--format format]...
[-O format]... [-p|--pid proclist] [--pgid pgrplist]
[--ppid proclist] [-s|--sid sidlist] [-t|--tty termlist]
@@ -128,6 +128,11 @@
lgrp name with the -o or -O options.
+ -I
+
+ Use ISO 8601-1:2019 format for the stime field.
+
+
-j
Print session ID and process group ID. These columns can also be
@@ -786,7 +791,15 @@
ago, the time is printed as the hour, minute, and second. If at
least 24 hours ago, the date is printed as month and day. If speci-
fied as -o stime, printed with no blanks. If enabled via the -f op-
- tion, dates will have a space between the month and day.
+ tion, dates will have a space between the month and day. If the -I
+ is specified an ISO 8601-1:2019 format date and time is displayed
+ instead, as per sitime but with the header remaining as stime.
+
+
+ sitime
+
+ The starting date and time of the process in ISO 8601-1:2019 for-
+ mat.
dmodel
@@ -1399,6 +1412,8 @@
+--------------------------------------------------+---------+
| OPTION |RELEASE |
+--------------------------------------------------+---------+
+ | -I |11.4.69 |
+ +--------------------------------------------------+---------+
| --scale |11.4.30 |
+--------------------------------------------------+---------+
| -C, -w, --cols, --columns, --format, --Group, |11.4.27 |
@@ -1429,6 +1444,8 @@
+--------------------------------------------------+---------+
| NAME |RELEASE |
+--------------------------------------------------+---------+
+ | sitime |11.4.69 |
+ +--------------------------------------------------+---------+
| %cpu, %mem, clearance, cls, cmd, command, |11.4.27 |
| cputime, cputimes, egid, egroup, etimes, euser, | |
| flag, flags, label, ni, pgrp, policy, rssize, | |
@@ -1455,4 +1472,4 @@
+--------------------------------------------------+---------+
-Oracle Solaris 11.4 29 Nov 2022 ps(1)
+Oracle Solaris 11.4 26 Jan 2024 ps(1)
diff -NurbBw 11.4.66/man2/read.2 11.4.69/man2/read.2
--- 11.4.66/man2/read.2 2024-05-25 09:57:47.302918855 -0700
+++ 11.4.69/man2/read.2 2024-05-25 09:58:11.011390509 -0700
@@ -1,7 +1,7 @@
read(2) System Calls read(2)
NAME
- read, readv, pread - read from file
+ read, readv, pread, preadv - read from file
SYNOPSIS
#include <unistd.h>
@@ -16,6 +16,10 @@
ssize_t readv(int fildes, const struct iovec *iov, int iovcnt);
+
+ ssize_t preadv(int fildes, const struct iovec *iov, int iovcnt,
+ off_t offset);
+
DESCRIPTION
The read() function attempts to read nbyte bytes from the file associ-
ated with the open file descriptor, fildes, into the buffer pointed to
@@ -216,14 +220,16 @@
Upon successful completion, readv() marks for update the st_atime field
of the file.
- pread()
- The pread() function performs the same action as read(), except that it
- reads from a given position in the file without changing the file
- pointer. The first three arguments to pread() are the same as read()
- with the addition of a fourth argument offset for the desired position
- inside the file. pread() will read up to the maximum offset value that
- can be represented in an off_t for regular files. An attempt to perform
- a pread() on a file that is incapable of seeking results in an error.
+ pread() and preadv()
+ The pread() and preadv() functions perform the same action as read()
+ and readv(), respectively, except that it reads from a given position
+ in the file without changing the file pointer. The first three argu-
+ ments to pread() and preadv() are the same as read() and readv(), re-
+ spectively, with the addition of a fourth argument offset for the de-
+ sired position inside the file. pread() and preadv() will read up to
+ the maximum offset value that can be represented in an off_t for regu-
+ lar files. An attempt to perform a pread() or preadv() on a file that
+ is incapable of seeking results in an error.
RETURN VALUES
Upon successful completion, read() and readv() return a non-negative
@@ -231,7 +237,7 @@
functions return -1 and set errno to indicate the error.
ERRORS
- The read(), readv(), and pread() functions will fail if:
+ The read(), readv(), pread(), and preadv() functions will fail if:
EACCES The file has the av_quarantined system attribute set.
@@ -316,7 +322,7 @@
- The readv() function may fail if:
+ The readv() and preadv() functions may fail if:
EFAULT The iov argument points outside the allocated address space.
@@ -330,15 +336,15 @@
- The pread() function will fail if:
+ The pread() and preadv() functions will fail if:
ESPIPE The fildes argument is associated with a file that is inca-
pable of seeking, such as a pipe, FIFO, or socket.
USAGE
- The pread() function has a transitional interface for 64-bit file off-
- sets. See lf64(7).
+ The pread() and preadv() functions have a transitional interface for
+ 64-bit file offsets. See lf64(7).
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -363,7 +369,10 @@
The pread() function was added to Solaris in Solaris 2.0.
+ The preadv() function was added to Oracle Solaris in Solaris 11.4.69.
+
+
The read() and readv() functions have been included in all Sun and Ora-
cle releases of Solaris.
-Oracle Solaris 11.4 30 Jan 2023 read(2)
+Oracle Solaris 11.4 8 Jan 2024 read(2)
diff -NurbBw 11.4.66/man2/sigaction.2 11.4.69/man2/sigaction.2
--- 11.4.66/man2/sigaction.2 2024-05-25 09:57:47.338061799 -0700
+++ 11.4.69/man2/sigaction.2 2024-05-25 09:58:11.054732457 -0700
@@ -86,11 +86,12 @@
ioctl(2), wait(3C), waitid(2), and the following func-
tions on slow devices like terminals: getmsg() and
getpmsg() (see getmsg(2)); putmsg() and putpmsg() (see
- putmsg(2)); pread(), read(), and readv() (see read(2));
- pwrite(), write(), and writev() (see write(2)); recv(),
- recvfrom(), and recvmsg() (see recv(3C)); and send(),
- sendto(), and sendmsg() (see send(3C)). Otherwise, the
- function returns an EINTR error.
+ putmsg(2)); pread(), preadv(), read(), and readv() (see
+ read(2)); pwrite(), pwritev(), write(), and writev()
+ (see write(2)); recv(), recvfrom(), and recvmsg() (see
+ recv(3C)); and send(), sendto(), and sendmsg() (see
+ send(3C)). Otherwise, the function returns an EINTR er-
+ ror.
SA_SIGINFO If cleared and the signal is caught, sig is passed as
@@ -168,4 +169,4 @@
signal. It is not recommended that ucp be used by the handler to re-
store the context from before the signal delivery.
-Oracle Solaris 11.4 9 Jul 2018 sigaction(2)
+Oracle Solaris 11.4 8 Jan 2024 sigaction(2)
diff -NurbBw 11.4.66/man2/write.2 11.4.69/man2/write.2
--- 11.4.66/man2/write.2 2024-05-25 09:57:47.378056296 -0700
+++ 11.4.69/man2/write.2 2024-05-25 09:58:11.102223931 -0700
@@ -1,7 +1,7 @@
write(2) System Calls write(2)
NAME
- write, pwrite, writev - write on a file
+ write, pwrite, writev, pwritev - write on a file
SYNOPSIS
#include <unistd.h>
@@ -17,6 +17,10 @@
ssize_t writev(int fildes, const struct iovec *iov, int iovcnt);
+
+ ssize_t pwritev(int fildes, const struct iovec *iov, int iovcnt,
+ off_t offset);
+
DESCRIPTION
The write() function attempts to write nbyte bytes from the buffer
pointed to by buf, to the file associated with the open file descrip-
@@ -211,13 +215,6 @@
value of errno does not reflect the result of write() or writev() but
reflects the prior error.
- pwrite()
- The pwrite() function is equivalent to write(), except that the write
- occurs at a user specified offset, without regard for O_APPEND, and the
- file pointer is not changed. The first three arguments to pwrite() are
- the same as write(), with the addition of a fourth argument offset for
- the desired position inside the file.
-
writev()
The writev() function performs the same action as write(), but gathers
the output data from the iovcnt buffers specified by the members of the
@@ -246,6 +243,14 @@
If the sum of the iov_len values is greater than SSIZE_MAX, the opera-
tion fails and no data is transferred.
+ pwrite() and pwritev()
+ The pwrite() and pwritev() functions are equivalent to write() and
+ writev(), respectively, except that the write occurs at a user speci-
+ fied offset, without regard for O_APPEND, and the file pointer is not
+ changed. The first three arguments to pwrite() and pwritev() are the
+ same as write() and writev(), respectively, with the addition of a
+ fourth argument offset for the desired position inside the file.
+
RETURN VALUES
Upon successful completion, write() returns the number of bytes actu-
ally written to the file associated with fildes. This number is never
@@ -263,8 +268,13 @@
ally written. Otherwise, it returns -1, the file pointer remains un-
changed, and errno is set to indicate an error.
+
+ Upon successful completion, pwritev() returns the number of bytes actu-
+ ally written. Otherwise, it returns -1, and errno is set to indicate an
+ error.
+
ERRORS
- The write(), pwrite(), and writev() functions will fail if:
+ The write(), pwrite(), writev(), and pwritev() functions will fail if:
EADI The buffer pointed to by buf or a buffer specified in the
iov array is enabled for ADI, and an ADI version mismatch is
@@ -364,7 +374,7 @@
- The pwrite() function fails if:
+ The pwrite() and pwritev() functions fail if:
ESPIPE The fildes argument is associated with a file that is inca-
pable of seeking, such as a pipe, FIFO, or socket.
@@ -390,7 +400,7 @@
cluded in the error message.
- The writev() function may fail if:
+ The writev() and pwritev() functions may fail if:
EINVAL The iovcnt argument is less than or equal to 0 or greater
than {IOV_MAX}; one of the iov_len values in the iov array is
@@ -399,8 +409,8 @@
USAGE
- The pwrite() function has a transitional interface for 64-bit file off-
- sets. See lf64(7).
+ The pwrite() and pwrite() functions have a transitional interface for
+ 64-bit file offsets. See lf64(7).
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -425,7 +435,10 @@
The pwrite() function was added to Solaris in Solaris 2.0.
+ The pwritev() function was added to Oracle Solaris in Solaris 11.4.69.
+
+
The write() and writev() functions have been included in all Sun and
Oracle releases of Solaris.
-Oracle Solaris 11.4 30 Jan 2023 write(2)
+Oracle Solaris 11.4 8 Jan 2024 write(2)
diff -NurbBw 11.4.66/man3/intro.3 11.4.69/man3/intro.3
--- 11.4.66/man3/intro.3 2024-05-25 09:57:47.428235594 -0700
+++ 11.4.69/man3/intro.3 2024-05-25 09:58:11.156133699 -0700
@@ -167,13 +167,6 @@
this library. See libdlpi(3LIB).
- (3DNS_SD)
-
- These functions constitute the DNS service discovery library,
- libdns_sd. Specify -ldns_sd on the cc command line to link with
- this library. See libdns_sd(3LIB).
-
-
(3GSS)
These functions constitute the generic security services library.
@@ -826,4 +819,4 @@
not be expected to test the length of an argument list given to a rou-
tine to determine if it was greater than {ARG_MAX}.
-Oracle Solaris 11.4 11 May 2021 Intro(3)
+Oracle Solaris 11.4 29 Nov 2023 Intro(3)
diff -NurbBw 11.4.66/man3c/mkstemp.3c 11.4.69/man3c/mkstemp.3c
--- 11.4.66/man3c/mkstemp.3c 2024-05-25 09:57:47.461760702 -0700
+++ 11.4.69/man3c/mkstemp.3c 2024-05-25 09:58:11.197386291 -0700
@@ -26,11 +26,12 @@
by template by a unique file name, and returns a file descriptor for
the file open for reading and writing. The function thus prevents any
possible race condition between testing whether the file exists and
- opening it for use. The string in template should look like a file name
- with six trailing 'X's; mkstemp() replaces each 'X' with a character
- from the portable file name character set. The characters are chosen
- such that the resulting name does not duplicate the name of an existing
- file.
+ opening it for use. The file is created with mode 0600, allowing read
+ and write for only the owner. The string in template should look like a
+ file name with six trailing 'X's; mkstemp() replaces each 'X' with a
+ character from the portable file name character set. The characters are
+ chosen such that the resulting name does not duplicate the name of an
+ existing file.
The mkstemps() function behaves the same as mkstemp(), except it per-
@@ -127,4 +128,4 @@
The mkostemp() and mkostemps() functions were defined in GNU libc 2.11,
and were added to Oracle Solaris in the Oracle Solaris 11.4.15 release.
-Oracle Solaris 11.4 5 Aug 2019 mkstemp(3C)
+Oracle Solaris 11.4 11 Mar 2024 mkstemp(3C)
diff -NurbBw 11.4.66/man3c/reflink.3c 11.4.69/man3c/reflink.3c
--- 11.4.66/man3c/reflink.3c 2024-05-25 09:57:47.496658357 -0700
+++ 11.4.69/man3c/reflink.3c 2024-05-25 09:58:11.245144134 -0700
@@ -35,8 +35,11 @@
If the preserve parameter is non-zero, as much of the uid, gid, mode,
- atime, mtime, and system attributes are copied as are allowed by the
- calling process's privileges. See privileges(7) for more information.
+ atime, mtime, and extended system attributes are copied as are allowed
+ by the calling process's privileges. See privileges(7) for more infor-
+ mation. Further, any extended attributes will also be reflink()ed with
+ the preserve parameter set. Retention time is excluded from the ex-
+ tended system attributes.
RETURN VALUES
Upon successful completion, 0 is returned. Otherwise, -1 is returned,
@@ -136,4 +139,4 @@
SEE ALSO
attributes(7), privileges(7), standards(7)
-Oracle Solaris 11.4 24 Aug 2023 reflink(3C)
+Oracle Solaris 11.4 1 Mar 2024 reflink(3C)
diff -NurbBw 11.4.66/man3c/sysconf.3c 11.4.69/man3c/sysconf.3c
--- 11.4.66/man3c/sysconf.3c 2024-05-25 09:57:47.541667332 -0700
+++ 11.4.69/man3c/sysconf.3c 2024-05-25 09:58:11.290343654 -0700
@@ -128,8 +128,8 @@
_SC_IOV_MAX IOV_MAX Max number of iovec
structures available
to one process for
- use with readv()
- and writev()
+ use with readv(), preadv(),
+ writev(), and pwritev()
_SC_JOB_CONTROL _POSIX_JOB_CONTROL Job control
supported?
_SC_LINE_MAX LINE_MAX Max length of input
@@ -544,4 +544,4 @@
not support ADI, or if the implementation does not require metadata
when writing pages to the backing store.
-Oracle Solaris 11.4 11 May 2021 sysconf(3C)
+Oracle Solaris 11.4 8 Jan 2024 sysconf(3C)
diff -NurbBw 11.4.66/man3dns_sd/DNSServiceBrowse.3dns_sd 11.4.69/man3dns_sd/DNSServiceBrowse.3dns_sd
--- 11.4.66/man3dns_sd/DNSServiceBrowse.3dns_sd 2024-05-25 09:57:47.575880034 -0700
+++ 11.4.69/man3dns_sd/DNSServiceBrowse.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,90 +0,0 @@
-DNS...wse(3DNS_SD) DNS Service Discovery Library Functions DNS...wse(3DNS_SD)
-
-NAME
- DNSServiceBrowse - browse service instances with DNS
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- DNSServiceErrorType DNSServiceBrowse(DNSServiceRef *sdRef,
- DNSServiceFlags flags, uint32_t interfaceIndex,
- const char *regtype, const char *domain,
- DNSServiceServiceBrowseReply callBack, void *context);
-
-
- typedef void(*DNSServiceBrowseReply)(DNSServiceRef sdRef,
- DNSServiceFlags flags, uint32_t interfaceIndex,
- DNSServiceErrorType errorCode, const char *serviceName,
- const char *regtype, const char *replyDomain,
- void *context);
-
-DESCRIPTION
- The DNSServiceBrowse() function is used to browse for service instances
- of a particular service and protocol type. The sdRef argument points to
- an uninitialized DNSServiceRef. If the call to DNSServiceBrowse suc-
- ceeds sdRef is initialized. The flags argument to DNSServiceBrowse() is
- currently unused and reserved for future use. A nonzero value to inter-
- faceIndex indicates DNSServiceBrowse() should do a browse on all inter-
- faces. Most applications will use an interfaceIndex value of 0 to per-
- form a browse on all interfaces. See the section "Constants for speci-
- fying an interface index" in <dns_sd.h> for more details.
-
-
- The callback function is invoked for every service instance found
- matching the service type and protocol. The callback argument points to
- a function of type DNSServiceBrowseReply listed above. The DNSService-
- Browse() call returns browse results asynchronously. The service browse
- call can be terminated by applications with a call to DNSSer-
- viceRefDeallocate().
-
-
- The regtype parameter is used to specify the service type and protocol
- (e.g. _ftp._tcp). The protocol type must be TCP or UDP. The domain ar-
- gument to DNSServiceBrowse() specifies the domain on which to browse
- for services. Most applications will not specify a domain and will per-
- form a browse on the default domain(s). The context argument can be
- NULL and points to a value passed to the callback function.
-
-
- The sdRef argument passed to the callback function is initialized by
- DNSServiceBrowse() call. The possible values passed to flags in the
- callback function are: kDNSServiceFlagsMoreComing and kDNSService-
- FlagsAdd. The kDNSServiceFlagsMoreComing value indicates to a callback
- that at least one more result is immediately available. The kDNSSer-
- viceFlagsAdd value indicates that a service instance was found. The er-
- rorCode argument will be kDNSServiceErr_NoError on success. Otherwise,
- failure is indicated. The discovered service name is returned to the
- callback via the serviceName argument. The regtype argument in the
- callback holds the service type of the found service instance. The dis-
- covered service type can be different from the requested service type
- in the browse request when the discovered service type has subtypes.
- The domain argument to the callback holds the domain name of the dis-
- covered service instance. The service type and the domain name must be
- stored and passed along with the service name to resolve a service in-
- stance using DNSServiceResolve().
-
-RETURN VALUES
- The DNSServiceBrowse function returns kDNSServiceErr_NoError on suc-
- cess. Otherwise, an error code defined in <dns_sd.h> is returned to in-
- dicate an error has occurred. When an error is returned by DNSService-
- Browse, the callback function is not invoked and the DNSServiceRef ar-
- gument is not initialized.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- DNSServiceRefDeallocate(3DNS_SD), DNSServiceResolve(3DNS_SD), attrib-
- utes(7)
-
-Oracle Solaris 11.4 20 Aug 2007 DNS...wse(3DNS_SD)
diff -NurbBw 11.4.66/man3dns_sd/DNSServiceConstructFullName.3dns_sd 11.4.69/man3dns_sd/DNSServiceConstructFullName.3dns_sd
--- 11.4.66/man3dns_sd/DNSServiceConstructFullName.3dns_sd 2024-05-25 09:57:47.609199940 -0700
+++ 11.4.69/man3dns_sd/DNSServiceConstructFullName.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,33 +0,0 @@
-DNS...Name(3DNS_SD) DNS Service Discovery Library FunctionsDNS...Name(3DNS_SD)
-
-NAME
- DNSServiceConstructFullName - construct full name
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- int DNSServiceConstructFullName (char *fullname,
- const char *service, const char *regtype, const char *domain);
-
-DESCRIPTION
- The DNSServiceConstructFullName() concatenates a three-part domain name
- that consists of a service name, service type, and domain name into a
- fully escaped full domain name.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- attributes(7)
-
-Oracle Solaris 11.4 20 Aug 2007 DNS...Name(3DNS_SD)
diff -NurbBw 11.4.66/man3dns_sd/DNSServiceCreateConnection.3dns_sd 11.4.69/man3dns_sd/DNSServiceCreateConnection.3dns_sd
--- 11.4.66/man3dns_sd/DNSServiceCreateConnection.3dns_sd 2024-05-25 09:57:47.642771534 -0700
+++ 11.4.69/man3dns_sd/DNSServiceCreateConnection.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,109 +0,0 @@
-DNS...ion(3DNS_SD) DNS Service Discovery Library Functions DNS...ion(3DNS_SD)
-
-NAME
- DNSServiceCreateConnection, DNSServiceRegisterRecord, DNSServiceAd-
- dRecord, DNSServiceUpdateRecord, DNSServiceRemoveRecord - registering
- multiple records
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- DNSServiceErrorType DNSServiceCreateConnection(DNSServiceRef *sdRef);
-
-
- DNSServiceErrorType DNSServiceRegisterRecord(DNSServiceRef sdRef,
- DNSRecordRef *RecordRef, DNSServiceFlags flags,
- uint32_t interfaceIndex, const char *fullname,
- uint16_t rrtype, uint16_t rrclass, uint16_t rdlen,
- const void *rdata, uint32_t ttl,
- DNSServiceServiceRegisterRecordReply callBack,
- void *context);
-
-
- typedef void(*DNSServiceRegisterRecordReply)(DNSServiceRef sdRef,
- DNSServiceRecordRef RecordRef, DNSServiceFlags flags,
- DNSServiceErrorType errorCode, void *context);
-
-
- DNSServiceErrorType DNSServiceAddRecord(DNSServiceRef sdRef,
- DNSRecordRef *RecordRef, DNSServiceFlags flags,
- uint16_t rrtype, uint16_t rdlen, const void *rdata,
- uint32_t ttl);
-
-
- DNSServiceErrorType DNSServiceUpdateRecord(DNSServiceRef sdRef,
- DNSRecordRef RecordRef, DNSServiceFlags flags,
- uint16_t rdlen, const void *rdata,
- uint32_t ttl);
-
-
- DNSServiceErrorType DNSServiceRemoveRecord(DNSServiceRef sdRef,
- DNSRecordRef RecordRef, DNSServiceFlags flags);
-
-DESCRIPTION
- The DNSServiceCreateConnection() function allows the creation of a con-
- nection to the mDNS daemon in order to register multiple individual
- records.
-
-
- The DNSServiceRegisterRecord() function uses the connection created by
- DNSServiceCreateConnection() to register a record. Name conflicts that
- occur from this function should be handled by the client in the call-
- back.
-
-
- The DNSServiceAddRecord() call adds a DNS record to a registered ser-
- vice. The name of the record is the same as registered service name.
- The RecordRef argument to DNSServiceAddRecord() points to an uninitial-
- ized DNSRecordRef. After successful completion of DNSServiceAd-
- dRecord(), the DNS record can be updated or deregistered by passing the
- DNSRecordRef initialized by DNSServiceAddRecord() to DNSServiceUp-
- dateRecord() or to DNSServiceRemoveRecord().
-
-
- The DNSServiceUpdateRecords() call updates the DNS record of the regis-
- tered service. The DNS record must be the primary resource record reg-
- istered using DNSServiceRegister() or a record added to a registered
- service using DNSServiceAddRecord() or an individual record added via
- DNSServiceRegisterRecord().
-
-
- The DNSServiceRemoveRecord() call removes a record that was added using
- DNSServiceAddRecord() or DNSServiceRegisterRecord().
-
-
- The sdRef argument points to DNSServiceRef initialized from a call to
- DNSServiceRegister(). If the sdRef argument is passed to DNSSer-
- viceRefDeallocate() and the service is deregistered DNS records added
- via DNSServiceAddRecord() are invalidated and cannot be further used.
- The flags argument is currently ignored and reserved for future use.
- The rrtype parameter value indicates the type of the DNS record. Suit-
- able values for the rrtype parameter are defined in <dns_sd.h>:
- kDNSServiceType_TXT, for example. The rdata argument points to the raw
- rdata to be contained in the resource record. The ttl value indicates
- the time to live of the resource record in seconds. A ttl value of 0
- should be passed to use a default value.
-
-RETURN VALUES
- The DNSServiceCreateConnection function returns kDNSServiceErr_NoError
- on success. Otherwise, an error code defined in <dns_sd.h> is returned
- to indicate the specific failure that occurred.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- DNSServiceRefDeallocate(3DNS_SD), DNSServiceRegister(3DNS_SD), attrib-
- utes(7)
-
-Oracle Solaris 11.4 20 Aug 2007 DNS...ion(3DNS_SD)
diff -NurbBw 11.4.66/man3dns_sd/DNSServiceEnumerateDomains.3dns_sd 11.4.69/man3dns_sd/DNSServiceEnumerateDomains.3dns_sd
--- 11.4.66/man3dns_sd/DNSServiceEnumerateDomains.3dns_sd 2024-05-25 09:57:47.676732685 -0700
+++ 11.4.69/man3dns_sd/DNSServiceEnumerateDomains.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,80 +0,0 @@
-DNS...ins(3DNS_SD) DNS Service Discovery Library Functions DNS...ins(3DNS_SD)
-
-NAME
- DNSServiceEnumerateDomains - enumerate recommended domains
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- DNSServiceErrorType DNSServiceEnumerateDomains(DNSServiceRef *sdRef,
- DNSServiceFlags flags, uint32_t interfaceIndex,
- DNSServiceDomainEnumReply callBack, void *context);
-
-
- typedef void(*DNSServiceDomainEnumReply)(DNSServiceRef sdRef,
- DNSServiceFlags flags, uint32_t interfaceIndex,
- DNSServiceErrorType errorCode, const char *replyDomain,
- void *context);
-
-DESCRIPTION
- The DNSServiceEnumerateDomains() function allows applications to deter-
- mine recommended browsing and registration domains for performing ser-
- vice discovery DNS queries. The callback argument points to a function
- to be called to return results or if the asynchronous call to DNSSer-
- viceEnumerateDomains() fails. The callback function should point to a
- function of type DNSServiceDomainEnumReply listed above.
-
-
- A pointer to an uninitialized DNSServiceRef, sdRef must be passed to
- DNSServiceEnumerateDomains(). If the call succeeds, sdRef is initial-
- ized and kDNSServiceErr_NoError is returned. The enumeration call runs
- indefinitely until the client terminates the call. The enumeration call
- must be terminated by passing the DNSServiceRef initialized by the enu-
- meration call to DNSServiceRefDeallocate() when no more domains are to
- be found.
-
-
- The value of flags is constructed by a bitwise-inclusive-OR of the
- flags used in DNSService functions and defined in <dns_sd.h>. Possible
- values for flags to the DNSServiceEnumerateDomains() call are: kDNSSer-
- viceFlagsBrowseDomains and kDNSServiceFlagsRegistrationDomains. The
- kDNSServiceFlagsBrowseDomains value is passed to enumerate domains rec-
- ommended for browsing. The kDNSServiceFlagsRegistrationDomains value is
- passed to enumerate domains recommended for registration. Possible val-
- ues of flags returned in the callback function are: kDNSService-
- FlagsMoreComing, kDNSServiceFlagsAdd, and kDNSServiceFlagsDefault.
-
-
- The interfaceIndex parameter to the enumeration call specifies the in-
- terface index searched for domains. Most applications pass 0 to enumer-
- ate domains on all interfaces. See the section "Constants for specify-
- ing an interface index" in <dns_sd.h> for more details. The context pa-
- rameter can be NULL and is passed to the enumeration callback function.
- The interfaceIndex value passed to the callback specifies the interface
- on which the domain exists.
-
-RETURN VALUES
- The DNSServiceEnumerateDomains() function returns kDNSServiceErr_NoEr-
- ror on success. Otherwise, the function returns an error code defined
- in <dns_sd.h>. The callback is not invoked on error and the DNSSer-
- viceRef that is passed is not initialized. Upon a successful call to
- DNSServiceEnumerateDomains(), subsequent asynchronous errors are deliv-
- ered to the callback.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- DNSServiceRefDeallocate(3DNS_SD), attributes(7)
-
-Oracle Solaris 11.4 27 Nov 2017 DNS...ins(3DNS_SD)
diff -NurbBw 11.4.66/man3dns_sd/DNSServiceProcessResult.3dns_sd 11.4.69/man3dns_sd/DNSServiceProcessResult.3dns_sd
--- 11.4.66/man3dns_sd/DNSServiceProcessResult.3dns_sd 2024-05-25 09:57:47.711852804 -0700
+++ 11.4.69/man3dns_sd/DNSServiceProcessResult.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,42 +0,0 @@
-DNS...sult(3DNS_SD) DNS Service Discovery Library FunctionsDNS...sult(3DNS_SD)
-
-NAME
- DNSServiceProcessResult - process results and invoke callback
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- DNSServiceErrorType DNSServiceProcessResult (DNSServiceRef sdRef);
-
-DESCRIPTION
- The DNSServiceProcessResult() call reads the returned results from the
- mDNS daemon and invokes the specified application callback. The sdRef
- points to a DNSServiceRef initialized by any of the DNSService calls
- that take a callback parameter. The DNSServiceProcessResult() call
- blocks until data is received from the mDNS daemon. The application is
- responsible for ensuring that DNSServiceProcessResult() is called when-
- ever there is a reply from the daemon. The daemon may terminate its
- connection with a client that does not process the daemon's responses.
-
-RETURN VALUES
- The DNSServiceProcessResult() call returns kDNSServiceErr_NoError on
- success. Otherwise, an error code defined in <dns_sd.h> is returned to
- indicate the specific failure that has occurred.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- DNSServiceBrowse(3DNS_SD), DNSServiceRegister(3DNS_SD), attributes(7)
-
-Oracle Solaris 11.4 20 Aug 2007 DNS...sult(3DNS_SD)
diff -NurbBw 11.4.66/man3dns_sd/DNSServiceQueryRecord.3dns_sd 11.4.69/man3dns_sd/DNSServiceQueryRecord.3dns_sd
--- 11.4.66/man3dns_sd/DNSServiceQueryRecord.3dns_sd 2024-05-25 09:57:47.744524190 -0700
+++ 11.4.69/man3dns_sd/DNSServiceQueryRecord.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,91 +0,0 @@
-DNS...cord(3DNS_SD) DNS Service Discovery Library FunctionsDNS...cord(3DNS_SD)
-
-NAME
- DNSServiceQueryRecord - query records from DNS
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- DNSServiceErrorType DNSServiceQueryRecord(DNSServiceRef *sdRef,
- DNSServiceFlags flags, uint32_t interfaceIndex, const char *fullname,
- uint16_t rrtype, uint16_t rrclass,
- DNSServiceServiceQueryRecordReply callBack, void *context);
-
-
- typedef void(*DNSServiceQueryRecordReply)(DNSServiceRef DNSServiceRef,
- DNSServiceFlags flags, uint32_t interfaceIndex,
- DNSServiceErrorType errorCode, const char *fullname,
- uint16_t rrtype, uint16_t rrclass, uint16_t rdlen,
- const void *rdata, uint32_t ttl, void *context);
-
-DESCRIPTION
- The DNSServiceQueryRecord() function is used to query the daemon for
- any DNS resource record type. The callback argument to DNSService-
- QueryRecord() points to a function of type DNSServiceQueryRecordReply()
- listed above. The sdRef parameter in DNSServiceQueryRecord() points to
- an uninitialized DNSServiceRef. The DNSServiceQueryRecord() function
- returns kDNSServiceErr_NoError and initializes sdRef on success. The
- query runs indefinitely until the client terminates by passing the ini-
- tialized sdRef from the query call to DNSServiceRefDeallocate().
-
-
- The flag kDNSServiceFlagsLongLivedQuery should be passed in the flags
- argument of DNSServiceQueryRecord() to create a "long-lived" unicast
- query in a non-local domain. This flag has no effect on link local mul-
- ticast queries. Without this flag, unicast queries will be one-shot and
- only the results that are available at the time of the query will be
- returned. With long-lived queries, add or remove events that are avail-
- able after the first call generate callbacks. The interfaceIndex argu-
- ment specifies the interface on which to issue the query. Most applica-
- tions will pass a 0 as the interfaceIndex to make the query on all in-
- terfaces. See the section "Constants for specifying an interface index"
- in <dns_sd.h>. The fullname argument indicates the full domain name of
- the resource record to be queried. The rrtype argument indicates the
- resource record type: kDNSServiceType_PTR, for example. The rrclass ar-
- gument holds the class of the resource record to be queried (kDNSSer-
- viceClass_IN). The context argument can be NULL and points to a value
- passed to the callback function.
-
-
- The sdRef argument passed to the callback function is initialized by
- the call to DNSServiceQueryRecord(). Possible values for the flags pa-
- rameter to the callback function are kDNSServiceFlagsMoreComing and
- kDNSServiceFlagsAdd. The kDNSServiceFlagsMoreComing value is set to in-
- dicate that additional results are immediately available. The kDNSSer-
- viceFlagsAdd value indicates that the results returned to the callback
- function are for a valid DNS record. If kDNSServiceFlagsAdd is not set,
- the results returned are for a delete event. The errorCode passed to
- the callback is kDNSServiceErr_NoError on success. Otherwise, failure
- is indicated and other parameter values are undefined. The fullname pa-
- rameter indicates the full domain name of the resource record . The
- rrtype indicates the resource record type. The rrclass indicates the
- class of the DNS resource record. The rdlen parameter indicates the
- length of the resource record rdata in bytes. The rdata parameter
- points to raw rdata of the resource record. The ttl parameter indicates
- the time to live of the resource record in seconds. The context parame-
- ter points to the value passed by the application in the context argu-
- ment to the DNSServiceQueryRecord() call.
-
-RETURN VALUES
- The DNSServiceQueryRecord function returns kDNSServiceErr_NoError on
- success. Otherwise, an error code defined in <dns_sd.h> is returned to
- indicate the specific failure that occurred.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- DNSServiceBrowse(3DNS_SD), DNSServiceRegister(3DNS_SD), DNSServiceRe-
- solve(3DNS_SD), attributes(7)
-
-Oracle Solaris 11.4 20 Aug 2007 DNS...cord(3DNS_SD)
diff -NurbBw 11.4.66/man3dns_sd/DNSServiceReconfirmRecord.3dns_sd 11.4.69/man3dns_sd/DNSServiceReconfirmRecord.3dns_sd
--- 11.4.66/man3dns_sd/DNSServiceReconfirmRecord.3dns_sd 2024-05-25 09:57:47.779413626 -0700
+++ 11.4.69/man3dns_sd/DNSServiceReconfirmRecord.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,41 +0,0 @@
-DNS...cord(3DNS_SD) DNS Service Discovery Library FunctionsDNS...cord(3DNS_SD)
-
-NAME
- DNSServiceReconfirmRecord - verify DNS record
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- void DNSServiceRefSockFD (DNSServiceFlags flags, uint32_t interfaceIndex,
- const char *fullname, uint16_t rrtype, uint16_t rrclass,
- uint16_t rrlen const void *rdata);
-
-DESCRIPTION
- The DNSServiceReconfirmRecord() function allows callers to verify
- whether a DNS record is valid. If an invalid record is found in the
- cache, the daemon flushes the record from the cache and from the cache
- of other daemons on the network.
-
-RETURN VALUES
- The DNSServiceReconfirmRecord() function returns kDNSServiceErr_NoError
- on success. Otherwise, an error code defined in <dns_sd.h> is returned
- to indicate the specific failure that occurred.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- DNSServiceBrowse(3DNS_SD), DNSServiceQueryRecord(3DNS_SD), DNSSer-
- viceRegister(3DNS_SD), DNSServiceResolve(3DNS_SD), attributes(7)
-
-Oracle Solaris 11.4 20 Aug 2007 DNS...cord(3DNS_SD)
diff -NurbBw 11.4.66/man3dns_sd/DNSServiceRefDeallocate.3dns_sd 11.4.69/man3dns_sd/DNSServiceRefDeallocate.3dns_sd
--- 11.4.66/man3dns_sd/DNSServiceRefDeallocate.3dns_sd 2024-05-25 09:57:47.811638187 -0700
+++ 11.4.69/man3dns_sd/DNSServiceRefDeallocate.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,33 +0,0 @@
-DNS...cate(3DNS_SD) DNS Service Discovery Library FunctionsDNS...cate(3DNS_SD)
-
-NAME
- DNSServiceRefDeallocate - close connection
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- void DNSServiceRefDeallocate (DNSServiceRef sdRef);
-
-DESCRIPTION
- The DNSServiceRefDeallocate() call terminates connection to the mDNS
- daemon. Any services and resource records registered with the DNSSer-
- viceRef are de-registered. Any browse or resolve queries initiated us-
- ing the DNSServiceRef are also terminated.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- DNSServiceBrowse(3DNS_SD), DNSServiceRegister(3DNS_SD), attributes(7)
-
-Oracle Solaris 11.4 20 Aug 2007 DNS...cate(3DNS_SD)
diff -NurbBw 11.4.66/man3dns_sd/DNSServiceRefSockFD.3dns_sd 11.4.69/man3dns_sd/DNSServiceRefSockFD.3dns_sd
--- 11.4.66/man3dns_sd/DNSServiceRefSockFD.3dns_sd 2024-05-25 09:57:47.845196784 -0700
+++ 11.4.69/man3dns_sd/DNSServiceRefSockFD.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,41 +0,0 @@
-DNS...ckFD(3DNS_SD) DNS Service Discovery Library FunctionsDNS...ckFD(3DNS_SD)
-
-NAME
- DNSServiceRefSockFD - access underlying UNIX domain socket descriptor
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- DNSServiceRefSockFD(DNSServiceRef *sdRef);
-
-DESCRIPTION
- Access the underlying UNIXTM domain socket from the initialized DNSSer-
- viceRef returned from DNS Service calls. Applications should only ac-
- cess the underlying UNIX domain socket to poll for results from the
- mDNS daemon. Applications should not directly read or write to the
- socket. When results are available, applications should call DNSServi-
- ceProcessResult(). The application is responsible for processing the
- data on the socket in a timely fashion. The daemon can terminate its
- connection with a client that does not clear its socket buffer.
-
-RETURN VALUES
- The underlying UNIX domain socket descriptor of the DNSServiceRef or -1
- is returned in case of error.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- DNSServiceBrowse(3DNS_SD), DNSServiceRegister(3DNS_SD), attributes(7)
-
-Oracle Solaris 11.4 20 Aug 2007 DNS...ckFD(3DNS_SD)
diff -NurbBw 11.4.66/man3dns_sd/DNSServiceRegister.3dns_sd 11.4.69/man3dns_sd/DNSServiceRegister.3dns_sd
--- 11.4.66/man3dns_sd/DNSServiceRegister.3dns_sd 2024-05-25 09:57:47.884178442 -0700
+++ 11.4.69/man3dns_sd/DNSServiceRegister.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,110 +0,0 @@
-DNS...ter(3DNS_SD) DNS Service Discovery Library Functions DNS...ter(3DNS_SD)
-
-NAME
- DNSServiceRegister - register service with DNS
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- DNSServiceErrorType DNSServiceRegister(DNSServiceRef *sdRef,
- DNSServiceFlags flags, uint32_t interfaceIndex,
- const char *name, const char *regtype,
- const char *domain, const char *host,
- uint16_t port, uint16_t *txtLen, const void *txtRecord
- DNSServiceServiceRegisterReply callBack
- void *context);
-
-
- typedef void(*DNSServiceRegisterReply)(DNSServiceRef sdRef,
- DNSServiceFlags flags, DNSServiceErrorType errorCode,
- const char *name, const char *regtype,
- const char *domain, void *context);
-
-DESCRIPTION
- The DNSServiceRegister function is used by clients to advertise a ser-
- vice that uses DNS. The service is registered with multicast DNS if the
- domain name is .local or the interface requested is local only. Other-
- wise, the service registration is attempted with the unicast DNS
- server. The callback argument should point to a function of type
- DNSServiceRegisterReply listed above.
-
-
- The sdRef parameter points to an uninitialized DNSServiceRef instance.
- If the DNSServiceRegister() call succeeds, sdRef is initialized and
- kDNSServiceErr_NoError is returned. The service registration remains
- active until the client terminates the registration by passing the ini-
- tialized sdRef to DNSServiceRefDeallocate(). The interfaceIndex when
- non-zero specifies the interface on which the service should be regis-
- tered. Most applications pass 0 to register the service on all inter-
- faces. See the section "Constants for specifying an interface index" in
- <dns_sd.h> for more details. The flags parameter determines the renam-
- ing behavior on a service name conflict. Most applications pass 0 to
- allow auto-rename of the service name in case of a name conflict. Ap-
- plications can pass the flag kDNSServiceFlagsNoAutoRename defined in
- <dns_sd.h> to disable auto-rename.
-
-
- The regtype indicates the service type followed by the protocol, sepa-
- rated by a dot, for example "_ftp._tcp.". The service type must be an
- underscore that is followed by 1 to 14 characters that can be letters,
- digits, or hyphens. The transport protocol must be _tcp or _udp. New
- service types should be registered at https://www.iana.org/form/ports-
- services. The domain parameter specifies the domain on which a service
- is advertised. Most applications leave the domain parameter NULL to
- register the service in default domains. The host parameter specifies
- the SRV target host name. Most applications do not specify the host pa-
- rameter value. Instead, the default host name of the machine is used.
- The port value on which the service accepts connections must be passed
- in network byte order. A value of 0 for a port is passed to register
- placeholder services. Placeholder services are not found when browsing,
- but other clients cannot register with the same name as the placeholder
- service.
-
-
- The txtLen parameter specifies the length of the passed txtRecord in
- bytes. The value must be zero if the txtRecord passed is NULL. The tx-
- tRecord points to the TXT record rdata. A non-NULL txtRecord must be a
- properly formatted DNSTXT record. For more details see the DNSSer-
- viceRegister call defined in <dns_sd.h>. The callback argument points
- to a function to be called when registration completes or when the call
- asynchronously fails. The client can pass NULL for the callback and not
- be notified of the registration results or asynchronous errors. The
- client may not pass the NoAutoRename flag if the callback is NULL. The
- client can unregister the service at any time via DNSServiceRefDeallo-
- cate().
-
-
- The callback function argument sdRef is initialized by DNSServiceRegis-
- ter(). The flags argument in the callback function is currently unused
- and reserved for future use. The error code returned to the callback is
- kDNSServiceErr_NoError on success. Otherwise, an error code defined in
- <dns_sd.h> is returned to indicate an error condition such as a name
- conflict in kDNSServiceFlagsNoAutoRename mode. The name argument holds
- the registered service name and the regtype argument is the registered
- service type passed to DNSServiceRegister(). The domain argument re-
- turned in the callback indicates the domain on which the service was
- registered.
-
-RETURN VALUES
- The DNSServiceRegister function returns kDNSServiceErr_NoError on suc-
- cess. Otherwise, an error code defined in <dns_sd.h> is returned. Upon
- registration, any subsequent asynchronous errors are delivered to the
- callback.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- DNSServiceRefDeallocate(3DNS_SD), attributes(7)
-
-Oracle Solaris 11.4 20 Aug 2007 DNS...ter(3DNS_SD)
diff -NurbBw 11.4.66/man3dns_sd/DNSServiceResolve.3dns_sd 11.4.69/man3dns_sd/DNSServiceResolve.3dns_sd
--- 11.4.66/man3dns_sd/DNSServiceResolve.3dns_sd 2024-05-25 09:57:47.919416195 -0700
+++ 11.4.69/man3dns_sd/DNSServiceResolve.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,86 +0,0 @@
-DNS...olve(3DNS_SD) DNS Service Discovery Library FunctionsDNS...olve(3DNS_SD)
-
-NAME
- DNSServiceResolve - resolve service instances with DNS
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- DNSServiceErrorType DNSServiceResolve(DNSServiceRef *sdRef,
- DNSServiceFlags flags, uint32_t interfaceIndex, const char *name,
- const char *regtype, const char *domain,
- DNSServiceServiceResolveReply callBack, void *context);
-
-
- typedef void(*DNSServiceResolveReply)(DNSServiceRef sdRef,
- DNSServiceFlags flags, uint32_t interfaceIndex,
- DNSServiceErrorType errorCode, const char *fullname,
- const char *hosttarget, uint16_t port, uint16_t txtLen,
- const char *txtRecord, void *context);
-
-DESCRIPTION
- The DNSServiceResolve() function is used to resolve a service name re-
- turned by DNSServiceBrowse() to host IP address, port number, and TXT
- record. The DNSServiceResolve() function returns results asynchro-
- nously. A DNSServiceResolve() call to resolve service name can be ended
- by calling DNSServiceRefDeallocate(). The callback argument points to a
- function of type DNSServiceResolveReply as listed above. The callback
- function is invoked on finding a result or when the asynch resolve call
- fails. The sdRef argument to DNSServiceResolve() points to an unini-
- tialized DNSServiceRef. If the call to DNSServiceResolve() succeeds,
- sdRef is initialized and kDNSServiceErr_NoError is returned.
-
-
- The flags argument to DNSServiceResolve() is currently unused and re-
- served for future use. The interfaceIndex argument indicates the inter-
- face on which to resolve the service. If the DNSServiceResolve() call
- is the result of an earlier DNSServiceBrowse() operation, pass the in-
- terfaceIndex to perform a resolve on all interfaces. See the section
- "Constants for specifying an interface index" in <dns_sd.h> for more
- details. The name parameter is the service instance name to be re-
- solved, as returned from a DNSServiceBrowse() call. The regtype holds
- the service type and the domain parameter indicates the domain in which
- the service instance was found. The context parameter points to a value
- that is passed to the callback function.
-
-
- The sdRef argument passed to the callback function is initialized by
- DNSServiceResolve() call. The flags parameter in the callback function
- is currently unused and reserved for future use. The errorCode parame-
- ter is kDNSServiceErr_NoError on success. Otherwise, it will hold the
- error defined in <dns_sd.h> and other parameters are undefined when er-
- rorCode is nonzero. The fullname parameter in the callback holds the
- full service domain name in the format <servicename>.<protocol>.<do-
- main>. The full service domain name is escaped to follow standard DNS
- rules. The hosttarget parameter holds the target hostname of the ma-
- chine providing the service. The port parameter indicates the port in
- network byte order on which the service accepts connections. The txtLen
- and txtRecord parameters hold the length and the TXT record of the ser-
- vice's primary TXT record. The context parameter points to the value
- that was passed as context to the DNSServiceResolve() call.
-
-RETURN VALUES
- The DNSServiceResolve function returns kDNSServiceErr_NoError on suc-
- cess. Otherwise, an error code defined in <dns_sd.h> is returned to in-
- dicate an error has occurred. When an error is returned by DNSSer-
- viceResolve, the callback function is not invoked and the DNSServiceRef
- argument is not initialized.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- DNSServiceBrowse(3DNS_SD), DNSServiceRefDeallocate(3DNS_SD), attrib-
- utes(7)
-
-Oracle Solaris 11.4 20 Aug 2007 DNS...olve(3DNS_SD)
diff -NurbBw 11.4.66/man3dns_sd/TXTRecordCreate.3dns_sd 11.4.69/man3dns_sd/TXTRecordCreate.3dns_sd
--- 11.4.66/man3dns_sd/TXTRecordCreate.3dns_sd 2024-05-25 09:57:47.955537106 -0700
+++ 11.4.69/man3dns_sd/TXTRecordCreate.3dns_sd 1969-12-31 16:00:00.000000000 -0800
@@ -1,73 +0,0 @@
-TXT...eate(3DNS_SD) DNS Service Discovery Library FunctionsTXT...eate(3DNS_SD)
-
-NAME
- TXTRecordCreate, TXTRecordDeallocate, TXTRecordSetValue, TXTRecor-
- dRemoveValue, TXTRecordGetLength, TXTRecordGetBytesPtr, TXTRecordCon-
- tainsKey, TXTRecordGetValuePtr, TXTRecordGetCount, TXTRecordGetItem-
- AtIndex - DNS TXT record manipulation functions
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
- void TXTRecordCreate(TXTRecordRef *txtRecord, uint16_t bufferLen,
- void *buffer);
-
-
- void TXTRecordDeallocate(TXTRecordRef*txtRecord);
-
-
- DNSServiceErrorType txtRecord(TXTRecordRef *txtRecord,
- const char *key, uint8_t valueSize, const void *value);
-
-
- DNSServiceErrorType TXTRecordRemoveValue(TXTRecordRef *txtRecord,
- const char *key);
-
-
- uint16_t TXTRecordGetLength(const TXTRecordRef *txtRecord);
-
-
- const void *TXTRecordGetBytesPtr(const TXTRecordRef *txtRecord);
-
-
- int *TXTRecordContainsKey(uint16_t *txtLen,
- const void *txtRecord, const char *key);
-
-
- const void *TXTRecordGetValuePtr(uint16_t *txtLen,
- const void *txtRecord, const char *key,
- uint8_t *valueLen);
-
-
- uint16_t *TXTRecordGetCount(uint16_t *txtLen,
- const void *txtRecord);
-
-
- DNSServiceErrorType TXTRecordGetItemAtIndex(uint16_t *txtLen,
- const void *txtRecord, uint16_t *index,
- uint16_t *keyBufLen, char *key,
- uint8_t *valueLen, const void **value);
-
-DESCRIPTION
- These functions in the libdns_sd library allow applications to create
- and to manipulate TXT resource records. TXT resource records enable ap-
- plications to include service specific information, other than a host
- name and port number, as part of the service registration.
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- attributes(7)
-
-Oracle Solaris 11.4 20 Aug 2007 TXT...eate(3DNS_SD)
diff -NurbBw 11.4.66/man3head/limits.h.3head 11.4.69/man3head/limits.h.3head
--- 11.4.66/man3head/limits.h.3head 2024-05-25 09:57:48.007648643 -0700
+++ 11.4.69/man3head/limits.h.3head 2024-05-25 09:58:11.332668593 -0700
@@ -114,17 +114,6 @@
allowed to hold.
- LOGIN_NAME_MAX
-
- Maximum length of a login name.
-
-
- MQ_OPEN_MAX
-
- The maximum number of open message queue descriptors a process is
- allowed to hold.
-
-
MQ_PRIO_MAX
The maximum number of message priorities supported by the implemen-
@@ -381,10 +370,6 @@
within parentheses by the expr(1) utility.
- EXPR_NEST_MAX Maximum number of expressions that can be nested
- within parentheses by the expr utility.
-
-
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-
@@ -401,7 +386,7 @@
notation \{m,n\}.
- Maximum Values
+ Minimum Values
The symbolic constants in the following list are symbolic names for the
most restrictive value for certain features on an implementation sup-
porting the POSIX Timers option.
@@ -410,7 +395,7 @@
nanoseconds.
- Minimum Values
+ Maximum Values
The symbolic constants in the following list are symbolic names for the
most restrictive value for certain features on an implementation con-
forming to various POSIX and Single UNIX Specification requirements.
@@ -830,4 +815,4 @@
SEE ALSO
fpathconf(2), pathconf(2), sysconf(3C), standards(7)
-Oracle Solaris 11.4 11 May 2021 limits.h(3HEAD)
+Oracle Solaris 11.4 10 Jan 2024 limits.h(3HEAD)
diff -NurbBw 11.4.66/man3kstat2/kstat2.3kstat2 11.4.69/man3kstat2/kstat2.3kstat2
--- 11.4.66/man3kstat2/kstat2.3kstat2 2024-05-25 09:57:48.070708437 -0700
+++ 11.4.69/man3kstat2/kstat2.3kstat2 2024-05-25 09:58:11.393833874 -0700
@@ -1079,7 +1079,7 @@
/* Open a kstats handle */
kstat2_status_t stat;
kstat2_handle_t handle;
- stat = kstat2_open(&handle);
+ stat = kstat2_open(&handle, NULL);
if (stat != KSTAT2_S_OK) {
fatal("Can't open kstats", stat);
}
@@ -1279,4 +1279,4 @@
threads intend to share a kstat2_handle_t or any object obtained
through it. Synchronization is left to the application.
-Oracle Solaris 11.4 12 Jul 2018 kstat2(3KSTAT2)
+Oracle Solaris 11.4 16 Jan 2024 kstat2(3KSTAT2)
diff -NurbBw 11.4.66/man3lib/libc.3lib 11.4.69/man3lib/libc.3lib
--- 11.4.66/man3lib/libc.3lib 2024-05-25 09:57:48.159599469 -0700
+++ 11.4.69/man3lib/libc.3lib 2024-05-25 09:58:11.489653690 -0700
@@ -632,6 +632,7 @@
postwait_genkey postwait_post
postwait_post_deferred postwait_postn
ppoll pread
+ preadv
printf printstack
priocntl priocntlset
priv_addset priv_allocset
@@ -723,7 +724,8 @@
pututline pututxline
putw putwc
putwchar putws
- pwrite qeconvert
+ pwrite
+ pwritev qeconvert
qecvt qfconvert
qfcvt qgconvert
qgcvt qsort
@@ -1138,8 +1140,9 @@
mkstemp64 mkstemps64
mmap64
nftw64 open64
- pread64 ptrace
- pwrite64 readdir64
+ pread64 preadv64
+ ptrace pwrite64
+ pwritev64 readdir64
readdir64_r s_fcntl
s_ioctl select_large_fdset
sendfile64 sendfilev64
@@ -1349,4 +1352,4 @@
generation of applications that call the obsolete leading-underscore
synonym functions, nor to endorse this particular programming practice.
-Oracle Solaris 11.4 21 Oct 2021 libc(3LIB)
+Oracle Solaris 11.4 8 Jan 2024 libc(3LIB)
diff -NurbBw 11.4.66/man3lib/libdns_sd.3lib 11.4.69/man3lib/libdns_sd.3lib
--- 11.4.66/man3lib/libdns_sd.3lib 2024-05-25 09:57:48.195640418 -0700
+++ 11.4.69/man3lib/libdns_sd.3lib 1969-12-31 16:00:00.000000000 -0800
@@ -1,51 +0,0 @@
-libdns_sd(3LIB) Interface Libraries libdns_sd(3LIB)
-
-NAME
- libdns_sd - DNS service discovery library
-
-SYNOPSIS
- cc [ flag ... ] file ... -ldns_sd [ library ... ]
- #include <dns_sd.h>
-
-DESCRIPTION
- The libdns_sd library functions provide facilities for applications to
- advertise and discover services that use the DNS protocol.
-
-INTERFACES
- The shared object libdns_sd.so.1 provides the public interfaces defined
- below. See intro(3) for additional information on shared object inter-
- faces.
-
- DNSServiceBrowse DNSServiceConstructFullName
- DNSServiceCreateConnection DNSServiceEnumerateDomains
- DNSServiceProcessResult DNSServiceQueryRecord
- DNSServiceReconfirmRecord DNSServiceRefDeallocate
- DNSServiceRefSockFD DNSServiceRegister
- DNSServiceResolve TXTRecordCreate
-
-
-FILES
- /lib/libdns_sd.so.1 shared object
-
-
- /lib/64/libdns_sd.so.1 64-bit shared object
-
-
-ATTRIBUTES
- See attributes(7) for description of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE |ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Availability |service/network/dns/mdns |
- +------------------------------+-----------------------------+
- | Interface Stability |Committed |
- +------------------------------+-----------------------------+
- | MT-Level |Safe |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- intro(3), attributes(7)
-
-Oracle Solaris 11.4 27 Nov 2017 libdns_sd(3LIB)
diff -NurbBw 11.4.66/man4d/ahci.4d 11.4.69/man4d/ahci.4d
--- 11.4.66/man4d/ahci.4d 2024-05-25 09:57:48.230982561 -0700
+++ 11.4.69/man4d/ahci.4d 2024-05-25 09:58:11.525815441 -0700
@@ -16,7 +16,7 @@
troller hardware.
- The ahci driver currently supports the Intel ICH6/7/8/9/10, VIA vt8251
+ The ahci driver currently supports the Intel ICH6/7/8/9/10, VIA vt8251,
and JMicron AHCI controllers which are compliant with the Advanced Host
Controller Interface 1.0 specification. The Intel ICH6/7/8/9 and VIA
vt8251 controllers support standard SATA features. The ahci driver cur-
@@ -42,7 +42,7 @@
cal Region Descriptor Table) contains the scatter/gather list for
the data transfer. The number of PRDT in the command table can be
from 1 to 65,535. The default value is 257, (1MB (256KB/pg * 256) +
- 1).. See the AHCI specification for more details.
+ 1). See the AHCI specification for more details.
ahci-msi-enabled
@@ -118,6 +118,6 @@
Booting is not supported if toggle exists between the [IDE] and [AHCI]
- BIOS options
+ BIOS options.
-Oracle Solaris 11.4 4 Jan 2012 ahci(4D)
+Oracle Solaris 11.4 15 Mar 2024 ahci(4D)
diff -NurbBw 11.4.66/man4d/asy.4d 11.4.69/man4d/asy.4d
--- 11.4.66/man4d/asy.4d 2024-05-25 09:57:48.268886366 -0700
+++ 11.4.69/man4d/asy.4d 2024-05-25 09:58:11.560526761 -0700
@@ -32,10 +32,10 @@
the stream, providing the standard termio(4I) interface.
- The character-special devices /dev/term/a, /dev/term/b, /dev/term/c and
- /dev/term/d are used to access the four standard serial ports (COM1,
- COM2, COM3 and COM4 at I/O addresses 3f8, 2f8, 3e8 and 2e8 respec-
- tively). Serial ports on non-standard ISA-bus I/O addresses are ac-
+ The character-special devices /dev/term/a, /dev/term/b, /dev/term/c,
+ and /dev/term/d are used to access the four standard serial ports
+ (COM1, COM2, COM3, and COM4 at I/O addresses 3f8, 2f8, 3e8, and 2e8 re-
+ spectively). Serial ports on non-standard ISA-bus I/O addresses are ac-
cessed via the character-special devices /dev/term/0, /dev/term/1, etc.
Device names are typically used to provide a logical access point for a
dial-in line that is used with a modem.
@@ -53,10 +53,11 @@
- This module is affected by the setting of certain eeprom variables,
- ttya-ignore-cd and ttya-rts-dtr-off (and similarly for ttyb-, ttyc-,
- and ttyd- parameters). For information on these parameters, see the
- eeprom(8) man page.
+ This module is affected by the setting of the eeprom variables, tty-
+ ignore-cd and tty-rts-dtr-off, where tty represents the name of the
+ tty interface in question: ttya, ttyb, ttyc, or ttyd. For example,
+ ttya is affected by variables ttya-ignore-cd and ttya-rts-dtr-off.
+ For information on these parameters, see the eeprom(8) man page.
Note -
@@ -157,6 +158,8 @@
+------------------------------+-----------------------------+
| Architecture |x86 |
+------------------------------+-----------------------------+
+ | Availability |driver/serial/asy |
+ +------------------------------+-----------------------------+
SEE ALSO
@@ -176,4 +179,4 @@
be serviced.
-Oracle Solaris 11.4 19 Feb 2019 asy(4D)
+Oracle Solaris 11.4 15 Mar 2024 asy(4D)
diff -NurbBw 11.4.66/man4d/ata.4d 11.4.69/man4d/ata.4d
--- 11.4.66/man4d/ata.4d 2024-05-25 09:57:48.307605144 -0700
+++ 11.4.69/man4d/ata.4d 2024-05-25 09:58:11.601781461 -0700
@@ -115,19 +115,19 @@
ata-dma-enabled
This property is examined before the DMA properties discussed be-
- low. If it is set to '0,' DMA is disabled for all ATA/ATAPI de-
+ low. If it is set to '0', DMA is disabled for all ATA/ATAPI de-
vices, and no further property checks are made. If this property is
- absent or is set to '1,' DMA status is determined by further exam-
+ absent or is set to '1', DMA status is determined by further exam-
ining one of the other properties listed below.
ata-disk-dma-enabled
This property is examined only for ATA disk devices, and only if
- ata-dma-enabled is not set to '0.'
+ ata-dma-enabled is not set to '0'.
- If ata-disk-dma-enabled set to '0,' DMA is disabled for all ATA
- disks in the system. If this property is absent or set to '1,' DMA
+ If ata-disk-dma-enabled is set to '0', DMA is disabled for all ATA
+ disks in the system. If this property is absent or set to '1', DMA
is enabled for all ATA disks and no further property checks are
made. If needed, this property should be created by the administra-
tor using the GRUB multiboot command line or the eeprom(8) command.
@@ -136,10 +136,10 @@
atapi-cd-dma-enabled
This property is examined only for ATAPI CD/DVD devices, and only
- if ata-dma-enabled is not set to '0.'
+ if ata-dma-enabled is not set to '0'.
- If atapi-cd-dma-enabled is absent or set to '0,' DMA is disabled
- for all ATAPI CD/DVD's. If set to '1,' DMA is enabled and no fur-
+ If atapi-cd-dma-enabled is absent or set to '0', DMA is disabled
+ for all ATAPI CD/DVD's. If set to '1', DMA is enabled and no fur-
ther property checks are made.
The Solaris installation program creates this property in the boot
@@ -153,8 +153,8 @@
This property is examined only for non-CD/DVD ATAPI devices such as
ATAPI tape drives, and only if ata-dma-enabled is not set to '0.'
- If atapi-other-dma-enabled is set to '0,' DMA is disabled for all
- non-CD/DVD ATAPI devices. If this property is absent or set to '1,'
+ If atapi-other-dma-enabled is set to '0', DMA is disabled for all
+ non-CD/DVD ATAPI devices. If this property is absent or set to '1',
DMA is enabled and no further property checks are made.
If needed, this property should be created by the administrator us-
@@ -172,7 +172,7 @@
buffer size. Some controllers hang when buffering is used, so the
values in the configuration file are used by the driver to reduce
the effect of buffering (blocking). The values presented may be
- chosen from 0x1, 0x2, 0x4, 0x8 and 0x10.
+ chosen from 0x1, 0x2, 0x4, 0x8, and 0x10.
The values as shipped are set to 0x1, and they can be tuned to in-
crease performance.
@@ -186,7 +186,7 @@
ata-revert-to-defaults
- revert--<diskmodel>
+ revert-<diskmodel>
When rebooting or shutting down, the driver can set a feature which
allows the drive to return to the power-on settings when the drive
@@ -200,7 +200,7 @@
To determine the string to substitute for <diskmodel>, boot your
system (you may have to press the reset button or power-cycle) and
then view /var/adm/messages. Look for the string "IDE device at
- targ" or "ATAPI device at targ." The next line will contain the
+ targ" or "ATAPI device at targ". The next line will contain the
word "model" followed by the model number and a comma. Ignore all
characters except letters, digits, ".", "_", and "-". Change upper-
case letters to lowercase. If the string revert-<diskmodel> is
@@ -304,6 +304,8 @@
+------------------------------+-----------------------------+
| Architecture |x86 |
+------------------------------+-----------------------------+
+ | Availability |driver/storage/ata |
+ +------------------------------+-----------------------------+
SEE ALSO
@@ -312,4 +314,4 @@
INCITS T13 ATA/ATAPI-7 specifications
-Oracle Solaris 11.4 11 May 2021 ata(4D)
+Oracle Solaris 11.4 15 Mar 2024 ata(4D)
diff -NurbBw 11.4.66/man4d/audio.4d 11.4.69/man4d/audio.4d
--- 11.4.66/man4d/audio.4d 2024-05-25 09:57:48.347956986 -0700
+++ 11.4.69/man4d/audio.4d 2024-05-25 09:58:11.637969725 -0700
@@ -44,7 +44,7 @@
An audio data format is characterized in the audio driver by four para-
- meters: sample Rate, encoding, precision, and channels. Refer to the
+ meters: sample rate, encoding, precision, and channels. Refer to the
device-specific manual pages for a list of the audio formats that each
device supports. In addition to the formats that the audio device sup-
ports directly, other formats provide higher data compression. Applica-
@@ -116,17 +116,19 @@
Supported Formats
The audio mixer supports the following audio formats:
-
-
-
- Encoding Precision Channels
- Signed Linear PCM 32-bit Mono or Stereo
- Signed Linear PCM 16-bit Mono or Stereo
- Signed Linear PCM 8-bit Mono or Stereo
- u-Law 8-bit Mono or Stereo
- A-Law 8-bit Mono or Stereo
-
-
+ +------------------------+-------------+------------------------+
+ | ENCODING | PRECISION | CHANNELS |
+ +------------------------+-------------+------------------------+
+ | Signed Linear PCM | 32-bit | Mono or Stereo |
+ +------------------------+-------------+------------------------+
+ | Signed Linear PCM | 16-bit | Mono or Stereo |
+ +------------------------+-------------+------------------------+
+ | Signed Linear PCM | 8-bit | Mono or Stereo |
+ +------------------------+-------------+------------------------+
+ | u-Law | 8-bit | Mono or Stereo |
+ +------------------------+-------------+------------------------+
+ | A-Law | 8-bit | Mono or Stereo |
+ +------------------------+-------------+------------------------+
@@ -168,4 +170,4 @@
SEE ALSO
ioctl(2), audio(4I), dsp(4I), attributes(7)
-Oracle Solaris 11.4 27 Nov 2017 audio(4D)
+Oracle Solaris 11.4 15 Mar 2024 audio(4D)
diff -NurbBw 11.4.66/man4d/audio1575.4d 11.4.69/man4d/audio1575.4d
--- 11.4.66/man4d/audio1575.4d 2024-05-25 09:57:48.379240051 -0700
+++ 11.4.69/man4d/audio1575.4d 2024-05-25 09:58:11.670184386 -0700
@@ -5,11 +5,12 @@
terface
DESCRIPTION
- The audio1575 device uses the Uli M1575 AC97-compatible audio digital
- controller and an AC-97 Codec to implement the audio device interface.
- This interface allows analog only inputs and outputs.
+ The audio1575 device uses the Uli M1575 AC'97-compatible audio digital
+ controller and an AC'97 Codec to implement the audio device interface.
+ This interface allows analog-only inputs and outputs.
FILES
+ /kernel/drv/amd64/audio1575
/kernel/drv/sparcv9/audio1575
64-bit driver module
@@ -43,4 +45,4 @@
AD1981B AC '97 SoundMAX(R) Codec Data Sheet-- Analog Devices Inc.
-Oracle Solaris 11.4 16 Aug 2011 audio1575(4D)
+Oracle Solaris 11.4 15 Mar 2024 audio1575(4D)
diff -NurbBw 11.4.66/man4d/audio810.4d 11.4.69/man4d/audio810.4d
--- 11.4.66/man4d/audio810.4d 2024-05-25 09:57:48.410783517 -0700
+++ 11.4.69/man4d/audio810.4d 2024-05-25 09:58:11.704873854 -0700
@@ -5,7 +5,7 @@
core support
DESCRIPTION
- The audio810 driver provides support for AC 97 audio controllers embed-
+ The audio810 driver provides support for AC'97 audio controllers embed-
ded in Intel ICH, nVidia nForce, and AMD 8111 chips.
FILES
@@ -16,7 +16,7 @@
ATTRIBUTES
- See attributes(7) for a descriptions of the following attributes:
+ See attributes(7) for descriptions of the following attributes:
+---------------------+---------------------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
@@ -43,7 +43,7 @@
Some laptops (including Sony VAIO, among others), have their on-board
amplifier powered down by default, meaning that audio is suppressed
even if hardware and the audio810 driver are working normally. To cor-
- rect this, set the ac97-invert-amp=1 property in the /kernel/drv/au-
- dio810.conf to power-up the amplifier.
+ rect this, set the ac97-amplifier=0 property in the /kernel/drv/au-
+ dio810.conf file to power-up the amplifier.
-Oracle Solaris 11.4 14 Jun 2023 audio810(4D)
+Oracle Solaris 11.4 15 Mar 2024 audio810(4D)
diff -NurbBw 11.4.66/man4d/audiocmi.4d 11.4.69/man4d/audiocmi.4d
--- 11.4.66/man4d/audiocmi.4d 2024-05-25 09:57:48.442718358 -0700
+++ 11.4.69/man4d/audiocmi.4d 2024-05-25 09:58:11.736964541 -0700
@@ -1,7 +1,7 @@
audiocmi(4D) Device Drivers & /dev files audiocmi(4D)
NAME
- audiocmi - C-Media 8738, 8768, and 8338 driver support
+ audiocmi - C-Media 8738, 8768, and 8338 audio driver
DESCRIPTION
The audiocmi driver provides support for the C-Media 8738, 8768, and
@@ -9,23 +9,14 @@
add-in PCI cards.
FILES
- /kernel/drv/amd64/audiocmi
+ /kernel/drv/amd64/audiocmi 64-bit x86 kernel driver module
- 64-bit x86 kernel driver module
-
- /kernel/drv/sparcv9/audiocmi
-
- 64-bit SPARC kernel driver module
-
-
- /kernel/drv/audiocmi.conf
-
- Driver configuration file
+ /kernel/drv/audiocmi.conf Driver configuration file
ATTRIBUTES
- See attributes(7) for a descriptions of the following attributes:
+ See attributes(7) for descriptions of the following attributes:
+---------------------+--------------------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
@@ -39,4 +30,4 @@
SEE ALSO
ioctl(2), audio(4I), mixer(4I), streamio(4I), attributes(7)
-Oracle Solaris 11.4 14 Jun 2023 audiocmi(4D)
+Oracle Solaris 11.4 15 Mar 2024 audiocmi(4D)
diff -NurbBw 11.4.66/man4d/audiohd.4d 11.4.69/man4d/audiohd.4d
--- 11.4.66/man4d/audiohd.4d 2024-05-25 09:57:48.476278652 -0700
+++ 11.4.69/man4d/audiohd.4d 2024-05-25 09:58:11.768590829 -0700
@@ -1,7 +1,7 @@
audiohd(4D) Device Drivers & /dev files audiohd(4D)
NAME
- audiohd - Intel High Definition Audio Controller support
+ audiohd - Intel High Definition Audio Controller driver
DESCRIPTION
The audiohd driver provides support for the generic codec chips which
@@ -16,7 +16,7 @@
ATTRIBUTES
- See attributes(7) for a descriptions of the following attributes:
+ See attributes(7) for descriptions of the following attributes:
+---------------------+---------------------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
@@ -38,4 +38,4 @@
ALC880 Specification -- Realtek Inc.
-Oracle Solaris 11.4 14 Jun 2023 audiohd(4D)
+Oracle Solaris 11.4 15 Mar 2024 audiohd(4D)
diff -NurbBw 11.4.66/man4d/audioixp.4d 11.4.69/man4d/audioixp.4d
--- 11.4.66/man4d/audioixp.4d 2024-05-25 09:57:48.508303734 -0700
+++ 11.4.69/man4d/audioixp.4d 2024-05-25 09:58:11.799466856 -0700
@@ -5,7 +5,7 @@
DESCRIPTION
The audioixp device uses the IXP400 south bridge audio digital con-
- troller and a AC-97 Codec to implement the audio device interface.
+ troller and a AC'97 Codec to implement the audio device interface.
The audioixp device provides support for the internal speaker, head-
@@ -19,7 +19,7 @@
ATTRIBUTES
- See attributes(7) for a descriptions of the following attributes:
+ See attributes(7) for descriptions of the following attributes:
+---------------------+---------------------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
@@ -38,4 +38,4 @@
ATI IXP400 South Bridge Data Sheet
-Oracle Solaris 11.4 14 Jun 2023 audioixp(4D)
+Oracle Solaris 11.4 15 Mar 2024 audioixp(4D)
diff -NurbBw 11.4.66/man4d/audiopci.4d 11.4.69/man4d/audiopci.4d
--- 11.4.66/man4d/audiopci.4d 2024-05-25 09:57:48.544082273 -0700
+++ 11.4.69/man4d/audiopci.4d 2024-05-25 09:58:11.829858981 -0700
@@ -9,13 +9,19 @@
identified as Audio PCI and SoundBlaster PCI.
FILES
- /kernel/drv/amd64/audiopci 64-bit x86 kernel driver module
+ /kernel/drv/amd64/audiopci
+ 64-bit x86 kernel driver module
- /kernel/drv/amd64/audiopci 64-bit SPARC kernel driver module
+ /kernel/drv/sparcv9/audiopci
- /kernel/drv/audiopci.conf Driver configuration file
+ 64-bit SPARC kernel driver module
+
+
+ /kernel/drv/audiopci.conf
+
+ Driver configuration file
ATTRIBUTES
@@ -36,4 +42,4 @@
Creative Technology Ltd ES1370 Specification
-Oracle Solaris 11.4 2 Jan 2012 audiopci(4D)
+Oracle Solaris 11.4 15 Mar 2024 audiopci(4D)
diff -NurbBw 11.4.66/man4d/audiots.4d 11.4.69/man4d/audiots.4d
--- 11.4.66/man4d/audiots.4d 2024-05-25 09:57:48.579351401 -0700
+++ 11.4.69/man4d/audiots.4d 2024-05-25 09:58:11.863604509 -0700
@@ -4,7 +4,7 @@
audiots - Acer Laboratories Inc. M5451 audio processor interface
DESCRIPTION
- The audiots device uses the ALI M5451 audio processor and an AC-97
+ The audiots device uses the ALI M5451 audio processor and an AC'97
Codec to implement the audio device interface.
@@ -23,7 +23,7 @@
ATTRIBUTES
- See attributes(7) for a descriptions of the following attributes:
+ See attributes(7) for descriptions of the following attributes:
+---------------------+---------------------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
@@ -43,4 +43,4 @@
Acer Laboratories Inc. M5451 PCI Audio Processor Technical Specifica-
tion
-Oracle Solaris 11.4 14 Jun 2023 audiots(4D)
+Oracle Solaris 11.4 15 Mar 2024 audiots(4D)
diff -NurbBw 11.4.66/man4d/audiovia823x.4d 11.4.69/man4d/audiovia823x.4d
--- 11.4.66/man4d/audiovia823x.4d 2024-05-25 09:57:48.611576491 -0700
+++ 11.4.69/man4d/audiovia823x.4d 2024-05-25 09:58:11.897072526 -0700
@@ -1,7 +1,7 @@
audiovia823x(4D) Device Drivers & /dev files audiovia823x(4D)
NAME
- audiovia823x - VIA VT8233, VT8235, and VT8237) support
+ audiovia823x - VIA VT8233, VT8235, and VT8237 support
DESCRIPTION
The audiovia823x driver provides support for the VIA VT8233, VT8235,
@@ -31,4 +31,4 @@
SEE ALSO
audio(4I), dsp(4I), mixer(4I), attributes(7)
-Oracle Solaris 11.4 4 Jan 2012 audiovia823x(4D)
+Oracle Solaris 11.4 15 Mar 2024 audiovia823x(4D)
diff -NurbBw 11.4.66/man4d/balloon.4d 11.4.69/man4d/balloon.4d
--- 11.4.66/man4d/balloon.4d 2024-05-25 09:57:48.644354449 -0700
+++ 11.4.69/man4d/balloon.4d 2024-05-25 09:58:11.932749967 -0700
@@ -7,8 +7,8 @@
/platform/i86hvm/kernel/drv/amd64/balloon
DESCRIPTION
- The balloon driver is used to adjust current memory reservation for So-
- laris domU that is running on Xen hypervisor.
+ The balloon driver is used to adjust the current memory reservation for
+ an Oracle Solaris domU that is running under a Xen hypervisor.
Xen dom0 controls the balloon module running within Solaris guest, di-
@@ -84,7 +100,7 @@
Currently, the balloon driver only supports adjusting memory reserva-
- tion within the maximum memory size assigned at domU creation. It is
+ tions within the maximum memory size assigned at domU creation. It is
(0,4096] in the above example.
ATTRIBUTES
@@ -104,4 +120,8 @@
SEE ALSO
attributes(7)
-Oracle Solaris 11.4 16 Sep 2014 balloon(4D)
+HISTORY
+ The balloon driver was added to Solaris in the Oracle Solaris 11.1.0
+ release.
+
+Oracle Solaris 11.4 15 Mar 2024 balloon(4D)
diff -NurbBw 11.4.66/man4d/bge.4d 11.4.69/man4d/bge.4d
--- 11.4.66/man4d/bge.4d 2024-05-25 09:57:48.679464677 -0700
+++ 11.4.69/man4d/bge.4d 2024-05-25 09:58:11.969510450 -0700
@@ -9,13 +9,13 @@
DESCRIPTION
The bge Gigabit Ethernet driver is a multi-threaded, loadable, clon-
able, GLD-based STREAMS driver supporting the Data Link Provider Inter-
- face, dlpi(4P), on Broadcom BCM57xx
- (BCM5700/5701/5703/5704/5705/5705M/5714/5721/5751/5751M/5782/5788 on
- x86) Gigabit Ethernet controllers fitted to the system motherboard.
- With the exception of BCM5700/BCM5701/BCM5704S, these devices incorpo-
- rate both MAC and PHY functions and provide three-speed (copper) Ether-
- net operation on the RJ-45 connectors. (BCM5700/BCM5701/BCM5704S do not
- have a PHY integrated into the MAC chipset.)
+ face, dlpi(4P), on Broadcom BCM57xx (BCM5700/5701/5703/5704/5705/5705M/
+ 5714/5721/5751/5751M/5782/5788 on x86) Gigabit Ethernet controllers
+ fitted to the system motherboard. With the exception of
+ BCM5700/BCM5701/BCM5704S, these devices incorporate both MAC and PHY
+ functions and provide three-speed (copper) Ethernet operation on the
+ RJ-45 connectors. (BCM5700/BCM5701/BCM5704S do not have a PHY inte-
+ grated into the MAC chipset.)
The bge driver functions include controller initialization, frame
@@ -213,6 +205,8 @@
+------------------------------+-----------------------------+
| Architecture |SPARC, x86 |
+------------------------------+-----------------------------+
+ | Availability |driver/network/ethernet/bge |
+ +------------------------------+-----------------------------+
SEE ALSO
@@ -224,4 +218,4 @@
STREAMS Programming Guide
-Oracle Solaris 11.4 4 Jan 2012 bge(4D)
+Oracle Solaris 11.4 15 Mar 2024 bge(4D)
diff -NurbBw 11.4.66/man4d/bpf.4d 11.4.69/man4d/bpf.4d
--- 11.4.66/man4d/bpf.4d 2024-05-25 09:57:48.729356760 -0700
+++ 11.4.69/man4d/bpf.4d 2024-05-25 09:58:12.019095559 -0700
@@ -41,15 +41,13 @@
A packet can be sent out on the network by writing to a bpf file de-
scriptor. The writes are unbuffered, meaning that only one packet can
- be processed per write. Currently, only writes to Ethernets and SLIP
+ be processed per write. Currently, only writes to Ethernet and SLIP
links are supported.
IOCTLS
- The ioctl(2) command codes in this section are defined in <net/bfp.h>.
+ The ioctl(2) command codes in this section are defined in <net/bpf.h>.
All commands require these includes:
-
-
#include <sys/types.h>
#include <sys/time.h>
#include <sys/time.h>
@@ -373,11 +357,7 @@
For example, if p points to the start of a packet, this expression ad-
vances it to the next packet:
-
-
- p = (char *)p + BPF_WORDALIGN(p->bh_hdrlen + p->bh_caplen)
-
-
+ p = (char *)p + BPF_WORDALIGN(p->bh_hdrlen + p->bh_caplen);
@@ -591,18 +533,17 @@
-
The default and permitted range for these tunables is shown in bpf.conf
FILES
- /dev/bpf
/dev/bpf Special character device
- /usr/kernel/drv/bpf.conf Configuration file
+ /usr/kernel/drv/bpf.conf Configuration file
+
EXAMPLES
- Example 1 Using bfp to Accept Only Reverse ARP Requests
+ Example 1 Using bpf to Accept Only Reverse ARP Requests
@@ -623,9 +562,7 @@
};
-
-
- Example 2 Using bfp to Accept IP Packets
+ Example 2 Using bpf to Accept IP Packets
@@ -650,7 +585,7 @@
};
- Example 3 Using bfp to Return Only TCP Finger Packets
+ Example 3 Using bpf to Return Only TCP Finger Packets
@@ -687,6 +620,8 @@
+------------------------------+-----------------------------+
| Architecture |Sparc, x86 |
+------------------------------+-----------------------------+
+ | Availability |system/network/bpf |
+ +------------------------------+-----------------------------+
| Interface Stability |Committed |
+------------------------------+-----------------------------+
@@ -718,11 +653,11 @@
Under Oracle Solaris, if a BPF application reads more than 2^31 bytes
- of data, read fails in EINVALsignal(3C). You can either fix the bug in
- Oracle Solaris, or lseek(2) to 0 when read fails for this reason.
+ of data, read fails with EINVAL. You can lseek(2) to 0 when read fails
+ for this reason.
Immediate mode and the read timeout are misguided features. This func-
tionality can be emulated with non-blocking mode and select(3C).
-Oracle Solaris 11.4 11 May 2021 bpf(4D)
+Oracle Solaris 11.4 15 Mar 2024 bpf(4D)
diff -NurbBw 11.4.66/man4d/cmdk.4d 11.4.69/man4d/cmdk.4d
--- 11.4.66/man4d/cmdk.4d 2024-05-25 09:57:48.760324677 -0700
+++ 11.4.69/man4d/cmdk.4d 2024-05-25 09:58:12.053008396 -0700
@@ -8,7 +8,7 @@
DESCRIPTION
The cmdk device driver is a common interface to various disk devices.
- The driver supports magnetic fixed disks and magnetic removable disks.
+ The driver supports both fixed disks and removable disks.
The cmdk device driver supports three different disk labels: fdisk par-
@@ -25,15 +25,13 @@
found in /dev/rdsk.
- I/O requests to the magnetic disk must have an offset and transfer
- length that is a multiple of 512 bytes or the driver returns an EINVAL
- error.
+ I/O requests to the disk must have an offset and transfer length that
+ is a multiple of 512 bytes or the driver returns an EINVAL error.
- Slice 0 is normally used for the root file system on a disk, slice 1 as
- a paging area (for example, swap), and slice 2 for backing up the en-
- tire fdisk partition for Solaris software. Other slices may be used for
- usr file systems or system reserved area.
+ When not using ZFS, slice 2 is normally used for backing up the entire
+ fdisk partition for Solaris software. Other slices may be used for
+ other file systems or system reserved area.
The fdisk partition 0 is to access the entire disk and is generally
@@ -71,10 +69,12 @@
+------------------------------+-----------------------------+
| Architecture |x86 |
+------------------------------+-----------------------------+
+ | Availability |driver/storage/cmdk |
+ +------------------------------+-----------------------------+
SEE ALSO
lseek(2), read(2), write(2), readdir(3C), dkio(4I), scsi(5), vfstab(5),
attributes(7), fdisk(8), mount(8)
-Oracle Solaris 11.4 5 Jan 2012 cmdk(4D)
+Oracle Solaris 11.4 15 Mar 2024 cmdk(4D)
diff -NurbBw 11.4.66/man4d/console.4d 11.4.69/man4d/console.4d
--- 11.4.66/man4d/console.4d 2024-05-25 09:57:48.792936254 -0700
+++ 11.4.69/man4d/console.4d 2024-05-25 09:58:12.083826629 -0700
@@ -9,15 +9,16 @@
DESCRIPTION
The file /dev/console refers to the system console device. /dev/console
should be used for interactive purposes only. Use of /dev/console for
- logging purposes is discouraged; syslog(3C) or msglog(4D) should be
- used instead.
+ logging purposes is discouraged; syslog(3C), log(4D), or sysmsg(4D)
+ should be used instead.
The identity of this device depends on the EEPROM or NVRAM settings in
- effect at the most recent system reboot; by default, it is the "work-
- station console" device consisting of the workstation keyboard and
- frame buffer acting in concert to emulate an ASCII terminal (see ws-
- cons(4D)).
+ effect at the most recent system reboot; by default, if a graphics de-
+ vice is present in the system, it is the "workstation console" device
+ consisting of the system keyboard and graphics device acting in concert
+ to emulate an ASCII terminal (see wscons(4D)). If the system lacks a
+ graphics device, the default console is a serial port.
Regardless of the system configuration, the console device provides
@@ -26,7 +27,8 @@
terminal interface.
SEE ALSO
- syslog(3C), termios(3C), msglog(4D), wscons(4D), termio(4I), ldterm(4M)
+ syslog(3C), termios(3C), log(4D), sysmsg(4D), wscons(4D), termio(4I),
+ ldterm(4M)
NOTES
In contrast to pre-SunOS 5.0 releases, it is no longer possible to
@@ -38,7 +40,7 @@
See wscons(4D) for detailed descriptions of control sequence syntax,
- ANSI control functions, control character functions and escape sequence
- functions.
+ ANSI control functions, control character functions, and escape se-
+ quence functions.
-Oracle Solaris 11.4 23 Apr 1999 console(4D)
+Oracle Solaris 11.4 15 Mar 2024 console(4D)
diff -NurbBw 11.4.66/man4d/ecpp.4d 11.4.69/man4d/ecpp.4d
--- 11.4.66/man4d/ecpp.4d 2024-05-25 09:57:48.834062350 -0700
+++ 11.4.69/man4d/ecpp.4d 2024-05-25 09:58:12.125134689 -0700
@@ -117,25 +117,24 @@
The following ioctl(2) calls are supported for backward compatibility
and are not recommended for new applications:
- ECPPIOC_GETPARMS Get current transfer parameters. The argument is a
- pointer to a struct ecpp_transfer_parms. See below
- for a description of the elements of this struc-
- ture. If no parameters have been configured since
- the device was opened, the structure will be set to
- its default configuration. See DESCRIPTION for more
- information.
-
-
- ECPPIOC_SETPARMS Set transfer parameters. The argument is a pointer
- to a struct ecpp_transfer_parms. If a parameter is
- out of range, EINVAL is returned. If the peripheral
- or host device cannot support the requested mode,
- EPROTONOSUPPORT is returned. See below for a de-
- scription of ecpp_transfer_parms and its valid pa-
- rameters.
+ ECPPIOC_GETPARMS
- The Transfer Parameters Structure is defined in
- <sys/ecppio.h>.
+ Get current transfer parameters. The argument is a pointer to a
+ struct ecpp_transfer_parms. See below for a description of the ele-
+ ments of this structure. If no parameters have been configured
+ since the device was opened, the structure will be set to its de-
+ fault configuration. See DESCRIPTION for more information.
+
+
+ ECPPIOC_SETPARMS
+
+ Set transfer parameters. The argument is a pointer to a struct
+ ecpp_transfer_parms. If a parameter is out of range, EINVAL is re-
+ turned. If the peripheral or host device cannot support the re-
+ quested mode, EPROTONOSUPPORT is returned. See below for a descrip-
+ tion of ecpp_transfer_parms and its valid parameters.
+
+ The Transfer Parameters Structure is defined in <sys/ecppio.h>.
struct ecpp_transfer_parms {
@@ -143,31 +142,28 @@
int mode;
};
- The write_timeout field is set to the value of
- ecpp-transfer-timeout specified in the ecpp.conf.
- The write_timeout field specifies how long the dri-
- ver will wait for the peripheral to respond to a
- transfer request. The value must be greater than 0
- and less than ECPP_MAX_TIMEOUT. All other values
- are out of range.
-
- The mode field reflects the IEEE 1284 mode to which
- the parallel port is currently configured. The mode
- may be set to one of the following values only:
- ECPP_CENTRONICS, ECPP_COMPAT_MODE, ECPP_NIB-
- BLE_MODE, ECPP_ECP_MODE. All other values are in-
- valid. If the requested mode is not supported, ECP-
- PIOC_SETPARMS will return EPROTONOSUPPORT and the
- mode will be set to ECPP_CENTRONICS mode. After-
- ward, the application may change the mode back to
- the original mode with ECPPIOC_SETPARMS.
-
-
- ECPPIOC_GETDEVID This ioctl gets the IEEE 1284 device ID from the
- peripheral in specified mode. Currently, the device
- ID can be retrieved only in Nibble mode. A pointer
- to the structure defined in <sys/ecppsys.h> must be
- passed as an argument.
+ The write_timeout field is set to the value of ecpp-transfer-time-
+ out specified in the ecpp.conf. The write_timeout field specifies
+ how long the driver will wait for the peripheral to respond to a
+ transfer request. The value must be greater than 0 and less than
+ ECPP_MAX_TIMEOUT. All other values are out of range.
+
+ The mode field reflects the IEEE 1284 mode to which the parallel
+ port is currently configured. The mode may be set to one of the
+ following values only: ECPP_CENTRONICS, ECPP_COMPAT_MODE, ECPP_NIB-
+ BLE_MODE, ECPP_ECP_MODE. All other values are invalid. If the re-
+ quested mode is not supported, ECPPIOC_SETPARMS will return
+ EPROTONOSUPPORT and the mode will be set to ECPP_CENTRONICS mode.
+ Afterward, the application may change the mode back to the original
+ mode with ECPPIOC_SETPARMS.
+
+
+ ECPPIOC_GETDEVID
+
+ This ioctl gets the IEEE 1284 device ID from the peripheral in
+ specified mode. Currently, the device ID can be retrieved only in
+ Nibble mode. A pointer to the structure defined in <sys/ecppsys.h>
+ must be passed as an argument.
The 1284 device ID structure:
@@ -181,60 +175,52 @@
char *addr; /* buffer address */
};
- The mode is the IEEE 1284 mode into which the port
- will be negotiated to retrieve device ID informa-
- tion. If the peripheral or host do not support the
- mode, EPROTONOSUPPORT is returned. Applications
- should set mode to ECPP_NIBBLE_MODE. len is the
- length of the buffer pointed to by addr. rlen is
- the actual length of the device ID string returned
- from the peripheral. If the returned rlen is
- greater than len, the application can call ECP-
- PIOC_GETDEVID again with a buffer length equal or
- greater than rlen. Note that the two length bytes
- of the IEEE 1284 device ID are not taken into ac-
- count and are not returned in the user buffer.
-
- After ECPPIOC_GETDEVID successfully completes, the
- driver returns the link to ECPP_COMPAT_MODE. The
- application is responsible for determining the pre-
- vious mode the link was operating in and returning
- the link to that mode.
-
-
- BPPIOC_TESTIO Tests the forward transfer readiness of a periph-
- eral operating in Centronics or Compatibility mode.
-
- TESTIO determines if the peripheral is ready to re-
- ceive data by checking the open flags and the Cen-
- tronics status signals. If the current mode of the
- device is ECPP_NIBBLE_MODE, the driver negotiates
- the link into ECPP_COMPAT_MODE, check the status
- signals and then return the link to ECPP_NIB-
- BLE_MODE mode. If the current mode is ECPP_CENTRON-
- ICS or ECPP_COMPAT_MODE, TESTIO examines the Cen-
- tronics status signals in the current mode. To re-
- ceive data, the device must have the nErr and Se-
- lect signals asserted and must not have the PE and
- Busy signals asserted. If ecpp is transferring
- data, TESTIO waits until the previous data sent to
- the driver is delivered before executing TESTIO.
- However if an error condition occurs while a TESTIO
- is waiting, TESTIO returns immediately. If TESTIO
- determines that the conditions are ok, 0 is re-
- turned. Otherwise, -1 is returned, errno is set to
- EIO and the state of the status pins is captured.
- The captured status can be retrieved using the BP-
- PIOC_GETERR ioctl(2) call. The timeout_occurred
- and bus_error fields will never be set by this
- ioctl(2).
-
-
- BPPIOC_GETERR Get last error status. The argument is a pointer to
- a struct bpp_error_status defined in <sys/bpp_io.h>
- header file. The error status structure is:
-
-
+ The mode is the IEEE 1284 mode into which the port will be negoti-
+ ated to retrieve device ID information. If the peripheral or host
+ do not support the mode, EPROTONOSUPPORT is returned. Applications
+ should set mode to ECPP_NIBBLE_MODE. len is the length of the
+ buffer pointed to by addr. rlen is the actual length of the device
+ ID string returned from the peripheral. If the returned rlen is
+ greater than len, the application can call ECPPIOC_GETDEVID again
+ with a buffer length equal or greater than rlen. Note that the two
+ length bytes of the IEEE 1284 device ID are not taken into account
+ and are not returned in the user buffer.
+
+ After ECPPIOC_GETDEVID successfully completes, the driver returns
+ the link to ECPP_COMPAT_MODE. The application is responsible for
+ determining the previous mode the link was operating in and return-
+ ing the link to that mode.
+
+
+ BPPIOC_TESTIO
+
+ Tests the forward transfer readiness of a peripheral operating in
+ Centronics or Compatibility mode.
+
+ TESTIO determines if the peripheral is ready to receive data by
+ checking the open flags and the Centronics status signals. If the
+ current mode of the device is ECPP_NIBBLE_MODE, the driver negoti-
+ ates the link into ECPP_COMPAT_MODE, check the status signals and
+ then return the link to ECPP_NIBBLE_MODE mode. If the current mode
+ is ECPP_CENTRONICS or ECPP_COMPAT_MODE, TESTIO examines the Cen-
+ tronics status signals in the current mode. To receive data, the
+ device must have the nErr and Select signals asserted and must not
+ have the PE and Busy signals asserted. If ecpp is transferring
+ data, TESTIO waits until the previous data sent to the driver is
+ delivered before executing TESTIO. However if an error condition
+ occurs while a TESTIO is waiting, TESTIO returns immediately. If
+ TESTIO determines that the conditions are ok, 0 is returned. Other-
+ wise, -1 is returned, errno is set to EIO and the state of the sta-
+ tus pins is captured. The captured status can be retrieved using
+ the BPPIOC_GETERR ioctl(2) call. The timeout_occurred and bus_er-
+ ror fields will never be set by this ioctl(2).
+
+
+ BPPIOC_GETERR
+
+ Get last error status. The argument is a pointer to a struct
+ bpp_error_status defined in <sys/bpp_io.h> header file. The error
+ status structure is:
struct bpp_error_status {
@@ -244,32 +230,25 @@
/* could cause error */
};
+ The pin_status field indicates possible error conditions. The valid
+ bits for pin_status are: BPP_ERR_ERR, BPP_SLCT_ERR, BPP_PE_ERR,
+ BPP_BUSY_ERR. A set bit indicates that the associated pin is as-
+ serted.
+
+ This structure indicates the status of all the appropriate status
+ bits at the time of the most recent error condition during a
+ write(2) call, or the status of the bits at the most recent BP-
+ PIOC_TESTIO ioctl(2) call.
+
+ pin_status indicates possible error conditions under ECPP_CENTRON-
+ ICS or ECPP_COMPAT_MODE. Under these modes, the state of the status
+ pins will indicate the state of the device. For instance, many Cen-
+ tronics printers lower the nErr signal when a paper jam occurs. The
+ behavior of the status pins depends on the device. Additional sta-
+ tus information may be retrieved through the backchannel.
-
- The pin_status field indicates possible error con-
- ditions. The valid bits for pin_status are:
- BPP_ERR_ERR, BPP_SLCT_ERR, BPP_PE_ERR,
- BPP_BUSY_ERR. A set bit indicates that the associ-
- ated pin is asserted.
-
- This structure indicates the status of all the ap-
- propriate status bits at the time of the most re-
- cent error condition during a write(2) call, or the
- status of the bits at the most recent BPPIOC_TESTIO
- ioctl(2) call.
-
- pin_status indicates possible error conditions un-
- der ECPP_CENTRONICS or ECPP_COMPAT_MODE. Under
- these modes, the state of the status pins will in-
- dicate the state of the device. For instance, many
- Centronics printers lower the nErr signal when a
- paper jam occurs. The behavior of the status pins
- depends on the device. Additional status informa-
- tion may be retrieved through the backchannel.
-
- The timeout_occurred value is set when a timeout
- occurs during write(2). bus_error is not used in
- this interface.
+ The timeout_occurred value is set when a timeout occurs during
+ write(2). bus_error is not used in this interface.
@@ -389,4 +368,4 @@
Attach failed.
-Oracle Solaris 11.4 11 May 2021 ecpp(4D)
+Oracle Solaris 11.4 15 Mar 2024 ecpp(4D)
diff -NurbBw 11.4.66/man4d/full.4d 11.4.69/man4d/full.4d
--- 11.4.66/man4d/full.4d 2024-05-25 09:57:48.864700288 -0700
+++ 11.4.69/man4d/full.4d 2024-05-25 09:58:12.158873846 -0700
@@ -12,20 +12,24 @@
Data written on the full special file, /dev/full, is discarded, failure
- is returned and errno is set to ENOSPC.
+ is returned, and errno is set to ENOSPC.
Mapping a full special file creates an address reservation of a length
equal to the length of the mapping, and rounded up to the nearest page
size as returned by sysconf(3C). No resources are consumed by the
reservation. Mappings can be placed in the resulting address range via
- subsequent calls to mmap with the -MAP_FIXED option set.
+ subsequent calls to mmap with the MAP_FIXED option set.
FILES
/dev/full
SEE ALSO
- mmap(2), sysconf(3C)
+ mmap(2), sysconf(3C), null(4D), zero(4D)
-Oracle Solaris 11.4 1 June 2022 full(4D)
+HISTORY
+ The /dev/full device was added to Solaris in the Oracle Solaris 11.4.51
+ release.
+
+Oracle Solaris 11.4 15 Mar 2024 full(4D)
diff -NurbBw 11.4.66/man4d/gld.4d 11.4.69/man4d/gld.4d
--- 11.4.66/man4d/gld.4d 2024-05-25 09:57:48.916932509 -0700
+++ 11.4.69/man4d/gld.4d 2024-05-25 09:58:12.208263940 -0700
@@ -277,7 +271,7 @@
PPA using DL_ATTACH_REQ before this primitive will be successful.
- GLD supports the DL_NOTE_LINK_UP, DL_NOTE_LINK_DOWN and DL_NOTE_SPEED
+ GLD supports the DL_NOTE_LINK_UP, DL_NOTE_LINK_DOWN, and DL_NOTE_SPEED
notifications using the DL_NOTIFY_IND primitive. See dlpi(4P).
Implemented ioctl Functions
@@ -660,4 +654,4 @@
The physical address of a PPA may be changed by the superuser while
other streams are bound to the same PPA.
-Oracle Solaris 11.4 10 Nov 2005 gld(4D)
+Oracle Solaris 11.4 15 Mar 2024 gld(4D)
diff -NurbBw 11.4.66/man4d/hid.4d 11.4.69/man4d/hid.4d
--- 11.4.66/man4d/hid.4d 2024-05-25 09:57:48.952334211 -0700
+++ 11.4.69/man4d/hid.4d 2024-05-25 09:58:12.246194201 -0700
@@ -7,10 +7,12 @@
keyboard@unit-address
mouse@unit-address
input@unit-address:consumer_control
- #include <sys/hid.h>
- int ioctl(int fildes, int command, ... /*arg*/);
+ #include <sys/usb/clients/hid/hid.h>
+
+ int ioctl(int fildes, int command, ... /* arg */);
+
DESCRIPTION
The hid driver is a USBA (Solaris USB Architecture) compliant client
driver that supports the Human Interface Device Class (HID) 1.0 speci-
@@ -159,7 +161,7 @@
NOTES
- The hid driver currently supports only keyboard, mouse and audio HID
+ The hid driver currently supports only keyboard, mouse, and audio HID
control devices.
@@ -177,4 +177,4 @@
Modern mice that are power managed require a 'click' to wake up. Occa-
sionally, this may cause unexpected results.
-Oracle Solaris 11.4 14 Jun 2023 hid(4D)
+Oracle Solaris 11.4 15 Mar 2024 hid(4D)
diff -NurbBw 11.4.66/man4d/hubd.4d 11.4.69/man4d/hubd.4d
--- 11.4.66/man4d/hubd.4d 2024-05-25 09:57:48.990577649 -0700
+++ 11.4.69/man4d/hubd.4d 2024-05-25 09:58:12.281072949 -0700
@@ -10,7 +10,7 @@
The hubd is a USBA (Solaris USB Architecture) compliant client driver
that supports USB hubs conforming to the Universal Serial Bus Specifi-
cation 3.0. The hubd driver supports bus-powered and self-powered hubs.
- The driver supports hubs with individual port power, ganged power and
+ The driver supports hubs with individual port power, ganged power, and
no power switching.
@@ -24,9 +24,6 @@
vice.
FILES
- /kernel/drv/hubd 32- bit x86 ELF kernel module
-
-
/kernel/drv/amd64/hubd 64- bit x86 ELF kernel module
@@ -208,4 +205,4 @@
link configuration could not be completed.
-Oracle Solaris 11.4 14 Jun 2023 hubd(4D)
+Oracle Solaris 11.4 15 Mar 2024 hubd(4D)
diff -NurbBw 11.4.66/man4d/ib.4d 11.4.69/man4d/ib.4d
--- 11.4.66/man4d/ib.4d 2024-05-25 09:57:49.025893425 -0700
+++ 11.4.69/man4d/ib.4d 2024-05-25 09:58:12.318150348 -0700
@@ -11,9 +11,9 @@
gadm_ib(8) to manage hot-plugging of IB devices. The ib nexus driver
enumerates the port device, VPPA devices and HCA_SVC devices based on
entries specified in the ib.conf file. IOC devices are enumerated on
- demand. The IB nexus driver uses InfiniBand Device Manager services
- (ibdm(4D)) to enumerate port devices, VPPA devices, HCA_SVC devices,
- and IOCs on the IB fabric.
+ demand. The IB nexus driver uses InfiniBand Device Manager services,
+ ibdm(4D), to enumerate port devices, VPPA devices, HCA_SVC devices, and
+ IOCs on the IB fabric.
CONFIGURATION
You configure the ib driver by defining properties in the ib.conf file.
@@ -54,9 +54,9 @@
hca-svc-list with service names you want to add to the system.
- The service name specified in port-svc-list, vppa-svc-list and hca-svc-
- list must be unique, be a maximum of four characters long, and is lim-
- ited to digits 0-9 and letters a-z and A-Z.
+ The service name specified in port-svc-list, vppa-svc-list, and hca-
+ svc-list must be unique, be a maximum of four characters long, and is
+ limited to digits 0-9 and letters a-z and A-Z.
IOC drivers (which are parented by the IB nexus driver) may themselves
@@ -70,13 +70,7 @@
Example 1: A sample ib.conf file with one service name entry for PORT
communication services.
-
-
- #
- # Copyright (c) 2001, 2003, Oracle and/or its affiliates. All rights reserved.
- # Use is subject to license terms.
- #
- port-svc-list=""
+ port-svc-list="";
vppa-svc-list="";
hca-svc-list="";
@@ -88,8 +82,7 @@
Example 2: A sample ib.conf file with one entry for "srv" service:
-
- port-svc-list="srv"
+ port-svc-list="srv";
vppa-svc-list="";
hca-svc-list="";
@@ -104,8 +97,7 @@
Example 3: A sample ib.conf file with one service name entry for each
of Port and VPPA communication services:
-
- port-svc-list="srv"
+ port-svc-list="srv";
vppa-svc-list="ipib";
hca-svc-list="";
@@ -199,4 +186,4 @@
Waiting for port initialization from subnet manager.
-Oracle Solaris 11.4 5 Jan 2012 ib(4D)
+Oracle Solaris 11.4 15 Mar 2024 ib(4D)
diff -NurbBw 11.4.66/man4d/ipnet.4d 11.4.69/man4d/ipnet.4d
--- 11.4.66/man4d/ipnet.4d 2024-05-25 09:57:49.062613353 -0700
+++ 11.4.69/man4d/ipnet.4d 2024-05-25 09:58:12.351506702 -0700
@@ -139,4 +135,4 @@
SEE ALSO
dlpi(4P), attributes(7)
-Oracle Solaris 11.4 15 Mar 2011 ipnet(4D)
+Oracle Solaris 11.4 15 Mar 2024 ipnet(4D)
diff -NurbBw 11.4.66/man4d/ksyms.4d 11.4.69/man4d/ksyms.4d
--- 11.4.66/man4d/ksyms.4d 2024-05-25 09:57:49.098010503 -0700
+++ 11.4.69/man4d/ksyms.4d 2024-05-25 09:58:12.381808111 -0700
@@ -11,7 +11,7 @@
access to an ELF format image containing two sections: a symbol table
and a corresponding string table. The contents of the symbol table re-
flect the symbol state of the currently running kernel. You can deter-
- mine the size of the image with the fstat() system call. The recom-
+ mine the size of the image with the fstat(2) system call. The recom-
mended method for accessing the /dev/ksyms file is by using the ELF ac-
cess library. See elf(3ELF) for details. If you are not familiar with
ELF format, see a.out(5).
@@ -63,8 +63,8 @@
dated. In order to have access to the symbol information of the newly
loaded modules, you must first close and then reopen the /dev/ksyms
file. Be aware that the size of the /dev/ksyms file will have changed.
- You will need to use the fstat() function (see stat(2)) to determine
- the new size of the file.
+ You will need to use the fstat(2) function to determine the new size of
+ the file.
Avoid keeping the /dev/ksyms file open for extended periods of time,
@@ -90,4 +90,4 @@
/dev/ksyms as the default namelist file. See kvm_open(3KVM) for de-
tails.
-Oracle Solaris 11.4 11 Dec 2000 ksyms(4D)
+Oracle Solaris 11.4 15 Mar 2024 ksyms(4D)
diff -NurbBw 11.4.66/man4d/llc1.4d 11.4.69/man4d/llc1.4d
--- 11.4.66/man4d/llc1.4d 2024-05-25 09:57:49.134149724 -0700
+++ 11.4.69/man4d/llc1.4d 2024-05-25 09:58:12.419756163 -0700
@@ -176,4 +176,4 @@
SEE ALSO
dlpi(4P), attributes(7)
-Oracle Solaris 11.4 14 Jun 2023 llc1(4D)
+Oracle Solaris 11.4 15 Mar 2024 llc1(4D)
diff -NurbBw 11.4.66/man4d/lmrc.4d 11.4.69/man4d/lmrc.4d
--- 11.4.66/man4d/lmrc.4d 2024-05-25 09:57:49.165146618 -0700
+++ 11.4.69/man4d/lmrc.4d 2024-05-25 09:58:12.453743151 -0700
@@ -54,8 +54,8 @@
- The lmrc driver has different version on X86 and SPARC platform. The
- lmrc driver in X86 platform is a SCSAv3 compliant driver.
+ The lmrc driver has different versions on x86 and SPARC platforms. The
+ lmrc driver on the x86 platform is a SCSAv3 compliant driver.
Configuration
Configure your hardware through the related BIOS utility or the Raid-
@@ -67,7 +67,7 @@
The lmrc.conf file does not contain user editable parameters.
FILES
- /kernel/drv/amd64/lmrc 64-bit kernel module x86 ELF kernel module
+ /kernel/drv/amd64/lmrc 64-bit x86 ELF kernel module
/kernel/drv/sparcv9/lmrc 64-bit SPARC ELF kernel module
@@ -95,4 +95,4 @@
scsi_sync_pkt(9F), scsi_transport(9F), scsi_device(9S), scsi_in-
quiry(9S), scsi_pkt(9S)
-Oracle Solaris 11.4 21 Jul 2014 lmrc(4D)
+Oracle Solaris 11.4 15 Mar 2024 lmrc(4D)
diff -NurbBw 11.4.66/man4d/log.4d 11.4.69/man4d/log.4d
--- 11.4.66/man4d/log.4d 2024-05-25 09:57:49.203068946 -0700
+++ 11.4.69/man4d/log.4d 2024-05-25 09:58:12.495122291 -0700
@@ -20,45 +20,21 @@
own log messages.
Kernel Interface
- log messages are generated within the kernel by calls to the function
- strlog():
-
- strlog(short mid,
- short sid,
- char level,
- ushort_t flags,
- char *fmt,
- unsigned arg1...
- );
-
-
-
- Required definitions are contained in <sys/strlog.h>, <sys/log.h>, and
- <sys/syslog.h>. mid is the STREAMS module id number for the module or
- driver submitting the log message. sid is an internal sub-id number
- usually used to identify a particular minor device of a driver. level
- is a tracing level that allows for selective screening out of low pri-
- ority messages from the tracer. flags are any combination of SL_ERROR
- (the message is for the error logger), SL_TRACE (the message is for the
- tracer), SL_CONSOLE (the message is for the console logger), SL_FATAL
- (advisory notification of a fatal error), and SL_NOTIFY (request that a
- copy of the message be mailed to the system administrator). fmt is a
- printf(3C) style format string, except that %s, %e, %E, %g, and %G con-
- version specifications are not handled. Up to NLOGARGS (in this re-
- lease, three) numeric or character arguments can be provided.
+ log messages are generated within the kernel by calls to the strlog(9F)
+ and cmn_err(9F) functions.
User Interface
- log is implemented as a cloneable device, it clones itself without in-
- tervention from the system clone device. Each open of /dev/log obtains
- a separate stream to log. In order to receive log messages, a process
- must first notify log whether it is an error logger, trace logger, or
- console logger using a STREAMS I_STR ioctl call (see below). For the
- console logger, the I_STR ioctl has an ic_cmd field of I_CONSLOG, with
- no accompanying data. For the error logger, the I_STR ioctl has an
- ic_cmd field of I_ERRLOG, with no accompanying data. For the trace log-
- ger, the ioctl has an ic_cmd field of I_TRCLOG, and must be accompanied
- by a data buffer containing an array of one or more struct trace_ids
- elements.
+ log is implemented as a clonable device, which clones itself without
+ intervention from the system clone device. Each open of /dev/log ob-
+ tains a separate stream to log. In order to receive log messages, a
+ process must first notify log whether it is an error logger, trace log-
+ ger, or console logger using a STREAMS I_STR ioctl call. For the con-
+ sole logger, the I_STR ioctl has an ic_cmd field of I_CONSLOG, with no
+ accompanying data. For the error logger, the I_STR ioctl has an ic_cmd
+ field of I_ERRLOG, with no accompanying data. For the trace logger, the
+ ioctl has an ic_cmd field of I_TRCLOG, and must be accompanied by a
+ data buffer containing an array of one or more struct trace_ids ele-
+ ments.
struct trace_ids {
short ti_mid;
@@ -92,12 +68,11 @@
short sid;
char level; /* level of message for tracing */
short flags; /* message disposition */
- #if defined(_LP64) || defined(_I32LPx)
+ #if defined(_I32LPx)
clock32_t ltime; /* time in machine ticks since boot */
time32_t ttime; /* time in seconds since 1970 */
#else
- clock_t ltime;
- time_t ttime;
+ clock_t ltime; /* time in machine ticks since boot */
#endif
int seq_no; /* sequence number */
int pri; /* priority = (facility|level) */
@@ -121,10 +96,8 @@
ging streams, and are provided so that gaps in the sequence of messages
can be determined (during times of high message traffic some messages
may not be delivered by the logger to avoid hogging system resources).
- The data part of the message contains the unexpanded text of the format
- string (null terminated), followed by NLOGARGS words for the arguments
- to the format string, aligned on the first word boundary following the
- format string.
+ The data part of the message contains the expanded text of the format
+ string (null terminated).
A process may also send a message of the same structure to log, even if
@@ -132,9 +105,7 @@
structure in the control part of the message that are accepted are the
level, flags, and pri fields; all other fields are filled in by log be-
fore being forwarded to the appropriate logger. The data portion must
- contain a null terminated format string, and any arguments (up to NLOG-
- ARGS) must be packed, 32-bits each, on the next 32-bit boundary follow-
- ing the end of the format string.
+ contain a null terminated string.
ENXIO is returned for I_TRCLOG ioctls without any trace_ids structures,
@@ -151,7 +122,8 @@
log.conf file.
msgid=1 If msgid=1, each message will be preceded by a message ID as
- described in syslogd(8).
+ described in syslogd(8). This is the default if the property
+ is not set in the log.conf file.
msgid=0 If msgid=0, message IDs will not be generated. This property
@@ -219,10 +189,10 @@
SEE ALSO
- getmsg(2), ioctl(2), putmsg(2), write(2), printf(3C), Intro(3),
- strace(8), strerr(8), strlog(9F)
+ getmsg(2), ioctl(2), putmsg(2), write(2), printf(3C), Intro(3), ms-
+ gid(8), strace(8), strerr(8), cmn_err(9F), strlog(9F)
STREAMS Programming Guide
-Oracle Solaris 11.4 08 Aug 2018 log(4D)
+Oracle Solaris 11.4 15 Mar 2024 log(4D)
diff -NurbBw 11.4.66/man4d/mcxe.4d 11.4.69/man4d/mcxe.4d
--- 11.4.66/man4d/mcxe.4d 2024-05-25 09:57:49.239433988 -0700
+++ 11.4.69/man4d/mcxe.4d 2024-05-25 09:58:12.530548285 -0700
@@ -112,4 +112,4 @@
STREAMS Programming Guide
-Oracle Solaris 11.4 8 Oct 2012 mcxe(4D)
+Oracle Solaris 11.4 15 Mar 2024 mcxe(4D)
diff -NurbBw 11.4.66/man4d/md.4d 11.4.69/man4d/md.4d
--- 11.4.66/man4d/md.4d 2024-05-25 09:57:49.276616269 -0700
+++ 11.4.69/man4d/md.4d 2024-05-25 09:58:12.570923963 -0700
@@ -6,8 +6,10 @@
DESCRIPTION
md is a user configurable pseudo device driver that provides disk con-
catenation, striping, mirroring, RAID5 metadevices, trans metadevices,
- and hot spare utilities. Trans devices are no longer supported and have
- been replaced by UFS logging. See mount_ufs(8).
+ and hot spare utilities for UFS filesystems. Trans devices are no
+ longer supported and have been replaced by UFS logging. See
+ mount_ufs(8). Most other uses of md have been superseded by ZFS storage
+ pools.
The block devices access the disk using the system's normal buffering
@@ -124,13 +119,12 @@
-
-
An I/O or open error has occurred on a device within a mirror causing a
component in the mirror to change to the Maintenance state.
+ md: dnum: dev(num,num) last erred
+ md: dnum: dev last erred
- md: dnum: dev(num,num) last erred md: dnum: dev last erred
An I/O or open error has occurred on a device within a mirror and the
@@ -144,16 +138,13 @@
-
-
This error message comes when there are not enough usable replicas for
the state database to be able to update records in the database. All
accesses to the metadevice driver will fail. To fix this problem, more
replicas need to be added or inaccessible replicas need to be deleted.
- md: dnum: read error on devmd: dnum: write error on dev
-
-
+ md: dnum: read error on dev
+ md: dnum: write error on dev
@@ -161,10 +152,8 @@
specified device name. This happens if any read or write errors occur
on a submirror.
- md: dnum: read error on dev(num,num)md: dnum: write error on dev(
- num,num)
-
-
+ md: dnum: read error on dev(num,num)
+ md: dnum: write error on dev(num,num)
@@ -266,6 +245,20 @@
/kernel/misc/md_raid RAID5 driver misc module
+ATTRIBUTES
+ See attributes(7) for a description of the following attributes:
+
+ +------------------------------+-----------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------+
+ | Architecture |SPARC, x86 |
+ +------------------------------+-----------------------------+
+ | Availability |storage/svm |
+ +------------------------------+-----------------------------+
+ | Interface Stability |Obsolete |
+ +------------------------------+-----------------------------+
+
+
SEE ALSO
md.cf(5), md.tab(5), attributes(7), metarecover(8), mdmonitord(8),
metaclear(8), metadb(8), metadetach(8), metahs(8), metainit(8), metaof-
@@ -274,7 +267,8 @@
NOTES
Trans metadevices have been replaced by UFS logging. Existing trans de-
- vices are not logging--they pass data directly through to the underly-
- ing device. See mount_ufs(8) for more information about UFS logging.
+ vices are not logging -- they pass data directly through to the under-
+ lying device. See mount_ufs(8) for more information about UFS logging.
+ Most other uses of md have been superseded by ZFS storage pools.
-Oracle Solaris 11.4 27 Nov 2017 md(4D)
+Oracle Solaris 11.4 15 Mar 2024 md(4D)
diff -NurbBw 11.4.66/man4d/mlxne.4d 11.4.69/man4d/mlxne.4d
--- 11.4.66/man4d/mlxne.4d 2024-05-25 09:57:49.310503588 -0700
+++ 11.4.69/man4d/mlxne.4d 2024-05-25 09:58:12.606405292 -0700
@@ -105,4 +102,14 @@
https://standards.ieee.org/standard/802_3ae-2002.html
-Oracle Solaris 11.4 18 Oct 2018 mlxne(4D)
+HISTORY
+ The mlxne driver was added to Solaris in the Oracle Solaris 11.4.21 re-
+ lease with support for CX-5 devices.
+
+
+ Support for CX-6 devices was added in Oracle Solaris 11.4.51.
+
+
+ Support for CX-7 devices was added in Oracle Solaris 11.4.57.
+
+Oracle Solaris 11.4 15 Mar 2024 mlxne(4D)
diff -NurbBw 11.4.66/man4d/mpt_sas.4d 11.4.69/man4d/mpt_sas.4d
--- 11.4.66/man4d/mpt_sas.4d 2024-05-25 09:57:49.343972017 -0700
+++ 11.4.69/man4d/mpt_sas.4d 2024-05-25 09:58:12.637226658 -0700
@@ -51,22 +47,19 @@
line:
-
-
name="mpt_sas" parent="/pci@0,0/pci8086,2940@1c/pci1000,72@0"
mpxio-disable="yes";
FILES
- /kernel/drv/sparcv9/mpt_sas
-
- 64-bit SPARC ELF kernel module
-
-
/kernel/drv/amd64/mpt_sas
64-bit x86 ELF kernel module
+ /kernel/drv/sparcv9/mpt_sas
+
+ 64-bit SPARC ELF kernel module
+
/kernel/drv/mpt_sas.conf
@@ -81,6 +74,8 @@
+------------------------------+-----------------------------+
| Architecture |SPARC, x86 |
+------------------------------+-----------------------------+
+ | Availability |driver/storage/mpt_sas |
+ +------------------------------+-----------------------------+
SEE ALSO
@@ -89,4 +84,4 @@
scsi_reset(9F), scsi_sync_pkt(9F), scsi_transport(9F), scsi_device(9S),
scsi_extended_sense(9S), scsi_inquiry(9S), scsi_pkt(9S),
-Oracle Solaris 11.4 5 Jan 2012 mpt_sas(4D)
+Oracle Solaris 11.4 15 Mar 2024 mpt_sas(4D)
diff -NurbBw 11.4.66/man4d/mpt.4d 11.4.69/man4d/mpt.4d
--- 11.4.66/man4d/mpt.4d 2024-05-25 09:57:49.382291890 -0700
+++ 11.4.69/man4d/mpt.4d 2024-05-25 09:58:12.677296957 -0700
@@ -8,7 +8,7 @@
DESCRIPTION
The mpt host bus adapter driver is a SCSA compliant nexus driver that
- supports the LSI 53C1030 SCSI, SAS1064, SAS1068 and Dell SAS 6i/R con-
+ supports the LSI 53C1030 SCSI, SAS1064, SAS1068, and Dell SAS 6i/R con-
trollers.
@@ -17,7 +17,7 @@
SCSI/Ultra SCSI 2/Ultra SCSI 3/Ultra SCSI 4, and auto request sense.
The mpt driver does not support linked commands. The mpt driver also
supports SATA and Serial-Attached SCSI devices when connected to LSI
- SAS1064 (PCI-X), SAS1068 and Dell SAS 6i/R (PCI-Express) controllers.
+ SAS1064 (PCI-X), SAS1068, and Dell SAS 6i/R (PCI-Express) controllers.
DRIVER CONFIGURATION
The mpt driver obtains configuration parameters from the /ker-
@@ -64,7 +64,8 @@
following example shows how to disable multipathing on a controller
whose parent is /pci@7c0/pci@0/pci@9 and unit-address is 0:
- name="mpt" parent="/pci@7c0/pci@0/pci@9" unit-address="0" mpxio-disable="yes";
+ name="mpt" parent="/pci@7c0/pci@0/pci@9" unit-address="0"
+ mpxio-disable="yes";
@@ -98,6 +99,33 @@
3435 < n: Maximum, 3435 seconds
+ SCSI Transport Capabilities
+ SCSI transport capabilities as set by the target driver. The following
+ capabilities can be queried and modified by the target driver: synchro-
+ nous, tagged-qing, wide-xfer, auto-rqsense, qfull-retries, and qfull-
+ retry-interval. All other capabilities are query only.
+
+
+ By default, tagged-qing, auto-rqsense, and wide-xfer capabilities are
+ disabled, while disconnect, synchronous, and untagged-qing are enabled.
+ These capabilities can only have binary values (0 or 1). The default
+ value for qfull-retries is 10, while the default value for qfull-retry-
+ interval is 100. The qfull-retries capability is a uchar_t (0 to 255),
+ while qfull-retry-interval is a ushort_t (0 to 65535).
+
+
+ The target driver must enable tagged-qing and wide-xfer explicitly. The
+ untagged-qing capability is always enabled and its value cannot be mod-
+ ified.
+
+
+ If a conflict exists between the value of scsi-options and a capabil-
+ ity, the value set in scsi-options prevails. Only whom != 0 is sup-
+ ported in the scsi_ifsetcap(9F) call.
+
+
+ Refer to scsi_ifsetcap(9F) and scsi_ifgetcap(9F) for details.
+
EXAMPLES
Example 1 Using the mpt Configuration File
@@ -186,39 +212,11 @@
You must reboot the system for the specified scsi-options to take ef-
fect.
-
- SCSI Transport Capabilities
- SCSI transport capabilities as set by the target driver. The following
- capabilities can be queried and modified by the target driver: synchro-
- nous, tagged-qing, wide-xfer, auto-rqsense, qfull-retries, and qfull-
- retry-interval. All other capabilities are query only.
-
-
- By default, tagged-qing, auto-rqsense, and wide-xfer capabilities are
- disabled, while disconnect, synchronous, and untagged-qing are enabled.
- These capabilities can only have binary values (0 or 1). The default
- value for qfull-retries is 10, while the default value for qfull-retry-
- interval is 100. The qfull-retries capability is a uchar_t (0 to 255),
- while qfull-retry-interval is a ushort_t (0 to 65535).
-
-
- The target driver must enable tagged-qing and wide-xfer explicitly. The
- untagged-qing capability is always enabled and its value cannot be mod-
- ified.
-
-
- If a conflict exists between the value of scsi-options and a capabil-
- ity, the value set in scsi-options prevails. Only whom != 0 is sup-
- ported in the scsi_ifsetcap(9F) call.
-
-
- Refer to scsi_ifsetcap(9F) and scsi_ifgetcap(9F) for details.
-
FILES
- /kernel/drv/sparcv9/mpt 64-bit SPARC ELF kernel module
+ /kernel/drv/amd64/mpt 64-bit x86 ELF kernel module
- /kernel/drv/amd64/mpt 64-bit x86 ELF kernel module
+ /kernel/drv/sparcv9/mpt 64-bit SPARC ELF kernel module
/kernel/drv/mpt.conf Optional configuration file
@@ -230,9 +228,9 @@
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
- | Architecture |x86, SPARC (Limited to sys- |
- | |tems with LSI Fusion family |
- | |SCSI I/O processors). |
+ | Architecture |SPARC, x86 |
+ +------------------------------+-----------------------------+
+ | Availability |driver/storage/mpt |
+------------------------------+-----------------------------+
@@ -273,7 +271,7 @@
Device is using a hilevel intr
The device was configured with an interrupt level that cannot be
- used with this mtp driver. Check the PCI device.
+ used with this mpt driver. Check the PCI device.
Map setup failed
@@ -323,7 +321,7 @@
NOTES
The mpt driver supports the parallel SCSI LSI 53c1030 controller. The
- LSI 53c1030 controller series supports Wide, Fast and Ultra SCSI 4
+ LSI 53c1030 controller series supports Wide, Fast, and Ultra SCSI 4
mode. The maximum LVD SCSI bandwidth is 320 MB/sec.
@@ -374,4 +370,4 @@
value=00000bb8
-Oracle Solaris 11.4 27 Nov 2017 mpt(4D)
+Oracle Solaris 11.4 15 Mar 2024 mpt(4D)
diff -NurbBw 11.4.66/man4d/mr_sas.4d 11.4.69/man4d/mr_sas.4d
--- 11.4.66/man4d/mr_sas.4d 2024-05-25 09:57:49.417828548 -0700
+++ 11.4.69/man4d/mr_sas.4d 2024-05-25 09:58:12.714222032 -0700
@@ -6,10 +6,10 @@
DESCRIPTION
The mr_sas LSI MegaRAID SAS2.0/SAS3.0 controller host bus adapter dri-
ver is a SCSA-compliant nexus driver that supports the LSI
- SAS3108-based series of MegaRAID controllers, LSI SAS2208-based series
- of controllers running MegaRAID firmware, the LSI SAS2108-based series
- of MegaRAID controllers, and the Sun StorageTek 6Gb/s SAS RAID HBA se-
- ries of controllers.
+ SAS3108-based series of MegaRAID controllers, the LSI SAS2208-based se-
+ ries of controllers running MegaRAID firmware, the LSI SAS2108-based
+ series of MegaRAID controllers, and the Sun StorageTek 6Gb/s SAS RAID
+ HBA series of controllers.
Some of the RAID Features include the following:
@@ -60,7 +60,7 @@
parameter, for MSI or MSI-X support. Configure your hardware through
the related BIOS utility or the MegaCli Configuration Utility. If you
want to install to a drive attached to a mr_sas HBA, create the virtual
- drive first from the BIOS (X86) before running Solaris install. The
+ drive first from the BIOS (x86) before running Solaris install. The
MegaCli utility can be downloaded from the LSI website.
@@ -71,8 +71,7 @@
into the same virtual disk.
FILES
- /kernel/drv/amd64/mr_sas 64-bit kernel module x86 ELF kernel mod-
- ule
+ /kernel/drv/amd64/mr_sas 64-bit x86 ELF kernel module
/kernel/drv/sparcv9/mr_sas 64-bit SPARC ELF kernel module
@@ -109,4 +108,4 @@
The mr_sas driver only supports internal and external expanders that
are not fully SAS1.0 or fully SAS2.0 compliant.
-Oracle Solaris 11.4 05 May 2016 mr_sas(4D)
+Oracle Solaris 11.4 15 Mar 2024 mr_sas(4D)
diff -NurbBw 11.4.66/man4d/nge.4d 11.4.69/man4d/nge.4d
--- 11.4.66/man4d/nge.4d 2024-05-25 09:57:49.456678805 -0700
+++ 11.4.69/man4d/nge.4d 2024-05-25 09:58:12.754753554 -0700
@@ -45,7 +45,7 @@
You must send an explicit DL_ATTACH_REQ message to associate the opened
stream with a particular device (PPA). The PPA ID is interpreted as an
unsigned integer data type and indicates the corresponding device in-
- stance (unit) number. The driver returns an error (DL_ERROR_ACK) if the
+ stance (unit) number. The driver returns an DL_ERROR_ACK error if the
PPA field value does not correspond to a valid device instance number
for the system. The device is initialized on first attach and de-ini-
tialized (stopped) at last detach.
@@ -130,10 +130,8 @@
- For example, to prevent the device 'nge2' from advertising gigabit ca-
- pabilities, enter (as super-user):
-
-
+ For example, to prevent the device nge2 from advertising gigabit capa-
+ bilities, enter (as super-user):
# dladm set-linkprop -p en_1000fdx_cap=0 nge2
@@ -146,7 +144,7 @@
You can obtain the current parameters settings using dladm show-
linkprop. In addition, the driver exports the current state, speed, du-
- plex setting and working mode of the link via kstat parameters (which
+ plex setting, and working mode of the link via kstat parameters (which
are read only and can not be changed). For example, to check link state
of device nge0:
@@ -167,24 +163,27 @@
-
-
The output above indicates that the link is up and running at 100Mbps
full-duplex with its rx/tx direction pause capability. In addition, the
driver exports its working mode by loop_mode. If it is set to 0, the
loopback mode is disabled.
- Only MCP55/CK804 chipsets accept the Maximum MTU upper to 9000 bytes.
- Use default_mtu to set in /kernel/drv/nge.conf file, then reboot to
- make it available. The default MTU value is 1500. For MCP55/CK804
- chipsets, nge provides one option of minimal memory usage. Use minimal-
- memory-usage = 1 in the /kernel/drv/nge.conf file, then reboot to make
- it available. With this option, the nge driver can reduce memory usage
- by two thirds. Setting minimal-memory-usage = 1 does not take effect if
- MTU is increased above the default value. To avoid problems, do not set
- the minimal-memory-usage and default_mtu options together in the
- nge.conf file.
+ The default MTU value is 1500. For the MCP55/CK804 chipsets only, the
+ MTU can be a value up to 9000 bytes. To alter the MTU, set default_mtu
+ in the /kernel/drv/nge.conf file.
+
+
+ The MCP55/CK804 chipsets can be configured for minimal memory usage.
+ Set minimal-memory-usage = 1 in the /kernel/drv/nge.conf file. With
+ this option, the nge driver can reduce memory usage by two thirds. Set-
+ ting minimal-memory-usage = 1 does not take effect if the MTU has been
+ increased above the default value.
+
+
+ The system must be rebooted for changes to nge.conf to take effect.
+ Only one of the minimal-memory-usage and default_mtu options should be
+ specified in nge.conf.
FILES
/dev/nge nge special character device.
@@ -204,6 +203,8 @@
+------------------------------+-----------------------------+
| Architecture |x86 |
+------------------------------+-----------------------------+
+ | Availability |driver/network/ethernet/nge |
+ +------------------------------+-----------------------------+
SEE ALSO
@@ -215,4 +216,4 @@
STREAMS Programming Guide
-Oracle Solaris 11.4 5 Jan 2012 nge(4D)
+Oracle Solaris 11.4 15 Mar 2024 nge(4D)
diff -NurbBw 11.4.66/man4d/null.4d 11.4.69/man4d/null.4d
--- 11.4.66/man4d/null.4d 2024-05-25 09:57:49.488694698 -0700
+++ 11.4.69/man4d/null.4d 2024-05-25 09:58:12.789591154 -0700
@@ -17,13 +17,13 @@
equal to the length of the mapping, and rounded up to the nearest page
size as returned by sysconf(3C). No resources are consumed by the
reservation. Mappings can be placed in the resulting address range via
- subsequent calls to mmap with the -MAP_FIXED option set.
+ subsequent calls to mmap with the MAP_FIXED option set.
FILES
/dev/null
SEE ALSO
- mmap(2), sysconf(3C)
+ mmap(2), sysconf(3C), full(4D), zero(4D)
-Oracle Solaris 11.4 4 April 2001 null(4D)
+Oracle Solaris 11.4 15 Mar 2024 null(4D)
diff -NurbBw 11.4.66/man4d/nxge.4d 11.4.69/man4d/nxge.4d
--- 11.4.66/man4d/nxge.4d 2024-05-25 09:57:49.522995663 -0700
+++ 11.4.69/man4d/nxge.4d 2024-05-25 09:58:12.826264661 -0700
@@ -10,7 +10,7 @@
The nxge Gigabit Ethernet driver is a multi-threaded, loadable, clon-
able, GLD-based STREAMS driver supporting the Data Link Provider Inter-
face, dlpi(4P), on Sun Gigabit Ethernet hardware (NIU, Sun x8, Express
- Dual 10 Gigabit Ethernet fiber XFP low profile adapter and the
+ Dual 10 Gigabit Ethernet fiber XFP low profile adapter, and the
10/100/1000BASE-T x8 Express low profile adapter).
@@ -49,7 +49,7 @@
You must send an explicit DL_ATTACH_REQ message to associate the opened
stream with a particular device (PPA). The PPA ID is interpreted as an
unsigned integer data type and indicates the corresponding device in-
- stance (unit) number. The driver returns an error (DL_ERROR_ACK) if the
+ stance (unit) number. The driver returns a DL_ERROR_ACK error if the
PPA field value does not correspond to a valid device instance number
for the system. The device is initialized on first attach and de-ini-
tialized (stopped) at last detach.
@@ -134,10 +134,10 @@
/dev/nxge* Special character device.
- /kernel/drv/sparcv9/nxge 64-bit device driver (SPARC).
+ /kernel/drv/amd64/nxge 64-bit device driver (x86).
- /kernel/drv/amd64/nxge 64-bit device driver (x86).
+ /kernel/drv/sparcv9/nxge 64-bit device driver (SPARC).
/kernel/drv/nxge.conf Configuration file.
@@ -151,6 +151,8 @@
+------------------------------+-----------------------------+
| Architecture |SPARC, x86 |
+------------------------------+-----------------------------+
+ | Availability |driver/network/ethernet/nxge |
+ +------------------------------+-----------------------------+
SEE ALSO
@@ -168,4 +170,4 @@
https://standards.ieee.org/standard/802_3ae-2002.html
-Oracle Solaris 11.4 5 Jan 2012 nxge(4D)
+Oracle Solaris 11.4 15 Mar 2024 nxge(4D)
diff -NurbBw 11.4.66/man4d/openprom.4d 11.4.69/man4d/openprom.4d
--- 11.4.66/man4d/openprom.4d 2024-05-25 09:57:49.560347406 -0700
+++ 11.4.69/man4d/openprom.4d 2024-05-25 09:58:12.868485690 -0700
@@ -227,8 +232,9 @@
perror("OPROMGETPROPLEN");
/* exit(1); */
proplen = 0; /* down-rev driver? */
- } else
+ } else {
proplen = opp->oprom_len;
+ }
opp_free(opp);
if (proplen == -1) {
printf("'name' property does not exist!\n");
@@ -250,9 +256,10 @@
perror("OPROMGETPROP");
exit(1);
}
- if (opp->oprom_size != 0)
+ if (opp->oprom_size != 0) {
printf("Platform name <%s> property len <%d>\n",
opp->oprom_array, proplen);
+ }
opp_free(opp);
/*
* Allocate an openpromio structure assumed to be
@@ -301,4 +308,4 @@
data, if the user buffer is allocated at least one byte larger than the
property length.
-Oracle Solaris 11.4 25 Mar 2020 openprom(4D)
+Oracle Solaris 11.4 15 Mar 2024 openprom(4D)
diff -NurbBw 11.4.66/man4d/poll.4d 11.4.69/man4d/poll.4d
--- 11.4.66/man4d/poll.4d 2024-05-25 09:57:49.597423526 -0700
+++ 11.4.69/man4d/poll.4d 2024-05-25 09:58:12.906403809 -0700
@@ -34,7 +35,7 @@
- The /dev/poll device, associated driver and corresponding manpages
+ The /dev/poll device, associated driver, and corresponding manpages
may be removed in a future Solaris release. For similar functionality
in the event ports framework, see port_create(3C).
@@ -61,20 +62,19 @@
-
-
The fd field specifies the file descriptor being polled. The events
- field indicates the interested poll events on the file descriptor. If
- a pollfd array contains multiple pollfd entries with the same fd field,
- the "events" field in each pollfd entry is OR'ed. A special POLLREMOVE
+ field indicates the requested poll events on the file descriptor. If a
+ pollfd array contains multiple pollfd entries with the same fd field,
+ the events field in each pollfd entry is OR'ed. A special POLLREMOVE
event in the events field of the pollfd structure removes the fd from
- the monitored set. The revents field is not used. Write returns the
- number of bytes written successfully or -1 when write fails.
+ the monitored set. The revents field is not used. write() returns the
+ number of bytes written successfully or -1 when write() fails.
- The DP_POLL ioctl is used to retrieve returned poll events occurred on
- the polled file descriptors in the monitored set represented by fd. arg
- is a pointer to the devpoll structures which are defined as follows:
+ The DP_POLL ioctl is used to retrieve returned poll events which oc-
+ curred on the polled file descriptors in the monitored set represented
+ by fd. arg is a pointer to the devpoll structures which are defined as
+ follows:
struct dvpoll {
struct pollfd* dp_fds;
@@ -112,21 +110,23 @@
ioctl returns 1 if the file descriptor is in the set. The events field
contains 0. The revents field contains the currently polled events. The
ioctl returns 0 if the file descriptor is not in the set. The pollfd
- structure pointed by pfd is not modified. The ioctl returns a -1 if the
- call fails.
+ structure pointed to by pfd is not modified. The ioctl returns a -1 if
+ the call fails.
EXAMPLES
The following example shows how /dev/poll may be used.
{
+ struct pollfd *pollfd;
...
/*
* open the driver
*/
- if ((wfd = open("/dev/poll", O_RDWR)) < 0) {
+ wfd = open("/dev/poll", O_RDWR | O_CLOEXEC | O_CLOFORK);
+ if (wfd < 0) {
exit(-1);
}
- pollfd = (struct pollfd* )malloc(sizeof(struct pollfd) * MAXBUF);
+ pollfd = calloc(sizeof(struct pollfd), MAXBUF);
if (pollfd == NULL) {
close(wfd);
exit(-1);
@@ -233,7 +231,7 @@
}
loopcnt++;
}
-
+ }
ERRORS
@@ -254,7 +252,7 @@
field of the dvpoll struct pointed by arg is not valid (for
example, when using write/pwrite dp_nfds is greater than
{OPEN_MAX}, or when using the DPPOLL ioctl dp_nfds is greater
- than or equal to {OPEN_MAX}}.
+ than or equal to {OPEN_MAX}.
ENXIO The O_NONBLOCK flag is set, the named file is a FIFO, the
@@ -287,7 +285,7 @@
The /dev/poll API is particularly beneficial to applications that poll
a large number of file descriptors repeatedly. Applications will ex-
hibit the best performance gain if the polled file descriptor list
- rarely change.
+ rarely changes.
When using the /dev/poll driver, you should remove a closed file de-
@@ -296,8 +294,8 @@
file descriptor is closed but not removed from the monitored set, and
is reused in subsequent open of a different device, you will be polling
the device associated with the reused file descriptor. In a multi-
- threaded application, careful coordination among threads doing close
- and DP_POLL ioctl is recommended for consistent results.
+ threaded application, careful coordination among threads doing close()
+ and DP_POLL ioctl() is recommended for consistent results.
The /dev/poll driver caches a list of polled file descriptors, which
@@ -305,13 +303,13 @@
a process will be inherited by its child process, just like any other
file descriptors. But the child process will have very limited access
through this inherited /dev/poll file descriptor. Any attempt to write
- or do ioctl by the child process will result in an EACCES error. The
+ or do ioctl() by the child process will result in an EACCES error. The
child process should close the inherited /dev/poll file descriptor and
open its own if desired.
The /dev/poll driver does not yet support polling. Polling on a
/dev/poll file descriptor will result in POLLERR being returned in the
- revents field of pollfd structure.
+ revents field of the pollfd structure.
-Oracle Solaris 11.4 29 Sept 2016 poll(4D)
+Oracle Solaris 11.4 15 Mar 2024 poll(4D)
diff -NurbBw 11.4.66/man4d/ptm.4d 11.4.69/man4d/ptm.4d
--- 11.4.66/man4d/ptm.4d 2024-05-25 09:57:49.630272769 -0700
+++ 11.4.69/man4d/ptm.4d 2024-05-25 09:58:12.941797130 -0700
@@ -49,8 +49,8 @@
with errno set to EAGAIN if there is internal flow control.
IOCTLS
- The master driver supports the ISPTM and UNLKPT ioctls that are used
- by the functions grantpt(3C), unlockpt(3C) and ptsname(3C). The ioctl
+ The master driver supports the ISPTM and UNLKPT ioctls that are used by
+ the functions grantpt(3C), unlockpt(3C), and ptsname(3C). The ioctl
ISPTM determines whether the file descriptor is that of an open master
device. On success, it returns the 0. The ioctl UNLKPT unlocks the mas-
ter and slave devices. It returns 0 on success. On failure, the errno
@@ -64,7 +64,7 @@
SEE ALSO
- ptsname(3C), unlockpt(3C), grantpt(3C), pts(4D), pckt(4M)
+ grantpt(3C), ptsname(3C), unlockpt(3C), pts(4D), pckt(4M)
STREAMS Programming Guide
@@ -72,4 +72,4 @@
Oracle Solaris 11.4 Tunable Parameters Reference Manual
-Oracle Solaris 11.4 12 June 2017 ptm(4D)
+Oracle Solaris 11.4 15 Mar 2024 ptm(4D)
diff -NurbBw 11.4.66/man4d/pty.4d 11.4.69/man4d/pty.4d
--- 11.4.66/man4d/pty.4d 2024-05-25 09:57:49.664726284 -0700
+++ 11.4.69/man4d/pty.4d 2024-05-25 09:58:12.977208127 -0700
@@ -11,13 +11,13 @@
c_cflag word of the termios structure, and the CLOCAL flag in that
word. It does not support any of the other termio(4I) device control
functions specified by flags in the c_cflag word of the termios struc-
- ture and by the IGNBRK, IGNPAR, PARMRK, or INPCK flags in the
- c_iflag word of the termios structure, as these functions apply only to
- asynchronous serial ports. All other termio(4I) functions must be per-
- formed by STREAMS modules pushed atop the driver; when a slave device
- is opened, the ldterm(4M) and ttcompat(4M) STREAMS modules are auto-
- matically pushed on top of the stream, providing the standard
- termio(4I) interface.
+ ture and by the IGNBRK, IGNPAR, PARMRK, or INPCK flags in the c_iflag
+ word of the termios structure, as these functions apply only to asyn-
+ chronous serial ports. All other termio(4I) functions must be performed
+ by STREAMS modules pushed atop the driver; when a slave device is
+ opened, the ldterm(4M) and ttcompat(4M) STREAMS modules are automati-
+ cally pushed on top of the stream, providing the standard termio(4I)
+ interface.
Instead of having a hardware interface and associated hardware that
@@ -120,8 +120,8 @@
whenever XON/XOFF flow control is enabled after being disabled;
it is considered enabled when the IXON flag in the c_iflag word
- is set, the VSTOP member of the c_cc array is ^S and the VSTART
- member of the c_cc array is ^Q.
+ is set, the VSTOP member of the c_cc array is ^S, and the VS-
+ TART member of the c_cc array is ^Q.
TIOCPKT_NOSTOP
@@ -158,9 +158,9 @@
#include <fcntl.h>
#include <sys/termios.h>
- int fdm fds;
- fdm = open("/dev/ptyp0, O_RDWR); /* open master */
- fds = open("/dev/ttyp0, O_RDWR); /* open slave */
+ int fdm, fds;
+ fdm = open("/dev/ptyp0", O_RDWR); /* open master */
+ fds = open("/dev/ttyp0", O_RDWR); /* open slave */
FILES
@@ -171,10 +171,10 @@
SEE ALSO
- rlogin(1), termio(4I), ldterm(4M), ttcompat(4M), rlogind(8),
+ grantpt(3C), openpty(3C), termio(4I), ldterm(4M), ttcompat(4M)
NOTES
- It is apparently not possible to send an EOT by writing zero bytes in
- TIOCREMOTE mode.
+ It is not possible to send an EOT by writing zero bytes in TIOCREMOTE
+ mode.
-Oracle Solaris 11.4 8 Aug 1994 pty(4D)
+Oracle Solaris 11.4 15 Mar 2024 pty(4D)
diff -NurbBw 11.4.66/man4d/qede.4d 11.4.69/man4d/qede.4d
--- 11.4.66/man4d/qede.4d 2024-05-25 09:57:49.703096893 -0700
+++ 11.4.69/man4d/qede.4d 2024-05-25 09:58:13.014061225 -0700
@@ -152,4 +152,8 @@
STREAMS Programming Guide
-Oracle Solaris 11.4 11 May 2021 qede(4D)
+HISTORY
+ The qede driver was added to Solaris in the Oracle Solaris 11.4.9 re-
+ lease.
+
+Oracle Solaris 11.4 15 Mar 2024 qede(4D)
diff -NurbBw 11.4.66/man4d/ramdisk.4d 11.4.69/man4d/ramdisk.4d
--- 11.4.66/man4d/ramdisk.4d 2024-05-25 09:57:49.736268881 -0700
+++ 11.4.69/man4d/ramdisk.4d 2024-05-25 09:58:13.047743073 -0700
@@ -64,6 +64,11 @@
Raw device for ramdisk name diskname
+ /kernel/drv/amd64/ramdisk
+
+ x86 kernel module
+
+
/kernel/drv/ramdisk.conf
Driver configuration file. (Do not alter).
@@ -71,7 +76,7 @@
/kernel/drv/sparcv9/ramdisk
- 64-bit driver
+ SPARC kernel module
ATTRIBUTES
@@ -80,6 +85,10 @@
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
+ | Architecture |SPARC, x86 |
+ +------------------------------+-----------------------------+
+ | Availability |system/kernel |
+ +------------------------------+-----------------------------+
| Interface Stability |Committed |
+------------------------------+-----------------------------+
@@ -99,4 +108,4 @@
A ramdisk may not be the best possible use of system memory. Accord-
ingly, use ramdisks only when absolutely necessary.
-Oracle Solaris 11.4 5 Jan 2012 ramdisk(4D)
+Oracle Solaris 11.4 15 Mar 2024 ramdisk(4D)
diff -NurbBw 11.4.66/man4d/rge.4d 11.4.69/man4d/rge.4d
--- 11.4.66/man4d/rge.4d 2024-05-25 09:57:49.771415646 -0700
+++ 11.4.69/man4d/rge.4d 2024-05-25 09:58:13.084199634 -0700
@@ -13,7 +13,7 @@
Adapter.
- The rge driver functions includes controller initialization, frame
+ The rge driver functions include controller initialization, frame
transmit and receive, promiscuous and multicast support, and error re-
covery and reporting.
@@ -28,7 +28,7 @@
The values returned by the driver in the DL_INFO_ACK primitive in re-
- sponse to the DL_INFO_REQ are as follows:
+ sponse to the DDL_INFO_REQ are as follows:
o Maximum SDU (with jumbo frame) is 7000.
@@ -137,6 +133,8 @@
+------------------------------+-----------------------------+
| Architecture |SPARC, x86 |
+------------------------------+-----------------------------+
+ | Availability |driver/network/ethernet/rge |
+ +------------------------------+-----------------------------+
SEE ALSO
@@ -148,4 +146,4 @@
STREAMS Programming Guide
-Oracle Solaris 11.4 11 May 2021 rge(4D)
+Oracle Solaris 11.4 15 Mar 2024 rge(4D)
diff -NurbBw 11.4.66/man4d/sad.4d 11.4.69/man4d/sad.4d
--- 11.4.66/man4d/sad.4d 2024-05-25 09:57:49.805476646 -0700
+++ 11.4.69/man4d/sad.4d 2024-05-25 09:58:13.119530294 -0700
@@ -185,4 +179,4 @@
Unless otherwise specified, the return value from ioctl() is 0 upon
success and -1 upon failure with errno set as indicated.
-Oracle Solaris 11.4 11 May 2021 sad(4D)
+Oracle Solaris 11.4 15 Mar 2024 sad(4D)
diff -NurbBw 11.4.66/man4d/scsa2usb.4d 11.4.69/man4d/scsa2usb.4d
--- 11.4.66/man4d/scsa2usb.4d 2024-05-25 09:57:49.843981156 -0700
+++ 11.4.69/man4d/scsa2usb.4d 2024-05-25 09:58:13.156638445 -0700
@@ -49,7 +49,7 @@
Revision 11a, T10/1236-D Revision 20 or T10/1416-D Revision 23 for more
information. However, for backward compatibility, all USB disk storage
devices can still be managed by rmformat(1). With or without a volume
- manager, you can mount, eject, hot remove and hot insert a 1394 mass
+ manager, you can mount, eject, hot remove, and hot insert a USB mass
storage device as the following sections explain.
@@ -367,4 +366,4 @@
This driver also supports CBI devices that do not use USB interrupt
pipe for status completion.
-Oracle Solaris 11.4 14 Jun 2023 scsa2usb(4D)
+Oracle Solaris 11.4 15 Mar 2024 scsa2usb(4D)
diff -NurbBw 11.4.66/man4d/scsi_vhci.4d 11.4.69/man4d/scsi_vhci.4d
--- 11.4.66/man4d/scsi_vhci.4d 2024-05-25 09:57:49.879188701 -0700
+++ 11.4.69/man4d/scsi_vhci.4d 2024-05-25 09:58:13.193469106 -0700
@@ -81,7 +79,7 @@
cific failover module (or to indicate that a device should not be under
scsi_vhci multipathing control by way of NONE). In scsi_vhci.conf, the
property 'scsi-vhci-failover-override' defines overrides in
- scsi_get_device_type_string(9F) form. To add a third-party (non-Sun)
+ scsi_get_device_type_string(9F) form. To add a third-party (non-Oracle)
symmetric storage device to run under scsi_vhci (and thereby take ad-
vantage of scsi_vhci multipathing), you add the vendor ID and product
ID for the device, as those strings are returned by the SCSI Inquiry
@@ -131,14 +129,13 @@
FILES
- /kernel/drv/sparcv9/scsi_vhci
-
- 64-bit kernel module (SPARC).
+ /kernel/drv/amd64/scsi_vhci
+ 64-bit kernel module (x86).
- /kernel/drv/amd64/scsi_vhci
+ /kernel/drv/sparcv9/scsi_vhci
- 64-bit kernel module (amd64).
+ 64-bit kernel module (SPARC).
/kernel/drv/scsi_vhci.conf
@@ -152,7 +149,7 @@
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
- | Architecture |PCI-based systems |
+ | Architecture |SPARC, x86 |
+------------------------------+-----------------------------+
| Availability |system/kernel |
+------------------------------+-----------------------------+
@@ -193,4 +190,4 @@
In previous releases, Solaris I/O multipathing was also known as MPxIO
and Sun StorEdge Traffic Manager (STMS).
-Oracle Solaris 11.4 07 Nov 2016 scsi_vhci(4D)
+Oracle Solaris 11.4 15 Mar 2024 scsi_vhci(4D)
diff -NurbBw 11.4.66/man4d/sd.4d 11.4.69/man4d/sd.4d
--- 11.4.66/man4d/sd.4d 2024-05-25 09:57:49.934203989 -0700
+++ 11.4.69/man4d/sd.4d 2024-05-25 09:58:13.246549899 -0700
@@ -7,13 +7,6 @@
sd@target,lun:partition
DESCRIPTION
- To open a device without checking if the vtoc is valid, use the O_NDE-
- LAY flag. When the device is opened using O_NDELAY, the first read or
- write to the device that happens after the open results in the label
- being read if the label is not currently valid. Once read, the label
- remains valid until the last close of the device. Except for reading
- the label, O_NDELAY has no impact on the driver.
-
SPARC
The sd SCSI and SCSI/ATAPI driver supports embedded SCSI-2 and CCS-
compatible SCSI disk and CD-ROM drives, ATAPI 2.6 (SFF-8020i)-compliant
@@ -56,6 +49,14 @@
an EINVAL error. There are no alignment or length restrictions on I/O
requests to the block device.
+
+ To open a device without checking if the vtoc is valid, use the O_NDE-
+ LAY flag. When the device is opened using O_NDELAY, the first read or
+ write to the device that happens after the open results in the label
+ being read if the label is not currently valid. Once read, the label
+ remains valid until the last close of the device. Except for reading
+ the label, O_NDELAY has no impact on the driver.
+
CD-ROM DRIVE SUPPORT
A CD-ROM disk is single-sided and contains approximately 640 megabytes
of data or 74 minutes of audio. When the CD-ROM is opened, the eject
@@ -405,43 +408,59 @@
<duplet>:= "<vid+pid>" , "<tunable-list>"
+
+
and
<tunable-list>:= <tunable>[, <tunable> ]*;
<tunable> = <name> : <value>
- The <vid+pid> is the string that is returned by the target device
- on a SCSI inquiry command.
- The <tunable-list> contains one or more tunables to apply to
- all target devices with the specified <vid+pid>.
- Each <tunable> is a <name> : <value> pair. Supported
- tunable names are:
+ The <vid+pid> is the string that is returned by the target device on a
+ SCSI inquiry command.
+
+
+ The <tunable-list> contains one or more tunables to apply to all target
+ devices with the specified <vid+pid>.
+
+
+ Each <tunable> is a <name> : <value> pair. Supported tunable names are:
+
+ delay-busy
+
+ when busy, nsecs of delay before retry.
+
+
+ retries-timeout
- delay-busy: when busy, nsecs of delay before retry.
+ retries to perform on an IO timeout.
- retries-timeout: retries to perform on an IO timeout.
- disable-caching: to disable cache, set this boolean property to true.
+ disable-caching
+ to disable cache, set this boolean property to true.
rmw-type
Configure the behavior for a given device (4k native disk) dealing
- with misaligned IOs. It can be set to,
+ with misaligned IOs. It can be set to:
- 0 : Do RMW (READ MODIFY WRITE) with
- warning message.
- 1 : Do RMW without warning message.
- 2 : Do NOT do RMW and return error.
+ 0 Do RMW (READ MODIFY WRITE) with warning message.
+
+
+ 1 Do RMW without warning message.
+
+
+ 2 Do NOT do RMW and return error.
The following warning message is displayed on the console:
- Write requests are not aligned to the physical sector size (4096 bytes). Although they are handled
- through Read-Modify-Write operations, it may result in performance degradation.
+ Write requests are not aligned to the physical sector size
+ (4096 bytes). Although they are handled through Read-Modify-Write
+ operations, it may result in performance degradation.
@@ -679,6 +697,18 @@
pn Where n=0 the node corresponds to the entire disk.
+ATTRIBUTES
+ See attributes(7) for a description of the following attributes:
+
+ +------------------------------+-----------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------+
+ | Architecture |SPARC, x86 |
+ +------------------------------+-----------------------------+
+ | Availability |system/kernel |
+ +------------------------------+-----------------------------+
+
+
SEE ALSO
sar(1), close(2), ioctl(2), lseek(2), read(2), write(2), scsa2usb(4D),
ssd(4D), hsfs(4FS), pcfs(4FS), udfs(4FS), cdio(4I), dkio(4I), dri-
@@ -913,4 +943,4 @@
Once this has been done on a system, the devt_version (1 by default)
should not be changed back to 1.
-Oracle Solaris 11.4 3 Nov 2021 sd(4D)
+Oracle Solaris 11.4 15 Mar 2024 sd(4D)
diff -NurbBw 11.4.66/man4d/sda.4d 11.4.69/man4d/sda.4d
--- 11.4.66/man4d/sda.4d 2024-05-25 09:57:49.973958715 -0700
+++ 11.4.69/man4d/sda.4d 2024-05-25 09:58:13.278861325 -0700
@@ -30,7 +30,7 @@
NOTES
The sda module provides support only for SD/MMC devices that are con-
nected via a supported slot driver. Notably, slots that are on USB
- busses are normally treated as USB mass storage devices and are ser-
- viced by the scsa2usb(4D) driver.
+ buses are normally treated as USB mass storage devices and are serviced
+ by the scsa2usb(4D) driver.
-Oracle Solaris 11.4 5 Jan 2012 sda(4D)
+Oracle Solaris 11.4 15 Mar 2024 sda(4D)
diff -NurbBw 11.4.66/man4d/sdp.4d 11.4.69/man4d/sdp.4d
--- 11.4.66/man4d/sdp.4d 2024-05-25 09:57:50.009511065 -0700
+++ 11.4.69/man4d/sdp.4d 2024-05-25 09:58:13.314994390 -0700
@@ -4,9 +4,7 @@
sdp - Sockets Direct Protocol driver
SYNOPSIS
- #include <socket.h>
-
-
+ #include <sys/socket.h>
#include <netinet/in.h>
@@ -27,11 +25,11 @@
SDP supports a sockets-based SOCK_STREAM interface to application pro-
grams. It also supports graceful close (including half-closed sockets),
IP addressing (IPv4 or IPv6), the connecting/accepting connect model,
- out-of-band (OOB) data and common socket options. The SDP protocol also
- supports kernel bypass data transfers and data transfers from send-up-
- per-layer-protocol (ULP) buffers to receive ULP buffers. A SDP message
- includes a BSDH header followed by data. (A BSDH header advertises the
- amount of available buffers on the local side).
+ out-of-band (OOB) data, and common socket options. The SDP protocol
+ also supports kernel bypass data transfers and data transfers from
+ send-upper-layer-protocol (ULP) buffers to receive ULP buffers. A SDP
+ message includes a BSDH header followed by data. A BSDH header adver-
+ tises the number of available buffers on the local side.
SDP networking functionality is broken into the sdp driver and a func-
@@ -65,9 +63,9 @@
is identical to TCP. The caller may mark one byte as urgent with the
MSG_OOB flag to send(3C). This sets an urgent pointer pointing to the
byte in the SDP stream. The receiver of the stream is notified of the
- urgent data by a SIGURG signal. The SIOCATMARK ioctl(2) request returns
- a value indicating whether the stream is at the urgent mark. Because
- the system never returns data across the urgent mark in a single
+ urgent data by a SIGURG signal. The SIOCATMARK ioctl(2) request re-
+ turns a value indicating whether the stream is at the urgent mark. Be-
+ cause the system never returns data across the urgent mark in a single
read(2) call, it is possible to advance to the urgent data in a simple
loop which reads data, testing the socket with the SIOCATMARK ioctl()
request until it reaches the mark.
@@ -115,8 +113,8 @@
EACCES A bind() operation was attempted with a reserved
- port number and the effective user ID of the
- process was not the privileged user.
+ port number and the process does not have the
+ {PRIV_NET_PRIVADDR} privilege.
ENOBUFS The system ran out of memory for internal data
@@ -153,4 +151,4 @@
Infiniband Architecture Specification Vol 1- Annex 4 -- November, 2002
-Oracle Solaris 11.4 11 May 2021 sdp(4D)
+Oracle Solaris 11.4 15 Mar 2024 sdp(4D)
diff -NurbBw 11.4.66/man4d/se.4d 11.4.69/man4d/se.4d
--- 11.4.66/man4d/se.4d 2024-05-25 09:57:50.046386101 -0700
+++ 11.4.69/man4d/se.4d 2024-05-25 09:58:13.351580563 -0700
@@ -61,14 +61,14 @@
during periods of high system load.
- In async mode (obtained by opening /dev/cua/[a-z], /dev/term/[a-z] or
+ In async mode (obtained by opening /dev/cua/[a-z], /dev/term/[a-z], or
/dev/tty[a-z]), the driver supports the termio(4I) device control func-
tions specified by flags in the c_cflag word of the termios structure,
- and by the IGNBRK, IGNPAR, PARMRK, or INPCK flags in the c_iflag
- word. All other termio(4I) functions must be performed by STREAMS mod-
- ules pushed atop the driver. When a device is opened, the ldterm(4M)
- and ttcompat(4M) STREAMS modules are automatically pushed on top of
- the stream, providing the standard termio interface.
+ and by the IGNBRK, IGNPAR, PARMRK, or INPCK flags in the c_iflag word.
+ All other termio(4I) functions must be performed by STREAMS modules
+ pushed atop the driver. When a device is opened, the ldterm(4M) and
+ ttcompat(4M) STREAMS modules are automatically pushed on top of the
+ stream, providing the standard termio interface.
You can connect a single tty line to a modem for incoming and outgoing
@@ -128,11 +126,11 @@
The state of the DCD, CTS, RTS, and DTR interface signals can be
- queried through the use of the TIOCM_CAR, TIOCM_CTS, TIOCM_RTS, and
- TIOCM_DTR arguments to the TIOCMGET ioctl command, respectively. Due
- to hardware limitations, only the RTS and DTR signals may be set
- through their respective arguments to the TIOCMSET, TIOCMBIS, and TI-
- OCMBIC ioctl commands.
+ queried through the use of the TIOCM_CAR, TIOCM_CTS, TIOCM_RTS, and TI-
+ OCM_DTR arguments to the TIOCMGET ioctl command, respectively. Due to
+ hardware limitations, only the RTS and DTR signals may be set through
+ their respective arguments to the TIOCMSET, TIOCMBIS, and TIOCMBIC
+ ioctl commands.
The input and output line speeds may be set to all baud rates supported
@@ -211,6 +209,8 @@
+------------------------------+-----------------------------+
| Architecture |SPARC |
+------------------------------+-----------------------------+
+ | Availability |driver/serial/se |
+ +------------------------------+-----------------------------+
SEE ALSO
@@ -236,4 +236,4 @@
cal buffers fill up.
-Oracle Solaris 11.4 19 Feb 2019 se(4D)
+Oracle Solaris 11.4 15 Mar 2024 se(4D)
diff -NurbBw 11.4.66/man4d/sgen.4d 11.4.69/man4d/sgen.4d
--- 11.4.66/man4d/sgen.4d 2024-05-25 09:57:50.086358393 -0700
+++ 11.4.69/man4d/sgen.4d 2024-05-25 09:58:13.388391875 -0700
@@ -21,7 +21,7 @@
does not, and relies on the filesystem permissions on its device spe-
cial file to govern who may access that device. By default, access is
restricted and device nodes created by the sgen driver are readable and
- writable by the superuser exclusively.
+ writable exclusively by the superuser.
It is important to understand that SCSI devices coexisting on the same
@@ -102,63 +102,59 @@
vendorid
- is used to match the Vendor ID reported by the device. The SCSI
- specification limits Vendor IDs to eight characters. Correspond-
- ingly, the length of this string should not exceed eight charac-
- ters. As a special case, "*" may be used as a wildcard which
- matches any Vendor ID. This is useful in situations where more than
- one vendor produces a particular model of a product. vendorid is
- matched against the Vendor ID reported by the device in a case-in-
- sensitive manner.
+ The vendorid property is used to match the Vendor ID reported by
+ the device. The SCSI specification limits Vendor IDs to eight char-
+ acters. Correspondingly, the length of this string should not ex-
+ ceed eight characters. As a special case, "*" may be used as a
+ wildcard which matches any Vendor ID. This is useful in situations
+ where more than one vendor produces a particular model of a prod-
+ uct. vendorid is matched against the Vendor ID reported by the de-
+ vice in a case-insensitive manner.
productid
- is used to match the product ID reported by the device. The SCSI
- specification limits product IDs to sixteen characters (unused
- characters are filled with the whitespace characters). Correspond-
- ingly, the length of productid should not exceed sixteen charac-
- ters. When examining the product ID of the device, sgen examines
- the length l of productid and performs a match against only the
- first l characters in the device's product ID. productid is matched
- against the product ID reported by the device in a case-insensitive
- manner.
+ The productid property is used to match the product ID reported by
+ the device. The SCSI specification limits product IDs to sixteen
+ characters (unused characters are filled with the whitespace char-
+ acters). Correspondingly, the length of productid should not exceed
+ sixteen characters. When examining the product ID of the device,
+ sgen examines the length l of productid and performs a match
+ against only the first l characters in the device's product ID.
+ productid is matched against the product ID reported by the device
+ in a case-insensitive manner.
+ For example, to match some fictitious devices from ACME corp, the
+ inquiry-config-list can be configured as follows:
- For example, to match some fictitious devices from ACME corp, the in-
- quiry-config-list can be configured as follows:
-
inquiry-config-list = "ACME", "UltraToast 3000",
"ACME", "UltraToast 4000",
"ACME", "UltraToast 5000";
+ To match "UltraToast 4000" devices, regardless of vendor, inquiry-
+ config-list is modified as follows:
- To match "UltraToast 4000" devices, regardless of vendor, inquiry-con-
- fig-list is modified as follows:
-
inquiry-config-list = "*", "UltraToast 4000";
+ To match every device from ACME in the "UltraToast" series (i.e Ul-
+ traToast 3000, 4000, 5000, ...), inquiry-config-list is modified as
+ follows:
- To match every device from ACME in the "UltraToast" series (i.e Ultra-
- Toast 3000, 4000, 5000, ...), inquiry-config-list is modified as fol-
- lows:
-
- inquiry-config-list = "ACME" "UltraToast";
-
+ inquiry-config-list = "*", "UltraToast";
+
+ Whitespace characters are significant when specifying productid.
+ For example, a productid of "UltraToast 1000" is fifteen characters
+ in length. If a device reported its ID as "UltraToast 10000", the
+ sgen driver would bind to it because only the first fifteen charac-
+ ters are considered significant when matching. To remedy this situ-
+ ation, specify productid as "UltraToast 1000 ", (note trailing
+ space). This forces the sgen driver to consider all sixteen charac-
+ ters in the product ID to be significant.
- Whitespace characters are significant when specifying productid. For
- example, a productid of "UltraToast 1000" is fifteen characters in
- length. If a device reported its ID as "UltraToast 10000", the sgen
- driver would bind to it because only the first fifteen characters are
- considered significant when matching. To remedy this situation, specify
- productid as "UltraToast 1000 ", (note trailing space). This forces the
- sgen driver to consider all sixteen characters in the product ID to be
- significant.
-
device-type-config-list
The device-type-config-list property is a list of strings that enu-
@@ -196,13 +190,14 @@
this, specify type_0x<typenum> in the sgen-config-list. Case is not
significant when specifying device type names.
+
sgen-diag
The sgen-diag property sets the diagnostic output level. This prop-
erty can be set globally and/or per target/lun pair. sgen-diag is
- an integer property, and can be set to 0, 1, 2 or 3. Illegal values
- will silently default to 0. The meaning of each diagnostic level is
- as follows:
+ an integer property, and can be set to 0, 1, 2, or 3. Illegal val-
+ ues will silently default to 0. The meaning of each diagnostic
+ level is as follows:
0 No error reporting [default]
@@ -238,8 +233,8 @@
its SCSI device type. The files inside the directory are named ac-
cording to their controller number, target ID and LUN as follows:
- cn is the controller number, tn is the SCSI target id and dn is the
- SCSI LUN
+ cn is the controller number, tn is the SCSI target id, and dn is
+ the SCSI LUN.
This is analogous to the {controller;target;device} naming scheme,
and the controller numbers correspond to the same controller num-
@@ -308,6 +303,18 @@
that the parent="" property be used to specify which SCSI bus sgen
should examine.
+ATTRIBUTES
+ See attributes(7) for a description of the following attributes:
+
+ +------------------------------+-----------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------+
+ | Architecture |SPARC, x86 |
+ +------------------------------+-----------------------------+
+ | Availability |system/kernel |
+ +------------------------------+-----------------------------+
+
+
SEE ALSO
sd(4D), st(4D), uscsi(4I), driver.conf(5), scsi(5)
@@ -320,4 +327,4 @@
SCSI-3 SPC Draft Standard, Rev. 11a
-Oracle Solaris 11.4 27 Nov 2017 sgen(4D)
+Oracle Solaris 11.4 15 Mar 2024 sgen(4D)
diff -NurbBw 11.4.66/man4d/st.4d 11.4.69/man4d/st.4d
--- 11.4.66/man4d/st.4d 2024-05-25 09:57:50.144229075 -0700
+++ 11.4.69/man4d/st.4d 2024-05-25 09:58:13.442633508 -0700
@@ -20,14 +18,10 @@
-
-
x86 users can do the following to determine if the st device driver
supports a particular tape device:
-
-
- % strings /kernel/drv/st | grep -i <tape device name>
+ % strings /kernel/drv/amd64/st | grep -i <tape device name>
@@ -78,7 +70,7 @@
to provide reserve/release functionality before the command is issued.
Persistent Errors and Asynchronous Tape Operation
- The st driver now supports persistent errors (see mtio(4I) and asyn-
+ The st driver now supports persistent errors (see mtio(4I)) and asyn-
chronous tape operations (see mtio(4I), aioread(3C), and aiowrite(3C)).
Read Operation
@@ -416,18 +400,11 @@
tape ejection if ST_EJECT_TAPE_ON_CHANGER_FAILURE option is set to
0x200000:
- Sense ASC/ASCQ Description
-
- Key
-
+ Sense Key ASC/ASCQ Description
4 15/01 Mechanical Failure
-
4 44/00 Internal Target Failure
-
2 53/00 Media Load or Eject Failed
-
4 53/00 Media Load or Eject Failed
-
4 53/01 Unload Tape Failure
@@ -448,7 +426,7 @@
<number of densities> is the number of densities specified. Each tape
drive can support up to four densities. The value entered should there-
- fore be between 1 and 4; if less than 4, the remaining densities are be
+ fore be between 1 and 4; if less than 4, the remaining densities are
assigned a value of 0x0.
@@ -773,12 +741,9 @@
where d is data Protection enabled, l,m,h,u,c specifies the density
(low, medium, high, ultra/compressed), b the optional BSD behavior
- (see mtio(4I)), and n the optional no rewind behavior.
-
- where l,m,h,u,c specifies the density (low, medium, high, ul-
- tra/compressed), b the optional BSD behavior (see mtio(4I)), and n
- the optional no rewind behavior. For example, /dev/rmt/0lbn speci-
- fies unit 0, low density, BSD behavior, and no rewind.
+ (see mtio(4I)), and n the optional no rewind behavior. For example,
+ /dev/rmt/0lbn specifies unit 0, low density, BSD behavior, and no
+ rewind.
For 1/2" reel tape devices (HP-88780), the densities are:
@@ -814,6 +779,18 @@
+ATTRIBUTES
+ See attributes(7) for a description of the following attributes:
+
+ +------------------------------+-----------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------+
+ | Architecture |SPARC, x86 |
+ +------------------------------+-----------------------------+
+ | Availability |system/kernel |
+ +------------------------------+-----------------------------+
+
+
SEE ALSO
mt(1), open(2), read(2), write(2), aioread(3C), aiowrite(3C),
kstat(3KSTAT), mtio(4I), driver.conf(5), scsi(5), standards(7), mod-
@@ -854,7 +829,7 @@
sents the block where the transfer started. Error Block represents the
block that caused the error. Sense Key, ASC, ASCQ and FRU information
is returned by the target in response to a request sense command. See
- SCSI protocol documentation for description of Sense Key, ASC, ASCQ,
+ SCSI protocol documentation for descriptions of Sense Key, ASC, ASCQ,
FRU.
@@ -982,7 +953,8 @@
The operation reached the end of the tape media.
- Exabyte soft error reporting failed. DAT soft error reporting failed
+ Exabyte soft error reporting failed.
+ DAT soft error reporting failed
@@ -1138,4 +1110,4 @@
drives, for example, mistakenly report media error instead of blank
check error.
-Oracle Solaris 11.4 11 May 2021 st(4D)
+Oracle Solaris 11.4 15 Mar 2024 st(4D)
diff -NurbBw 11.4.66/man4d/sysmsg.4d 11.4.69/man4d/sysmsg.4d
--- 11.4.66/man4d/sysmsg.4d 2024-05-25 09:57:50.177782058 -0700
+++ 11.4.69/man4d/sysmsg.4d 2024-05-25 09:58:13.474937544 -0700
@@ -30,4 +30,4 @@
SEE ALSO
console(4D), attributes(7) , consadm(8), syslogd(8)
-Oracle Solaris 11.4 13 Oct 1998 sysmsg(4D)
+Oracle Solaris 11.4 15 Mar 2024 sysmsg(4D)
diff -NurbBw 11.4.66/man4d/ugen.4d 11.4.69/man4d/ugen.4d
--- 11.4.66/man4d/ugen.4d 2024-05-25 09:57:50.236562576 -0700
+++ 11.4.69/man4d/ugen.4d 2024-05-25 09:58:13.529098363 -0700
@@ -20,8 +20,8 @@
ugen supports control, bulk, isochronous and interrupt (in and out)
- transfers. libusb(3LIB) uses ugen to access devices that do not contain
- drivers (such as digital cameras and PDAs). Refer to
+ transfers. libusb(3LIB) uses ugen to access USB devices that do not
+ have a more specific driver, such as digital cameras and PDAs. Refer to
/usr/share/doc/libusb/libusb.txt for details.
BINDING
@@ -58,11 +58,9 @@
When using ugen for the first time, you must add the driver utilizing
add_drv(8), using a command of the following form:
-
-
Assuming that the vid is 472 and pid is b0b0:
- add_drv -n -m '* <device perms> <owner> <group>'
+ add_drv -n -m '* <device perms> <owner> <group>' \
-i '"usb472,b0b0"' ugen
@@ -75,9 +73,7 @@
...add the device using update_drv(8):
-
-
- update_drv -a -m '* <device perms> <owner> <group>'
+ update_drv -a -m '* <device perms> <owner> <group>' \
-i '"usb472,b0b0"' ugen
@@ -112,9 +106,7 @@
An example showing how to bind a child device representing interface 0
of configuration 1 of a composite device follows:
-
-
- update_drv -a -m '* 0666 root sys'
+ update_drv -a -m '* 0666 root sys' \
-i '"usbif472,b0b0.config1.0"' ugen
@@ -318,13 +302,10 @@
The following code reads the device status device logical name:
-
-
int fd;
int status;
- if ((fd = open("/dev/usb/472.b0b0/0/devstat",
- O_RDONLY)) < 0) {
+ if ((fd = open("/dev/usb/472.b0b0/0/devstat", O_RDONLY)) < 0) {
/* handle error */
}
@@ -377,13 +356,11 @@
uchar_t request[8];
ep1_data_fd = open ("/dev/usb/472.b0b0/0/if0out1", O_WRONLY);
-
if (ep1_data_fd < 0) {
/* Handle open error. */
}
- ep1_stat_fd = open ("/dev/usb/472.b0b0/0/if0out1stat",
- O_RDONLY);
+ ep1_stat_fd = open ("/dev/usb/472.b0b0/0/if0out1stat", O_RDONLY);
if (ep1_stat_fd < 0) {
/* Handle open error. */
}
@@ -418,7 +395,7 @@
Applications requiring I/O on a control endpoint should open the corre-
sponding logical device name and use regular UNIX I/O system calls. For
- example: read(2), write(2), aioread(3C) and aiowrite(3C). poll(2) is
+ example: read(2), write(2), aioread(3C), and aiowrite(3C). poll(2) is
not supported on control endpoints.
@@ -634,7 +601,8 @@
* boundaries. The issue is that some structures may
* be adjacent to others which have an odd-numbered
* byte size, and may thus start on an odd-numbered
- * boundary. */
+ * boundary.
+ */
bcopy(curr_descr, &cfg_descr, curr_descr_len);
/* Remember to read any words in endian-neutral way. */
@@ -676,7 +644,7 @@
INTERRUPT-IN TRANSFERS
Applications requiring data from an interrupt-IN endpoint should open
- the corresponding logical device name and use read(2), aioread(3C) and
+ the corresponding logical device name and use read(2), aioread(3C), and
poll(2) system calls.
@@ -685,13 +653,11 @@
fd = open("/dev/usb/472.b0b0/0/if0in1", O_RDONLY);
-
fdstat = open("/dev/usb/472.b0b0/0/if0in1stat", O_RDONLY);
-
- ugen starts polling interrupt--IN endpoints immediately upon opening
+ ugen starts polling interrupt-IN endpoints immediately upon opening
them and stops polling them upon closure. (Polling refers to interroga-
tion of the device by the driver and should not be confused with
poll(2), which is an interrogation of the driver by the application.)
@@ -740,8 +704,8 @@
- ugen never drop data. However, the device can drop data if the applica-
- tion cannot read it at the rate that it is produced.
+ ugen never drops data. However, the device can drop data if the appli-
+ cation cannot read it at the rate that it is produced.
Applications requiring unbuffered data from an interrupt-IN endpoint
@@ -832,7 +789,7 @@
BULK TRANSFERS
Applications requiring I/O on a bulk endpoint can open the correspond-
ing logical device name and perform regular UNIX I/O system calls. For
- example: read(2), write(2), aioread(3C) and aiowrite(3C). poll(2) is
+ example: read(2), write(2), aioread(3C), and aiowrite(3C). poll(2) is
not supported on bulk endpoints.
@@ -969,8 +920,7 @@
pktcnt = 4; /* 4 packets in this request */
- len = sizeof(int) +
- sizeof(ugen_isoc_pkt_descr_t) * pktcount;
+ len = sizeof(int) + sizeof(ugen_isoc_pkt_descr_t) * pktcount;
buf = malloc(len);
if (!buf) {
@@ -980,8 +930,7 @@
req = (ugen_isoc_req_head_t *)buf;
req->req_isoc_pkts_count = pktcnt;
- pktdesc = (ugen_isoc_pkt_descr_t *)
- (req->req_isoc_pkt_descrs);
+ pktdesc = (ugen_isoc_pkt_descr_t *) (req->req_isoc_pkt_descrs);
for (i = 0; i < pktcnt; i++) {
/*
@@ -1009,8 +958,8 @@
* length + payload data length of all pkts
* (sizeof(ugen_isoc_pkt_descr_t) + pktlen) * pktcnt
*/
- if (read(fd, rdbuf, (sizeof(ugen_isoc_pkt_descr_t) +
- pktlen) * pktcnt) < 0) {
+ if (read(fd, rdbuf,
+ (sizeof(ugen_isoc_pkt_descr_t) + pktlen) * pktcnt) < 0) {
/* Error recovery. */
}
@@ -1020,8 +969,8 @@
p = rdbuf + pktcnt * sizeof(ugen_isoc_pkt_descr_t);
for (i = 0; i < pktcnt; i++) {
- printf("packet %d len = %d,"
- " actual_len = %d, status = 0x%x\n",
+ printf(
+ "packet %d len = %d, actual_len = %d, status = 0x%x\n",
i, pktdesc->dsc_isoc_pkt_len,
pktdesc->dsc_isoc_pkt_actual_len,
pktdesc->dsc_isoc_pkt_status);
@@ -1069,8 +1017,7 @@
*/
pktlen = 1024;
- len = sizeof(int) +
- sizeof(ugen_isoc_pkt_descr_t) * pktcount;
+ len = sizeof(int) + sizeof(ugen_isoc_pkt_descr_t) * pktcount;
len += pktlen * pktcnt;
@@ -1082,8 +1029,7 @@
req = (ugen_isoc_req_head_t *)buf;
req->req_isoc_pkts_count = pktcnt;
- pktdesc =
- (ugen_isoc_pkt_descr_t *)(req->req_isoc_pkt_descrs);
+ pktdesc = (ugen_isoc_pkt_descr_t *)(req->req_isoc_pkt_descrs);
for (i = 0; i < pktcnt; i++) {
pktdesc[i].dsc_isoc_pkt_len = pktlen;
@@ -1293,45 +1235,44 @@
FILES
- /kernel/drv/ugen 32 bit ELF kernel module (x86 platform only)
- /kernel/drv/sparcv9/ugen 64 bit ELF kernel module
+ /kernel/drv/amd64/ugen 64-bit ELF kernel module (x86)
- /dev/usb/<vid>.<pid>/<N>/cntrl0
- /dev/usb/<vid>.<pid>/<N>/cntrl0stat
- /dev/usb/<vid>.<pid>/<N>/if<interface#>
- <in|out|cntrl><endpoint#>
- /dev/usb/<vid>.<pid>/<N>/if<interface#>
- <in|out|cntrl><endpoint#>stat
+ /kernel/drv/sparcv9/ugen 64-bit ELF kernel module (SPARC)
- /dev/usb/<vid>.<pid>/<N>/if<interface#>.
- <alternate><in|out|cntrl<endpoint#>
- /dev/usb/<vid>.<pid>/<N>/if<interface#>.
- <alternate><in|out|cntrl><endpoint#>stat
- /dev/usb/<vid>.<pid>/<N>/cfg<value>if<interface#>
- <in|out|cntrl><endpoint#>
- /dev/usb/<vid>.<pid>/<N>/cfg<value>if<interface#>
- <in|out|cntrl<endpoint#stat>
- /dev/usb/<vid>.<pid>/<N>/cfg<value>if<interface#>.
- <alternate><in|out|cntrl><endpoint#>
- /dev/usb/<vid>.<pid>/<N>/cfg<value>if<interface#>.
- <alternate><in|out|cntrl><endpoint#>stat
+ The following files are located in the directory
+ /dev/usb/<vid>.<pid>/<N>/, where N is an integer representing the in-
+ stance number of this type of device. (All logical device names for a
+ single device share the same N.)
+ cntrl0
+ cntrl0stat
- /dev/usb/<vid>.<pid>/<N>/devstat
- /dev/usb/<vid>.<pid>/<N>/if<interface#>cntrl0
- /dev/usb/<vid>.<pid>/<N>/if<interface#>cntrl0stat
+ if<interface#><in|out|cntrl><endpoint#>
+ if<interface#><in|out|cntrl><endpoint#>stat
+
+
+ if<interface#>.<alternate><in|out|cntrl><endpoint#>
+ if<interface#>.<alternate><in|out|cntrl><endpoint#>stat
+
+
+ cfg<value>if<interface#><in|out|cntrl><endpoint#>
+ cfg<value>if<interface#><in|out|cntrl><endpoint>#stat
+
+
+ cfg<value>if<interface#>.<alternate><in|out|cntrl><endpoint#>
+ cfg<value>if<interface#>.<alternate><in|out|cntrl><endpoint#>stat
+ devstat
+ if<interface#>cntrl0
+ if<interface#>cntrl0stat
- where N is an integer representing the instance number of this type of
- device. (All logical device names for a single device share the same
- N.)
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -1386,4 +1327,4 @@
close and reopen all open minor nodes to reinstate successful communi-
cation.
-Oracle Solaris 11.4 14 Jun 2023 ugen(4D)
+Oracle Solaris 11.4 15 Mar 2024 ugen(4D)
diff -NurbBw 11.4.66/man4d/usbftdi.4d 11.4.69/man4d/usbftdi.4d
--- 11.4.66/man4d/usbftdi.4d 2024-05-25 09:57:50.277078711 -0700
+++ 11.4.69/man4d/usbftdi.4d 2024-05-25 09:58:13.563310937 -0700
@@ -6,9 +6,10 @@
SYNOPSIS
#include <fcntl.h>
#include <sys/termio.h>
- usbftdi@unit
+ usbftdi@unit
+
DESCRIPTION
The usbftdi driver is a loadable STREAMS and USBA (Solaris USB Archi-
tecture) compliant client driver that provides basic asynchronous com-
@@ -41,7 +42,7 @@
Input and output line speeds can be set to the following baud rates:
300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 230400,
- 460800 or 921600. Input and output line speeds can not be set indepen-
+ 460800, or 921600. Input and output line speeds can not be set indepen-
dently. For example, when the output speed is set, the input speed is
automatically set to the same speed.
@@ -71,8 +72,8 @@
or by setting the value of the property to zero.
- More sophisticated selection of which devices ignore or obey the DCD
- signal can be effected using port-%d-ignore-cd properties.
+ More sophisticated selection of which devices should ignore or obey the
+ DCD signal can be effected using port-%d-ignore-cd properties.
Dial-In and Dial-Out Support
A related feature is available for traditional usage that enables a
@@ -168,7 +169,7 @@
In addition to being logged, the following messages might appear on the
system console. All messages are formatted in the following manner:
- Warning: device_path usbftdiinstance num): Error Message ...
+ Warning: device_path (usbftdiinstance number): Error Message ...
Device was disconnected while open. Data may have been lost.
@@ -205,10 +206,12 @@
The following messages might be logged into the system log. They are
formatted in the following manner:
- device_path usbftdiiinstance number): message ...
+ device_path (usbftdiinstance number): message ...
+
+ Input overrun.
- Input overrun. Data was lost.
+ Data was lost.
-Oracle Solaris 11.4 14 Jun 2023 usbftdi(4D)
+Oracle Solaris 11.4 15 Mar 2024 usbftdi(4D)
diff -NurbBw 11.4.66/man4d/usbprn.4d 11.4.69/man4d/usbprn.4d
--- 11.4.66/man4d/usbprn.4d 2024-05-25 09:57:50.315128126 -0700
+++ 11.4.69/man4d/usbprn.4d 2024-05-25 09:58:13.603058825 -0700
@@ -46,7 +44,7 @@
mode is set to centronics mode (ECPP_CENTRONICS). Parameters can be
changed through the ECPPIOC_SETPARMS ioctl and read through the ECP-
PIOC_GETPARMS ioctl. Each time the USB printer device is opened, the
- device is marked as busy and all further opens returns EBUSY. Once the
+ device is marked as busy and all further opens return EBUSY. Once the
device is open, applications can write to the device and the driver can
send data and obtain device id and status.
@@ -185,7 +183,7 @@
ver while one of the units is open.
- EINVAL An unsupported IOCTL has been received. A ECP-
+ EINVAL An unsupported IOCTL has been received. An ECP-
PIOC_SETPARMS ioctl(2) is attempted with an out of
range value in the ecpp_transfer_parms structure.
@@ -305,4 +302,4 @@
connecting the USB cable of USB Parallel Printer Adapter from the host
or hub port.
-Oracle Solaris 11.4 14 Jun 2023 usbprn(4D)
+Oracle Solaris 11.4 15 Mar 2024 usbprn(4D)
diff -NurbBw 11.4.66/man4d/virtualkm.4d 11.4.69/man4d/virtualkm.4d
--- 11.4.66/man4d/virtualkm.4d 2024-05-25 09:57:50.349186270 -0700
+++ 11.4.69/man4d/virtualkm.4d 2024-05-25 09:58:13.643426802 -0700
@@ -61,8 +58,8 @@
Under the virtualkm facility, the PS/2 mouse is coalesced into a vir-
tual mouse single input stream and can be accessed using the /dev/mouse
- file. (Note that in previous releases, the PS/2 mouse was accessed via
- the /dev/kdmouse physical device file). In the current release, you use
+ file. Note that in previous releases, the PS/2 mouse was accessed via
+ the /dev/kdmouse physical device file. In the current release, you use
the /dev/kdmouse file to directly access the physical PS/2 mouse.
INTERFACES
@@ -101,7 +98,7 @@
If, for example, the system has a single two-button USB mouse attached,
the application, by default, will graphically display the mouse with a
left and a right button. However, if a another three-button USB mouse
- is hot-plugged into the system, a MOUSE_CAP_CHANGE_NUM_BUT Firm event
+ is hot-plugged into the system, a MOUSE_CAP_CHANGE_NUM_BUT Firm_event
with Firm_event.value of three instructs the demo application to update
the mouse display to indicate three buttons.
@@ -175,7 +170,7 @@
WARNING: Error message...
- conskbd: keyboard is not available for system debugging: device_path.
+ conskbd: keyboard is not available for system debugging: <device_path>.
Errors were encountered while entering kmdb during initialization
for debugger mode. As a result, the keyboard is not available.
@@ -202,4 +197,8 @@
Currently, the virtualkm device supports only USB and PS2 keyboards and
mice.
-Oracle Solaris 11.4 11 Nov 2016 virtualkm(4D)
+HISTORY
+ The virtual keyboard and mouse support was added to Solaris in the So-
+ laris 10 1/06 (Update 1) release.
+
+Oracle Solaris 11.4 15 Mar 2024 virtualkm(4D)
diff -NurbBw 11.4.66/man4d/vtio.4d 11.4.69/man4d/vtio.4d
--- 11.4.66/man4d/vtio.4d 2024-05-25 09:57:50.380741441 -0700
+++ 11.4.69/man4d/vtio.4d 2024-05-25 09:58:13.674682296 -0700
@@ -37,4 +37,8 @@
https://docs.oasis-open.org/virtio/virtio/v1.1/virtio-v1.1.html
-Oracle Solaris 11.4 11 May 2021 vtio(4D)
+HISTORY
+ The vtio kernel module was added to Oracle Solaris in the Solaris
+ 11.4.33 release.
+
+Oracle Solaris 11.4 15 Mar 2024 vtio(4D)
diff -NurbBw 11.4.66/man4d/vtioblk.4d 11.4.69/man4d/vtioblk.4d
--- 11.4.66/man4d/vtioblk.4d 2024-05-25 09:57:50.411347213 -0700
+++ 11.4.69/man4d/vtioblk.4d 2024-05-25 09:58:13.708925981 -0700
@@ -5,7 +5,7 @@
DESCRIPTION
The vtioblk host driver is a nexus driver that supports the Virtio
- Block Device. It uses the blkdev(7D) service to expose the block de-
+ Block Device. It uses the blkdev(4D) service to expose the block de-
vices as disks.
FILES
@@ -37,4 +37,8 @@
https://docs.oasis-open.org/virtio/virtio/v1.1/virtio-v1.1.html
-Oracle Solaris 11.4 11 May 2021 vtioblk(4D)
+HISTORY
+ The vtioblk driver was added to Oracle Solaris in the Solaris 11.4.33
+ release.
+
+Oracle Solaris 11.4 15 Mar 2024 vtioblk(4D)
diff -NurbBw 11.4.66/man4d/vtioentropy.4d 11.4.69/man4d/vtioentropy.4d
--- 11.4.66/man4d/vtioentropy.4d 2024-05-25 09:57:50.442241294 -0700
+++ 11.4.69/man4d/vtioentropy.4d 2024-05-25 09:58:13.741776680 -0700
@@ -78,4 +78,8 @@
https://docs.oasis-open.org/virtio/virtio/v1.1/virtio-v1.1.html
-Oracle Solaris 11.4 11 May 2021 vtioentropy(4D)
+HISTORY
+ The vtioentropy driver was added to Oracle Solaris in the Solaris
+ 11.4.33 release.
+
+Oracle Solaris 11.4 15 Mar 2024 vtioentropy(4D)
diff -NurbBw 11.4.66/man4d/vtionet.4d 11.4.69/man4d/vtionet.4d
--- 11.4.66/man4d/vtionet.4d 2024-05-25 09:57:50.476692095 -0700
+++ 11.4.69/man4d/vtionet.4d 2024-05-25 09:58:13.775863820 -0700
@@ -33,7 +33,7 @@
You must send an explicit DL_ATTACH_REQ message to associate the opened
stream with a particular device (PPA). The PPA ID is interpreted as an
unsigned integer data type and indicates the corresponding device in-
- stance (unit) number. The driver returns an error (DL_ERROR_ACK) if the
+ stance (unit) number. The driver returns a DL_ERROR_ACK error if the
PPA field value does not correspond to a valid device instance number.
@@ -53,9 +53,9 @@
o MAC type is DL_ETHER.
- o The sap length value is -2, means that the physical address
- component is followed immediately by a 2-byte sap component
- within the DLSAP address.
+ o The sap length value is -2, meaning that the physical ad-
+ dress component is followed immediately by a 2-byte sap com-
+ ponent within the DLSAP address.
o The broadcast address value is Ethernet/IEEE broadcast ad-
@@ -116,4 +116,8 @@
https://docs.oasis-open.org/virtio/virtio/v1.1/virtio-v1.1.html
-Oracle Solaris 11.4 11 May 2021 vtionet(4D)
+HISTORY
+ The vtionet driver was added to Oracle Solaris in the Solaris 11.4.33
+ release.
+
+Oracle Solaris 11.4 15 Mar 2024 vtionet(4D)
diff -NurbBw 11.4.66/man4d/vtioscsi.4d 11.4.69/man4d/vtioscsi.4d
--- 11.4.66/man4d/vtioscsi.4d 2024-05-25 09:57:50.510361073 -0700
+++ 11.4.69/man4d/vtioscsi.4d 2024-05-25 09:58:13.808765750 -0700
@@ -46,4 +46,8 @@
https://docs.oasis-open.org/virtio/virtio/v1.1/virtio-v1.1.html
-Oracle Solaris 11.4 15 Dec 2020 vtioscsi(4D)
+HISTORY
+ The vtioscsi driver was added to Oracle Solaris in the Solaris 11.4.33
+ release.
+
+Oracle Solaris 11.4 15 Mar 2024 vtioscsi(4D)
diff -NurbBw 11.4.66/man4d/wscons.4d 11.4.69/man4d/wscons.4d
--- 11.4.66/man4d/wscons.4d 2024-05-25 09:57:50.555999143 -0700
+++ 11.4.69/man4d/wscons.4d 2024-05-25 09:58:13.854454249 -0700
@@ -1,7 +1,7 @@
wscons(4D) Device Drivers & /dev files wscons(4D)
NAME
- wscons - workstation console
+ wscons - system console
SYNOPSIS
#include <sys/strredir.h>
@@ -13,12 +13,11 @@
ioctl(fd, SRIOCISREDIR, target);
DESCRIPTION
- The wscons workstation console consists of a workstation keyboard and
- frame buffer that act together to emulate an ASCII terminal. It in-
- cludes a redirection facility that allows I/O issued to the workstation
- console to be diverted to a STREAMS device, enabling window systems to
- redirect output that would otherwise appear directly on the frame
- buffer in corrupted form.
+ The wscons system console consists of a keyboard and display device
+ that act together to emulate an ASCII terminal. It includes a redirec-
+ tion facility that allows I/O issued to the system console to be di-
+ verted to a STREAMS device, enabling window systems to redirect output
+ that would otherwise appear directly on the display in corrupted form.
Redirection
The wscons redirection facility maintains a list of devices that are
@@ -31,8 +30,8 @@
The ioctls described below control the redirection facility. In both
- cases, fd is a descriptor for the device being redirected (or worksta-
- tion console) and target is a descriptor for a STREAMS device.
+ cases, fd is a descriptor for the device being redirected (or system
+ console) and target is a descriptor for a STREAMS device.
SRIOCSREDIR Designates target as the source and destination of I/O
ostensibly directed to the device denoted by fd.
@@ -53,26 +52,26 @@
tion. See visual_io(4I) for more details.
- Note: The VT100 adheres the ANSI X3.64 standard. However, because the
- VT100 features nonstandard extensions to ANSI X3.64, it is incompatible
- with Sun terminal emulators.
+ Note: The VT100 adheres to the ANSI X3.64 standard. However, because
+ the VT100 features nonstandard extensions to ANSI X3.64, it is incom-
+ patible with Solaris terminal emulators.
The SPARC console displays 34 lines of 80 ASCII characters per line.
The x86 console displays 25 lines of 80 ASCII characters per line. De-
vices with smaller text capacities may display less. On SPARC systems,
- the screen-#rows screen-#columns should be set to 34 or 80 respectively
- or text capacities will vary from those described above. On SPARC sys-
- tems, the screen-#rows and screen-#columns fields are stored in
- NVRAM/EEPROM. See eeprom(8) for more information. Both SPARC and x86
+ the screen-#rows and screen-#columns should be set to 34 or 80 respec-
+ tively or text capacities will vary from those described above. On
+ SPARC systems, the screen-#rows and screen-#columns fields are stored
+ in NVRAM/EEPROM. See eeprom(8) for more information. Both SPARC and x86
consoles offer scrolling, (x, y) cursor addressing ability and a number
of other control functions.
The console cursor marks the current line and character position on the
screen. ASCII characters between 0x20(space) and 0x7E (tilde) inclusive
- are printing characters. When a print character is written to the con-
- sole (and is not part of an escape sequence), it is displayed at the
+ are printing characters. When a printing character is written to the
+ console (and is not part of an escape sequence), it is displayed at the
current cursor position and the cursor moves one position to the right
on the current line.
@@ -138,7 +137,7 @@
In the following examples of syntactically valid escape sequences, ESC
- represent the single ASCII character, Escape:
+ represents the single ASCII character, Escape:
ESC[m Select graphic rendition with default parameter
@@ -160,9 +159,10 @@
Each control function requires a specified number of parameters. If
fewer parameters are supplied, the remaining parameters (with certain
exceptions noted below) default to 1. If more parameters are supplied,
- the first n parameters are used by kernel terminal emulator. In con-
- trast, only the last n parameters are used by PROM based emulator,
- where n is the number required by that particular command character.
+ the first n parameters are used by the kernel terminal emulator. In
+ contrast, only the last n parameters are used by the PROM based emula-
+ tor, where n is the number required by that particular command charac-
+ ter.
Parameters which are omitted or set to 0 are reset to the default value
@@ -204,9 +204,8 @@
CTRL-G
0x7
Used for consoles that are not equipped with an
- audible bell. Current Sun workstation models also
- flash the screen if the keyboard is not the con-
- sole input device.
+ audible bell. Some systems also flash the screen
+ if the keyboard is not the console input device.
@@ -221,10 +220,10 @@
Tab (TAB), The cursor moves right on the current line to the
CTRL-I, next tab stop. The tab stops are fixed at every
0x9 multiple of eight columns. If the cursor is al-
- ready at the right edge of the screen, nothing
- change takes place. Otherwise, the cursor moves
- right a minimum of one and a maximum of eight
- character positions.
+ ready at the right edge of the screen, no change
+ takes place. Otherwise, the cursor moves right a
+ minimum of one and a maximum of eight character
+ positions.
@@ -233,15 +232,15 @@
CTRL-J, position on the line, moves down one line. If the
0xA cursor is at the bottom line, the screen either
scrolls up or wraps around depending on the set-
- ting of an internal variable n (initially 1) .
- The internal variable can be changed using the
- ESC[r control sequence. If n is greater than
- zero, the entire screen (including the cursor) is
- scrolled up by n lines before executing the line-
- feed. The top n lines scroll off the screen and
- are lost. New blank lines n scroll onto the bot-
- tom of the screen. After scrolling, move the cur-
- sor down one line to execute the line feed.
+ ting of an internal variable n (initially 1). The
+ internal variable can be changed using the ESC[r
+ control sequence. If n is greater than zero, the
+ entire screen (including the cursor) is scrolled
+ up by n lines before executing the line-feed. The
+ top n lines scroll off the screen and are lost.
+ New blank lines n scroll onto the bottom of the
+ screen. After scrolling, move the cursor down one
+ line to execute the line feed.
If n is zero, wrap-around mode is entered. The
ESC [ 1 r exits back to scroll mode. If a line-
@@ -267,14 +266,17 @@
and fills in the newly created lines. As long as
escape codes or other control characters are not
intermixed with the text, this results in faster
- scrolling
+ scrolling.
- Reverse Line-feed, With kernel terminal emulator (while remaining at
- CTRL-K, the same character position on the line), the
- 0xB cursor moves down one line. However, with PROM
+ Reverse Line-feed,
+ CTRL-K,
+ 0xB
+ With kernel terminal emulator (while remaining at
+ the same character position on the line), the
+ cursor moves down one line. However, with PROM
based emulator (while remaining at the same char-
acter position on the line), the cursor moves up
one line. If the cursor is already at the top
@@ -584,8 +586,7 @@
RETURN VALUES
When there are no errors, the redirection ioctls have return values as
described above. Otherwise, they return -1 and set errno to indicate
- the error. If the target stream is in an error state, errno is set ac-
- cordingly.
+ the error.
If the target stream is in an error state, errno is set accordingly.
@@ -598,8 +599,7 @@
FILES
- /dev/wscons Workstation console, accessed via the redirection fa-
- cility
+ /dev/wscons System console, accessed via the redirection facility
/dev/systty Devices that must be opened for the SRIOCSREDIR and
@@ -618,6 +618,10 @@
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
+ | Architecture |SPARC, x86 |
+ +------------------------------+-----------------------------+
+ | Availability |system/kernel |
+ +------------------------------+-----------------------------+
| Interface Stability |Committed |
+------------------------------+-----------------------------+
@@ -628,8 +632,8 @@
WARNINGS
The redirection ioctls block while there is I/O outstanding on the de-
- vice instance being redirected. If you try to redirect the workstation
- console while there is a outstanding read, the workstation console will
- hang until the read completes.
+ vice instance being redirected. If you try to redirect the system con-
+ sole while there is a outstanding read, the system console will hang
+ until the read completes.
-Oracle Solaris 11.4 13 Nov 2020 wscons(4D)
+Oracle Solaris 11.4 15 Mar 2024 wscons(4D)
diff -NurbBw 11.4.66/man4d/zero.4d 11.4.69/man4d/zero.4d
--- 11.4.66/man4d/zero.4d 2024-05-25 09:57:50.588045245 -0700
+++ 11.4.69/man4d/zero.4d 2024-05-25 09:58:13.885699387 -0700
@@ -3,6 +3,9 @@
NAME
zero - source of zeroes
+SYNOPSIS
+ /dev/zero
+
DESCRIPTION
A zero special file is a source of zeroed unnamed memory.
@@ -26,6 +29,6 @@
SEE ALSO
- fork(2), mmap(2), sysconf(3C)
+ fork(2), mmap(2), sysconf(3C), full(4D), null(4D)
-Oracle Solaris 11.4 3 Jul 1990 zero(4D)
+Oracle Solaris 11.4 15 Mar 2024 zero(4D)
diff -NurbBw 11.4.66/man4p/inet6.4p 11.4.69/man4p/inet6.4p
--- 11.4.66/man4p/inet6.4p 2024-05-25 09:57:50.627229620 -0700
+++ 11.4.69/man4p/inet6.4p 2024-05-25 09:58:13.927380324 -0700
@@ -290,6 +290,12 @@
fined in RFC 3041. Temporary addresses are disabled by default and
may be enabled by appropriate settings in ndpd.conf(5).
+ RFC 6724 reversed this preference to "prefer temporary addresses",
+ Solaris kept the RFC 3484 preference by default to maintain back-
+ ward compatibility with existing applications. Solaris will follow
+ the RFC 6724 rule if the ipadm IPv6 protocol property "prefer-sr-
+ caddr" is set to "temporary", see ipadm(8).
+
The sense of this rule may be set on a per-socket basis using the
IPV6_SRC_PREFERENCES socket option. Passing the flag IPV6_PRE-
FER_SRC_TMP or IPV6_PREFER_SRC_PUBLIC will cause temporary or pub-
diff -NurbBw 11.4.66/man5/a.out.5 11.4.69/man5/a.out.5
--- 11.4.66/man5/a.out.5 2024-05-25 09:57:50.661280435 -0700
+++ 11.4.69/man5/a.out.5 2024-05-25 09:58:13.961544817 -0700
@@ -90,6 +90,11 @@
The data segment is extended as requested by the brk(2) system call.
SEE ALSO
- as(1), ld(1), brk(2), elf(3ELF)
+ as(1), elfcompress(1), elfdiff(1), elfdump(1), elfedit(1), elffile(1),
+ elfsign(1), elfwrap(1), ld(1), ld.so.1(1), ldd(1), mcs(1), nm(1),
+ pvs(1), strip(1), brk(2), mmapobj(2), elf(3ELF)
-Oracle Solaris 11.4 30 Jul 2018 a.out(5)
+
+ Oracle Solaris 11.4 Linkers and Libraries Guide
+
+Oracle Solaris 11.4 14 Dec 2023 a.out(5)
diff -NurbBw 11.4.66/man5/ai_manifest.5 11.4.69/man5/ai_manifest.5
--- 11.4.66/man5/ai_manifest.5 2024-05-25 09:57:50.742302982 -0700
+++ 11.4.69/man5/ai_manifest.5 2024-05-25 09:58:14.045206424 -0700
@@ -1595,13 +1592,13 @@
order in which the publishers are set in the installed image.
- Use the cmd_options sub-element of the publisher element to specify an
- options string to be passed to the pkg(1) set-publisher command to be
- run on the publisher. This element can be used to set properties, at-
- tributes, or other options on the publisher. See the pkg(1) man page
- for more information about the set-publisher subcommand. Note that not
- all options are applicable to be set on publishers in the context of
- installation.
+ The cmd_options sub-element of the publisher element specifies an op-
+ tions string. This options string is added to the pkg set-publisher
+ command run on the publisher. This element can be used to set proper-
+ ties, attributes, or other options on the publisher. See the pkg(1) man
+ page for more information about the set-publisher subcommand. Note that
+ not all options are applicable to be set on publishers in the context
+ of installation.
The following example specifies a publisher that has two cmd_options to
@@ -1675,8 +1672,7 @@
The value of the key element is the key. See the pkg(1) man page for
- more information about the pkg
- set-publisher command.
+ more information about the pkg set-publisher command.
The cert element maps to the following pkg command:
@@ -1686,8 +1682,7 @@
The value of the cert element is the cert. See the pkg(1) man page for
- more information about the pkg
- set-publisher command.
+ more information about the pkg set-publisher command.
The cacert element maps to the following pkg command:
@@ -1700,15 +1695,12 @@
date the certificate issuer. This is element is optional within the
credentials element. If not specified then the CA certificates within
/etc/certs/CA will be used. See the pkg(1) man page for more informa-
- tion about the pkg
- set-publisher command.
-
-
- The key, cert, and cacert can be a URI, an inlined file or a combina-
- tion of URI and inlined file. http, https, file are supported URI pro-
- tocols. The inlined credentials might look like the following:
+ tion about the pkg set-publisher command.
+ The key, cert, and cacert can be a URI, an inlined file, or a combina-
+ tion of URI and inlined file. http, https, and file are supported URI
+ protocols. The inlined credentials might look like the following:
<software type="IPS">
<source>
@@ -1720,13 +1712,13 @@
MIICXgIBAAKBgQC508UlZ...
...
-----END RSA PRIVATE KEY-----
- <key>
+ </key>
<cert>
-----BEGIN CERTIFICATE-----
MIIB+jCCAWMCAQowDQYJK...
...
-----END CERTIFICATE-----
- <cert>
+ </cert>
</credentials>
</publisher>
</source>
@@ -1930,7 +1920,7 @@
ARCHIVE Installations
For an ARCHIVE transfer, a source file URI must be specified. The URI
- value can be an HTTP, HTTPS or FILE URI specification.
+ value can be an HTTP, HTTPS, or FILE URI specification.
<software type="ARCHIVE">
@@ -1941,15 +1931,14 @@
- Use elements of the file element to specify SSL Keys, certificates and
- CA certificates or an authorization token that are required to access
+ Use elements of the file element to specify SSL Keys, certificates, and
+ CA certificates, or an authorization token that are required to access
the unified archive securely.
To access a unified archive requiring SSL client authentication you can
- provide key, certificate and CA certificate within the credentials sub-
- element.
-
+ provide key, certificate, and CA certificate within the credentials
+ sub-element.
<software type="ARCHIVE">
<source>
@@ -1966,7 +1955,7 @@
Refer to the section on IPS Installations for specific information on
- format and accepted values for key, cert and cacert elements.
+ format and accepted values for key, cert, and cacert elements.
To access a unified archive requiring a specific authorization token
@@ -2070,7 +2054,7 @@
ages but are optional components of any given software package such as
locales, documentation, and development files such as files with debug
information. You can save space by specifying that you only want to in-
- stall one or two languages, for example. See the pkg(1) man page for
+ stall one or two languages, for example. See the pkg(7) man page for
more information about IPS facets.
@@ -2185,8 +2167,9 @@
Use the boot_entry sub-element to add one or more menu items to the
boot menu. These menu items are in addition to any menu items that are
- automatically generated by the installer. The default menu item for ac-
- tive BE will not be present if menu item from boot_entry is present.
+ automatically generated by the installer. The default menu item for the
+ active BE will not be present if a menu item from boot_entry is
+ present.
The boot_entry element has the following attributes:
@@ -2287,7 +2269,7 @@
For more information about configuring and installing zones, see Chap-
- ter 6, Installing and Configuring Zones in Automatically Installing Or-
+ ter 7, Installing and Configuring Zones in Automatically Installing Or-
acle Solaris 11.4 Systems.
FILES
@@ -2331,9 +2313,9 @@
SEE ALSO
- pkg(1), grub(7), smf(7), beadm(8), boot(8), croinfo(8), fdisk(8), for-
- mat(8), installadm(8), iostat(8), iscsiadm(8), pkg.sysrepo(8), prt-
- conf(8), zfs(8), zoneadm(8), zonecfg(8), zpool(8)
+ pkg(1), grub(7), pkg(7), smf(7), beadm(8), boot(8), croinfo(8),
+ fdisk(8), format(8), installadm(8), iostat(8), iscsiadm(8), pkg.sys-
+ repo(8), prtconf(8), zfs(8), zoneadm(8), zonecfg(8), zpool(8)
Automatically Installing Oracle Solaris 11.4 Systems
@@ -2420,4 +2401,4 @@
When using name_type in a manifest, it is important to use a name that
is unique across all the devices being installed.
-Oracle Solaris 11.4 23 Aug 2023 ai_manifest(5)
+Oracle Solaris 11.4 14 Dec 2023 ai_manifest(5)
diff -NurbBw 11.4.66/man5/audit_class.5 11.4.69/man5/audit_class.5
--- 11.4.66/man5/audit_class.5 2024-05-25 09:57:50.777459349 -0700
+++ 11.4.69/man5/audit_class.5 2024-05-25 09:58:14.080376943 -0700
@@ -127,4 +127,10 @@
Managing Auditing in Oracle Solaris 11.4
-Oracle Solaris 11.4 21 Jun 2021 audit_class(5)
+HISTORY
+ The /etc/security/audit_class.system file was introduced in Oracle So-
+ laris 11.4.33. Prior to this release, sites with audit_class customiza-
+ tions were required to manually merge their changes with the system de-
+ livered file every time the system definitions were changed.
+
+Oracle Solaris 11.4 14 Dec 2023 audit_class(5)
diff -NurbBw 11.4.66/man5/core.5 11.4.69/man5/core.5
--- 11.4.66/man5/core.5 2024-05-25 09:57:50.815853423 -0700
+++ 11.4.69/man5/core.5 2024-05-25 09:58:14.118713284 -0700
@@ -283,13 +283,15 @@
one to be matched with the other.
- The size of the core file created by a process can be controlled by the
- user (see getrlimit(2)).
+ The size of the core file created by a process using the per-process
+ core file name pattern can be controlled by the user. See setrlimit(2).
+ This limit will not affect core files created using the global core
+ file name pattern.
SEE ALSO
- elfdump(1), gcore(1), mdb(1), proc(1), ps(1), getrlimit(2), setr-
- limit(2), setuid(2), sysinfo(2), uname(2), getzoneid(3C), getzonename-
- byid(3C), elf(3ELF), signal.h(3HEAD), a.out(5), proc(5), zones(7),
- coreadm(8)
+ elfdump(1), gcore(1), mdb(1), pargs(1), pmap(1), proc(1), ps(1), getr-
+ limit(2), setrlimit(2), setuid(2), sysinfo(2), uname(2), getzoneid(3C),
+ getzonenamebyid(3C), elf(3ELF), signal.h(3HEAD), a.out(5), proc(5),
+ zones(7), coreadm(8)
-Oracle Solaris 11.4 1 Sep 2020 core(5)
+Oracle Solaris 11.4 14 Dec 2023 core(5)
diff -NurbBw 11.4.66/man5/datalink-management.5 11.4.69/man5/datalink-management.5
--- 11.4.66/man5/datalink-management.5 2024-05-25 09:57:50.849344968 -0700
+++ 11.4.69/man5/datalink-management.5 2024-05-25 09:58:14.155293176 -0700
@@ -126,10 +121,8 @@
</service>
-
Example 4 Customize Datalink Name Mapping such that ixgbe0 is named
- mynet0, and ixgbe1 is named
- mynet1
+ mynet0, and ixgbe1 is named mynet1
@@ -178,22 +170,20 @@
</service>
-
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
- | Availability |svc:/network/datalink-man- |
- | |agement:default properties |
+ | Availability |system/network |
+------------------------------+-----------------------------+
| Interface Stability |Committed |
+------------------------------+-----------------------------+
SEE ALSO
- dladm(8), flowadm(8), installadm(8), service_bundle(5), smf(7), syscon-
+ service_bundle(5), smf(7), dladm(8), flowadm(8), installadm(8), syscon-
fig(8)
-Oracle Solaris 11.4 18 Apr 2016 datalink-management(5)
+Oracle Solaris 11.4 14 Dec 2023 datalink-management(5)
diff -NurbBw 11.4.66/man5/dc_manifest.5 11.4.69/man5/dc_manifest.5
--- 11.4.66/man5/dc_manifest.5 2024-05-25 09:57:50.892168488 -0700
+++ 11.4.69/man5/dc_manifest.5 2024-05-25 09:58:14.196062975 -0700
@@ -185,13 +180,13 @@
Use the mirror sub-element to specify a mirror repository location.
- Use the cmd_options sub-element of the publisher element to specify an
- options string to be passed to the pkg(1) set-publisher command to be
- run on the publisher. This element can be used to set properties, at-
- tributes, or other options on the publisher. See the pkg(1) man page
- for more information about the set-publisher subcommand. Note that not
- all options are applicable to be set on publishers in the context of
- distribution construction.
+ The cmd_options sub-element of the publisher element specifies an op-
+ tions string. This options string is added to the pkg set-publisher
+ command run on the publisher. This element can be used to set proper-
+ ties, attributes, or other options on the publisher. See the pkg(1) man
+ page for more information about the set-publisher subcommand. Note that
+ not all options are applicable to be set on publishers in the context
+ of distribution construction.
See the pkg(7) man page for information about IPS publishers and repos-
@@ -251,9 +246,10 @@
- Do not remove the installation of the packaged named entire. The
- packaged named entire is an incorporation used to manage multiple
- packages.
+ Do not remove or prevent the installation of the package named en-
+ tire. The package named entire is an incorporation used to manage
+ multiple packages that form the Oracle Solaris OS. Systems without
+ entire installed are unsupported.
Software Packages Section: Uninstall
@@ -273,8 +269,8 @@
In the source element, use the publisher name and optional mirror name
to specify where the installed system can access additional packages to
download and install. Use the optional cmd_options sub-element to spec-
- ify options strings to be passed to the pkg(1) set-publisher command to
- be run on the publisher.
+ ify options strings to be passed to the pkg set-publisher command to be
+ run on the publisher.
<source>
<publisher name="solaris">
@@ -418,9 +412,9 @@
SEE ALSO
- pkg(1), distro_const(8)
+ pkg(1), pkg(7), distro_const(8)
Creating a Custom Oracle Solaris 11.4 Image
-Oracle Solaris 11.4 6 Nov 2019 dc_manifest(5)
+Oracle Solaris 11.4 14 Dec 2023 dc_manifest(5)
diff -NurbBw 11.4.66/man5/devices.5 11.4.69/man5/devices.5
--- 11.4.66/man5/devices.5 2024-05-25 09:57:50.923303779 -0700
+++ 11.4.69/man5/devices.5 2024-05-25 09:58:14.231068225 -0700
@@ -37,7 +37,7 @@
There are no administrative actions necessary with respect to files in
/etc/devices. Should the contents of a file become corrupted or an up-
- date fail, the file can simply be removed. The system re-creates the
+ date fail, most files can simply be removed. The system re-creates the
file as necessary.
@@ -45,7 +45,7 @@
sistent or /etc/devices/pci_unitaddr_persistent_cache.
SEE ALSO
- dev(4FS), devfsadm(8), ddi_devid_compare(9F), ddi_devid_compare(9F)
+ dev(4FS), devfsadm(8), ddi_devid_compare(9F)
NOTES
Files in this directory do not constitute an API. Files might not exist
@@ -53,4 +53,4 @@
lease. The existence of this notice does not imply that any other docu-
mentation that lacks this notice constitutes an API.
-Oracle Solaris 11.4 14 Sep 2010 devices(5)
+Oracle Solaris 11.4 14 Dec 2023 devices(5)
diff -NurbBw 11.4.66/man5/dhcp_inittab.5 11.4.69/man5/dhcp_inittab.5
--- 11.4.66/man5/dhcp_inittab.5 2024-05-25 09:57:50.969372808 -0700
+++ 11.4.69/man5/dhcp_inittab.5 2024-05-25 09:58:14.279196365 -0700
@@ -212,8 +212,7 @@
Mnemonic Identifiers for IPv4 Options
The following table maps the mnemonic identifiers used in Solaris DHCP
- to RFC
- 2132 and RFC 3442 options:
+ to RFC 2132 and RFC 3442 options:
Symbol Code Description
------------------------------------------------------------------------
@@ -221,7 +220,7 @@
(IP).
UTCoffst 2 Coordinated Universal time offset (sec-
onds).
- Router 3 List of Routers, IP.
+ Router 3 * List of Routers, IP.
Timeserv 4 List of RFC-868 servers, IP.
IEN116ns 5 List of IEN 116 name servers, IP.
DNSserv 6 List of DNS name servers, IP.
@@ -306,7 +305,7 @@
PXEarch 93 Client system architecture, NUMBER.
DNSDomSearch 119 List of FQDN to populate DNS Search,
FQDN.
- ClasslessRt 121 List of Classless Static Routes,
+ ClasslessRt 121 * List of Classless Static Routes,
CLROUTE.
BootFile N/A File to Boot, ASCII.
BootPath N/A Boot path prefix to apply to client's
@@ -322,11 +321,10 @@
-
- defines that as per RFC 3442, if the DHCP server returns both, a
- Classless Static Route option and a Router option, the Solaris DHCP
- client ignores the Router option.
-
+ As per RFC 3442, if the DHCP server returns both a Classless Static
+ Route option and a Router option, the Solaris DHCP client ignores the
+ Router option. Affected options are indicated with a '*' in the above
+ table.
Mnemonic Identifiers for IPv6 Options
@@ -417,15 +414,13 @@
Lemon, T., and S. Cheshire. RFC 3396, Encoding Long Options in the Dy-
- namic Host
- Configuration Protocol (DHCPv4). Network Working Group. November
- 2002.
+ namic Host Configuration Protocol (DHCPv4). Network Working Group. No-
+ vember 2002.
Lemon, T., S. Cheshire, and B. Volz. RFC 3442, The Classless Static
- Route Option
- for Dynamic Host Configuration Protocol (DHCP) version 4. Network
- Working Group. December 2002.
+ Route Option for Dynamic Host Configuration Protocol (DHCP) version 4.
+ Network Working Group. December 2002.
Droms, R. RFC 3646, DNS Configuration options for Dynamic Host Configu-
@@ -445,4 +440,28 @@
Mockapetris, P.V. RFC 1035, Domain names - implementation and specifi-
cation. ISI. November 1987.
-Oracle Solaris 11.4 14 May 2018 dhcp_inittab(5)
+HISTORY
+ The /etc/dhcp/inittab file was added to Solaris in the Solaris 8 re-
+ lease. The /etc/dhcp/inittab6 file was added to Solaris in the Solaris
+ 10 8/07 (Update 4) release.
+
+
+ The following options are present in these files in Oracle Solaris
+ starting with the listed release:
+
+ +-------------------------------------+---------------------------+
+ | OPTION | RELEASE |
+ +-------------------------------------+---------------------------+
+ | DNSDomSearch (IPv4) | 11.4.63 |
+ +-------------------------------------+---------------------------+
+ | ClasslessRt (IPv4) | 11.3.20, Solaris 10 patch |
+ +-------------------------------------+---------------------------+
+ | DHCPv6 options | 10 8/07 (Update 4) |
+ +-------------------------------------+---------------------------+
+ | SbootURI, SHTTPproxy | 9 12/03 (Update 5) |
+ +-------------------------------------+---------------------------+
+ | all other IPv4 options | 8 |
+ +-------------------------------------+---------------------------+
+
+
+Oracle Solaris 11.4 14 Dec 2023 dhcp_inittab(5)
diff -NurbBw 11.4.66/man5/driver.conf.5 11.4.69/man5/driver.conf.5
--- 11.4.66/man5/driver.conf.5 2024-05-25 09:57:51.009305569 -0700
+++ 11.4.69/man5/driver.conf.5 2024-05-25 09:58:14.323696518 -0700
@@ -222,15 +222,12 @@
look up the earlier property on the admin list and if found, continue
to honor it.
-
-
/*
* Has the timeout been locally configured using the
* prior option of timeout in units of seconds?
*/
if (ddi_prop_lookup_int(DDI_DEV_T_ANY, dip,
- DDI_PROP_ADMIN, "timeout",) ==
- DDI_PROP_SUCCESS) {
+ DDI_PROP_ADMIN, "timeout") == DDI_PROP_SUCCESS) {
if (n != 1) {
ddi_prop_free(ivalues);
return (EINVAL);
@@ -299,8 +295,8 @@
the pseudo node in the kernel device tree. The instance property is
only interpreted by the pseudo node, see pseudo(5) for further details.
A property called debug-level is created on the first devinfo node
- which has the value 1. The example driver is able to fetch the value
- of this property using ddi_prop_get_int(9F).
+ which has the value 1. The example driver is able to fetch the value of
+ this property using ddi_prop_get_int(9F).
@@ -475,12 +441,10 @@
-
-
and that it is desired to also support a target=1 device instance. Fur-
ther suppose that target=0 should be configured with the max-retries
- parameter set to 10 and queueing set to 32, and that target=1 with
- max-retries to 10 and queueing to 64. Place the following lines in the
+ parameter set to 10 and queueing set to 32, and that target=1 with max-
+ retries set to 10 and queueing to 64. Place the following lines in the
sd.conf file in /etc/driver/drv:
@@ -576,4 +532,4 @@
or to remove a parent specification, defined in a vendor driver.conf
file with an addition to an /etc/driver/drv driver.conf file.
-Oracle Solaris 11.4 15 Apr 2019 driver.conf(5)
+Oracle Solaris 11.4 14 Dec 2023 driver.conf(5)
diff -NurbBw 11.4.66/man5/fd.5 11.4.69/man5/fd.5
--- 11.4.66/man5/fd.5 2024-05-25 09:57:51.042384336 -0700
+++ 11.4.69/man5/fd.5 2024-05-25 09:58:14.354288092 -0700
@@ -5,17 +5,18 @@
DESCRIPTION
These files, conventionally called /dev/fd/0, /dev/fd/1, /dev/fd/2, and
- so on, refer to files accessible through file descriptors. If file de-
- scriptor n is open, these two system calls have the same effect:
+ so on, refer to files accessible through file descriptors of the
+ process accessing them. If file descriptor n is open, these two system
+ calls have the same effect:
fd = open("/dev/fd/n",mode);
fd = dup(n);
- On these files creat(2) is equivalent to open, and mode is ignored. As
- with dup, subsequent reads or writes on fd fail unless the original
- file descriptor allows the operations.
+ On these files creat(2) is equivalent to open(2), and mode is ignored.
+ As with dup(2), subsequent reads or writes on fd fail unless the origi-
+ nal file descriptor allows the operations.
For convenience in referring to standard input, standard output, and
@@ -23,11 +24,15 @@
synonym for /dev/fd/0, /dev/stdout for /dev/fd/1, and /dev/stderr for
/dev/fd/2.
+
+ To access file descriptors of other processes, see the fd section of
+ proc(5) for information on the /proc/pid/fd/ subdirectory.
+
SEE ALSO
- creat(2), dup(2), open(2)
+ creat(2), dup(2), open(2), proc(5)
DIAGNOSTICS
open(2) returns -1 and EBADF if the associated file descriptor is not
open.
-Oracle Solaris 11.4 3 Jul 1990 fd(5)
+Oracle Solaris 11.4 14 Dec 2023 fd(5)
diff -NurbBw 11.4.66/man5/hosts.equiv.5 11.4.69/man5/hosts.equiv.5
--- 11.4.66/man5/hosts.equiv.5 2024-05-25 09:57:51.079689740 -0700
+++ 11.4.69/man5/hosts.equiv.5 2024-05-25 09:58:14.394229086 -0700
@@ -8,11 +8,11 @@
tion" database for rlogin(1), rsh(1), rcp(1), and rcmd(3C). The files
specify remote hosts and users that are considered "trusted". Trusted
users are allowed to access the local system without supplying a pass-
- word. The library routine ruserok() (see rcmd(3C)) performs the authen-
- tication procedure for programs by using the /etc/hosts.equiv and
- .rhosts files. The /etc/hosts.equiv file applies to the entire system,
- while individual users can maintain their own .rhosts files in their
- home directories.
+ word. The library routine ruserok(3C) performs the authentication pro-
+ cedure for programs by using the /etc/hosts.equiv and .rhosts files.
+ The /etc/hosts.equiv file applies to the entire system, while individ-
+ ual users can maintain their own .rhosts files in their home directo-
+ ries.
These files bypass the standard password-based user authentication
@@ -220,8 +220,8 @@
SEE ALSO
- rcp(1), rlogin(1), rsh(1), rcmd(3C), hosts(5), netgroup(5), passwd(5),
- pam_rhosts_auth(7)
+ rcp(1), rlogin(1), rsh(1), rcmd(3C), ruserok(3C), hosts(5), net-
+ group(5), passwd(5), pam_rhosts_auth(7)
NOTES
The PAM configuration of pam_rhosts_auth(7) can cause the hosts.equiv
@@ -243,4 +243,10 @@
will not deny access to "hostxxx".
-Oracle Solaris 11.4 27 Nov 2017 hosts.equiv(5)
+
+ There is no comment character defined for these files. The ruserok(3C)
+ function will attempt to resolve any character string starting a line
+ in these files as a hostname, even if it uses characters not typically
+ found in hostnames.
+
+Oracle Solaris 11.4 14 Dec 2023 hosts.equiv(5)
diff -NurbBw 11.4.66/man5/ike.config.5 11.4.69/man5/ike.config.5
--- 11.4.66/man5/ike.config.5 2024-05-25 09:57:51.128430331 -0700
+++ 11.4.69/man5/ike.config.5 2024-05-25 09:58:14.445883364 -0700
@@ -391,9 +391,9 @@
a receiver is expected to only accept such an entry if it matches
one in a phase 1 rule. There can be several of these, and they are
additive. There must be either at least one phase 1 transform in a
- rule or a global default phase 1 transform list. In a configuration
+ rule or a global default phase 1 transform list. A configuration
file without a global default phase 1 transform list and a rule
- without a phase, transform list is an invalid file. Unless speci-
+ without a phase 1 transform list is an invalid file. Unless speci-
fied as optional, elements in the parameter-list must occur exactly
once within a given transform's parameter-list:
@@ -664,7 +664,7 @@
# Root certificates. I SHOULD use a full Distinguished Name.
# I must have this certificate in my local filesystem, see ikecert(8).
- cert_root "C=US, O=Oracle\\, Inc., CN=Sun CA"
+ cert_root "C=US, O=Oracle\\, Inc., CN=Oracle CA"
# Explicitly trusted certs that need no signatures, or perhaps
# self-signed ones. Like root certificates, use full DNs for them
@@ -886,4 +886,4 @@
https://tools.ietf.org/html/rfc5114
-Oracle Solaris 11.4 21 Jun 2021 ike.config(5)
+Oracle Solaris 11.4 14 Dec 2023 ike.config(5)
diff -NurbBw 11.4.66/man5/inittab.5 11.4.69/man5/inittab.5
--- 11.4.66/man5/inittab.5 2024-05-25 09:57:51.164000344 -0700
+++ 11.4.69/man5/inittab.5 2024-05-25 09:58:14.482102271 -0700
@@ -58,16 +58,16 @@
is specified, then the process is assumed to be valid at all
run levels 0 through 6.
- There are three other values, a, b and c, which can appear
+ There are three other values, a, b, and c, which can appear
in the rstate field, even though they are not true run lev-
els. Entries which have these characters in the rstate field
are processed only when an init or telinit process requests
them to be run (regardless of the current run level of the
system). See init(8). These differ from run levels in that
- init can never enter run level a, b or c. Also, a request
+ init can never enter run level a, b, or c. Also, a request
for the execution of any of these processes does not change
the current run level. Furthermore, a process started by an
- a , b or c command is not killed when init changes levels.
+ a, b, or c command is not killed when init changes levels.
They are killed only if their line in inittab is marked off
in the action field, their line is deleted entirely from
inittab, or init goes into single-user state.
@@ -143,7 +143,7 @@
respawn action. It is functionally identical to
respawn but is given a different keyword in or-
der to divorce its association with run levels.
- This instruction is used only with the a, b or
+ This instruction is used only with the a, b, or
c values described in the rstate field.
@@ -172,9 +172,10 @@
provided /etc/inittab file is greatly reduced from previous releases.
- The initdefault entry is not recognized in Solaris 10. See smf(7) for
- information on SMF milestones, and svcadm(8), which describes the "sv-
- cadm milestone -d" command; this provides similar functionality to
- modifying the initdefault entry in previous versions of the Solaris OS.
+ The initdefault entry is not recognized in Solaris 10 and later re-
+ leases. See smf(7) for information on SMF milestones, and svcadm(8),
+ which describes the "svcadm milestone -d" command; this provides simi-
+ lar functionality to modifying the initdefault entry in previous ver-
+ sions of the Solaris OS.
-Oracle Solaris 11.4 30 Sept 2016 inittab(5)
+Oracle Solaris 11.4 14 Dec 2023 inittab(5)
diff -NurbBw 11.4.66/man5/Intro.5 11.4.69/man5/Intro.5
--- 11.4.66/man5/Intro.5 2024-05-25 09:57:51.197010048 -0700
+++ 11.4.69/man5/Intro.5 2024-05-25 09:58:14.512931848 -0700
@@ -11,4 +11,4 @@
guage programs, however, the syntax #include <filename.h> or #include
<sys/filename.h> should be used.
-Oracle Solaris 11.4 16 Apr 2003 Intro(5)
+Oracle Solaris 11.4 14 Dec 2023 Intro(5)
diff -NurbBw 11.4.66/man5/ipaddrsel.conf.5 11.4.69/man5/ipaddrsel.conf.5
--- 11.4.66/man5/ipaddrsel.conf.5 2024-05-25 09:57:51.229540458 -0700
+++ 11.4.69/man5/ipaddrsel.conf.5 2024-05-25 09:58:14.548158459 -0700
@@ -21,18 +21,23 @@
The following is the default /etc/inet/ipaddrsel.conf file:
+
#
- #ident "@(#)ipv6das.conf 1.1 02/07/28 SMI"
+ # Copyright (c) 2002, 2023, Oracle and/or its affiliates.
#
- # Copyright (c) 2002, Oracle and/or its affiliates. All rights reserved.
+ # This is the IPv6 default address selection policy table. See
+ # ipaddrsel(8) for details and examples.
#
# Prefix Precedence Label
- ::1/128 50 0
- ::/0 40 1
- 2002::/16 30 2
- ::/96 20 3
- ::ffff:0.0.0.0/96 10 4
-
+ ::1/128 50 Loopback (RFC4291)
+ ::/0 40 Default
+ ::ffff:0:0/96 35 IPv4 ::ffff:0.0.0.0/96 (RFC4038)
+ 2002::/16 30 6to4 (RFC3056)
+ 2001::/32 5 Terado (RFC4380)
+ fc00::/7 3 Unique Local Addresses (RFC4193)
+ ::/96 1 IPv4_Compatible (RFC4291-deprecated)
+ fec0::/10 1 Site-local (RFC3879-deprecated)
+ 3ffe::/16 1 6Bone (RFC3701-deprecated)
diff -NurbBw 11.4.66/man5/md.tab.5 11.4.69/man5/md.tab.5
--- 11.4.66/man5/md.tab.5 2024-05-25 09:57:51.267774443 -0700
+++ 11.4.69/man5/md.tab.5 2024-05-25 09:58:14.587212908 -0700
@@ -99,20 +92,16 @@
-
-
The number 4 indicates there are four individual stripes in the con-
catenation. Each stripe is made of one slice, hence the number 1 ap-
pears in front of each slice. Note that the first disk sector in all of
the above devices contains a disk label. To preserve the labels on de-
- vices /dev/dsk/c0t2d0s0 , /dev/dsk/c0t3d0s0, and /dev/dsk/c0t4d0s0 ,
- the metadisk driver must skip at least the first sector of those disks
- when mapping accesses across the concatenation boundaries. Since skip-
- ping only the first sector would create an irregular disk geometry, the
- entire first cylinder of these disks will be skipped. This allows
- higher level file system software to optimize block allocations cor-
- rectly.
-
+ vices /dev/dsk/c0t2d0s0, /dev/dsk/c0t3d0s0, and /dev/dsk/c0t4d0s0, the
+ metadisk driver must skip at least the first sector of those disks when
+ mapping accesses across the concatenation boundaries. Since skipping
+ only the first sector would create an irregular disk geometry, the en-
+ tire first cylinder of these disks will be skipped. This allows higher
+ level file system software to optimize block allocations correctly.
Example 2 Stripe
@@ -132,11 +119,9 @@
-
-
The number 1 indicates that one stripe is being created. Because the
- stripe is made of two slices, the number 2 follows next. The optional -
- i followed by 32k specifies the interlace size will be 32 Kbytes. If
+ stripe is made of two slices, the number 2 follows next. The optional
+ -i followed by 32k specifies the interlace size will be 32 Kbytes. If
the interlace size were not specified, the stripe would use the default
value of 16 Kbytes.
@@ -190,15 +167,12 @@
-
-
- In this example, a one-way mirror is first defined using the -
- m option. The one-way mirror consists of submirror d51. The other two
- submirrors, d52 and d53, are attached later using the metattach com-
- mand. The default read and write options in this example are a round-
- robin read algorithm and parallel writes to all submirrors. The order
- in which mirrors appear in the /etc/lvm/md.tab file is unimportant.
-
+ In this example, a one-way mirror is first defined using the -m option.
+ The one-way mirror consists of submirror d51. The other two submirrors,
+ d52 and d53, are attached later using the metattach command. The de-
+ fault read and write options in this example are a round-robin read al-
+ gorithm and parallel writes to all submirrors. The order in which mir-
+ rors appear in the /etc/lvm/md.tab file is unimportant.
Example 5 RAID5
@@ -312,24 +268,21 @@
-
-
- In this example, a one-way mirror is first defined using the -
- m option. The submirrors are attached later using the metattach(8) com-
- mand. The hot spare pools to be used are tied to the submirrors with
- the -h option. In this example, there are three disks used as hot
- spares, defined in three separate hot spare pools. The hot spare pools
- are given the names hsp001, hsp002, and hsp003. Setting up three hot
- spare pools rather than assigning just one hot spare with each compo-
- nent helps to maximize the use of hardware. This configuration enables
- the user to specify that the most desirable hot spare be selected
- first, and improves availability by having more hot spares available.
- At the end of the entry, the hot spares to be used are defined. Note
- that, when using the md.tab file, to associate hot spares with metade-
- vices, the hot spare spool does not have to exist prior to the associa-
- tion. Volume Manager takes care of the order in which metadevices and
- hot spares are created when using the md.tab file.
-
+ In this example, a one-way mirror is first defined using the -m option.
+ The submirrors are attached later using the metattach(8) command. The
+ hot spare pools to be used are tied to the submirrors with the -h op-
+ tion. In this example, there are three disks used as hot spares, de-
+ fined in three separate hot spare pools. The hot spare pools are given
+ the names hsp001, hsp002, and hsp003. Setting up three hot spare pools
+ rather than assigning just one hot spare with each component helps to
+ maximize the use of hardware. This configuration enables the user to
+ specify that the most desirable hot spare be selected first, and im-
+ proves availability by having more hot spares available. At the end of
+ the entry, the hot spares to be used are defined. Note that, when using
+ the md.tab file, to associate hot spares with metadevices, the hot
+ spare spool does not have to exist prior to the association. Volume
+ Manager takes care of the order in which metadevices and hot spares are
+ created when using the md.tab file.
Example 9 State Database Replicas
@@ -404,4 +348,4 @@
vices are not logging--they pass data directly through to the underly-
ing device. See mount_ufs(8) for more information about UFS logging.
-Oracle Solaris 11.4 15 Dec 2004 md.tab(5)
+Oracle Solaris 11.4 14 Dec 2023 md.tab(5)
diff -NurbBw 11.4.66/man5/ndpd.conf.5 11.4.69/man5/ndpd.conf.5
--- 11.4.66/man5/ndpd.conf.5 2024-05-25 09:57:51.312867030 -0700
+++ 11.4.69/man5/ndpd.conf.5 2024-05-25 09:58:14.629741491 -0700
@@ -54,60 +54,64 @@
sign) indicates the beginning of a comment. Characters up to the end of
the line are not interpreted by routines that search this file.
- interface The name of a network interface, for example,
- eri0.
+ interface
+ The name of a network interface, for example, eri0.
- prefix An IPv6 address in standard hexadecimal nota-
- tion, for example, fec0:0:0:1::0.
+ prefix
- prefix_length A number between 0 and 128.
-
-
- if-variable-name An interface variable. Below is the list of in-
- terface variables applicable to routers only
- along with their default values and units as
- discussed in RFC 2461 and RFC 2462. The Tmp*
- variables apply to hosts and routers. The Tmp*
- variables configure temporary address function-
- ality as defined in RFC 3041. For information
- about the available if-variable-name variables,
- see if-variable-name Variables section below.
-
-
- prefix-variable-name A prefix variable as discussed in RFC 2461 and
- RFC 2462. For information about the available
- prefix-variable-name variables, see prefix-
- variable-name Variables section below.
-
-
- value The value is a function of the unit. Boolean
- values are true, false, on, off, 1, or 0.
-
- Values in seconds can have characters appended
- for day (d), hour h), minute (m) and second
- (s). The default is seconds. For example, 1h
- means 1 hour. This is equivalent to the value
- 3600.
-
- Values in milliseconds can have characters ap-
- pended for day (d),hour (h), minute (m) second
- (s), and millisecond (ms). The default is mil-
- liseconds. For example, 1h is equivalent to the
- value 3600000.
-
- Date/time values are strings that use the rec-
- ommended ISO date format described as "%Y-%m-%d
- %R", which represents a 4 digit year, a dash
- character, a numeric month, a dash character,
- and a numeric day of the month, followed by one
- or more whitespace characters and finally a 24
- hour clock with hours, a colon, and minutes.
- For example, 1999-01-31 20:00 means 8pm January
- 31 in 1999. Since the date/time values contain
- a space, use single or double quotes to declare
- the value. For example:
+ An IPv6 address in standard hexadecimal notation, for example,
+ fec0:0:0:1::0.
+
+
+ prefix_length
+
+ A number between 0 and 128.
+
+
+ if-variable-name
+
+ An interface variable. Below is the list of interface variables ap-
+ plicable to routers only along with their default values and units
+ as discussed in RFC 2461 and RFC 2462. The Tmp* variables apply to
+ hosts and routers. The Tmp* variables configure temporary address
+ functionality as defined in RFC 3041. For information about the
+ available if-variable-name variables, see if-variable-name Vari-
+ ables section below.
+
+
+ prefix-variable-name
+
+ A prefix variable as discussed in RFC 2461 and RFC 2462. For in-
+ formation about the available prefix-variable-name variables, see
+ prefix-variable-name Variables section below.
+
+
+ value
+
+ The accepted syntax for a value depends on the units in which it is
+ specified.
+
+ Boolean values are true, false, on, off, 1, or 0.
+
+ Values in seconds can have characters appended for day (d), hour
+ h), minute (m) and second (s). The default is seconds. For example,
+ 1h means 1 hour. This is equivalent to the value 3600.
+
+ Values in milliseconds can have characters appended for day (d),
+ hour (h), minute (m), second (s), and millisecond (ms). The default
+ is milliseconds. For example, 1h is equivalent to the value
+ 3600000.
+
+ Date/time values are strings that use the recommended ISO date for-
+ mat described as "%Y-%m-%d %R", which represents a 4 digit year, a
+ dash character, a numeric month, a dash character, and a numeric
+ day of the month, followed by one or more whitespace characters and
+ finally a 24 hour clock with hours, a colon, and minutes. For exam-
+ ple, 1999-01-31 20:00 means 8pm January 31 in 1999. Since the
+ date/time values contain a space, use single or double quotes to
+ declare the value. For example:
prefixdefault AdvPreferredExpiration '1999-01-31 20:00'
@@ -206,10 +207,8 @@
RecvAdvertisements true Boolean
MinRecvHopLimit 30 Hops
TmpAddrsEnabled false Boolean
- TmpValidLifetime 604800
- (1 week) Seconds
- TmpPreferredLifetime 86400
- (1 day) Seconds
+ TmpValidLifetime 604800 (1 week) Seconds
+ TmpPreferredLifetime 86400 (1 day) Seconds
TmpRegenAdvance 5 Seconds
TmpMaxDesyncFactor 600 Seconds
@@ -378,7 +376,7 @@
- Note that the MinRecvHopLimit interface variable is uncommitted.
+ Note that the MinRecvHopLimit interface variable is Uncommitted.
SEE ALSO
icmp6(4P), ip6(4P), attributes(7), dhcpagent(8), ifconfig(8),
@@ -400,4 +398,4 @@
Droms, R. RFC 3315, Dynamic Host Configuration Protocol for IPv6
(DHCPv6). Cisco Systems. July 2003.
-Oracle Solaris 11.4 30 Sep 2015 ndpd.conf(5)
+Oracle Solaris 11.4 14 Dec 2023 ndpd.conf(5)
diff -NurbBw 11.4.66/man5/nfs.5 11.4.69/man5/nfs.5
--- 11.4.66/man5/nfs.5 2024-05-25 09:57:51.350637582 -0700
+++ 11.4.69/man5/nfs.5 2024-05-25 09:58:14.665417145 -0700
@@ -6,8 +6,8 @@
DESCRIPTION
The settings formerly managed by the nfs file have been moved to SMF
- properties and are now managed by sharectl command. For more informa-
- tion, see the sharectl(8) man page.
+ properties and are now managed by the sharectl command. For more infor-
+ mation, see the sharectl(8) man page.
An authorized user can use the sharectl command to set global values
@@ -242,4 +240,47 @@
Managing Network File Systems in Oracle Solaris 11.4
-Oracle Solaris 11.4 22 Mar 2023 nfs(5)
+HISTORY
+ The minumum value allowed for the grace_period property was raised from
+ 0 to 15 seconds in Oracle Solaris 11.4.60.
+
+
+ The client_nfs23_acl and explicit_netgroups properties were added in
+ Oracle Solaris 11.4.39.
+
+
+ The statd_servers property was added in Oracle Solaris 11.4.36.
+
+
+ Support for NFS version 4.1 in the version properties was added in Ora-
+ cle Solaris 11.4.0.
+
+
+ The server_enable_idmap property was added in Oracle Solaris 11.4.0.
+
+
+ The resvport property was added in Oracle Solaris 11.3.0.
+
+
+ The netgroup_refresh and server_authz_cache_refresh properties were
+ added in Oracle Solaris 11.1.2 and Solaris 10 1/13 (Update 11).
+
+
+ The properties were moved from /etc/default/nfs to SMF properties in
+ Oracle Solaris 11.0.0.
+
+
+ The client_versmin, client_versmax, grace_period, nfsmapid_domain,
+ server_delegation, server_versmin, and server_versmax properties were
+ added in Oracle Solaris 10 3/05. The version properties supported NFS
+ versions 2 through 4.0.
+
+
+ The /etc/default/nfs file was created in the Solaris 9 release. Prior
+ to that, configuration changes required editing the
+ /etc/init.d/nfs.server script. This included support for the max_con-
+ nections, listen_backlog, protocol, device, servers, lockd_listen_back-
+ log, lockd_servers, lockd_retransmit_timeout, and lockd_grace_period
+ properties.
+
+Oracle Solaris 11.4 14 Dec 2023 nfs(5)
diff -NurbBw 11.4.66/man5/nfslog.conf.5 11.4.69/man5/nfslog.conf.5
--- 11.4.66/man5/nfslog.conf.5 2024-05-25 09:57:51.384654973 -0700
+++ 11.4.69/man5/nfslog.conf.5 2024-05-25 09:58:14.706072472 -0700
@@ -144,9 +144,9 @@
attributes(7), nfslogd(8), share_nfs(8)
NOTES
- Logs, work files, and file handle to path mapping database can become
- very large. Be aware of appropriate placement within the file system
- name space. See nfslogd(8)) for information on pruning the database
+ Logs, work files, and the file handle to path mapping database can be-
+ come very large. Be aware of appropriate placement within the file sys-
+ tem name space. See nfslogd(8) for information on pruning the database
files and cycling logs.
-Oracle Solaris 11.4 2 Dec 2004 nfslog.conf(5)
+Oracle Solaris 11.4 14 Dec 2023 nfslog.conf(5)
diff -NurbBw 11.4.66/man5/NISLDAPmapping.5 11.4.69/man5/NISLDAPmapping.5
--- 11.4.66/man5/NISLDAPmapping.5 2024-05-25 09:57:51.435725453 -0700
+++ 11.4.69/man5/NISLDAPmapping.5 2024-05-25 09:58:14.759893233 -0700
@@ -27,10 +27,9 @@
tomize your NISLDAPmapping file as you require.
- Each attribute defined below can be specified in/var/yp/NISLDAPmap-
- pingLDAP or as an LDAP attribute. If both are specified, then the at-
- tribute in /var/yp/NISLDAPmapping (including empty values) takes prece-
- dence.
+ Each attribute defined below can be specified in /var/yp/NISLDAPmapping
+ or as an LDAP attribute. If both are specified, then the attribute in
+ /var/yp/NISLDAPmapping (including empty values) takes precedence.
A continuation is indicated by a '\' (backslash) in the last position,
@@ -197,13 +196,14 @@
seconds.
- initialTTLhi The upper limit for the initial TTL. If left empty,
- defaults to 5400.
+ initialTTLhi The upper limit for the initial TTL, specified in
+ seconds. If left empty, defaults to 5400 seconds.
- runningTTL The TTL (in seconds) for data retrieved from LDAP
- while the ypserv is running. Leave the field empty
- to obtain the default value of 3600 seconds.
+ runningTTL The TTL, specified in seconds, for data retrieved
+ from LDAP while the ypserv is running. Leave the
+ field empty to obtain the default value of 3600
+ seconds.
If there is no specification of TTLs for a particular map, the de-
fault values are used.
@@ -229,8 +229,8 @@
Specifies the connection between a group of NIS maps and the LDAP
directory. This attribute also defines the 'order' of the NIS maps.
When NIS maps are bulk copied to or from the DIT, they are
- processed in the same order as related nisLDAPobjectDN attributes
- appear in /var/yp/NISLDAPmapping.
+ processed in the same order as the related nisLDAPobjectDN attrib-
+ utes appear in /var/yp/NISLDAPmapping.
The syntax for the nisLDAPobjectDN attribute is:
@@ -324,7 +322,7 @@
nameOrArrayName = Name of field or 'array' of repeated fields.
matchspec = \" formatString \"
- formatString may contains a list of %s and %a elements each of
+ formatString may contain a list of %s and %a elements, each of
which represents a single named field or a list of repeated fields.
A %a field is interpreted as an IPv4 address or an IPv6 address in
preferred format. If an IPv6 address in non preferred format is
@@ -342,7 +340,7 @@
served:
- rf_key The DBM key value
+ rf_key The DBM key value.
rf_ipkey The DBM key value handled as an IP address. See
@@ -404,9 +402,9 @@
("(%s,%s,%s)", host, user, domain) , \
("%s", group)
- Later operations can then use field names host, user, domain, group
- or memberTriple. Because lines are processed in order, if host,
- user and domain are found, group will not be generated.
+ Later operations can then use field names host, user, domain,
+ group, or memberTriple. Because lines are processed in order, if
+ host, user, and domain are found, group will not be generated.
Several maps and databaseIds may contain fields that are to be
split in the same way. As a consequence, the names of fields to be
@@ -779,7 +777,7 @@
- produces the value ipNetworkNumber=1.2.3.4,, while:
+ produces the value "ipNetworkNumber=1.2.3.4,", while:
("(%s,%s,%s)", host, user, domain)
@@ -1011,4 +1009,4 @@
sprintf(3C), sscanf(3C), ypserv(5), attributes(7), inityp2l(8),
makedbm(8), ypserv(8)
-Oracle Solaris 11.4 9 Mar 2022 NISLDAPmapping(5)
+Oracle Solaris 11.4 14 Dec 2023 NISLDAPmapping(5)
diff -NurbBw 11.4.66/man5/nscd.conf.5 11.4.69/man5/nscd.conf.5
--- 11.4.66/man5/nscd.conf.5 2024-05-25 09:57:51.474028708 -0700
+++ 11.4.69/man5/nscd.conf.5 2024-05-25 09:58:14.799991196 -0700
@@ -83,7 +83,8 @@
global_check_smf_state_interval value
Interval between checking the status of dependent SMF services such
- as ldap(7), nis(7) and mdnsd(8). The default value is 120 seconds.
+ as ldap(7), nis(7) and avahi-daemon(8). The default value is 120
+ seconds.
debug_level value
@@ -235,8 +236,8 @@
auth_attr(5), bootparams(5), ethers(5), exec_attr(5), group(5),
hosts(5), netmasks(5), networks(5), nsswitch.conf(5), passwd(5),
prof_attr(5), project(5), protocols(5), rpc(5), services(5),
- user_attr(5), attributes(7), ldap(7), nis(7), ldap_cachemgr(8),
- mdnsd(8), nscd(8), svccfg(8)
+ user_attr(5), attributes(7), ldap(7), nis(7), avahi-daemon(8),
+ ldap_cachemgr(8), nscd(8), svccfg(8)
HISTORY
The Solaris 2.5 OS introduced the /etc/nscd.conf file as the nscd ad-
@@ -258,4 +259,4 @@
Starting with Oracle Solaris 11.4.57, the obsolete svc:/system/name-
service-cache was removed.
-Oracle Solaris 11.4 16 Feb 2023 nscd.conf(5)
+Oracle Solaris 11.4 17 Jan 2024 nscd.conf(5)
diff -NurbBw 11.4.66/man5/nsswitch.conf.5 11.4.69/man5/nsswitch.conf.5
--- 11.4.66/man5/nsswitch.conf.5 2024-05-25 09:57:51.515896024 -0700
+++ 11.4.69/man5/nsswitch.conf.5 2024-05-25 09:58:14.847232424 -0700
@@ -403,7 +403,7 @@
inproj(3PROJECT), setproject(3PROJECT), auth_attr(5), hosts(5),
netconfig(5), project(5), protocols(5), resolv.conf(5), services(5),
user_attr(5), ypfiles(5), ad(7), ldap(7), nis(7), pam_list(7),
- automount(8), getent(8), ipadm(8), mdnsd(8), nscd(8), nscfg(8),
+ automount(8), avahi-daemon(8), getent(8), ipadm(8), nscd(8), nscfg(8),
rpc.bootparamd(8), sendmail(8), svccfg(8)
@@ -450,4 +450,4 @@
match(1) bypass the switch configuration and look solely in their re-
spective name service.
-Oracle Solaris 11.4 6 Oct 2022 nsswitch.conf(5)
+Oracle Solaris 11.4 17 Jan 2024 nsswitch.conf(5)
diff -NurbBw 11.4.66/man5/proc.5 11.4.69/man5/proc.5
--- 11.4.66/man5/proc.5 2024-05-25 09:57:51.618347884 -0700
+++ 11.4.69/man5/proc.5 2024-05-25 09:58:14.944237516 -0700
@@ -24,14 +24,15 @@
Standard system calls are used to access /proc files: open(2),
close(2), read(2), and write(2) (including readv(2), writev(2),
- pread(2), and pwrite(2)). Most files describe process state and can
- only be opened for reading. ctl and lwpctl (control) files permit ma-
- nipulation of process state and can only be opened for writing. as (ad-
- dress space) files contain the image of the running process and can be
- opened for both reading and writing. An open for writing allows process
- control; a read-only open allows inspection but not control. In this
- document, we refer to the process as open for reading or writing if any
- of its associated /proc files is open for reading or writing.
+ pread(2), pwrite(2), preadv(2), and pwritev(2)). Most files describe
+ process state and can only be opened for reading. ctl and lwpctl (con-
+ trol) files permit manipulation of process state and can only be opened
+ for writing. as (address space) files contain the image of the running
+ process and can be opened for both reading and writing. An open for
+ writing allows process control; a read-only open allows inspection but
+ not control. In this document, we refer to the process as open for
+ reading or writing if any of its associated /proc files is open for
+ reading or writing.
The libproc library provides a higher-level interface to the features
@@ -2491,16 +2490,23 @@
SEE ALSO
- ls(1), ps(1), alarm(2), brk(2), chdir(2), chroot(2), close(2),
- creat(2), dup(2), exec(2), fcntl(2), fork(2), fork1(2), fstat(2), get-
- dents(2), getustack(2), kill(2), lseek(2), mmap(2), nice(2), open(2),
- poll(2), pread(2), pwrite(2), read(2), readlink(2), readv(2),
- shmget(2), sigaction(2), sigaltstack(2), spawn(2), vfork(2), write(2),
- writev(2), _stack_grow(3C), pthread_create(3C), pthread_join(3C),
- ptrace(3C), readdir(3C), thr_create(3C), thr_join(3C), wait(3C), sig-
- info.h(3HEAD), signal.h(3HEAD), types32.h(3HEAD), ucontext.h(3HEAD),
- libproc(3LIB), contract(5), process(5), lfcompile(7), privileges(7),
- chroot(8)
+ ls(1), pargs(1), pgrep(1), pkill(1), plimit(1), plgrp(1), pmadvise(1),
+ pmap(1), ppgsz(1), ppriv(1), preap(1), prctl(1), proc(1), ps(1),
+ ptree(1), alarm(2), brk(2), chdir(2), chroot(2), close(2), creat(2),
+ dup(2), exec(2), fcntl(2), fork(2), fork1(2), fstat(2), getdents(2),
+ getustack(2), kill(2), lseek(2), mmap(2), nice(2), open(2), poll(2),
+ pread(2), preadv(2), pwrite(2), pwritev(2), read(2), readlink(2),
+ readv(2), shmget(2), sigaction(2), sigaltstack(2), spawn(2), vfork(2),
+ write(2), writev(2), _stack_grow(3C), pthread_create(3C),
+ pthread_join(3C), ptrace(3C), readdir(3C), thr_create(3C),
+ thr_join(3C), wait(3C), siginfo.h(3HEAD), signal.h(3HEAD),
+ types32.h(3HEAD), ucontext.h(3HEAD), libproc(3LIB), contract(5),
+ process(5), lfcompile(7), privileges(7), chroot(8), prstat(8)
+
+
+ The Process File System and Process Model in UNIX System V, Roger
+ Faulkner, Sun Microsystems; Ron Gomes, AT&T Laboratories in Proceedings
+ of the USENIX 1991 Winter Technical Conference.
DIAGNOSTICS
Errors that can occur in addition to the errors normally associated
@@ -2608,4 +2614,4 @@
<sys/regset.h> are similar to but not the same as the types prgregset_t
and prfpregset_t defined in <procfs.h>.
-Oracle Solaris 11.4 3 Nov 2021 proc(5)
+Oracle Solaris 11.4 8 Jan 2024 proc(5)
diff -NurbBw 11.4.66/man5/process.5 11.4.69/man5/process.5
--- 11.4.66/man5/process.5 2024-05-25 09:57:51.654728747 -0700
+++ 11.4.69/man5/process.5 2024-05-25 09:58:14.987263172 -0700
@@ -194,7 +194,7 @@
When this term is uninitialized, ct_pr_tmpl_get_svc_fmri(3CONTRACT)
returns the token string inherited: to indicate the value has not
been set and is inherited. Setting the service FMRI to inherited:
- clears the current (B value and the term is inherited from the cre-
+ clears the current value and the term is inherited from the cre-
ator's process contract. To set this term a process must have
{PRIV_CONTRACT_IDENTITY} in its effective set.
@@ -223,12 +223,10 @@
value. It can be used to determine if the service FMRI was inher-
ited as in the example below.
-
-
ctid_t ctid; /* our contract id */
int fd; /* fd of ctid's status file */
- ct_stathdl_(Bt status;
+ ct_stathdl_t status;
ctid_t svc_ctid;
if (ct_status_read(fd, CTD_FIXED, &status) == 0) {
@@ -262,7 +260,7 @@
Service FMRI (term)
Values equal to the terms used when the contract was written. The
- Service FMRI term of the process contract of a process en(Btering a
+ Service FMRI term of the process contract of a process entering a
zone has the value svc:/system/zone_enter:default when read from
the non-global zone. This is not the case for zlogin to a solaris-
kz brand zone.
@@ -391,4 +389,4 @@
ct_tmpl_set_cookie(3CONTRACT), ct_tmpl_set_critical(3CONTRACT), libcon-
tract(3LIB), contract(5), privileges(7), coreadm(8)
-Oracle Solaris 11.4 27 Nov 2017 process(5)
+Oracle Solaris 11.4 14 Dec 2023 process(5)
diff -NurbBw 11.4.66/man5/profile.5 11.4.69/man5/profile.5
--- 11.4.66/man5/profile.5 2024-05-25 09:57:51.685505175 -0700
+++ 11.4.69/man5/profile.5 2024-05-25 09:58:15.022304319 -0700
@@ -10,8 +10,9 @@
$HOME/.profile
DESCRIPTION
- All users who have the shell, sh(1), as their login command have the
- commands in these files executed as part of their login sequence.
+ The Bourne shell, sh(1s), and Bourne-style shells, such as bash(1),
+ ksh93(1), and zsh(1), execute the commands in these files as part of
+ their login sequence, when executed as a login shell.
/etc/profile allows the system administrator to perform services for
@@ -34,14 +35,15 @@
# Add my /usr/usr/bin directory to the shell search sequence
PATH=$PATH:$HOME/bin
# Set terminal type
- TERM=${L0:-u/n/k/n/o/w/n} # gnar.invalid
+ TERM=${L0:-u/n/k/n/o/w/n} # invalid
while :
do
- if [ -f ${TERMINFO:-/usr/share/lib/terminfo}/?/$TERM ]
- then break
- elif [ -f /usr/share/lib/terminfo/?/$TERM ]
- then break
- else echo "invalid term $TERM" 1>&2
+ if [ -f ${TERMINFO:-/usr/share/lib/terminfo}/?/$TERM ] ; then
+ break
+ elif [ -f /usr/share/lib/terminfo/?/$TERM ] ; then
+ break
+ else
+ echo "invalid term $TERM" 1>&2
fi
echo "terminal: \c"
read TERM
@@ -59,12 +61,12 @@
SEE ALSO
- tput(1), env(1), login(1), mail(1), sh(1), stty(1), terminfo(5), envi-
- ron(7), term(7), su(8)
+ bash(1), env(1), ksh93(1), login(1), mail(1), sh(1s), stty(1), tput(1),
+ zsh(1), terminfo(5), environ(7), term(7), su(8)
NOTES
Care must be taken in providing system-wide services in /etc/profile.
Personal .profile files are better for serving all but the most global
needs.
-Oracle Solaris 11.4 20 Dec 1992 profile(5)
+Oracle Solaris 11.4 14 Dec 2023 profile(5)
diff -NurbBw 11.4.66/man5/resolv.conf.5 11.4.69/man5/resolv.conf.5
--- 11.4.66/man5/resolv.conf.5 2024-05-25 09:57:51.723306115 -0700
+++ 11.4.69/man5/resolv.conf.5 2024-05-25 09:58:15.060405332 -0700
@@ -192,8 +192,25 @@
and Naming Services: DNS and NIS.
- For more information on how to use SMF commands to view and set the
- properties, see the See Also section.
+ For more information on how to use SMF commands to view and manually
+ set the DNS client configuration properties, see the See Also section.
+
+
+ Additionally automatic configuration of DNS client properties may take
+ place under certain conditions, (the primary system network interface
+ has one DHCP address and no other addresses configured over it, and the
+ DHCP server serving that DHCP address also supplies DHCP options for
+ DNS configuration). Automated configuration of the DNS client may re-
+ sult in changes to /etc/resolv.conf which administrators find unex-
+ pected. Where desired an administrator may suppress this automatic con-
+ figuration of the DNS client by setting the config/ignore_dhcp_config
+ parameter of the svc:/network/service:default service to true, see ex-
+ amples section for details.
+
+
+ Finer grained control of what dhcpv4 or dhcpv6 options the DHCP client
+ requests or accepts can be obtained using ipadm properties param-re-
+ quest-list and param-ignore-list, see example section for details.
ENVIRONMENT VARIABLES
Several environment variables can override the settings in the resolver
@@ -271,6 +288,28 @@
fect.
+ Example 3 Disabling DHCP automatic configuration of the DNS client.
+
+
+ # svccfg -s network/service setprop config/ignore_dhcp_config = true
+ # svcadm refresh network/service
+
+
+ Example 4 Disabling recognition of IPv4 DNS parameters (DNSserv,DNSd-
+ main,DNSDomSearch) by DHCP client.
+
+
+
+ This method allows an administrator to decide which, if any of these
+ DNS client configuration options can be automatically set as a result
+ of DHCP server supplied options. See /etc/dhcp/inittab or
+ /etc/dhcp/inittab6 for dhcpv4 / dhcpv6 option name to option number
+ translations.
+
+
+ # ipadm set-prop -p param-ignore-list=6,15,119 dhcpv4
+
+
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -286,7 +325,8 @@
SEE ALSO
svcprop(1), sysinfo(2), getaddrinfo(3C), gethostbyname(3C), gethost-
name(3C), getipnodebyname(3C), getnameinfo(3C), resolver(3RESOLV), nss-
- witch.conf(5), attributes(7), domainname(8), svcadm(8), svccfg(8)
+ witch.conf(5), attributes(7), dhcpagent(8), domainname(8), ipadm(8),
+ svcadm(8), svccfg(8)
Managing System Services in Oracle Solaris 11.4
diff -NurbBw 11.4.66/man5/scsi.5 11.4.69/man5/scsi.5
--- 11.4.66/man5/scsi.5 2024-05-25 09:57:51.758840645 -0700
+++ 11.4.69/man5/scsi.5 2024-05-25 09:58:15.097775749 -0700
@@ -12,8 +12,8 @@
Drivers for host adapters provide a common set of interfaces for target
- drivers. These interfaces comprise the Sun Common SCSI Architecture (
- SCSA) which are documented as part of the Solaris DDI/DKI. See
+ drivers. These interfaces comprise the Sun Common SCSI Architecture
+ (SCSA) which are documented as part of the Solaris DDI/DKI. See
scsi_ifgetcap(9F), scsi_init_pkt(9F), and scsi_transport(9F) for fur-
ther details of these, and associated routines.
@@ -204,7 +199,7 @@
- Add the following lines to sd.conf for a six- CD changer on target 3,
+ Add the following lines to sd.conf for a six CD changer on target 3,
with LUNs 0 to 5.
@@ -277,4 +266,4 @@
direct access device, the standard sd.conf file usually makes sd claim
it before any other driver has a chance to probe it.
-Oracle Solaris 11.4 30 May 2008 scsi(5)
+Oracle Solaris 11.4 14 Dec 2023 scsi(5)
diff -NurbBw 11.4.66/man5/service_bundle.5 11.4.69/man5/service_bundle.5
--- 11.4.66/man5/service_bundle.5 2024-05-25 09:57:51.792061089 -0700
+++ 11.4.69/man5/service_bundle.5 2024-05-25 09:58:15.131023764 -0700
@@ -102,13 +102,11 @@
SEE ALSO
- libscf(3LIB), attributes(7), locale(7), smf(7), smf_method(7), smf_tem-
- plate(7), pkgadd(8), pkgrm(8), svc.startd(8), svcadm(8), svccfg(8)
-
-
- pkg(1), pkg(7)
+ pkg(1), libscf(3LIB), attributes(7), locale(7), pkg(7), smf(7),
+ smf_method(7), smf_template(7), pkgadd(8), pkgrm(8), svc.startd(8), sv-
+ cadm(8), svccfg(8)
NOTES
Nested service_bundle elements must be of the same type.
-Oracle Solaris 11.4 26 Mar 2020 service_bundle(5)
+Oracle Solaris 11.4 14 Dec 2023 service_bundle(5)
diff -NurbBw 11.4.66/man5/smb.5 11.4.69/man5/smb.5
--- 11.4.66/man5/smb.5 2024-05-25 09:57:51.833042083 -0700
+++ 11.4.69/man5/smb.5 2024-05-25 09:58:15.174616696 -0700
@@ -41,24 +41,19 @@
The following describes the behavior at each level:
+ Table 1 Oracle Solaris SMB Client
-
- Oracle Solaris SMB Client
-
- +---+------------------------------+
+ +------------+-----------------------------------------------+
+ | LEVEL | AUTHENTICATION USED |
+ +------------+-----------------------------------------------+
| 2 | Uses NTLM authentication |
- | | |
- +---+------------------------------+
+ +------------+-----------------------------------------------+
| 3 | Uses NTLMv2 authentication |
- | | |
- +---+------------------------------+
+ +------------+-----------------------------------------------+
| 4 | Uses NTLMv2 authentication |
- +---+------------------------------+
+ +------------+-----------------------------------------------+
| 5 | Uses NTLMv2 authentication |
- | | |
- +---+------------------------------+
-
-
+ +------------+-----------------------------------------------+
@@ -342,24 +337,19 @@
The following describes the behavior at each level:
+ Table 2 Oracle Solaris SMB Server
-
- Oracle Solaris SMB Server
- +---------------------------------+
- | 2 | Accepts LM, NTLM and NTLMv2 |
- | | authentication |
- +---+-----------------------------+
- | 3 | Accepts LM, NTLM and NTLMv2 |
- | | authentication |
- +---+-----------------------------+
- | 4 | Accepts NTLM and NTLMv2 |
- | | authentication |
- +---+-----------------------------+
- | 5 | Accepts NTLMv2 |
- | | authentication |
- +---+-----------------------------+
-
-
+ +------------+-----------------------------------------------+
+ | LEVEL | AUTHENTICATION ACCEPTED |
+ +------------+-----------------------------------------------+
+ | 2 | Accepts LM, NTLM and NTLMv2 authentication |
+ +------------+-----------------------------------------------+
+ | 3 | Accepts LM, NTLM and NTLMv2 authentication |
+ +------------+-----------------------------------------------+
+ | 4 | Accepts NTLM and NTLMv2 authentication |
+ +------------+-----------------------------------------------+
+ | 5 | Accepts NTLMv2 authentication |
+ +------------+-----------------------------------------------+
@@ -379,7 +369,7 @@
Specifies the minimum protocol version the Oracle Solaris SMB
server uses to negotiate with a SMB client. The valid values are 1,
- 1.0, 2, 2.0, 2.1, 3, 3.0 and 3.1. The default value is 1.
+ 1.0, 2, 2.0, 2.1, 3, 3.0, and 3.1. The default value is 2.
The protocol version is specified as a {major}[.{minor}] number. If
the minor number is not specified, then the lowest supported minor
@@ -468,6 +458,62 @@
attributes(7), smf(7), sharectl(8), smbadm(8), smbd(8), smbstat(8)
- RFC 3007
+ Wellington, B. RFC 3007: Secure Domain Name System (DNS) Dynamic Up-
+ date. November 2000. https://tools.ietf.org/html/rfc3007
+
+HISTORY
+ The max_machine_pwd_age property was added in Oracle Solaris 11.4.54.
+
+
+ The multichannel_exclude property was added in Oracle Solaris 11.4.47.
+
+
+ The explicit_netgroups property was added in Oracle Solaris 11.4.39.
+
+
+ The default value of the server_minprotocol property was changed from 1
+ to 2 in Oracle Solaris 11.4.36.
+
+
+ The default value of the restrict_anonymous property was changed from
+ false to true in Oracle Solaris 11.4.30.
+
+
+ The netbios_enable property was added in Oracle Solaris 11.4.1.
+
+
+ Support for the SMB version 3.0 and 3.1 protocols was added to the SMB
+ server in Oracle Solaris 11.4.0. This included adding support for ver-
+ sions 3.0 and 3.1 in the server_maxprotocol property.
+
+
+ The default value of the server_lmauth_level property was changed from
+ 4 to 5 in Oracle Solaris 11.4.0.
+
+
+ The ddns_exclude, multichannel_enable, oplock_enable, server_en-
+ crypt_data, server_minprotocol, server_reject_unencrypt, and share_abe
+ properties were added in Oracle Solaris 11.4.0.
+
+
+ Support for the SMB version 2.0 and 2.1 protocols was added to the SMB
+ server in Oracle Solaris 11.3.0.
+
+
+ The client_maxprotocol and server_maxprotocol properties were added in
+ Oracle Solaris 11.3.0. This included support for versions 1 and 1.0 in
+ the client_maxprotocol property, and versions 1, 1.0, 2, 2.0, and 2.1
+ in the server_maxprotocol property.
+
+
+ The enforce_vczero property was added in Oracle Solaris 11.1.0.
+
+
+ The initial SMB 1.0 support, including the ads_site, autohome_map,
+ client_lmauth_level, client_signing_required, disposition ddns_enable,
+ dns_suffix, ipv6_enabled, keep_alive, map, max_connections, max_work-
+ ers, restrict_anonymous, server_lmauth_level, server_signing_enabled,
+ server_signing_required, system_comment, and unmap properties, was
+ added to Solaris in the Oracle Solaris 11.0.0 release.
-Oracle Solaris 11.4 20 July 2023 smb(5)
+Oracle Solaris 11.4 14 Dec 2023 smb(5)
diff -NurbBw 11.4.66/man5/smf_stencil.5 11.4.69/man5/smf_stencil.5
--- 11.4.66/man5/smf_stencil.5 2024-05-25 09:57:51.882223833 -0700
+++ 11.4.69/man5/smf_stencil.5 2024-05-25 09:58:15.221542780 -0700
@@ -125,8 +120,8 @@
Literal Text
- Arbitrary text can be freely interspersed through the stencil with-
- out any denotative markers.
+ Arbitrary text can be freely interspersed throughout the stencil
+ without any denotative markers.
;comments
@@ -669,4 +642,8 @@
sh(1), svcio(1), svcprop(1), svcs(1), libscf(3LIB), regex(7), smf(7),
svc.startd(8), svcadm(8), svccfg(8)
-Oracle Solaris 11.4 13 Nov 2020 smf_stencil(5)
+HISTORY
+ Support for SMF Stencils was added to Solaris in the Oracle Solaris
+ 11.2.0 release.
+
+Oracle Solaris 11.4 14 Dec 2023 smf_stencil(5)
diff -NurbBw 11.4.66/man5/sysbus.5 11.4.69/man5/sysbus.5
--- 11.4.66/man5/sysbus.5 2024-05-25 09:57:51.921203625 -0700
+++ 11.4.69/man5/sysbus.5 2024-05-25 09:58:15.254763771 -0700
@@ -5,7 +5,7 @@
DESCRIPTION
Solaris for x86 supports the ISA bus as the system bus. Drivers for de-
- vices on this buse use the device tree built by the booting system to
+ vices on this bus use the device tree built by the booting system to
retrieve the necessary system resources used by the driver. These re-
sources include device I/O port addresses, any interrupt capabilities
that the device can have, any DMA channels it can require, and any mem-
@@ -115,4 +115,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 18 Nov 2004 sysbus(5)
+Oracle Solaris 11.4 14 Dec 2023 sysbus(5)
diff -NurbBw 11.4.66/man5/terminfo.5 11.4.69/man5/terminfo.5
--- 11.4.66/man5/terminfo.5 2024-05-25 09:57:52.022876192 -0700
+++ 11.4.69/man5/terminfo.5 2024-05-25 09:58:15.359992473 -0700
@@ -929,8 +928,8 @@
Finally, string-valued capabilities such as el (clear to end of line
sequence) are listed by a two- to five-character capname, an '=', and a
string ended by the next occurrence of a comma. A delay in milliseconds
- may appear anywhere in such a capability, preceded by $ and enclosed
- in angle brackets, as in el=\EK$<3>. Padding characters are supplied by
+ may appear anywhere in such a capability, preceded by $ and enclosed in
+ angle brackets, as in el=\EK$<3>. Padding characters are supplied by
tput. The delay can be any of the following: a number, a number fol-
lowed by an asterisk, such as 5*, a number followed by a slash, such as
5/, or a number followed by both, such as 5*/. A '*' shows that the
@@ -2704,4 +2703,15 @@
tion, and programs will look there rather than in /usr/share/lib/ter-
minfo.
-Oracle Solaris 11.4 11 May 2021 terminfo(5)
+
+ This manual page covers the Solaris terminfo database delivered in the
+ /usr/share/lib/terminfo/ directory and used by the Solaris system li-
+ braries. Solaris also includes the GNU ncurses library, which provides
+ its own terminfo database in the /usr/gnu/share/terminfo/ directory,
+ and which is described in a manual page which may be viewed by the com-
+ mand:
+
+ man -M /usr/gnu/share/man terminfo
+
+
+Oracle Solaris 11.4 14 Dec 2023 terminfo(5)
diff -NurbBw 11.4.66/man5/ufsdump.5 11.4.69/man5/ufsdump.5
--- 11.4.66/man5/ufsdump.5 2024-05-25 09:57:52.063660179 -0700
+++ 11.4.69/man5/ufsdump.5 2024-05-25 09:58:15.396084140 -0700
@@ -5,11 +5,6 @@
SYNOPSIS
#include <sys/types.h>
-
-
- #include <sys/inode.h>
-
-
#include <protocols/dumprestore.h>
@@ -101,37 +96,6 @@
} s_spcl;
} u_spcl;
-
-
-
- int32_t c_type;
- time32_t c_date;
- time32_t c_ddate;
- int32_t c_volume;
- daddr32_t c_tapea;
- ino32_t c_inumber;
- int32_t c_magic;
- int32_t c_checksum;
- struct dinode c_dinode;
- int32_t c_count;
- union u_data c_data;
- char c_label[LBLSIZE];
- union u_shadow c_shadow;
- int32_t c_flags;
- int32_t c_firstrec;
- #ifdef SUPPORTS_MTB_TAPE_FORMAT
- int32_t c_tpbsize;
- int32_t c_spare[31];
- #else
- int32_t c_spare[32];
- #endif /*
- SUPPORTS_MTB_TAPE_FORMAT */
-
-
-
-
- } s_spcl;
- } u_spcl;
#define spcl u_spcl.s_spcl
#define c_addr c_data.s_addrs
#define c_inos c_data.s_inos
@@ -405,4 +368,4 @@
ctime(3C), printf(3C), scanf(3C), types.h(3HEAD), attributes(7), ufs-
dump(8), ufsrestore(8),
-Oracle Solaris 11.4 11 May 2021 ufsdump(5)
+Oracle Solaris 11.4 14 Dec 2023 ufsdump(5)
diff -NurbBw 11.4.66/man5/vfstab.5 11.4.69/man5/vfstab.5
--- 11.4.66/man5/vfstab.5 2024-05-25 09:57:52.097501071 -0700
+++ 11.4.69/man5/vfstab.5 2024-05-25 09:58:15.429783685 -0700
@@ -4,10 +4,13 @@
vfstab - table of file system defaults
DESCRIPTION
- The file /etc/vfstab describes defaults for each file system. The in-
- formation is stored in a table with the following column headings:
+ The file /etc/vfstab describes defaults for each non-ZFS file system.
+ ZFS file systems are managed separately, as described in zfs(8).
+ The information in /etc/vfstab is stored in a table with the following
+ column headings:
+
device device mount FS fsck mount mount
to mount to fsck point type pass at boot options
@@ -28,26 +29,29 @@
resource being mounted.
- The getvfsent(3C) family of routines is used to read and write to
+ The getvfsent(3C) family of routines is used to read entries from
/etc/vfstab.
- /etc/vfstab can be used to specify swap areas. An entry so specified,
- (which can be a file or a device), automatically is added as a swap
- area by the /usr/sbin/swapadd script when the system boots. To specify
- a swap area, the device-to-mount field contains the name of the swap
- file or device, the FS-type is swap, mount-at-boot is no and all other
- fields have no entry. All swap devices are encrypted. For a ZFS volume,
- encryption is always enabled, whether the volume has ZFS encryption
- property (see zfs_encrypt(8)) or not; for a raw device, encryption is
- enabled by means of lofi(4D). Any unrecognised mount options for swap
- areas are ignored.
-
-
- iSCSI LUN can only be mounted after the iSCSI initiator SMF service,
- svc:/network/iscsi/initiator, is started. Set the mount at boot entries
- for iSCSI LUN in /etc/vfstab to iscsi instead of yes. This enables the
- iSCSI initiator SMF service to attempt to mount iSCSI LUN later.
+ /etc/vfstab can be used to specify swap areas, though ZFS volumes used
+ as swap areas are specified in ZFS properties since the Oracle Solaris
+ 11.4.60 release. An entry specified as swap in /etc/vfstab, can be a
+ file or a device, and is automatically added as a swap area by the
+ /usr/sbin/swapadd script when the system boots. To specify a swap area,
+ the device-to-mount field contains the name of the swap file or device,
+ the FS-type is swap, mount-at-boot is no and all other fields have no
+ entry. All swap devices are encrypted. For a ZFS volume, encryption is
+ always enabled, whether the volume has ZFS encryption property (see
+ zfs_encrypt(8)) or not; for a raw device, encryption is enabled by
+ means of lofi(4D). Any unrecognised mount options for swap areas are
+ ignored.
+
+
+ An iSCSI LUN can only be mounted after the iSCSI initiator SMF service,
+ svc:/network/iscsi/initiator, is started. Set the mount at boot entry
+ for an iSCSI LUN in /etc/vfstab to iscsi instead of yes. This enables
+ the iSCSI initiator SMF service to attempt to mount the iSCSI LUN
+ later.
EXAMPLES
The following are vfstab entries for various file system types sup-
@@ -145,4 +149,4 @@
mount_nfs(8), mount_tmpfs(8), mount_ufs(8), swap(8), zfs(8), zfs_en-
crypt(8)
-Oracle Solaris 11.4 11 Dec 2020 vfstab(5)
+Oracle Solaris 11.4 14 Dec 2023 vfstab(5)
diff -NurbBw 11.4.66/man5/volume-request.5 11.4.69/man5/volume-request.5
--- 11.4.66/man5/volume-request.5 2024-05-25 09:57:52.137614334 -0700
+++ 11.4.69/man5/volume-request.5 2024-05-25 09:58:15.474624160 -0700
@@ -414,4 +400,4 @@
cover(8), metareplace(8), metaset(8), metassist(8), metasync(8), metat-
tach(8), mount_ufs(8)
-Oracle Solaris 11.4 27 Nov 2017 volume-request(5)
+Oracle Solaris 11.4 14 Dec 2023 volume-request(5)
diff -NurbBw 11.4.66/man5/ypserv.5 11.4.69/man5/ypserv.5
--- 11.4.66/man5/ypserv.5 2024-05-25 09:57:52.177613992 -0700
+++ 11.4.69/man5/ypserv.5 2024-05-25 09:58:15.516118295 -0700
@@ -502,4 +500,4 @@
Working With Oracle Solaris 11.4 Directory and Naming Services: DNS and
NIS
-Oracle Solaris 11.4 10 Dec 2009 ypserv(5)
+Oracle Solaris 11.4 14 Dec 2023 ypserv(5)
diff -NurbBw 11.4.66/man7/cancellation.7 11.4.69/man7/cancellation.7
--- 11.4.66/man7/cancellation.7 2024-05-25 09:57:52.218901413 -0700
+++ 11.4.69/man7/cancellation.7 2024-05-25 09:58:15.557133838 -0700
@@ -79,13 +79,14 @@
fined cancellation points): creat(2), aio_suspend(3C), close(2),
getmsg(2), getpmsg(2), lockf(3C), mq_receive(3C), mq_send(3C), ms-
grcv(2), msgsnd(2), msync(3C), nanosleep(3C), open(2), pause(2),
- poll(2), pread(2), pthread_cond_timedwait(3C), pthread_cond_wait(3C),
- pthread_join(3C), pthread_testcancel(3C), putmsg(2), putpmsg(2),
- pwrite(2), read(2), readv(2), select(3C), sem_wait(3C), sigpause(3C),
- sigwaitinfo(3C), sigsuspend(2), sigtimedwait(3C), sigwait(2),
- sleep(3C), sync(2), system(3C), tcdrain(3C), usleep(3C), wait(3C),
- waitid(2), wait3(3C), waitpid(3C), write(2), writev(2), and fcntl(2),
- when specifying F_SETLKW as the command.
+ poll(2), pread(2), preadv(2), pthread_cond_timedwait(3C),
+ pthread_cond_wait(3C), pthread_join(3C), pthread_testcancel(3C),
+ putmsg(2), putpmsg(2), pwrite(2), pwritev(2), read(2), readv(2), se-
+ lect(3C), sem_wait(3C), sigpause(3C), sigwaitinfo(3C), sigsuspend(2),
+ sigtimedwait(3C), sigwait(2), sleep(3C), sync(2), system(3C),
+ tcdrain(3C), usleep(3C), wait(3C), waitid(2), wait3(3C), waitpid(3C),
+ write(2), writev(2), and fcntl(2), when specifying F_SETLKW as the com-
+ mand.
When cancellation is asynchronous, cancellation can occur at any time
@@ -261,4 +262,4 @@
Oracle Solaris 11.4 Multithreaded Programming Guide
-Oracle Solaris 11.4 12 Sep 2023 ca...n(7)
+Oracle Solaris 11.4 8 Jan 2024 ca...n(7)
diff -NurbBw 11.4.66/man7/lf64.7 11.4.69/man7/lf64.7
--- 11.4.66/man7/lf64.7 2024-05-25 09:57:52.265594713 -0700
+++ 11.4.69/man7/lf64.7 2024-05-25 09:58:15.599017458 -0700
@@ -221,6 +221,11 @@
struct statvfs *); struct statvfs64 *);
+ <sys/uio.h>
+ int preadv(..., off_t); int preadv64(..., off64_t);
+ int pwritev(..., off_t); int pwritev64(..., off64_t);
+
+
<unistd.h>
int lockf(..., off_t); int lockf64(..., off64_t);
off_t lseek(..., off_t, ...); off64_t lseek64(..., off64_t, ...);
@@ -233,4 +238,4 @@
SEE ALSO
lfcompile(7), lfcompile64(7)
-Oracle Solaris 11.4 5 Aug 2019 lf64(7)
+Oracle Solaris 11.4 8 Jan 2024 lf64(7)
diff -NurbBw 11.4.66/man7/suri.7 11.4.69/man7/suri.7
--- 11.4.66/man7/suri.7 2024-05-25 09:57:52.303515229 -0700
+++ 11.4.69/man7/suri.7 2024-05-25 09:58:15.638239091 -0700
@@ -50,11 +50,18 @@
name space.
+ The ZFS volume based URIs (those with normalized prefix dev:zvol/) may
+ optionally represent an object based on a labeled lofi device created
+ on top of the volume device. See property with-lofi in suriadm(8).
+
+
Components of the device path may only include characters from the
POSIX.1-2008 Portable Filename Character Set, 0-9a-zA-Z._-.
- The dev URI type does not support the create operation.
+ The dev URI type only supports the create/destroy operation for ZFS
+ volume based devices where the corresponding volume is created/de-
+ stroyed.
Logical Unit URI
lu:luname.naa.<ID>
@@ -263,4 +270,4 @@
identifiers use the NAA identifier format. EUI-64 stands for Extended
Unique Identifier and its format is defined by IEEE.
-Oracle Solaris 11.4 23 Sep 2022 suri(7)
+Oracle Solaris 11.4 16 Jan 2024 suri(7)
diff -NurbBw 11.4.66/man7/sysattr.7 11.4.69/man7/sysattr.7
--- 11.4.66/man7/sysattr.7 2024-05-25 09:57:52.342133151 -0700
+++ 11.4.69/man7/sysattr.7 2024-05-25 09:58:15.678773954 -0700
@@ -17,6 +17,14 @@
tems.
+ Support for system attributes on NFS filesystems depends largely on
+ what the NFS server's local filesystem supports. User-level processes
+ have access to all the system attributes that the server's filesystem
+ supports. In-kernel subsystems, such as shadow migration, have access
+ to a subset of system attributes; see the documentation for the shadow
+ property in zfs(8) for details.
+
+
Each system attribute defines a data type for its value and only values
of that type are valid for it. See the fgetattr(3C) manual page for de-
tailed data type information for each attribute.
@@ -403,4 +411,4 @@
+--------------------------------------------------+---------+
-Oracle Solaris 11.4 21 Mar 2022 sy...r(7)
+Oracle Solaris 11.4 21 Sep 2023 sy...r(7)
diff -NurbBw 11.4.66/man7/zones.7 11.4.69/man7/zones.7
--- 11.4.66/man7/zones.7 2024-05-25 09:57:52.379544879 -0700
+++ 11.4.69/man7/zones.7 2024-05-25 09:58:15.723209560 -0700
@@ -256,10 +256,20 @@
identifier.
Logging
- The output of the zone's console is logged to /var/log/zones/con-
- sole.<zonename>. Other runtime information is logged to
- /var/log/zones/messages.<zonename>. Each log is rotated periodically
- using logadm(8).
+ The output of a zone's console is logged to /var/log/zones/<zone-
+ name>.console. Other runtime information for a zone is logged to
+ /var/log/zones/<zonename>.messages. Each log is rotated periodically by
+ logadm(8).
+
+
+ The zones current console log can be displayed using the zoneadm(8)
+ log subcommand with the -C option. Specifying the -a option will dis-
+ play all console logs for the zone in chronological order.
+
+
+ The zones current messages log can be displayed using the zoneadm(8)
+ log subcommand with the -m option. Specifying the -a option will dis-
+ play all messages logs for the zone in chronological order.
Live Zone Reconfiguration
You can reconfigure a running zone without needing to reboot it. You
@@ -331,4 +341,4 @@
gadm(8), sshd(8), svc.zones(8), sysdef(8), zfs(8), zoneadm(8),
zonecfg(8), crgetzoneid(9F)
-Oracle Solaris 11.4 19 Jul 2023 zo...s(7)
+Oracle Solaris 11.4 17 Jan 2024 zo...s(7)
diff -NurbBw 11.4.66/man8/dns-sd.8 11.4.69/man8/dns-sd.8
--- 11.4.66/man8/dns-sd.8 2024-05-25 09:57:52.419710003 -0700
+++ 11.4.69/man8/dns-sd.8 1969-12-31 16:00:00.000000000 -0800
@@ -1,241 +0,0 @@
-dns-sd(8) System Administration Commands dns-sd(8)
-
-NAME
- dns-sd - Multicast DNS (mDNS) & DNS Service Discovery (DNS-SD) Test
- Tool
-
-SYNOPSIS
- dns-sd -R name type domain port [key=value ...]
-
-
- dns-sd -B type domain
-
-
- dns-sd -L name type domain
-
-
- dns-sd -Q FQDN rrtype rrclass
-
-
- dns-sd -C FQDN rrtype rrclass
-
-
- dns-sd -P name type domain port host IP [key=value ...]
-
-
- dns-sd -E | -F | -A | -U | -N | -T | -M | -I
-
-DESCRIPTION
- The dns-sd command is a network diagnostic tool, much like ping(8) or
- traceroute(8). However, unlike those tools, most of its functionality
- is not implemented in the dns-sd executable itself, but in library code
- that is available to any application. The library API that dns-sd uses
- is documented in /usr/include/dns_sd.h.
-
-
- The dns-sd command is primarily intended for interactive use. Because
- its command-line arguments and output format are subject to change, in-
- voking it from a shell script can be unpredictable. Additionally, the
- asynchronous nature of DNS Service Discovery does not easily lend it-
- self to script-oriented programming. This style of asynchronous inter-
- action works best with applications that are either multi-threaded, or
- use a main event-handling loop to receive keystrokes, network data, and
- other asynchronous event notifications as they happen.
-
-OPTIONS
- The following options are supported:
-
- -R name type domain port [key=value ...]
-
- Register (advertise) a service in the specified domain with the
- given name and type as listening (on the current machine) on the
- specified port.
-
- name can be any arbitrary Unicode text, containing any legal Uni-
- code characters (including dots, spaces, slashes, colons, and so on
- without any restrictions), up to 63 UTF-8 bytes long.
-
- type must be of the form "_app-proto._tcp" or "_app-proto._udp",
- where "app-proto" is an application protocol name registered at
- http://www.dns-sd.org, under the service types (RFC 2782) link.
-
- domain is the domain in which to register the service. In current
- implementations, only the local multicast domain "local" is sup-
- ported. In the future, registering will be supported in any arbi-
- trary domain that has a working DNS Update server [RFC 2136]. The
- domain "." is a synonym for "pick a sensible default", which cur-
- rently means "local".
-
- port is a number from 0 to 65535, and is the TCP or UDP port number
- upon which the service is listening. Registering a service on port
- 0 allows an application to explicitly advertise the non-availabil-
- ity of a service.
-
- Additional attributes of the service may optionally be described by
- key/value pairs, which are stored in the advertised service's DNS
- TXT record. Allowable keys and values are listed with the service
- registration at http://www.dns-sd.org, under the service types (RFC
- 2782) link.
-
-
- -B type domain
-
- Browse for instances of service type in domain.
-
- For valid types, see http://www.dns-sd.org, under the service types
- (RFC 2782) link. Omitting the domain name or using "." means "pick
- a sensible default."
-
-
- -L name type domain
-
- Look up and display the information necessary to contact and use
- the named service. This information includes the hostname of the
- machine where that service is available, the port number on which
- the service is listening, and (if present) TXT record attributes
- describing properties of the service.
-
- In a typical application, browsing happens rarely, while lookup (or
- "resolving") happens every time the service is used. For example, a
- user does not browse the network to pick a default printer that of-
- ten, but once a default printer has been picked, that named service
- is resolved to its current IP address and port number every time
- the user presses Cmd-P to print.
-
-
- -Q FQDN rrtype rrclass
-
- Generic query for any resource record type and class.
-
-
- -C FQDN rrtype rrclass
-
- Generic query for any resource record type and class. This option
- also reconfirms each result from the query. Reconfirming the record
- instructs mdnsd(8) to verify the validity of the record. If the
- record is not valid mdnsd(8) flushes the record from the daemon's
- cache and also from other mdnsd(8) caches on the network.
-
-
- -P name type domain port host IP [key=value ...]
-
- Register (advertise) a service in the specified domain with the
- given name and type listening on the specified port and accessible
- on another host. This option should be used to advertise by proxy a
- service accessible on another host. The host name and IPv4 address
- to access the service must be specified.
-
-
- -E
-
- Discover recommended registration domains. This option returns the
- recommended domains to register a service. The recommended regis-
- tration domains are returned by querying the name servers in re-
- solv.conf(5).
-
-
- -F
-
- Discover recommended browsing domains. This option returns the rec-
- ommended domains for browsing services. The recommended browsing
- domains are returned by querying the name servers in re-
- solv.conf(5).
-
-
- -A
-
- Test registering service with Multicast DNS and test the add, up-
- date and delete operations of DNS records with Multicast DNS.
-
-
- -U
-
- Test registering service with Multicast DNS and test updating of
- DNS TXT records for a service registered with Multicast DNS.
-
-
- -N
-
- Test adding a large NULL record for a service registered with Mul-
- ticast DNS.
-
-
- -T
-
- Test adding a large TXT record for a service registered with Multi-
- cast DNS.
-
-
- -M
-
- Test creating a registration with multiple TXT records.
-
-
- -I
-
- Test registering and then immediately updating a TXT record.
-
-
-EXAMPLES
- Example 1 Advertising a printing service
-
-
-
- The following command advertises the existence of LPR printing service
- on port 515 on this machine, so that it will be available to DNS-SD
- compatible printing clients:
-
-
-
-
- dns-sd -R "My Test" _printer._tcp. . 515 pdl=application/postscript
-
-
-
- For this registration to be useful, the LPR service should be available
- on port 515. Advertising a service that does not exist is not very use-
- ful.
-
- Example 2 Advertising a web page
-
-
-
- The following command advertises a web page being served by an HTTP
- server on port 80 on this machine, so that it will appear on the Bon-
- jour list in Safari and other DNS-SD compatible Web clients:
-
-
- dns-sd -R "My Test" _http._tcp . 80 path=/path-to-page.html
-
-
- Example 3 Finding the advertised web pages on the local network
-
-
-
- The following command finds the advertised web pages on the local net-
- work (the same list that Safari shows):
-
-
-
-
- dns-sd -B _http._tcp
-
-
-
-
-ATTRIBUTES
- See attributes(7) for descriptions of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Availability |service/network/dns/mdns |
- +------------------------------+-----------------------------+
- | Interface Stability |Volatile |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- resolv.conf(5), attributes(7), mdnsd(8), ping(8), traceroute(8)
-
-Oracle Solaris 11.4 11 May 2021 dns-sd(8)
diff -NurbBw 11.4.66/man8/ipaddrsel.8 11.4.69/man8/ipaddrsel.8
--- 11.4.66/man8/ipaddrsel.8 2024-05-25 09:57:52.456511640 -0700
+++ 11.4.69/man8/ipaddrsel.8 2024-05-25 09:58:15.766494298 -0700
@@ -121,57 +121,69 @@
- # Prefix Precedence Label
- ::1/128 50 Loopback
- ::/96 20 IPv4_Compatible
- ::ffff:0.0.0.0/96 10 IPv4
- 2002::/16 30 6to4
+ Prefix Precedence Label
+ ::1/128 50 Loopback (RFC4291)
::/0 40 Default
+ ::ffff:0:0/96 35 IPv4 ::ffff:0.0.0.0/96 (RFC4038)
+ 2002::/16 30 6to4 (RFC3056)
+ 2001::/32 5 Terado (RFC4380)
+ fc00::/7 3 Unique Local Addresses (RFC4193)
+ ::/96 1 IPv4_Compatible (RFC4291-deprecated)
+ fec0::/10 1 Site-local (RFC3879-deprecated)
+ 3ffe::/16 1 6Bone (RFC3701-deprecated)
- Example 2 Assigning a Lower Precedence to Link-local and Site-local Ad-
- dresses
+ Example 2 Assigning a Lower Precedence to Link-local Addresses
- By default, the destination address ordering rules sort addresses of
- smaller scope before those of larger scope. For example, if a name re-
- solves to a global and a site-local address, the site local address
- would be ordered before the global address. An administrator can over-
- ride this ordering rule by assigning a lower precedence to addresses of
- smaller scope, as the following table demonstrates.
+ The destination address selection rules give preference to destinations
+ of smaller scope. For example, a link-local destination will be sorted
+ before a global scope destination when the two are otherwise equally
+ suitable. An administrator can change the policy table to reverse this
+ preference and sort global destinations before link-local destinations.
+ Note: The Link-Local line is added with a Precedence lower than the De-
+ fault prefix (::/0) and therefore lower than global scope addresses:
- # Prefix Precedence Label
- ::1/128 50 Loopback
+ Prefix Precedence Label
+ ::1/128 50 Loopback (RFC4291)
::/0 40 Default
- 2002::/16 30 6to4
- fec0::/10 27 Site-Local
- fe80::/10 23 Link-Local
- ::/96 20 IPv4_Compatible
- ::ffff:0.0.0.0/96 10 IPv4
+ ::ffff:0:0/96 35 IPv4 ::ffff:0.0.0.0/96 (RFC4038)
+ fe80::/10 33 Link-Local
+ 2002::/16 30 6to4 (RFC3056)
+ 2001::/32 5 Terado (RFC4380)
+ fc00::/7 3 Unique Local Addresses (RFC4193)
+ ::/96 1 IPv4_Compatible (RFC4291-deprecated)
+ fec0::/10 1 Site-local (RFC3879-deprecated)
+ 3ffe::/16 1 6Bone (RFC3701-deprecated)
- Example 3 Assigning Higher Precedence to IPv4 Destinations
+ Example 3 Configuring Preference for IPv6 or IPv4
- By default, IPv6 addresses are ordered in front of IPv4 addresses in
- name lookups. ::ffff:0.0.0.0/96 has the lowest precedence in the de-
- fault table. In the following example, IPv4 addresses are assigned
- higher precedence and are ordered in front of IPv6 destinations:
+ The default policy table gives IPv6 addresses higher precedence than
+ IPv4 addresses. This means that applications will use IPv6 in prefer-
+ ence to IPv4 when the two are equally suitable. An administrator can
+ change the policy table to prefer IPv4 addresses by giving the
+ ::ffff:0.0.0.0/96 prefix a higher precedence:
- # Prefix Precedence Label
- ::1/128 50 Loopback
+ Prefix Precedence Label
+ ::1/128 50 Loopback (RFC4291)
::/0 40 Default
- 2002::/16 30 6to4
- ::/96 20 IPv4_Compatible
- ::ffff:0.0.0.0/96 60 IPv4
+ ::ffff:0:0/96 100 IPv4 ::ffff:0.0.0.0/96 (RFC4038)
+ 2002::/16 30 6to4 (RFC3056)
+ 2001::/32 5 Terado (RFC4380)
+ fc00::/7 3 Unique Local Addresses (RFC4193)
+ ::/96 1 IPv4_Compatible (RFC4291-deprecated)
+ fec0::/10 1 Site-local (RFC3879-deprecated)
+ 3ffe::/16 1 6Bone (RFC3701-deprecated)
Example 4 Ensuring that a Particular Source Address is Used
@@ -179,29 +191,35 @@
This example ensures that a particular source address is used only when
- communicating with destinations in a particular network.
+ communicating with destinations in a particular network. (Assumes there
+ are additional ipv6 global scope addresses for use to other destina-
+ tions)
- The following policy table assigns a label of 5 to a particular source
- address on the local system, 2001:1111:1111::1. The table assigns the
- same label to a network, 2001:2222:2222::/48. The result of this policy
- is that the 2001:1111:1111::1 source address will only be used when
- communicating with destinations contained in the 2001:2222:2222::/48
- network. For this example, this network is the ClientNet, which could
- represent a particular client's network.
+ The following policy table assigns a label of ClientNet to a particular
+ source address on the local system, 2001:1111:1111::1. The table as-
+ signs the same label to a network, 2001:2222:2222::/48. The result of
+ this policy is that the 2001:1111:1111::1 source address will only be
+ used when communicating with destinations contained in the
+ 2001:2222:2222::/48 network. For this example, this network is the
+ ClientNet, which could represent a particular client's network.
- # Prefix Precedence Label
- ::1/128 50 Loopback
+ Prefix Precedence Label
+ ::1/128 50 Loopback (RFC4291)
2001:1111:1111::1/128 40 ClientNet
2001:2222:2222::/48 40 ClientNet
::/0 40 Default
- 2002::/16 30 6to4
- ::/96 20 IPv4_Compatible
- ::ffff:0.0.0.0/96 10 IPv4
+ ::ffff:0:0/96 35 IPv4 ::ffff:0.0.0.0/96 (RFC4038)
+ 2002::/16 30 6to4 (RFC3056)
+ 2001::/32 5 Terado (RFC4380)
+ fc00::/7 3 Unique Local Addresses (RFC4193)
+ ::/96 1 IPv4_Compatible (RFC4291-deprecated)
+ fec0::/10 1 Site-local (RFC3879-deprecated)
+ 3ffe::/16 1 6Bone (RFC3701-deprecated)
diff -NurbBw 11.4.66/man8/ipadm.8 11.4.69/man8/ipadm.8
--- 11.4.66/man8/ipadm.8 2024-05-25 09:57:52.553919915 -0700
+++ 11.4.69/man8/ipadm.8 2024-05-25 09:58:15.862961167 -0700
@@ -2039,6 +2039,17 @@
managed interfaces when the DHCP client terminates. See the de-
scription in the "Address Properties" section.
+ prefer-srcaddr (ipv6)
+
+ System wide setting, set this option to temporary to have IPv6
+ source address selection prefer temporary addresses over public
+ (stable) addresses as specified in RFC 6724. The default value of
+ public means Solaris prefers public (stable) addresses over tempo-
+ rary addresses. Either setting can be overridden on a per connec-
+ tion basis by the IPV6_SRC_PREFERENCES socket option, (passing the
+ flag IPV6_PREFER_SRC_TMP or IPV6_PREFER_SRC_PUBLIC will cause tem-
+ porary or public addresses to be preferred, respectively).
+
Interface Properties
The following interface properties are supported:
diff -NurbBw 11.4.66/man8/ldapservercfg.8 11.4.69/man8/ldapservercfg.8
--- 11.4.66/man8/ldapservercfg.8 2024-05-25 09:57:52.598655403 -0700
+++ 11.4.69/man8/ldapservercfg.8 2024-05-25 09:58:15.910052380 -0700
@@ -61,14 +61,34 @@
work/ldap/server:openldap.
- If necessary, the server is converted to use Online Configuration
- (OLC). The server is configured to accept unencrypted connections on
- port 389, encrypted connections (with STARTTLS) on port 389, and en-
- crypted connections (using raw TLS) on port 636.
+ If necessary, the server is converted to use Online Configuration (OLC)
+ database; refer to slapd-config(5). The server is configured to accept
+ unencrypted connections on port 389, encrypted connections (with START-
+ TLS) on port 389, and encrypted connections (using raw TLS) on port
+ 636.
When the server configuration is successful, the configuration proper-
- ties in svc:/network/ldap/server:openldap are updated.
+ ties in svc:/network/ldap/server:openldap are updated and it is en-
+ abled.
+
+
+ Service instance svc:/network/ldap/server:openldap starts slapd and may
+ enable service svc:/network/ldap/identity:openldap when slapd-con-
+ fig(8oldap) value for olcTLSCertificateKeyFile is /etc/certs/local-
+ host/host.key; the default svc:/system/identity:cert property certifi-
+ cate/cert/private_key/uri value.
+
+
+ Service Instance svc:/network/ldap/identity:openldap is a transient
+ service that has a restart_on dependency on identity(8s) service
+ svc:/system/identity:cert. As described above it is enabled by Service
+ instance svc:/network/ldap/server:openldap when olcTLSCertificateKey-
+ File value is /etc/certs/localhost/host.key. It checks if that file has
+ been updated since slapd was started. And if so performs a restart of
+ svc:/network/ldap/server:openldap to stop and start slapd so that it
+ uses the latest key. Decisions made concerning the status of the file
+ are logged to the SMF log file.
Special Accounts
Four special accounts might be created. Their names, default Distin-
@@ -219,6 +239,48 @@
+ Transport Layer Security (TLS) files
+ When configuring OpenLDAP with TLS support the certificate files used
+ by default are those created by identity(8s). Those file locations can
+ be overridden using the properties below. If any of the files are miss-
+ ing then an automatic configuration is halted. Following the configura-
+ tion the file locations are stored within slapd-config(8oldap) for use
+ by slapd server.
+
+
+ TLS Certificate Authority certificates:
+ cred/ca_certificates
+
+ Default: /etc/certs/ca-certificates.crt
+
+ Specifies the file that contains certificates for all of the Cer-
+ tificate Authorities that slapd will recognize.
+
+
+
+ TLS certificate:
+ cred/certificate
+
+ Default: /etc/certs/localhost/host.crt
+
+ The location of the PEM-formatted x509 certificate.
+
+
+
+ TLS private key:
+ cred/privatekey
+
+ Default: /etc/certs/localhost/host.key
+
+ The location of the PEM-formatted private key. The
+ ldap/server:openldap profile includes the required {file_dac_read}
+ privilege to read the default file. That privilege is dropped if
+ the slapd-config(8oldap) value for olcTLSCertificateKeyFile does
+ not match cred/privatekey.
+
+
+
+
LDAP configuration properties
These properties are used to configure LDAP service and to save a
client profile within the Directory.
@@ -589,23 +651,6 @@
-FILES
- /etc/openldap/certs/server.pem (OpenLDAP)
- /etc/openldap/certs/server.key (OpenLDAP)
-
- A self-signed certificate and private key are generated. They can
- be replaced as desired.
-
-
-
- /etc/certs/ca-certificates.crt
-
- Contains a list of root certificates that the server trusts. This
- list should include the certificates used to sign the server's cer-
- tificate, if a CA-signed certificate is used.
-
-
-
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -619,9 +664,9 @@
SEE ALSO
- attributes(7), idsconfig(8), ldap(7), ldap_cachemgr(8), ldapaddent(8),
- ldapclient(8), ldaplist(1), resolv.conf(5), slapd(8oldap), slap-
- passwd(8oldap)
+ ldaplist(1), resolv.conf(5), attributes(7), ldap(7), privileges(7), id-
+ sconfig(8), ldap_cachemgr(8), ldapaddent(8), ldapclient(8),
+ slapd(8oldap), slapd-config(8oldap), slappasswd(8oldap), identity(8s)
RFC 4876: A Configuration Profile Schema for Lightweight Directory Ac-
@@ -635,4 +680,12 @@
https://docs.oracle.com/cd/E37838_01/html/E61012/appendixa-5.html
-Oracle Solaris 11.4 23 Jul 2020 ldapservercfg(8)
+HISTORY
+ Introduced in Oracle Solaris 11.4.
+
+
+ Began using TLS certificates generated by identity(8) for OpenLDAP con-
+ figuration in Oracle Solaris 11.4.69. Prior to which it created and
+ used /etc/openldap/certs/server.pem and /etc/openldap/certs/server.key.
+
+Oracle Solaris 11.4 02 Feb 2024 ldapservercfg(8)
diff -NurbBw 11.4.66/man8/mdnsd.8 11.4.69/man8/mdnsd.8
--- 11.4.66/man8/mdnsd.8 2024-05-25 09:57:52.632751725 -0700
+++ 11.4.69/man8/mdnsd.8 1969-12-31 16:00:00.000000000 -0800
@@ -1,104 +0,0 @@
-mdnsd(8) System Administration Commands mdnsd(8)
-
-NAME
- mdnsd - Multicast DNS daemon
-
-SYNOPSIS
- mdnsd [-debug]
-
-DESCRIPTION
- mdnsd is the daemon program for Multicast DNS and DNS Service Discov-
- ery.
-
-
- The mdnsd daemon listens on UDP port 5353 for Multicast DNS Query pack-
- ets. When it receives a query for which it knows an answer, mdnsd is-
- sues the appropriate Multicast DNS Reply packet.
-
-
- The mdnsd daemon also performs Multicast DNS Queries on behalf of
- client processes, and maintains a cache of the replies.
-
-
- The mdnsd daemon has no user-specifiable command-line argument, and
- users should not run mdnsd manually. The mdnsd daemon should be managed
- by the Solaris Management Facility (SMF) and should be administered by
- the svcadm(8) command using the following fault management resource
- identifier (FMRI):
-
- svc:/network/dns/multicast:default
-
-
-
- To examine mdnsd's internal state for debugging and diagnostic pur-
- poses, send it a SIGUSR1 signal, and it will then log a snapshot sum-
- mary of its internal state using the syslog(3C) facility. mdnsd uses
- the syslog facility code daemon and info priority level.
-
-OPTIONS
- The mdnsd daemon recognizes the following option:
-
- -debug Debug mode. The mdnsd daemon sends output to the standard er-
- ror, and does not run in the background. This option is only
- intended for debugging the daemon.
-
-
- CONFIGURATION
- Multicast DNS can be used to look up host names and host addresses by
- specifying mdns as a source for hosts and ipnodes in the name service
- switch configuration file nsswitch.conf(5). The configuration options
- for host name and host address queries using Multicast DNS are stored
- in the SMF repository. This configuration can be modified by the svc-
- cfg(8) command using the following fault management resource identifier
- (FMRI):
-
- svc:/network/dns/multicast:default
-
-
-
- The configuration options for host name and host address queries using
- Multicast DNS are stored in a property group named "nss_mdns_config".
- The properties that make up the configuration options are as follows:
-
- search A list of search domains for host name look up. By default,
- no search domains are included in the configuration. The
- search list is currently limited to six domains.
-
-
- valid A list of valid domains checked before Multicast DNS is used
- to look up the host name or host address for a domain. Do-
- mains specified in the search list are always included in the
- valid list. The valid domain list is currently limited to ten
- domains.
-
-
-
- Please note the above configuration options are Volatile and may change
- in a future release.
-
-FILES
- /usr/lib/inet/mdnsd
-
-ATTRIBUTES
- See attributes(7) for descriptions of the following attributes:
-
- +------------------------------+-----------------------------+
- | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
- +------------------------------+-----------------------------+
- | Availability |service/network/dns/mdns |
- +------------------------------+-----------------------------+
- | Interface Stability |Volatile |
- +------------------------------+-----------------------------+
-
-
-SEE ALSO
- syslog(3C), nsswitch.conf(5), attributes(7), dns-sd(8), svcadm(8), svc-
- cfg(8)
-
-
- For information on Multicast DNS, see http://www.multicastdns.org/
-
-
- For information on DNS Service Discovery, see http://www.dns-sd.org/.
-
-Oracle Solaris 11.4 14 May 2018 mdnsd(8)
diff -NurbBw 11.4.66/man8/modinfo.8 11.4.69/man8/modinfo.8
--- 11.4.66/man8/modinfo.8 2024-05-25 09:57:52.665898501 -0700
+++ 11.4.69/man8/modinfo.8 2024-05-25 09:58:15.947838246 -0700
@@ -4,89 +4,178 @@
modinfo - display information about loaded kernel modules
SYNOPSIS
- /usr/sbin/modinfo [-aw] [-c | [-i module] [-pP] [-o field[,...]]]
+ /usr/sbin/modinfo [-ahwx] [--scale[=item1,item2,...]]
+ [-c | [-i module] [-pP] [-o field[,...]]]
DESCRIPTION
- The modinfo utility displays information about the loaded modules. The
- format of the information is as follows:
+ The modinfo utility displays information about the kernel modules cur-
+ rently known to the running system. The following information is avail-
+ able.
- ID LOADADDR SIZE INFO REV NAMEDESC
+ id Module identifier.
+ loadaddr When run by a privileged user, the starting text address of
+ the module in hexadecimal format. The string '--' is dis-
+ played for unprivileged users.
- where ID is the decimal module Id, LOADADDR is the starting text ad-
- dress in hexadecimal for privileged users but '--' for unprivileged
- users. SIZE is the size of text, data, and bss in hexadecimal bytes,
- INFO is module specific information, REV is the revision of the load-
- able modules system, and NAMEDESC is the filename and description of
- the module.
+ size The size in bytes, of the module text, data, and bss, in
+ hexadecimal format.
- The module specific information is the block and character major num-
- bers for drivers, the system call number for system calls, and unspeci-
- fied for other module types.
+
+ info Module specific information. The block and character major
+ numbers are shown for drivers. The system call number is
+ provided for for system calls. Other module types do not
+ specify a meaning for this field, and the string '--' is
+ displayed.
+
+
+ rev The revision of the loadable modules system for which the
+ module was built. A small number of primary system modules,
+ including the unix kernel, do not specify a revision, and
+ the string '--' is displayed.
+
+
+ sys Identifies system modules built and delivered with the core
+ Oracle Solaris system. A value of 1 is shown for system
+ modules, 0 for others.
+
+
+ path Path at which the module file resides. For a loaded module,
+ the actual path that the kernel used when loading the mod-
+ ule is shown. For a module that is not loaded, the path at
+ which the kernel would be expected to load the module is
+ shown. If modinfo is unable to determine where the module
+ would be loaded from, a path based on the module name is
+ constructed, with a question mark ('?') at the beginning to
+ indicate its placeholder status.
+
+
+ name Module name.
+
+
+ desc A brief description of the module's purpose.
+
+
+ namedesc The module name, followed in parenthesis by a brief de-
+ scription of the module's purpose.
+
+
+ loadcnt The number of times the module has been loaded since system
+ boot.
+
+
+ state The module state, indicating whether the module is cur-
+ rently loaded, as well as whether it is installed and is
+ available for use.
+
+
+
+ By default, id, loadaddr, size, info, sys, and namedesc are shown. If
+ the -c option is specified, id, loadcnt, name, and state are shown. The
+ -o option can be used to specify an arbitrary subset of this informa-
+ tion, and to control the order in which it is displayed.
+
+
+ For modules that are not currently loaded, output may not match the
+ binding which occurs if software is added or removed from the system.
+ Such changes may cause a different path to be used when the module is
+ next loaded.
OPTIONS
The following options are supported:
- -c Displays the number of times the module was loaded
- and the module's current state. This option includes
- -a and cannot be used with -i, -o, -p, or -P.
+ -a
+
+ Display information for all modules known to the system, including
+ those not currently loaded.
+
+
+ -c
+
+ Display the number of times the module has been loaded and the cur-
+ rent module state. This option implicitly sets the -a option, and
+ cannot be used with the -i, -o, -p, or -P options.
+
+
+ -h
+
+ Prints the size field in decimal, scaled to a human readable for-
+ mat. The -h option is equivalent to using the --scale=max,1024 op-
+ tion.
+
+
+ -i module
+
+ Displays information about the specified module only. If 'module'
+ starts with a digit then it is interpreted as a decimal module Id,
+ otherwise it is interpreted as a module name. The module id for a
+ given module is assigned dynamically by the system, and can change
+ across a reboot.
+
+
+ -o field[,...]
+
+ A case-insensitive, comma-separated list of output fields to dis-
+ play. The available field names are listed above. See DESCRIPTION.
+ Alternatively, the special value all can be specified to display
+ all the fields in the order listed above. This option implicitly
+ enables the -w option.
+
+
+ -p
+
+ Display information in a stable machine-parsable format. The -o op-
+ tion must be used in conjunction with this option. The output in-
+ cludes only those fields requested by means of the -o option, in
+ the order requested.
+
+ When more than one field of information is requested, the lines of
+ output consist of colon (:) delimited fields, and any literal colon
+ characters are escaped by a backslash character (\) before being
+ output. Similarly, literal backslash characters are also escaped
+ (\\). This escape format is parsable by using shell read(1) func-
+ tions with the IFS environment variable set as IFS=:.
+
+ When a single field of output is requested, each line of output
+ provides of the requested information directly, with no escaping of
+ colon or or backslash characters.
+
+ -P
- -i module Displays information about the specified module only.
- If 'module' starts with a digit then it is inter-
- preted as a decimal module Id, otherwise it is inter-
- preted as a module name. A decimal module Id may
- change across a reboot.
+ Only displays the path and header information. The -P option is
+ equivalent to '-p -o path'.
- -o field[,...] A case-insensitive, comma-separated list of output
- fields to display. The field name must be one of the
- fields listed below, or the special value all to dis-
- play all fields. The following fields are supported:
- id, loadaddr, size, info, rev, path, name, desc,
- namedesc, loadcnt, state, all. For a loaded module,
- 'path' is the actual path that the kernel used when
- loading the module is displayed. For a module that is
- not loaded the path that the kernel would use to load
- the module is derived. Output may not match the bind-
- ing which occurs if software is added or removed from
- the system. Such changes may cause a different path
- to be used when the module is next loaded. If mod-
- info(8) is unable to determine where the module would
- be loaded from, it prints a question mark in front of
- the path. This option implicitly includes -w.
+ --scale[=item1,item2,...]
+ Prints the size field in decimal, scaled to a human readable for-
+ mat. Scaling is done by repetitively dividing by 1024, unless oth-
+ erwise specified. --scale specified without arguments enables de-
+ fault scaled output, and is equivalent to --scale=max,1024. See
+ scale(7) for a complete description of --scale features.
- -p Displays using a stable machine-parsable format. The
- -o option is required with this option. See "Parsable
- Output Format" below.
+ -w
- -P Only displays the path and header information. It's a
- alias for '-p -o path'.
+ Do not truncate module information at 80 characters.
- -a Displays information for all modules, including ones
- not currently loaded.
+ -x
+ Only display modules not built and delivered with the core Oracle
+ Solaris system. These modules correspond to the modules for which
+ the sys output field has the value 0. See DESCRIPTION.
- -w Do not truncate module information at 80 characters.
+ -?
+ --help
- Parseable Output Format
- If more than one field is listed for the -o option, the output format
- is one or more lines of colon (:) delimited fields. The output includes
- only those fields requested by means of the -o option, in the order re-
- quested. When you request multiple fields, any literal colon characters
- are escaped by a backslash (\) before being output. Similarly, literal
- backslash characters are also escaped (\\). This escape format is
- parsable by using shell read(1) functions with the IFS environment
- variable set as IFS=:.
+ Print usage message and immediately exit.
- Note that escaping is not done when you request only a single field.
EXAMPLES
Example 1 Displaying the Status of a Module
@@ -99,7 +188,7 @@
example% modinfo -i 3
- ID LOADADDR SIZE INFO REV NAMEDESC
+ ID LOADADDR SIZE INFO SYS NAMEDESC
3 fffffffffbdcf000 7410 1 1 specfs (filesystem for specfs)
@@ -107,7 +196,7 @@
example% modinfo -i specfs
- ID LOADADDR SIZE INFO REV NAMEDESC
+ ID LOADADDR SIZE INFO SYS NAMEDESC
3 fffffffffbdcf000 7410 1 1 specfs (filesystem for specfs)
@@ -121,9 +210,9 @@
example% modinfo
- ID LOADADDR SIZE INFO REV NAMEDESC
- 0 fffffffffb800000 3b3cb4 -- 0 unix ()
- 1 fffffffffb9f8208 43e068 -- 0 genunix ()
+ ID LOADADDR SIZE INFO SYS NAMEDESC
+ 0 fffffffffb800000 3b3cb4 -- -- unix ()
+ 1 fffffffffb9f8208 43e068 -- -- genunix ()
3 fffffffffbdcf000 7410 1 1 specfs (filesystem for specfs)
4 fffffffffbdd6370 5d80 3 1 fifofs (filesystem for fifo)
5 fffffffff80b4000 267c8 53 1 dtrace (Dynamic Tracing)
@@ -192,6 +281,6 @@
SEE ALSO
- attributes(7), modload(8), modunload(8)
+ attributes(7), scale(7), modload(8), modunload(8)
-Oracle Solaris 11.4 28 November 2022 modinfo(8)
+Oracle Solaris 11.4 14 February 2024 modinfo(8)
diff -NurbBw 11.4.66/man8/nscd.8 11.4.69/man8/nscd.8
--- 11.4.66/man8/nscd.8 2024-05-25 09:57:52.706807538 -0700
+++ 11.4.69/man8/nscd.8 2024-05-25 09:58:15.988915061 -0700
@@ -64,7 +64,7 @@
o svc:/network/ldap/client:default, see ldapclient(8)
- o svc:/network/dns/multicast:default, see mdnsd(8)
+ o svc:/network/dns/multicast:default, see avahi-daemon(8)
@@ -297,7 +297,8 @@
hosts(5), netmasks(5), networks(5), nscd.conf(5), nsswitch.conf(5),
passwd(5), prof_attr(5), project(5), protocols(5), resolv.conf(5),
rpc(5), services(5), user_attr(5), ypfiles(5), attributes(7), ldap(7),
- getent(8), ldapclient(8), mdnsd(8), svcadm(8), svccfg(8), ypbind(8)
+ avahi-daemon(8), getent(8), ldapclient(8), svcadm(8), svccfg(8), yp-
+ bind(8)
NOTES
You can use the svcadm command to perform administrative actions on
@@ -320,4 +321,4 @@
Starting with Oracle Solaris 11.4, the nscd daemon must be running for
ldap(7) services to function correctly.
-Oracle Solaris 11.4 15 Feb 2023 nscd(8)
+Oracle Solaris 11.4 17 Jan 2024 nscd(8)
diff -NurbBw 11.4.66/man8/suriadm.8 11.4.69/man8/suriadm.8
--- 11.4.66/man8/suriadm.8 2024-05-25 09:57:52.746747076 -0700
+++ 11.4.69/man8/suriadm.8 2024-05-25 09:58:16.028893630 -0700
@@ -29,7 +29,7 @@
supported, file-permissions, group, hostname, initiator, is-slice,
lun, luname, mapped-dev, mapped-devs, mount-options, mountpoint-
prefix, mountpoint, path, port, removable, target, teardown-sup-
- ported, uri, uri-type, and user.
+ ported, uri, uri-type, user, and with-lofi.
normalize URI
@@ -78,7 +78,7 @@
shows only the first device path of mapped-devs.
Allowed input property names for the -p option are mount-options,
- mountpoint-prefix, and removable.
+ mountpoint-prefix, removable, and with-lofi.
lookup-mapping [-H] [-o p,p,...] [-p prop=value] URI
@@ -96,8 +96,8 @@
Creates the backing store for the storage URI then maps it. Option
-p has the same meaning as for the map subcommand.
- Allowed input property names for the -p option are create-size and
- file-permissions.
+ Allowed input property names for the -p option are create-size,
+ file-permissions, mount-options, mountpoint-prefix, and with-lofi.
destroy [-p prop=value] URI
@@ -106,6 +106,9 @@
has the same meaning as for the map subcommand. The object repre-
sented by the URI must be mapped.
+ Allowed input property names for the -p option are mountpoint-pre-
+ fix and with-lofi.
+
unmap [-p prop=value] URI
@@ -122,11 +125,10 @@
lookup-uri [-t uri-type] device-path
lookup-uri [-t uri-type] -p mapped-dev=device-path
- Looks up and displays URIs based on a local system device path. Al-
- lowed URI types for -t are dev, lu, and iscsi. If the -t option is
- not specified, the output consists of all URIs that match the de-
- vice path for any URI type. Using the property option -p is op-
- tional.
+ Looks up and displays URIs based on a local system device path. See
+ suri(7) for uri-type supported values. If the -t option is not
+ specified, the output consists of all URIs that match the device
+ path for any URI type. Using the property option -p is optional.
@@ -466,6 +468,15 @@
iscsi://10.10.10.10/target.iqn.1986-03.com.sun:02:60ae9e51-dbc79738b319,lun.1
+ Example 19 Create and map a ZFS volume based dev URI object with an op-
+ tional lofi layer
+
+
+ $ suriadm create -p create-size=50m -p with-lofi=true dev:zvol/dsk/rpool/myzvol
+ PROPERTY VALUE
+ mapped-devs /dev/dsk/c10t1d0
+
+
EXIT STATUS
0
@@ -510,4 +521,4 @@
URI is being processed, the service will be automatically enabled tem-
porarily. The service is never disabled through the suriadm command.
-Oracle Solaris 11.4 19 Jul 2023 suriadm(8)
+Oracle Solaris 11.4 16 Jan 2024 suriadm(8)
diff -NurbBw 11.4.66/man8/sxadm.8 11.4.69/man8/sxadm.8
--- 11.4.66/man8/sxadm.8 2024-05-25 09:57:52.798534975 -0700
+++ 11.4.69/man8/sxadm.8 2024-05-25 09:58:16.086202769 -0700
@@ -171,6 +171,37 @@
+ GDS - Gather Data Sampling
+
+ GDS is a mitigation for the Gather Data Sampling vulnerabilities
+ for Intel CPUs only (CVE-2022-40982). In some situations after a
+ gather instruction performs certain types of loads to memory a ma-
+ licious process may be able to use this type of instruction to in-
+ fer stale data from previously used vector registers.
+
+ This mitigation is enabled by default on systems where it is re-
+ quired and supported. When it is enabled some workloads might expe-
+ rience lower performance.
+
+ A reboot is required after enabling or disabling GDS for the
+ changes to take effect.
+
+
+ GDS_NO Gather Data Sampling Mitigation
+
+ GDS_NO is a readonly extension that is only enabled if the CPU is
+ not vulnerable to the Gather Data Sampling (GDS) vulnerabilities in
+ CVE-2022-40982 that are mitigated by the GDS extension.
+
+ Note -
+
+
+
+ On Intel CPUs that have the GDS_NO mitigation enabled, the GDS
+ extension will always be enabled as a readonly extension.
+
+
+
HW_BTI - Hardware BTI Mitigation
HW_BTI provides hardware-based mitigation for CVE-2017-5715 (Branch
@@ -274,7 +305,7 @@
changes to take effect.
- MD_CLEAR - Microarchitectural Data Sampling Avoidance Mitigation
+ MD_CLEAR - Microarchitectural Data Sampling Avoidance
MD_CLEAR is a mitigation for the Microarchitectural Data Sampling
(MDS) series of vulnerabilities for Intel CPUs only. The vulnera-
@@ -868,6 +899,8 @@
+--------------------------------------------------+---------+
| EXTENSION |RELEASE |
+--------------------------------------------------+---------+
+ | GDS, GDS_NO |11.4.69 |
+ +--------------------------------------------------+---------+
| BTC_NO, SMEP (see below) |11.4.63 |
+--------------------------------------------------+---------+
| FB_CLEAR, FBSDP_NO, PSDP_NO, SBDR_SSDP_NO |11.4.57 |
@@ -912,4 +945,4 @@
viously only available for Intel CPUs are also available for supported
AMD CPUs as of Oracle Solaris 11.4.60.
-Oracle Solaris 11.4 31 July 2023 sxadm(8)
+Oracle Solaris 11.4 31 Jan 2024 sxadm(8)
diff -NurbBw 11.4.66/man8/syslogd.8 11.4.69/man8/syslogd.8
--- 11.4.66/man8/syslogd.8 2024-05-25 09:57:52.835529882 -0700
+++ 11.4.69/man8/syslogd.8 2024-05-25 09:58:16.121145970 -0700
@@ -66,8 +66,8 @@
This property specifies whether remote messages are logged.
- log_from_remote=true is equivalent to the -t command-line option and
- false is equivalent to the -T command-line option. The default value
+ log_from_remote=true is equivalent to the -T command-line option and
+ false is equivalent to the -t command-line option. The default value
for log_from_remote is false. See NOTES.
config/time_precision
@@ -292,4 +292,4 @@
On installation, the initial value of SMF instance svc:/system/system-
log:default property config/log_from_remote is false.
-Oracle Solaris 11.4 6 Mar 2020 syslogd(8)
+Oracle Solaris 11.4 8 Jan 2024 syslogd(8)
diff -NurbBw 11.4.66/man8/zfs.8 11.4.69/man8/zfs.8
--- 11.4.66/man8/zfs.8 2024-05-25 09:57:52.945968647 -0700
+++ 11.4.69/man8/zfs.8 2024-05-25 09:58:16.242794872 -0700
@@ -1186,6 +1186,12 @@
to none. Or, when the migration is complete, you can manually set
the shadow property to none.
+ Note that if a file has system attributes set (see sysattr(7) ),
+ migration from an NFSv2 or NFSv3 server will not preserve those at-
+ tributes. Migration from an NFSv4.0 server will preserve the
+ archive, crtime, hidden, and system attributes. Migration from an
+ NFSv4.1 server will additionally preserve the rtime attribute.
+
sharenfs=on | off
@@ -1431,6 +1437,10 @@
cannot be set unless the default retention period is greater
than zero.
+ The deletion may be delayed by setting the retention.pe-
+ riod.deletegrace to greater than zero. See retention.pe-
+ riod.deletegrace below.
+
hold
@@ -1441,6 +1451,16 @@
+ retention.period.deletegrace
+
+ When retention.policy.onexpiry is set to delete, the file is imme-
+ diately deleted once the retention expires. This property allows
+ the deletion to be delayed by the specified amount of time.
+
+ As with the other retention period values, this one too must be
+ less than 100 years.
+
+
retention.status.expiry
The latest-expiring retention timestamp of a file is shown by this
@@ -3550,4 +3570,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 16 Feb 2023 zfs(8)
+Oracle Solaris 11.4 21 Sep 2023 zfs(8)
diff -NurbBw 11.4.66/man8/zoneadm.8 11.4.69/man8/zoneadm.8
--- 11.4.66/man8/zoneadm.8 2024-05-25 09:57:53.021170237 -0700
+++ 11.4.69/man8/zoneadm.8 2024-05-25 09:58:16.325860041 -0700
@@ -284,6 +284,27 @@
+ zoneadm log [-C | -m] [-a]
+
+ Display the contents of the zones console log or messages log.
+
+ -C
+
+ Display the current console log for the zone.
+
+
+ -m
+
+ Display the current messages log for the zone.
+
+
+ -a
+
+ Display all previously rotated console or messages logs for the
+ zone, in chronological order.
+
+
+
zoneadm get-prom [variable]
The get-prom subcommand displays OpenBoot configuration variables.
@@ -1939,4 +1960,4 @@
when the zone is booted with -w/-W, the write-only protection is dis-
abled. Care must be taken that the zone is otherwise protected.
-Oracle Solaris 11.4 19 Jul 2023 zoneadm(8)
+Oracle Solaris 11.4 10 Dec 2023 zoneadm(8)
diff -NurbBw 11.4.66/man8/zonecfg.8 11.4.69/man8/zonecfg.8
--- 11.4.66/man8/zonecfg.8 2024-05-25 09:57:53.127575124 -0700
+++ 11.4.69/man8/zonecfg.8 2024-05-25 09:58:16.427837315 -0700
@@ -525,7 +525,7 @@
where each <value> is a string property. A list of a single value is
equivalent to specifying that value without the list syntax. That is,
- "foo" is equivalent to "[foo]". A list can be empty (denoted by "[]").
+ foo is equivalent to [foo]. A list can be empty (denoted by []).
The property types are described as follows:
@@ -599,9 +599,9 @@
specification as described in priv_str_to_set(3C) man page. Privi-
leges can be excluded from the resulting set by preceding their
names with a dash (-) or an exclamation point (!). The special
- privilege string "zone" is not supported in this context. If the
- special string "default" occurs as the first token in the property,
- it expands into a safe set of privileges that preserve the resource
+ privilege string zone is not supported in this context. If the spe-
+ cial string default occurs as the first token in the property, it
+ expands into a safe set of privileges that preserve the resource
and security isolation described in zones(7) man page. A missing or
empty property is equivalent to this same set of safe privileges.
@@ -612,7 +612,7 @@
zone as doing so would allow processes inside a zone to unduly af-
fect processes in other zones. zoneadm(8) indicates when an invalid
privilege has been added or removed from a zone's privilege set
- when an attempt is made to either "boot" or "ready" the zone.
+ when an attempt is made to either boot or ready the zone.
See privileges(7) man page for a description of privileges. The
command "ppriv -l" (see ppriv(1) man page) produces a list of all
@@ -861,7 +861,7 @@
with the SI_HW_PROVIDER command for a solaris10 branded zone. See
sysinfo(2) man page.
- When set, the only valid property value is "Sun_Microsystems". When
+ When set, the only valid property value is Sun_Microsystems. When
this property is untouched or cleared, the hardware manufacturer
string in the global zone is used.
@@ -1575,14 +1575,14 @@
smi-enabled
Specifies whether the virtual HCA can use Subnet Management
- Packets (SMPs). If the value of this property is "on", then
- SMPs are allowed for this virtual HCA. If this property is
- "off" then SMPs cannot be used with this virtual HCA. If the
- value is "readonly", then this virtual HCA can only use query
- SMP operations and not "set" operations. The default value is
- "off". The value "on" is not recommended without considering
- the possible security impact on the fabric. When running with
- "on", M_Keys should be set on fabric components.
+ Packets (SMPs). If the value of this property is on, then SMPs
+ are allowed for this virtual HCA. If this property is off then
+ SMPs cannot be used with this virtual HCA. If the value is
+ readonly, then this virtual HCA can only use query SMP opera-
+ tions and not set operations. The default value is off. The
+ value on is not recommended without considering the possible
+ security impact on the fabric. When running with on, M_Keys
+ should be set on fabric components.
id
@@ -1700,9 +1700,9 @@
in a fashion similar but not identical to zone names: it must begin
with an alphanumeric, and can contain alphanumerics plus the hyphen
(-), underscore (_), and dot (.) characters. Attribute names begin-
- ning with "zone" are reserved for use by the system. Finally, the
- autoboot and global-time global property must have a value of true
- or false.
+ ning with string zone are reserved for use by the system. Finally,
+ the autoboot and global-time global property must have a value of
+ true or false.
dataset: name, alias
@@ -2027,7 +2027,10 @@
Defines one or more storage URIs to be used exclusively for a dedi-
cated ZFS pool containing the zone installation. The allowed values
- for storage are defined in suri(7).
+ for storage are defined in suri(7). Only dev, iscsi, and lu storage
+ URI types are supported. The dev storage URIs equivalent to the
+ normalized form with the prefix of dev:zvol/dsk/ are implicitly
+ mapped with the with-lofi property set to true.
If multiple storage properties are present during installation, a
mirrored ZFS pool will be created.
@@ -2037,8 +2040,9 @@
Defines one or more storage URIs to be used exclusively for a zpool
delegated to the zone. The allowed values for storage are defined
- in suri(7) man page. The allowed values for name are defined in
- zpool(8) man page. The name rpool is not permitted.
+ in suri(7) man page. Only storage URI types permitted in the
+ rootzpool property are supported. The allowed values for name are
+ defined in zpool(8) man page. The name rpool is not permitted.
If multiple storage properties are present during installation, a
mirrored ZFS pool will be created.
@@ -3847,13 +3851,13 @@
limitation.
- The mount point for a lofs file system specified by an fs" resource
- must not lie within any filesystem that is mounted by the zone. In par-
- ticular, such mountpoints must not lie beneath /var and /export.
+ The mount point for a lofs file system specified by an fs resource must
+ not lie within any filesystem that is mounted by the zone. In particu-
+ lar, such mountpoints must not lie beneath /var and /export.
The special property for a ZFS file system specified by an fs resource
cannot be a descendant of any dataset delegated to the zone, including
the zone's top-level delegated dataset.
-Oracle Solaris 11.4 19 Jul 2023 zonecfg(8)
+Oracle Solaris 11.4 9 Feb 2024 zonecfg(8)
diff -NurbBw 11.4.66/man8/zpool.8 11.4.69/man8/zpool.8
--- 11.4.66/man8/zpool.8 2024-05-25 09:57:53.217344460 -0700
+++ 11.4.69/man8/zpool.8 2024-05-25 09:58:16.522843930 -0700
@@ -2891,7 +2891,7 @@
action: Wait for the resilver to complete.
Run 'zpool status -v' to see device specific details.
scan: resilver in progress since Fri Jan 19 10:33:36 2018
- 2.38G scanned out of 2.48G at 144M/s, 1s to go
+ 2.38G scanned out of 2.48G at 144M/s, 1s to go (1/2)
0 resilvered
config:
@@ -3016,4 +3016,4 @@
ble in such tools as ps(1). A user has no interaction with these
processes. For more information, see the SDC(4) man page.
-Oracle Solaris 11.4 3 Jul 2023 zpool(8)
+Oracle Solaris 11.4 17 Jan 2024 zpool(8)
diff -NurbBw 11.4.66/man8s/identity.8s 11.4.69/man8s/identity.8s
--- 11.4.66/man8s/identity.8s 2024-05-25 09:57:53.253096425 -0700
+++ 11.4.69/man8s/identity.8s 2024-05-25 09:58:16.562856365 -0700
@@ -10,7 +10,8 @@
The SMF service svc:/system/identity configures the basic network iden-
tity (names) of the Oracle Solaris instance. This includes its node-
name, RPC domainname and the default set of X.509 certificates used for
- the Remote Administration Daemon (RAD) and WebUI.
+ the Remote Administration Daemon (RAD), WebUI, and possibly the OpenL-
+ DAP server (slapd(8)) (see ldapservercfg(8)).
The service is composed of multiple instances:
@@ -152,11 +159,25 @@
- Restarting svc:/system/identity:cert results in svc:/system/we-
- bui/server, svc:/system/rad:remote, and svc:/system/ca-certificates:de-
- fault also being restarted.
+ Restarting svc:/system/identity:cert results in the following service
+ instances being restarted:
+
+ o svc:/network/ldap/identity:openldap (When svc:/net-
+ work/ldap/identity:openldap is configured to use identity
+ private key, see ldapservercfg(8).)
+
+
+ o svc:/system/webui/server
+
+
+ o svc:/system/rad:remote
+
+
+ o svc:/system/ca-certificates:default
+
SEE ALSO
- uname(1), hostname(1), webui-service(7), domainname(8)
+ uname(1), hostname(1), webui-service(7), domainname(8), ldapserver-
+ cfg(8), slapd(8)
-Oracle Solaris 11.4 11 Nov 2022 identity(8s)
+Oracle Solaris 11.4 02 Feb 2024 identity(8s)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment