Skip to content

Instantly share code, notes, and snippets.

@alanc

alanc/SRU84-man-page-changes.diff

Created August 19, 2025 21:03
Show Gist options
  • Save alanc/ae834f8047eb234c68cf9b4db4a96958 to your computer and use it in GitHub Desktop.
Save alanc/ae834f8047eb234c68cf9b4db4a96958 to your computer and use it in GitHub Desktop.
Download ZIP
Changes to core OS man pages in Oracle Solaris 11.4 SRU 84
Raw
Solaris-11.4-SRU84-man-page-changes.txt
15019483 truss(1) restore behavior where truss exits with the child's exit code
35501944 problem in KERNEL/ARCH-AMD64
36281414 format is not updating geometry for shared drives
36456733 fmthard should obey dm_inuse retention protections
36907402 listing disks non-interactively in format(8)
37455033 clonedir with RW permission fails to write if original filesystem is readonly
37484712 more minor issues in 3KSTAT2 man pages
37562004 shmat(2) does not return an EMFILE in Solaris 11.4
37691234 Factor csh into a separate package
37776953 ctfgen should translate GNU CTF to native Solaris CTF
37784490 solaris-kz(7) could use example on installation into NFS storage
37784641 suri(7) should also mention destroy op where it mentions create
37784676 suri(7) should say the path in nfs/file URIs is absolute
37811029 Add to ldm(8) man page to describe new "set-vdisk timeout=" functionality
37845450 sxadm(8) document how to see tags on binaries
37885477 Would like a way to determine if a variable existed
37898560 strip: removing symtab should also take CTF
37919455 Refactor IKEv1 and move to legacy state
37931872 libucrypto thinks it needs Blowfish but it does not
37948398 door file descriptors should not return ENOSYS when polling them
38107047 Assorted fixes for Section 8 man pages
PSARC/2025/036 Translate GNU CTF from gcc to Solaris CTF
PSARC/2025/037 sxadm(1m) update for Intel Register File Data Sampling Vulnerabilities
PSARC/2025/045 Force flag for fmthard
PSARC/2025/048 Re-loading disk information on format(8) startup and non-interactive disk listing
PSARC/2025/053 IKEv1 EOF
PSARC/2025/055 restore behavior where truss(1) exits with the child's exit code
Copyright (c) 1983, 2025, Oracle and/or its affiliates.
Raw
SRU84-man-page-changes.diff
diff -NurbBw 11.4.81/man1/ctfconvert.1 11.4.84/man1/ctfconvert.1
--- 11.4.81/man1/ctfconvert.1 2025-08-17 09:30:02.061405006 -0700
+++ 11.4.84/man1/ctfconvert.1 2025-08-17 09:30:24.278094059 -0700
@@ -4,7 +4,7 @@
ctfconvert - convert debug sections to CTF
SYNOPSIS
- ctfconvert [-irsS] [-l label] [-L labelenv] [-o outfile]
+ ctfconvert [-GirsS] [-l label] [-L labelenv] [-o outfile]
[-V version] file
DESCRIPTION
@@ -16,7 +16,7 @@
Compilers produce debug sections for the objects they create. These de-
bug sections are valuable for debuggers, and particularly for source
level debuggers, but they can be very large, and are often omitted from
- production software used in non-debug environments. In constrast, CTF
+ production software used in non-debug environments. In contrast, CTF
data is generally small enough to be kept in almost any object, while
providing basic type information valuable to low level observability
tools. The mdb(1) and kmdb(1) debuggers, dtrace(8), and the proc(1)
@@ -25,6 +25,15 @@
OPTIONS
The following options are supported:
+ -G
+
+ Translate the GNU CTF produced by the -gctf option to the gcc com-
+ piler to native Solaris CTF. Note that it is not necessary to use
+ ctfconvert -G on objects compiled with gcc, as the merge process
+ will automatically translate them. The -G option exists primarily
+ to facilitate inspection with ctfdump. See ctf(7).
+
+
-i
Silently ignore, and leave unmodified, object files built from lan-
@@ -114,6 +123,15 @@
such as -O. In addition, the -gdwarf-2 option should be used with gcc.
+ A better option for users of gcc is to bypass the use of ctfconvert en-
+ tirely, and use gcc -gctf option to generate CTF directly. The CTF
+ produced by gcc is a different variant of CTF that is not directly com-
+ patible with the native CTF used on Oracle Solaris. However, the So-
+ laris CTF implementation is able to recognize GNU CTF, and will auto-
+ matically translate it to the native form when it is read during the
+ merge stage. See ctf(7).
+
+
ctfconvert cannot process archive libraries. The individual objects may
be processed with ctfconvert before inserting them into the archive.
@@ -165,7 +183,12 @@
Support for CTF version 3, and the -V option, were added in Oracle So-
laris 11.4.75.81.
+
+ Support for reading GNU CTF from relocatable objects created by the gcc
+ compilers and translating it to the native CTF representation was added
+ in the Oracle Solaris 11.4.84 release.
+
SEE ALSO
- ctfdump(1), ctfmerge(1), ctf(5)
+ ctfdump(1), ctfmerge(1), ctf(5), ctf(7)
-Oracle Solaris 11.4 24 Jan 2025 ctfconvert(1)
+Oracle Solaris 11.4 8 April 2025 ctfconvert(1)
diff -NurbBw 11.4.81/man1/ctfdump.1 11.4.84/man1/ctfdump.1
--- 11.4.81/man1/ctfdump.1 2025-08-17 09:30:02.098499169 -0700
+++ 11.4.84/man1/ctfdump.1 2025-08-17 09:30:24.310626156 -0700
@@ -16,6 +16,14 @@
In this case, each object within the archive is processed using the op-
tions supplied.
+
+ In addition to native Solaris CTF, the ctfdump utility is also able to
+ dump the GNU CTF produced by the -gctf option to the gcc compilers.
+ GNU CTF is a different variant that is not directly compatible with the
+ native CTF used on Oracle Solaris. However, ctfdump can be used to in-
+ spect their contents, and the Solaris CTF implementation is able to
+ translate them to native CTF as part of the merge process. See ctf(7).
+
OPTIONS
The following options are supported:
@@ -76,7 +84,11 @@
tion of Solaris since Sun Solaris 9. They were added as system utili-
ties in Oracle Solaris 11.4.75.
+
+ Support for dumping GNU CTF from relocatable objects created by the gcc
+ compilers was added in the Oracle Solaris 11.4.84 release.
+
SEE ALSO
- ar(1), ctfconvert(1), ctfmerge(1)
+ ar(1), ctfconvert(1), ctfmerge(1), ctf(7)
-Oracle Solaris 11.4 6 Jan 2025 ctfdump(1)
+Oracle Solaris 11.4 8 April 2025 ctfdump(1)
diff -NurbBw 11.4.81/man1/ctfmerge.1 11.4.84/man1/ctfmerge.1
--- 11.4.81/man1/ctfmerge.1 2025-08-17 09:30:02.134021465 -0700
+++ 11.4.84/man1/ctfmerge.1 2025-08-17 09:30:24.347567503 -0700
@@ -58,12 +58,12 @@
-D uniqlabel
- Uniquify against the label given by uniqlabel.
+ Uniquify against the label given by uniqlabel. See ctf(7).
-d uniqfile
- Uniquify against the file given by uniqfile.
+ Uniquify against the file given by uniqfile. See ctf(7).
-i
@@ -84,7 +84,7 @@
Specifies a label to be associated with the generated CTF. Labels
are of use when employing uniquification to share definitions be-
tween parent and children objects as a space saving measure. See
- NOTES.
+ ctf(7).
-L labelenv
@@ -93,6 +93,7 @@
value of the environment variable specified by labelenv provides
the label to be used. If the environment variable is not defined,
no label is set, and the behavior is as if no label were specified.
+ See ctf(7).
-o outfile
@@ -145,7 +146,7 @@
-w withfile
- Additive merge against the file given by withfile. See NOTES.
+ Additive merge against the file given by withfile. See ctf(7).
-?
@@ -164,42 +165,13 @@
NOTES
- Labels
- Labels can be associated with CTF data, using the -l, or -L options.
- Labels can be useful for identification purposes, but are optional, un-
- less uniquification is desired, in which case labels must be provided.
-
- Uniquification
- When multiple objects share common type definitions provided by a cen-
- tral core object, the size of the overall CTF data can be greatly re-
- duced through the process of uniquification. Uniquification removes de-
- finitions found the core object from other objects, leaving those other
- objects with only the additional definitions that are unique to them.
- The core object is usually referred to as the parent, and the other ob-
- ject as the child. A given child can only have one parent, and the par-
- ent/child relationship is only one level deep, with no further descen-
- dants. The CTF data in the parent and child objects to be uniquified
- should define a common label, identifying them as sharing common type
- definitions.
-
-
- Uniquification is specified using the -d and -D options. Uniquification
- is typically applied only to kernel modules. In the kernel environment,
- the genunix kernel module is the parent, and the other kernel modules
- delivered with the system are uniquified against it.
-
- Additive Merges
- There are cases where it is desired to issue a new version of an object
- that has an existing uniquification relationship to another object. A
- common example occurs when operating system kernel modules are patched.
- For this to work smoothly, it is necessary to preserve all preexisting
- CTF data, unchanged, while adding any necessary additional definitions
- needed by the replacement object. This operation is known as an addi-
- tive merge. An additive merge is done using the -w option. In this
- case, a final uniquification is performed against the CTF data in the
- previous version of the module. The result is the placement of new and
- changed data after the existing data, thus preserving the existing type
- definitions.
+ GNU CTF
+ The ctfmerge utility provides support for the GNU CTF produced by the
+ -gctf option to the gcc compilers. The CTF produced by gcc is a differ-
+ ent variant that is not directly compatible with the native CTF used on
+ Oracle Solaris. However, the Solaris CTF implementation is able to rec-
+ ognize GNU CTF, and will automatically translate it to the native form
+ when it is read during the merge stage. See ctf(7).
Deprecated Historical Options
The ctfmerge utility silently accepts -f and -g options for backward
@@ -288,8 +260,15 @@
Support for CTF version 3, and the -V option, were added in Oracle So-
laris 11.4.75.81.
+
+ Support for reading GNU CTF from relocatable objects created by the gcc
+ compilers and translating it to the native CTF representation was added
+ in the Oracle Solaris 11.4.84 release.
+
SEE ALSO
- ctfconvert(1), ctfdump(1), ld(1), ctf(5) and Oracle Solaris 11.4 Link-
- ers and Libraries Guide
+ ctfconvert(1), ctfdump(1), ld(1), ctf(5), ctf(7)
+
+
+ Oracle Solaris 11.4 Linkers and Libraries Guide
-Oracle Solaris 11.4 24 Jan 2025 ctfmerge(1)
+Oracle Solaris 11.4 8 April 2025 ctfmerge(1)
diff -NurbBw 11.4.81/man1/elfdump.1 11.4.84/man1/elfdump.1
--- 11.4.81/man1/elfdump.1 2025-08-17 09:30:02.172934364 -0700
+++ 11.4.84/man1/elfdump.1 2025-08-17 09:30:24.391347378 -0700
@@ -58,6 +58,13 @@
+ An object may contain section types not listed here. The elfdump util-
+ ity does not produce output for such sections. Other utilities may ex-
+ ist to display the contents of such sections. See ctfdump(1), dis(1),
+ and elfsign(1). In addition, compilers typically provide utilities to
+ display the contents of the debug sections they create.
+
+
The general matching options (-I, -N, -T) can be used to select the
display of data for any desired section. See Matching Options. In addi-
tion, elfdump provides convenience options for the most commonly re-
@@ -515,8 +522,8 @@
SEE ALSO
- ar(1), dump(1), elffile(1), file(1), nm(1), pvs(1), elf(3ELF),
- libproc(3LIB), core(5), attributes(7)
+ ar(1), ctfdump(1), dis(1), dump(1), elffile(1), elfsign(1), file(1),
+ nm(1), pvs(1), elf(3ELF), libproc(3LIB), core(5), attributes(7)
Oracle Solaris 11.4 Linkers and Libraries Guide
@@ -567,4 +574,4 @@
The elfdump command was introduced in Solaris 7.
-Oracle Solaris 11.4 13 Sep 2024 elfdump(1)
+Oracle Solaris 11.4 2 May 2025 elfdump(1)
diff -NurbBw 11.4.81/man1/ld.1 11.4.84/man1/ld.1
--- 11.4.81/man1/ld.1 2025-08-17 09:30:02.276040395 -0700
+++ 11.4.84/man1/ld.1 2025-08-17 09:30:24.494516550 -0700
@@ -922,7 +922,7 @@
additive-merge=withfile
- Additive merge against the file given by withfile.
+ Additive merge against the file given by withfile. See ctf(7).
compress
@@ -962,7 +962,7 @@
Specifies a label to be associated with the generated CTF. La-
bels are of use when employing uniquification to share defini-
tions between parent and children objects as a space saving
- measure.
+ measure. See ctf(7).
label-env=labelenv
@@ -971,7 +971,7 @@
value of the environment variable specified by labelenv pro-
vides the label to be used. If the environment variable is not
defined, no label is set, and the behavior is as if no label
- were specified.
+ were specified. See ctf(7).
require
@@ -983,12 +983,12 @@
uniqify-file=uniqfile
- Uniquify against the file given by uniqfile.
+ Uniquify against the file given by uniqfile. See ctf(7).
uniqify-label=uniqlabel
- Uniquify against the label given by uniqlabel.
+ Uniquify against the label given by uniqlabel. See ctf(7).
version=ctf-version
@@ -2522,7 +2522,7 @@
as(1), crle(1), ctfconvert(1), ctfmerge(1), elfcompress(1), gprof(1),
ld.so.1(1), ldd(1), mcs(1), pvs(1), strip(1), exec(2), stat(2), dl-
dump(3C), zlib(3), dlopen(3C), elf(3ELF), ar.h(3HEAD), a.out(5),
- ctf(5), attributes(7), sxadm(8)
+ ctf(5), attributes(7), ctf(7), sxadm(8)
Oracle Solaris 11.4 Linkers and Libraries Guide
@@ -2560,4 +2560,4 @@
hard links to linker output files should explicitly remove and relink
the other file names.
-Oracle Solaris 11.4 24 January 2025 ld(1)
+Oracle Solaris 11.4 8 April 2025 ld(1)
diff -NurbBw 11.4.81/man1/mdb.1 11.4.84/man1/mdb.1
--- 11.4.81/man1/mdb.1 2025-08-17 09:30:02.420968761 -0700
+++ 11.4.84/man1/mdb.1 2025-08-17 09:30:24.644323778 -0700
@@ -265,6 +265,11 @@
The value of the variable named by identifier.
+ <?identifier
+
+ 1 if the variable named by identifier is defined otherwise 0.
+
+
identifier
The value of the symbol or constant named by identifier.
@@ -5387,4 +5392,4 @@
provides source code for an example module in the directory
/usr/demo/mdb.
-Oracle Solaris 11.4 7 March 2025 mdb(1)
+Oracle Solaris 11.4 1 May 2025 mdb(1)
diff -NurbBw 11.4.81/man1/truss.1 11.4.84/man1/truss.1
--- 11.4.81/man1/truss.1 2025-08-17 09:30:02.467656750 -0700
+++ 11.4.84/man1/truss.1 2025-08-17 09:30:24.692946847 -0700
@@ -528,6 +528,20 @@
0.002761 nanosleep(0xFFFFFED318188A60, 0xFFFFFED318188A50) = 0
+EXIT STATUS
+ When truss is able to execute the command, it will return the exit code
+ of that command's execution.
+
+
+ Otherwise, the following exit values are returned:
+
+ 0 Successful operation.
+
+
+ non-zero Invalid usage, the command could not be executed, or none
+ of provided pid[/lwps] could be traced.
+
+
FILES
/proc/* Process files
@@ -639,4 +653,4 @@
operation.
-Oracle Solaris 11.4 29 Nov 2022 truss(1)
+Oracle Solaris 11.4 26 May 2025 truss(1)
diff -NurbBw 11.4.81/man2/poll.2 11.4.84/man2/poll.2
--- 11.4.81/man2/poll.2 2025-08-17 09:30:02.506493635 -0700
+++ 11.4.84/man2/poll.2 2025-08-17 09:30:24.732714910 -0700
@@ -205,7 +205,7 @@
The poll() and ppoll() functions may fail if:
ENOSYS One of the fd members is from a filesystem type for which
- there is no poll() interface, such as doorfs.
+ there is no poll() interface.
ATTRIBUTES
@@ -255,4 +255,4 @@
The poll() function has been included in all Sun and Oracle releases of
Solaris.
-Oracle Solaris 11.4 30 Jan 2023 poll(2)
+Oracle Solaris 11.4 14 May 2025 poll(2)
diff -NurbBw 11.4.81/man2/shmop.2 11.4.84/man2/shmop.2
--- 11.4.81/man2/shmop.2 2025-08-17 09:30:02.544012379 -0700
+++ 11.4.84/man2/shmop.2 2025-08-17 09:30:24.770728833 -0700
@@ -218,4 +218,9 @@
Support for the SHM_PAGEABLE flag was added to Solaris in the Solaris 8
1/01 (Update 3) release.
-Oracle Solaris 11.4 15 Sep 2020 shmop(2)
+
+ As of the Solaris 9 release, there is no longer a limit on the number
+ of shared memory segments attached to the calling process, as a result,
+ shmat() will never set errno to EMFILE.
+
+Oracle Solaris 11.4 17 May 2025 shmop(2)
diff -NurbBw 11.4.81/man7/ctf.7 11.4.84/man7/ctf.7
--- 11.4.81/man7/ctf.7 1969-12-31 16:00:00.000000000 -0800
+++ 11.4.84/man7/ctf.7 2025-08-17 09:30:24.816046787 -0700
@@ -0,0 +1,461 @@
+ctf(7) Standards, Environments, Macros, Character Sets, and miscellany ctf(7)
+
+NAME
+ ctf - Compact C Type Format
+
+DESCRIPTION
+ CTF (Compact C Type Format) is designed to be a compact representation
+ of the C programming language's type information, focused on serving
+ the needs of dynamic tracing, debuggers, and other in-situ and post-
+ mortem introspection tools. CTF data is generally included in ELF ob-
+ jects, in a section named .SUNW_ctf, of type SHT_SUNW_CTF, to ensure
+ that the data is accessible in a running process and in subsequent core
+ dumps, if generated.
+
+
+ This man page discusses high level CTF concepts, and describes the
+ process of adding CTF to objects. Other man pages document the format,
+ and the utilities that manipulate it.
+
+ ctf(5) on-disk CTF format
+
+
+ ctfconvert(1) add CTF to relocatable objects
+
+
+ ctfdump(1) dump CTF content
+
+
+ ctfmerge(1) merge CTF from multiple objects
+
+
+ ld(1) -z ctf: perform CTF convert/merge as part of link-edit
+
+
+
+ Compilers produce debug sections for the objects they create. These de-
+ bug sections are valuable for debuggers, and particularly for source
+ level debuggers, but they can be very large, and are often omitted from
+ production software used in non-debug environments. In contrast, CTF
+ data is generally small enough to be kept in almost any object, while
+ providing basic type information valuable to low level observability
+ tools. The mdb(1) and kmdb(1) debuggers, dtrace(8), and the proc(1)
+ tools, all make use of CTF, when present, to enhance their operation.
+
+
+ There are 2 stages in the process of adding CTF to objects: generation,
+ and merging.
+
+ Generation
+ CTF is added when source code is compiled into relocatable objects.
+ This process is often called conversion, as CTF is often produced by
+ reading the type information from the debug sections produced by the
+ compiler to extract the type information, thereby converting it to CTF.
+ CTF is typically generated by requesting debug data from the compiler,
+ and applying the ctfconvert utility to the resulting object. Having
+ served its purpose, the debug data may then optionally be stripped as
+ part of this operation.
+
+ % cc -c -g main.c
+ % ctfconvert -S main.o
+
+
+
+ The ctfconvert utility is the only option for generating CTF for ob-
+ jects compiled with the native Studio compilers, and is compatible with
+ the debug data produced by that compiler's -g option. There is also
+ support for converting the DWARF sections produced by the gcc compil-
+ ers. However, this support is limited to version 2 GNU DWARF, which is
+ not the current version produced by those compilers.
+
+ % gcc -c -g -gdwarf=2 main.c
+ % ctfconvert -S main.o
+
+
+
+ A better option for users of gcc is to bypass the use of ctfconvert en-
+ tirely, and specify the -gctf option to generate CTF directly.
+
+ % gcc -c -gctf main.c
+
+
+
+ The CTF produced by gcc is a different variant of CTF that is not di-
+ rectly compatible with the native CTF used on Oracle Solaris. However,
+ the Solaris CTF implementation is able to recognize GNU CTF, and will
+ automatically translate it to the native form when it is read during
+ the merge stage. See GNU CTF.
+
+ Merging
+ When objects are linked together to form a final object, such as an ex-
+ ecutable, shared object, or kernel module, the CTF from the input ob-
+ jects must be merged to form a final single CTF section that describes
+ the resulting object. The ctfmerge utility is used to carry out the
+ merge step. A small complete example, including the compile and link,
+ might look as follows.
+
+ % cc -c -g main.c
+ % ctfconvert -S main.o
+ % cc -o main main.o
+ % ctfmerge -o main main.o
+
+
+
+ It is not sufficient to simply link the program, and omit the merge
+ step. While the resulting object will contain a .SUNW_ctf section
+ formed from the concatenation of the input CTF data, that section is
+ not valid CTF, and is not usable. The ctfmerge utility reads the CTF
+ data from the input objects, merges them to form a description of the
+ complete output object, and rewrites the object, replacing the contents
+ of the .SUNW_ctf section with valid CTF.
+
+
+ The required sequence of commands can be simplified, by omitting the
+ use of ctfconvert for each input object, and instead, specifying the -a
+ option to ctfmerge to have it perform the conversion step for each ob-
+ ject before doing the merge.
+
+ % cc -c -g main.c
+ % cc -o main main.o
+ % ctfmerge -a -o main main.o
+
+
+
+ An even larger simplification results from using the ld -z ctf option
+ to incorporate the CTF convert and merge steps into the link-edit. This
+ is very close to the commands required to build a program without CTF,
+ and is the simplest way to incorporate CTF into most software.
+
+ % cc -c -g main.c
+ % cc -o main main.o -zctf=convert
+
+
+
+ The Solaris CTF implementation is able to recognize GNU CTF, and will
+ automatically translate it to the native form when it is read during
+ the merge stage. See GNU CTF. This support allows the gcc version of
+ the example to be a single command.
+
+ % gcc -gctf main.c -zctf
+
+
+ GNU CTF
+ The GNU gcc compilers, and supporting binutils toolchain components,
+ including the GNU link-editor, support a different version of CTF, the
+ design of which evolved from the Solaris version. Despite that connec-
+ tion, the two are distinct and incompatible formats. The GNU CTF pro-
+ duced by the -gctf option to gcc cannot be used directly on Solaris.
+ However, the two formats are similar enough that one can be translated
+ to the other. The merge support provided by the Solaris CTF implementa-
+ tion is able to recognize GNU CTF, and will automatically translate it
+ to Solaris compatible CTF on input.
+
+
+ The ctfdump utility is able to dump GNU CTF, and can be used to inspect
+ its details. The result of the conversion to Solaris CTF can be seen by
+ applying ctfdump to the final object that includes this object in the
+ link, or more directly, by applying ctfconvert -G to the object com-
+ piled with gcc -gctf. Note that it is not necessary to use ctfconvert
+ -G on objects compiled with gcc, since the merge process will automati-
+ cally translate them. The -G option exists primarily to facilitate in-
+ spection with ctfdump.
+
+
+ Solaris CTF is written to ELF objects in a section named .SUNW_ctf, of
+ type SHT_SUNW_CTF. In contrast, the GNU CTF produced by gcc is written
+ to a section named .ctf, of type SHT_PROGBITS. As such, the 2 formats
+ are able to coexist. When a .ctf section is encountered by the Solaris
+ CTF merge implementation, the data is automatically translated to a
+ form compatible with Solaris, merged with the data from other objects,
+ and the result is written as a native Solaris .SUNW_ctf section, fully
+ compatible with tools such as mdb and dtrace.
+
+
+ The gcc -gctf option is known to be well supported for the C language.
+ Support for some C++ language levels may not be present. See CTF Cover-
+ age and Language Compatibility.
+
+ CTF Coverage And Language Compatibility
+ The CTF format describes types at the level of the type system of the C
+ programming language. As such, it is most useful when applied to pro-
+ grams written in C, or languages with type systems similar to C. This
+ is sometimes called a machine level view
+
+ Languages with more complex type systems can be used with CTF, but the
+ CTF will correspond to the basic building blocks from which those more
+ complex types are constructed, and the correspondence between the two
+ may not be obvious. A significant example is that of C++. CTF can be
+ used with C++, and will properly represent the machine level types from
+ which abstractions such as classes are formed. However, those higher
+ level concepts will not be visible in the CTF, which can limit its
+ value.
+
+
+ Ideally, every input object used to build an executable, shared object,
+ or kernel module, contains CTF describing its contents. When linked to-
+ gether into a resulting final object and merged, the resulting CTF will
+ provide full coverage for all types used within that object. The
+ ctfmerge -t option, or ld -zctf=require, can be used to enforce this,
+ and guarantee full coverage. Otherwise, the coverage will depend on the
+ objects being linked. Similarly, and related to the discussion of lan-
+ guages other than C above, the ctfmerge -i option, or ld -zctf=ignore-
+ non-c, can be used to exclude non-C code from this requirement. Not re-
+ quiring CTF in all input objects may allow the CTF in a program that
+ has still has high coverage to succeed, which is a useful outcome. Con-
+ versely, it can allow a program with low coverage to produce CTF that
+ is too incomplete to be useful. The programmer must use their knowledge
+ of the code being built to determine whether useful CTF can be produced
+ for a given code base, and to decide whether and how to use these op-
+ tions to best effect.
+
+ Compression
+ CTF data may be compressed to reduce the space used in the object. The
+ ctfconvert utility does not compress the CTF it produces, as the size
+ of the CTF in a single compilation unit is typically very small. How-
+ ever, the ctfmerge utility compresses the merged CTF it produces. The
+ behavior of these utilities with respect to compression is fixed, and
+ not optional. In contrast, the -z ctf option to the link-editor does
+ not compress by default. Compression can be enabled by specifying ld
+ -z ctf=compress.
+
+
+ Compression is done using the libz compression library deflate algo-
+ rithm. See ctf(5), and libz(3). Although conceptually similar in na-
+ ture, CTF compression is distinct from, and does not use standard ELF
+ section compression. This is because CTF compression predates the ELF
+ mechanism. ELF section compression is documented in Oracle Solaris 11.4
+ Linkers and Libraries Guide.
+
+ Labels
+ Labels can be associated with CTF data. Labels can be useful for iden-
+ tification purposes, but are optional, unless uniquification is de-
+ sired, in which case labels must be provided. When using the ctfmerge
+ and ctfconvert utilities, labels are specified using the -l, or -L op-
+ tions. When using ld -z ctf, labels are specified with the label, or
+ label-env suboptions.
+
+ Uniquification
+ When multiple objects share common type definitions provided by a cen-
+ tral core object, the size of the overall CTF data can be greatly re-
+ duced through the process of uniquification. Uniquification removes de-
+ finitions found the core object from other objects, leaving those other
+ objects with only the additional definitions that are unique to them.
+ The core object is usually referred to as the parent, and the other ob-
+ ject as the child. A given child can only have one parent, and the par-
+ ent/child relationship is only one level deep, with no further descen-
+ dants. The CTF data in the parent and child objects to be uniquified
+ should define a common label, identifying them as sharing common type
+ definitions.
+
+
+ When using the ctfmerge utility, uniquification is specified using the
+ -d and -D options. When using ld -z ctf, uniquification is specified
+ with the uniqify-file, and uniqify-label suboptions.
+
+
+ Uniquification is typically applied only to kernel modules. In the ker-
+ nel environment, the genunix kernel module is the parent, and the other
+ kernel modules delivered with the system are uniquified against it. For
+ non-kernel objects, the benefits of unification are minor, the overhead
+ in terms of management complexity significant, and unification is not
+ recommended.
+
+ Additive Merges
+ There are cases where it is desired to issue a new version of an object
+ that has an existing uniquification relationship to another object. A
+ common example occurs when operating system kernel modules are patched.
+ For this to work smoothly, it is necessary to preserve all preexisting
+ CTF data, unchanged, while adding any necessary additional definitions
+ needed by the replacement object. This operation is known as an addi-
+ tive merge. In the case of an additive merge, a final uniquification is
+ performed against the CTF data in the previous version of the module.
+ The result is the placement of new and changed data after the existing
+ data, thus preserving the existing type definitions.
+
+
+ When using the ctfmerge utility, an additive merge is done using the -w
+ option. When using ld -z ctf, an additive merge is specified with the
+ additive-merge suboption.
+
+EXAMPLES
+ The following examples demonstrate the options for adding CTF data to a
+ program named prog, built from 3 source files, main.c, sub1.c, and
+ sub2.c. In each case, the options for the native cc compiler, and gcc,
+ are shown.
+
+ Example 1 Add CTF Using ctfconvert and ctfmerge
+
+
+
+ The most basic way to add CTF to a program is to use ctfconvert to add
+ CTF to each source file as it is compiled into a relocatable object,
+ and then to apply ctfmerge to the resulting program.
+
+
+ # cc
+ % cc -c -g main.c
+ % ctfconvert -S main.o
+ % cc -c -g sub1.c
+ % ctfconvert -S sub1.o
+ % cc -c -g sub2.c
+ % ctfconvert -S sub2.o
+ % cc -o prog main.o sub1.o sub2.o
+ % ctfmerge -o prog main.o sub1.o sub2.o
+
+
+
+
+ When using gcc, the need for the -g option goes away, and the -gctf op-
+ tion is used instead of running ctfconvert .
+
+ # gcc
+ % gcc -c -gctf main.c
+ % gcc -c -gctf sub1.c
+ % gcc -c -gctf sub2.c
+ % gcc -o prog main.o sub1.o sub2.o
+ % ctfmerge -o prog main.o sub1.o sub2.o
+
+
+
+
+ Without the need to run ctfconvert on each relocatable object, the gcc
+ version can be further reduced to a single invocation of the compiler
+ to compile all source files in a single call. Note that the compile and
+ link steps must still be kept separate, as ctfmerge needs to examine
+ each input object individually. .
+
+ # gcc
+ % gcc -c -gctf main.c sub1.c sub2.c
+ % gcc -o prog main.o sub1.o sub2.o
+ % ctfmerge -o prog main.o sub1.o sub2.o
+
+
+ Example 2 Add CTF Using ctfmerge -a
+
+
+
+ The -a option to ctfmerge can be used to simplify the previous example,
+ by removing the requirement to run ctfconvert on each input object. A
+ convert operation is still needed, but in this version, is done by
+ ctfmerge as each object enters the merge operation. When a program is
+ built once, the cost of these two approaches is identical. In a case
+ where the code is being modified and built repeatedly as part of code
+ development, possibly driven by the make utility, it can be marginally
+ more expensive, as the convert step is done for every input object af-
+ ter every link, as opposed to once when each input object is recom-
+ piled. This cost may be noticed when working on very large code bases,
+ but probably not otherwise. Conversely, the required Makefile rules
+ will be simpler.
+
+
+ # cc
+ % cc -c -g main.c
+ % cc -c -g sub1.c
+ % cc -c -g sub2.c
+ % cc -o prog main.o sub1.o sub2.o
+ % ctfmerge -a -o prog main.o sub1.o sub2.o
+
+
+
+
+ While the -a option to ctfmerge can be used with gcc as well, it pro-
+ vides no benefit when the -gctf option to gcc is used, as the resulting
+ input objects are created with CTF, and do not need ctfmerge to gener-
+ ate it.
+
+
+
+ For smaller programs, this can be simplified further, by passing all
+ source files to a single invocation of the compiler. Note that compile
+ and link steps must still be kept separate, as ctfmerge needs to exam-
+ ine each input object individually.
+
+
+ # cc
+ % cc -c -g main.c sub1.c sub2.c
+ % cc -o prog main.o sub1.o sub2.o
+ % ctfmerge -a -o prog main.o sub1.o sub2.o
+
+
+ Example 3 Add CTF Using ld -z ctf
+
+
+
+ The link-editor can be used to simplify the addition of CTF by dropping
+ the use of ctfconvert and ctfmerge, and instead using the link-editor's
+ -z ctf option to invoke those operations from within the link-edit. The
+ cost of this approach is similar to that of the previous example which
+ used ctfmerge -a. Note that the cc version requires the use of the
+ convert suboption to -z ctf, while the gcc version does not.
+
+
+ # cc
+ % cc -c -g main.c
+ % cc -c -g sub1.c
+ % cc -c -g sub2.c
+ % cc -o prog main.o sub1.o sub2.o -zctf=convert
+
+ # gcc
+ % gcc -c -gctf main.c
+ % gcc -c -gctf sub1.c
+ % gcc -c -gctf sub2.c
+ % gcc -o prog main.o sub1.o sub2.o -zctf
+
+
+
+
+ For smaller programs, this can be simplified further, by passing all
+ source files to a single invocation of the compiler.
+
+
+ # cc
+ % cc -c -g main.c sub1.c sub2.c
+ % cc -o prog main.o sub1.o sub2.o -zctf=convert
+
+ # gcc
+ % gcc -c -gctf main.c sub1.c sub2.c
+ % gcc -o prog main.o sub1.o sub2.o -zctf
+
+
+
+
+ Unlike the version that employs the -a to ctfmerge, the compile and
+ link do not need to be kept separate, so this can be reduced to a sin-
+ gle operation.
+
+
+ # cc
+ % cc -g -o prog main.c sub1.c sub2.c -zctf=convert
+
+ # gcc
+ % gcc -gctf -o prog main.c sub1.c sub2.c -zctf
+
+
+HISTORY
+ The CTF version 2 format has been used in the construction of Solaris
+ since Sun Solaris 9. Version 1, the initial development version, was
+ never included in a user visible release.
+
+
+ The required ELF section type for .SUNW_ctf sections was changed from
+ SHT_PROGBITS to SHT_SUNW_CTF in the Oracle Solaris 11.4.75 release.
+ Support for existing objects with CTF in SHT_PROGBITS sections is re-
+ tained to to support historical usage.
+
+
+ Support for CTF version 3, was added in the Oracle Solaris 11.4.81 re-
+ lease.
+
+
+ Support for reading GNU CTF from relocatable objects created by the gcc
+ compilers and translating it to the native CTF representation was added
+ in the Oracle Solaris 11.4.84 release.
+
+SEE ALSO
+ ctfconvert(1), ctfdump(1), ctfmerge(1), ld(1), mdb(1), libz(3), ctf(5),
+ dtrace(8)
+
+
+ Oracle Solaris 11.4 Linkers and Libraries Guide
+
+Oracle Solaris 11.4 2 May 2025 ctf(7)
diff -NurbBw 11.4.81/man7/scale.7 11.4.84/man7/scale.7
--- 11.4.81/man7/scale.7 2025-08-17 09:30:02.577338346 -0700
+++ 11.4.84/man7/scale.7 2025-08-17 09:30:24.849755932 -0700
@@ -20,7 +20,7 @@
the utility in question, as follows.
df(8), du(1), ipstat(8), ls(1), plimit(1), pmadvise(1), pmap(1), ps(1),
- quota(8), ramdiskadm(8), size(1), swap(8), tcpstat(8),
+ quota(8), ramdiskadm(8), savecore(8), size(1), swap(8), tcpstat(8)
--scale=max,1024
@@ -94,7 +94,7 @@
SEE ALSO
du(1), ls(1), plimit(1), pmadvise(1), pmap(1), ps(1), size(1), df(8),
- dlstat(8), flowstat(8), ipstat(8), quota(8), ramdiskadm(8), swap(8),
- tcpstat(8),
+ dlstat(8), flowstat(8), ipstat(8), quota(8), ramdiskadm(8),
+ savecore(8), swap(8), tcpstat(8),
-Oracle Solaris 11.4 11 Dec 2024 sc...e(7)
+Oracle Solaris 11.4 24 June 2025 sc...e(7)
diff -NurbBw 11.4.81/man7/solaris-kz.7 11.4.84/man7/solaris-kz.7
--- 11.4.81/man7/solaris-kz.7 2025-08-17 09:30:02.641699951 -0700
+++ 11.4.84/man7/solaris-kz.7 2025-08-17 09:30:24.915079862 -0700
@@ -1155,6 +1155,64 @@
+ Example 3 Install a Kernel Zone into NFS storage
+
+
+
+ Configure a system hosting the NFS storage object as an NFS server
+ first. Note that it is not recommended to access the storage files with
+ root privileges.
+
+
+
+ nfsserver# svcadm enable svc:/network/nfs/server:default
+ nfsserver# zfs create -o share.nfs=on rpool/kznfs
+ nfsserver# useradd -c "NFS user" -u 1000 -m -g staff nfsuser
+ nfsserver# chown nfsuser:staff /rpool/kznfs
+
+
+
+
+
+ Configure the Kernel Zone host system to be an NFS client. The user ID
+ must be identical on both systems.
+
+
+
+ kzhost# svcadm enable svc:/network/nfs/client:default
+ kzhost# useradd -c "NFS user" -u 1000 -m -g staff nfsuser
+
+
+
+
+
+ Verify the mapping works by creating and destroying a test NFS file.
+
+
+
+ kzhost# suriadm create -p file-permissions=600 -p create-size=10m \
+ nfs://nfsuser:staff@nfsserver/rpool/kznfs/test
+ PROPERTY VALUE
+ mapped-devs /dev/dsk/c10t1d0
+ kzhost# suriadm destroy nfs://nfsuser:staff@nfsserver/rpool/kznfs/test
+
+
+
+
+
+ Create, install, and boot the Kernel Zone.
+
+
+
+ kzhost# zonecfg -z kznfs1 "create -t SYSsolaris-kz; \
+ select device 0; \
+ set storage=nfs://nfsuser:staff@nfsserver/rpool/kznfs/kznfs1; \
+ set create-size=20g; end; commit"
+ kzhost# zoneadm -z kznfs1 install -x storage-create-missing
+ kzhost# zoneadm -z kznfs1 boot
+
+
+
SEE ALSO
zlogin(1), ai_manifest(5), brands(7), resource-management(7), zones(7),
archiveadm(8), ntpd(8), poolcfg(8), psrset(8), zfs(8), zoneadm(8),
@@ -1181,4 +1239,4 @@
this will only succeed if coreadm(8) has configured a location for and
enabled kernel zone core dumps.
-Oracle Solaris 11.4 12 Oct 2023 so...z(7)
+Oracle Solaris 11.4 2 Apr 2025 so...z(7)
diff -NurbBw 11.4.81/man7/suri.7 11.4.84/man7/suri.7
--- 11.4.81/man7/suri.7 2025-08-17 09:30:02.678069643 -0700
+++ 11.4.84/man7/suri.7 2025-08-17 09:30:24.958018837 -0700
@@ -113,7 +113,7 @@
via an alternate path.
- The lu URI type does not support the create operation.
+ The lu URI type does not support the create/destroy operation.
iSCSI URI
iscsi:///luname.naa.<ID>
@@ -178,10 +178,10 @@
to the logical unit is configured to be independent of the initiator.
- The iscsi URI type does not support the create operation.
+ The iscsi URI type does not support the create/destroy operation.
NFS URI
- nfs://<user>:<group>@<host>[:<port>]/<nfs-share-path>/<file>
+ nfs://<user>:<group>@<host>[:<port>]/<nfs-share-absolute-path>/<file>
@@ -193,20 +193,25 @@
The NFS URI specifies an object based on a labeled lofi device created
- on the given NFS file. The NFS file will be accessed with credentials
- derived from user and group. User and group can be given as usernames
- or userids. The host can be given as an IPv4 address, IPv6 address, or
- as a hostname. IPv6 addresses must be enclosed in square brackets.
+ on the given NFS file specified by its absolute path. The NFS file will
+ be accessed with credentials derived from user and group. User and
+ group can be given as usernames or userids. The host can be given as an
+ IPv4 address, IPv6 address, or as a hostname. IPv6 addresses must be
+ enclosed in square brackets.
Components of the NFS share path may only include characters from the
POSIX.1-2008 Portable Filename Character Set, 0-9a-zA-Z._-.
- The nfs URI type supports the create operation.
+ The nfs URI type supports the create/destroy operation.
+
+
+ See example in solaris-kz(7) on how to install a Kernel Zone into NFS
+ storage.
File URI
- file://<user>:<group>@<host>/<file-path>
+ file://<user>:<group>@<host>/<file-absolute-path>
@@ -218,18 +223,18 @@
The file URI specifies an object based on a labeled lofi device created
- on the given local file. The file will be accessed with credentials de-
- rived from user and group. User and group can be given as usernames or
- userids. The host does not need to be specified, but must be localhost
- when given.
+ on the given local file specified by its absolute path. The file will
+ be accessed with credentials derived from user and group. User and
+ group can be given as usernames or userids. The host does not need to
+ be specified, but must be localhost when given.
Components of the file path may only include characters from the
POSIX.1-2008 Portable Filename Character Set, 0-9a-zA-Z._-.
- The file URI type supports the create operation, and may also be mapped
- to a removable/read-only device.
+ The file URI type supports the create/destroy operation, and may also
+ be mapped to a removable/read-only device.
Getting URIs
To avoid errors by generating URIs manually, the suriadm(8) subcommand
@@ -253,8 +258,8 @@
SEE ALSO
- attributes(7), fcadm(8), iscsiadm(8), lofi(4D), sasinfo(8), suriadm(8),
- zpool(8)
+ lofi(4D), attributes(7), solaris-kz(7), fcadm(8), iscsiadm(8), sas-
+ info(8), suriadm(8), zpool(8)
Small Computer System Interface-3 (SCSI-3)
@@ -270,4 +275,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 16 Jan 2024 suri(7)
+Oracle Solaris 11.4 3 Apr 2025 suri(7)
diff -NurbBw 11.4.81/man8/add_drv.8 11.4.84/man8/add_drv.8
--- 11.4.81/man8/add_drv.8 2025-08-17 09:30:02.719952931 -0700
+++ 11.4.84/man8/add_drv.8 2025-08-17 09:30:25.000853049 -0700
@@ -63,20 +63,20 @@
The first line sets all devices exported by the sd node to 0640 permis-
sions, owned by root, with group sys. In the second line, devices such
- as a,cu and z,cu exported by the zs driver are set to 0600 permis-
- sion, owned by uucp, with group uucp. In the third line the kmem device
- exported by the mm driver is set to 0640 permission, owned by root,
- with group bin.
+ as a,cu and z,cu exported by the zs driver are set to 0600 permission,
+ owned by uucp, with group uucp. In the third line the kmem device ex-
+ ported by the mm driver is set to 0640 permission, owned by root, with
+ group bin.
Running add_drv from a postinstall Script
- When running add_drv from within the context of a package's postinstall
- script, you must consider whether the package is being added to a sys-
- tem image or to a running system. When a package is being installed on
- a system image, the BASEDIR variable refers to the image's base direc-
- tory. In this situation, add_drv should be invoked with -b $BASEDIR.
- This causes add_drv only to update the image's system files; a reboot
- of the system or client would be required to make the driver opera-
- tional.
+ When running add_drv from within the context of a SVR4 package's
+ postinstall script, you must consider whether the package is being
+ added to a system image or to a running system. When a package is being
+ installed on a system image, the BASEDIR variable refers to the image's
+ base directory. In this situation, add_drv should be invoked with -b
+ $BASEDIR. This causes add_drv only to update the image's system files;
+ a reboot of the system or client would be required to make the driver
+ operational.
When a package is being installed on the running system itself, the
@@ -108,15 +108,21 @@
The -b option is described below.
+
+ When installing a driver from an IPS package, the driver action handles
+ this without requiring a script. See pkg(7) for details on specifying
+ the options that can be passed to add_drv as part of package installa-
+ tion.
+
OPTIONS
-b basedir
Installs the driver on the system with a root directory of basedir
- rather than installing on the system executing add_drv . This op-
- tion is typically used in package post-installation scripts when
+ rather than installing on the system executing add_drv. This option
+ is typically used in SVR4 package post-installation scripts when
the package is not being installed on the system executing the
- pkgadd command. The system using basedir as its root directory
- must reboot to complete the driver installation.
+ pkgadd command. The system using basedir as its root directory must
+ reboot to complete the driver installation.
Note -
@@ -231,11 +235,9 @@
- The following example adds the SUNW,example driver to a 32-bit system,
- with an alias name of SUNW,alias. It assumes the driver has already
- been copied to /usr/kernel/drv.
-
-
+ The following example adds the SUNW,example driver to a system, with an
+ alias name of SUNW,alias. It assumes the driver has already been copied
+ to the appropriate subdirectory under /usr/kernel/drv.
example# add_drv -m '* 0666 bin bin','a 0644 root sys' \
@@ -360,16 +357,10 @@
example# add_drv -i '"pci10c5,25"' smc
-
EXIT STATUS
add_drv returns 0 on success and 1 on failure.
FILES
- /kernel/drv
-
- 32-bit boot device drivers
-
-
/kernel/drv/sparcv9
64-bit SPARC boot device drivers
@@ -380,27 +371,16 @@
64-bit x86 boot device drivers
- /usr/kernel/drv
-
- other 32-bit drivers that could potentially be shared between plat-
- forms
-
-
/usr/kernel/drv/sparcv9
other 64-bit SPARC drivers that could potentially be shared between
- platforms
+ SPARC platforms
/usr/kernel/drv/amd64
other 64-bit x86 drivers that could potentially be shared between
- platforms
-
-
- /platform/`uname -i`/kernel/drv
-
- 32-bit platform-dependent drivers
+ x86 platforms
/platform/`uname -i`/kernel/drv/sparcv9
@@ -466,8 +446,7 @@
figuration boot, device links in /dev and references to these files may
no longer be valid (see the -v flag). If a reconfiguration boot would
be required to complete the driver installation, add_drv will fail un-
- less the -f option is specified. See Example 3 in the EXAMPLES sec-
- tion.
+ less the -f option is specified. See Example 3 in the EXAMPLES section.
With the introduction of the device policy several drivers have had
@@ -509,8 +486,8 @@
rebooted, thus assuring an environment in which the driver can be con-
figured properly.
-BUGS
+
Previous versions of add_drv accepted a pathname for device_driver.
This feature is no longer supported and results in failure.
-Oracle Solaris 11.4 23 Jan 2017 add_drv(8)
+Oracle Solaris 11.4 23 Jun 2025 add_drv(8)
diff -NurbBw 11.4.81/man8/auditreduce.8 11.4.84/man8/auditreduce.8
--- 11.4.81/man8/auditreduce.8 2025-08-17 09:30:02.769314907 -0700
+++ 11.4.84/man8/auditreduce.8 2025-08-17 09:30:25.048378367 -0700
@@ -82,7 +82,7 @@
Delete input files after they are read if the entire run is suc-
cessful. If auditreduce detects an error while reading a file, then
- that file is not deleted. If -D is specified, -A, -C and -O are
+ that file is not deleted. If -D is specified, -A, -C, and -O are
also implied. suffix is given to the -O option. This helps prevent
the loss of audit records by ensuring that all of the records are
written, only complete files are processed, and the records are
@@ -259,10 +259,10 @@
annotation=text
- Select records that contain annotation which contains the text.
- The text may be a regular expression. For example, annota-
- tion='.*' will select all audit records which contain any anno-
- tation. For more information, see the regex(7) man page.
+ Select records that contain an annotation which matches the
+ given regular expression. For example, annotation='.*' will se-
+ lect all audit records which contain any annotation. For more
+ information, see the regex(7) man page.
auth=authorization
@@ -356,8 +356,8 @@
pid=ID
Select records containing process objects with the specified ID
- where ID is a process ID. Process are objects when they are re-
- ceivers of signals.
+ where ID is a process ID. Processes are objects when they are
+ receivers of signals.
procgroup=group
@@ -500,7 +500,7 @@
The default is 00 for hh, mm and ss.
An offset can be specified as: +n d|h|m| s where n is a number of
- units, and the tags d, h, m, and s stand for days, hours, minutes
+ units, and the tags d, h, m, and s stand for days, hours, minutes,
and seconds, respectively. An offset is relative to the starting
time. Thus, this form can only be used with the -b option.
@@ -683,9 +683,9 @@
ted. The binary file contents is Uncommitted.
SEE ALSO
- praudit(8), audit.log(5), audit_class(5), audit_tags(5), group(5),
- hosts(5), passwd(5), attributes(7), audit_flags(7), privileges(7),
- smf(7)
+ audit.log(5), audit_class(5), audit_tags(5), group(5), hosts(5),
+ passwd(5), attributes(7), audit_flags(7), privileges(7), smf(7),
+ admhist(8), auditrecord(8), praudit(8)
Managing Auditing in Oracle Solaris 11.4
@@ -720,4 +720,4 @@
HISTORY
The auditreduce command was added in Solaris 2.3.
-Oracle Solaris 11.4 21 Jun 2021 auditreduce(8)
+Oracle Solaris 11.4 23 Jun 2025 auditreduce(8)
diff -NurbBw 11.4.81/man8/beadm.8 11.4.84/man8/beadm.8
--- 11.4.81/man8/beadm.8 2025-08-17 09:30:02.828959975 -0700
+++ 11.4.84/man8/beadm.8 2025-08-17 09:30:25.110854682 -0700
@@ -33,8 +33,7 @@
beadm rename BeFmri newBeFmri
- beadm set-policy {-n [-]policy [-n
- [-]policy2] ...} BeFmri [BeFmri2 .
+ beadm set-policy {-n [-]policy [-n [-]policy2]...} BeFmri [BeFmri...]
beadm activate BeFmri
@@ -42,9 +41,9 @@
DESCRIPTION
The beadm command is the user interface for managing ZFS Boot Environ-
ments (BEs). This utility is intended to be used by system administra-
- tors who want to manage multiple Oracle Solaris instances on a single
- system. Users identify BEs that are to be managed by using BeFmris. For
- more information on BeFmris, see the fmri(7) man page.
+ tors to manage multiple Oracle Solaris instances on a single system.
+ Users identify BEs that are to be managed by using BeFmris. For more
+ information on BeFmris, see the fmri(7) man page.
Using beadm, you can do the following:
@@ -96,8 +95,12 @@
Displays command usage.
- beadm create [-a] [-d description] [-e non-activeBeFmri | BeFmri@snap-
- shot] [-o property=value] ... BeFmri
+
+
+ beadm create [-a] [-d description]
+ [-e non-activeBeFmri | BeFmri@snapshot]
+ [-o property=value]... BeFmri
+
Creates a new boot environment named BeFmri. If the -e option is
not provided, the new boot environment will be created as a clone
@@ -122,9 +125,9 @@
-e non-activeBeFmri
Create a new BE from an existing inactive BE that resides in
- the same zpool as the new BE. Copying BE across zpools is not
- allowed. In a zone BE, only bootable BEs can be used with this
- option.
+ the same zpool as the new BE. Copying a BE between different
+ zpools is not allowed. In a zone BE, only bootable BEs can be
+ used with this option.
-e beFmri@snapshot
@@ -170,10 +173,9 @@
BEs that are not bootable but are not marked as active on reboot
can be destroyed.
-
-f
- Forcefully unmounts the boot environment if it is currently
+ Forcibly unmounts the boot environment if it is currently
mounted.
@@ -204,18 +208,17 @@
The Flags field indicates whether the boot environment is active
now, represented by N; active on reboot, represented by R; or both,
represented by NR. Unbootable global zone BEs are represented by an
- exclamation point (!). In such BEs the ZFS pool version that they
- support is lower than the pool version of the boot pool. Unbootable
- BEs inside of a zone BE are represented by an exclamation point
- (!). In such zones, the ! flag means that boot environment's boot
- artifacts are not resident on the boot pool and, therefore, that BE
- is NOT directly bootable. (To transfer a BE's boot artifacts to the
- boot pool, either make the BE activate with the activate subcom-
- mand, or change the BE's policy to noevict with the set-policy sub-
- command). Zone boot environments that have no corresponding global
- zone boot environment are represented by an O, indicating they are
- orphaned.
-
+ exclamation point (!). In such BEs the highest ZFS pool version
+ that they support is lower than the pool version of the boot pool.
+ Unbootable BEs inside of a zone BE are also represented by an ex-
+ clamation point (!). In such zones, the ! flag means that boot en-
+ vironment's boot artifacts are not resident on the boot pool and,
+ therefore, that BE is NOT directly bootable. (To transfer a BE's
+ boot artifacts to the boot pool, either make the BE active with the
+ activate subcommand, or change the BE's policy to noevict with the
+ set-policy subcommand). Zone boot environments that have no corre-
+ sponding global zone boot environment are represented by an O, in-
+ dicating they are orphaned.
-a
@@ -250,13 +253,13 @@
The -o option can be specified alone for displaying attributes
in a tabular format. It can also be specified together with the
- -H option for semicolon-delimited parsable output.
+ -H option for semicolon-delimited parseable output.
If an attribute has multiple values and the -H option is not
specified, each value will be displayed in a separate row under
its own column heading. If a multi-value attribute is specified
together with attributes that have a single value, data of the
- single-value attribute will only be displayed once under it's
+ single-value attribute will only be displayed once under its
own column heading.
If an attribute has multiple values, and both the -o and -H op-
@@ -337,13 +339,12 @@
-
-H
- Request machine parsable output. The output format is a list of
- lines with semicolon-delimited fields. The space field is dis-
- played in bytes and the created field is displayed in UTC for-
- mat.
+ Request machine parseable output. The output format is a list
+ of lines with semicolon-delimited fields. The space field is
+ displayed in bytes and the created field is displayed in UTC
+ format.
If no option is specified, one line with the following fields
is displayed for each boot environment. When running in the
@@ -378,8 +379,10 @@
- beadm list -z zonename [-z zonename]... [[-a | -ds] | [-o
- attr[,attr]...]...] [-H]
+
+ beadm list -z zonename [-z zonename]...
+ [[-a | -ds] | [-o attr[,attr]...]...] [-H]
+
Lists information about all zone BEs in the given zones. This com-
mand is only valid when executing from the global zone. The speci-
@@ -454,10 +455,8 @@
boot pool dataset will be mounted under <mountpoint>/bootpool_data.
This directory will be automatically created when the dataset is
mounted, and automatically removed when the BE is unmounted with
- the beadm
- unmount subcommand. Note that unmounting the
- BE through another mechanism will NOT clean up this created direc-
- tory.
+ the beadm unmount subcommand. Note that unmounting the BE through
+ another mechanism will NOT clean up this created directory.
beadm unmount [-f] BeFmri
@@ -466,8 +465,8 @@
-f
- Forcefully unmount the boot environment even if it is currently
- busy.
+ Force the unmount of the boot environment even if it is cur-
+ rently busy.
@@ -477,7 +476,10 @@
BE, only bootable BEs can be renamed.
- beadm set-policy {-n [-]policy [-n [-]policy2] ...} BeFmri [BeFmri2 .
+
+
+ beadm set-policy {-n [-]policy [-n [-]policy2]...} BeFmri [BeFmri...]
+
Sets (or unsets) the specified set of policies for the specified
list of boot environments. Multiple -n arguments are permitted. The
@@ -499,7 +500,7 @@
svc:/system/auto-update:cleanup instance based on the
config/keep property.
- To opt an auto-update boot evnironment out of automatic
+ To opt an auto-update boot environment out of automatic
removal and allow it to be preserved and managed manu-
ally set the policy to static.
@@ -520,10 +521,9 @@
-
beadm activate BeFmri
- Makes BE specified by BeFmri as the active BE on next reboot. In a
+ Makes BE specified by BeFmri the active BE on next reboot. In a
zone BE, only bootable BEs can be activated.
@@ -1072,7 +1049,7 @@
FILES
- <log_dir>/beadm/beadm.yyyymmdd_hhmmss.<pid>.log
+ log_dir/beadm/beadm.yyyymmdd_hhmmss.pid.log
Log used for capturing beadm debugging output. A log file is cre-
ated in one of the following 3 locations for each command invoca-
@@ -1135,7 +1112,7 @@
SEE ALSO
- zpool(8), zfs(8), fmri(7), attributes(7)
+ attributes(7), fmri(7), zfs(8), zpool(8)
HISTORY
The pool_version property was added in Oracle Solaris 11.4.30.
@@ -1163,4 +1140,4 @@
The beadm command was introduced in Oracle Solaris 11.0.0.
-Oracle Solaris 11.4 13 Sep 2024 beadm(8)
+Oracle Solaris 11.4 23 Jun 2025 beadm(8)
diff -NurbBw 11.4.81/man8/boot.8 11.4.84/man8/boot.8
--- 11.4.81/man8/boot.8 2025-08-17 09:30:02.898896360 -0700
+++ 11.4.84/man8/boot.8 2025-08-17 09:30:25.180471579 -0700
@@ -32,10 +32,10 @@
alone.
- Once the kernel is loaded, it starts the UNIX system, mounts the neces-
- sary file systems (see vfstab(5)), and runs /usr/sbin/init to bring the
- system to the "initdefault" state specified in /etc/inittab. See init-
- tab(5).
+ Once the kernel is loaded, it starts the Solaris system, mounts the
+ necessary file systems (see vfstab(5)), and runs /usr/sbin/init to
+ bring the system to the "initdefault" state specified in /etc/inittab.
+ See inittab(5).
Verified Boot
Verified boot in Oracle Solaris secures a system's boot process. The
@@ -149,7 +147,7 @@
On recent sun4v SPARC systems, it is possible to network boot over a
VLAN that requires tagging by the client, rather than relying on the
switch to provide automatic tagging. This functionality is enabled by
- specifying the VLAN id as a modifier to the net path, For example, to
+ specifying the VLAN id as a modifier to the net path. For example, to
boot on VLAN 816, the command would be:
boot net:vlan=816
@@ -933,21 +931,21 @@
the case of GRUB running on BIOS firmware, that other location is a
dedicated partition known as the BIOS Boot Partition. Once GRUB's boot
sector code loads the rest of GRUB into memory, the boot process con-
- tinues in earnest. Booting from a DVD, the firmware's reading special
- data structures (defined by the El Torito Bootable CD Specification)
- from the disc and loading sectors from the DVD into memory, as defined
- by those structures. These sectors comprise the first stage boot pro-
- gram. This boot program then loads the next stage, which, in the case
- of Oracle Solaris, is GRUB itself. Booting from the network is yet a
- different process on BIOS systems. Bootable network adapters include
- firmware that complies with the PXE (Preboot eXecution Environment)
- specification. When activated, the PXE firmware performs a DHCP ex-
- change on the network, and downloads the BootFile that the DHCP server
- included in the DHCP response from the TFTP server that is also in the
- DHCP response. For Oracle Solaris, this BootFile (pxegrub2, or equiva-
- lent) is GRUB itself. GRUB then proceeds, ultimately, to download the
- UNIX kernel and the boot archive (see below), loads them into memory,
- and transfers control to UNIX.
+ tinues in earnest. Booting from a DVD, the firmware reads special data
+ structures (defined by the El Torito Bootable CD Specification) from
+ the disc and loads sectors from the DVD into memory, as defined by
+ those structures. These sectors comprise the first stage boot program.
+ This boot program then loads the next stage, which, in the case of Ora-
+ cle Solaris, is GRUB itself. Booting from the network is yet a differ-
+ ent process on BIOS systems. Bootable network adapters include firmware
+ that complies with the PXE (Preboot eXecution Environment) specifica-
+ tion. When activated, the PXE firmware performs a DHCP exchange on the
+ network, and downloads the BootFile that the DHCP server included in
+ the DHCP response from the TFTP server that is also in the DHCP re-
+ sponse. For Oracle Solaris, this BootFile (pxegrub2, or equivalent) is
+ GRUB itself. GRUB then proceeds, ultimately, to download the kernel and
+ the boot archive (see below), loads them into memory, and transfers
+ control to the kernel.
For systems with UEFI-based firmware, the boot process is quite differ-
@@ -971,15 +969,15 @@
the BootFile from the DHCP server. Once the UEFI boot application
(which is GRUB itself) specified in the BootFile (grub2netx64.efi, or
equivalent) is downloaded to the UEFI client, it (GRUB) is executed. As
- with the BIOS network boot process, GRUB downloads the UNIX kernel and
- boot archive from the DHCP-specified TFTP server, loads them into mem-
- ory, then transfers control to UNIX.
+ with the BIOS network boot process, GRUB downloads the kernel and boot
+ archive from the DHCP-specified TFTP server, loads them into memory,
+ then transfers control to the kernel.
Once GRUB is running, it executes script commands in its configuration
file, grub.cfg, and, when directed to do so, loads the Oracle Solaris
- kernel (UNIX kernel) and a pre-constructed boot archive that contains
- kernel modules and essential data required for boot.
+ kernel and a pre-constructed boot archive that contains kernel modules
+ and essential data required for boot.
If the device identified by GRUB as the boot device contains a ZFS
@@ -1003,12 +1001,12 @@
Kernel initialization starts when GRUB finishes loading the boot
archive and hands control over to the unix binary. At this point, GRUB
- becomes inactive and no more I/O occurs with the boot device. The UNIX
- operating system initializes, links in the necessary modules from the
- boot archive and mounts the root file system on the real root device.
- At this point, the kernel regains storage I/O, mounts additional file
- systems (see vfstab(5)), and starts various operating system services
- (see smf(7)).
+ becomes inactive and no more I/O occurs with the boot device. The So-
+ laris operating system initializes, links in the necessary modules from
+ the boot archive and mounts the root file system on the real root de-
+ vice. At this point, the kernel regains storage I/O, mounts additional
+ file systems (see vfstab(5)), and starts various operating system ser-
+ vices (see smf(7)).
Enabling Automatic Rebooting (x86)
The Oracle Solaris operating system supports an smf(7) property that
@@ -1084,11 +1082,11 @@
milestone.
- An update to any kernel file, driver, module or driver configuration
- file that needs to be included in the boot archive after the umountall
- service is complete will result in a failed boot archive consistency
- check during the next boot. To avoid this, it is recommended to always
- shut down a machine cleanly.
+ An update to any kernel file, driver, module, or configuration file
+ that needs to be included in the boot archive after the umountall ser-
+ vice is complete will result in a failed boot archive consistency check
+ during the next boot. To avoid this, it is recommended to always shut
+ down a machine cleanly.
If an update is required to the kernel after completion of the umoun-
@@ -1206,18 +1204,16 @@
form/i86pc/kernel/amd64/unix.
X86 BOOT SEQUENCE DETAILS
- After a PC-compatible machine is turned on, the system firmware exe-
- cutes a power-on self test (POST), runs BIOS extensions in peripheral
- board ROMs, and locates and installs firmware extensions from periph-
- eral board ROMs, and begins the boot process through a firmware-spe-
- cific mechanism.
+ After an x86 machine is turned on, the system firmware executes a
+ power-on self test (POST), locates and installs firmware extensions
+ from peripheral board ROMs, and begins the boot process through a
+ firmware-specific mechanism.
For BIOS systems, software interrupt INT 19h is executed. The INT 19h
- handler typically performs the standard PC-compatible boot, which con-
- sists of trying to read the first physical sector from the first hard
- disk. The processor then jumps to the first byte of the sector image in
- memory.
+ handler typically performs the standard x86 boot, which consists of
+ trying to read the first physical sector from the first hard disk. The
+ processor then jumps to the first byte of the sector image in memory.
For UEFI firmware, the process is quite different, as previously ex-
@@ -1252,8 +1248,8 @@
If the disk is partitioned with the traditional DOS scheme, the master
boot program finds the active partition in the DOS partition table,
loads its first sector, and jumps to that which it loaded into memory.
- This completes the standard PC-compatible hard disk boot sequence. If
- GRUB's first stage is installed in the MBR (see the -m option of the
+ This completes the standard x86 hard disk boot sequence. If GRUB's
+ first stage is installed in the MBR (see the -m option of the
bootadm(8) install-bootloader subcommand), then the remainder of GRUB
is loaded directly from the Oracle Solaris DOS partition, regardless of
the active partition.
@@ -1469,8 +1461,9 @@
SEE ALSO
kmdb(1), uname(1), uadmin(2), bootparams(5), inittab(5), vfstab(5),
- wanboot.conf(5), attributes(7), filesystem(7), smf(7), bootadm(8), eep-
- rom(8), init(8), kernel(8), shutdown(8), svcadm(8), svccfg(8), zpool(8)
+ wanboot.conf(5), attributes(7), filesystem(7), grub(7), smf(7),
+ bootadm(8), eeprom(8), init(8), kernel(8), shutdown(8), svcadm(8),
+ svccfg(8), zpool(8)
RFC 903, A Reverse Address Resolution Protocol
@@ -1508,4 +1501,4 @@
platform-name can be found using the -i option of uname(1). hardware-
class-name can be found using the -m option of uname(1).
-Oracle Solaris 11.4 25 Mar 2020 boot(8)
+Oracle Solaris 11.4 23 Jun 2025 boot(8)
diff -NurbBw 11.4.81/man8/bootadm.8 11.4.84/man8/bootadm.8
--- 11.4.81/man8/bootadm.8 2025-08-17 09:30:02.943939433 -0700
+++ 11.4.84/man8/bootadm.8 2025-08-17 09:30:25.230034969 -0700
@@ -17,7 +17,7 @@
/usr/sbin/bootadm boot-pool {
[{add|remove} [-P rpool] <device list>] |
list [-P rpool] |
- resync [-P rpool] [-vA] [<BE_list>] |
+ resync [-P rpool] [-vA] [<BE-list>] |
set [-P rpool] <param>=<value> ... }
@@ -33,29 +33,29 @@
/usr/sbin/bootadm set-menu-password [-P pool] [-R altroot]
- [-f <path to file>] | -s] | [-r] | [-l -t [-i entry_number] | -g]
+ [-f <path-to-file>] | -s] | [-r] | [-l -t [-i entry-number] | -g]
/usr/sbin/bootadm list-menu [-P pool] [-R altroot]
- [[-i entry_number] | entry_title]
+ [[-i entry-number] | entry-title]
/usr/sbin/bootadm generate-menu [-P pool] [-f]
- /usr/sbin/bootadm show-entry [-P pool] <entry_name> | -i <index>
+ /usr/sbin/bootadm show-entry [-P pool] <entry-name> | -i <index>
- /usr/sbin/bootadm add-entry [-P pool] [-i entry_number] entry_title
+ /usr/sbin/bootadm add-entry [-P pool] [-i entry-number] entry-title
- /usr/sbin/bootadm change-entry [-P pool] {[entry_title[,entry_title...]
- | -i entry_number[,entry_number]...]} {key=value [key=value ...]
- | set-default }
+ /usr/sbin/bootadm change-entry [-P pool]
+ {[entry-title[,entry-title...] | -i entry-number[,entry-number]...]}
+ {key=value [key=value ...] | set-default}
- /usr/sbin/bootadm remove-entry [-P pool] {[entry_title[,entry_title...]
- | -i entry_number[,entry_number]...]}
+ /usr/sbin/bootadm remove-entry [-P pool]
+ {[entry-title[,entry-title...] | -i entry-number[,entry-number]...]}
DESCRIPTION
The bootadm command manages the boot archive and, with x86 boot envi-
@@ -72,14 +72,13 @@
The set-menu-password subcommand sets the password to protect the GRUB
- menu from being seen. To set, use -f <path to
- file>; if -s is used, will prompt for the password
- twice; -r removes the password; -l lists whether there is a global menu
- password lock, and the menu entry userlist -l -t lists the menu entry
- userlist in parsable output; if -l -t -i <entry number>, list the
- userlist for that list of entry numbers in parsable output; if -l -t
- -g, list whether there is a global menu password lock in parsable out-
- put.
+ menu from being seen. To set, use -f path-to-file; if -s is used, it
+ will prompt for the password twice; -r removes the password; -l lists
+ whether there is a global menu password lock, and the menu entry
+ userlist -l -t lists the menu entry userlist in parsable output; if
+ -l -t -i entry-number, list the userlist for that list of entry num-
+ bers in parsable output; if -l -t -g, list whether there is a global
+ menu password lock in parsable output.
The list-menu subcommand displays the current GRUB menu entries, or,
@@ -95,11 +94,11 @@
When an active boot pool is present, bootable datasets are maintained,
each corresponding to one boot environment and storing that boot envi-
ronment's bootable artifacts (such as the boot_archive (x64 and SPARC
- platforms) and the UNIX kernel executable (x64 platforms only)). The
- boot-pool subcommand allows an administrator to manage aspects of the
- boot pool, including device membership (with the add/remove subcom-
- mands), manual synchronization of boot artifacts (with the resync sub-
- command), and setting boot pool attributes (with the set subcommand).
+ platforms) and the kernel executable (x64 platforms only)). The boot-
+ pool subcommand allows an administrator to manage aspects of the boot
+ pool, including device membership (with the add/remove subcommands),
+ manual synchronization of boot artifacts (with the resync subcommand),
+ and setting boot pool attributes (with the set subcommand).
The generate-menu subcommand provides a way to create a new menu con-
@@ -123,11 +122,11 @@
used to manage diskless clients of a different platform type.
SUBCOMMANDS
- For the subcommands that support specifying entry_title, entry_title is
+ For the subcommands that support specifying entry-title, entry-title is
a string that can be either double- or single-quoted.
- An entry_number is a non-negative integer number representing the index
+ An entry-number is a non-negative integer number representing the index
of the menu entry in the GRUB menu.
@@ -154,7 +153,7 @@
Possible values are:
- default=entry_number
+ default=entry-number
The entry number (for example, 0, 1, or 2) in the GRUB menu
designating the operating system to boot when the timer ex-
@@ -168,7 +167,7 @@
-1, auto boot is disabled.
- console=GRUB_console_type
+ console=GRUB-console-type
Sets the type of console used for GRUB.
@@ -206,18 +205,16 @@
[add|del]-user=<username>
- Adds or deletes the username to the list of authorized user.
- Will prompt for the password twice. Password is stored in
- hashed form. Username does not have to be the same as the So-
- laris username.
+ Adds or deletes the username to the list of authorized users.
+ The bootadm command will prompt for the password twice. The
+ password is stored in hashed form. The username does not have
+ to be the same as the Solaris username.
+
+ [auth-file]=file-path
- [auth-file]=<file path>
-
- Adds username and password in <file
- path> to the
- list of authorized users. <file path> is a file with <user-
- name>=<password> pairs.
+ Adds username and password in file-path to the list of autho-
+ rized users. file-path is a file with username=password pairs.
[add|del]-superuser=<username>
@@ -305,7 +302,7 @@
set-menu-password [-R altroot] [-f <path to file> | -s] [-r]
- [-l -t [-i entry_number[,entry_number]...]|-g]
+ [-l -t [-i entry-number[,entry-number]...]|-g]
Sets and deletes the password to protect the GRUB menu from being
seen. Also, lists whether the entire GRUB menu password is set and
@@ -327,24 +324,24 @@
tries currently installed on the system.
- bootadm show-entry [-P pool] <entry_name> | -i <index>
+ bootadm show-entry [-P pool] <entry-name> | -i <index>
- Show the entry found by name <entry_name> or index from the menu.
- Both entry_name and index may also be a comma-separated list of en-
+ Show the entry found by name entry-name or index from the menu.
+ Both entry-name and index may also be a comma-separated list of en-
tries/indices.
- add-entry [-P pool] [-i entry_number] entry_title
+ add-entry [-P pool] [-i entry-number] entry-title
Create a new entry in the menu with given entry title.
- If entry_number is specified, the new entry will be inserted at the
- given position, or added as the last entry if the given entry_num-
+ If entry-number is specified, the new entry will be inserted at the
+ given position, or added as the last entry if the given entry-num-
ber is more than current number of entries.
change-entry [-P pool]
- {[entry_title[,entry_title...] | -i entry_number[,entry_number]...]}
+ {[entry-title[,entry-title...] | -i entry-number[,entry-number]...]}
{ key=value [ key=value ...] | set-default }
Modify the contents of a given entry or a comma-separated list of
@@ -361,12 +358,12 @@
Possible values are:
- title=entry_title
+ title=entry-title
The new title for the entry (or entries).
- kernel=path_to_kernel
+ kernel=path-to-kernel
Path to the kernel. Example:
@@ -374,15 +371,15 @@
- kargs=kernel_arguments
+ kargs=kernel-arguments
Argument or a list of arguments passed to kernel during boot.
Please refer to kernel(8) for possible options. If there are
- any spaces in the list, value of the key should be enclosed in
- quotes or double quotes.
+ any spaces in the list, the value of the key should be enclosed
+ in quotes or double quotes.
- boot_archive=path_to_boot_archive
+ boot_archive=path-to-boot-archive
The path to the boot archive.
@@ -402,8 +399,8 @@
- remove-entry [-P pool] [{entry_title [,entry_title...] | -i entry_num-
- ber[,entry_number...]}
+ remove-entry [-P pool] [{entry-title [,entry-title...] | -i entry-num-
+ ber[,entry-number...]}
Remove a given entry or a comma-separated list of entries. If there
are multiple entries with the same specified title, all will be re-
@@ -440,11 +436,10 @@
-
boot-pool {
[{add|remove} [-P rpool] <device list>] |
list [-P rpool] |
- resync [-P rpool] [-vA] [<BE_list>] |
+ resync [-P rpool] [-vA] [<BE-list>] |
set [-P rpool] <param>=<value> ... }
The boot-pool subcommand manipulates the active boot pool (if the
@@ -487,7 +481,7 @@
settings.
- resync [-P rpool] [-vA] {<BE_list>}
+ resync [-P rpool] [-vA] {<BE-list>}
Resynchronize the boot pool (rebuilding it, if necessary, using
the set of devices previously configured) and creates bootable
@@ -519,7 +510,7 @@
When eviction_algorithm is set to none and a boot environ-
ment's bootable files need to be copied to the boot pool,
if there is insufficient space on the boot pool, the copy
- operation will fail. NOTE that the boot pool will not be
+ operation will fail. Note that the boot pool will not be
allowed to exceed 85% of its maximum capacity to ensure
maximum system performance.
@@ -527,13 +518,11 @@
datasets that correspond to the least recently-used boot
environments will be evicted until sufficient space exists
for the copy operation to succeed. Note that the noevict BE
- policy (settable on a per-BE basis changes this behavior
- and stops those BEs from being evicted (if enough BEs are
+ policy (settable on a per-BE basis) changes this behavior
+ and stops those BEs from being evicted. If enough BEs are
marked noevict, it's possible for bootable dataset creation
to fail, since the system would not be able to find enough
- free space by evicting datasets.))
-
-
+ free space by evicting datasets.
@@ -556,8 +545,7 @@
behavior.
- -B [x86 systems with legacy BIOS firmware
- only]
+ -B [x86 systems with legacy BIOS firmware only]
In install-bootloader operation on x86 systems with legacy BIOS
firmware, do not install the boot loader into the Master Boot
@@ -644,42 +631,39 @@
# bootadm update-archive -R /a
-
- Example 3 Switching Default Boot Entry
+ Example 3 Listing GRUB Menu Entries
- The following command refers to the menu displayed in the previous ex-
- ample. The user selects Linux (item 2).
-
-
- # bootadm set-menu default=2
+ The following command lists the GRUB menu entries:
+ # bootadm list-menu
+ The location for the active GRUB menu is: /stubboot/boot/grub/menu.lst
+ default 0
+ timeout 10
+ 0 Oracle Solaris 11.4
+ 1 11.4.75.182.2
+ 2 11.4.81.195.2
- or
+ Example 4 Switching Default Boot Entry
- # bootadm change-entry -i 2 set-default
+ The following command refers to the menu displayed in the previous ex-
+ ample. The user selects 11.4.81.195.2 (item 2).
- Example 4 Listing GRUB Menu Entries
+ # bootadm set-menu default=2
- The following command lists the GRUB menu entries:
+ or
- # bootadm list-menu
- The location for the active GRUB menu is: /stubboot/boot/grub/menu.lst
- default 0
- timeout 10
- 0 Solaris10
- 1 Solaris10 failsafe
- 2 Linux
+ # bootadm change-entry -i 2 set-default
Example 5 Showing a Menu Entry
@@ -687,10 +671,10 @@
The following command shows the information of a menu entry with the
- title "Solaris10".
+ title "Oracle Solaris 11.4".
- # bootadm show-entry "Solaris10"
+ # bootadm show-entry "Oracle Solaris 11.4"
@@ -804,4 +784,4 @@
https://www.gnu.org/software/grub/
-Oracle Solaris 11.4 12 July 2024 bootadm(8)
+Oracle Solaris 11.4 23 Jun 2025 bootadm(8)
diff -NurbBw 11.4.81/man8/cfgadm_fp.8 11.4.84/man8/cfgadm_fp.8
--- 11.4.81/man8/cfgadm_fp.8 2025-08-17 09:30:02.987309195 -0700
+++ 11.4.84/man8/cfgadm_fp.8 2025-08-17 09:30:25.272814310 -0700
@@ -62,8 +60,7 @@
A simple listing of attachment points in the system includes attachment
points at fp port nodes but not Fibre Channel devices. The following
- example uses the -a flag to the list option (-l) to list Fibre Channel
- devices:
+ example uses the list option (-l) to list Fibre Channel devices:
# cfgadm -l
Ap_Id Type Receptacle Occupant Condition
@@ -317,8 +314,7 @@
-h ap_id
- Obtain fp--transport-specific help. Specify any fp attachment
- point.
+ Obtain fp-transport-specific help. Specify any fp attachment point.
-o hardware_options
@@ -458,8 +437,8 @@
SEE ALSO
- cfgadm(8), config_admin(3CFGADM), libcfgadm(3LIB), fp(4D), attrib-
- utes(7)
+ config_admin(3CFGADM), libcfgadm(3LIB), fp(4D), attributes(7), cf-
+ gadm(8)
NOTES
For devices with unknown or no SCSI device type (for example, a Fibre
@@ -481,4 +460,4 @@
show_SCSI_LUN option, and the deprecated unusable_FCP_dev option has
been replaced by the new unusable_SCSI_LUN option.
-Oracle Solaris 11.4 19 Jan 2017 cfgadm_fp(8)
+Oracle Solaris 11.4 23 Jun 2025 cfgadm_fp(8)
diff -NurbBw 11.4.81/man8/cfgadm_pci.8 11.4.84/man8/cfgadm_pci.8
--- 11.4.81/man8/cfgadm_pci.8 2025-08-17 09:30:03.027243865 -0700
+++ 11.4.84/man8/cfgadm_pci.8 2025-08-17 09:30:25.316075923 -0700
@@ -29,8 +29,8 @@
through the cfgadm command (see cfgadm(8)). This library does not in-
clude support for PCI Express Hotplug or Standard PCI Hotplug adapter
cards, which are provided by a different library (see cfgadm_shp(8)).
- Hotplug administrative models between PCI, CompactPCI remain the same
- except where noted in this document.
+ Hotplug administrative models between PCI and CompactPCI remain the
+ same except where noted in this document.
For PCI Hot Plug, each hotplug slot on a specific PCI bus is repre-
@@ -70,7 +70,7 @@
connect
- Connect the slot to PCI bus.
+ Connect the slot to the PCI bus.
disconnect
@@ -131,7 +131,7 @@
When the -v option is used with the -l option, the cfgadm command
outputs information about the attachment point. For PCI Hotplug at-
- tachment points located in a PCI PCI Express hierarchy, see cf-
+ tachment points located in a PCI Express hierarchy, see cf-
gadm_shp(8) for details. For PCI Hot Plug attachment points not lo-
cated in a PCI Express hierarchy, the Information field will be the
slot's system label, if any. This string will be obtained from the
@@ -166,7 +166,7 @@
devices, but are implemented as a PCI bridge with arbitrary de-
vices behind them. In those cases, the subclass displayed is
that of the PCI bridge. Most commonly, the bridges are pci-pci,
- a generic PCI to PCI bridge or stpci, a semitransparent PCI
+ a generic PCI to PCI bridge; or stpci, a semitransparent PCI
bridge.
@@ -220,7 +220,7 @@
Specify led_sub_arg as fault, power, attn, or active.
- Specify mode_sub_arg as on, off or blink.
+ Specify mode_sub_arg as on, off, or blink.
Changing the state of the LED does not change the state of the
receptacle or occupant. Normally, the LEDs are controlled by
@@ -350,4 +350,4 @@
config_admin(3CFGADM), libcfgadm(3LIB), attributes(7), cfgadm(8), cf-
gadm_shp(8)
-Oracle Solaris 11.4 11 May 2021 cfgadm_pci(8)
+Oracle Solaris 11.4 23 Jun 2025 cfgadm_pci(8)
diff -NurbBw 11.4.81/man8/cfgadm_scsi.8 11.4.84/man8/cfgadm_scsi.8
--- 11.4.81/man8/cfgadm_scsi.8 2025-08-17 09:30:03.071935927 -0700
+++ 11.4.84/man8/cfgadm_scsi.8 2025-08-17 09:30:25.358708228 -0700
@@ -22,12 +22,11 @@
/usr/sbin/cfgadm [-v] [-o hardware_option] -h [ap_id]...
DESCRIPTION
- The SCSI hardware specific library /usr/lib/cfgadm/scsi.so.1
- provides the functionality for SCSI hot-plugging through the cf-
- gadm(8) command. cfgadm operates on attachment points, which are loca-
- tions in the system where hardware resources can be dynamically recon-
- figured. For information regarding attachment points, see the cfgadm(8)
- man page.
+ The SCSI hardware specific library /usr/lib/cfgadm/scsi.so.1 provides
+ the functionality for SCSI hot-plugging through the cfgadm(8) command.
+ cfgadm operates on attachment points, which are locations in the system
+ where hardware resources can be dynamically reconfigured. For informa-
+ tion regarding attachment points, see the cfgadm(8) man page.
For SCSI hot-plugging, each SCSI controller is represented by an at-
@@ -70,8 +69,8 @@
...where 0,0 uniquely identifies the target and logical unit informa-
tion. The Type field for a path of such ap_ids indicates if it repre-
- sent a path to the scsi_vhci(4D) multipath devices, along with the type
- of device that is connected to through the path.
+ sents a path to the scsi_vhci(4D) multipath devices, along with the
+ type of device that is connected to through the path.
A simple listing of attachment points in the system will include at-
@@ -562,15 +516,13 @@
# cfgadm -c unconfigure c0::2,0
-
-
FILES
/usr/lib/cfgadm/scsi.so.1
hardware-specific library for generic SCSI hot-plugging
- /usr/platform/SUNW,SPARC-Enterprise/lib/cfgadm/scsi.so.1
+ /usr/platform/sun4v/lib/cfgadm/scsi.so.1
platform-specific library for generic SCSI hot-plugging
@@ -615,4 +567,4 @@
damage to the hardware on the SCSI bus. Refer to your hardware manual
for additional information.
-Oracle Solaris 11.4 20 Jan 2017 cfgadm_scsi(8)
+Oracle Solaris 11.4 23 Jun 2025 cfgadm_scsi(8)
diff -NurbBw 11.4.81/man8/consadm.8 11.4.84/man8/consadm.8
--- 11.4.81/man8/consadm.8 2025-08-17 09:30:03.106436480 -0700
+++ 11.4.84/man8/consadm.8 2025-08-17 09:30:25.396667878 -0700
@@ -68,8 +68,8 @@
-p Prints the list of auxiliary consoles that will be auxil-
iary across reboots.
- When invoked with the -a or -d options , tells the appli-
- cation to make the change persist across reboot.
+ When invoked with the -a or -d options, tells the applica-
+ tion to make the change persist across reboot.
EXAMPLES
@@ -160,4 +157,4 @@
requesting restart, can be performed using svcadm(8). The service's
status can be queried using the svcs(1) command.
-Oracle Solaris 11.4 27 Oct 2004 consadm(8)
+Oracle Solaris 11.4 23 Jun 2025 consadm(8)
diff -NurbBw 11.4.81/man8/croinfo.8 11.4.84/man8/croinfo.8
--- 11.4.81/man8/croinfo.8 2025-08-17 09:30:03.156854874 -0700
+++ 11.4.84/man8/croinfo.8 2025-08-17 09:30:25.444299572 -0700
@@ -118,7 +118,7 @@
override the default fields, and output any fields, in the specified
order, in a column-aligned whitespace separated format. In general,
output will be one line of output per matching record with undefined
- (empty) field-name values displayed as a hyphen (--). If, however, a
+ (empty) field-name values displayed as a hyphen (-). If, however, a
displayed record has a multiple string value field, then multiple lines
of output are produced with any secondary non-multiple string values
fields showing a colon (:).
@@ -133,7 +133,7 @@
field, then all the values are concatenated, separated by a semicolon.
Any occurrence of a colon or a semicolon in a value is escaped with a
leading backslash (\). To make scripts more legible, use of the -O
- field-name[,...]' notation is encouraged.
+ field-name[,...] notation is encouraged.
The -o and -O options are mutually exclusive.
@@ -284,7 +284,7 @@
-t occupant-type
A receptacle without an occupant has an undefined (empty) occupant-
- type value, shown as a hyphen (--).
+ type value, shown as a hyphen (-).
Example occupant-type value: disk
@@ -297,7 +297,7 @@
-d occupant-devices
A receptacle without an occupant has an undefined (empty) occupant-
- devices value, shown as a hyphen (--).
+ devices value, shown as a hyphen (-).
Example occupant-devices value:
@@ -308,7 +308,7 @@
-p occupant-paths
A receptacle without an occupant has an undefined (empty) occupant-
- paths value, shown as a hyphen (--).
+ paths value, shown as a hyphen (-).
Example occupant-paths value:
@@ -319,7 +319,7 @@
-c occupant-compdev
A receptacle without an occupant has an undefined (empty) occupant-
- compdev value, shown as a hyphen (--).
+ compdev value, shown as a hyphen (-).
Example occupant-compdev value: c0t5000C500101BA0A3d0
@@ -327,7 +327,7 @@
-i occupant-devid
A receptacle without an occupant has an undefined (empty) occupant-
- devid value, shown as a hyphen (--).
+ devid value, shown as a hyphen (-).
Example occupant-devid value: id1,sd@n5000c500101ba0a3
@@ -335,7 +335,7 @@
-m occupant-mfg
A receptacle without an occupant has an undefined (empty) occupant-
- mfg value, shown as a hyphen (--).
+ mfg value, shown as a hyphen (-).
Example occupant-mfg value: SEAGATE
@@ -343,7 +343,7 @@
-e occupant-model
A receptacle without an occupant has an undefined (empty) occupant-
- model, shown as a hyphen (--).
+ model, shown as a hyphen (-).
Example occupant-model value: ST32000SSSUN2.0T
@@ -351,7 +351,7 @@
-n occupant-part
A receptacle without an occupant has an undefined (empty) occupant-
- part value, shown as a hyphen (--).
+ part value, shown as a hyphen (-).
Example occupant-part value: SEAGATE-ST32000SSSUN2.0T
@@ -359,7 +359,7 @@
-s occupant-serial
A receptacle without an occupant has an undefined (empty) occupant-
- serial value, shown as a hyphen (--).
+ serial value, shown as a hyphen (-).
Example occupant-serial value: 000949L09C8L________9WM09C8L
@@ -367,7 +367,7 @@
-f occupant-firm
A receptacle without an occupant has an undefined (empty) occupant-
- firm value, shown as a hyphen (--).
+ firm value, shown as a hyphen (-).
Example occupant-firm value: 0313
@@ -375,19 +375,19 @@
-1 occupant-misc-1
A receptacle without an occupant has an undefined (empty) occupant-
- misc-1 value, shown as a hyphen (--).
+ misc-1 value, shown as a hyphen (-).
-2 occupant-misc-2
A receptacle without an occupant has an undefined (empty) occupant-
- misc-2 value, shown as a hyphen (--).
+ misc-2 value, shown as a hyphen (-).
-3 occupant-misc-3
A receptacle without an occupant has an undefined (empty) occupant-
- misc-3 value, shown as a hyphen (--).
+ misc-3 value, shown as a hyphen (-).
-?
@@ -400,9 +400,9 @@
Output specified fields, in order, in human-readable format.
- For croinfo and smpinfo, default output is in -o Dtc format. For
- diskinfo, and sesinfo, the default output is in -O Dc format. For
- hbainfo the default output is in -O Dc2 format.
+ For croinfo and smpinfo, the default output is in -o Dtc format.
+ For diskinfo and sesinfo, the default output is in -O Dc format.
+ For hbainfo, the default output is in -O Dc2 format.
-O fields
@@ -652,12 +638,13 @@
- The interface stability of croinfo, diskinfo, sesinfo, smpinfo and
+ The interface stability of croinfo, diskinfo, sesinfo, smpinfo, and
hbainfo is Committed. The interface stability of command output is Not-
an-Interface.
SEE ALSO
- devchassis(4FS), attributes(7), devchassisd(8), fmd(8)
+ regex(3C), devchassis(4FS), attributes(7), devchassisd(8), fmadm(8)
+ fmd(8)
The SCSI Storage Interfaces committee website, https://www.t10.org
@@ -680,4 +667,4 @@
do not meet this criterion will not be fully enumerated, and thus will
not be properly represented.
-Oracle Solaris 11.4 19 Aug 2019 croinfo(8)
+Oracle Solaris 11.4 23 Jun 2025 croinfo(8)
diff -NurbBw 11.4.81/man8/cron.8 11.4.84/man8/cron.8
--- 11.4.81/man8/cron.8 2025-08-17 09:30:03.196939087 -0700
+++ 11.4.84/man8/cron.8 2025-08-17 09:30:25.481390918 -0700
@@ -37,15 +37,15 @@
mitted.
- cron and at jobs are not executed if your account is locked or expired.
- Consult shadow(5) to determine which accounts are not locked and not
- expired.
+ cron and at jobs are not executed for accounts that are locked or ex-
+ pired. Consult shadow(5) to determine which accounts are not locked and
+ not expired.
Setting cron Jobs Across Time Zones
The time zone of the cron daemon sets the system-wide time zone for
- cron entries. This, in turn, is by set by default system-wide using
- /etc/default/init. The time zone for cron entries can be overridden in
- a user's crontab file; see crontab(1).
+ cron entries. This, in turn, is set by default system-wide as described
+ under TZ in environ(7). The time zone for cron entries can be overrid-
+ den in a user's crontab file; see crontab(1).
If some form of daylight savings or summer/winter time is in effect,
@@ -67,15 +67,14 @@
Example /etc/default/cron file:
-
-
CRONLOG=YES
PATH=/usr/bin
This example enables logging and sets the default PATH used by non-root
- jobs to /usr/bin. Root jobs continue to use /usr/bin.
+ jobs to /usr/bin. Root jobs continue to use the default superuser path
+ of /usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(8).
@@ -114,13 +113,14 @@
SEE ALSO
- at(1), crontab(1), sh(1), svcs(1), queuedefs(5), shadow(5), attrib-
- utes(7), rbac(7), smf(7), smf_security(7), logadm(8), svcadm(8)
+ at(1), crontab(1), sh(1), svcs(1), queuedefs(5), shadow(5),
+ attributes(7), environ(7), rbac(7), smf(7), smf_security(7), logadm(8),
+ svcadm(8), svc.periodicd(8)
NOTES
A cron job is executed in a separate invocation of the shell, running
in a separate process group with no controlling terminal. Open file de-
- scriptors, traps and priority inherited from the invoking environment
+ scriptors, traps, and priority inherited from the invoking environment
are lost.
@@ -135,10 +135,15 @@
requesting restart, can be performed using svcadm(8). The service's
status can be queried using the svcs(1) command. Most administrative
actions may be delegated to users with the solaris.smf.manage.cron au-
- thorization (see rbac(7) and smf_security(7)).
+ thorization. See rbac(7) and smf_security(7).
+
+
+ Additional flexibility in running scheduled or periodic tasks is avail-
+ able via the Service Management Facility periodic restarter. See
+ svc.periodicd(8).
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and
possibly in /var/cron/olog.
-Oracle Solaris 11.4 11 May 2021 cron(8)
+Oracle Solaris 11.4 23 Jun 2025 cron(8)
diff -NurbBw 11.4.81/man8/devprop.8 11.4.84/man8/devprop.8
--- 11.4.81/man8/devprop.8 2025-08-17 09:30:03.237137988 -0700
+++ 11.4.84/man8/devprop.8 2025-08-17 09:30:25.524230209 -0700
@@ -4,16 +4,20 @@
devprop - display device property-value or device-path information
SYNOPSIS
- /usr/sbin/devprop [-n device-path] [-v] [-{e|b|i|l|s}] [-q]
+ /usr/sbin/devprop [-n device-path] [-v] [-e|-b|-i|-l|-s] [-q]
[-c separator] property-name ...
- /usr/sbin/devprop -a [-v] [-{e|b|i|l|s}] [-q]
+ /usr/sbin/devprop -a [-v] [-e|-b|-i|-l|-s] [-q]
[-c separator] property-name ...
DESCRIPTION
- Use of '-n device-path' and '-a' are exclusive. If neither are speci-
- fied then '-n /' is assumed.
+ The devprop command displays device property-value or device-path in-
+ formation.
+
+
+ Use of '-n device-path' and '-a' are mutually exclusive. If neither are
+ specified then '-n /' is assumed.
If no property-name is specified, the devprop -n device-path command
@@ -67,9 +71,9 @@
-v
- Specifies verbose mode for -noption. The "property-name=" is dis-
- played before each property-value for the -a option. The "property-
- name=property-value" is displayed after the device-path.
+ Specifies verbose mode for the -n option. The "property-name=" is
+ displayed before each property-value for the -a option. The "prop-
+ erty-name=property-value" is displayed after the device-path.
@@ -98,15 +101,13 @@
-
The following options related to property-value display.
-
-c separator Specifies the separator between array property-value
elements. Use double quotation marks (" ") to specify a
space. The default separator is the plus sign (+) for
- the string type, and period (.) for others, such as
- prtconf(8).
+ the string type, and period (.) for others, as in prt-
+ conf(8).
-q Specifies quoted display mode in which string proper-
@@ -124,14 +124,10 @@
EXIT STATUS
- 0
-
- No error occurred.
-
+ 0 No error occurred.
- non-zero
- An error occurred.
+ non-zero An error occurred.
EXAMPLES
@@ -162,14 +155,12 @@
device-nblocks=585937500
-
Example 3 Listing paths for all devices with defined properties.
- The following example lists the path of each device that defines one
- or more of the specified properties.
-
+ The following example lists the path of each device that defines one or
+ more of the specified properties.
# devprop -a device-nblocks devid inquiry-serial-no
@@ -230,4 +218,4 @@
SEE ALSO
libdevinfo(3LIB), attributes(7), prtconf(8)
-Oracle Solaris 11.4 15 May 2019 devprop(8)
+Oracle Solaris 11.4 23 Jun 2025 devprop(8)
diff -NurbBw 11.4.81/man8/df_ufs.8 11.4.84/man8/df_ufs.8
--- 11.4.81/man8/df_ufs.8 2025-08-17 09:30:03.273132223 -0700
+++ 11.4.84/man8/df_ufs.8 2025-08-17 09:30:25.558089278 -0700
@@ -4,35 +4,44 @@
df_ufs - report free disk space on ufs file systems
SYNOPSIS
- df -F ufs [generic_options] [-o i] [directory | special]
+ df -F ufs [generic_options] [-o i] [directory | special]...
DESCRIPTION
- df displays the amount of disk space occupied by ufs file systems, the
- amount of used and available space, and how much of the file system's
- total capacity has been used. The amount of space reported as used and
- available is less than the amount of space in the file system; this is
- because the system reserves a fraction of the space in the file system
- to allow its file system allocation routines to work well. The amount
- reserved is typically about 10%; this can be adjusted using tunefs(8).
- When all the space on the file system except for this reserve is in
- use, only the superuser can allocate new files and data blocks to ex-
- isting files. When the file system is overallocated in this way, df
- might report that the file system is more than 100% utilized. If nei-
- ther directory nor special is specified, df displays information for
- all mounted ufs file systems.
+ The df command displays the amount of disk space occupied by ufs(4FS)
+ file systems, the amount of used and available space, and how much of
+ the file system's total capacity has been used. The amount of space re-
+ ported as used and available is less than the amount of space in the
+ file system; this is because the system reserves a fraction of the
+ space in the file system to allow its file system allocation routines
+ to work well. The amount reserved is typically about 10%; this can be
+ adjusted using tunefs(8). When all the space on the file system except
+ for this reserve is in use, only the superuser can allocate new files
+ and data blocks to existing files. When the file system is overallo-
+ cated in this way, df might report that the file system is more than
+ 100% utilized.
+
+
+ If directory operands are specified, df displays information for the
+ filesystem containing each listed path. If special operands are speci-
+ fied, df displays information for the filesystem stored on each speci-
+ fied device, if any. If neither directory nor special operands are
+ specified, df displays information for all mounted file systems.
OPTIONS
The following options are supported:
- generic_options Options supported by the generic df command. See
- df(8) for a description of these options.
+ generic_options
+ Options supported by the generic df command. See df(8) for a de-
+ scription of these options.
- -o Specify ufs file system specific options. The avail-
- able option is:
- i Report the number of used and free inodes. This
- option can not be used with generic_options.
+ -o
+
+ Specify ufs file system specific options. The available option is:
+
+ i Report the number of used and free inodes. This option can not
+ be used with generic_options.
@@ -46,14 +55,12 @@
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
- | Availability |system/file-system/ufs, |
- | |system/xopen/xcu4 |
+ | Availability |system/file-system/ufs |
+------------------------------+-----------------------------+
SEE ALSO
- ufs(4FS), mnttab(5), attributes(7), df(8), fsck(8), fstyp(8),
- tunefs(8),
+ ufs(4FS), mnttab(5), attributes(7), df(8), fsck(8), fstyp(8), tunefs(8)
NOTES
df calculates its results differently for mounted and unmounted file
@@ -77,4 +84,4 @@
other items, the number of fragments and the degree of fragmentation.
See fsck(8).
-Oracle Solaris 11.4 27 Nov 2017 df_ufs(8)
+Oracle Solaris 11.4 23 Jun 2025 df_ufs(8)
diff -NurbBw 11.4.81/man8/disks.8 11.4.84/man8/disks.8
--- 11.4.81/man8/disks.8 2025-08-17 09:30:03.314886975 -0700
+++ 11.4.84/man8/disks.8 2025-08-17 09:30:25.595954736 -0700
@@ -7,8 +7,8 @@
/usr/sbin/disks [-C] [-r rootdir]
DESCRIPTION
- devfsadm(8) is now the preferred command for /dev and should be used
- instead of disks.
+ devfsadm(8) is now the preferred command for maintaining /dev and
+ should be used instead of disks.
disks creates symbolic links in the /dev/dsk and /dev/rdsk directories
@@ -29,11 +29,10 @@
controller. The first controller found on the first occasion
this program is run on a system, is assigned number 0. tN is
the bus-address number of a subsidiary controller attached
- to a peripheral bus such as SCSI or IPI (the target number
- for SCSI, and the facility number for IPI controllers). dN
- is the number of the disk attached to the controller. sN is
- the slice number on the disk. pN is the FDISK partition num-
- ber used by fdisk(8). (x86 Only)
+ to a peripheral bus such as SCSI (the target number for
+ SCSI). dN is the number of the disk attached to the con-
+ troller. sN is the slice number on the disk. On x86 systems,
+ pN is the FDISK partition number used by fdisk(8).
3. If only some of the disk entries are found in /dev/dsk for a
@@ -59,8 +58,8 @@
Notice to Driver Writers
disks considers all devices with a node type of DDI_NT_BLOCK,
- DDI_NT_BLOCK_CHAN, DDI_NT_CD, DDI_NT_BLOCK_WWN or DDI_NT_CD_CHAN to
- be disk devices. disks requires the minor name of disk devices obey the
+ DDI_NT_BLOCK_CHAN, DDI_NT_CD, DDI_NT_BLOCK_WWN, or DDI_NT_CD_CHAN to be
+ disk devices. disks requires the minor name of disk devices obey the
following format conventions.
@@ -109,7 +108,7 @@
been removed, powered off, or are otherwise inaccessible.
- -r rootdir Causes disks to presume that the /dev/dsk, /dev/rdsk and
+ -r rootdir Causes disks to presume that the /dev/dsk, /dev/rdsk, and
/devices directory trees are found under rootdir, not di-
rectly under /.
@@ -153,14 +151,14 @@
/*
* create block device interface
*/
- sprintf(name, "%c", slice + 'a');
+ snprintf(name, sizeof(name), "%c", slice + 'a');
ddi_create_minor_node(dip, name, S_IFBLK,
MINOR_NUM(instance, slice), DDI_NT_BLOCK_CHAN, 0);
/*
* create the raw (character) device interface
*/
- sprintf(name,"%c,raw", slice + 'a');
+ snprintf(name, sizeof(name), "%c,raw", slice + 'a');
ddi_create_minor_node(dip, name, S_IFCHR,
MINOR_NUM(instance, slice), DDI_NT_BLOCK_CHAN, 0);
}
@@ -169,12 +167,10 @@
-
-
Installing the xkdisk disk driver on a Sun Fire 4800, with the driver
- controlling a SCSI disk (target 3 attached to an isp(4D) SCSI HBA)
- and performing a reconfiguration-boot (causing disks to be run) creates
- the following special files in /devices.
+ controlling a SCSI disk (target 3 attached to an isp(4D) SCSI HBA) and
+ performing a reconfiguration-boot (causing disks to be run) creates the
+ following special files in /devices.
# ls -l /devices/ssm@0,0/pci@18,700000/pci@1/SUNW,isptwo@4/
@@ -264,4 +253,4 @@
BUGS
disks silently ignores malformed minor device names.
-Oracle Solaris 11.4 11 Aug 2014 disks(8)
+Oracle Solaris 11.4 23 Jun 2025 disks(8)
diff -NurbBw 11.4.81/man8/dtrace.8 11.4.84/man8/dtrace.8
--- 11.4.81/man8/dtrace.8 2025-08-17 09:30:03.360935753 -0700
+++ 11.4.84/man8/dtrace.8 2025-08-17 09:30:25.640153624 -0700
@@ -15,11 +15,11 @@
[-i probe-id [[predicate] action]]
DESCRIPTION
- DTrace is a comprehensive dynamic tracing framework for the Solaris Op-
- erating System. DTrace provides a powerful infrastructure that permits
- administrators, developers, and service personnel to concisely answer
- arbitrary questions about the behavior of the operating system and user
- programs.
+ DTrace is a comprehensive dynamic tracing framework for the Oracle So-
+ laris Operating System. DTrace provides a powerful infrastructure that
+ permits administrators, developers, and service personnel to concisely
+ answer arbitrary questions about the behavior of the operating system
+ and user programs.
The Oracle Solaris 11.4 DTrace (Dynamic Tracing) Guide describes how to
@@ -434,7 +434,7 @@
compiled)
- o __`uname -s`_`uname -r` (for example, __SunOS_5_10)
+ o __`uname -s`_`uname -r` (for example, __SunOS_5_11)
o __SUNW_D=1
@@ -505,8 +505,8 @@
committed.
SEE ALSO
- cpp(1), isainfo(1), ssh(1), libdtrace(3LIB), dtrace(4D), dri-
- ver.conf(5), attributes(7)
+ cpp(1), isainfo(1), ssh(1), Intro(2D), libdtrace(3LIB), dtrace(4D),
+ driver.conf(5), attributes(7)
Oracle Solaris 11.4 DTrace (Dynamic Tracing) Guide
@@ -516,9 +516,9 @@
inspecting them and reporting results. A process can do nothing while
it is stopped. This means that, if , for example, the X server is in-
spected by dtrace running in a window under the X server's control, the
- whole window system can become deadlocked, because the proc tool would
- be attempting to display its results to a window that cannot be re-
- freshed. In such a case, logging in from another system using ssh(1)
- and killing the offending proc tool clears the deadlock.
+ whole window system can become deadlocked, because the dtrace command
+ would be attempting to display its results to a window that cannot be
+ refreshed. In such a case, logging in from another system using ssh(1)
+ and killing the offending dtrace command clears the deadlock.
-Oracle Solaris 11.4 29 Mar 2023 dtrace(8)
+Oracle Solaris 11.4 23 Jun 2025 dtrace(8)
diff -NurbBw 11.4.81/man8/edquota.8 11.4.84/man8/edquota.8
--- 11.4.81/man8/edquota.8 2025-08-17 09:30:03.394297014 -0700
+++ 11.4.84/man8/edquota.8 2025-08-17 09:30:25.675261605 -0700
@@ -10,13 +10,14 @@
edquota -t
DESCRIPTION
- edquota is a quota editor. One or more users may be specified on the
- command line. For each user a temporary file is created with an ASCII
- representation of the current disk quotas for that user for each
- mounted ufs file system that has a quotas file, and an editor is then
- invoked on the file. The quotas may then be modified, new quotas added,
- etc. Upon leaving the editor, edquota reads the temporary file and mod-
- ifies the binary quota files to reflect the changes made.
+ edquota is a quota editor for ufs(4FS) filesystems. One or more users
+ may be specified on the command line. For each user a temporary file is
+ created with an ASCII representation of the current disk quotas for
+ that user for each mounted ufs file system that has a quotas file, and
+ an editor is then invoked on the file. The quotas may then be modified,
+ new quotas added, etc. Upon leaving the editor, edquota reads the tem-
+ porary file and modifies the binary quota files to reflect the changes
+ made.
The editor invoked is vi(1) unless the EDITOR environment variable
@@ -38,9 +39,8 @@
or more lines of the format, where a block is considered to be a 1024
byte (1K) block:
- fsmount_point blocks (soft =number, \
- hard =number ) inodes (soft =number, \
- hard =number)
+ fs mount_point blocks (soft = number, hard = number) \
+ inodes (soft = number, hard = number)
@@ -96,4 +96,7 @@
NOTES
All UIDs can be assigned quotas.
-Oracle Solaris 11.4 4 Feb 2015 edquota(8)
+
+ See zfs(8) to set quotas on ZFS filesystems.
+
+Oracle Solaris 11.4 23 Jun 2025 edquota(8)
diff -NurbBw 11.4.81/man8/eeprom.8 11.4.84/man8/eeprom.8
--- 11.4.81/man8/eeprom.8 2025-08-17 09:30:03.445315651 -0700
+++ 11.4.84/man8/eeprom.8 2025-08-17 09:30:25.739672901 -0700
@@ -37,7 +37,7 @@
SPARC
SPARC based systems implement firmware password protection with eeprom,
- using the security-mode, security-password and security-#badlogins
+ using the security-mode, security-password, and security-#badlogins
properties.
x86
@@ -49,7 +49,7 @@
Because x86 based systems typically implement password protection in
the system BIOS, there is no support for password protection in the
eeprom program. While it is possible to set the security-mode, secu-
- rity-password and security-#badlogins properties on x86 based systems,
+ rity-password, and security-#badlogins properties on x86 based systems,
these properties have no special meaning or behavior on x86 based sys-
tems.
@@ -109,9 +109,9 @@
tion. The acceptable values for this variable depend on the release
of the Solaris operating system you are using.
- For all releases of Solaris 10 and Solaris 11, a value of of 0x0
- means that there will be an attempt to use ACPI if it is available
- on the system. A value of 0x2 disables the use of ACPI.
+ For all releases of Solaris 10 and Solaris 11, a value of 0x0 means
+ that there will be an attempt to use ACPI if it is available on the
+ system. A value of 0x2 disables the use of ACPI.
For the Solaris 10 1/06 release, a value of 0x8 means that there
will be an attempt to use ACPI in a mode compatible with previous
@@ -131,7 +131,7 @@
console
Specifies the console device. Possible values are ttya, ttyb, text,
- graphics and force-text. In text mode, console output goes to the
+ graphics, and force-text. In text mode, console output goes to the
frame buffer and input comes from the keyboard. A variant of text
mode, graphics displays an image with an animation until either a
key is pressed or console interaction is required by console login,
@@ -278,7 +278,7 @@
boot-device-index
- Keeps track onf the device index into the boot-device variable.
+ Keeps track of the device index into the boot-device variable.
boot-file
@@ -513,9 +513,8 @@
separated by semicolons (;). Multiple root descriptors are sepa-
rated by double-semicolons (;;).
- For example (a single root descriptor (reassembled, it forms a sin-
- gle, uninterrupted line of text)):
-
+ For example, a single root descriptor (reassembled, it forms a sin-
+ gle, uninterrupted line of text):
osroot-type=ZFS/iSCSI/IPv4/IPoIB;osroot-iscsi-port=3260;\
@@ -526,9 +525,8 @@
141.141.1.1;osroot-path=/pci@301/pci@1/pciex15b3,1003@0:\
port=1,pkey=FFFF,protocol=ip
- Another example (multiple root descriptors (reassembled, it forms a
- single, uninterrupted line of text)):
-
+ Another example, with multiple root descriptors (reassembled, it
+ forms a single, uninterrupted line of text):
osroot-type=ZFS/iSCSI/IPv4/IPoIB;osroot-iscsi-port=3260;\
osroot-iscsi-target-ip=141.141.1.2;osroot-iscsi-partition=a;\
@@ -819,15 +815,13 @@
# eeprom boot-command="boot -k"
- Example 5 Read all UEFI Variables on an UEFI Capable X86 System While
+ Example 5 Read all UEFI Variables on an UEFI Capable x86 System While
in UEFI Mode
The following command shows how to read all UEFI variables on an UEFI
- capable X86 system while in UEFI mode:
-
-
+ capable x86 system while in UEFI mode:
example# eeprom -u
@@ -953,6 +943,6 @@
Oracle OpenBoot 4.x Administration Guide
x86 Only
- biosconfig(8), ubiosconfig(8)
+ grub(7), biosconfig(8), ubiosconfig(8)
-Oracle Solaris 11.4 3 Nov 2021 eeprom(8)
+Oracle Solaris 11.4 23 Jun 2025 eeprom(8)
diff -NurbBw 11.4.81/man8/ff.8 11.4.84/man8/ff.8
--- 11.4.81/man8/ff.8 2025-08-17 09:30:03.480126827 -0700
+++ 11.4.84/man8/ff.8 2025-08-17 09:30:25.784161812 -0700
@@ -7,11 +7,11 @@
ff [-F FSType] [-V] [generic_options] [-o specific_options] special...
DESCRIPTION
- ff prints the pathnames and inode numbers of files in the file system
- which resides on the special device special. Other information about
- the files may be printed using options described below. Selection cri-
- teria may be used to instruct ff to only print information for certain
- files. If no selection criteria are specified, information for all
+ ff prints the pathnames and inode numbers of files in the ufs(4FS) file
+ system which resides on the special device special. Other information
+ about the files may be printed using options described below. Selection
+ criteria may be used to instruct ff to only print information for cer-
+ tain files. If no selection criteria are specified, information for all
files considered will be printed (the default); the -i option may be
used to limit files to those whose inodes are specified.
@@ -19,12 +19,11 @@
Output is sorted in ascending inode number order. The default line pro-
duced by ff is:
-
path-name i-number
- The maximum information the command will provide is:
+ The maximum information the command will provide is:
path-name i-number size uid
@@ -96,7 +96,8 @@
Specify FSType-specific options in a comma separated (without
spaces) list of suboptions and keyword-attribute pairs for inter-
- pretation by the FSType-specific module of the command.
+ pretation by the FSType-specific module of the command. See
+ ff_ufs(8).
OPERANDS
@@ -109,8 +110,8 @@
default local file system type. Default values can be set for the
following flags in /etc/default/fs. For example: LOCAL=ufs
- LOCAL The default partition for a command if no FSType is speci-
- fied.
+ LOCAL The default FSType for a command if no FSType is specified
+ or found in /etc/vfstab.
@@ -130,16 +131,16 @@
SEE ALSO
- find(1), stat(2), vfstab(5), attributes(7), ncheck(8)
+ find(1), stat(2), ufs(4FS), vfstab(5), attributes(7), ncheck(8)
- Manual pages for the FSType-specific modules of ff.
+ Manual pages for the FSType-specific modules of ff: ff_ufs(8)
NOTES
- This command may not be supported for all FSTypes.
+ This command may not be supported for FSTypes other than ufs(4FS).
The -a, -m, and -c flags examine the st_atime, st_mtime, and st_ctime
fields of the stat structure respectively. (See stat(2).)
-Oracle Solaris 11.4 4 Feb 2015 ff(8)
+Oracle Solaris 11.4 23 Jun 2025 ff(8)
diff -NurbBw 11.4.81/man8/fmthard.8 11.4.84/man8/fmthard.8
--- 11.4.81/man8/fmthard.8 2025-08-17 09:30:03.518359353 -0700
+++ 11.4.84/man8/fmthard.8 2025-08-17 09:30:25.827734447 -0700
@@ -5,11 +5,11 @@
SYNOPSIS
SPARC
- fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c?
+ fmthard -d data | -n volume_name | -s datafile [-f] [-i] /dev/rdsk/c?
[t?] d?s2
x86
- fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c?
+ fmthard -d data | -n volume_name | -s datafile [-f] [-i] /dev/rdsk/c?
[t?] d?s2
DESCRIPTION
@@ -43,6 +43,12 @@
these fields.
+ -f
+
+ Force the writing of the label even if the disk contains an un-
+ mounted file system or exported zfs(4fs) pool.
+
+
-i
This option allows the command to create the desired VTOC table,
@@ -129,8 +135,15 @@
+------------------------------+-----------------------------+
+ENVIRONMENT VARIABLES
+ NOINUSE_CHECK When set, all non-mandatory checks are disabled. With
+ this set, fmthard silently writes labels even when it
+ will result in the loss of data and or the system
+ crashing.
+
+
SEE ALSO
- uname(1), attributes(7), format(8), prtvtoc(8)
+ uname(1), zfs(4fs), attributes(7), format(8), prtvtoc(8)
x86 Only
fdisk(8)
@@ -144,4 +157,4 @@
For disks under two terabytes, fmthard cannot write a VTOC on an unla-
beled disk. Use format(8) for this purpose.
-Oracle Solaris 11.4 14 Mar 2016 fmthard(8)
+Oracle Solaris 11.4 27 May 2025 fmthard(8)
diff -NurbBw 11.4.81/man8/format.8 11.4.84/man8/format.8
--- 11.4.81/man8/format.8 2025-08-17 09:30:03.559189048 -0700
+++ 11.4.84/man8/format.8 2025-08-17 09:30:25.873949707 -0700
@@ -4,20 +4,17 @@
format - disk partitioning and maintenance utility
SYNOPSIS
- format [-f command-file] [-l log-file] [-d disk-name]
- [-s] [-m] [-M] [-e] [disk-list]
+ format [-emMqrs] [-f command-file | -n] [-l log-file] [-d disk-name]
+ [disk-list]
format -L label-type -d disk-name
DESCRIPTION
format enables you to format, label, repair, and analyze disks on your
- system. Unlike previous disk maintenance programs, format runs under
- Oracle Solaris. Because there are limitations to what can be done to
- the system disk while the system is running, format is also supported
- within the memory-resident system environment. For most applications,
- however, running format under Oracle Solaris is the more convenient ap-
- proach.
+ system. There are limitations to what can be done to the system disk
+ while the system is running, in which case format may be run while
+ booted off of an alternate device, such as install media.
disk-list is a list of disks in the form c?t?d?, /dev/rdsk/c?t?d?s?, or
@@ -116,6 +111,23 @@
ting.
+ -n
+
+ Prints information about disks and exit. The disks are not modi-
+ fied. The -n option is not allowed with -f and -L.
+
+
+ -q
+
+ Show less verbose initial disk list.
+
+
+ -r
+
+ Reload disk information directly from drives on startup, instead of
+ using cached values. This may be time consuming.
+
+
-s
Silent. Suppress all of the standard output. Error messages are
@@ -147,7 +159,12 @@
Run read, write, compare tests, and data purge. The data purge
function implements the National Computer Security Center Guide to
Understanding Data Remnance (NCSC-TG-025 version 2) Overwriting Al-
- gorithm. See NOTES.
+ gorithm. See NOTES. Note that the purge function attempts to over-
+ write data may not work as expected when not operating directly on
+ physical media (such as when accessing an iSCSI LUN) or on some
+ forms of physical media which have their own mapping layer between
+ the OS and the raw blocks on disk (such as hardware level bad block
+ handling).
backup
@@ -325,4 +342,18 @@
Security Manual) Eraser Procedures specification. The NIST Guidelines
for Media Sanitization (NIST SP 800-88) also reference this algorithm.
-Oracle Solaris 11.4 31 Jan 2018 format(8)
+HISTORY
+ The options -n, -q, and -r were added in Oracle Solaris 11.4.84.
+
+
+ Prior to Oracle Solaris 11.4, each disk was opened and its label was
+ re-read on format start-up. For performance reasons, starting with Ora-
+ cle Solaris 11.4, the label information displayed in the initial disk
+ list is read from OS cached data. The label is re-read when a particu-
+ lar disk is selected.
+
+
+ Use the option -r to force re-reading label information from every disk
+ on format start-up.
+
+Oracle Solaris 11.4 23 Jun 2025 format(8)
diff -NurbBw 11.4.81/man8/fsck.8 11.4.84/man8/fsck.8
--- 11.4.81/man8/fsck.8 2025-08-17 09:30:03.596712242 -0700
+++ 11.4.84/man8/fsck.8 2025-08-17 09:30:25.916231597 -0700
@@ -7,7 +7,7 @@
fsck [-F FSType] [-m] [-V] [-v] [special]...
- fsck [-F FSType] [-n | N | y | Y] [-V] [-v]
+ fsck [-F FSType] [-n | -N | -y | -Y] [-V] [-v]
[-o FSType-specific-options] [special]...
DESCRIPTION
@@ -85,7 +85,7 @@
specific fsck implementations.
- -y | Y
+ -y | -Y
Assume a yes response to all questions asked by fsck.
@@ -118,8 +118,8 @@
being converted at once. The format of a file system can be de-
termined from the first line of output from fstyp(8). Note: the
c option is seldom used and is included only for compatibility
- with pre-4.1 releases. There is no guarantee that this option
- will be included in future releases.
+ with pre-SunOS-4.1 releases. There is no guarantee that this
+ option will be included in future releases.
f
@@ -237,7 +237,8 @@
tem modifies the file system.
NOTES
- This command may not be supported for all FSTypes.
+ This command may not be supported for all FSTypes. Most notably, fsck
+ does not support zfs(4FS), nor does zfs require such a utility.
Starting with Solaris 9, fsck manages extended attribute data on the
@@ -252,4 +253,4 @@
aware fsck to stabilize the file system before using it in an at-
tribute-aware environment.
-Oracle Solaris 11.4 4 Feb 2015 fsck(8)
+Oracle Solaris 11.4 23 Jun 2025 fsck(8)
diff -NurbBw 11.4.81/man8/fsdb_udfs.8 11.4.84/man8/fsdb_udfs.8
--- 11.4.81/man8/fsdb_udfs.8 2025-08-17 09:30:03.640216432 -0700
+++ 11.4.84/man8/fsdb_udfs.8 2025-08-17 09:30:25.967120927 -0700
@@ -32,11 +32,13 @@
of fsdb through familiarity.
OPTIONS
- The following options are supported:
+ The following option is supported:
- -o specific_option Specify udfs file system specific options in a
- comma-separated list with no intervening spaces.
- The following specific options are supported:
+ -o specific_option
+
+ Specify udfs file system specific options in a comma-separated list
+ with no intervening spaces. The following specific options are sup-
+ ported:
o Override some error conditions.
@@ -57,9 +59,9 @@
or sets the input and output base. Once set, all input defaults to this
base and all output displays in this base. The base can be overridden
temporarily for input by preceding hexadecimal numbers by 0x, preceding
- decimal numbers with a 0t, or octal numbers with a 0. Hexadecimal num-
- bers beginning with a-f or A -F must be preceded with a 0x to distin-
- guish them from commands.
+ decimal numbers with a 0t, or preceding octal numbers with a 0. Hexa-
+ decimal numbers beginning with a-f or A-F must be preceded with a 0x to
+ distinguish them from commands.
Disk addressing by fsdb is at the byte level. However, fsdb offers many
@@ -93,7 +95,7 @@
- first sets the value of dot (.) to 2, colon (:), signifies the start of
+ first sets the value of dot (.) to 2, colon (:) signifies the start of
a command, and the inode command sets inode to 2. A count is specified
after a comma (,). Once set, count remains at this value until a new
command is encountered that resets the value back to 1 (the default).
@@ -149,10 +150,10 @@
# Update the value of dot by specifying a numeric expres-
sion. Specify numeric expressions using addition, subtrac-
- tion, multiplication, and division operators ( +, -, *,
- and %). Numeric expressions are evaluated from left to
- right and can use parentheses. After evaluation, the value
- of dot is updated.
+ tion, multiplication, and division operators (+, -, *, and
+ %). Numeric expressions are evaluated from left to right
+ and can use parentheses. After evaluation, the value of
+ dot is updated.
, count Update the count indicator. The global value of count is
@@ -174,7 +175,7 @@
+e Increment the value of dot by the expression e. The amount
actually incremented is dependent on the size of type: dot
- = dot + e * sizeof (type) The default for e is 1.
+ = dot + e * sizeof (type). The default for e is 1.
-e Decrement the value of dot by the expression e. See +.
@@ -228,8 +229,8 @@
To view a potentially unmounted disk in a reasonable manner, fsdb sup-
ports the cd, pwd, ls, and find commands. The functionality of each of
- these commands basically matches that of its UNIX counterpart. See
- cd(1), pwd(1), ls(1), and find(1) for details. The *, ,, ?, and - wild-
+ these commands basically matches that of its shell counterpart. See
+ cd(1), pwd(1), ls(1), and find(1) for details. The *, ?, and [-] wild-
card characters are also supported.
@@ -388,11 +389,10 @@
> 7:dir:nm="foo"
-
gets the 7th directory entry of the current inode and changes
its name to foo. Directory names cannot be made larger than the
field allows. If an attempt is made to make a directory name
- larger than the field allows,, the string is truncated to fit
+ larger than the field allows, the string is truncated to fit
and a warning message is displayed.
@@ -458,8 +458,8 @@
- The following command displays the i-number 386 in inode format.386 be-
- comes the current inode.
+ The following command displays the i-number 386 in inode format. 386
+ becomes the current inode.
> 386:ino?i
@@ -606,4 +606,4 @@
SEE ALSO
dir(5), attributes(7), clri(8), fsck_udfs(8)
-Oracle Solaris 11.4 14 May 2018 fsdb_udfs(8)
+Oracle Solaris 11.4 23 Jun 2025 fsdb_udfs(8)
diff -NurbBw 11.4.81/man8/fsdb_ufs.8 11.4.84/man8/fsdb_ufs.8
--- 11.4.81/man8/fsdb_ufs.8 2025-08-17 09:30:03.687220158 -0700
+++ 11.4.84/man8/fsdb_ufs.8 2025-08-17 09:30:26.017284652 -0700
@@ -8,11 +8,11 @@
DESCRIPTION
The fsdb_ufs command is an interactive tool that can be used to patch
- up a damaged UFS file system. It has conversions to translate block and
- i-numbers into their corresponding disk addresses. Also included are
- mnemonic offsets to access different parts of an inode. These greatly
- simplify the process of correcting control block entries or descending
- the file system tree.
+ up a damaged ufs(4FS) file system. It has conversions to translate
+ block and i-numbers into their corresponding disk addresses. Also in-
+ cluded are mnemonic offsets to access different parts of an inode.
+ These greatly simplify the process of correcting control block entries
+ or descending the file system tree.
fsdb contains several error-checking routines to verify inode and block
@@ -34,9 +34,11 @@
OPTIONS
The following option is supported:
- -o Specify UFS file system specific options. These options can be
- any combination of the following separated by commas (with no in-
- tervening spaces). The options available are:
+ -o specific_option
+
+ Specify UFS file system specific options. These options can be any
+ combination of the following separated by commas (with no interven-
+ ing spaces). The options available are:
? Display usage
@@ -44,7 +46,7 @@
o Override some error conditions
- p='string' set prompt to string
+ p=string set prompt to string
w open for write
@@ -57,15 +59,15 @@
will display or set the input/output base. Once set, all input will de-
fault to this base and all output will be shown in this base. The base
can be overridden temporarily for input by preceding hexadecimal num-
- bers with '0x', preceding decimal numbers with '0t', or octal numbers
- with '0'. Hexadecimal numbers beginning with a-f or A-F must be pre-
- ceded with '0x' to distinguish them from commands.
+ bers with '0x', preceding decimal numbers with '0t', or preceding octal
+ numbers with '0'. Hexadecimal numbers beginning with a-f or A-F must be
+ preceded with '0x' to distinguish them from commands.
Disk addressing by fsdb is at the byte level. However, fsdb offers many
- commands to convert a desired inode, directory entry, block, superblock
- and so forth to a byte address. Once the address has been calculated,
- fsdb will record the result in dot (.).
+ commands to convert a desired inode, directory entry, block, su-
+ perblock, and so forth to a byte address. Once the address has been
+ calculated, fsdb will record the result in dot (.).
Several global values are maintained by fsdb:
@@ -89,12 +91,12 @@
Most commands use the preset value of dot in their execution. For exam-
ple,
-
> 2:inode
- will first set the value of dot to 2, ':', will alert the start of a
- command, and the inode command will set inode to 2. A count is speci-
+
+ will first set the value of dot to 2, colon (:) signifies the start of
+ a command, and the inode command will set inode to 2. A count is speci-
fied after a ','. Once set, count will remain at this value until a new
command is encountered which will then reset the value back to 1 (the
default). So, if
@@ -110,12 +112,13 @@
block to be displayed.
- End of fragment, block and file are maintained by fsdb. When displaying
- data as fragments or blocks, an error message will be displayed when
- the end of fragment or block is reached. When displaying data using the
- db, ib, directory, or file commands an error message is displayed if
- the end of file is reached. This is mainly needed to avoid passing the
- end of a directory or file and getting unknown and unwanted results.
+ End of fragment, block, and file are maintained by fsdb. When display-
+ ing data as fragments or blocks, an error message will be displayed
+ when the end of fragment or block is reached. When displaying data us-
+ ing the db, ib, directory, or file commands an error message is dis-
+ played if the end of file is reached. This is mainly needed to avoid
+ passing the end of a directory or file and getting unknown and unwanted
+ results.
An example showing several commands and the use of RETURN would be:
@@ -146,31 +149,30 @@
# numeric expressions may be composed of +, -, *, and % op-
- erators (evaluated left to right) and may use parenthe-
- ses. Once evaluated, the value of dot is updated.
+ erators (evaluated left to right) and may use parentheses.
+ Once evaluated, the value of dot is updated.
- ,count count indicator. The global value of count will be up-
- dated to count. The value of count will remain until a
- new command is run. A count specifier of '*' will attempt
- to show a blocks's worth of information. The default for
- count is 1.
+ ,count count indicator. The global value of count will be updated
+ to count. The value of count will remain until a new com-
+ mand is run. A count specifier of '*' will attempt to show
+ a blocks's worth of information. The default for count is
+ 1.
?f display in structured style with format specifier f. See
Formatted Output.
- /f display in unstructured style with format specifier f See
+ /f display in unstructured style with format specifier f. See
Formatted Output.
. the value of dot.
- +e increment the value of dot by the expression e. The
- amount actually incremented is dependent on the size of
- type:
+ +e increment the value of dot by the expression e. The amount
+ actually incremented is dependent on the size of type:
dot = dot + e * sizeof (type)
@@ -180,9 +182,9 @@
-e decrement the value of dot by the expression e. See +.
- *e multiply the value of dot by the expression e. Multipli-
- cation and division don't use type. In the above calcula-
- tion of dot, consider the sizeof(type) to be 1.
+ *e multiply the value of dot by the expression e. Multiplica-
+ tion and division don't use type. In the above calculation
+ of dot, consider the sizeof(type) to be 1.
%e divide the value of dot by the expression e. See *.
@@ -196,10 +198,10 @@
letter or digit.
- =f display indicator. If f is a legitimate format specifier.
- then the value of dot is displayed using the format spec-
- ifier f. See Formatted Output. Otherwise, assignment is
- assumed See =.
+ =f display indicator. If f is a legitimate format specifier,
+ then the value of dot is displayed using the format speci-
+ fier f. See Formatted Output. Otherwise, assignment is as-
+ sumed. See =.
= [s] [e] assignment indicator. The address pointed to by dot has
@@ -224,8 +226,8 @@
In order to view a potentially unmounted disk in a reasonable manner,
- fsdb offers the cd, pwd, ls and find commands. The functionality of
- these commands substantially matches those of its UNIX counterparts.
+ fsdb offers the cd, pwd, ls, and find commands. The functionality of
+ these commands substantially matches those of their shell counterparts.
See individual commands for details. The '*', '?', and '[-]' wild card
characters are available.
@@ -275,8 +277,8 @@
find files by name or i-number. find recursively searches directory
dir and below for filenames whose i-number matches i or whose name
matches pattern n. Note that only one of the two options (-name or
- -inum) may be used at one time. Also, the -print is not needed or
- accepted.
+ -inum) may be used at one time. Also, the -print option is not
+ needed or accepted.
fill=p
@@ -333,16 +335,15 @@
end of the log (EOL).
- ls
+ ls [ -R ] [ -l ] pat1 pat2...
- [ -R ] [ -l ] pat1
- pat2... list directories
- or files. If no file is specified, the current directory is as-
- sumed. Either or both of the options may be used (but, if used,
- must be specified before the filename specifiers). Also, as stated
- above, wild card characters are available and multiple arguments
- may be given. The long listing shows only the i-number and the
- name; use the inode command with '?i' to get more information.
+ list directories or files. If no file is specified, the current di-
+ rectory is assumed. Either or both of the options may be used (but,
+ if used, must be specified before the filename specifiers). Also,
+ as stated above, wild card characters are available and multiple
+ arguments may be given. The long listing shows only the i-number
+ and the name; use the inode command with '?i' to get more informa-
+ tion.
override
@@ -353,7 +354,7 @@
promptp
- change the fsdb prompt to p. p must be surrounded by (")s.
+ change the fsdb prompt to p. p must be surrounded by quotes (").
pwd
@@ -472,7 +473,7 @@
Formatted Output
There are two styles and many format types. The two styles are struc-
tured and unstructured. Structured output is used to display inodes,
- directories, superblocks and the like. Unstructured displays raw data.
+ directories, superblocks, and the like. Unstructured displays raw data.
The following shows the different ways of displaying:
?
@@ -792,11 +723,6 @@
SEE ALSO
ufs(4FS), dir_ufs(5), attributes(7), clri(8), fsck_ufs(8)
-WARNINGS
- Since fsdb reads the disk raw, extreme caution is advised in determin-
- ing its availability of fsdb on the system. Suggested permissions are
- 600 and owned by bin.
-
NOTES
The old command line syntax for clearing i-nodes using the ufs-specific
'-z i-number' option is still supported by the new debugger, though it
@@ -806,4 +732,4 @@
The equivalent functionality is available using the more flexible
clri(8) command.
-Oracle Solaris 11.4 20 Aug 2019 fsdb_ufs(8)
+Oracle Solaris 11.4 23 Jun 2025 fsdb_ufs(8)
diff -NurbBw 11.4.81/man8/fwflash.8 11.4.84/man8/fwflash.8
--- 11.4.81/man8/fwflash.8 2025-08-17 09:30:03.732412390 -0700
+++ 11.4.84/man8/fwflash.8 2025-08-17 09:30:26.062006749 -0700
@@ -4,11 +4,10 @@
fwflash - firmware query and update utility
SYNOPSIS
- /usr/sbin/fwflash [-l [-c device_class | ALL ]]
- | [-h]
+ /usr/sbin/fwflash [-l [-c device_class | ALL ]] | [-h]
- fwflash [-f file1,file2,file3,... | -r file]
+ /usr/sbin/fwflash [-f file1,file2,file3,... | -r file]
[-y] [-d device_path]
DESCRIPTION
@@ -46,11 +45,10 @@
-d dev_path
- The dev_path is absolute path name of the device that the user
- wants to modify with the -for -
- r operation. If the device cannot be found, the command fails. If
- the -d option is specified, then either -f or -r must also be spec-
- ified.
+ The dev_path is the absolute path name of the device that the user
+ wants to modify with the -f or -r operation. If the device cannot
+ be found, the command fails. If the -d option is specified, then
+ either -f or -r must also be specified.
-f file1,file2,file3,...
@@ -117,40 +115,7 @@
EXAMPLES
- Example 1 Entering Command Without Arguments
-
-
-
- The following command shows fwflash when the command is entered without
- arguments.
-
-
- example# fwflash
- Usage:
- Usage:
- fwflash [-l [-c device_class | ALL]] | [-h]
- fwflash [-f file1,file2,file3,... | -r file] [-y] -d device_path
-
- -l list flashable devices in this system
- -c device_class limit search to a specific class
- eg IB for InfiniBand, ses for SCSI Enclosures
- -h print this usage message
-
- -f file1,file2,file3,...
- firmware image file list to flash
- -r file file to dump device firmware to
- -y answer Yes/Y/y to prompts
- -d device_path pathname of device to be flashed
-
- If -d device_path is specified, then one of -f <files>
- or -r <file> must also be specified
-
- If multiple firmware images are required to be flashed
- they must be listed together, separated by commas. The
- images will be flashed in the order specified.
-
-
- Example 2 Listing Devices Available to Flash
+ Example 1 Listing Devices Available to Flash
@@ -211,7 +176,7 @@
Firmware revision: 5021
- Example 3 Flash Upgrading an IB HCA Device
+ Example 2 Flash Upgrading an IB HCA Device
@@ -249,7 +212,7 @@
Done. New image will be active after the system is rebooted.
- Example 4 Flash Upgrading an ETH Device
+ Example 3 Flash Upgrading an ETH Device
@@ -273,7 +236,7 @@
- Example 5 Reading Device Firmware to File
+ Example 4 Reading Device Firmware to File
@@ -291,9 +254,7 @@
Done.
-
-
- Example 6 When No Flashable Devices Are Found
+ Example 5 When No Flashable Devices Are Found
@@ -318,14 +279,10 @@
RETURN VALUES
The fwflash command returns the following values:
- 0
-
- Success
-
+ 0 Success
- 1
- Failure
+ 1 Failure
ATTRIBUTES
@@ -393,4 +350,4 @@
firmware from the card.
-Oracle Solaris 11.4 18 Oct 2018 fwflash(8)
+Oracle Solaris 11.4 23 Jun 2025 fwflash(8)
diff -NurbBw 11.4.81/man8/getty.8 11.4.84/man8/getty.8
--- 11.4.81/man8/getty.8 2025-08-17 09:30:03.767983817 -0700
+++ 11.4.84/man8/getty.8 2025-08-17 09:30:26.096236562 -0700
@@ -4,78 +4,18 @@
getty - set terminal type, modes, speed, and line discipline
SYNOPSIS
- /usr/lib/saf/ttymon [-h] [-t timeout] line
- [speed [type [linedisc]]]
-
-
- /usr/lib/saf/ttymon -c file
+ /etc/getty
DESCRIPTION
- getty sets terminal type, modes, speed, and line discipline. getty is a
- symbolic link to /usr/lib/saf/ttymon. It is included for compatibility
- with previous releases for the few applications that still call getty
- directly.
-
-
- getty can only be executed by the super-user, (a process with the user
- ID root). Initially getty prints the login prompt, waits for the
- user's login name, and then invokes the login command. getty attempts
- to adapt the system to the terminal speed by using the options and ar-
- guments specified on the command line.
-
-
- Without optional arguments, getty specifies the following: The speed of
- the interface is set to 300 baud, either parity is allowed, NEWLINE
- characters are converted to carriage return-line feed, and tab expan-
- sion is performed on the standard output. getty types the login prompt
- before reading the user's name a character at a time. If a null charac-
- ter (or framing error) is received, it is assumed to be the result of
- the user pressing the BREAK key. This will cause getty to attempt the
- next speed in the series. The series that getty tries is determined by
- what it finds in /etc/ttydefs .
-
-OPTIONS
- The following options are supported:
-
- -h If the -h flag is not set, a hangup will be forced by
- setting the speed to zero before setting the speed to the
- default or a specified speed.
-
-
- -t timeout Specifies that getty should exit if the open on the line
- succeeds and no one types anything in timeout seconds.
-
-
- -c file The -c option is no longer supported. Instead use
- /usr/sbin/sttydefs -l to list the contents of the
- /etc/ttydefs file and perform a validity check on the
- file.
-
-
-OPERANDS
- The following operands are supported:
-
- line The name of a TTY line in /dev to which getty is
- to attach itself. getty uses this string as the
- name of a file in the /dev directory to open for
- reading and writing.
-
-
- speed The speed argument is a label to a speed and TTY
- definition in the file /etc/ttydefs. This defini-
- tion tells getty at what speed to run initially,
- what the initial TTY settings are, and what speed
- to try next, (should the user press the BREAK key
- to indicate that the speed is inappropriate). The
- default speed is 300 baud.
-
-
- type and linedisc These options are obsolete and will be ignored.
-
+ In Solaris 1.x, SunOS 4.x, and earlier releases, the getty command set
+ terminal type, modes, speed, and line discipline. In the Solaris 2.0
+ through Solaris 10 releases, /etc/getty was a symbolic link to
+ /usr/lib/saf/ttymon, included for compatibility with previous releases
+ for the few applications that still called getty directly.
-FILES
- /etc/ttydefs
+ In Oracle Solaris 11.0 and later releases, the getty symlink has been
+ removed and ttymon(8) should be executed directly instead.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -83,11 +23,11 @@
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
- | Availability |system/core-os |
+ | Availability |None |
+------------------------------+-----------------------------+
SEE ALSO
- login(1), ioctl(2), tty(4D), attributes(7), sttydefs(8), ttymon(8)
+ login(1), tty(4D), ttydefs(5), attributes(7), sttydefs(8), ttymon(8)
-Oracle Solaris 11.4 19 Feb 2019 getty(8)
+Oracle Solaris 11.4 23 Jun 2025 getty(8)
diff -NurbBw 11.4.81/man8/hal-device.8 11.4.84/man8/hal-device.8
--- 11.4.81/man8/hal-device.8 2025-08-17 09:30:03.801916796 -0700
+++ 11.4.84/man8/hal-device.8 2025-08-17 09:30:26.132903483 -0700
@@ -4,7 +4,7 @@
hal-device - manage HAL devices
SYNOPSIS
- hal-device [-h] [--a udi | --r udi]
+ hal-device [-h | -a udi | -r udi]
DESCRIPTION
The Hardware Abstraction Layer (HAL) provides a view of the various
@@ -20,7 +20,7 @@
udi to HAL's global device list.
- -h Display usage information.
+ -h, --help Display usage information.
-r, --remove udi Remove device specified by Universal Device Identi-
@@ -42,4 +42,4 @@
SEE ALSO
attributes(7), hal(7), hald(8)
-Oracle Solaris 11.4 16 Aug 2011 hal-device(8)
+Oracle Solaris 11.4 23 Jun 2025 hal-device(8)
diff -NurbBw 11.4.81/man8/halt.8 11.4.84/man8/halt.8
--- 11.4.81/man8/halt.8 2025-08-17 09:30:03.833046386 -0700
+++ 11.4.84/man8/halt.8 2025-08-17 09:30:26.169565891 -0700
@@ -70,4 +70,9 @@
in inittab(5). To ensure a complete shutdown of system services, use
shutdown(8) or init(8) to reboot a Solaris system.
-Oracle Solaris 11.4 4 Dec 2023 halt(8)
+
+ System halt may be blocked if an admin has used sysadm(8) to place the
+ system into a noreboot maintenance mode, or if the config/noreboot
+ property is set to true on the svc:/system/boot-config SMF service.
+
+Oracle Solaris 11.4 23 Jun 2025 halt(8)
diff -NurbBw 11.4.81/man8/inetd.8 11.4.84/man8/inetd.8
--- 11.4.81/man8/inetd.8 2025-08-17 09:30:03.882369394 -0700
+++ 11.4.84/man8/inetd.8 2025-08-17 09:30:26.222846479 -0700
@@ -302,8 +302,8 @@
max_con_rate
The maximum allowed connection rate, in connections per second, for
- a nowait-type service. The values 0 and -1 specify that that con-
- nection rate limiting is disabled.
+ a nowait-type service. The values 0 and -1 specify that connection
+ rate limiting is disabled.
max_copies
@@ -384,8 +384,8 @@
warning severity level). See syslog.conf(5) for a description of
syslog codes and severity levels. The Interface Stability of the
TCP wrappers facility and its configuration files is Volatile. As
- the TCP wrappers facility is not controlled by Sun, intra-release
- incompatibilities are not uncommon. See attributes(7).
+ the TCP wrappers facility is not controlled by Oracle, intra-re-
+ lease incompatibilities may occur. See attributes(7).
For more information about configuring TCP wrappers, see the
tcpd(8) and hosts_access(5) man pages, available in the secu-
@@ -441,8 +441,8 @@
Each method specified for a service will have its configuration stored
in the SMF repository, within a property group of the same name as the
method. The set of properties allowable for these methods includes
- those specified for the services managed by svc.startd(8). (See
- svc.startd(8) for further details.) Additionally, for the inetd_start
+ those specified for the services managed by svc.startd(8). See
+ svc.startd(8) for further details. Additionally, for the inetd_start
method, you can set the arg0 property.
@@ -623,4 +623,4 @@
properties, respectively. These properties are described above, under
"Service Properties".
-Oracle Solaris 11.4 27 Nov 2017 inetd(8)
+Oracle Solaris 11.4 23 Jun 2025 inetd(8)
diff -NurbBw 11.4.81/man8/infocmp.8 11.4.84/man8/infocmp.8
--- 11.4.81/man8/infocmp.8 2025-08-17 09:30:03.921480171 -0700
+++ 11.4.84/man8/infocmp.8 2025-08-17 09:30:26.261742275 -0700
@@ -11,16 +11,16 @@
DESCRIPTION
infocmp compares a binary terminfo entry with other terminfo entries,
rewrites a terminfo description to take advantage of the use= terminfo
- field, or prints out a terminfo description from the binary file ( term
- ) in a variety of formats. It displays boolean fields first, then nu-
- meric fields, followed by the string fields. If no options are speci-
- fied and zero, or one termname is specified, the -I option is assumed.
- If more than one termname is specified, the -d option is assumed.
+ field, or prints out a terminfo description from the binary file (term)
+ in a variety of formats. It displays boolean fields first, then numeric
+ fields, followed by the string fields. If no options are specified, and
+ zero or one termname is specified, the -I option is assumed. If more
+ than one termname is specified, the -d option is assumed.
OPTIONS
- The -d , -c , and -n options can be used for comparisons. infocmp
- compares the terminfo description of the first terminal termname with
- each of the descriptions given by the entries for the other terminal's
+ The -d, -c, and -n options can be used for comparisons. infocmp com-
+ pares the terminfo description of the first terminal termname with each
+ of the descriptions given by the entries for the other terminal's
termname. If a capability is defined for only one of the terminals, the
value returned will depend on the type of the capability: F for boolean
variables, -1 for integer variables, and NULL for string variables.
@@ -43,8 +43,8 @@
- The -I , -L , and -C options will produce a source listing for each
- terminal named.
+ The -I, -L, and -C options will produce a source listing for each ter-
+ minal named.
-I Use the terminfo names.
@@ -74,12 +74,12 @@
tional.
- All termcap variables no longer supported by terminfo , but are deriv-
- able from other terminfo variables, will be displayed. Not all terminfo
- capabilities will be translated; only those variables which were part
- of termcap will normally be displayed. Specifying the -r option will
- take off this restriction, allowing all capabilities to be displayed in
- termcap form.
+ All termcap variables which are no longer supported by terminfo, but
+ are derivable from other terminfo variables, will be displayed. Not all
+ terminfo capabilities will be translated; only those variables which
+ were part of termcap will normally be displayed. Specifying the -r op-
+ tion will take off this restriction, allowing all capabilities to be
+ displayed in termcap form.
Note that because padding is collected to the beginning of the capabil-
@@ -94,13 +94,21 @@
Some common terminfo parameter sequences, their termcap equivalents,
and some terminal types which commonly have such sequences, are:
- terminfo termcap Representative Terminals
- %p1%c %. adm
- %p1%d %d hp, ANSI standard, vt100
- %p1%'x'%+%c %+x concept
- %i %i ANSI standard, vt100
- %p1%?%'x'%>%t%p1%'y'%+%; %>xy concept
- %p2 is printed before %p1 %r hp
+ +------------------------------+---------+-------------------------+
+ | terminfo |termcap |Representative Terminals |
+ +------------------------------+---------+-------------------------+
+ | %p1%c |%. |adm |
+ +------------------------------+---------+-------------------------+
+ | %p1%d |%d |hp, ANSI standard, vt100 |
+ +------------------------------+---------+-------------------------+
+ | %p1%'x'%+%c |%+x |concept |
+ +------------------------------+---------+-------------------------+
+ | %i |%i |ANSI standard, vt100 |
+ +------------------------------+---------+-------------------------+
+ | %p1%?%'x'%>%t%p1%'y'%+%; |%>xy |concept |
+ +------------------------------+---------+-------------------------+
+ | %p2 is printed before %p1 |%r |hp |
+ +------------------------------+---------+-------------------------+
-u Produce a terminfo source description of the first terminal
@@ -219,4 +227,4 @@
SEE ALSO
curses(3CURSES), terminfo(5), attributes(7), captoinfo(8), tic(8)
-Oracle Solaris 11.4 11 May 2021 infocmp(8)
+Oracle Solaris 11.4 23 Jun 2025 infocmp(8)
diff -NurbBw 11.4.81/man8/init.8 11.4.84/man8/init.8
--- 11.4.81/man8/init.8 2025-08-17 09:30:03.964333188 -0700
+++ 11.4.84/man8/init.8 2025-08-17 09:30:26.304265515 -0700
@@ -36,8 +36,9 @@
When the system is booted, init is invoked and the following occurs.
First, it reads the properties for the svc:/system/environment:init
service. Among these properties are values for locale-related environ-
- ments, such as LANG or LC_CTYPE . init then looks in /etc/inittab for
- the initdefault entry (see inittab(5)). If the initdefault entry:
+ ment variables, such as LANG or LC_CTYPE. init then looks in /etc/init-
+ tab for the initdefault entry (see inittab(5)). If the initdefault en-
+ try:
exists
@@ -61,10 +62,10 @@
init goes to the single-user state. In this state, the system con-
sole device (/dev/console) is opened for reading and writing and
- the command /usr/sbin/su, (see su(8)), is invoked. Use init to
- change the run level of the system. Note that if the shell is ter-
- minated (using an end-of-file), init only re-initializes to the
- single-user state if /etc/inittab does not exist.
+ the sulogin(8) command is invoked. Use init to change the run level
+ of the system. Note that if the shell is terminated (using an end-
+ of-file), init only re-initializes to the single-user state if
+ /etc/inittab does not exist.
0-6
@@ -132,7 +133,8 @@
Setting Environment Variables
You can set default values for environment variables, for such items as
time zone and character formatting, in the list of properties for the
- svc:/system/environment:init service.
+ svc:/system/environment:init service. See environ(7) for definitions of
+ commonly used environment variables.
SECURITY
init uses pam(3PAM) for session management. The PAM configuration pol-
@@ -282,9 +284,8 @@
TZ
- Always set to localtime. To set the system time zone, an admin-
- istrator must set the timezone/localtime property in time-
- zone:default SMF service.
+ Always set to localtime. To set the system time zone, see the
+ TZ entry in environ(7).
CMASK
@@ -293,7 +294,7 @@
inherits from the init process. If not set, init uses the mask
it inherits from the kernel. Note that init always attempts to
apply a umask of 022 before creating a file, regardless of the
- setting of CMASK
+ setting of CMASK.
LC_CTYPE
@@ -378,9 +379,10 @@
SEE ALSO
login(1), sh(1), stty(1), who(1), ioctl(2), kill(2), ctime(3C),
- pam(3PAM), termio(4I), environ(7), init.d(5), inittab(5), pam.conf(5),
- utmpx(5), attributes(7), pam_unix_session(7), smf(7), kernel(8), shut-
- down(8), su(8), svc.configd(8), svc.startd(8), sysadm(8), ttymon(8)
+ pam(3PAM), termio(4I), init.d(5), inittab(5), pam.conf(5), utmpx(5),
+ attributes(7), environ(7), pam_unix_session(7), smf(7), kernel(8),
+ shutdown(8), sulogin(8), svc.configd(8), svc.startd(8), sysadm(8),
+ ttymon(8)
DIAGNOSTICS
If init finds that it is respawning an entry from /etc/inittab more
@@ -424,4 +426,54 @@
When you shut down an image, services are shut down in reverse depen-
dency order.
-Oracle Solaris 11.4 25 Jul 2023 init(8)
+
+ Transition to run levels 0, 5, or 6 may be blocked if an admin has used
+ sysadm(8) to place the system into a noreboot maintenance mode, or if
+ the config/noreboot property is set to true on the svc:/system/boot-
+ config SMF service.
+
+HISTORY
+ The init daemon has always been run with process id 1 in the global
+ zone, or on systems without zones. In non-global zones, the init daemon
+ for that zone was identified with a process id other than 1 before Ora-
+ cle Solaris 11.4.81. Starting in Solaris 11.4.81, the init daemon for a
+ zone will always show as process id 1 when viewed from within the zone.
+
+
+ When the parent process of a process exits or is killed, the child
+ process is assigned the init daemon as its parent process. Prior to Or-
+ acle Solaris 11.4.66, this was always the global zone's init daemon,
+ process id 1. Starting in Solaris 11.4.66, orphaned processes in non-
+ global zones have their parent process set to the non-global zone's
+ init daemon, which may have a process id other than 1 in releases prior
+ to 11.4.81, as described above.
+
+
+ The ability to block certain run level changes with the sysadm maintain
+ command was added in Oracle Solaris 11.4.63.
+
+
+ Support for the -c option to provide a comment for run-level changes
+ was added in Oracle Solaris 11.4.63.
+
+
+ The TZ environment variable was removed from the default /etc/de-
+ fault/init file in Oracle Solaris 11.4.0.
+
+
+ The /etc/default/init file was replaced by the svc:/system/environ-
+ ment:init service properties in Oracle Solaris 11.0.0.
+
+
+ The TZ environment variable was changed to the value of localtime in
+ the default /etc/default/init file in Oracle Solaris 11.0.0.
+
+
+ Management of system services was migrated from init to the service
+ management facility, smf(7), in Solaris 10 3/05.
+
+
+ Support for run levels and /etc/inittab was added to Solaris in Solaris
+ 2.0.
+
+Oracle Solaris 11.4 23 Jun 2025 init(8)
diff -NurbBw 11.4.81/man8/install.8 11.4.84/man8/install.8
--- 11.4.81/man8/install.8 2025-08-17 09:30:04.001688481 -0700
+++ 11.4.84/man8/install.8 2025-08-17 09:30:26.341930512 -0700
@@ -74,8 +74,8 @@
This version of install (/usr/sbin/install) is not compatible with the
install command in many systems other than Solaris. For a higher degree
- of compatibility with other systems, use GNU install described in the
- install(1) man page.
+ of cross-platform compatibility, use GNU install, available as
+ /usr/bin/install. See install(1).
OPTIONS
The following options are supported:
@@ -89,8 +89,8 @@
-f dirb Force file to be installed in given directory, even if the
file already exists. If the file being installed does not
already exist, the mode and owner of the new file is set to
- 755 and bin , respectively. If the file already exists,
- the mode and owner is that of the already existing file.
+ 755 and bin, respectively. If the file already exists, the
+ mode and owner is that of the already existing file.
-n dirc If file is not found in any of the searched directories, it
@@ -99,8 +99,8 @@
-d Create a directory. Missing parent directories are created
- as required as in mkdir -p. If the directory already ex-
- ists, the owner, group and mode is set to the values given
+ as required, as in mkdir -p. If the directory already ex-
+ ists, the owner, group, and mode is set to the values given
on the command line.
@@ -123,7 +123,7 @@
-o If file is found, save the existing file by copying it to
OLDfile in the directory in which it was found. This option
is useful when installing a frequently used file such as
- /bin/sh or /lib/saf/ttymon, where the existing file cannot
+ /bin/sh or /usr/sbin/ttymon, where the existing file cannot
be removed.
@@ -144,4 +144,4 @@
make(1S), chgrp(1), chmod(1), chown(1), cp(1), install(1), mkdir(1),
attributes(7)
-Oracle Solaris 11.4 11 May 2021 install(8)
+Oracle Solaris 11.4 23 Jun 2025 install(8)
diff -NurbBw 11.4.81/man8/iscsiadm.8 11.4.84/man8/iscsiadm.8
--- 11.4.81/man8/iscsiadm.8 2025-08-17 09:30:04.055090484 -0700
+++ 11.4.84/man8/iscsiadm.8 2025-08-17 09:30:26.395875988 -0700
@@ -47,7 +47,7 @@
add Subcommand
The syntax for the add subcommand is:
- # iscsiadm add direct_object [operands...]
+ iscsiadm add direct_object [operands...]
@@ -67,7 +67,7 @@
The discovery-address parameter is formatted as:
- <IP address>[:port]
+ <IP-address>[:port]
If port is not specified, the default of 3260 will be used.
@@ -109,7 +109,7 @@
list Subcommand
The syntax for the list subcommand is:
- # iscsiadm list direct-object [options]
+ iscsiadm list direct-object [options]
@@ -152,8 +152,7 @@
method was used for the target's discovery. Reports information for
specified targets or, if no targets are specified, all targets that
have been discovered or have had parameters modified by the modify
- target subcom-
- mand.
+ target subcommand.
When used with the -S option for a specified target, this subcom-
mand returns:
@@ -225,7 +224,7 @@
modify Subcommand
The syntax for the modify subcommand is:
- # iscsiadm modify direct_object [options]
+ iscsiadm modify direct_object [options]
@@ -574,7 +573,7 @@
The conn-login-max option lets the iSCSI initiator reestab-
lish the connection to the target in case of IO timeout or
connection failure during the given time window. Valid
- value is from 0 to 60*60, default to 180 seconds.
+ value is from 0 to 60*60. The default value is 180 seconds.
polling-login-delay
@@ -584,7 +583,7 @@
The polling-login-delay option specifies the time interval
between each login retry when iSCSI initiator to target IO
timeout or connection failure. Valid value is from 0 to
- 60*60, default to 60 seconds.
+ 60*60. The default value is 60 seconds.
@@ -592,7 +591,7 @@
remove Subcommand
The syntax for the remove subcommand is:
- # iscsiadm remove direct_object
+ iscsiadm remove direct_object
@@ -737,13 +734,11 @@
-
-
Example 4 Obtaining Verbose Discovery Output
- The following commands uses the -v option (one with, one without) with
+ The following commands use the -v option (one with, one without) with
the list subcommand to obtain verbose output.
@@ -1018,4 +999,4 @@
command. You can query the status of this service by using the svcs
command.
-Oracle Solaris 11.4 19 Jul 2023 iscsiadm(8)
+Oracle Solaris 11.4 23 Jun 2025 iscsiadm(8)
diff -NurbBw 11.4.81/man8/isns.8 11.4.84/man8/isns.8
--- 11.4.81/man8/isns.8 2025-08-17 09:30:04.090671011 -0700
+++ 11.4.84/man8/isns.8 2025-08-17 09:30:26.432352871 -0700
@@ -102,19 +102,19 @@
The isns server supports certain rbac(7) authorizations that allow you
to administer isns activity. These authorizations include the following
- auth_attr(5) privileges:
+ auth_attr(5) authorizations:
solaris.isnsmgr.write
Required to create a discovery domain or domain set, to enable/dis-
- able a discovery domain set and to change grouping of iSNS clients
+ able a discovery domain set, and to change grouping of iSNS clients
in a discovery domain or grouping of discovery domains in a discov-
ery domain set.
solaris.smf.manage.isns
- Required to manage the isns server through the smf(7).
+ Required to manage the isns server through smf(7).
solaris.smf.value.isns
@@ -201,4 +201,4 @@
to add a member to it, in order to create discovery domain and discov-
ery domain set associations.
-Oracle Solaris 11.4 11 May 2021 isns(8)
+Oracle Solaris 11.4 23 Jun 2025 isns(8)
diff -NurbBw 11.4.81/man8/kstat2.8 11.4.84/man8/kstat2.8
--- 11.4.81/man8/kstat2.8 2025-08-17 09:30:04.131642069 -0700
+++ 11.4.84/man8/kstat2.8 2025-08-17 09:30:26.475987395 -0700
@@ -4,9 +4,8 @@
kstat2 - display kernel statistics
SYNOPSIS
- kstat2 [[-j | -l | -p | -q] | [-h] [-d]]
- [-m] [-i N] [-c N] [-T d|u]
- [[-g <glob_uri>] ...] [[-r <re_uri>] ...] [[uri] ...]
+ kstat2 [[-j | -l | -p | -q] | [-h] [-d]] [-m] [-i N] [-c N] [-T d|u]
+ [-g glob_uri]... [-r re_uri]... [uri]...
DESCRIPTION
The kstat2 utility examines the available kernel statistics or kstats
@@ -55,13 +53,12 @@
-
Kstats may be selected for display by providing a selector URI either
as a plain string for direct comparison with the kstat URI, or as a
- shell glob pattern or Perl Compatible Regular expression(PCRE) to match
- against the kstat URI. When specifying a selector URI, the URI scheme
- is optional. For example, the following two selectors are equivalent.
-
+ shell glob pattern or Perl Compatible Regular expression (PCRE) to
+ match against the kstat URI. When specifying a selector URI, the URI
+ scheme is optional. For example, the following two selectors are equiv-
+ alent.
/<category>/<component>/<name>
kstat:/<category>/<component>/<name>
@@ -145,10 +141,10 @@
JSON output provides output consisting of the kstat URI, the statistics
- value and optionally the metadata. All kstats that match the selectors
+ value, and optionally the metadata. All kstats that match the selectors
provided will be output as a single JSON result set, in the following
- format (For readability, this is formatted over multiple lines. The re-
- sult set is actually output on a single line.)
+ format. (For readability, this is formatted over multiple lines. The
+ result set is actually output on a single line.)
{
"<URI_A>": {
@@ -200,69 +196,68 @@
The following options are supported:
-
- -c --count=N
+ -c N, --count=N
The number of reports to be printed.
- -d --desc
+ -d, --desc
- Includes the statistic description in the output
+ Includes the statistic description in the output.
- -g --glob=glob_uri
+ -g glob_uri, --glob=glob_uri
Displays only kstats where the kstat URI matches the given shell
glob pattern.
- -h --human-readable
+ -h, --human-readable
Displays output in a human readable format. This differs from the
default output format in that kstat values are scaled and formatted
to make them more human readable.
- -i --interval=N
+ -i N, --interval=N
The number of seconds between reports.
- -j --json
+ -j, --json
Displays output in JSON output format.
- -l --list
+ -l, --list
Lists matching kstat URIs without displaying values.
- -m --metadata
+ -m, --metadata
Includes metadata for the kstat or statistic in the displayed out-
put.
- -p --parseable
+ -p, --parseable
Displays output in parseable format.
- -q --quiet
+ -q, --quiet
Displays no output, but returns appropriate exit status for matches
against given criteria.
- -r --regex=re_uri
+ -r re_uri, --regex=re_uri
Displays only kstats where the kstat URI matches the given Perl
- Compatible Regular expression(PCRE).
+ Compatible Regular Expression (PCRE).
- -T --timestamp d | u
+ -T d | u, --timestamp d | u
Displays a time stamp before each statistics block, either in
date(1) format (d) or as an alphanumeric representation of the
@@ -273,12 +267,10 @@
OPERANDS
The following operand is supported:
-
uri
Displays only kstats where the kstat URI is equal to the specified
- URI.
-
+ URI, or if a pattern is specified, matches the pattern.
EXIT STATUS
@@ -416,14 +393,11 @@
kstat:/system/cpu/0/sys;syscall 124308113
-
Example 8 Display Readable Statistics
- example$ kstat2 kstat:/vm/unix/vminfo:swap_free kstat:/vm/unix/vminfo:snaptime
-
-
-
+ example$ kstat2 kstat:/vm/unix/vminfo:swap_free \
+ kstat:/vm/unix/vminfo:snaptime
snaptime 2193622143290103 / 1000000000 seconds
swap_free 1262611263678 * 4096 bytes
@@ -428,12 +402,11 @@
swap_free 1262611263678 * 4096 bytes
-
Example 9 Displaying Readable Statistic Metadata
-
- example$ kstat2 -m kstat:/vm/unix/vminfo:swap_free kstat:/vm/unix/vminfo:snaptime
+ example$ kstat2 -m kstat:/vm/unix/vminfo:swap_free \
+ kstat:/vm/unix/vminfo:snaptime
snaptime 2193622143290103 / 1000000000 seconds
type: Relative time
@@ -559,4 +521,4 @@
are also shell metacharacters, it will be necessary to enclose the pat-
tern with appropriate shell quotes.
-Oracle Solaris 11.4 11 May 2021 kstat2(8)
+Oracle Solaris 11.4 23 Jun 2025 kstat2(8)
diff -NurbBw 11.4.81/man8/ldap_cachemgr.8 11.4.84/man8/ldap_cachemgr.8
--- 11.4.81/man8/ldap_cachemgr.8 2025-08-17 09:30:04.168092796 -0700
+++ 11.4.84/man8/ldap_cachemgr.8 2025-08-17 09:30:26.513383932 -0700
@@ -9,23 +9,26 @@
DESCRIPTION
The ldap_cachemgr daemon is a process that provides an up-to-date con-
- figuration cache for LDAP naming services. It is started during multi-
- user boot.
+ figuration cache for LDAP naming services. It is started automatically
+ by the service management facility, smf(7), under the service identi-
+ fier:
+
+ svc:/network/ldap/client
- The ldap_cachemgr utility provides caching for all parameters as speci-
+ The ldap_cachemgr daemon provides caching for all parameters as speci-
fied and used by the LDAP naming service clients. The ldap_cachemgr
- utility uses the cache files which are originally created by executing
+ daemon uses the cache files which are originally created by executing
the ldapclient(8) utility, as cold start files. Updates to the cache
files take place dynamically if profiles are used to configure the
client. See the init option to ldapclient(8).
- The ldap_cachemgr utility helps improve the performance of the clients
+ The ldap_cachemgr daemon helps improve the performance of the clients
that are using LDAP as the Naming service repository. In order for the
LDAP naming services to function properly, the ldap_cachemgr daemon
must be running. ldap_cachemgr also improves system security by making
- the configuration files readable by superuser only.
+ the configuration files readable only by the superuser.
The cache maintained by this daemon is shared by all the processes that
@@ -68,8 +71,7 @@
The following example shows how to stop and to restart the
- ldap_cachemgr
- daemon.
+ ldap_cachemgr daemon.
example# svcadm disable network/ldap/client
@@ -76,18 +78,15 @@
example# svcadm enable network/ldap/client
-
Example 2 Forcing ldap_cachemgr to Reread Configuration Files
The following example shows how to force ldap_cachemgr to reread the
- /var/ldap/ldap_client_file and /var/ldap/ldap_client_cred
- files
-
+ /var/ldap/ldap_client_file and /var/ldap/ldap_client_cred files.
- example# pkill -HUP ldap_cachemgr
+ example# svcadm refresh network/ldap/client
FILES
@@ -132,4 +131,4 @@
requesting restart, can be performed using svcadm(8). The service's
status can be queried using the svcs(1) command.
-Oracle Solaris 11.4 4 Oct 2018 ldap_cachemgr(8)
+Oracle Solaris 11.4 23 Jun 2025 ldap_cachemgr(8)
diff -NurbBw 11.4.81/man8/ldapclient.8 11.4.84/man8/ldapclient.8
--- 11.4.81/man8/ldapclient.8 2025-08-17 09:30:04.230726066 -0700
+++ 11.4.84/man8/ldapclient.8 2025-08-17 09:30:26.572414011 -0700
@@ -200,12 +200,11 @@
Initializes an LDAP client machine from a profile that is stored on
the specified LDAP_server; a single address or name with optional
- port as described in Server
- List.
+ port as described in Server List.
Once the profile is loaded, the preferredServerList and
defaultServerList specified in the profile are used; LDAP_server
- becomes irrelevant
+ becomes irrelevant.
The LDAP client uses the attributes in the specified profile to de-
termine the configuration of the LDAP client. Using a configuration
@@ -401,8 +400,8 @@
enableShadowUpdate=true | false
Specify whether the client is allowed to update Shadow Data (de-
- fined below) . If set to true and the credential level is proxy
- then adminDN and adminPassword must be specified.
+ fined below). If set to true and the credential level is proxy then
+ adminDN and adminPassword must be specified.
followReferrals=true | false
@@ -607,7 +606,7 @@
It does not set up the client to resolve hostnames using DNS. Refer to
the DNS documentation for information on setting up DNS in re-
- solv.conf(5)
+ solv.conf(5).
Note that for sasl/GSSAPI DNS should be used.
@@ -733,7 +732,7 @@
This authentication method is used in conjunction with nscd per-
user mode to enable per-user lookups. In per-user mode a separate
nscd process runs for each user which binds to the server using the
- sasl/GSSAPI method and the users Kerberos(7) credentials. The per-
+ sasl/GSSAPI method and the users kerberos(7) credentials. The per-
user nscd process then performs all the user's lookups using the
user's Kerberos principal. Access can be controlled in the direc-
tory server on a per-user basis. See the enable_per_user_lookup
@@ -1029,7 +1028,7 @@
/etc/nsswitch.ldap
Sample configuration file for the name-service switch configured
- with LDAP, files and DNS.
+ with LDAP, files, and DNS.
ATTRIBUTES
@@ -1080,7 +1079,7 @@
traffic ldapclient displays (and ldap_cachemgr(8) logs) a warning iden-
tifying the faulty method, for example:
- "Warning: Using non-integrity-protected authentication method: simple
+ Warning: Using non-integrity-protected authentication method: simple
NOTES
@@ -1180,4 +1179,4 @@
Starting with Oracle Solaris 11.4, nscd daemon must be running for
ldap(7) services to function correctly.
-Oracle Solaris 11.4 31 Jul 2024 ldapclient(8)
+Oracle Solaris 11.4 23 Jun 2025 ldapclient(8)
diff -NurbBw 11.4.81/man8/ldm.8 11.4.84/man8/ldm.8
--- 11.4.81/man8/ldm.8 2025-08-17 09:30:04.457489572 -0700
+++ 11.4.84/man8/ldm.8 2025-08-17 09:30:26.798453338 -0700
@@ -481,9 +481,9 @@
o migration-class2 is a cross-CPU migration family for
SPARC T7, SPARC M7, SPARC S7, SPARC T8 and SPARC M8 se-
- ries servers. These platforms support 16GB pagesizes and
- the DAX co-processor, which this migration class pre-
- serves.
+ ries servers. These platforms support 16GB pagesizes,
+ ADI, and the DAX co-processor, which this migration
+ class preserves.
This value is not compatible with Fujitsu M10 servers
and Fujitsu SPARC M12 servers.
@@ -776,9 +776,9 @@
o migration-class2 is a cross-CPU migration family for
SPARC T7, SPARC M7, SPARC S7, SPARC T8 and SPARC M8 se-
- ries servers. These platforms support 16GB pagesizes and
- the DAX co-processor, which this migration class pre-
- serves.
+ ries servers. These platforms support 16GB pagesizes,
+ ADI, and the DAX co-processor, which this migration
+ class preserves.
This value is not compatible with Fujitsu M10 servers
and Fujitsu SPARC M12 servers.
@@ -3259,13 +3259,17 @@
Set Options for a Virtual Disk
The set-vdisk subcommand sets options for a virtual disk in the speci-
- fied logical domain. An optional timeout property allows you to specify
- a timeout for a virtual disk if it cannot establish a connection with
- the virtual disk server.
+ fied logical domain.
+
+
+ Use the timeout property to specify the maximum number of seconds that
+ a virtual disk spends to establish a connection with the virtual disk
+ server. This property can be set when the specified logical domain is
+ active or inactive.
- Except when used for mpgroup disks, this command can be used only when
- the domain is bound or inactive.
+ Use the volume property to specify the new active path for an mpgroup
+ disk.
When disk-name is an mpgroup disk, you can use the ldm set-vdisk com-
@@ -3304,10 +3308,8 @@
ent vds, and the timeout ensures that a connection to any
vds is established within the specified amount of time.
- Set timeout=0 to disable the timeout.
-
- Do not specify a timeout= argument to have the virtual disk
- wait indefinitely.
+ Set timeout=0 to disable the timeout. This causes vdc to
+ wait forever to establish a connection with vds.
o volume=volume-name is the name of the virtual disk server
@@ -3322,7 +3324,7 @@
virtual disk was previously added.
- Set Options for a Virtual Disk
+ Remove a Virtual Disk
The remove-vdisk subcommand removes a virtual disk from the specified
logical domain.
@@ -7204,4 +7206,4 @@
Oracle VM Server for SPARC 3.6 Administration Guide
-Oracle Solaris 11.4 14 Jan 2025 ldm(8)
+Oracle Solaris 11.4 23 Jun 2025 ldm(8)
diff -NurbBw 11.4.81/man8/lockstat.8 11.4.84/man8/lockstat.8
--- 11.4.81/man8/lockstat.8 2025-08-17 09:30:04.503355703 -0700
+++ 11.4.84/man8/lockstat.8 2025-08-17 09:30:26.843313473 -0700
@@ -68,7 +68,7 @@
-e event_list
- Only watch the specified events. event list is a comma-separated
+ Only watch the specified events. event_list is a comma-separated
list of events or ranges of events such as 1,4-7,35. Run lockstat
with no arguments to get a brief description of all events.
@@ -346,20 +336,13 @@
[...]
-
-
Example 3 Measuring Hold Times for Stack Traces Containing a Specific
Function
example# lockstat -H -f so_recvmsg -s 50 -D 10 sleep 10
- Adaptive mutex hold: 171792 events in 10.089 seconds (17028 events/sec)
-
-
-
-
-
+ Adaptive mutex hold: 171792 events in 10.089 seconds (17028 events/sec)
-------------------------------------------------------------------------------
Count indv cuml rcnt nsec Lock Caller
@@ -403,12 +384,7 @@
example# lockstat -kIW -D 20 ./polltest
- Profiling interrupt: 82 events in 0.424 seconds (194
- events/sec)
-
-
-
-
+ Profiling interrupt: 82 events in 0.424 seconds (194 events/sec)
Count indv cuml rcnt nsec Hottest CPU+PIL Caller
-----------------------------------------------------------------------
@@ -620,4 +588,4 @@
content of lockstat output reflect the current Solaris kernel implemen-
tation and are therefore subject to change in future releases.
-Oracle Solaris 11.4 6 Sept 2019 lockstat(8)
+Oracle Solaris 11.4 23 Jun 2025 lockstat(8)
diff -NurbBw 11.4.81/man8/lofiadm.8 11.4.84/man8/lofiadm.8
--- 11.4.81/man8/lofiadm.8 2025-08-17 09:30:04.549834433 -0700
+++ 11.4.84/man8/lofiadm.8 2025-08-17 09:30:26.889222394 -0700
@@ -13,13 +13,16 @@
/usr/sbin/lofiadm -l [-b block_size] [-u user:group] -r file [device]
- /usr/sbin/lofiadm -c crypto_algorithm [-b block_size] [-u user:group] -a file | -r [device]
+ /usr/sbin/lofiadm -c crypto_algorithm [-b block_size] [-u user:group]
+ -a file | -r [device]
- /usr/sbin/lofiadm -c crypto_algorithm -l [-b block_size] [-u user:group] -a file
+ /usr/sbin/lofiadm -c crypto_algorithm -l [-b block_size] [-u user:group]
+ -a file
- /usr/sbin/lofiadm -c crypto_algorithm -l [-b block_size] [-u user:group] -r file [device]
+ /usr/sbin/lofiadm -c crypto_algorithm -l [-b block_size] [-u user:group]
+ -r file [device]
/usr/sbin/lofiadm -c crypto_algorithm -k raw_key_file
@@ -58,10 +61,12 @@
-l [-b block_size] [-u user:group] -r file [device]
- /usr/sbin/lofiadm -c crypto_algorithm -e [-b block_size] [-u user:group] -a file [device]
+ /usr/sbin/lofiadm -c crypto_algorithm -e [-b block_size] [-u user:group]
+ -a file [device]
- /usr/sbin/lofiadm -c crypto_algorithm -e -l [-b block_size] [-u user:group] -a file
+ /usr/sbin/lofiadm -c crypto_algorithm -e -l [-b block_size]
+ [-u user:group] -a file
/usr/sbin/lofiadm -C algorithm [-s segment_size] file
@@ -331,7 +336,7 @@
This example mounts an existing CD-ROM image (sparc.iso), of the Red
Hat 6.0 CD which was downloaded from the Internet. It was created with
- the mkisofs utility from the Internet.
+ the mkisofs utility.
@@ -420,7 +419,7 @@
Making a UFS filesystem on a file can be useful, particularly if a test
suite requires a scratch filesystem. It can be painful (or annoying) to
have to repartition a disk just for the test suite, but you do not have
- to. You can newfs a file with lofi
+ to. You can newfs a file with lofi.
@@ -475,7 +474,13 @@
# mkfile 10M /export/test/testfs
# lofiadm -a /export/test/testfs
/dev/lofi/1
- Note use of rlofi, not lofi, in following command.
+
+
+
+
+ Note use of rlofi, not lofi, in the following command.
+
+
# mkfs -F pcfs -o nofdisk,size=20480 /dev/rlofi/1
Construct a new FAT file system on /dev/rlofi/1: (y/n)? y
# mount -F pcfs /dev/lofi/1 /mnt
@@ -551,10 +556,8 @@
# lofiadm -c aes-256-cbc -a /export/home/secrets
- Enter passphrase: My-M0th3r;l0v3s_m3+4lw4ys! (
- not echoed)
- Re-enter passphrase: My-M0th3r;l0v3s_m3+4lw4ys! (
- not echoed)
+ Enter passphrase: My-M0th3r;l0v3s_m3+4lw4ys! [not echoed]
+ Re-enter passphrase: My-M0th3r;l0v3s_m3+4lw4ys! [not echoed]
/dev/lofi/1
# newfs /dev/rlofi/1
@@ -597,8 +600,8 @@
# lofiadm -c blowfish-cbc -a /export/home/secrets
- Enter passphrase: mommy (not echoed)
- Re-enter passphrase: mommy (not echoed)
+ Enter passphrase: mommy [not echoed]
+ Re-enter passphrase: mommy [not echoed]
lofiadm: could not map file /root/lofi: Invalid argument
# lofiadm
Block Device File Options
@@ -736,20 +737,16 @@
ENVIRONMENT VARIABLES
See environ(7) for descriptions of the following environment variables
- that affect the execution of lofiadm: LC_CTYPE, LC_MESSAGES and
+ that affect the execution of lofiadm: LC_CTYPE, LC_MESSAGES, and
NLSPATH.
EXIT STATUS
The following exit values are returned:
- 0
-
- Successful completion.
-
+ 0 Successful completion.
- >0
- An error occurred.
+ >0 An error occurred.
ATTRIBUTES
@@ -796,4 +793,4 @@
The output of lofiadm (without arguments) might change in future re-
leases.
-Oracle Solaris 11.4 11 May 2021 lofiadm(8)
+Oracle Solaris 11.4 23 Jun 2025 lofiadm(8)
diff -NurbBw 11.4.81/man8/logadm.8 11.4.84/man8/logadm.8
--- 11.4.81/man8/logadm.8 2025-08-17 09:30:04.595638136 -0700
+++ 11.4.84/man8/logadm.8 2025-08-17 09:30:26.938196505 -0700
@@ -81,7 +81,7 @@
Three options control when old log files are expired, -A, -C, and -S.
These options expire the oldest log files until a particular condition
- or conditions are met. For example, the combination -C 5 and the -S
+ or conditions are met. For example, the combination of the -C 5 and -S
10m options expires old log files until there are no more than 5 of the
files and their combined disk usage is no more than 10 megabytes. If
none of these options are specified, the default expiration is -C 10
@@ -139,9 +139,9 @@
Rotate the log file by copying it and truncating the original log-
file to zero length, rather than renaming the file.
- This option cannot be used along with -o, -g or -m as the file per-
- missions need to match the owner of the original file being trun-
- cated.
+ This option cannot be used along with -o, -g, or -m as the file
+ permissions need to match the owner of the original file being
+ truncated.
-C count
@@ -275,7 +275,7 @@
Rotate a log file after the specified time period (period).
Specify period as a number followed by d for days, h for hours, w
- for weeks, m for months (30 days) or y for years. There are also
+ for weeks, m for months (30 days), or y for years. There are also
two special values for period: now and never. "-p now" forces log
rotation. "-p never" forces no log rotation.
@@ -707,4 +689,4 @@
reverts to the same behavior as in prior releases. That is, timestamps
are written to the configuration file.
-Oracle Solaris 11.4 28 Jun 2021 logadm(8)
+Oracle Solaris 11.4 23 Jun 2025 logadm(8)
diff -NurbBw 11.4.81/man8/metaset.8 11.4.84/man8/metaset.8
--- 11.4.81/man8/metaset.8 2025-08-17 09:30:04.641614683 -0700
+++ 11.4.84/man8/metaset.8 2025-08-17 09:30:26.985308972 -0700
@@ -543,16 +538,12 @@
-
-
The name of the disk set is relo-red. The names of the first and second
- hosts added to the set are red and blue, respectively. (The hostname
- is the nodename established by svc:/system/identity:node smf(7) ser-
- vice.) Adding the first host creates the disk set. A disk set can be
- created with just one host, with the second added later. The last host
- cannot be deleted until all of the drives within the set have been
- deleted.
-
+ hosts added to the set are red and blue, respectively. (The hostname is
+ the nodename established by svc:/system/identity:node smf(7) service.)
+ Adding the first host creates the disk set. A disk set can be created
+ with just one host, with the second added later. The last host cannot
+ be deleted until all of the drives within the set have been deleted.
Example 2 Adding Drives to a Disk Set
@@ -641,20 +621,18 @@
The following command defines a multi-owner disk set:
-
# metaset -s blue -M -a -h hahost1 hahost2
The name of the disk set is blue. The names of the first and second
- hosts added to the set are hahost1 and hahost2, respectively. The
- hostname is the nodename established by svc:/system/identity:node
- smf(7) service. Adding the first host creates the multi-owner disk set.
- A disk set can be created with just one host, with additional hosts
- added later. The last host cannot be deleted until all of the drives
- within the set have been deleted.
-
+ hosts added to the set are hahost1 and hahost2, respectively. The host-
+ name is the nodename established by svc:/system/identity:node smf(7)
+ service. Adding the first host creates the multi-owner disk set. A disk
+ set can be created with just one host, with additional hosts added
+ later. The last host cannot be deleted until all of the drives within
+ the set have been deleted.
FILES
/etc/lvm/md.tab
@@ -665,14 +643,10 @@
EXIT STATUS
The following exit values are returned:
- 0
-
- Successful completion.
-
+ 0 Successful completion.
- >0
- An error occurred.
+ >0 An error occurred.
ATTRIBUTES
@@ -699,4 +673,4 @@
and drives, requires all hosts in the set to be accessible from the
network.
-Oracle Solaris 11.4 11 May 2021 metaset(8)
+Oracle Solaris 11.4 23 Jun 2025 metaset(8)
diff -NurbBw 11.4.81/man8/metattach.8 11.4.84/man8/metattach.8
--- 11.4.81/man8/metattach.8 2025-08-17 09:30:04.683224529 -0700
+++ 11.4.84/man8/metattach.8 2025-08-17 09:30:27.031163845 -0700
@@ -126,7 +126,7 @@
-s setname Specify the name of the diskset on which the metattach
- command or the metadetach command works.. Using the -s
+ command or the metadetach command works. Using the -s
option causes the command to perform its administrative
function within the specified diskset. Without this op-
tion, the command performs its function on local
@@ -387,4 +353,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 11 May 2021 metattach(8)
+Oracle Solaris 11.4 23 Jun 2025 metattach(8)
diff -NurbBw 11.4.81/man8/mkfifo.8 11.4.84/man8/mkfifo.8
--- 11.4.81/man8/mkfifo.8 2025-08-17 09:30:04.717339038 -0700
+++ 11.4.84/man8/mkfifo.8 2025-08-17 09:30:27.068607227 -0700
@@ -19,9 +19,9 @@
The mkfifo utility calls the library routine mkfifo(3C), with the path
- argument is passed as the path argument from the command line, and mode
- is set to the equivalent of a=rw, modified by the current value of the
- file mode creation mask umask(1).
+ argument passed the path argument from the command line, and mode set
+ to the equivalent of a=rw, modified by the current value of the file
+ mode creation mask. See umask(1).
OPTIONS
The following option is supported:
@@ -29,7 +29,7 @@
-m mode Set the file permission bits of the newly-created FIFO to
the specified mode value. The mode option-argument will be
the same as the mode operand defined for the chmod(1) com-
- mand. In <symbolicmode> strings, the op characters + and -
+ mand. In symbolic mode strings, the op characters + and -
will be interpreted relative to an assumed initial mode of
a=rw.
@@ -37,7 +37,7 @@
OPERANDS
The following operand is supported:
- file A path name of the FIFO special file to be created.
+ path A path name of the FIFO special file to be created.
ENVIRONMENT VARIABLES
@@ -71,4 +71,4 @@
SEE ALSO
chmod(1), umask(1), mkfifo(3C), attributes(7), environ(7), standards(7)
-Oracle Solaris 11.4 4 Feb 2015 mkfifo(8)
+Oracle Solaris 11.4 23 Jun 2025 mkfifo(8)
diff -NurbBw 11.4.81/man8/mountall.8 11.4.84/man8/mountall.8
--- 11.4.81/man8/mountall.8 2025-08-17 09:30:04.752387110 -0700
+++ 11.4.84/man8/mountall.8 2025-08-17 09:30:27.102786344 -0700
@@ -52,12 +52,12 @@
mote-mounted from host.
- -k Use the fuser -k mount-point command. See the fuser(8) for
- details. The -k option sends the SIGKILL signal to each
- process using the file. As this option spawns kills for each
- process, the kill messages might not show up immediately.
- There is no guarantee that umountall unmounts busy file sys-
- tems, even if the -k option is specified.
+ -k Use the fuser -k mount-point command. See the fuser(8) man
+ page for details. The -k option sends the SIGKILL signal to
+ each process using the file. As this option spawns kills for
+ each process, the kill messages might not show up immedi-
+ ately. There is no guarantee that umountall unmounts busy
+ file systems, even if the -k option is specified.
-l Limit the action to local file systems.
@@ -126,4 +126,4 @@
At this time, NFS is the only remote file system supported by the -l,
-r, and -h options.
-Oracle Solaris 11.4 17 Dec 2008 mountall(8)
+Oracle Solaris 11.4 23 Jun 2025 mountall(8)
diff -NurbBw 11.4.81/man8/mvdir.8 11.4.84/man8/mvdir.8
--- 11.4.81/man8/mvdir.8 2025-08-17 09:30:04.785008101 -0700
+++ 11.4.84/man8/mvdir.8 2025-08-17 09:30:27.132270717 -0700
@@ -7,18 +7,17 @@
/usr/sbin/mvdir dirname name
DESCRIPTION
- mvdir moves directories within a file system. dirname must be a direc-
- tory. If name does not exist, it will be created as a directory. If
- name does exist, and is a directory, dirname will be created as
- name/dirname. dirname and name may not be on the same path; that is,
- one may not be subordinate to the other. For example:
-
+ mvdir moves directories. dirname must be a directory. If name does not
+ exist, it will be created as a directory. If name does exist, and is a
+ directory, dirname will be created as name/dirname. dirname and name
+ may not be on the same path; that is, one may not be subordinate to the
+ other. For example:
example% mvdir x/y x/z
- is legal, but
+ is legal, but
example% mvdir x/y x/y/z
@@ -55,4 +55,9 @@
SEE ALSO
mkdir(1), mv(1), attributes(7)
-Oracle Solaris 11.4 4 Feb 2015 mvdir(8)
+NOTES
+ The mvdir script is a historical compatibility relic that calls the mv
+ command to do the move. It is recommended that the mv command be called
+ directly, in preference to mvdir.
+
+Oracle Solaris 11.4 23 Jun 2025 mvdir(8)
diff -NurbBw 11.4.81/man8/pginfo.8 11.4.84/man8/pginfo.8
--- 11.4.81/man8/pginfo.8 2025-08-17 09:30:04.825323573 -0700
+++ 11.4.84/man8/pginfo.8 2025-08-17 09:30:27.173973285 -0700
@@ -109,9 +109,9 @@
Display the physical relationship that corresponds to a PGs. If a
PG has the same CPUs as the whole system, a processor core, or a
- chip, system, core, or chip will be displayed along with the cor-
- responding ID, as appropriate, after the sharing relationship of
- the PG in square brackets ("[]").
+ chip, system, core, or chip will be displayed along with the corre-
+ sponding ID, as appropriate, after the sharing relationship of the
+ PG in square brackets ("[]").
-r string1,string2,...
@@ -282,19 +281,13 @@
EXIT STATUS
- 0
-
- Successful completion.
-
-
- 1
+ 0 Successful completion.
- An error occurred.
+ 1 An error occurred.
- 2
- Invalid syntax.
+ 2 Invalid syntax.
ATTRIBUTES
@@ -315,4 +308,4 @@
SEE ALSO
attributes(7), pgstat(8)
-Oracle Solaris 11.4 04 May 2016 pginfo(8)
+Oracle Solaris 11.4 23 Jun 2025 pginfo(8)
diff -NurbBw 11.4.81/man8/poweradm.8 11.4.84/man8/poweradm.8
--- 11.4.81/man8/poweradm.8 2025-08-17 09:30:04.866534025 -0700
+++ 11.4.84/man8/poweradm.8 2025-08-17 09:30:27.213416088 -0700
@@ -56,12 +56,12 @@
- ...with platform as the default value. The significance of this prop-
- erty is the source of administrative control for power management
- within the Solaris kernel. That is, this property indicates the origin
- of time-to-full-capacity and time-to-minimum-responsiveness settings
- within the Solaris kernel. Only a Solaris user with appropriate privi-
- leges can set this property.
+ The default value is platform. The significance of this property is the
+ source of administrative control for power management within the So-
+ laris kernel. That is, this property indicates the origin of time-to-
+ full-capacity and time-to-minimum-responsiveness settings within the
+ Solaris kernel. Only a Solaris user with appropriate privileges can set
+ this property.
When the administrative-authority is set to platform the values of
@@ -79,12 +79,12 @@
When the administrative-authority is set to smf, the values of time-to-
full-capacity and time-to-minimum-responsiveness will be taken from
SMF. As these values in SMF are changed by the Solaris administrator,
- so they will be applied to the kernel. Setting these values in the
- platform will have no effect upon the values in the kernel while admin-
- istrative-authority is set to smf. Under this condition, the poweradm
+ they will be applied to the kernel. Setting these values in the plat-
+ form will have no effect upon the values in the kernel while adminis-
+ trative-authority is set to smf. Under this condition, the poweradm
command will indicate that the kernel is currently using the values
- from SMF. As these values are changed by the Solaris administrator, so
- they will be modified in kernel.
+ from SMF. As these values are changed by the Solaris administrator,
+ they will be modified in the kernel.
When the administrative-authority is set to none, power management
@@ -105,7 +105,8 @@
This parameter defines the maximum time the system is allowed to
reach (re-provision and make available) its full capacity, return-
ing from any lower-capacity/less-responsive state, while it has
- been using any or all of the PM features falling within this bound.
+ been using any or all of the power management features falling
+ within this bound.
By default, this value is taken from the platform (for example,
i86pc), because the default setting for administrative-authority is
@@ -196,7 +197,7 @@
specified then current is assumed.
The administrative-authority and suspend-enable properties do not
- have a platform value
+ have a platform value.
set property=value...
@@ -379,19 +380,13 @@
EXIT STATUS
- 0
+ 0 Successful completion.
- Successful completion.
+ 1 An error occurred.
- 1
- An error occurred.
-
-
- 2
-
- Invalid command line options were specified.
+ 2 Invalid command line options were specified.
ATTRIBUTES
@@ -453,8 +448,8 @@
To set properties in the active_config and suspend property groups, the
solaris.smf.value.power_config authorization is required. To set prop-
- erties in the active_control property group requires the so-
+ erties in the active_control property group the so-
laris.smf.value.power_control authorization is required. Both of these
authorizations are part of the Maintenance and Repair profile.
-Oracle Solaris 11.4 27 Nov 2017 poweradm(8)
+Oracle Solaris 11.4 23 Jun 2025 poweradm(8)
diff -NurbBw 11.4.81/man8/projmod.8 11.4.84/man8/projmod.8
--- 11.4.81/man8/projmod.8 2025-08-17 09:30:04.904322853 -0700
+++ 11.4.84/man8/projmod.8 2025-08-17 09:30:27.251910573 -0700
@@ -21,119 +21,116 @@
OPTIONS
The following options are supported:
- -A Apply the project's resource controls, as
- defined in the system's project database,
- to the project if it is active.
-
-
- -a Specify that the users, groups, attrib-
- utes, or attribute values specified by the
- -U, -G or -K options should be added to
- the project, rather than replacing the ex-
- isting member or attribute list.
-
-
- -c comment Specify comment as a text string. Gener-
- ally, comment contains a short description
- of the project. This information is stored
- in the project's /etc/project entry.
-
-
- -f filename | - Specify the project file to modify or val-
- idate or specify input from stdin for val-
- idation. As noted under OPERANDS, if you
- do not specify a project in a projmod com-
- mand line, projmod validates the argument
- to -f. If you do not use this option, the
- system project file, /etc/project, is mod-
- ified.
-
-
- -G group [,group...] Specify a replacement list of member
- groups of the project. When used in con-
- junction with the -a or -r options, this
- option specifies a list of groups to be
- added or removed from the project.
-
-
- -K name[=value[,value...] Specify a replacement list of project at-
- tributes for the project. When used in
- conjunction with the -a, -r, or -s op-
- tions, this option specifies a list of at-
- tribute values to be added, removed, or
- replaced in the project. Attributes must
- be delimited by semicolons (;). Multiple
- -K options can be specified to set, add,
- remove, or substitute values on multiple
- keys, such as:
+ -A
+
+ Apply the project's resource controls, as defined in the system's
+ project database, to the project if it is active.
+
+
+ -a
+
+ Specify that the users, groups, attributes, or attribute values
+ specified by the -U, -G, or -K options should be added to the
+ project, rather than replacing the existing member or attribute
+ list.
+
+
+ -c comment
+
+ Specify comment as a text string. Generally, comment contains a
+ short description of the project. This information is stored in the
+ project's /etc/project entry.
+
+
+ -f filename | -
+
+ Specify the project file to modify or validate or specify input
+ from stdin for validation. As noted under OPERANDS, if you do not
+ specify a project in a projmod command line, projmod validates the
+ argument to -f. If you do not use this option, the system project
+ file, /etc/project, is modified.
+
+
+ -G group [,group...]
+
+ Specify a replacement list of member groups of the project. When
+ used in conjunction with the -a or -r options, this option speci-
+ fies a list of groups to be added or removed from the project.
+
+
+ -K name[=value[,value...]
+
+ Specify a replacement list of project attributes for the project.
+ When used in conjunction with the -a, -r, or -s options, this op-
+ tion specifies a list of attribute values to be added, removed, or
+ replaced in the project. Attributes must be delimited by semicolons
+ (;). Multiple -K options can be specified to set, add, remove, or
+ substitute values on multiple keys, such as:
-K key1=value1 -K "key2=(value2a),(value2b)"
- Resource control attributes use parenthe-
- ses to specify values for a key. Because
- many user shells interpret parentheses as
- special characters, it is best to enclose
- an argument to -K that contains parenthe-
- ses with double quotes, as shown above and
- in EXAMPLES, below. See resource-con-
- trols(7) for a description of the resource
+ Resource control attributes use parentheses to specify values for a
+ key. Because many user shells interpret parentheses as special
+ characters, it is best to enclose an argument to -K that contains
+ parentheses with double quotes, as shown above and in EXAMPLES, be-
+ low. See resource-controls(7) for a description of the resource
controls you can specify for a project.
- -l new_projectname Specify the new project name for the
- project. The new_projectname argument is a
- string consisting of characters from the
- set of alphabetic characters, numeric
- characters, period (.), underline (_), and
- hyphen (-). The first character should be
- alphabetic. An error message is written if
- these restrictions are not met. The
- project name must also be unique within
- the project file.
-
-
- -n Syntax check. Check the format of the ex-
- isting system project file and modifica-
- tions only. The contents of the existing
- project file, such as user names, group
- names, and resources that are specified in
- the project attributes are not checked.
-
-
- -o This option allows the project ID speci-
- fied by the -p option to be non-unique
- within the project file.
-
-
- -p projid Specify a new project ID for the project.
- It must be a non-negative decimal integer
- less than MAXUID as defined in param.h.
- This value must be unique within the
- project file if the -o option is not spec-
- ified.
-
-
- -r Specify that the users, groups, attrib-
- utes, or attribute values specified by the
- -U, -G or -K options should be removed
- from the project, rather than replacing
- the existing member or attribute list.
-
-
- -s Specify that the list of attributes speci-
- fied by the -K option should have their
- values replaced. If the attributes do not
- exist, they are added as if the a option
- was used. This option has no effect the -U
- or -G options.
-
-
- -U user [,user...] Specify a replacement list of member users
- of the project. When used in conjunction
- with the -a or -r options, this option
- specifies a list of users to be added or
- removed from the project.
+ -l new_projectname
+
+ Specify the new project name for the project. The new_projectname
+ argument is a string consisting of characters from the set of al-
+ phabetic characters, numeric characters, period (.), underline (_),
+ and hyphen (-). The first character should be alphabetic. An error
+ message is written if these restrictions are not met. The project
+ name must also be unique within the project file.
+
+
+ -n
+
+ Syntax check. Check the format of the existing system project file
+ and modifications only. The contents of the existing project file,
+ such as user names, group names, and resources that are specified
+ in the project attributes are not checked.
+
+
+ -o
+
+ This option allows the project ID specified by the -p option to be
+ non-unique within the project file.
+
+
+ -p projid
+
+ Specify a new project ID for the project. It must be a non-negative
+ decimal integer less than MAXUID as defined in param.h. This value
+ must be unique within the project file if the -o option is not
+ specified.
+
+
+ -r
+
+ Specify that the users, groups, attributes, or attribute values
+ specified by the -U, -G, or -K options should be removed from the
+ project, rather than replacing the existing member or attribute
+ list.
+
+
+ -s
+
+ Specify that the list of attributes specified by the -K option
+ should have their values replaced. If the attributes do not exist,
+ they are added as if the a option was used. This option has no ef-
+ fect on the -U or -G options.
+
+
+ -U user [,user...]
+
+ Specify a replacement list of member users of the project. When
+ used in conjunction with the -a or -r options, this option speci-
+ fies a list of users to be added or removed from the project.
OPERANDS
@@ -390,4 +387,4 @@
projmod verifies the uniqueness of project name and project ID against
the external name service.
-Oracle Solaris 11.4 6 Oct 2022 projmod(8)
+Oracle Solaris 11.4 23 Jun 2025 projmod(8)
diff -NurbBw 11.4.81/man8/prtdiag.8 11.4.84/man8/prtdiag.8
--- 11.4.81/man8/prtdiag.8 2025-08-17 09:30:04.939741553 -0700
+++ 11.4.84/man8/prtdiag.8 2025-08-17 09:30:27.285324491 -0700
@@ -72,4 +72,4 @@
platform, and therefore cannot be displayed by prtdiag. On those plat-
forms, further information can be obtained from the System Controller.
-Oracle Solaris 11.4 27 Nov 2017 prtdiag(8)
+Oracle Solaris 11.4 23 Jun 2025 prtdiag(8)
diff -NurbBw 11.4.81/man8/psrinfo.8 11.4.84/man8/psrinfo.8
--- 11.4.81/man8/psrinfo.8 2025-08-17 09:30:04.973317687 -0700
+++ 11.4.84/man8/psrinfo.8 2025-08-17 09:30:27.320589663 -0700
@@ -28,57 +28,60 @@
OPTIONS
The following options are supported:
- -s processor_id Silent mode. Displays 1 if the specified processor
- is fully on-line. Displays 0 if the specified
- processor is non-interruptible, spare, off-line,
- faulted or powered off.
+ -s processor_id
+
+ Silent mode. Displays 1 if the specified processor is fully on-
+ line. Displays 0 if the specified processor is non-interruptible,
+ spare, off-line, faulted, or powered off.
Use silent mode when using psrinfo in shell scripts.
- -p Display the number of physical processors in a sys-
- tem.
+ -p
+
+ Display the number of physical processors in a system.
+
+ When combined with the -v option, reports additional information
+ about the physical layout of the physical processor. The additional
+ information also gives which virtual CPUs are contained in a
+ processor socket or core. Typically, a physical processor plugs
+ into a socket and socket is often used to refer to a physical
+ processor. Each physical processor usually contains some number of
+ cores which each contain one or more virtual CPUs that can each ex-
+ ecute instructions.
+
+ These physical groupings of virtual CPUs may have some performance
+ relevant shared hardware components such as execution pipeline,
+ FPU, cache, or pipe to memory. However, these performance relevant
+ shared hardware components may not necessarily be inferred across
+ different physical processors. Also, one cannot necessarily infer
+ which CPUs are in a Non Uniform Memory Access (NUMA) node from
+ physical groupings. To see the NUMA configuration, refer to the
+ lgrpinfo(1) man page. For more information, see the pginfo(8) man
+ page.
+
+
+ -v
+
+ Verbose mode. Displays additional information about the specified
+ processors, including: processor type, floating point unit type and
+ clock speed. If any of this information cannot be determined,
+ psrinfo displays unknown.
+
+ When combined with the -p option, reports additional information
+ about each physical processor.
- When combined with the -v option, reports additional
- information about the physical layout of the physi-
- cal processor. The additional information also gives
- which virtual CPUs are contained in a processor
- socket or core. Typically, a physical processor
- plugs into a socket and socket is often used to re-
- fer to a physical processor. Each physical processor
- usually contains some number of cores which each
- contain one or more virtual CPUs that can each exe-
- cute instructions.
-
- These physical groupings of virtual CPUs may have
- some performance relevant shared hardware components
- such as execution pipeline, FPU, cache, or pipe to
- memory. However, these performance relevant shared
- hardware components may not necessarily be inferred
- across different physical processors. Also, one can-
- not necessarily infer which CPUs are in a Non Uni-
- form Memory Access (NUMA) node from physical group-
- ings. To see the NUMA configuration, refer to the
- lgrpinfo(1) man page. For more information, see the
- pginfo(8) man page.
-
-
- -v Verbose mode. Displays additional information about
- the specified processors, including: processor type,
- floating point unit type and clock speed. If any of
- this information cannot be determined, psrinfo dis-
- plays unknown.
-
- When combined with the -p option, reports additional
- information about each physical processor.
+ -t
- -t Tree mode. Displays a tree of the system's proces-
- sors and their associated socket, core, and cpu ids.
+ Tree mode. Displays a tree of the system's processors and their as-
+ sociated socket, core, and cpu ids.
- -L Locality group mode. Annotates output with lgroup
- membership information. Must be used with -t option.
+ -L
+
+ Locality group mode. Annotates output with lgroup membership infor-
+ mation. Must be used with -t option.
OPERANDS
@@ -133,7 +134,7 @@
the number of physical processors in the system:
- > psrinfo -p
+ % psrinfo -p
8
@@ -142,12 +143,10 @@
psrinfo also accepts command line arguments (processor IDs):
-
-
- > psrinfo -p 0 512 # IDs 0 and 512 exist on the
+ % psrinfo -p 0 512 # IDs 0 and 512 exist on the
1 # same physical processor
- > psrinfo -p 0 1 # IDs 0 and 1 exist on different
+ % psrinfo -p 0 1 # IDs 0 and 1 exist on different
2 # physical processors
@@ -189,4 +185,4 @@
The specified processor does not exist.
-Oracle Solaris 11.4 27 Sept 2016 psrinfo(8)
+Oracle Solaris 11.4 23 Jun 2025 psrinfo(8)
diff -NurbBw 11.4.81/man8/reboot.8 11.4.84/man8/reboot.8
--- 11.4.81/man8/reboot.8 2025-08-17 09:30:05.008025831 -0700
+++ 11.4.84/man8/reboot.8 2025-08-17 09:30:27.358634931 -0700
@@ -4,19 +4,41 @@
reboot - restart the operating system
SYNOPSIS
- /usr/sbin/reboot [-dlnq] [-c comment] [-f | -p] [boot_arguments]
+ /usr/sbin/reboot [-c comment] [-f [-e environment] | -p] [-dlnq]
+ [boot_arguments]
+DESCRIPTION
+ The reboot utility restarts the system.
- /usr/sbin/reboot [-c comment] [-f [-e environment] | -p] [-dlnq] [boot_arguments]
-DESCRIPTION
- The reboot utility restarts the kernel. The kernel is loaded into mem-
- ory by the PROM monitor, which transfers control to the loaded kernel.
+ Oracle Solaris supports two methods of reboot:
+
+ PROM
+
+ The kernel transfers control to the PROM monitor, firmware, or hy-
+ pervisor, which loads the next kernel into memory and then trans-
+ fers control to the loaded kernel. This is the same method used
+ when initially powering up a system.
+
+
+ Fast
+
+ The running kernel loads the next kernel into memory, and then
+ transfers control to the newly loaded kernel directly, bypassing
+ the PROM, firmware, or hypervisor. This has the potential to run
+ much more quickly than a PROM boot, and minimizes downtime. Note
+ that the system may fall back to PROM reboot if fast reboot is not
+ possible. The most common reason for such a fall back is a driver
+ failing to quiesce a hardware device in preparation for a fast re-
+ boot. See quiesce(9e).
- When the -f flag is specified, the running kernel will load the next
- kernel into memory, then transfer control to the newly loaded kernel.
- This form of reboot is shown in the second synopsis, above.
+
+ The default method of reboot is controlled on a per-system basis by the
+ config/fastreboot_default property of the svc:/system/boot-config:de-
+ fault SMF service. The -p or -f option can be used to override the sys-
+ tem default, and explicitly specify which reboot method is to be used
+ for the reboot initiated by this command.
Although reboot can be run at any time, shutdown(8) is normally used
@@ -74,6 +96,8 @@
See EXAMPLES for details.
+ The -p and -f options are mutually exclusive.
+
-l
@@ -93,8 +117,8 @@
Reboot to prom. This flag can be used to reboot the system through
firmware without changing the default reboot behavior as denoted by
- the config/fastreboot_default property setting in system/boot-con-
- fig service.
+ the config/fastreboot_default property setting in the system/boot-
+ config service.
The -p and -f options are mutually exclusive.
@@ -150,8 +174,9 @@
- If the service svc:/system/boot-config:default is enabled and property
- config/fastreboot_default is set to true, the -f option can be omitted.
+ If the service svc:/system/boot-config:default is enabled and the prop-
+ erty config/fastreboot_default is set to true, the -f option can be
+ omitted.
@@ -225,7 +250,7 @@
example# svcadm refresh svc:/system/boot-config:default
- Example 4 Rebooting to a Particular GRUB Menu
+ Example 4 Rebooting to a Particular GRUB Menu Entry
@@ -263,7 +288,11 @@
SEE ALSO
mdb(1), sync(2), uadmin(2), reboot(3C), wtmpx(5), attributes(7),
grub(7), boot(8), bootadm(8), dumpadm(8), halt(8), init(8), kernel(8),
- shutdown(8), svcadm(8), svccfg(8), sync(8), syslogd(8)
+ shutdown(8), svcadm(8), svccfg(8), sync(8), sysadm(8), syslogd(8)
+
+
+ Rebooting a System in Booting and Shutting Down Oracle Solaris 11.4
+ Systems
NOTES
The reboot utility does not execute the scripts in /etc/rcnum.d or exe-
@@ -275,4 +304,9 @@
System services managed by SMF are shutdown in reverse dependency or-
der.
-Oracle Solaris 11.4 16 Dec 2022 reboot(8)
+
+ Reboot may be blocked if an admin has used sysadm(8) to place the sys-
+ tem into a noreboot maintenance mode, or if the config/noreboot prop-
+ erty is set to true on the svc:/system/boot-config SMF service.
+
+Oracle Solaris 11.4 23 Jun 2025 reboot(8)
diff -NurbBw 11.4.81/man8/rmt.8 11.4.84/man8/rmt.8
--- 11.4.81/man8/rmt.8 2025-08-17 09:30:05.046427050 -0700
+++ 11.4.84/man8/rmt.8 2025-08-17 09:30:27.394721683 -0700
@@ -18,8 +18,9 @@
indication. All responses are in ASCII and in one of two forms. Suc-
cessful commands have responses of:
- Anumber\n where number is an ASCII representation of a decimal
- number.
+ Anumber\n
+
+ where number is an ASCII representation of a decimal number.
@@ -28,58 +29,62 @@
Eerror-number\nerror-message\n
where error-number is one of the possible error numbers described
- in intro(3), and error-message is the corresponding error string as
+ in Intro(3), and error-message is the corresponding error string as
printed from a call to perror(3C).
The protocol consists of the following commands:
- S\n Return the status of the open device, as ob-
- tained with a MTIOCGET ioctl call. If the
- operation was successful, an "ack" is sent
- with the size of the status buffer, then the
- status buffer is sent (in binary).
-
-
- Cdevice\n Close the currently open device. The device
- specified is ignored.
-
-
- Ioperation\ncount\n Perform a MTIOCOP ioctl(2) command using the
- specified parameters. The parameters are in-
- terpreted as the ASCII representations of the
- decimal values to place in the mt_op and
- mt_count fields of the structure used in the
- ioctl call. When the operation is successful
+ S\n
+
+ Return the status of the open device, as obtained with a MTIOCGET
+ ioctl(2) call. If the operation was successful, an "ack" is sent
+ with the size of the status buffer, then the status buffer is sent
+ (in binary).
+
+
+ Cdevice\n
+
+ Close the currently open device. The device specified is ignored.
+
+
+ Ioperation\ncount\n
+
+ Perform a MTIOCOP ioctl(2) command using the specified parameters.
+ The parameters are interpreted as the ASCII representations of the
+ decimal values to place in the mt_op and mt_count fields of the
+ structure used in the ioctl call. When the operation is successful
the return value is the count parameter.
- Loffset\nwhence\n Perform an lseek(2) operation using the spec-
- ified parameters. The response value is re-
- turned from the lseek call.
-
-
- Odevice\nmode\n Open the specified device using the indicated
- mode. device is a full pathname, and mode is
- an ASCII representation of a decimal number
- suitable for passing to open(9E). If a device
- is already open, it is closed before a new
- open is performed.
-
-
- Rcount\n Read count bytes of data from the open de-
- vice. rmt performs the requested read(9E) and
- responds with Acount-read\n if the read was
- successful; otherwise an error in standard
- format is returned. If the read was success-
- ful, the data read is sent.
-
-
- Wcount\n Write data onto the open device. rmt reads
- count bytes from the connection, aborting if
- a premature EOF is encountered. The response
- value is returned from the write(9E) call.
+ Loffset\nwhence\n
+
+ Perform an lseek(2) operation using the specified parameters. The
+ response value is returned from the lseek call.
+
+
+ Odevice\nmode\n
+
+ Open the specified device using the indicated mode. device is a
+ full pathname, and mode is an ASCII representation of a decimal
+ number suitable for passing to open(9E). If a device is already
+ open, it is closed before a new open is performed.
+
+
+ Rcount\n
+
+ Read count bytes of data from the open device. rmt performs the re-
+ quested read(9E) and responds with Acount-read\n if the read was
+ successful; otherwise an error in standard format is returned. If
+ the read was successful, the data read is sent.
+
+
+ Wcount\n
+
+ Write data onto the open device. rmt reads count bytes from the
+ connection, aborting if a premature EOF is encountered. The re-
+ sponse value is returned from the write(9E) call.
@@ -96,7 +101,7 @@
SEE ALSO
- ioctl(2), lseek(2), intro(3), perror(3C), rcmd(3C), rexec(3C),
+ ioctl(2), lseek(2), Intro(3), perror(3C), rcmd(3C), rexec(3C),
mtio(4I), attributes(7), ufsdump(8), ufsrestore(8), open(9E), read(9E),
write(9E)
@@ -106,4 +111,4 @@
BUGS
Do not use this for a remote file access protocol.
-Oracle Solaris 11.4 19 Sep 2016 rmt(8)
+Oracle Solaris 11.4 23 Jun 2025 rmt(8)
diff -NurbBw 11.4.81/man8/sar.8 11.4.84/man8/sar.8
--- 11.4.81/man8/sar.8 2025-08-17 09:30:05.080249956 -0700
+++ 11.4.84/man8/sar.8 2025-08-17 09:30:27.428030751 -0700
@@ -65,17 +63,10 @@
/var/spool/cron/crontabs/sys will report important activities hourly
during the working day:
-
-
5 18 * * 1-5 /usr/lib/sa/sa2 -s 8:00 -e 18:01 -i 1200 -A
FILES
- /tmp/sa.adrfl
-
- address file
-
-
/var/adm/sa/sadd
daily data file
@@ -123,4 +114,4 @@
ways, including the System Web Interface. See the Using Oracle Solaris
11.4 StatsStore and System Web Interface book for more information.
-Oracle Solaris 11.4 14 Aug 2020 sar(8)
+Oracle Solaris 11.4 23 Jun 2025 sar(8)
diff -NurbBw 11.4.81/man8/savecore.8 11.4.84/man8/savecore.8
--- 11.4.81/man8/savecore.8 2025-08-17 09:30:05.119562185 -0700
+++ 11.4.84/man8/savecore.8 2025-08-17 09:30:27.472434207 -0700
@@ -58,8 +58,9 @@
remain free on the file system containing directory. If after saving
the crash dump the file system containing directory would have less
free space the number of kilobytes specified in minfree, the crash dump
- is not saved. if the minfree file does not exist, savecore assumes a
- minfree value of 1 megabyte.
+ is not saved. If the minfree file does not exist, savecore assumes a
+ minfree value of 1 megabyte. Use the -m option to dumpadm(8) to set
+ this value.
The savecore utility also logs a reboot message using facility LOG_AUTH
@@ -100,6 +101,13 @@
dd(8) command.
+ -h
+
+ Display the output from the -z option in a more human readable for-
+ mat. The -h option is equivalent to using the --scale=max,1024 op-
+ tion.
+
+
-H
Omits the column headers.
@@ -134,7 +142,7 @@
-s section_list
- Selective extraction of sections from dump device. List of avail-
+ Selective extraction of sections from dump device. A list of avail-
able sections can be acquired using the -l option. By default all
available sections are extracted. Individual members of the list
are divided by comma character.
@@ -173,14 +181,8 @@
-z
- Size. It reads the dump file header and print the uncompressed size
- in bytes.
-
-
- -h
-
- Size with units. If used with -z option, it reads the dump file
- header and print the uncompressed size with units.
+ Display the uncompressed size from the dump file header. The size
+ is given in bytes unless modified with the -h or --scale options.
--scale[=item1,item2,...]
@@ -272,8 +274,8 @@
SEE ALSO
- mdb(1), svcs(1), syslog(3C), fma(3M), attributes(7), smf(7), dd(8),
- dumpadm(8), svcadm(8)
+ mdb(1), svcs(1), syslog(3C), fma(3M), attributes(7), scale(7), smf(7),
+ dd(8), dumpadm(8), svcadm(8)
NOTES
The system crash dump service is managed by the service management fa-
@@ -301,4 +303,4 @@
savecore process and wait for it to complete. In the latter case, re-
move the partial file and re-create it by running savecore -d.
-Oracle Solaris 11.4 28 July 2023 savecore(8)
+Oracle Solaris 11.4 23 Jun 2025 savecore(8)
diff -NurbBw 11.4.81/man8/share_smb.8 11.4.84/man8/share_smb.8
--- 11.4.81/man8/share_smb.8 2025-08-17 09:30:05.161973244 -0700
+++ 11.4.84/man8/share_smb.8 2025-08-17 09:30:27.518905008 -0700
@@ -8,10 +8,10 @@
pathname sharename | [-A]]
- zfs set share.smb=on | off filesystem|filesystem%share
+ zfs set share.smb={on | off} filesystem|filesystem%share
- zfs share -o share.smb=on | off specific_options
+ zfs share -o share.smb={on | off} specific_options
filesystem|filesystem%share
DESCRIPTION
@@ -69,14 +69,10 @@
false or not defined, ABE filtering will not be performed on this
share. This property is not defined by default.
- false
+ false Disable ABE for this share.
- Disable ABE for this share.
-
- true
-
- Enable ABE for this share.
+ true Enable ABE for this share.
@@ -92,13 +88,17 @@
tainer:
- $ share -F smb -o abe=true,ad-container=cn=sales,ou=mycompany,dc=com /export/home
+ $ share -F smb \
+ -o abe=true,ad-container=cn=sales,ou=mycompany,dc=com \
+ /export/home
The following example uses the zfs share command to specify the AD
container:
- $ zfs share -o share.smb=on -o share.smb.ad-container=cn=sales,ou=mycompany,dc=com -o share.smb.abe=on rpool/export/home%share1
+ $ zfs share -o share.smb=on \
+ -o share.smb.ad-container=cn=sales,ou=mycompany,dc=com \
+ -o share.smb.abe=on rpool/export/home%share1
@@ -167,7 +167,7 @@
cont_avail=boolean
- The new cont_avail property can take one of the following values:
+ The cont_avail property can take one of the following values:
true Enables continuous availability for this share
@@ -178,7 +178,8 @@
The following command shows how to use the zfs share command to
specify the cont_avail property:
- # zfs share -o share.smb=on -o share.smb.cont_avail=true tank/home%hsr
+ # zfs share -o share.smb=on -o share.smb.cont_avail=true \
+ tank/home%hsr
@@ -188,28 +189,26 @@
caching is a client feature and offline files are managed entirely
by the clients.
-
The following are valid values for the csc property:
- o manual - Clients are permitted to cache files from the
- specified share for offline use as requested by users.
- However, automatic file-by-file reintegration is not
- permitted. manual is the default value.
+ manual Clients are permitted to cache files from the specified
+ share for offline use as requested by users. However,
+ automatic file-by-file reintegration is not permitted.
+ manual is the default value.
- o auto - Clients are permitted to automatically cache
- files from the specified share for offline use and file-
- by-file reintegration is permitted.
+ auto Clients are permitted to automatically cache files from
+ the specified share for offline use and file-by-file
+ reintegration is permitted.
- o vdo - Clients are permitted to automatically cache
- files from the specified share for offline use, file-by-
- file reintegration is permitted, and clients are permit-
- ted to work from their local cache even while offline.
+ vdo Clients are permitted to automatically cache files from
+ the specified share for offline use, file-by-file rein-
+ tegration is permitted, and clients are permitted to
+ work from their local cache even while offline.
- o disabled - Client-side caching is not permitted for
- this share.
+ disabled Client-side caching is not permitted for this share.
@@ -228,7 +227,7 @@
default value. When set to true, the SMB server requires the client
to encrypt all the requests for accessing the specific share.
Again, the enforcement can be bypassed if the server allows unen-
- crypted access. For more information, see the description about the
+ crypted access. For more information, see the description of the
server_reject_unencypt property. Note that when server_encrypt_data
is true, encrypt will not have any effect.
@@ -390,20 +389,23 @@
The following examples use the zfs share and share commands to create
and publish an SMB share.
- o The following example shows how to use the zfs share command
- to create and publish an SMB share that also enables guest
- access:
+
+
+ The following example shows how to use the zfs share command to create
+ and publish an SMB share that also enables guest access:
+
# zfs share -o share.smb=on -o share.smb.guestok=on tank/home%hshare
- o The following example shows how to use the share command to
- enable guest access on a share:
- # share -F smb -o guestok=true /tank/home
+ The following example shows how to use the share command to enable
+ guest access on a share:
+ # share -F smb -o guestok=true /tank/home
+
Example 2 Viewing the Share Properties
@@ -453,4 +455,4 @@
getnetbyname(3C), netgroup(5), attributes(7), idmap(8), share(8),
zfs(8), zfs_share(8)
-Oracle Solaris 11.4 20 July 2023 share_smb(8)
+Oracle Solaris 11.4 23 Jun 2025 share_smb(8)
diff -NurbBw 11.4.81/man8/shutdown.8 11.4.84/man8/shutdown.8
--- 11.4.81/man8/shutdown.8 2025-08-17 09:30:05.196239152 -0700
+++ 11.4.84/man8/shutdown.8 2025-08-17 09:30:27.552179769 -0700
@@ -38,7 +38,7 @@
The warning message and the user provided message are output when there
are 7200, 3600, 1800, 1200, 600, 300, 120, 60, and 30 seconds remaining
before shutdown begins. The user provided message (as much as will fit)
- is added to the wtmpx record generated init(8). See EXAMPLES.
+ is added to the wtmpx record generated by init(8). See EXAMPLES.
System state definitions are:
@@ -166,4 +166,9 @@
When you shut down an image, services are shut down in reverse depen-
dency order.
-Oracle Solaris 11.4 25 Aug 2023 shutdown(8)
+
+ Shutdown may be blocked if an admin has used sysadm(8) to place the
+ system into a noreboot maintenance mode, or if the config/noreboot
+ property is set to true on the svc:/system/boot-config SMF service.
+
+Oracle Solaris 11.4 23 Jun 2025 shutdown(8)
diff -NurbBw 11.4.81/man8/spliceadm.8 11.4.84/man8/spliceadm.8
--- 11.4.81/man8/spliceadm.8 2025-08-17 09:30:05.238227197 -0700
+++ 11.4.84/man8/spliceadm.8 2025-08-17 09:30:27.592603305 -0700
@@ -4,13 +4,20 @@
spliceadm - administer splice state
SYNOPSIS
- spliceadm status [-c] [[-p]-o <field1>,...] [all|<id>]
- spliceadm freeze [-qnN] [<id>]
+ spliceadm status [-c] [[-p] -o field1,...] [all|id]
+
+ spliceadm freeze [-qnN] [id]
+
spliceadm unfreeze [-qnN]
+
spliceadm sync [-L]
- spliceadm apply [-vL] <kid>
- spliceadm reverse [-vL] <kid>
+
+ spliceadm apply [-vL] kid
+
+ spliceadm reverse [-vL] kid
+
spliceadm clear
+
spliceadm log [-vDp]
DESCRIPTION
@@ -19,7 +26,7 @@
live system.
SUB-COMMANDS
- status [-c] [[-p]-o <field1>,...] [all|<id>]
+ status [-c] [[-p]-o field1,...] [all|id]
Shows the current state of all the installed splices or an individ-
ual splice.
@@ -44,19 +49,18 @@
the state of the svc:/system/splice:default service.
-
# spliceadm status -c
PROPERTY VALUE
version_lock off
service_state online
- The -p option produces machine parsable output in both the cases.
- The -o option allows to select what field(s) to be printed out.
- When parsable output (-p) is requested, the -o option is mandatory.
+ The -p option produces machine parsable output in both cases. The
+ -o option allows to select what field(s) to be printed out. When
+ parsable output (-p) is requested, the -o option is mandatory.
It is recommended for scripts to use the -p option. The -p option
will retry in a loop if the kernel resource is unavailable. Without
- the -p switch, status immediately returns a failure which is more
+ the -p switch, status immediately returns a failure, which is more
useful in the interactive case.
@@ -81,30 +83,29 @@
disk.
- excluded The splice is not applied because it has an <id>
+ excluded The splice is not applied because it has an id
larger than the version lock set on the system.
- faulted The splice is not applied because it has an <id>
- larger than the largest <id> that can be safely
+ faulted The splice is not applied because it has an id
+ larger than the largest id that can be safely
applied on the system.
- evaluating The splice is applied beyond the largest <id>
- that can be safely applied on the system. A
- splice is in this state after it is applied and
- before the timeout expires.
+ evaluating The splice is applied beyond the largest id that
+ can be safely applied on the system. A splice is
+ in this state after it is applied and before the
+ timeout expires.
pending-removal The splice is applied beyond the version lock.
This can happen when version lock is set to a
lower level by using spliceadm freeze with the
- "-N" switch.
-
+ -N option.
- freeze [-qnN] [<id>]
+ freeze [-qnN] [id]
Locks and brings the system to a specific splice version. When in-
voked with the -N option, the version lock is set, but the system
@@ -260,13 +257,13 @@
to stderr.
- apply [-vL] <kid>
+ apply [-vL] kid
- Applies a specific splice, as identified by <kid>. Version locks
- are honored when manually applying splices. Splices must be applied
- in increasing order.
+ Applies a specific splice, as identified by kid. Version locks are
+ honored when manually applying splices. Splices must be applied in
+ increasing order.
- If the <kid> of the splice being applied is higher than the splice
+ If the kid of the splice being applied is higher than the splice
level, then the system is locked and the splice is deemed to be ex-
cluded. Use the spliceadm unfreeze command to unlock the splice
level and apply the splice. For example:
@@ -272,17 +269,14 @@
level and apply the splice. For example:
-
# spliceadm apply 1003
Failed to apply splice 1003.
Use spliceadm unfreeze to allow this splice to be applied.
- If the <kid> of the splice being applied is higher than the largest
- <kid> that can safely run on the system, then the splice is deemed
- to be faulted. To apply the splice, use spliceadm
- clear command after fixing the problem with the
- splice. For example:
-
+ If the kid of the splice being applied is higher than the largest
+ kid that can safely run on the system, then the splice is deemed to
+ be faulted. To apply the splice, use the spliceadm clear command
+ after fixing the problem with the splice. For example:
# spliceadm apply 1003
@@ -302,11 +296,11 @@
The -v option prints verbose log to stderr.
- reverse [-vL] <kid>
+ reverse [-vL] kid
- Reverses a specific splice, as identified by <kid>. Splices must be
- reversed in decreasing order, from the one with the highest <kid>
- to the one with the lowest.
+ Reverses a specific splice, as identified by kid. Splices must be
+ reversed in decreasing order, from the one with the highest kid to
+ the one with the lowest.
Note that the reverse subcommand is intended for debugging and
testing purposes. Users should use the unfreeze and freeze subcom-
@@ -366,4 +359,4 @@
unfreeze command, and if constrained by the safety threshold, use the
spliceadm clear command.
-Oracle Solaris 11.4 27 Nov 2017 spliceadm(8)
+Oracle Solaris 11.4 23 Jun 2025 spliceadm(8)
diff -NurbBw 11.4.81/man8/sxadm.8 11.4.84/man8/sxadm.8
--- 11.4.81/man8/sxadm.8 2025-08-17 09:30:05.292487680 -0700
+++ 11.4.84/man8/sxadm.8 2025-08-17 09:30:27.643710548 -0700
@@ -370,6 +370,27 @@
ties.
+ RFDS_CLEAR - Register File Data Sampling
+
+ RFDS_CLEAR is a mitigation for the Register File Data Sampling
+ (RFDS) vulnerabilities found in Intel CPUs (CVE-2023-28746). The
+ mitigation will overwrite stale register values on the processors
+ that are affected by RFDS.
+
+ This mitigation is enabled by default on systems where it is re-
+ quired and supported.
+
+ A reboot is required after enabling or disabling RFDS_CLEAR for the
+ changes to take effect.
+
+
+ RFDS_NO - Register File Data Sampling Mitigation
+
+ RFDS_NO is a readonly extension that is only enabled if the CPU is
+ not vulnerable to Register File Data Sampling (RFDS) vulnerabili-
+ ties (CVE-2023-28746).
+
+
RDCL_NO - Rogue Data Cache Avoidance Mitigation
RDCL_NO is a readonly extension that is only enabled if the CPU is
@@ -702,6 +723,17 @@
executable settings.
+
+ To determine the tags for an individual executable use elfdump to dis-
+ play the dynamic section, and look for tags starting with SUNW_SX_, for
+ example:
+
+ $ elfdump -d /usr/bin/ssh | grep SUNW_SX_
+ [52] SUNW_SX_ASLR 0x2 ENABLE
+ [53] SUNW_SX_NXHEAP 0x2 ENABLE
+ [54] SUNW_SX_NXSTACK 0x2 ENABLE
+
+
SUB-COMMANDS
The sxadm command has the following subcommands.
@@ -936,7 +968,7 @@
SEE ALSO
- ld(1), exec(2), sx_enabled(3C), adi(7), attributes(7)
+ elfdump(1), ld(1), exec(2), sx_enabled(3C), adi(7), attributes(7)
Oracle ILOM Administrator's Guide for Configuration and Maintenance
@@ -955,6 +987,8 @@
+--------------------------------------------------+---------+
| EXTENSION |RELEASE |
+--------------------------------------------------+---------+
+ | RFDS_CLEAR, RFDS_NO |11.4.84 |
+ +--------------------------------------------------+---------+
| SBPB, SRSO_NO, SRSO_USER_KERNEL_NO |11.4.78 |
+--------------------------------------------------+---------+
| GDS, GDS_NO |11.4.68 |
@@ -1003,4 +1037,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 6 Jan 2025 sxadm(8)
+Oracle Solaris 11.4 17 Apr 2025 sxadm(8)
diff -NurbBw 11.4.81/man8/syncloop.8 11.4.84/man8/syncloop.8
--- 11.4.81/man8/syncloop.8 2025-08-17 09:30:05.330626084 -0700
+++ 11.4.84/man8/syncloop.8 2025-08-17 09:30:27.680212583 -0700
@@ -69,9 +66,9 @@
The options for syncloop are described in the following table:
Option Parameter Default Description
- -c packet_count 100 Specifies the number of
- packets to be sent in the
- multiple-packet phase.
+ -c packet_count 100 Specifies the number of pack-
+ ets to be sent in the multi-
+ ple-packet phase.
-d hex_data_byte random Specifies that each packet
will be filled with bytes
with the value of
@@ -114,8 +111,8 @@
All numeric options except -d are entered as decimal numbers (for exam-
- ple, -s 19200). If you do not provide the -ttest_type
- option, syncloop prompts for it.
+ ple, -s 19200). If you do not provide the -t test_type option, syn-
+ cloop prompts for it.
EXAMPLES
Example 1 A sample display of using the syncloop command.
@@ -206,4 +202,4 @@
normal operations, syncloop should only be run on a port that is not
being used for any other purpose at that time.
-Oracle Solaris 11.4 9 Mar 1993 syncloop(8)
+Oracle Solaris 11.4 23 Jun 2025 syncloop(8)
diff -NurbBw 11.4.81/man8/sysadm.8 11.4.84/man8/sysadm.8
--- 11.4.81/man8/sysadm.8 2025-08-17 09:30:05.373155318 -0700
+++ 11.4.84/man8/sysadm.8 2025-08-17 09:30:27.722859874 -0700
@@ -34,18 +34,18 @@
remove it from service.
- If software maintenance is being performed. The creation of Automated
+ If software maintenance is being performed, the creation of Automated
Service Requests (ASR) is prevented for software defects and alerts.
A noreboot maintenance prevents the system being rebooted by any use of
- the halt, reboot, uadmin, shutdown commands; but does not prevent sys-
- tem panic or cluster failover. A noreboot maintenance state in a zone
- does not prevent reboot of the host. If the system reboots due to panic
- or power loss then the noreboot maintenance will be reapplied on next
- boot. The system can be automatically placed in a noreboot maintenance
- state by setting the config/noreboot = true property on the svc:/sys-
- tem/boot-config SMF service.
+ the halt, init, reboot, uadmin, or shutdown commands; but does not pre-
+ vent system panic or cluster failover. A noreboot maintenance state in
+ a zone does not prevent reboot of the host. If the system reboots due
+ to panic or power loss then the noreboot maintenance will be reapplied
+ on next boot. The system can be automatically placed in a noreboot
+ maintenance state by setting the config/noreboot = true property on the
+ svc:/system/boot-config SMF service.
Maintenance state is held across host reboots and changes between dif-
@@ -57,42 +57,47 @@
Optionally, the host may be evacuated by migrating all solaris-kz, so-
- laris and solaris10 brand zones away from the system. A non-interactive
- RAD URI of the destination zones host must be given in the evacua-
+ laris, and solaris10 brand zones away from the system. A non-interac-
+ tive RAD URI of the destination zones host must be given in the evacua-
tion/target property of the zone instance. A default destination host
may also be specified on the zone service svc:/system/zones/zone.
SUB-COMMANDS
The following subcommands are supported:
+ sysadm maintain -s [ -t admin|noreboot|software ] [ -m message ]
+
+ Starts maintenance.
- sysadm maintain -s [ -t software|admin ] [ -m message ]
+ -m Provide a free-form message string.
- Starts maintenance.
+ -t Specify one of the following maintenance types:
- Optionally, you can use the -m option to specify a free-form message
- string.
+ admin
+ disables zone migration to this host, and zone boot and
+ attach on the host. This is the default type, and invok-
+ ing sysadm maintain -s with no option will set the type
+ to admin.
- Optionally, you can use the -t option to specify one of the following
- maintenance types:
- o admin disables zone migration to this host, and zone boot
- and attach on the host. This is the default type, and invok-
- ing sysadm maintain -s with no option will set the type to
- admin.
+ noreboot
+ prevents the system being rebooted by administrative com-
+ mands; but does not prevent system panic or cluster
+ failover.
- o software disables the logging of ASRs for any FMA defect or
- alert that is the result of a software problem.
+ software
+ disables the logging of ASRs for any FMA defect or alert
+ that is the result of a software problem.
- Either, both or no software maintenance types can be active at any
- time.
+ Either none, or any combination of these software maintenance types
+ can be active at any time.
Starting maintenance clears any existing evacuation state.
@@ -108,15 +112,14 @@
display. The field name must be one of the fields listed below,
or the special value all to display all fields.
-
TYPE The type of maintenance mode. Valid values are admin
(default), noreboot, and software.
- USER The user who sets the maintenance mode.
+ USER The user who set the maintenance mode.
- DATE The date when the maintenance mode is set.
+ DATE The date when the maintenance mode was set.
MESSAGE Any message associated with the maintenance mode.
@@ -376,19 +357,25 @@
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
- +-----------------------------------------+-----------------------------+
+ +------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
- +-----------------------------------------+-----------------------------+
+ +------------------------------+-----------------------------+
| Interface Stability | See below. |
- +-----------------------------------------+-----------------------------+
- | - CLI options | Committed |
- +-----------------------------------------+-----------------------------+
- | - Parsable output of sysadm evacuate -l | Committed |
- +-----------------------------------------+-----------------------------+
- | - Human readable and verbose output | Not-an-Interface |
- +-----------------------------------------+-----------------------------+
+ +------------------------------+-----------------------------+
| Availability | system/zones |
- +-----------------------------------------+-----------------------------+
+ +------------------------------+-----------------------------+
+
+
+ Interface Stability
+ +---------------------------------------+--------------------+
+ | INTERFACE | STABILITY LEVEL |
+ +---------------------------------------+--------------------+
+ | CLI options | Committed |
+ +---------------------------------------+--------------------+
+ | Parsable output of sysadm evacuate -l | Committed |
+ +---------------------------------------+--------------------+
+ | Human readable and verbose output | Not-an-Interface |
+ +---------------------------------------+--------------------+
SEE ALSO
@@ -417,4 +404,4 @@
The sysadm command was introduced in Oracle Solaris 11.4.0.
-Oracle Solaris 11.4 13 Sep 2024 sysadm(8)
+Oracle Solaris 11.4 23 Jun 2025 sysadm(8)
diff -NurbBw 11.4.81/man8/sysconfig.8 11.4.84/man8/sysconfig.8
--- 11.4.81/man8/sysconfig.8 2025-08-17 09:30:05.418505973 -0700
+++ 11.4.84/man8/sysconfig.8 2025-08-17 09:30:27.768325014 -0700
@@ -7,8 +7,8 @@
/usr/sbin/sysconfig
- /usr/sbin/sysconfig configure | reconfigure [-s]
- [-c config_profile.xml | dir] [--destructive] [-g grouping,grouping]
+ /usr/sbin/sysconfig configure | reconfigure [-s] [--destructive]
+ [-c config_profile.xml | dir] [-g grouping,grouping]
/usr/sbin/sysconfig unconfigure [-s] [--destructive]
@@ -76,8 +76,8 @@
ured systems. It is designed to provide system configuration for newly
created non-global zones and during text installation. If there is a
need to modify the configuration of an already configured system uti-
- lizing SCI tool, such a system has to be unconfigured first before SCI
- tool can run.
+ lizing the SCI tool, such a system has to be unconfigured first before
+ the SCI tool can run.
Besides using sysconfig to perform system configurations, individual
@@ -91,41 +91,38 @@
The following groupings are configurable.
-
- Grouping | Components | Unconfigured Stat
- ------------------------------------------------------------
+ | |
+ Grouping | Components | Unconfigured State
+ ----------------+---------------------------+----------------------------
identity | system nodename | unknown
- ------------------------------------------------------------
- keyboard | Keyboard | U.S. English
- ------------------------------------------------------------
- naming_services | DNS, NIS and LDAP | No network naming
- | clients, nsswitch | services
- ------------------------------------------------------------
+ ----------------+---------------------------+----------------------------
+ keyboard | keyboard | U.S. English
+ ----------------+---------------------------+----------------------------
+ naming_services | DNS, NIS, & LDAP clients, | No network naming services
+ | nsswitch |
+ ----------------+---------------------------+----------------------------
network | network | No network
- ------------------------------------------------------------
+ ----------------+---------------------------+----------------------------
location | timezone | UTC
| locale | C locale
- ------------------------------------------------------------
+ ----------------+---------------------------+----------------------------
support | ASR | ASR disabled
- ------------------------------------------------------------
- system | all groupings | all groupings
- | | unconfigured
- ------------------------------------------------------------
+ ----------------+---------------------------+----------------------------
+ system | all groupings | all groupings unconfigured
+ ----------------+---------------------------+----------------------------
users | root | Empty root password
| initial user account | Remove user account
- ------------------------------------------------------------
- The sysconfig utility makes use of the Solaris Management Facility
+ The sysconfig utility makes use of the Service Management Facility
(SMF) to centralize configuration information. The data generated by a
system configuration operation is an administrative customization to
the SMF repository stored by default at the sysconfig-profile layer of
- the SMF repository. When sysconfig configure -c <dir> is used, individ-
- ual profiles can be applied at the enterprise-profile, site-profile,
- and node-profile SMF layers by placing those profiles in the appropri-
- ate subdirectory within dir: <dir>/enterprise, <dir>/site, and
- <dir>/node.
+ the SMF repository. When sysconfig configure -c dir is used, individual
+ profiles can be applied at the enterprise-profile, site-profile, and
+ node-profile SMF layers by placing those profiles in the appropriate
+ subdirectory within dir: dir/enterprise, dir/site, and dir/node.
When sysconfig is used to configure the system, any values present in
@@ -137,7 +134,11 @@
This section describes supported subcommands and their associated op-
tions.
- unconfigure [-s] [-g grouping] [--destructive]
+
+
+ /usr/sbin/sysconfig unconfigure [-s] [--destructive]
+ [-g grouping,grouping]
+
Unconfigure a system and leave it in the unconfigured state.
@@ -163,7 +164,11 @@
- unconfigure [-s] [-g system] --remove-profiles
+
+
+ /usr/sbin/sysconfig unconfigure [-s] [-g system] [--destructive]
+ --remove-profiles
+
--remove-profiles
@@ -184,7 +189,7 @@
will be deleted.
Because this action is extensive, the removed XML profiles will
- be archived in a tar file named profiles-<timestamp>.tar in the
+ be archived in a tar file named profiles-timestamp.tar in the
/etc/svc/profile/backup directory.
This option is only valid with the system grouping. Using -g
@@ -192,8 +197,11 @@
- configure|reconfigure [-s] [-g grouping] [-c config_profile.xml | dir]
- [--destructive]
+
+
+ /usr/sbin/sysconfig configure | reconfigure [-s] [--destructive]
+ [-c config_profile.xml | dir] [-g grouping,grouping]
+
Configure or reconfigure a grouping. The configure subcommand has
access to the same options as the unconfigure subcommand. It also
@@ -214,8 +222,11 @@
- create-profile [-o output_directory] [-l logfile] [-v verbosity] [-b]
- [-g grouping,...]
+
+
+ /usr/sbin/sysconfig create-profile [-o output_directory] [-l logfile]
+ [-v verbosity] [-b] [-g grouping,grouping]
+
Run the SCI tool and create a system configuration profile. The de-
fault location for the profile is /system/volatile/profile/sc_pro-
@@ -271,7 +282,7 @@
# sysconfig unconfigure -g system
- Example 3 Reconfiguring System Using SCI Tool
+ Example 3 Reconfiguring the System Using the SCI Tool
@@ -300,7 +311,8 @@
# sysconfig create-profile -o /tmp/my_sysconfig_directory/
- # sysconfig configure -g system -c /tmp/my_sysconfig_directory/sc_profile.xml
+ # sysconfig configure -g system \
+ -c /tmp/my_sysconfig_directory/sc_profile.xml
Example 6 Configuring the System in a Zone
@@ -354,14 +366,10 @@
EXIT STATUS
- 0
-
- Success.
-
+ 0 Success.
- >0
- Failure.
+ >0 Failure.
ATTRIBUTES
@@ -371,11 +379,8 @@
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
| Availability |system/core-os |
- +------------------------------+-----------------------------+
| |system/install |
- +------------------------------+-----------------------------+
| |system/install/configuration |
- +------------------------------+-----------------------------+
| |system/library/install |
+------------------------------+-----------------------------+
| Interface Stability |Committed |
@@ -385,4 +390,4 @@
SEE ALSO
svcprop(1), attributes(7), attributes(7), svcadm(8), svccfg(8)
-Oracle Solaris 11.4 26 Mar 2020 sysconfig(8)
+Oracle Solaris 11.4 23 Jun 2025 sysconfig(8)
diff -NurbBw 11.4.81/man8/syslogd.8 11.4.84/man8/syslogd.8
--- 11.4.81/man8/syslogd.8 2025-08-17 09:30:05.454559843 -0700
+++ 11.4.84/man8/syslogd.8 2025-08-17 09:30:27.804047413 -0700
@@ -28,7 +28,7 @@
syslogd reads the configuration file when it starts up, and again when-
- ever it receives a HUP signal (see signal.h(3HEAD), at which time it
+ ever it receives a HUP signal (see signal.h(3HEAD)), at which time it
also closes all files it has open, re-reads its configuration file, and
then opens only the log files that are listed in that file. syslogd ex-
its when it receives a TERM signal.
@@ -234,7 +234,8 @@
SEE ALSO
logger(1), svcs(1), syslog(3C), signal.h(3HEAD), log(4D), sys-
- log.conf(5), attributes(7), smf(7), msgid(8), svcadm(8), svccfg(8)
+ log.conf(5), attributes(7), smf(7), msgid(8), rsyslogd(8), svcadm(8),
+ svccfg(8)
NOTES
The mark message is a system time stamp, and so it is only defined for
@@ -292,4 +293,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 8 Jan 2024 syslogd(8)
+Oracle Solaris 11.4 23 Jun 2025 syslogd(8)
diff -NurbBw 11.4.81/man8/sysobjadm.8 11.4.84/man8/sysobjadm.8
--- 11.4.81/man8/sysobjadm.8 2025-08-17 09:30:05.496343027 -0700
+++ 11.4.84/man8/sysobjadm.8 2025-08-17 09:30:27.843336933 -0700
@@ -16,9 +16,6 @@
/usr/sbin/sysobjadm [-R rootpath] dump [search]
- /usr/sbin/sysobjadm [-R rootpath] dump [class]
-
-
/usr/sbin/sysobjadm [-R rootpath] device-list [-P] [-I] [-i] [-a]
[-u uuid | -p path | -d driver]
@@ -28,7 +25,7 @@
/usr/sbin/sysobjadm [-R rootpath] device-set-instance
- -u uuid | -p path <instance>
+ -u uuid | -p path instance
DESCRIPTION
The sysobjadm command is the administrative command that interacts with
@@ -79,13 +73,13 @@
The backup file can be specified in two ways:
- o Through -f <file> for a non-standard backup file. For
- example, copied to a non-standard location by the system
+ o Through -f file for a non-standard backup file. For ex-
+ ample, copied to a non-standard location by the system
administrator.
- o Using the <name> parameter, which selects a file from
- the standard location.
+ o Using the name parameter, which selects a file from the
+ standard location.
After restoring the database, all auxiliary files (if any), gener-
ated by sysobjd plugins, will be regenerated using the restored
@@ -95,8 +89,8 @@
dump [search]
Prints all aliases and properties of system objects. The optional
- <search> parameter specifies the class of objects to be printed. If
- it is omitted, all objects will be printed. The <search> parameter
+ search parameter specifies the class of objects to be printed. If
+ it is omitted, all objects will be printed. The search parameter
has the same syntax as the search string specified to
sysobj_lookup(3SYSOBJ).
@@ -132,19 +125,18 @@
boot -- -r) is likely needed to make sure /dev and /devices are in
sync.
-
device-list [-P] [-I] [-i] [-a] [-u uuid | -p path | -d driver]
Lists device objects in the database, prints their UUID, driver,
- instance and state (active or inactive). If -P option is specified,
- the device path is printed instead of the UUID.
+ instance, and state (active or inactive). If -P option is speci-
+ fied, the device path is printed instead of the UUID.
If -I option is specified, the format of path_to_inst is mimicked,
- printing the path, driver and instance. The -I flag is mutually ex-
- clusive with the -P flag.
+ printing the path, driver, and instance. The -I flag is mutually
+ exclusive with the -P flag.
- If -u, -p or -d option is not specified, this will list all device
- objects, else only devices with the specified UUID, path or driver
+ If -u, -p, or -d option is not specified, this will list all device
+ objects, else only devices with the specified UUID, path, or driver
will be listed.
With the -a option, only active devices are listed. With the -i op-
@@ -172,7 +164,7 @@
- device-set-instance -u uuid | -p path <instance>
+ device-set-instance -u uuid | -p path instance
Sets the instance number for a device. If done on an running de-
vice, this command should be run with the sysobj service disabled,
@@ -213,8 +203,7 @@
-
- This example shows how sysobjadm(8) can be used to fix a duplicate in-
+ This example shows how sysobjadm can be used to fix a duplicate in-
stance number problem, if for example two devices have been in error
assigned the same instance number. In this case, two sd devices have
been assigned the instance number 1.
@@ -219,12 +208,12 @@
assigned the same instance number. In this case, two sd devices have
been assigned the instance number 1.
-
# svcadm disable -st sysobj
# sysobjadm device-list -I
"/pseudoscsibus/pseudoscsibus@0,0/pseudoscsi@0/sd@0,0" 1 "sd"
"/pseudoscsibus/pseudoscsibus@0,0/pseudoscsi@0/sd@1,0" 1 "sd"
- # sysobjadm device-set-instance -p /pseudoscsibus/pseudoscsibus@0,0/pseudoscsi@0/sd@1,0 2
+ # sysobjadm device-set-instance \
+ -p /pseudoscsibus/pseudoscsibus@0,0/pseudoscsi@0/sd@1,0 2
# reboot
[ after reboot ]
@@ -235,18 +224,16 @@
-
- This example is the same as above, but illustrates how sysobjadm(8) can
- be used to repair a duplicate instance assignment on a mounted root im-
- age.
-
+ This example is the same as above, but illustrates how sysobjadm can be
+ used to repair a duplicate instance assignment on a mounted root image.
[ mount alternate root image on /mnt ]
# sysobjadm -R /mnt device-list -I
"/pseudoscsibus/pseudoscsibus@0,0/pseudoscsi@0/sd@0,0" 1 "sd"
"/pseudoscsibus/pseudoscsibus@0,0/pseudoscsi@0/sd@1,0" 1 "sd"
- # sysobjadm -R /mnt device-set-instance -p /pseudoscsibus/pseudoscsibus@0,0/pseudoscsi@0/sd@1,0 2
+ # sysobjadm -R /mnt device-set-instance \
+ -p /pseudoscsibus/pseudoscsibus@0,0/pseudoscsi@0/sd@1,0 2
# sysobjadm -R /mnt device-list -I
"/pseudoscsibus/pseudoscsibus@0,0/pseudoscsi@0/sd@0,0" 1 "sd"
"/pseudoscsibus/pseudoscsibus@0,0/pseudoscsi@0/sd@1,0" 2 "sd"
@@ -326,4 +306,4 @@
SEE ALSO
sysobjd(8), libsysobj(3LIB), svcadm(8), beadm(8)
-Oracle Solaris 11.4 04 September 2024 sysobjadm(8)
+Oracle Solaris 11.4 23 Jun 2025 sysobjadm(8)
diff -NurbBw 11.4.81/man8/tapes.8 11.4.84/man8/tapes.8
--- 11.4.81/man8/tapes.8 2025-08-17 09:30:05.533317410 -0700
+++ 11.4.84/man8/tapes.8 2025-08-17 09:30:27.881712414 -0700
@@ -7,8 +7,8 @@
/usr/sbin/tapes [-r root_dir]
DESCRIPTION
- devfsadm(8) is now the preferred command for /dev and /devices and
- should be used instead of tapes.
+ devfsadm(8) is now the preferred command for managing /dev and /devices
+ and should be used instead of tapes.
tapes creates symbolic links in the /dev/rmt directory to the actual
@@ -56,10 +56,10 @@
ultra (u). These specifiers only express a relative density; it is up
to the driver to assign specific meanings as needed. For example, 9
track tape devices interpret these as actual bits-per-inch densities,
- where l means 800 BPI, m means 1600 BPI , and h means 6250 BPI,
- whereas 4mm DAT tapes defines l as standard format, and m, h, c and u
- as compressed format. Drivers may choose to implement any or all of
- these format types.
+ where l means 800 BPI, m means 1600 BPI, and h means 6250 BPI, whereas
+ 4mm DAT tapes defines l as standard format, and m, h, c, and u as com-
+ pressed format. Drivers may choose to implement any or all of these
+ format types.
During normal tape operation (non-BSD behavior), once an EOF mark has
@@ -242,4 +239,4 @@
BUGS
tapes silently ignores malformed minor device names.
-Oracle Solaris 11.4 14 May 2018 tapes(8)
+Oracle Solaris 11.4 23 Jun 2025 tapes(8)
diff -NurbBw 11.4.81/man8/th_manage.8 11.4.84/man8/th_manage.8
--- 11.4.81/man8/th_manage.8 2025-08-17 09:30:05.565957767 -0700
+++ 11.4.84/man8/th_manage.8 2025-08-17 09:30:27.914873733 -0700
@@ -21,8 +21,8 @@
broadcast Awaken all th_define processes, causing them to dis-
play their current status and exit if the errdef is
- now defunct (that is, if count, failcount , and
- acc_chk are all zero).
+ now defunct (that is, if count, failcount, and acc_chk
+ are all zero).
clear_acc_chk Awaken all th_define processes. If count and failcount
@@ -30,7 +30,7 @@
th_define exits once it has displayed its status.
- clear_errdefs Awaken all th_define processes. count, failcount and
+ clear_errdefs Awaken all th_define processes. count, failcount, and
acc_chk are all set to zero so that all th_define com-
mands exit once they have displayed their status.
@@ -58,13 +58,12 @@
To begin the tests, enter:
-
# th_manage foo 0 start
- To check the status of the errdefs, enter:
+ To check the status of the errdefs, enter:
# th_manage foo 0 broadcast
@@ -79,13 +79,12 @@
fline using libdevice, clear the error condition by entering:
-
# th_manage foo 0 clear_acc_chk
- or
+ or
# th_manage foo 0 clear_errors
@@ -99,10 +99,10 @@
To terminate testing, enter:
-
# th_manage foo 0 clear_errdefs
+
SEE ALSO
th_define(8)
-Oracle Solaris 11.4 4 Jan 2001 th_manage(8)
+Oracle Solaris 11.4 23 Jun 2025 th_manage(8)
diff -NurbBw 11.4.81/man8/tic.8 11.4.84/man8/tic.8
--- 11.4.81/man8/tic.8 2025-08-17 09:30:05.600029936 -0700
+++ 11.4.84/man8/tic.8 2025-08-17 09:30:27.953768629 -0700
@@ -75,4 +75,4 @@
entry_name_1 before use= for these capabilities to be canceled in en-
try_name_1.
-Oracle Solaris 11.4 5 Jul 1990 tic(8)
+Oracle Solaris 11.4 23 Jun 2025 tic(8)
diff -NurbBw 11.4.81/man8/tpmadm.8 11.4.84/man8/tpmadm.8
--- 11.4.81/man8/tpmadm.8 2025-08-17 09:30:05.635499216 -0700
+++ 11.4.84/man8/tpmadm.8 2025-08-17 09:30:27.995362066 -0700
@@ -73,7 +73,7 @@
SUB-COMMANDS
The following subcommands are used in the form:
- # tpmadm <subcommand> [operand]
+ tpmadm <subcommand> [operand]
status
@@ -283,4 +282,4 @@
See tcsd(8) for more details.
-Oracle Solaris 11.4 21 Jun 2021 tpmadm(8)
+Oracle Solaris 11.4 23 Jun 2025 tpmadm(8)
diff -NurbBw 11.4.81/man8/ttymon.8 11.4.84/man8/ttymon.8
--- 11.4.81/man8/ttymon.8 2025-08-17 09:30:05.673288944 -0700
+++ 11.4.84/man8/ttymon.8 2025-08-17 09:30:28.035859711 -0700
@@ -255,11 +255,12 @@
SEE ALSO
- svcs(1), pam(3PAM), logindevperm(5), pam.conf(5), utmpx(5), attrib-
- utes(7), environ(7), pam_authtok_check(7), pam_authtok_get(7), pam_au-
- thtok_store(7), pam_dhkeys(7), pam_passwd_auth(7), pam_unix_account(7),
- pam_unix_auth(7), pam_unix_session(7), smf(7), autopush(8), stty-
- defs(8), svcadm(8), svccfg(8), vtdaemon(8)
+ svcs(1), pam(3PAM), tty(4D), logindevperm(5), pam.conf(5), ttydefs(5),
+ utmpx(5), attributes(7), environ(7), pam_authtok_check(7),
+ pam_authtok_get(7), pam_authtok_store(7), pam_dhkeys(7),
+ pam_passwd_auth(7), pam_unix_account(7), pam_unix_auth(7),
+ pam_unix_session(7), smf(7), autopush(8), sttydefs(8), svcadm(8),
+ svccfg(8), vtdaemon(8)
NOTES
Service Access Facility (SAF and SAC)
@@ -283,4 +284,4 @@
abling additional service instances to avoid this situation, or the two
ttymons will compete for input.
-Oracle Solaris 11.4 11 May 2021 ttymon(8)
+Oracle Solaris 11.4 23 Jun 2025 ttymon(8)
diff -NurbBw 11.4.81/man8/tunefs.8 11.4.84/man8/tunefs.8
--- 11.4.81/man8/tunefs.8 2025-08-17 09:30:05.707432713 -0700
+++ 11.4.84/man8/tunefs.8 2025-08-17 09:30:28.069091802 -0700
@@ -8,82 +8,79 @@
[-m minfree] [-o space | time] special | filesystem
DESCRIPTION
- tunefs is designed to change the dynamic parameters of a file system
- that affect the layout policies. When using tunefs with filesystem,
+ tunefs is designed to change the dynamic parameters of a UFS file sys-
+ tem that affect the layout policies. When using tunefs with filesystem,
filesystem must be in /etc/vfstab. The parameters that can be changed
are indicated by the options given below.
OPTIONS
The following options are supported:
- -a maxcontig The maximum number of logical blocks, belonging to
- one file, that is allocated contiguously. The de-
- fault is calculated as follows:
-
+ -a maxcontig
+ The maximum number of logical blocks, belonging to one file, that
+ is allocated contiguously. The default is calculated as follows:
maxcontig = disk drive maximum transfer size / disk block size
+ If the disk drive's maximum transfer size cannot be determined, the
+ default value for maxcontig is calculated from kernel parameters as
+ follows:
+
+ If maxphys is less than ufs_maxmaxphys, which is 1 Mbyte, then max-
+ contig is set to maxphys. Otherwise, maxcontig is set to ufs_max-
+ maxphys.
+
+ You can set maxcontig to any positive integer value.
+
+ The actual value will be the lesser of what has been specified and
+ what the hardware supports.
+
+
+ -d rotdelay
+
+ This parameter is obsolete as of the Solaris 10 release. The value
+ is always set to 0, regardless of the input value.
+
+
+ -e maxbpg
+
+ Indicates the maximum number of contiguous logical blocks any sin-
+ gle file can allocate from a cylinder group before it is forced to
+ begin allocating blocks from another cylinder group. Typically this
+ value is set to approximately one quarter of the total contiguous
+ logical blocks in a cylinder group. The intent is to prevent any
+ single file from using up all the blocks in a single cylinder
+ group, thus degrading access times for all files subsequently allo-
+ cated in that cylinder group.
+
+ The effect of this limit is to cause big files to do long seeks
+ more frequently than if they were allowed to allocate all the
+ blocks in a cylinder group before seeking elsewhere. For file sys-
+ tems with exclusively large files, this parameter should be set
+ higher.
+
+
+ -m minfree
+
+ Specifies the minimum free space threshold, or the percentage of
+ space held back from normal users. This value can be set to 0. How-
+ ever, up to a factor of three in throughput will be lost over the
+ performance obtained at a 10% threshold. Note: If the value is
+ raised above the current usage level, users will be unable to allo-
+ cate files until enough files have been deleted to get under the
+ higher threshold.
+
+ -o space|time
- If the disk drive's maximum transfer size cannot be
- determined, the default value for maxcontig is cal-
- culated from kernel parameters as follows:
-
- If maxphys is less than ufs_maxmaxphys, which is 1
- Mbyte, then maxcontig is set to maxphys. Otherwise,
- maxcontig is set to ufs_maxmaxphys.
-
- You can set maxcontig to any positive integer
- value.
-
- The actual value will be the lesser of what has
- been specified and what the hardware supports.
-
-
- -d rotdelay This parameter is obsolete as of the Solaris 10 re-
- lease. The value is always set to 0, regardless of
- the input value.
-
-
- -e maxbpg Indicates the maximum number of contiguous logical
- blocks any single file can allocate from a cylinder
- group before it is forced to begin allocating
- blocks from another cylinder group. Typically this
- value is set to approximately one quarter of the
- total contiguous logical blocks in a cylinder
- group. The intent is to prevent any single file
- from using up all the blocks in a single cylinder
- group, thus degrading access times for all files
- subsequently allocated in that cylinder group.
-
- The effect of this limit is to cause big files to
- do long seeks more frequently than if they were al-
- lowed to allocate all the blocks in a cylinder
- group before seeking elsewhere. For file systems
- with exclusively large files, this parameter should
- be set higher.
-
-
- -m minfree Specifies the minimum free space threshold, or the
- percentage of space held back from normal users.
- This value can be set to 0. However, up to a factor
- of three in throughput will be lost over the per-
- formance obtained at a 10% threshold. Note: If the
- value is raised above the current usage level,
- users will be unable to allocate files until enough
- files have been deleted to get under the higher
- threshold.
-
-
- -ospace|time The file system can either be instructed to try to
- minimize the time spent allocating blocks, or to
- try to minimize the space fragmentation on the
- disk. The default is time.
+ The file system can either be instructed to try to minimize the
+ time spent allocating blocks, or to try to minimize the space frag-
+ mentation on the disk. The default is time.
- Generally, you should optimize for time unless the
- file system is over 90% full.
+ Generally, you should optimize for time unless the file system is
+ over 90% full.
ATTRIBUTES
@@ -102,4 +99,4 @@
NOTES
You can tune a file-system, but you can't tune a fish.
-Oracle Solaris 11.4 4 Feb 2015 tunefs(8)
+Oracle Solaris 11.4 23 Jun 2025 tunefs(8)
diff -NurbBw 11.4.81/man8/txzonemgr.8 11.4.84/man8/txzonemgr.8
--- 11.4.81/man8/txzonemgr.8 2025-08-17 09:30:05.741236566 -0700
+++ 11.4.84/man8/txzonemgr.8 2025-08-17 09:30:28.102109194 -0700
@@ -90,8 +90,8 @@
SEE ALSO
- zenity(1), attributes(7), rbac(7), zones(7), ipadm(8), zoneadm(8),
- zonecfg(8)
+ zenity(1), attributes(7), brands(7), rbac(7), trusted_extensions(7),
+ zones(7), ipadm(8), zoneadm(8), zonecfg(8)
Trusted Extensions Configuration and Administration
@@ -101,4 +101,4 @@
5). Prior to that it was included in the Trusted Extensions add-on for
Solaris.
-Oracle Solaris 11.4 21 Jun 2021 txzonemgr(8)
+Oracle Solaris 11.4 23 Jun 2025 txzonemgr(8)
diff -NurbBw 11.4.81/man8/ufsdump.8 11.4.84/man8/ufsdump.8
--- 11.4.81/man8/ufsdump.8 2025-08-17 09:30:05.780439572 -0700
+++ 11.4.84/man8/ufsdump.8 2025-08-17 09:30:28.143283959 -0700
@@ -8,8 +8,12 @@
DESCRIPTION
ufsdump backs up all files specified by files_to_dump (usually either a
- whole file system or files within a file system changed after a certain
- date) to magnetic tape or disk file.
+ whole UFS file system or files within a UFS file system changed after a
+ certain date) to magnetic tape or disk file.
+
+
+ ufsdump can only operate on files residing on UFS filesystems, or an
+ entire UFS file system.
The ufsdump command can only be used on unmounted file systems, or
@@ -79,8 +83,8 @@
half-inch reel. This sets the density to 1000BPI and the blocking
factor to 126. Since ufsdump can automatically detect the end-of-
media, only the blocking parameter normally has an effect. When
- cartridge tapes are used, and this option is not specified, ufsdump
- will slightly miscompute the size of the tape. If the b, d, s or t
+ cartridge tapes are used, if this option is not specified, ufsdump
+ will slightly miscompute the size of the tape. If the b, d, s, or t
options are specified with this option, their values will override
the defaults set by this option.
@@ -101,8 +105,8 @@
1/4 inch cartridge
- 1000 BPI The tape densities and other options are documented in
- the st(4D) man page.
+ 1000 BPI. The tape densities and other options are documented
+ in the st(4D) man page.
@@ -231,8 +235,8 @@
Sets the amount of time to wait for an autoload command to com-
plete. This option is ignored unless the l option has also been
specified. The default time period to wait is two minutes. Specify
- time units with a trailing h ( for hours), m (for minutes), or s
- (for seconds). The default unit is minutes.
+ time units with a trailing h for hours, m for minutes, or s for
+ seconds. The default unit is minutes.
u
@@ -319,19 +323,13 @@
While running, ufsdump emits many verbose messages. ufsdump returns the
following exit values:
- 0
-
- Normal exit.
-
-
- 1
+ 0 Normal exit.
- Startup errors encountered.
+ 1 Startup errors encountered.
- 3
- Abort - no checkpoint attempted.
+ 3 Abort - no checkpoint attempted.
FILES
@@ -361,9 +359,9 @@
SEE ALSO
- cpio(1), tar(1), scanf(3C), st(4D), ufsdump(5), attributes(7), dd(8),
- devnm(8), fssnap(8), prtvtoc(8), rmt(8), shutdown(8), ufsrestore(8),
- volcopy(8), wall(8)
+ cpio(1), tar(1), scanf(3C), st(4D), ufs(4FS), ufsdump(5), attrib-
+ utes(7), dd(8), devnm(8), fssnap(8), prtvtoc(8), rmt(8), shutdown(8),
+ ufsrestore(8), volcopy(8), wall(8)
NOTES
Read Errors
@@ -431,7 +429,7 @@
Most disks contain one or more overlapping slices because slice 2 cov-
ers the entire disk. The other slices are of various sizes and usually
do not overlap. For example, a common configuration places root on
- slice 0, swap on slice 1, /opt on slice 5 and /usr on slice 6.
+ slice 0, swap on slice 1, /opt on slice 5, and /usr on slice 6.
It should be emphasized that ufsdump dumps one ufs file system at a
@@ -447,4 +445,4 @@
and W options assume file systems should be backed up daily, which lim-
its the usefulness of these options.
-Oracle Solaris 11.4 6 Oct 2022 ufsdump(8)
+Oracle Solaris 11.4 23 Jun 2025 ufsdump(8)
diff -NurbBw 11.4.81/man8/virtinfo.8 11.4.84/man8/virtinfo.8
--- 11.4.81/man8/virtinfo.8 2025-08-17 09:30:05.818232170 -0700
+++ 11.4.84/man8/virtinfo.8 2025-08-17 09:30:28.183405357 -0700
@@ -4,53 +4,71 @@
virtinfo - virtual environment information
SYNOPSIS
+ virtinfo [-c {class[,...] | all}] [subcommand]
+ list [[-H] -o field[,...]] [environment] ...
+ get [[-H] -o field[,...]] {all | property[,...]} [environment] ...
+
+ Legacy SPARC-only Interface
virtinfo [-acdptsu]
- virtinfo [-c {<class>[,...] | all}] [<subcommand>]
- list [[-H] -o <field>[,...]] [<environment>] ...
- get [[-H] -o <field>[,...]] {all | <property>[,...]}
- [<environment>] ...
DESCRIPTION
The virtinfo utility provides virtualization information returned by
- libv12n(3LIB) about the current environment, parent environment and a
+ libv12n(3LIB) about the current environment, parent environment, and a
list of supported environments. If no options are specified, virtinfo
performs the equivalent of virtinfo list.
+
+ The virtinfo command has two interfaces, a legacy interface only avail-
+ able on SPARC systems that only reports on Logical Domains (LDoms) en-
+ vironments, and a generic interface available for all platforms and
+ virtualization types that are supported by libv12n(3LIB).
+
OPTIONS
- The virtinfo command supports the following option:
+ The virtinfo command supports the following option in the generic in-
+ terface:
- -a SPARC only: Execute with all flags.
+ -c Choose from available virtual environment classes: current, par-
+ ent, supported, or unsupported.
- -c SPARC only: Report if a control domain.
+ Without the -c option, all classes are assumed.
- -d SPARC only: Report domain name.
+ Legacy SPARC-only Interface
+ The virtinfo command supports the following options in the legacy in-
+ terface:
+ -a Execute with all flags.
- -p SPARC only: Parsable format.
+ -c Report if a control domain.
- -t SPARC only: Report domain role.
+ -d Report domain name.
- -s SPARC only: Report chassis serial number.
+ -p Parsable format, similar to ldm(8).
- -u SPARC only: Report UUID.
+ -t Report domain role.
- -c Choose from available virtual environment classes: current, par-
- ent, supported, or unsupported.
+ -s Report chassis serial number.
- Without the -c option, all classes are assumed.
+ -u Report UUID.
+
+
+
+ If none of these options are specified, or if an argument is provided
+ to the -c option, then the generic interface is used instead of the
+ legacy interface.
SUB-COMMANDS
- The virtinfo command supports the following subcommands:
+ The virtinfo command supports the following subcommands in the generic
+ interface:
- list [[-H] -o <field>[,...]] [<environment>] ...
+ list [[-H] -o field[,...]] [environment]...
Lists all virtual environments from chosen environment classes. The
list can be limited by listing environments of interest. For each
@@ -72,8 +90,7 @@
- get [[-H] -o < field>[,...]] {all | <property>[,...]}
- [<environment>] ...
+ get [[-H] -o field[,...]] {all | property[,...]} [environment] ...
Retrieve a property of an environment. Properties are environment
and class specific. For example an LDoms supported environment may
@@ -113,6 +130,8 @@
+ The legacy interface does not include any subcommands.
+
EXIT STATUS
The following exit values are returned:
@@ -247,6 +259,39 @@
kz1
+ Legacy SPARC-only Interface
+ Example 7 Print all information available from legacy interface
+
+
+
+ This command prints the information for an LDoms guest domain in the
+ default format.
+
+
+ # virtinfo -a
+ Domain role: LDoms guest
+ Domain name: ldg1
+ Domain UUID: 12345678-1234-5678-1234-567812345678
+ Control domain: ld-host.example.com
+ Chassis serial#: AC0012345
+
+
+ Example 8 Print information in parsable format from legacy interface
+
+
+
+ This command prints the information for an LDoms guest domain in the
+ parsable format.
+
+
+ # virtinfo -ap
+ VERSION 1.0
+ DOMAINROLE|impl=LDoms|control=false|io=false|service=false|root=false
+ DOMAINNAME|name=ldg1
+ DOMAINUUID|uuid=12345678-1234-5678-1234-567812345678
+ DOMAINCONTROL|name=ld-host.example.com
+ DOMAINCHASSIS|serialno=AC0012345
+
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -261,6 +306,6 @@
SEE ALSO
- libuuid(3LIB), libv12n(3LIB)
+ libuuid(3LIB), libv12n(3LIB), ldm(8)
-Oracle Solaris 11.4 8 Jan 2020 virtinfo(8)
+Oracle Solaris 11.4 23 Jun 2025 virtinfo(8)
diff -NurbBw 11.4.81/man8/vmstat.8 11.4.84/man8/vmstat.8
--- 11.4.81/man8/vmstat.8 2025-08-17 09:30:05.854444862 -0700
+++ 11.4.84/man8/vmstat.8 2025-08-17 09:30:28.224052464 -0700
@@ -16,7 +16,7 @@
vmstat only supports statistics for certain devices. For more general
- system statistics, use sar(1), iostat(8), or sar(8).
+ system statistics, use sstore(1), sar(1), iostat(8), or sar(8).
Without options, vmstat displays a one-line summary of the virtual mem-
@@ -103,7 +99,7 @@
-w Wide display format. Headers will be more descriptive and
two space gap is provided between each column.
- Refer the examples section for sample outputs
+ Refer to the examples section for sample outputs.
OPERANDS
@@ -115,8 +111,8 @@
disks Specifies which disks are to be given priority in the out-
put (only four disks fit on a line). Common disk names are
- id, sd, xd, or xy, followed by a number (for example, sd2,
- xd0, and so forth).
+ sd, cmdk, or xy, followed by a number (for example, sd2,
+ xy0, and so forth).
interval Specifies the last number of seconds over which vmstat sum-
@@ -223,8 +210,8 @@
disk Report the number of disk operations per second. There are
slots for up to four disks, labeled with a single letter and
- number. The letter indicates the type of disk (s = SCSI, i =
- IPI, and so forth); the number is the logical unit number.
+ number. The letter indicates the type of disk (s = SCSI and
+ so forth); the number is the logical unit number.
faults Report the trap/interrupt rates (per second).
@@ -315,7 +290,8 @@
Invocation is evolving. Human readable output is unstable.
SEE ALSO
- date(1), sar(1), time(2), attributes(7), iostat(8), mpstat(8), sar(8)
+ date(1), sar(1), sstore(1), time(2), attributes(7), iostat(8),
+ mpstat(8), sar(8)
NOTES
The sum of CPU utilization might vary slightly from 100 because of
@@ -356,4 +332,4 @@
The vmstat command, including support for the -i, -s, and -S options,
has been included in all Sun and Oracle releases of Solaris.
-Oracle Solaris 11.4 13 Sep 2024 vmstat(8)
+Oracle Solaris 11.4 23 Jun 2025 vmstat(8)
diff -NurbBw 11.4.81/man8/wanboot_keygen.8 11.4.84/man8/wanboot_keygen.8
--- 11.4.81/man8/wanboot_keygen.8 2025-08-17 09:30:05.890281584 -0700
+++ 11.4.84/man8/wanboot_keygen.8 2025-08-17 09:30:28.260066791 -0700
@@ -110,4 +110,4 @@
SEE ALSO
attributes(7)
-Oracle Solaris 11.4 02 Nov 2017 wanboot_keygen(8)
+Oracle Solaris 11.4 23 Jun 2025 wanboot_keygen(8)
diff -NurbBw 11.4.81/man8/ypbind.8 11.4.84/man8/ypbind.8
--- 11.4.81/man8/ypbind.8 2025-08-17 09:30:05.930324359 -0700
+++ 11.4.84/man8/ypbind.8 2025-08-17 09:30:28.295864190 -0700
@@ -74,8 +74,8 @@
Send a broadcast datagram using UDP/IP that requests the informa-
tion needed to bind to a specific NIS server. This option is analo-
- gous to ypbind with no options in earlier Sun releases and is rec-
- ommended for ease of use.
+ gous to ypbind with no options in earlier SunOS releases and is
+ recommended for ease of use.
Enabling the SMF property config.use_broadcast enables -broadcast.
@@ -121,8 +121,8 @@
SEE ALSO
svcs(1), ypcat(1), ypmatch(1), ypwhich(1), ypclnt(3C), hosts(5), yp-
- files(5), attributes(7), smf(7), ifconfig(8), svcadm(8), ypinit(8),
- ypset(8)
+ files(5), attributes(7), nis(7), smf(7), ifconfig(8), svcadm(8), yp-
+ init(8), ypset(8)
NOTES
ypbind supports multiple domains. The ypbind process can maintain bind-
@@ -146,4 +146,4 @@
requesting restart, can be performed using svcadm(8). The service's
status can be queried using the svcs(1) command.
-Oracle Solaris 11.4 24 Dec 2014 ypbind(8)
+Oracle Solaris 11.4 23 Jun 2025 ypbind(8)
diff -NurbBw 11.4.81/man8/zdump.8 11.4.84/man8/zdump.8
--- 11.4.81/man8/zdump.8 2025-08-17 09:30:05.963152211 -0700
+++ 11.4.84/man8/zdump.8 2025-08-17 09:30:28.332630757 -0700
@@ -72,4 +72,4 @@
SEE ALSO
ctime(3C), mktime(3C), attributes(7), environ(7), zic(8)
-Oracle Solaris 11.4 3 Jan 2006 zdump(8)
+Oracle Solaris 11.4 23 Jun 2025 zdump(8)
diff -NurbBw 11.4.81/man8/zfs.8 11.4.84/man8/zfs.8
--- 11.4.81/man8/zfs.8 2025-08-17 09:30:06.098233304 -0700
+++ 11.4.84/man8/zfs.8 2025-08-17 09:30:28.455967806 -0700
@@ -330,20 +330,20 @@
File system snapshots can be accessed under the .zfs/snapshot directory
- in the root of the file system. If mkdir is is run in this directory, a
+ in the root of the file system. If mkdir is run in this directory, a
new snapshot is created with the name of the specified directory. If
rmdir is run against a snapshot in that directory, that snapshot will
be destroyed.
If a clone of a file system has its mountpoint property set to
- clonedir, then that clone will be mounted in the .zfs/clone directory.
- If mkdir is is run in this directory, a new snapshot is created and a
- clone is made from that snapshot with the name of the directory speci-
- fied. Its mountpoint will be set to clonedir. If rmdir is run against a
- clone mounted there, that clone will be destroyed, but the correspond-
- ing snapshot will remain. See the mountpoint property description below
- for more information.
+ clonedir, then that clone will be mounted in the .zfs/clone directory
+ of its clone source. If mkdir is run in this directory, a new snapshot
+ is created and a clone is made from that snapshot with the name of the
+ directory specified. Its mountpoint will be set to clonedir. If rmdir
+ is run against a clone mounted there, that clone will be destroyed, but
+ the corresponding snapshot will remain. See the mountpoint property de-
+ scription below for more information.
When SMB shares are created, the SMB share name appears as an entry in
@@ -943,6 +943,11 @@
the file system will be mounted in the .zfs/clone directory of the
file system this is a clone of.
+ If the mountpoint is set to clonedir, certain mount options will
+ follow the clone source's setting rather than the one on the clone.
+ These include: devices, exec, multilevel, nbmand, readonly,
+ rstchown, setuid, and xattr. For more information, see mount(8).
+
nbmand=on | off
@@ -3950,4 +3955,4 @@
+---------------------------+---------------------------+---------------+
-Oracle Solaris 11.4 17 Mar 2025 zfs(8)
+Oracle Solaris 11.4 2 Apr 2025 zfs(8)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment