Skip to content

Instantly share code, notes, and snippets.

@alanc

alanc/SRU72-man-page-changes.diff

Created August 20, 2024 19:54
Show Gist options
  • Save alanc/6588edeb91692c7145f0e22363a8a5b8 to your computer and use it in GitHub Desktop.
Save alanc/6588edeb91692c7145f0e22363a8a5b8 to your computer and use it in GitHub Desktop.
Download ZIP
Changes to core OS man pages in Oracle Solaris 11.4 SRU 72
Raw
Solaris-11.4-SRU72-man-page-changes.txt
14924522 umask(2) is not really mt-safe as it has process wide consequences; need getumask(2)
25720605 per-file audit should include SMB vs NFS indicator
31484392 closefrom(3c) is no longer MT-Unsafe
35001134 add support for clones being exposed under .zfs
35219802 Provide LDoms statistics to StatsStore and WebUI
35675930 audit_syslog should include timestamp from audit record
35954438 snapdir property is poorly described and mislabeled in the AK BUI
35998856 Add TLS support for Solaris/ZFSSA Virus Scan Service
36354283 elfdump should be able to dump PLTs
36383314 ::printf can not read simple values
36405494 Add a "noresvport" mount option for NFS
36416832 Assorted fixes for Section 4d man pages
36448609 pam_krb5 option to limit expiry warning period
36486238 introduce DPD log level for iked
36487229 Customer requests examples of disabling caches in nscd.conf man page
36527124 tar(1) improperly documents the /etc/default/tar arguments
36595035 closefrom(3c) is defined in <stdlib.h>, other OSes define it in <unistd.h>
36603375 bpf(4d) should document required privileges
36674072 Default ldm stop timeout too short
36736399 Assorted fixes for Section 4, 4fs, and 4i man pages
36765854 Adopt "manager" and "subsidiary" terms for ptys in man pages
PSARC 2024/045 getumask(2)
PSARC 2024/058 'noresvport' mount option for NFS
PSARC/2023/088 audit_syslog optional ISO8601 UTC event timestamp
PSARC/2023/102 ZFS clonedir
PSARC/2024/041 elfdump -L option for displaying PLT details
PSARC/2024/052 pam_krb5 option to limit expiry warning period
PSARC/2024/064 Add remote protocol identifier to audit_sylog output.
Copyright (c) 1983, 2024, Oracle and/or its affiliates.
Raw
SRU72-man-page-changes.diff
diff -NurbBw 11.4.69/man1/elfdump.1 11.4.72/man1/elfdump.1
--- 11.4.69/man1/elfdump.1 2024-08-20 12:29:43.276888435 -0700
+++ 11.4.72/man1/elfdump.1 2024-08-20 12:30:00.431797350 -0700
@@ -4,7 +4,7 @@
elfdump - dumps selected parts of an object file
SYNOPSIS
- elfdump [-cCdegGhHiklmnPrsSuvVy] [-p | -w file]
+ elfdump [-cCdegGhHiklLmnPrsSuvVy] [-p | -w file]
[-F fmtopt1,fmtopt2,...] [-I index-expr]
[-N name] [-O osabi] [-T type] file...
@@ -42,6 +42,7 @@
Interpreter -i Special, see below.
Move -m SHT_SUNW_move
Note -n SHT_NOTE
+ Procedure Linkage Table (PLT) -L Special, see below.
Relocation -r SHT_RELA
SHT_REL
Stack Unwind/Exceptions -u Special, see below.
@@ -63,10 +64,11 @@
quested types of section data.
- Interpreter and global offset table sections do not have a special ELF
- section type, but are instead implemented as SHT_PROGBITS sections with
- well known names (.interp and .got respectively). elfdump is able to
- recognize and display these special sections.
+ Interpreter, global offset table, and procedure linkage table sections
+ do not have a special ELF section type, but are instead implemented as
+ SHT_PROGBITS sections with well known names (.interp, .got, and .plt
+ respectively). elfdump is able to recognize and display these special
+ sections.
When run without options to narrow the information displayed, elfdump
@@ -207,6 +209,11 @@
Equivalent to -F notrunc. See -F.
+ -L
+
+ Dumps the contents of the .plt section.
+
+
-m
Dumps the contents of the .SUNW_move section.
@@ -528,4 +535,4 @@
this information. Section names are augmented with the name of the ob-
ject to which they apply.
-Oracle Solaris 11.4 30 August 2017 elfdump(1)
+Oracle Solaris 11.4 29 February 2024 elfdump(1)
diff -NurbBw 11.4.69/man1/mdb.1 11.4.72/man1/mdb.1
--- 11.4.69/man1/mdb.1 2024-08-20 12:29:43.448460156 -0700
+++ 11.4.72/man1/mdb.1 2024-08-20 12:30:00.559697507 -0700
@@ -3223,7 +3223,8 @@
- address ::printf [ -e ] [ -c lim ] [ -t format ... ] format [type] ...
+ address ::printf [ -e ] [ -i ] [ -c lim ] [ -t format ... ] format
+ [type][ +/-i ] arg ...
Print the data structure using the printf format command. Arguments
to the format can be:
@@ -3249,6 +3250,12 @@
given then write subsequent output to standard error. For possible
expansions in the format string, see the ::help printf command.
+ The option -i tells ::printf to treat the subsequent arguments as
+ immediate values. The +i option stops ::printf from treating argu-
+ ments as immediate values. There can be multiple -i and +i argu-
+ ments allowing immediate and non-immediate arguments to mixed in a
+ single line
+
address ::poke[ -AnFfS ][ type ][ member ][ operator ][ -AnFfS ][ -v
var ][ -- ]
@@ -5198,4 +5205,4 @@
provides source code for an example module in the directory
/usr/demo/mdb.
-Oracle Solaris 11.4 22 February 2024 mdb(1)
+Oracle Solaris 11.4 14 March 2024 mdb(1)
diff -NurB 11.4.69/man1/tar.1 11.4.72/man1/tar.1
--- 11.4.69/man1/tar.1 2024-08-20 12:29:43.506608015 -0700
+++ 11.4.72/man1/tar.1 2024-08-20 12:30:00.633215441 -0700
@@ -242,7 +242,7 @@
example,
- tar -c 2/tmp/*
+ tar -c2 /tmp/*
writes the output to the device specified as archive2 in /etc/de-
fault/tar.
@@ -950,4 +950,4 @@
-Oracle Solaris 11.4 3 Nov 2021 tar(1)
+Oracle Solaris 11.4 21 Apr 2024 tar(1)
diff -NurbBw 11.4.69/man2/close.2 11.4.72/man2/close.2
--- 11.4.69/man2/close.2 2024-08-20 12:29:43.548901053 -0700
+++ 11.4.72/man2/close.2 2024-08-20 12:30:00.675791832 -0700
@@ -60,15 +60,15 @@
tached, the stream associated with that end is also dismantled.
- If fildes refers to the master side of a pseudo-terminal, a SIGHUP sig-
- nal is sent to the session leader, if any, for which the slave side of
- the pseudo-terminal is the controlling terminal. It is unspecified
- whether closing the master side of the pseudo-terminal flushes all
- queued input and output.
+ If fildes refers to the manager side of a pseudo-terminal, a SIGHUP
+ signal is sent to the session leader, if any, for which the subsidiary
+ side of the pseudo-terminal is the controlling terminal. It is unspeci-
+ fied whether closing the manager side of the pseudo-terminal flushes
+ all queued input and output.
- If fildes refers to the slave side of a streams-based pseudo-terminal,
- a zero-length message may be sent to the master.
+ If fildes refers to the subsidiary side of a streams-based pseudo-ter-
+ minal, a zero-length message may be sent to the manager.
When there is an outstanding cancelable asynchronous I/O operation
@@ -211,4 +211,4 @@
The close() function has been included in all Sun and Oracle releases
of Solaris.
-Oracle Solaris 11.4 30 Jan 2023 close(2)
+Oracle Solaris 11.4 19 Jun 2024 close(2)
diff -NurbBw 11.4.69/man2/open.2 11.4.72/man2/open.2
--- 11.4.69/man2/open.2 2024-08-20 12:29:43.594970233 -0700
+++ 11.4.72/man2/open.2 2024-08-20 12:30:00.717640049 -0700
@@ -320,10 +320,10 @@
receive the file descriptor.
- If path names the master side of a pseudo-terminal device, then it is
- unspecified whether open() locks the slave side so that it cannot be
- opened. Portable applications must call unlockpt(3C) before opening the
- slave side.
+ If path names the manager side of a pseudo-terminal device, then it is
+ unspecified whether open() locks the subsidiary side so that it cannot
+ be opened. Portable applications must call unlockpt(3C) before opening
+ the subsidiary side.
If the file is a regular file and the local file system is mounted with
@@ -560,8 +560,8 @@
The open() and openat() functions may fail if:
- EAGAIN The path argument names the slave side of a pseudo-ter-
- minal device that is locked.
+ EAGAIN The path argument names the subsidiary side of a
+ pseudo-terminal device that is locked.
EINVAL The value of the oflag argument is not valid.
@@ -745,4 +745,4 @@
Oracle Solaris 11.4 also added the openpty(3C) function to encapsulate
most of this detail behind a portable interface.
-Oracle Solaris 11.4 30 Jan 2023 open(2)
+Oracle Solaris 11.4 19 Jun 2024 open(2)
diff -NurbBw 11.4.69/man2/umask.2 11.4.72/man2/umask.2
--- 11.4.69/man2/umask.2 2024-08-20 12:29:43.643568703 -0700
+++ 11.4.72/man2/umask.2 2024-08-20 12:30:00.744741686 -0700
@@ -1,23 +1,33 @@
umask(2) System Calls umask(2)
NAME
- umask - set and get file creation mask
+ umask, getumask - set and get file creation mask
SYNOPSIS
- #include <sys/types.h>
#include <sys/stat.h>
mode_t umask(mode_t cmask);
+ mode_t getumask(void);
DESCRIPTION
The umask() function sets the process's file mode creation mask to
cmask and returns the previous value of the mask. Only the access per-
- mission bits of cmask and the file mode creation mask are used. The
- mask is inherited by child processes. See Intro(2) for more information
- on masks.
+ mission bits of cmask and the file mode creation mask are used.
+
+
+ The getumask() function returns the process's file mode creation mask.
+
+
+ The mask is inherited by child processes. See Intro(2) for more infor-
+ mation on masks.
RETURN VALUES
- The previous value of the file mode creation mask is returned.
+ The umask() function returns the previous value of the file mode cre-
+ ation mask.
+
+
+ The getumask() function returns the current value of the file mode cre-
+ ation mask.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -37,4 +47,11 @@
mkdir(1), sh(1), chmod(2), creat(2), Intro(2), mknod(2), open(2),
stat.h(3HEAD), attributes(7), standards(7)
-Oracle Solaris 11.4 28 Dec 1996 umask(2)
+HISTORY
+ The getumask() function was added to Oracle Solaris in Solaris 11.4.72.
+
+
+ The umask() function has been included in all Sun and Oracle releases
+ of Solaris.
+
+Oracle Solaris 11.4 11 Mar 2024 umask(2)
diff -NurbBw 11.4.69/man3c/closefrom.3c 11.4.72/man3c/closefrom.3c
--- 11.4.69/man3c/closefrom.3c 2024-08-20 12:29:43.675664394 -0700
+++ 11.4.72/man3c/closefrom.3c 2024-08-20 12:30:00.773487709 -0700
@@ -4,11 +4,13 @@
closefrom, fdwalk - close or iterate over open file descriptors
SYNOPSIS
- #include <stdlib.h>
+ #include <unistd.h>
void closefrom(int lowfd);
+ #include <stdlib.h>
+
int fdwalk(int (*func)(void *, int), void *cd);
DESCRIPTION
@@ -31,7 +33,8 @@
except that close() is called only on file descriptors that are actu-
ally open, not on every possible file descriptor greater than or equal
to lowfd, and close() is also called on any open file descriptors
- greater than or equal to rl.rlim_max (and lowfd), should any exist.
+ greater than or equal to rl.rlim_max (and lowfd), should any exist, us-
+ ing an undocumented fcntl() command.
The fdwalk() function first makes a list of all currently open file de-
@@ -103,12 +106,18 @@
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
- | MT-Level |Unsafe |
+ | MT-Level |See below |
+------------------------------+-----------------------------+
+ MT-Level
+ The fdwalk() function is Unsafe.
+
+
+ The closefrom() function is Async-Signal-Safe.
+
SEE ALSO
- close(2), getrlimit(2), posix_spawn_file_actions_addclosefrom_np(3C),
- proc(5), attributes(7)
+ close(2), fcntl(2), getrlimit(2), posix_spawn_file_actions_addclose-
+ from_np(3C), proc(5), attributes(7)
-Oracle Solaris 11.4 9 Jul 2018 closefrom(3C)
+Oracle Solaris 11.4 9 May 2024 closefrom(3C)
diff -NurbBw 11.4.69/man3c/grantpt.3c 11.4.72/man3c/grantpt.3c
--- 11.4.69/man3c/grantpt.3c 2024-08-20 12:29:43.706971363 -0700
+++ 11.4.72/man3c/grantpt.3c 2024-08-20 12:30:00.814371932 -0700
@@ -1,7 +1,7 @@
grantpt(3C) Standard C Library Functions grantpt(3C)
NAME
- grantpt - grant access to the slave pseudo-terminal device
+ grantpt - grant access to the subsidiary pseudo-terminal device
SYNOPSIS
#include <stdlib.h>
@@ -9,13 +9,14 @@
int grantpt(int fildes);
DESCRIPTION
- The grantpt() function changes the mode and ownership of the slave
- pseudo-terminal device associated with its master pseudo-terminal coun-
- terpart. fildes is the file descriptor returned from a successful open
- of the master pseudo-terminal device. The user ID of the slave is set
- to the real UID of the calling process and the group ID is set to a re-
- served group. The permission mode of the slave pseudo-terminal is set
- to readable and writable by the owner and writable by the group.
+ The grantpt() function changes the mode and ownership of the subsidiary
+ pseudo-terminal device associated with its manager pseudo-terminal
+ counterpart. fildes is the file descriptor returned from a successful
+ open of the manager pseudo-terminal device. The user ID of the sub-
+ sidiary is set to the real UID of the calling process and the group ID
+ is set to a reserved group. The permission mode of the subsidiary
+ pseudo-terminal is set to readable and writable by the owner and
+ writable by the group.
RETURN VALUES
Upon successful completion, grantpt() returns 0. Otherwise, it returns
@@ -27,12 +28,12 @@
EBADF The fildes argument is not a valid open file descriptor.
- EINVAL The fildes argument is not associated with a master pseudo-
+ EINVAL The fildes argument is not associated with a manager pseudo-
terminal device.
- EACCES The corresponding slave pseudo-terminal device could not be
- accessed.
+ EACCES The corresponding subsidiary pseudo-terminal device could not
+ be accessed.
ATTRIBUTES
@@ -55,4 +56,4 @@
STREAMS Programming Guide
-Oracle Solaris 11.4 14 Aug 2006 grantpt(3C)
+Oracle Solaris 11.4 19 Jun 2024 grantpt(3C)
diff -NurbBw 11.4.69/man3c/openpty.3c 11.4.72/man3c/openpty.3c
--- 11.4.69/man3c/openpty.3c 2024-08-20 12:29:43.740715006 -0700
+++ 11.4.72/man3c/openpty.3c 2024-08-20 12:30:00.851392588 -0700
@@ -6,12 +6,12 @@
SYNOPSIS
#include <termios.h>
- int openpty(int *amaster, int *aslave, char *name,
+ int openpty(int *amanager, int *asubsidiary, char *name,
struct termios *termp, struct winsize *winp);
int login_tty(int fd);
- pid_t forkpty(int *amaster, char *name, struct termios *termp,
+ pid_t forkpty(int *amanager, char *name, struct termios *termp,
struct winsize *winp);
DESCRIPTION
@@ -20,35 +20,37 @@
The openpty() function finds an available pseudo-tty and returns file
- descriptors for the master and slave in amaster and aslave. If name is
- non-null, the filename of the slave is returned in name, a string of at
- least 32 characters. If termp is non-null, the terminal parameters of
- the slave will be set to the values in termp. If winp is non-null, the
- window size of the slave will be set to the values in winp. The
- openpty() function first attempts to allocate the pseudo-tty through
- the /dev/ptmx device using the posix_openpt command. It then invokes
- the grantpt(), unlockpt(), and ptsname() functions to obtain the path
- of the pseudo-terminal slave. It opens the pseudo-terminal slave, and
- attempts to set terminal attribute and window size of the pty slave if
- termp and winp are valid. Finally, the function returns the pty master
- fd, pty slave, and pty slave name to the caller. For more information,
- see pty, ptm and pts man pages.
+ descriptors for the manager and subsidiary in amanager and asubsidiary.
+ If name is non-null, the filename of the subsidiary is returned in
+ name, a string of at least 32 characters. If termp is non-null, the
+ terminal parameters of the subsidiary will be set to the values in
+ termp. If winp is non-null, the window size of the subsidiary will be
+ set to the values in winp. The openpty() function first attempts to al-
+ locate the pseudo-tty through the /dev/ptmx device using the
+ posix_openpt command. It then invokes the grantpt(), unlockpt(), and
+ ptsname() functions to obtain the path of the pseudo-terminal sub-
+ sidiary. It opens the pseudo-terminal subsidiary, and attempts to set
+ terminal attribute and window size of the pty subsidiary if termp and
+ winp are valid. Finally, the function returns the pty manager fd, pty
+ subsidiary, and pty subsidiary name to the caller. For more informa-
+ tion, see pty, ptm and pts man pages.
The login_tty() function prepares for a login on the tty fd, which can
- either be a real tty device, or a slave of the pseudo-tty as returned
- by the openpty() function. The function prepares for a login by creat-
- ing a new session, making fd the controlling terminal for the current
- process, setting fd to be the standard input, output, and error streams
- of the current process, and closing fd.
+ either be a real tty device, or a subsidiary of the pseudo-tty as re-
+ turned by the openpty() function. The function prepares for a login by
+ creating a new session, making fd the controlling terminal for the cur-
+ rent process, setting fd to be the standard input, output, and error
+ streams of the current process, and closing fd.
The forkpty() function combines the openpty(), fork(), and login_tty()
functions to create a new process attached to a pseudo-tty. The file
- descriptor of the master side of the pseudo-tty is returned in amaster,
- and the filename of the slave in name, if it is non-null. The termp and
- winp parameters, if non-null, will determine the terminal attributes
- and window size of the slave side of the pseudo-terminal.
+ descriptor of the manager side of the pseudo-tty is returned in aman-
+ ager, and the filename of the subsidiary in name, if it is non-null.
+ The termp and winp parameters, if non-null, will determine the terminal
+ attributes and window size of the subsidiary side of the pseudo-termi-
+ nal.
RETURN VALUES
If a call to the openpty(), login_tty(), or forkpty() functions is not
@@ -72,8 +74,8 @@
EAGAIN Out of pseudo-terminal resources
- EACCES The corresponding slave pseudo-terminal device could not be
- accessed
+ EACCES The corresponding subsidiary pseudo-terminal device could not
+ be accessed
@@ -118,10 +120,10 @@
FILES
- /dev/ptmx Master clone device
+ /dev/ptmx Manager clone device
- /dev/pts/M Slave devices (M = 0 -> N-1)
+ /dev/pts/M Subsidiary devices (M = 0 -> N-1)
@@ -141,4 +143,4 @@
pty(4D), pts(4D), posix_openpt(3C), grantpt(3C), unlockpt(3C), pt-
sname(3C), getrlimit(2)
-Oracle Solaris 11.4 17 Aug 2018 openpty(3C)
+Oracle Solaris 11.4 19 Jun 2024 openpty(3C)
diff -NurbBw 11.4.69/man3c/posix_openpt.3c 11.4.72/man3c/posix_openpt.3c
--- 11.4.69/man3c/posix_openpt.3c 2024-08-20 12:29:43.771769015 -0700
+++ 11.4.72/man3c/posix_openpt.3c 2024-08-20 12:30:00.879137997 -0700
@@ -10,7 +10,7 @@
int posix_openpt(int oflag);
DESCRIPTION
- The posix_openpt() function establishes a connection between a master
+ The posix_openpt() function establishes a connection between a manager
device for a pseudo-terminal and a file descriptor. The file descriptor
is used by other I/O functions that refer to that pseudo-terminal.
@@ -33,7 +33,7 @@
The behavior of other values for the oflag argument is unspecified.
RETURN VALUES
- Upon successful completion, the posix_openpt() function opens a master
+ Upon successful completion, the posix_openpt() function opens a manager
pseudo-terminal device and returns a non-negative integer representing
the lowest numbered unused file descriptor. Otherwise, -1 is returned
and errno is set to indicate the error.
@@ -67,35 +67,36 @@
The following example opens a pseudo-terminal and returns the name of
- the slave device and a file descriptor.
+ the subsidiary device and a file descriptor.
#include <fcntl.h>
#include <stdio.h>
- int masterfd, slavefd;
- char *slavedevice;
+ int managerfd, subsidiaryfd;
+ char *subsidiarydevice;
- masterfd = posix_openpt(O_RDWR|O_NOCTTY);
+ managerfd = posix_openpt(O_RDWR|O_NOCTTY);
- if (masterfd == -1
- || grantpt (masterfd) == -1
- || unlockpt (masterfd) == -1
- || (slavedevice = ptsname (masterfd)) == NULL)
+ if (managerfd == -1
+ || grantpt (managerfd) == -1
+ || unlockpt (managerfd) == -1
+ || (subsidiarydevice = ptsname (managerfd)) == NULL)
return -1;
- printf("slave device is: %s\n", slavedevice);
+ printf("subsidiary device is: %s\n", subsidiarydevice);
- slavefd = open(slave, O_RDWR|O_NOCTTY);
- if (slavefd < 0)
+ subsidiaryfd = open(subsidiary, O_RDWR|O_NOCTTY);
+ if (subsidiaryfd < 0)
return -1;
USAGE
This function provides a method for portably obtaining a file descrip-
- tor of a master terminal device for a pseudo-terminal. The grantpt(3C)
+ tor of a manager terminal device for a pseudo-terminal. The grantpt(3C)
and ptsname(3C) functions can be used to manipulate mode and ownership
- permissions and to obtain the name of the slave device, respectively.
+ permissions and to obtain the name of the subsidiary device, respec-
+ tively.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -115,4 +116,4 @@
open(2), grantpt(3C), ptsname(3C), unlockpt(3C), spawn.h(3HEAD), at-
tributes(7), standards(7)
-Oracle Solaris 11.4 17 Aug 2018 posix_openpt(3C)
+Oracle Solaris 11.4 19 Jun 2024 posix_openpt(3C)
diff -NurbBw 11.4.69/man3c/ptsname.3c 11.4.72/man3c/ptsname.3c
--- 11.4.69/man3c/ptsname.3c 2024-08-20 12:29:43.800590880 -0700
+++ 11.4.72/man3c/ptsname.3c 2024-08-20 12:30:00.905787574 -0700
@@ -1,7 +1,7 @@
ptsname(3C) Standard C Library Functions ptsname(3C)
NAME
- ptsname - get name of the slave pseudo-terminal device
+ ptsname - get name of the subsidiary pseudo-terminal device
SYNOPSIS
#include <stdlib.h>
@@ -9,20 +9,20 @@
char *ptsname(int fildes);
DESCRIPTION
- The ptsname() function returns the name of the slave pseudo-terminal
- device associated with a master pseudo-terminal device. fildes is a
- file descriptor returned from a successful open of the master device.
- ptsname() returns a pointer to a string containing the null-terminated
- path name of the slave device of the form /dev/pts/N, where N is a non-
- negative integer.
+ The ptsname() function returns the name of the subsidiary pseudo-termi-
+ nal device associated with a manager pseudo-terminal device. fildes is
+ a file descriptor returned from a successful open of the manager de-
+ vice. ptsname() returns a pointer to a string containing the null-ter-
+ minated path name of the subsidiary device of the form /dev/pts/N,
+ where N is a non-negative integer.
RETURN VALUES
Upon successful completion, the function ptsname() returns a pointer to
- a string which is the name of the pseudo-terminal slave device. This
- value points to a static data area that is overwritten by each call to
- ptsname(). Upon failure, ptsname() returns NULL. This could occur if
- fildes is an invalid file descriptor or if the slave device name does
- not exist in the file system.
+ a string which is the name of the pseudo-terminal subsidiary device.
+ This value points to a static data area that is overwritten by each
+ call to ptsname(). Upon failure, ptsname() returns NULL. This could oc-
+ cur if fildes is an invalid file descriptor or if the subsidiary device
+ name does not exist in the file system.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -45,4 +45,4 @@
STREAMS Programming Guide
-Oracle Solaris 11.4 9 Jul 2018 ptsname(3C)
+Oracle Solaris 11.4 19 Jun 2024 ptsname(3C)
diff -NurbBw 11.4.69/man3c/unlockpt.3c 11.4.72/man3c/unlockpt.3c
--- 11.4.69/man3c/unlockpt.3c 2024-08-20 12:29:43.828245959 -0700
+++ 11.4.72/man3c/unlockpt.3c 2024-08-20 12:30:00.933239744 -0700
@@ -1,7 +1,7 @@
unlockpt(3C) Standard C Library Functions unlockpt(3C)
NAME
- unlockpt - unlock a pseudo-terminal master/slave pair
+ unlockpt - unlock a pseudo-terminal manager/subsidiary pair
SYNOPSIS
#include <stdlib.h>
@@ -9,12 +9,12 @@
int unlockpt(int fildes);
DESCRIPTION
- The unlockpt() function unlocks the slave pseudo-terminal device asso-
- ciated with the master to which fildes refers.
+ The unlockpt() function unlocks the subsidiary pseudo-terminal device
+ associated with the manager to which fildes refers.
- Portable applications must call unlockpt() before opening the slave
- side of a pseudo-terminal device.
+ Portable applications must call unlockpt() before opening the sub-
+ sidiary side of a pseudo-terminal device.
RETURN VALUES
Upon successful completion, unlockpt() returns 0. Otherwise, it returns
@@ -27,7 +27,7 @@
ing.
- EINVAL The fildes argument is not associated with a master pseudo-
+ EINVAL The fildes argument is not associated with a manager pseudo-
terminal device.
@@ -51,4 +51,4 @@
STREAMS Programming Guide
-Oracle Solaris 11.4 14 Aug 2002 unlockpt(3C)
+Oracle Solaris 11.4 19 Jun 2024 unlockpt(3C)
diff -NurbBw 11.4.69/man4/cpr.4 11.4.72/man4/cpr.4
--- 11.4.69/man4/cpr.4 2024-08-20 12:29:43.863785265 -0700
+++ 11.4.72/man4/cpr.4 2024-08-20 12:30:00.962855832 -0700
@@ -54,7 +54,7 @@
cycle. This largely depends on the underlying network protocol and the
applications involved. In general, applications that retry and automat-
ically reestablish connections continues to operate transparently on a
- resume operation; those applications that do not likely fails.
+ resume operation; those applications that do not likely fail.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -79,8 +79,6 @@
Suspend-resume is currently supported only on a limited set of hardware
- platforms. Please see the book Using Power Management for a complete
- list of platforms that support system Power Management. See uname(2) to
- programmatically determine if the machine supports suspend-resume.
+ platforms.
-Oracle Solaris 11.4 13 Nov 2020 cpr(4)
+Oracle Solaris 11.4 14 Jun 2024 cpr(4)
diff -NurbBw 11.4.69/man4/FSS.4 11.4.72/man4/FSS.4
--- 11.4.69/man4/FSS.4 2024-08-20 12:29:43.898749249 -0700
+++ 11.4.72/man4/FSS.4 2024-08-20 12:30:01.005119349 -0700
@@ -132,10 +131,10 @@
# priocntl -s -c FSS -i pid 1
-CONFIGURING SCHEDULER WITH DISPADMIN
+CONFIGURING THE SCHEDULER WITH DISPADMIN
You can use the dispadmin(8) command to examine and tune the FSS sched-
- uler's time quantum value. Time quantum is the amount of time that a
- thread is allowed to run before it must relinquish the processor. The
+ uler's time quantum value. The time quantum is the amount of time that
+ a thread is allowed to run before it must relinquish the processor. The
following example dumps the current time quantum for the fair share
scheduler:
@@ -151,13 +150,11 @@
-
-
The value of the QUANTUM represents some fraction of a second with the
fractional value determined by the reciprocal value of RES. With the
- default value of RES = 1000, the reciprocal of 1000 is .001, or mil-
- liseconds. Thus, by default, the QUANTUM value represents the time
- quantum in milliseconds.
+ default value of RES=1000, the reciprocal of 1000 is .001, or millisec-
+ onds. Thus, by default, the QUANTUM value represents the time quantum
+ in milliseconds.
If you change the RES value using dispadmin with the -r option, you
@@ -187,4 +184,4 @@
Administering Resource Management in Oracle Solaris 11.4
-Oracle Solaris 11.4 27 Nov 2017 FSS(4)
+Oracle Solaris 11.4 14 Jun 2024 FSS(4)
diff -NurbBw 11.4.69/man4/Intro.4 11.4.72/man4/Intro.4
--- 11.4.69/man4/Intro.4 2024-08-20 12:29:43.927113571 -0700
+++ 11.4.72/man4/Intro.4 2024-08-20 12:30:01.037457413 -0700
@@ -13,9 +13,9 @@
This section contains the following major collections:
(4D) The system provides drivers for a variety of hardware devices,
- such as disk, magnetic tapes, serial communication lines,
- mice, and frame buffers, as well as virtual devices such as
- pseudo-terminals and windows.
+ such as disk, tapes, serial communication lines, and network
+ interface controllers, as well as virtual devices such as
+ pseudo-terminals and the null device.
This section describes special files that refer to specific
hardware peripherals and device drivers. STREAMS device dri-
@@ -31,25 +31,25 @@
All device special files are located under the /devices direc-
tory. The /devices directory hierarchy attempts to mirror the
- hierarchy of system busses, controllers, and devices config-
- ured on the system. Logical device names for special files in
- /devices are located under the /dev directory. Although not
- every special file under /devices will have a corresponding
- logical entry under /dev, whenever possible, an application
- should reference a device using the logical name for the de-
- vice. Logical device names are listed in the FILES section of
- the page for the device in question.
+ hierarchy of system buses, controllers, and devices configured
+ on the system. Logical device names for special files in /de-
+ vices are located under the /dev directory. Although not every
+ special file under /devices will have a corresponding logical
+ entry under /dev, whenever possible, an application should
+ reference a device using the logical name for the device. Log-
+ ical device names are listed in the FILES section of the page
+ for the device in question.
This section also describes driver configuration where applic-
able. Many device drivers have a driver configuration file of
the form driver_name.conf associated with them (see dri-
ver.conf(5)). The configuration information stored in the dri-
ver configuration file is used to configure the driver and the
- device. Driver configuration files are located in /kernel/drv
- and /usr/kernel/drv. Driver configuration files for platform
- dependent drivers are located in /platform/`uname -i`/ker-
- nel/drv where `uname -i` is the output of the uname(1) com-
- mand with the -i option.
+ device. Driver configuration files provided with the driver
+ are located in /kernel/drv and /usr/kernel/drv. Driver config-
+ uration files for platform dependent drivers are located in
+ /platform/`uname -i`/kernel/drv where `uname -i` is the output
+ of the uname(1) command with the -i option.
Some driver configuration files may contain user configurable
properties. These properties may be set in user-administered
@@ -65,8 +65,8 @@
change.
- (4FS) This section describes the programmatic interface for several
- file systems supported by Oracle Solaris.
+ (4FS) This section describes file systems supported by Oracle So-
+ laris.
(4I) This section describes ioctl requests which apply to a class
@@ -78,12 +78,12 @@
listed in section 4I.
- (4M) This section describes STREAMS modules. Note that STREAMS dri-
- vers are discussed in section 4D. streamio(4I) contains a list
- of ioctl requests used to manipulate STREAMS modules and in-
- terface with the STREAMS framework. Ioctl requests specific to
- a STREAMS module will be discussed on the man page for that
- module.
+ (4M) This section describes STREAMS modules other than device dri-
+ vers. Note that STREAMS drivers are discussed in section 4D.
+ streamio(4I) contains a list of ioctl requests used to manipu-
+ late STREAMS modules and interface with the STREAMS framework.
+ Ioctl requests specific to a STREAMS module will be discussed
+ on the man page for that module.
(4P) This section describes various network protocols available in
@@ -91,21 +91,23 @@
Oracle Solaris supports both socket-based and STREAMS-based
network communications. The Internet protocol family, de-
- scribed in inet(4P), is the primary protocol family supported
- by Oracle Solaris, although the system can support a number of
- others. The raw interface provides low-level services, such as
- packet fragmentation and reassembly, routing, addressing, and
- basic transport for socket-based implementations. Facilities
- for communicating using an Internet-family protocol are gener-
- ally accessed by specifying the AF_INET address family when
- binding a socket; see socket(3C) for details.
+ scribed in inet(4P) and inet6(4P), is the primary protocol
+ family supported by Oracle Solaris, although the system can
+ support a number of others. The raw interface provides low-
+ level services, such as packet fragmentation and reassembly,
+ routing, addressing, and basic transport for socket-based im-
+ plementations. Facilities for communicating using an Internet-
+ family protocol are generally accessed by specifying the
+ AF_INET or AF_INET6 address family when binding a socket; see
+ socket(3C) for details.
Major protocols in the Internet family include:
o The Internet Protocol (IP) itself, which supports
the universal datagram format, as described in
- ip(4P). This is the default protocol for SOCK_RAW
- type sockets within the AF_INET domain.
+ ip(4P) and ip6(4P). These are the default protocols
+ for SOCK_RAW type sockets within the AF_INET and
+ AF_INET6 domains respectively.
o The Transmission Control Protocol (TCP); see
@@ -122,17 +124,17 @@
o The Internet Control Message Protocol (ICMP); see
- icmp(4P).
+ icmp(4P) and icmp6(4P).
SEE ALSO
add_drv(8), update_drv(8), rem_drv(8), Intro(3), ioctl(2), socket(3C),
- driver.conf(5), arp(4P), icmp(4P), inet(4P), ip(4P), mtio(4I), st(4D),
- streamio(4I), tcp(4P), udp(4P)
+ driver.conf(5), arp(4P), icmp(4P), icmp6(4P), inet(4P), inet6(4P),
+ ip(4P), ip6(4P), mtio(4I), st(4D), streamio(4I), tcp(4P), udp(4P)
- Managing System Services in Oracle Solaris 11.4
+ Managing Devices in Oracle Solaris 11.4
STREAMS Programming Guide
@@ -140,4 +142,4 @@
Writing Device Drivers in Oracle Solaris 11.4
-Oracle Solaris 11.4 08 Aug 2018 Intro(4)
+Oracle Solaris 11.4 14 Jun 2024 Intro(4)
diff -NurbBw 11.4.69/man4d/bpf.4d 11.4.72/man4d/bpf.4d
--- 11.4.69/man4d/bpf.4d 2024-08-20 12:29:43.966419437 -0700
+++ 11.4.72/man4d/bpf.4d 2024-08-20 12:30:01.076819420 -0700
@@ -9,11 +9,18 @@
those destined for other hosts, are accessible through this mechanism.
- The packet filter appears as a character special device, /dev/bpf. Af-
- ter opening the device, the file descriptor must be bound to a specific
- network interface with the BIOSETIF ioctl. A specific interface can be
- shared by multiple listeners, and the filter underlying each descriptor
- sees an identical packet stream.
+ The packet filter appears as a character special device, /dev/bpf.
+ Opening the device for reading requires that either the
+ {PRIV_NET_RAWACCESS} or {PRIV_NET_OBSERVABILITY} privilege is asserted
+ in the effective set of the process. Opening the device for writing re-
+ quires that the {PRIV_NET_RAWACCESS} privilege is asserted in the ef-
+ fective set of the process.
+
+
+ After opening the device, the file descriptor must be bound to a spe-
+ cific network interface with the BIOSETIF ioctl. A specific interface
+ can be shared by multiple listeners, and the filter underlying each de-
+ scriptor sees an identical packet stream.
Associated with each open instance of a bpf file is a user-settable
@@ -660,4 +667,4 @@
Immediate mode and the read timeout are misguided features. This func-
tionality can be emulated with non-blocking mode and select(3C).
-Oracle Solaris 11.4 15 Mar 2024 bpf(4D)
+Oracle Solaris 11.4 9 May 2024 bpf(4D)
diff -NurbBw 11.4.69/man4d/ptm.4d 11.4.72/man4d/ptm.4d
--- 11.4.69/man4d/ptm.4d 2024-08-20 12:29:43.994748373 -0700
+++ 11.4.72/man4d/ptm.4d 2024-08-20 12:30:01.104017229 -0700
@@ -1,66 +1,66 @@
ptm(4D) Device Drivers & /dev files ptm(4D)
NAME
- ptm - STREAMS pseudo-tty master driver
+ ptm - STREAMS pseudo-tty manager driver
DESCRIPTION
The pseudo-tty subsystem simulates a terminal connection, where the
- master side represents the terminal and the slave represents the user
- process's special device end point. The master device is set up as a
- cloned device where its major device number is the major for the clone
- device and its minor device number is the major for the ptm driver.
- There are no nodes in the file system for master devices. The master
- pseudo driver is opened using the open(2) system call with /dev/ptmx as
- the device parameter. The clone open finds the next available minor de-
- vice for the ptm major device.
-
-
- A master device is available only if it and its corresponding slave de-
- vice are not already open. When the master device is opened, the corre-
- sponding slave device is automatically locked out. Only one open is al-
- lowed on a master device. Multiple opens are allowed on the slave de-
- vice. After both the master and slave have been opened, the user has
- two file descriptors which are the end points of a full duplex connec-
- tion composed of two streams which are automatically connected at the
- master and slave drivers. The user may then push modules onto either
- side of the stream pair.
+ manager side represents the terminal and the subsidiary represents the
+ user process's special device end point. The manager device is set up
+ as a cloned device where its major device number is the major for the
+ clone device and its minor device number is the major for the ptm dri-
+ ver. There are no nodes in the file system for manager devices. The
+ manager pseudo driver is opened using the open(2) system call with
+ /dev/ptmx as the device parameter. The clone open finds the next avail-
+ able minor device for the ptm major device.
+
+
+ A manager device is available only if it and its corresponding sub-
+ sidiary device are not already open. When the manager device is opened,
+ the corresponding subsidiary device is automatically locked out. Only
+ one open is allowed on a manager device. Multiple opens are allowed on
+ the subsidiary device. After both the manager and subsidiary have been
+ opened, the user has two file descriptors which are the end points of a
+ full duplex connection composed of two streams which are automatically
+ connected at the manager and subsidiary drivers. The user may then push
+ modules onto either side of the stream pair.
- The master and slave drivers pass all messages to their adjacent
+ The manager and subsidiary drivers pass all messages to their adjacent
queues. Only the M_FLUSH needs some processing. Because the read queue
of one side is connected to the write queue of the other, the FLUSHR
- flag is changed to the FLUSHW flag and vice versa. When the master de-
- vice is closed an M_HANGUP message is sent to the slave device which
- will render the device unusable. The process on the slave side gets the
- errno EIO when attempting to write on that stream but it will be able
- to read any data remaining on the stream head read queue. When all the
- data has been read, read() returns 0 indicating that the stream can no
- longer be used. On the last close of the slave device, a 0-length mes-
- sage is sent to the master device. When the application on the master
- side issues a read() or getmsg() and 0 is returned, the user of the
- master device decides whether to issue a close() that dismantles the
- pseudo-terminal subsystem. If the master device is not closed, the
- pseudo-tty subsystem will be available to another user to open the
- slave device.
+ flag is changed to the FLUSHW flag and vice versa. When the manager de-
+ vice is closed an M_HANGUP message is sent to the subsidiary device
+ which will render the device unusable. The process on the subsidiary
+ side gets the errno EIO when attempting to write on that stream but it
+ will be able to read any data remaining on the stream head read queue.
+ When all the data has been read, read() returns 0 indicating that the
+ stream can no longer be used. On the last close of the subsidiary de-
+ vice, a 0-length message is sent to the manager device. When the appli-
+ cation on the manager side issues a read() or getmsg() and 0 is re-
+ turned, the user of the manager device decides whether to issue a
+ close() that dismantles the pseudo-terminal subsystem. If the manager
+ device is not closed, the pseudo-tty subsystem will be available to an-
+ other user to open the subsidiary device.
- If O_NONBLOCK or O_NDELAY is set, read on the master side returns -1
+ If O_NONBLOCK or O_NDELAY is set, read on the manager side returns -1
with errno set to EAGAIN if no data is available, and write returns -1
with errno set to EAGAIN if there is internal flow control.
IOCTLS
- The master driver supports the ISPTM and UNLKPT ioctls that are used by
- the functions grantpt(3C), unlockpt(3C), and ptsname(3C). The ioctl
- ISPTM determines whether the file descriptor is that of an open master
- device. On success, it returns the 0. The ioctl UNLKPT unlocks the mas-
- ter and slave devices. It returns 0 on success. On failure, the errno
- is set to EINVAL indicating that the master device is not open.
+ The manager driver supports the ISPTM and UNLKPT ioctls that are used
+ by the functions grantpt(3C), unlockpt(3C), and ptsname(3C). The ioctl
+ ISPTM determines whether the file descriptor is that of an open manager
+ device. On success, it returns the 0. The ioctl UNLKPT unlocks the man-
+ ager and subsidiary devices. It returns 0 on success. On failure, the
+ errno is set to EINVAL indicating that the manager device is not open.
FILES
- /dev/ptmx master clone device
+ /dev/ptmx manager clone device
- /dev/pts/N slave devices (N = 1 -> number of ptys available)
+ /dev/pts/N subsidiary devices (N = 1 -> number of ptys available)
SEE ALSO
@@ -72,4 +72,10 @@
Oracle Solaris 11.4 Tunable Parameters Reference Manual
-Oracle Solaris 11.4 15 Mar 2024 ptm(4D)
+NOTES
+ In previous releases and earlier standards, manager devices were re-
+ ferred to as "master" devices. This release has adopted the "manager"
+ terminology used in the POSIX.1-2024 and The Open Group Standard Base
+ Specifications, Issue 8 standards.
+
+Oracle Solaris 11.4 19 Jun 2024 ptm(4D)
diff -NurbBw 11.4.69/man4d/pts.4d 11.4.72/man4d/pts.4d
--- 11.4.69/man4d/pts.4d 2024-08-20 12:29:44.022247336 -0700
+++ 11.4.72/man4d/pts.4d 2024-08-20 12:30:01.133462042 -0700
@@ -1,80 +1,82 @@
pts(4D) Device Drivers & /dev files pts(4D)
NAME
- pts - STREAMS pseudo-tty slave driver
+ pts - STREAMS pseudo-tty subsidiary driver
DESCRIPTION
The pseudo-tty subsystem simulates a terminal connection, where the
- master side represents the terminal and the slave represents the user
- process's special device end point. The master device is set up as a
- cloned device where its major device number is the major for the clone
- device and its minor device number is the major for the ptm driver.
- There are no nodes in the filesystem for master devices. The master
- pseudo driver is opened using the open system call with /dev/ptmx as
- the device parameter. For more information, see the open(2) man page.
- The clone open finds the next available minor device for the ptm major
- device. A master device is available only if it and its corresponding
- slave device are not already open. When the master device is opened,
- the corresponding slave device is automatically locked out. No user may
- open that slave device until its permissions are adjusted and the de-
- vice unlocked by calling the functions grantpt() and unlockpt(). For
- more information, see the grantpt(3C) and unlockpt(3C) man pages. The
- user can then invoke the open system call with the name that is re-
- turned by the ptsname() function. For more information, see the pt-
- sname(3C) man page. See the example below.
-
-
- Only one open is allowed on a master device. Multiple opens are allowed
- on the slave device. After both the master and slave have been opened,
- the user has two file descriptors which are the end points of a full
- duplex connection composed of two streams which are automatically con-
- nected at the master and slave drivers. The user may then push modules
- onto either side of the stream pair. The autopush(8) system will push
- the required STREAMS modules for terminal semantics on first open.
+ manager side represents the terminal and the subsidiary represents the
+ user process's special device end point. The manager device is set up
+ as a cloned device where its major device number is the major for the
+ clone device and its minor device number is the major for the ptm dri-
+ ver. There are no nodes in the filesystem for manager devices. The man-
+ ager pseudo driver is opened using the open system call with /dev/ptmx
+ as the device parameter. For more information, see the open(2) man
+ page. The clone open finds the next available minor device for the ptm
+ major device. A manager device is available only if it and its corre-
+ sponding subsidiary device are not already open. When the manager de-
+ vice is opened, the corresponding subsidiary device is automatically
+ locked out. No user may open that subsidiary device until its permis-
+ sions are adjusted and the device unlocked by calling the functions
+ grantpt() and unlockpt(). For more information, see the grantpt(3C) and
+ unlockpt(3C) man pages. The user can then invoke the open system call
+ with the name that is returned by the ptsname() function. For more in-
+ formation, see the ptsname(3C) man page. See the example below.
+
+
+ Only one open is allowed on a manager device. Multiple opens are al-
+ lowed on the subsidiary device. After both the manager and subsidiary
+ have been opened, the user has two file descriptors which are the end
+ points of a full duplex connection composed of two streams which are
+ automatically connected at the manager and subsidiary drivers. The user
+ may then push modules onto either side of the stream pair. The auto-
+ push(8) system will push the required STREAMS modules for terminal se-
+ mantics on first open.
- The master and slave drivers pass all messages to their adjacent
+ The manager and subsidiary drivers pass all messages to their adjacent
queues. Only the M_FLUSH needs some processing. Because the read queue
of one side is connected to the write queue of the other, the FLUSHR
- flag is changed to the FLUSHW flag and vice versa. When the master de-
- vice is closed an M_HANGUP message is sent to the slave device which
- will render the device unusable. The process on the slave side gets the
- errno EIO when attempting to write on that stream but it will be able
- to read any data remaining on the stream head read queue. When all the
- data has been read, read returns 0 indicating that the stream can no
- longer be used. On the last close of the slave device, a 0-length mes-
- sage is sent to the master device. When the application on the master
- side issues a read() or getmsg() and 0 is returned, the user of the
- master device decides whether to issue a close() that dismantles the
- pseudo-terminal subsystem. If the master device is not closed, the
- pseudo-tty subsystem will be available to another user to open the
- slave device. Since 0-length messages are used to indicate that the
- process on the slave side has closed and should be interpreted that way
- by the process on the master side, applications on the slave side
- should not write 0-length messages. If that occurs, the write returns
- 0, and the 0-length message is discarded by the ptem module.
+ flag is changed to the FLUSHW flag and vice versa. When the manager de-
+ vice is closed an M_HANGUP message is sent to the subsidiary device
+ which will render the device unusable. The process on the subsidiary
+ side gets the errno EIO when attempting to write on that stream but it
+ will be able to read any data remaining on the stream head read queue.
+ When all the data has been read, read returns 0 indicating that the
+ stream can no longer be used. On the last close of the subsidiary de-
+ vice, a 0-length message is sent to the manager device. When the appli-
+ cation on the manager side issues a read() or getmsg() and 0 is re-
+ turned, the user of the manager device decides whether to issue a
+ close() that dismantles the pseudo-terminal subsystem. If the manager
+ device is not closed, the pseudo-tty subsystem will be available to an-
+ other user to open the subsidiary device. Since 0-length messages are
+ used to indicate that the process on the subsidiary side has closed and
+ should be interpreted that way by the process on the manager side, ap-
+ plications on the subsidiary side should not write 0-length messages.
+ If that occurs, the write returns 0, and the 0-length message is dis-
+ carded by the ptem module.
The standard STREAMS system calls can access the pseudo-tty devices.
- The slave devices support the O_NDELAY and O_NONBLOCK flags.
+ The subsidiary devices support the O_NDELAY and O_NONBLOCK flags.
EXAMPLES
int fdm fds;
- char *slavename;
+ char *subsidiaryname;
extern char *ptsname();
- fdm = open("/dev/ptmx", O_RDWR); /* open master */
- grantpt(fdm); /* change permission of slave */
- unlockpt(fdm); /* unlock slave */
- slavename = ptsname(fdm); /* get name of slave */
- fds = open(slavename, O_RDWR); /* open slave */
+ fdm = open("/dev/ptmx", O_RDWR); /* open manager */
+ grantpt(fdm); /* change permission of subsidiary */
+ unlockpt(fdm); /* unlock subsidiary */
+ subsidiaryname = ptsname(fdm); /* get name of subsidiary */
+ fds = open(subsidiaryname, O_RDWR); /* open subsidiary */
FILES
- /dev/ptmx master clone device
+ /dev/ptmx manager clone device
- /dev/pts/N slave devices (N = 1 -> number of ptys available)
+ /dev/pts/N subsidiary devices (N = 1 -> number of ptys available)
SEE ALSO
@@ -87,16 +89,22 @@
Oracle Solaris 11.4 Tunable Parameters Reference Manual
+NOTES
+ In previous releases and earlier standards, subsidiary devices were re-
+ ferred to as "slave" devices. This release has adopted the "subsidiary"
+ terminology used in the POSIX.1-2024 and The Open Group Standard Base
+ Specifications, Issue 8 standards.
+
HISTORY
Prior to Oracle Solaris 11.4, the user needed to push the ptem and
- ldterm modules onto the slave side of the pseudo-terminal subsystem to
- get terminal semantics, and the ttcompat module on the slave side for
- BSD compatibility ioctl calls, but only if open() was called from a
- program not linked for XPG4 or later standards. If called from a pro-
- gram linked with values-xpg4.o or values-xpg6.o, then open() would au-
- tomatically push ptem, ldterm, and ttcompat modules onto the slave
- side, and callers pushing them as well would encounter unexpected be-
- havior.
+ ldterm modules onto the subsidiary side of the pseudo-terminal subsys-
+ tem to get terminal semantics, and the ttcompat module on the sub-
+ sidiary side for BSD compatibility ioctl calls, but only if open() was
+ called from a program not linked for XPG4 or later standards. If called
+ from a program linked with values-xpg4.o or values-xpg6.o, then open()
+ would automatically push ptem, ldterm, and ttcompat modules onto the
+ subsidiary side, and callers pushing them as well would encounter unex-
+ pected behavior.
Oracle Solaris 11.4 added these modules to /etc/iu.system.ap so that
@@ -108,4 +116,4 @@
Oracle Solaris 11.4 also added the openpty(3C) to encapsulate most of
this detail behind a portable interface.
-Oracle Solaris 11.4 9 Jul 2018 pts(4D)
+Oracle Solaris 11.4 19 Jun 2024 pts(4D)
diff -NurbBw 11.4.69/man4d/pty.4d 11.4.72/man4d/pty.4d
--- 11.4.69/man4d/pty.4d 2024-08-20 12:29:44.050861868 -0700
+++ 11.4.72/man4d/pty.4d 2024-08-20 12:30:01.178963788 -0700
@@ -6,15 +6,15 @@
DESCRIPTION
The pty driver provides support for a pair of devices collectively
known as a pseudo-terminal. The two devices comprising a pseudo-termi-
- nal are known as a controller and a slave. The slave device distin-
- guishes between the B0 baud rate and other baud rates specified in the
- c_cflag word of the termios structure, and the CLOCAL flag in that
+ nal are known as a manager and a subsidiary. The subsidiary device dis-
+ tinguishes between the B0 baud rate and other baud rates specified in
+ the c_cflag word of the termios structure, and the CLOCAL flag in that
word. It does not support any of the other termio(4I) device control
functions specified by flags in the c_cflag word of the termios struc-
ture and by the IGNBRK, IGNPAR, PARMRK, or INPCK flags in the c_iflag
word of the termios structure, as these functions apply only to asyn-
chronous serial ports. All other termio(4I) functions must be performed
- by STREAMS modules pushed atop the driver; when a slave device is
+ by STREAMS modules pushed atop the driver; when a subsidiary device is
opened, the ldterm(4M) and ttcompat(4M) STREAMS modules are automati-
cally pushed on top of the stream, providing the standard termio(4I)
interface.
@@ -22,31 +22,31 @@
Instead of having a hardware interface and associated hardware that
supports the terminal functions, the functions are implemented by an-
- other process manipulating the controller device of the pseudo-termi-
- nal.
+ other process manipulating the manager device of the pseudo-terminal.
- The controller and the slave devices of the pseudo-terminal are tightly
- connected. Any data written on the controller device is given to the
- slave device as input, as though it had been received from a hardware
- interface. Any data written on the slave terminal can be read from the
- controller device (rather than being transmitted from a UAR).
+ The manager and the subsidiary devices of the pseudo-terminal are
+ tightly connected. Any data written on the manager device is given to
+ the subsidiary device as input, as though it had been received from a
+ hardware interface. Any data written on the subsidiary terminal can be
+ read from the manager device (rather than being transmitted from a
+ UAR).
By default, 48 pseudo-terminal pairs are configured as follows:
- /dev/pty[p-r][0-9a-f] controller devices
- /dev/tty[p-r][0-9a-f] slave devices
+ /dev/pty[p-r][0-9a-f] manager devices
+ /dev/tty[p-r][0-9a-f] subsidiary devices
IOCTLS
- The standard set of termio ioctls are supported by the slave device.
- None of the bits in the c_cflag word have any effect on the pseudo-ter-
- minal, except that if the baud rate is set to B0, it will appear to the
- process on the controller device as if the last process on the slave
- device had closed the line; thus, setting the baud rate to B0 has the
- effect of "hanging up" the pseudo-terminal, just as it has the effect
- of "hanging up" a real terminal.
+ The standard set of termio ioctls are supported by the subsidiary de-
+ vice. None of the bits in the c_cflag word have any effect on the
+ pseudo-terminal, except that if the baud rate is set to B0, it will ap-
+ pear to the process on the manager device as if the last process on the
+ subsidiary device had closed the line; thus, setting the baud rate to
+ B0 has the effect of "hanging up" the pseudo-terminal, just as it has
+ the effect of "hanging up" a real terminal.
There is no notion of parity on a pseudo-terminal, so none of the flags
@@ -57,8 +57,8 @@
Input flow control is automatically performed; a process that attempts
- to write to the controller device will be blocked if too much uncon-
- sumed data is buffered on the slave device. The input flow control pro-
+ to write to the manager device will be blocked if too much unconsumed
+ data is buffered on the subsidiary device. The input flow control pro-
vided by the IXOFF flag in the c_iflag word is not supported.
@@ -69,9 +69,9 @@
return or alter the state of modem control lines are silently ignored.
- A few special ioctls are provided on the controller devices of pseudo-
- terminals to provide the functionality needed by applications programs
- to emulate real hardware interfaces:
+ A few special ioctls are provided on the manager devices of pseudo-ter-
+ minals to provide the functionality needed by applications programs to
+ emulate real hardware interfaces:
TIOCSTOP
@@ -90,11 +90,11 @@
The argument is a pointer to an int. If the value of the int is
non-zero, packet mode is enabled; if the value of the int is zero,
packet mode is disabled. When a pseudo-terminal is in packet mode,
- each subsequent read(2) from the controller device will return data
- written on the slave device preceded by a zero byte (symbolically
- defined as TIOCPKT_DATA), or a single byte reflecting control sta-
- tus information. In the latter case, the byte is an inclusive-or of
- zero or more of the bits:
+ each subsequent read(2) from the manager device will return data
+ written on the subsidiary device preceded by a zero byte (symboli-
+ cally defined as TIOCPKT_DATA), or a single byte reflecting control
+ status information. In the latter case, the byte is an inclusive-or
+ of zero or more of the bits:
TIOCPKT_FLUSHREAD
@@ -136,22 +136,22 @@
non-zero, remote mode is enabled; if the value of the int is zero,
remote mode is disabled. This mode can be enabled or disabled inde-
pendently of packet mode. When a pseudo-terminal is in remote mode,
- input to the slave device of the pseudo-terminal is flow controlled
- and not input edited (regardless of the mode the slave side of the
- pseudo-terminal). Each write to the controller device produces a
- record boundary for the process reading the slave device. In normal
- usage, a write of data is like the data typed as a line on the ter-
- minal; a write of 0 bytes is like typing an EOF character. Note:
- this means that a process writing to a pseudo-terminal controller
- in remote mode must keep track of line boundaries, and write only
- one line at a time to the controller. If, for example, it were to
- buffer up several NEWLINE characters and write them to the con-
- troller with one write(), it would appear to a process reading from
- the slave as if a single line containing several NEWLINE characters
- had been typed (as if, for example, a user had typed the LNEXT
- character before typing all but the last of those NEWLINE charac-
- ters). Remote mode can be used when doing remote line editing in a
- window manager, or whenever flow controlled input is required.
+ input to the subsidiary device of the pseudo-terminal is flow con-
+ trolled and not input edited (regardless of the mode the subsidiary
+ side of the pseudo-terminal). Each write to the manager device pro-
+ duces a record boundary for the process reading the subsidiary de-
+ vice. In normal usage, a write of data is like the data typed as a
+ line on the terminal; a write of 0 bytes is like typing an EOF
+ character. Note: this means that a process writing to a pseudo-ter-
+ minal manager in remote mode must keep track of line boundaries,
+ and write only one line at a time to the manager. If, for example,
+ it were to buffer up several NEWLINE characters and write them to
+ the manager with one write(), it would appear to a process reading
+ from the subsidiary as if a single line containing several NEWLINE
+ characters had been typed (as if, for example, a user had typed the
+ LNEXT character before typing all but the last of those NEWLINE
+ characters). Remote mode can be used when doing remote line editing
+ in a window manager, or whenever flow controlled input is required.
EXAMPLES
@@ -159,22 +159,29 @@
#include <sys/termios.h>
int fdm, fds;
- fdm = open("/dev/ptyp0", O_RDWR); /* open master */
- fds = open("/dev/ttyp0", O_RDWR); /* open slave */
+ fdm = open("/dev/ptyp0", O_RDWR); /* open manager */
+ fds = open("/dev/ttyp0", O_RDWR); /* open subsidiary */
FILES
- /dev/pty[p-z][0-9a-f] pseudo-terminal controller devices
+ /dev/pty[p-z][0-9a-f] pseudo-terminal manager devices
- /dev/tty[p-z][0-9a-f] pseudo-terminal slave devices
+ /dev/tty[p-z][0-9a-f] pseudo-terminal subsidiary devices
SEE ALSO
grantpt(3C), openpty(3C), termio(4I), ldterm(4M), ttcompat(4M)
NOTES
+ In previous releases and earlier standards, manager devices were re-
+ ferred to as "master" or "controller" devices, and subsidiary devices
+ were referred to as "slave" devices. This release has adopted the "man-
+ ager" and "subsidiary" terminology used in the POSIX.1-2024 and The
+ Open Group Standard Base Specifications, Issue 8 standards.
+
+
It is not possible to send an EOT by writing zero bytes in TIOCREMOTE
mode.
-Oracle Solaris 11.4 15 Mar 2024 pty(4D)
+Oracle Solaris 11.4 19 Jun 2024 pty(4D)
diff -NurbBw 11.4.69/man4fs/dcfs.4fs 11.4.72/man4fs/dcfs.4fs
--- 11.4.69/man4fs/dcfs.4fs 2024-08-20 12:29:44.078554816 -0700
+++ 11.4.72/man4fs/dcfs.4fs 2024-08-20 12:30:01.204693725 -0700
@@ -8,10 +8,10 @@
#include <sys/fs/decomp.h>
DESCRIPTION
- The dcfs filesystem is a layered filesystem that you use to compress
- data when writing to a file and decompress upon read. The primary func-
- tion of the dcfs filesystem is to compress individual files when con-
- structing a boot archive and when reading or booting from the archive.
+ The dcfs filesystem is a layered filesystem that compresses data when
+ writing to a file and decompresses upon read. The primary function of
+ the dcfs filesystem is to compress individual files when constructing a
+ boot archive and when reading or booting from the archive.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -27,6 +27,8 @@
ufs(4FS), attributes(7), boot(8), bootadm(8), fiocompress(8)
NOTES
- The dcfs compression/decompression file system works only with UFS.
+ The dcfs compression/decompression file system only works with UFS. To
+ use compression with a ZFS file system, see the compression property in
+ zfs(8).
-Oracle Solaris 11.4 28 Nov 2007 dcfs(4FS)
+Oracle Solaris 11.4 14 Jun 2024 dcfs(4FS)
diff -NurbBw 11.4.69/man4fs/dev.4fs 11.4.72/man4fs/dev.4fs
--- 11.4.69/man4fs/dev.4fs 2024-08-20 12:29:44.105085965 -0700
+++ 11.4.72/man4fs/dev.4fs 2024-08-20 12:30:01.232460272 -0700
@@ -17,7 +17,7 @@
rectly causing a lookup or readdir operation in the filesystem to oc-
cur. For example, you can discover a disk that was attached when the
system was powered down (and generate a name for that device) by invok-
- ing format(8)).
+ ing format(8).
The /dev/zvol/dsk and /dev/zvol/rdsk directories are generated based on
@@ -49,9 +49,9 @@
SEE ALSO
- devfsadm(8), format(8), zonecfg(8)
+ devfs(4FS), devfsadm(8), format(8), zonecfg(8)
NOTES
The global /dev instance cannot be unmounted.
-Oracle Solaris 11.4 11 Dec 2020 dev(4FS)
+Oracle Solaris 11.4 14 Jun 2024 dev(4FS)
diff -NurbBw 11.4.69/man4fs/devchassis.4fs 11.4.72/man4fs/devchassis.4fs
--- 11.4.69/man4fs/devchassis.4fs 2024-08-20 12:29:44.132580007 -0700
+++ 11.4.72/man4fs/devchassis.4fs 2024-08-20 12:30:01.258392742 -0700
@@ -20,7 +20,7 @@
An empty receptacle is represented as an empty directory.
- If an fmadm(8)--managed <alias-id> exists, then the <chassis-
+ If an <alias-id> managed by fmadm(8) exists, then the <chassis-
name>.<chassis-serial> is replaced by a managed <alias-id>. A managed
<alias-id> can establish the physical location of chassis, like a
building, lab, rack, and chassis U-number range inside the rack.
@@ -76,4 +76,4 @@
Gaps in fmd(8) topology representation result in gaps in the /dev/chas-
sis name space.
-Oracle Solaris 11.4 14 May 2018 devchassis(4FS)
+Oracle Solaris 11.4 14 Jun 2024 devchassis(4FS)
diff -NurbBw 11.4.69/man4fs/devfs.4fs 11.4.72/man4fs/devfs.4fs
--- 11.4.69/man4fs/devfs.4fs 2024-08-20 12:29:44.162859197 -0700
+++ 11.4.72/man4fs/devfs.4fs 2024-08-20 12:30:01.295150246 -0700
@@ -46,7 +46,7 @@
SEE ALSO
- vfstab(5), devfsadm(8), attach(9E)
+ dev(4FS), devfsadm(8), attach(9E)
NOTES
The /devices name space cannot be unmounted.
@@ -56,4 +56,4 @@
artifact and subject to incompatible change or removal without notifi-
cation.
-Oracle Solaris 11.4 11 Dec 2020 devfs(4FS)
+Oracle Solaris 11.4 14 Jun 2024 devfs(4FS)
diff -NurbBw 11.4.69/man4fs/hsfs.4fs 11.4.72/man4fs/hsfs.4fs
--- 11.4.69/man4fs/hsfs.4fs 2024-08-20 12:29:44.190861021 -0700
+++ 11.4.72/man4fs/hsfs.4fs 2024-08-20 12:30:01.328918120 -0700
@@ -1,24 +1,24 @@
hsfs(4FS) File Systems hsfs(4FS)
NAME
- hsfs - High Sierra & ISO 9660 CD-ROM file system
+ hsfs - High Sierra & ISO 9660 file system
DESCRIPTION
HSFS is a file system type that allows users to access files on High
- Sierra or ISO 9660 format CD-ROM disks from within the Oracle Solaris
- operating system. Once mounted, a HSFS file system provides standard
- Oracle Solaris read-only file system operations and semantics, meaning
- that you can read and list files in a directory on a High Sierra or ISO
- 9660 CD-ROM and applications can use standard UNIX system calls on
- these files and directories.
+ Sierra or ISO 9660 format disks or disk images from within the Oracle
+ Solaris operating system. Once mounted, a HSFS file system provides
+ standard Oracle Solaris read-only file system operations and semantics,
+ meaning that you can read and list files in a directory on a High
+ Sierra or ISO 9660 media and applications can use standard UNIX system
+ calls on these files and directories.
- This file system contains support for Rock Ridge, ISO 9660 Version 2
+ This file system contains support for Rock Ridge, ISO 9660 Version 2,
and Joliet extensions. These extensions provide support for file names
with a length of at least 207 bytes, but only Rock Ridge extensions
(with the exception of writability and hard links) can provide file
system semantics and file types as they are found in UFS. The presence
- of Rock Ridge, ISO 9660 Version 2 and Joliet is autodetected and the
+ of Rock Ridge, ISO 9660 Version 2, and Joliet is autodetected and the
best-suitable available extension is used by the HSFS driver for file
name and attribute lookup.
@@ -45,57 +43,58 @@
By default, Rock Ridge extensions are used if available, otherwise ISO
- 9660 Version 2, then Joliet are used. If neither extension is present
- HSFS defaults to the standard capabilities of ISO 9660. Since so-called
- hybrid CD-ROMs that contain multiple extensions are possible, you can
- use the following mount options to deliberately disable the search for
- a specific extension or to force the use of a specific extension even
- if a preferable type is present:
+ 9660 Version 2, then Joliet are used. If none of the extensions are
+ present HSFS defaults to the standard capabilities of ISO 9660. Since
+ so-called hybrid disks that contain multiple extensions are possible,
+ you can use the following mount options to deliberately disable the
+ search for a specific extension or to force the use of a specific ex-
+ tension even if a preferred type is present:
mount -F hsfs -o ro,nrr device-special directory-name
- Mount options are:
+ Mount options for selecting ISO 9660 extensions are:
+ rr Request HSFS to use Rock Ridge extensions, if present. This
+ is the default behavior and does not need to be explicitly
+ specified.
- rr--request HSFS to use Rock Ridge extensions, if present. This is the
- default behavior and does not need to be explicitly specified.
-
- nrr--disable detection and use of Rock Ridge extensions, even if
+ nrr Disable detection and use of Rock Ridge extensions, even if
present.
- vers2--request HSFS to use ISO 9660 Version 2 extensions, even if Rock
- Ridge is available.
+ vers2 Request HSFS to use ISO 9660 Version 2 extensions, even if
+ Rock Ridge is available.
+
+ novers2 Disable detection and use of ISO 9660 Version 2 extensions.
- novers2--disable detection and use of ISO 9660 Version 2 extensions.
+ joliet Request HSFS to use Joliet extensions, even if Rock Ridge
+ or ISO 9660 Version 2 extensions are available.
- joliet--request HSFS to use Joliet extensions, even if Rock Ridge or
- ISO 9660 Version 2 extensions are available.
+ nojoliet Disable detection and use of Joliet extensions.
- nojoliet--disable detection and use of Joliet extensions.
- Files on a High Sierra or ISO 9660 CD-ROM disk have names of the form
- filename.ext;version, where filename and the optional ext consist of a
- sequence of uppercase alphanumeric characters (including '_'), while
- the version consists of a sequence of digits, representing the version
- number of the file. HSFS converts all the uppercase characters in a
- file name to lowercase, and truncates the ';' and version information.
- If more than one version of a file is present on the CD-ROM, only the
- file with the highest version number is accessible.
+ Files on a High Sierra or ISO 9660 disk have names of the form file-
+ name.ext;version, where filename and the optional ext consist of a se-
+ quence of uppercase alphanumeric characters (including '_'), while the
+ version consists of a sequence of digits, representing the version num-
+ ber of the file. HSFS converts all the uppercase characters in a file
+ name to lowercase, and truncates the ';' and version information. If
+ more than one version of a file is present on the disk, only the file
+ with the highest version number is accessible.
Conversion of uppercase to lowercase characters may be disabled by us-
ing the -o nomaplcase option to mount(8). (See mount_hsfs(8)).
- If the CD-ROM contains Rock Ridge, ISO 9660 version 2 or Joliet exten-
+ If the disk contains Rock Ridge, ISO 9660 version 2, or Joliet exten-
sions, the file names and directory names may contain any character
supported under UFS. The names may also be uppercase and/or lowercase
and are case sensitive. File name lengths can be as long as those of
@@ -103,7 +102,7 @@
Files accessed through HSFS have mode 555 (owner, group and world read-
- able and executable), uid 0 and gid 3. If a directory on the CD-ROM has
+ able and executable), uid 0 and gid 3. If a directory on the disk has
read permission, HSFS grants execute permission to the directory, al-
lowing it to be searched.
@@ -114,18 +113,18 @@
write operations.
- Like High Sierra and ISO 9660 CD-ROMs, HSFS supports only regular files
- and directories. A Rock Ridge CD-ROM can support regular files, direc-
- tories, and symbolic links, as well as device nodes, such as block,
- character, and FIFO.
+ Like High Sierra and ISO 9660 disks, HSFS supports only regular files
+ and directories. A Rock Ridge disk can support regular files, directo-
+ ries, and symbolic links, as well as device nodes, such as block, char-
+ acter, and FIFO.
EXAMPLES
Example 1 Sample Display of File System Files
- If there is a file BIG.BAR on a High Sierra or ISO 9660 format CD-ROM
- it will show up as big.bar when listed on a HSFS file system.
+ If there is a file BIG.BAR on a High Sierra or ISO 9660 format disk it
+ will show up as big.bar when listed on a HSFS file system.
@@ -149,11 +148,21 @@
- on a High Sierra or ISO 9660 format CD-ROM, only the file BAR.BAZ;3
- will be accessible. It will be listed as bar.baz.
+ on a High Sierra or ISO 9660 format disk only the file BAR.BAZ;3 will
+ be accessible. It will be listed as bar.baz.
+
+ATTRIBUTES
+ See attributes(7) for a description of the following attributes:
+
+ +------------------------------+-----------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------+
+ | Availability |system/file-system/hsfs |
+ +------------------------------+-----------------------------+
+
SEE ALSO
- vfstab(5), mount(8), mount_hsfs(8), zonecfg(8)
+ vfstab(5), mkisofs(8), mount(8), mount_hsfs(8), zonecfg(8)
N. V. Phillips and Sony Corporation, System Description Compact Disc
@@ -172,7 +181,7 @@
does not conform to the ISO-9660 spec
The specific reason appears on the following line. You might be at-
- tempting to mount a CD-ROM containing a different file system, such
+ tempting to mount a disk containing a different file system, such
as UFS.
@@ -181,7 +190,7 @@
contains a file [with an] unsupported type
The hsfs file system does not support the format of some file or
- directory on the CD-ROM, for example a record structured file.
+ directory on the disk, for example a record structured file.
@@ -194,12 +203,13 @@
WARNINGS
- Do not physically eject a CD-ROM while the device is still mounted as a
- HSFS file system.
+ Do not physically eject a CD-ROM, DVD, or other media while the device
+ is still mounted as a HSFS file system.
- Under MS-DOS (for which CD-ROMs are frequently targeted), files with no
- extension may be represented either as:
+ Under Microsoft operating systems (for which CD-ROM and DVD media are
+ frequently targeted), files with no extension may be represented either
+ as:
filename.
@@ -225,8 +235,8 @@
are not names for the same file under the UNIX system. This may cause
- confusion if you are consulting documentation for CD-ROMs originally
- intended for MS-DOS systems.
+ confusion if you are consulting documentation for disks originally in-
+ tended for Microsoft systems.
Use of the -o notraildot option to mount(8) makes it optional to spec-
@@ -234,10 +244,10 @@
NOTES
No translation of any sort is done on the contents of High Sierra or
- ISO 9660 format CD-ROMs; only directory and file names are subject to
- interpretation by HSFS.
+ ISO 9660 format media; only directory and file names are subject to in-
+ terpretation by HSFS.
By default, zones can mount this file system.
-Oracle Solaris 11.4 11 May 2021 hsfs(4FS)
+Oracle Solaris 11.4 14 Jun 2024 hsfs(4FS)
diff -NurbBw 11.4.69/man4fs/lofs.4fs 11.4.72/man4fs/lofs.4fs
--- 11.4.69/man4fs/lofs.4fs 2024-08-20 12:29:44.226319606 -0700
+++ 11.4.72/man4fs/lofs.4fs 2024-08-20 12:30:01.376562371 -0700
@@ -7,7 +7,7 @@
#include <sys/param.h>
#include <sys/mount.h>
- int mount (const char* dir, const char* virtual, int mflag, lofs, NULL, 0);
+ mount(dir, virtual, mflag, MNTTYPE_LOFS, NULL, 0, NULL, 0);
DESCRIPTION
The loopback file system device allows new, virtual file systems to be
@@ -74,4 +74,4 @@
it depends on. This is most easily accomplished by making the loopback
mount entry the last in /etc/vfstab.
-Oracle Solaris 11.4 11 May 2021 lofs(4FS)
+Oracle Solaris 11.4 14 Jun 2024 lofs(4FS)
diff -NurbBw 11.4.69/man4fs/pcfs.4fs 11.4.72/man4fs/pcfs.4fs
--- 11.4.69/man4fs/pcfs.4fs 2024-08-20 12:29:44.259574067 -0700
+++ 11.4.72/man4fs/pcfs.4fs 2024-08-20 12:30:01.410530519 -0700
@@ -9,7 +9,7 @@
#include <sys/fs/pc_fs.h>
int mount(const char *spec, const char * dir, int mflag,
- "pcfs", NULL, 0, char *optptr, int optlen);
+ MNTTYPE_PCFS, NULL, 0, char *optptr, int optlen);
DESCRIPTION
@@ -38,16 +38,16 @@
tions supported by pcfs.
- Because FAT formatted media can record file timestamps between January
- 1st 1980 and December 31st 2127, it's not possible to fully represent
- UNIX time_t in pcfs for 32 bit or 64 bit programs. In particular, if
- post-2038 timestamps are present on a FAT formatted medium and pcfs re-
- turns these, 32bit applications may unexpectedly fail with EOVERFLOW
- errors. To prevent this, the default behaviour of pcfs has been modi-
- fied to clamp post-2038 timestamps to the latest possible value for a
- 32bit time_t, which is January 19th 2038, 03:14:06 UTC when setting and
- retrieving file timestamps. You can override this behavior using the
- noclamptime mount option, as described in mount_pcfs(8).
+ Because FAT formatted media can only record file timestamps between
+ January 1st 1980 and December 31st 2127, it's not possible to fully
+ represent UNIX time_t in pcfs for 32 bit or 64 bit programs. In partic-
+ ular, if post-2038 timestamps are present on a FAT formatted medium and
+ pcfs returns these, 32bit applications may unexpectedly fail with
+ EOVERFLOW errors. To prevent this, the default behaviour of pcfs has
+ been modified to clamp post-2038 timestamps to the latest possible
+ value for a 32bit time_t, which is January 19th 2038, 03:14:06 UTC when
+ setting and retrieving file timestamps. You can override this behavior
+ using the noclamptime mount option, as described in mount_pcfs(8).
Timestamps on FAT formatted media are recorded in local time. If the
@@ -157,7 +157,7 @@
Given a long file name such as This is a really long filename.TXT, the
short file name will generally be of the form THISIS~N.TXT, where N is
a number. The long file name will probably get the short name THI-
- SIS~1.TXT, or THISIS~2.TXT if THISIS~1.TXT already exits (or THI-
+ SIS~1.TXT, or THISIS~2.TXT if THISIS~1.TXT already exists (or THI-
SIS~3.TXT if both exist, and so forth). If you use pcfs file systems on
systems that do not support long file names, you may want to continue
following the short file name conventions. See EXAMPLES.
@@ -274,19 +274,39 @@
MARCHW~1.DAT
FILES
- /usr/lib/fs/pcfs/mount pcfs mount command
+ /usr/lib/fs/pcfs/mount
+ pcfs mount command
- /usr/kernel/fs/pcfs 32-bit kernel module
+
+ /usr/kernel/fs/amd64/pcfs
+
+ Kernel module (x86)
+
+
+ /usr/kernel/fs/sparcv9/pcfs
+
+ Kernel module (SPARC)
ENVIRONMENT VARIABLES
See environ(7) for descriptions of the following environment variables
for the current locale setting: LANG, LC_ALL, LC_CTYPE, and LC_COLLATE.
+ATTRIBUTES
+ See attributes(7) for a description of the following attributes:
+
+ +------------------------------+-----------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------+
+ | Availability |system/file-system/pcfs |
+ +------------------------------+-----------------------------+
+
+
SEE ALSO
dos2unix(1), chgrp(1), chown(1), eject(1), unix2dos(1), volcheck(1),
- ctime(3C), vfstab(5), environ(7), mount(8), mount_pcfs(8), umount(8),
+ ctime(3C), vfstab(5), environ(7), mount(8), mount_pcfs(8), rmmount(8),
+ umount(8)
WARNINGS
When mounting pcfs on a hard disk, make sure the first block on that
@@ -341,4 +361,4 @@
pcfs should handle the disk change condition in the same way that DOS
does, so you do not need to unmount the file system to change floppies.
-Oracle Solaris 11.4 11 May 2021 pcfs(4FS)
+Oracle Solaris 11.4 14 Jun 2024 pcfs(4FS)
diff -NurbBw 11.4.69/man4fs/tmpfs.4fs 11.4.72/man4fs/tmpfs.4fs
--- 11.4.69/man4fs/tmpfs.4fs 2024-08-20 12:29:44.299764110 -0700
+++ 11.4.72/man4fs/tmpfs.4fs 2024-08-20 12:30:01.449451721 -0700
@@ -6,7 +6,7 @@
SYNOPSIS
#include <sys/mount.h>
- mount (special, directory, MS_DATA, "tmpfs", NULL, 0);
+ mount(special, directory, MS_DATA, MNTTYPE_TMPFS, NULL, 0, NULL, 0);
DESCRIPTION
tmpfs is a memory based file system which uses kernel resources relat-
@@ -23,11 +23,11 @@
- Alternatively, to mount a tmpfs file system on /tmp at multi-user
- startup time (maximizing possible performance improvements), add the
- following line to /etc/vfstab:
+ The system automatically mounts a tmpfs file system on /tmp during sys-
+ tem boot. Additional tmpfs file systems can be mounted by adding a line
+ like the following to /etc/vfstab:
- swap -/tmp tmpfs - yes -
+ swap - directory tmpfs - yes -
@@ -40,12 +40,19 @@
Users of tmpfs should be aware of some constraints involved in mounting
a tmpfs file system. The resources used by tmpfs are the same as those
- used when commands are executed (for example, swap space allocation).
- This means that large sized tmpfs files can affect the amount of space
- left over for programs to execute. Likewise, programs requiring large
- amounts of memory use up the space available to tmpfs. Users running
- into this constraint (for example, running out of space on tmpfs) can
- allocate more swap space by using the swap(8) command.
+ used when commands are executed (for example, virtual memory alloca-
+ tion). This means that large sized tmpfs files can affect the amount of
+ space left over for programs to execute. Limits can be placed on the
+ size to which a tmpfs filesystem can grow by using the -o size option
+ in the /etc/vfstab file or when running the mount command as documented
+ in mount_tmpfs(8).
+
+
+ Likewise, programs requiring large amounts of memory use up the space
+ available to tmpfs. Users running into this constraint (for example,
+ running out of space on tmpfs) can allocate more swap space by using
+ the swap(8) command, or by increasing the size of existing ZFS swap
+ volumes.
Another constraint is that the number of files available in a tmpfs
@@ -101,18 +108,16 @@
will not work as expected.
NOTES
- Compilers do not necessarily use /tmp to write intermediate files
- therefore missing some significant performance benefits. This can be
- remedied by setting the environment variable TMPDIR to /tmp. Compilers
- use the value in this environment variable as the name of the directory
- to store intermediate files.
-
-
swap to a tmpfs file is not supported.
df(8) output is of limited accuracy since a tmpfs file system size is
- not static and the space available to tmpfs is dependent on the swap
- space demands of the entire system.
+ not static and the space available to tmpfs is dependent on the virtual
+ memory usage of the entire system.
+
+
+ Only a subset of the available extended system attributes are supported
+ on tmpfs file systems. See the entry for each attribute in the
+ sysattr(7) man page for details.
-Oracle Solaris 11.4 9 Oct 1990 tmpfs(4FS)
+Oracle Solaris 11.4 14 Jun 2024 tmpfs(4FS)
diff -NurbBw 11.4.69/man4fs/udfs.4fs 11.4.72/man4fs/udfs.4fs
--- 11.4.69/man4fs/udfs.4fs 2024-08-20 12:29:44.334178612 -0700
+++ 11.4.72/man4fs/udfs.4fs 2024-08-20 12:30:01.489648842 -0700
@@ -23,7 +23,7 @@
- Use:
+ You can use:
mount /udfs
@@ -42,7 +42,17 @@
The udfs file system also supports regular files, directories, and sym-
bolic links, as well as device nodes such as block, character, FIFO,
- and Socket.
+ and socket.
+
+ATTRIBUTES
+ See attributes(7) for a description of the following attributes:
+
+ +------------------------------+-----------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------+
+ | Availability |system/file-system/udfs |
+ +------------------------------+-----------------------------+
+
SEE ALSO
vfstab(5), mount(8), mount_udfs(8)
@@ -58,4 +68,4 @@
ple, the file name ".." will become "__#4C05".
-Oracle Solaris 11.4 11 Dec 2020 udfs(4FS)
+Oracle Solaris 11.4 14 Jun 2024 udfs(4FS)
diff -NurbBw 11.4.69/man4fs/ufs.4fs 11.4.72/man4fs/ufs.4fs
--- 11.4.69/man4fs/ufs.4fs 2024-08-20 12:29:44.364330461 -0700
+++ 11.4.72/man4fs/ufs.4fs 2024-08-20 12:30:01.530573527 -0700
@@ -161,22 +161,29 @@
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
+ | Availability |system/file-system/ufs |
+ +------------------------------+-----------------------------+
| Interface Stability |Uncommitted |
+------------------------------+-----------------------------+
SEE ALSO
- mount(2), attributes(7), df(8), fsck(8), fsck_ufs(8), fstyp(8),
- lockfs(8), mkfs_ufs(8), newfs(8), tunefs(8), ufsdump(8), ufsrestore(8)
+ mount(2), quotactl(4I), attributes(7), df(8), fsck(8), fsck_ufs(8),
+ fstyp(8), lockfs(8), mkfs_ufs(8), mount_ufs(8), newfs(8), tunefs(8),
+ ufsdump(8), ufsrestore(8)
- Writing Device Drivers in Oracle Solaris 11.4
+ Managing File Systems in Oracle Solaris 11.4
NOTES
+ The zfs(4FS) file system has replaced most usages of UFS in Oracle So-
+ laris 11.
+
+
For information about internal UFS structures, see newfs(8) and
mkfs_ufs(8). For information about the ufsdump and ufsrestore commands,
- see ufsdump(8), ufsrestore(8), and /usr/include/protocols/dumpre-
- store.h.
+ see ufsdump(8), ufsrestore(8), ufsdump(5), and /usr/include/proto-
+ cols/dumprestore.h.
If you experience difficulty in allocating space on the ufs filesystem,
@@ -194,4 +201,4 @@
and the degree of fragmentation. To correct a fragmentation problem,
run ufsdump(8) and ufsrestore(8) on the ufs filesystem.
-Oracle Solaris 11.4 27 Nov 2017 ufs(4FS)
+Oracle Solaris 11.4 14 Jun 2024 ufs(4FS)
diff -NurbBw 11.4.69/man4fs/uvfs.4fs 11.4.72/man4fs/uvfs.4fs
--- 11.4.69/man4fs/uvfs.4fs 2024-08-20 12:29:44.390449993 -0700
+++ 11.4.72/man4fs/uvfs.4fs 2024-08-20 12:30:01.557595602 -0700
@@ -25,8 +25,8 @@
Each separate user-level file system mount creates a separate SMF ser-
vice instance under the uvfs-server service. The instance is named:
- fsid-hex_value_of _fsid. If you have multiple uvfs mounts, you would
- see multiple lines of output from the following command:
+ fsid-hex_value_of_fsid. If you have multiple uvfs mounts, you would see
+ multiple lines of output from the following command:
# svcs uvfs-server
@@ -37,11 +37,13 @@
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
+ | Availability |system/file-system/uvfs |
+ +------------------------------+-----------------------------+
| Interface Stability |Private |
+------------------------------+-----------------------------+
SEE ALSO
- attributes(7)
+ attributes(7), mount_uvfs(8)
-Oracle Solaris 11.4 21 Feb 2011 uvfs(4FS)
+Oracle Solaris 11.4 14 Jun 2024 uvfs(4FS)
diff -NurbBw 11.4.69/man4fs/zfs.4fs 11.4.72/man4fs/zfs.4fs
--- 11.4.69/man4fs/zfs.4fs 2024-08-20 12:29:44.418692559 -0700
+++ 11.4.72/man4fs/zfs.4fs 2024-08-20 12:30:01.586071082 -0700
@@ -75,6 +75,8 @@
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
+ | Availability |system/file-system/zfs |
+ +------------------------------+-----------------------------+
| Interface Stability |Uncommitted |
+------------------------------+-----------------------------+
@@ -93,12 +95,12 @@
tures are also available.
- 2. Use the zpool list and zfs list to identify ZFS space con-
- sumption. A limitation of using the du(1) command to deter-
- mine ZFS file system sizes is that it also reports ZFS meta-
- data space consumption. The df(8) command does not account
- for space that is consumed by ZFS snapshots, clones, or quo-
- tas.
+ 2. Use the zpool list and zfs list commands to identify ZFS
+ space consumption. A limitation of using the du(1) command
+ to determine ZFS file system sizes is that it also reports
+ ZFS metadata space consumption. The df(8) command does not
+ account for space that is consumed by ZFS snapshots, clones,
+ or quotas.
3. A ZFS storage pool that is not used for booting should be
@@ -110,4 +112,10 @@
-Oracle Solaris 11.4 21 Mar 2022 zfs(4FS)
+HISTORY
+ ZFS was introduced in the Solaris 10 6/06 (Update 2) release. History
+ for the different versions of the ZFS pool and ZFS file system formats
+ is provided in Appendix A of the Managing ZFS File Systems in Oracle
+ Solaris 11.4 guide.
+
+Oracle Solaris 11.4 14 Jun 2024 zfs(4FS)
diff -NurbBw 11.4.69/man4i/audio.4i 11.4.72/man4i/audio.4i
--- 11.4.69/man4i/audio.4i 2024-08-20 12:29:44.479409350 -0700
+++ 11.4.72/man4i/audio.4i 2024-08-20 12:30:01.628663560 -0700
@@ -117,21 +117,24 @@
The audio mixer sets the hardware to the maximum number of channels
supported. If a mono signal is played or recorded, it is mixed on the
first two (usually the left and right) channels only. Silence is mixed
- on the remaining channels
+ on the remaining channels.
Supported Formats
The audio mixer supports the following audio formats:
-
-
- Encoding Precision Channels
- Signed Linear PCM 32-bit Mono or Stereo
- Signed Linear PCM 16-bit Mono or Stereo
- Signed Linear PCM 8-bit Mono or Stereo
- u-Law 8-bit Mono or Stereo
- A-Law 8-bit Mono or Stereo
-
-
+ +------------------------+-------------+------------------------+
+ | ENCODING | PRECISION | CHANNELS |
+ +------------------------+-------------+------------------------+
+ | Signed Linear PCM | 32-bit | Mono or Stereo |
+ +------------------------+-------------+------------------------+
+ | Signed Linear PCM | 16-bit | Mono or Stereo |
+ +------------------------+-------------+------------------------+
+ | Signed Linear PCM | 8-bit | Mono or Stereo |
+ +------------------------+-------------+------------------------+
+ | u-Law | 8-bit | Mono or Stereo |
+ +------------------------+-------------+------------------------+
+ | A-Law | 8-bit | Mono or Stereo |
+ +------------------------+-------------+------------------------+
@@ -414,7 +418,8 @@
#define AUDIO_AUX1_OUT (0x10)/* aux1 out */
#define AUDIO_AUX2_OUT (0x20)/* aux2 out */
- /* input ports (usually only one may be
+ /*
+ * input ports (usually only one may be
* enabled at a time)
*/
#define AUDIO_MICROPHONE (0x01) /* microphone */
@@ -439,7 +444,8 @@
/*
* Parameter for the AUDIO_GETDEV ioctl
* to determine current audio devices
- */#define MAX_AUDIO_DEV_LEN(16)
+ */
+ #define MAX_AUDIO_DEV_LEN (16)
struct audio_device {
char name[MAX_AUDIO_DEV_LEN];
char version[MAX_AUDIO_DEV_LEN];
@@ -530,7 +535,7 @@
The audio data format is indicated by the sample_rate, channels, preci-
- sion and encoding fields. The values of these fields correspond to the
+ sion, and encoding fields. The values of these fields correspond to the
descriptions in the AUDIO FORMATS section of this man page. Refer to
the audio device-specific manual pages for a list of supported data
format combinations.
@@ -595,8 +600,8 @@
Note: The play.samples, record.samples, play.error,
record.error, and play.eof fields are modified to re-
flect the state of the device when the AUDIO_SETINFO
- is issued. This allows programs to automatically mod-
- ify these fields while retrieving the previous value.
+ is issued. This allows programs to atomically modify
+ these fields while retrieving the previous value.
As with AUDIO_SETINFO, the settings managed by this
ioctl deal with a logical view of the device which is
@@ -611,8 +616,8 @@
and encoding information, may have a restricted set of acceptable val-
ues. Applications that attempt to modify such fields should check the
returned values to be sure that the corresponding change took effect.
- The sample_rate, channels, precision, and encoding fields treated as
- read-only for /dev/audioctl, so that applications can be guaranteed
+ The sample_rate, channels, precision, and encoding fields are treated
+ as read-only for /dev/audioctl, so that applications can be guaranteed
that the existing audio format will stay in place until they relinquish
the audio device. AUDIO_SETINFO will return EINVAL when the desired
configuration is not possible, or EBUSY when another process has con-
@@ -629,12 +634,10 @@
following code switches the output port from the built-in speaker to
the headphone jack without modifying any other audio parameters:
-
-
audio_info_t info;
AUDIO_INITINFO();
info.play.port = AUDIO_HEADPHONE;
- err = ioctl(audio_fd, AUDIO_SETINFO, );
+ err = ioctl(audio_fd, AUDIO_SETINFO, &info);
@@ -706,4 +709,4 @@
dio output should catch the SIGINT signal and flush the output stream
before exiting.
-Oracle Solaris 11.4 16 Aug 2011 audio(4I)
+Oracle Solaris 11.4 14 Jun 2024 audio(4I)
diff -NurbBw 11.4.69/man4i/cdio.4i 11.4.72/man4i/cdio.4i
--- 11.4.69/man4i/cdio.4i 2024-08-20 12:29:44.515255833 -0700
+++ 11.4.72/man4i/cdio.4i 2024-08-20 12:30:01.663775346 -0700
@@ -497,8 +488,10 @@
CDROM_QUAD_SPEED 600k/second
- CDROM_MAXIMUM_SPEED 300k/second (2x drive) 600k/second (4x
- drive)
+ CDROM_TWELVE_SPEED 1800k/second
+
+
+ CDROM_MAXIMUM_SPEED Maximum speed supported by the drive
Note that these numbers are only accurate when reading 2048 byte
blocks. The CD-ROM drive will automatically switch to normal speed
@@ -507,7 +500,7 @@
SEE ALSO
- ioctl(2), read(2)
+ ioctl(2), read(2), sd(4D), hsfs(4FS)
N. V. Phillips and Sony Corporation, System Description Compact Disc
@@ -533,23 +526,17 @@
NOTES
The CDROMCDDA, CDROMCDXA, CDROMSUBCODE, CDROMGDRVSPEED, CDROMSDRVSPEED,
- and some of the block sizes in CDROMSBLKMODE are designed for new Sun-
- supported CD-ROM drives and might not work on some of the older CD-ROM
- drives.
-
-
- CDROMCDDA, CDROMCDXA and CDROMSUBCODE will return error if the transfer
- length exceeds valid limits as determined appropriate. Example: for
- MMC-2 drives, length can not exceed 3 bytes (i.e. 0xffffff). The same
- restriction is enforced for older, pre-MMC-2 drives, as no limit was
- published for these older drives (and 3 bytes is reasonable for all me-
- dia). Note that enforcing this limit does not imply that values passed
- in below this limit will actually be applicable for each and every
- piece of media.
-
-
- The interface to this device is preliminary and subject to change in
- future releases. Programs should be written in a modular fashion so
- that future changes can be easily incorporated.
+ and some of the block sizes in CDROMSBLKMODE might not be supported on
+ some older CD-ROM drives.
+
+
+ CDROMCDDA, CDROMCDXA, and CDROMSUBCODE will return an error if the
+ transfer length exceeds valid limits as determined appropriate. Exam-
+ ple: for MMC-2 drives, length can not exceed 3 bytes (i.e. 0xffffff).
+ The same restriction is enforced for older, pre-MMC-2 drives, as no
+ limit was published for these older drives (and 3 bytes is reasonable
+ for all media). Note that enforcing this limit does not imply that val-
+ ues passed in below this limit will actually be applicable for each and
+ every piece of media.
-Oracle Solaris 11.4 4 Oct 2001 cdio(4I)
+Oracle Solaris 11.4 14 Jun 2024 cdio(4I)
diff -NurbBw 11.4.69/man4i/dkio.4i 11.4.72/man4i/dkio.4i
--- 11.4.69/man4i/dkio.4i 2024-08-20 12:29:44.560097998 -0700
+++ 11.4.72/man4i/dkio.4i 2024-08-20 12:30:01.702436334 -0700
@@ -19,8 +19,8 @@
DKIOCINFO
The argument is a pointer to a dk_cinfo structure (described be-
- low). This structure tells the controller-type and attributes re-
- garding bad-block processing done on the controller.
+ low). This structure describes the controller and provides attrib-
+ utes regarding bad-block processing done on the controller.
/*
@@ -69,7 +69,7 @@
#define DKC_PCMCIA_ATA 22 /* PCMCIA AT Attached type */
/*
- * Sun reserves up through 1023
+ * Solaris reserves up through 1023
*/
#define DKC_CUSTOMER_BASE 1024
@@ -126,7 +124,8 @@
/*
* Partition map (part of dk_label)
- */ struct dk_map {
+ */
+ struct dk_map {
daddr_t dkl_cylno; /* starting cylinder */
daddr_t dkl_nblk; /* number of blocks */
};
@@ -185,10 +185,8 @@
/* sanity */
unsigned long v_version; /* layout version */
char v_volume[LEN_DKL_VVOL]; /* volume name */
- ushort_t v_sectorsz; \*
- sector size in bytes*/
- ushort_t v_nparts; \*
- number of partitions*/
+ ushort_t v_sectorsz; /* sector size in bytes */
+ ushort_t v_nparts; /* number of partitions */
unsigned long v_reserved[10]; /* free space */
struct partition v_part[V_NUMPAR]; /* partition headers */
time_t timestamp[V_NUMPAR]; /* partition timestamp */
@@ -477,18 +470,21 @@
vc_info is a bitmap and the valid flag values are:
- DKV_ABR_CAP - Capable of application-based recovery
- DKV_DMR_CAP - Ability to read specific copy of data when
- multiple copies exist. For example, in a two
- way mirror, this ioctl is used to read each
- side of the mirror.
+ DKV_ABR_CAP Capable of application-based recovery
+
+
+ DKV_DMR_CAP Ability to read specific copy of data when multiple
+ copies exist. For example, in a two way mirror, this
+ ioctl is used to read each side of the mirror.
vc_set is a bitmap and the valid flag values are:
- DKV_ABR_CAP - This flag is set if ABR has been set on a device
+ DKV_ABR_CAP This flag is set if ABR has been set on a device
that supports ABR functionality.
- DKV_DMR_CAP - Directed read has been enabled.
+
+
+ DKV_DMR_CAP Directed read has been enabled.
These capabilities are not required to be persistent across a sys-
tem reboot and their persistence depends upon the implementation.
@@ -519,13 +515,11 @@
vc_set valid flags are:
- DKV_ABR_CAP - Flag to set application-based recovery. A device can
+ DKV_ABR_CAP Flag to set application-based recovery. A device can
successfully support ABR only if it is capable.
- DKV_DMR_CAP - Flag to set directed read.
- int
- ioctl(int , DKIODMR, vol_directed_rd *);
+ DKV_DMR_CAP Flag to set directed read.
@@ -535,17 +529,26 @@
robin reads from the underlying devices of a replicated device.
+ vdr_offset Offset at which the read should occur.
+
+
+ vdr_nbytes Number of bytes to be read.
+
+ vdr_bytesread Number of bytes successfully read by the kernel.
- vdr_offset - offset at which the read should occur.
- vdr_nbytes - number of bytes to be read
- vdr_bytesread - number of bytes successfully read by the kernel.
- vdr_data - pointer to a user allocated buffer to return the
- data read
- vdr_side - side to be read. Initialized to DKV_SIDE_INIT
- vdr_side_name - The volume name that has been read.
+
+ vdr_data Pointer to a user allocated buffer to return the
+ data read.
+
+
+ vdr_side Side to be read. Initialized to DKV_SIDE_INIT.
+
+
+ vdr_side_name The volume name that has been read.
Valid vdr_flags are:
+
DKV_DMR_NEXT_SIDE (set by user)
DKV_DMR_DONE (return value)
DKV_DMR_ERROR (return value)
@@ -571,18 +573,17 @@
that are returned when an error occurs:
-
- vdr_flags | vdr_side | Notes
- -------------|-------------------|----------------------------
- DKV_DMR_ERROR| DKV_SIDE_INIT | No valid side to read
- DKV_DMR_DONE | Not Init side | All valid sides read
- DKV_DMR_SHORT| Any value | Bytes requested cannot
- be read. vdr_bytesread
- set to bytes actually
- read.
-
-
-
+ +----------------+----------------+-----------------------------+
+ | vdr_flags | vdr_side | Notes |
+ +----------------+----------------+-----------------------------+
+ | DKV_DMR_ERROR | DKV_SIDE_INIT | No valid side to read |
+ +----------------+----------------+-----------------------------+
+ | DKV_DMR_DONE | Not Init side | All valid sides read |
+ +----------------+----------------+-----------------------------+
+ | DKV_DMR_SHORT | Any value | Bytes requested cannot be |
+ | | | read. vdr_bytesread set to |
+ | | | bytes actually read. |
+ +----------------+----------------+-----------------------------+
Typical code fragment:
@@ -637,7 +638,8 @@
/*
* Definition of a disk's geometry
*/
- */struct dk_geom {
+
+ struct dk_geom {
unsigned shor dkg_ncyl; /* # of data cylinders */
unsigned shor dkg_acyl; /* # of alternate cylinders */
unsigned short dkg_bcyl; /* cyl offset (for fixed head */
@@ -697,8 +698,9 @@
/*
* Used by applications to get partition or slice information
*/
+
struct extpart_info {
- diskkaddr_t p_start;
+ diskaddr_t p_start;
diskaddr_t p_length;
};
@@ -740,4 +742,4 @@
point, the old valid VTOC is read from the disk if it is still avail-
able.
-Oracle Solaris 11.4 11 May 2021 dkio(4I)
+Oracle Solaris 11.4 14 Jun 2024 dkio(4I)
diff -NurbBw 11.4.69/man4i/dsp.4i 11.4.72/man4i/dsp.4i
--- 11.4.69/man4i/dsp.4i 2024-08-20 12:29:44.596558865 -0700
+++ 11.4.72/man4i/dsp.4i 2024-08-20 12:30:01.754578320 -0700
@@ -58,8 +58,8 @@
Before changing record parameters, the input should be stopped using
- the SNDCTL_DSP_HALT_INPUT ioctl, which also flushes the any underlying
- device input FIFOs. (This is not necessary if the process never started
+ the SNDCTL_DSP_HALT_INPUT ioctl, which also flushes any underlying de-
+ vice input FIFOs. (This is not necessary if the process never started
recording by calling read(2). Otherwise, subsequent reads can return
samples in the old format followed by samples in the new format. This
is particularly important when new parameters result in a changed sam-
@@ -108,7 +108,7 @@
Before changing playback parameters, the output should be drained using
the SNDCTL_DSP_SYNC ioctl, and then stopped using the SND-
- CTL_DSP_HALT_OUTPUT ioctl, which also flushes the any underlying device
+ CTL_DSP_HALT_OUTPUT ioctl, which also flushes any underlying device
output FIFOs. This is not necessary if the process never started play-
back, such as by calling write(2). This is particularly important when
new parameters result in a changed sample size.
@@ -125,7 +125,7 @@
Playback volume for a stream can be adjusted by issuing the SND-
CTL_DSP_SETPLAYVOL ioctl. The volume can also be retrieved using the
- SNDCTL_DSP_GETPLAYVOL.
+ SNDCTL_DSP_GETPLAYVOL ioctl.
Asynchronous I/O
The O_NONBLOCK flag can be set using the F_SETFL fcntl(2) to enable
@@ -190,14 +190,14 @@
(in Hz) to be used. The rate applies to both input and output for
the file descriptor. On return the actual rate, which can differ
from that requested, is stored in the integer pointed to by the ar-
- gument. To query the configured speed without changing it the value
- 0 can be used by the application
+ gument. To query the configured speed without changing it, the
+ value 0 can be used by the application.
SNDCTL_DSP_GETFMTS
The argument is a pointer to an integer, which receives a bit mask
- of encodings supported by the device. Possible values are
+ of encodings supported by the device. Possible values are:
AFMT_MU_LAW 8-bit unsigned u-Law
@@ -250,8 +250,9 @@
AFMT_S24_PACKED 24-bit signed little-endian packed linear PCM
- Not all devices support all of these encodings. This implementation
- uses AFMT_S24_LE or AFMT_S24_BE, whichever is native, internally.
+ Not all devices support all of these encodings. Internally, this
+ implementation uses AFMT_S24_LE or AFMT_S24_BE, whichever is na-
+ tive.
SNDCTL_DSP_SETFMT
@@ -265,7 +266,7 @@
SNDCTL_DSP_CHANNELS
The argument is a pointer to an integer, indicating the number of
- channels to be used (1 for mono, 2 for stereo, etc.) The value ap-
+ channels to be used (1 for mono, 2 for stereo, etc.). The value ap-
plies to both input and output for the file descriptor. On return
the actual channel configuration (which can differ from that re-
quested) is stored in the integer pointed to by the argument. To
@@ -276,7 +277,7 @@
SNDDCTL_DSP_GETCAPS
The argument is a pointer to an integer bit mask, which indicates
- the capabilities of the device. The bits returned can include
+ the capabilities of the device. The bits returned can include:
PCM_CAP_OUTPUT Device supports playback
@@ -311,7 +312,7 @@
bytes. The value for each channel has a range of 0-100. Note that
in this implementation, only the low order byte is used, as the
value is treated as a monophonic value. Portable applications
- should assign the same value to both bytes
+ should assign the same value to both bytes.
@@ -508,6 +509,6 @@
SEE ALSO
close(2), fcntl(2), ioctl(2), mmap(2), open(2), poll(2), read(2),
- write(2), audio(4D), mixer(4I), attributes(7)
+ write(2), audio(4D), audio(4I), mixer(4I), attributes(7)
-Oracle Solaris 11.4 11 May 2009 dsp(4I)
+Oracle Solaris 11.4 14 Jun 2024 dsp(4I)
diff -NurbBw 11.4.69/man4i/hdio.4i 11.4.72/man4i/hdio.4i
--- 11.4.69/man4i/hdio.4i 2024-08-20 12:29:44.624156212 -0700
+++ 11.4.72/man4i/hdio.4i 2024-08-20 12:30:01.780851331 -0700
@@ -16,9 +16,9 @@
- The SMD and IPI disk drivers supplied with this release support a set
- of ioctl(2) requests for diagnostics and bad sector information. Basic
- to these ioctl() requests are the definitions in <sys/hdio.h>.
+ The SMD and IPI disk drivers supplied with previous releases supported
+ a set of ioctl(2) requests for diagnostics and bad sector information.
+ Basic to these ioctl() requests are the definitions in <sys/hdio.h>.
IOCTLS
HDKIOCGTYPE The argument is a pointer to a hdk_type structure (de-
@@ -77,7 +77,17 @@
};
+ATTRIBUTES
+ See attributes(7) for a description of the following attributes:
+
+ +------------------------------+-----------------------------+
+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+ +------------------------------+-----------------------------+
+ | Interface Stability |Obsolete |
+ +------------------------------+-----------------------------+
+
+
SEE ALSO
ioctl(2), dkio(4I)
-Oracle Solaris 11.4 13 Mar 2023 hdio(4I)
+Oracle Solaris 11.4 14 Jun 2024 hdio(4I)
diff -NurbBw 11.4.69/man4i/mhd.4i 11.4.72/man4i/mhd.4i
--- 11.4.69/man4i/mhd.4i 2024-08-20 12:29:44.668887001 -0700
+++ 11.4.72/man4i/mhd.4i 2024-08-20 12:30:01.812472260 -0700
@@ -32,7 +32,7 @@
Non-shared multihost disks
Non-shared multihost disks ioctls consist of MHIOCTKOWN, MHIOCRELEASE,
- HIOCSTATUS, and MHIOCQRESERVE. These ioctl requests control the access
+ MHIOCSTATUS, and MHIOCQRESERVE. These ioctl requests control the access
rights of non-shared multihost disks. A non-shared multihost disk is
one that supports serialized, mutually exclusive I/O mastery by the
connected hosts. This is in contrast to the shared-disk model, in which
@@ -291,4 +291,4 @@
SEE ALSO
ioctl(2), open(2), attributes(7), privileges(7)
-Oracle Solaris 11.4 3 Nov 2021 mhd(4I)
+Oracle Solaris 11.4 14 Jun 2024 mhd(4I)
diff -NurbBw 11.4.69/man4i/mtio.4i 11.4.72/man4i/mtio.4i
--- 11.4.69/man4i/mtio.4i 2024-08-20 12:29:44.741723314 -0700
+++ 11.4.72/man4i/mtio.4i 2024-08-20 12:30:01.855058763 -0700
@@ -285,8 +285,7 @@
are from <sys/mtio.h>.
- The minor device byte structure is::
-
+ The minor device byte structure is:
15 7 6 5 4 3 2 1 0
@@ -417,16 +408,12 @@
DADP_RW_ENABLE, /* 6 */
DADP_RBDP_RW_ENABLE, /* 7 */
-
-
The *RBDP* values enable use of the SCSI Recover
Buffered Data command to read back the data trapped in
the device's buffer when a write error is detected.
- MTVERIFY Issues a scsi(5) Verify command. When issued with DADP
- reads enabled causes the drive to read data from tape
- and compare the stored
+ MTVERIFY Issues a scsi(5) Verify command.
When issued with DADP reads enabled causes the drive
to read data from tape and compare the stored data
@@ -636,20 +624,21 @@
The MTIOCGET get status ioctl call returns the drive ID (mt_type),
sense key error (mt_erreg), file number (mt_fileno), optimum blocking
- factor (mt_bf) and record number (mt_blkno) of the last error. The
+ factor (mt_bf), and record number (mt_blkno) of the last error. The
residual count (mt_resid) is set to the number of bytes not transferred
or files/records not spaced. The flags word (mt_flags) contains infor-
mation indicating if the device is SCSI, if the device is a reel device
and whether the device supports absolute file positioning. The mt_flags
also indicates if the device is requesting cleaning media be used,
whether the device is capable of reporting the requirement of cleaning
- media and if the currently loaded media is WORM (Write Once Read Many)
+ media, and if the currently loaded media is WORM (Write Once Read Many)
media.
When tape alert cleaning is managed by the st driver, the tape target
driver may continue to return a drive needs cleaning status unless an
- MTIOCGET ioctl() call is made while the cleaning media is in the drive.
+ MTIOCGET ioctl() call is made while the cleaning media is in the
+ drive.
The MTIOCGETDRIVETYPE get drivetype ioctl call returns the name of the
@@ -729,7 +718,7 @@
Asynchronous and State Change IOCTLS
MTIOCSTATE This ioctl blocks until the state of the drive, inserted
or ejected, is changed. The argument is a pointer to a
- mtio_state, enum, whose possible enumerations are listed
+ mtio_state enum, whose possible enumerations are listed
below. The initial value should be either the last re-
ported state of the drive, or MTIO_NONE. Upon return, the
enum pointed to by the argument is updated with the cur-
@@ -941,4 +930,4 @@
1/4 Inch Tape Drive Tutorial
-Oracle Solaris 11.4 3 Nov 2021 mtio(4I)
+Oracle Solaris 11.4 14 Jun 2024 mtio(4I)
diff -NurbBw 11.4.69/man4i/prnio.4i 11.4.72/man4i/prnio.4i
--- 11.4.69/man4i/prnio.4i 2024-08-20 12:29:44.776608702 -0700
+++ 11.4.72/man4i/prnio.4i 2024-08-20 12:30:01.902604286 -0700
@@ -32,13 +32,13 @@
During the Identification phase, the application retrieves a set of de-
vice capabilities and additional information using the PRNIOC_GET_IF-
- CAP, PRNIOC_GET_STATUS, PRNIOC_GET_TIMEOUTS, PRNIOC_GET_IFINFO and
+ CAP, PRNIOC_GET_STATUS, PRNIOC_GET_TIMEOUTS, PRNIOC_GET_IFINFO, and
PRNIOC_GET_1284_DEVID commands.
During the Setup phase the application sets some interface attributes
and probably resets the printer as described in the PRNIOC_SET_IFCAP,
- PRNIOC_SET_TIMEOUTS and PRNIOC_RESET sections.
+ PRNIOC_SET_TIMEOUTS, and PRNIOC_RESET sections.
During the Transfer phase, data is transferred in a forward (host to
@@ -62,67 +62,80 @@
tion.
IOCTLS
- PRNIOC_GET_IFCAP Application can retrieve printer interface capa-
- bilities using this command. The ioctl(2) argument
- is a pointer to uint_t, a bit field representing a
- set of properties and services provided by a
- printer driver. Set bit means supported capabil-
- ity. The following values are defined:
- PRN_BIDI - When this bit is set, the interface
- operates in a bidirectional mode, instead of
- forward-only mode.
- PRN_HOTPLUG - If this bit is set, the interface
- allows device hot-plugging.
- PRN_1284_DEVID - If this bit is set, the device
- is capable of returning 1284 device ID (see
- PRNIOC_GET_1284_DEVID.)
- PRN_1284_STATUS - If this bit is set, the device
- driver can return device status lines (see
- PRNIOC_GET_1284_STATUS). Some devices support
- this ioctl in unidirectional mode only.
- PRN_TIMEOUTS - If this bit is set the peripheral
- may stall during the transfer phase and the dri-
- ver can timeout and return from the write(2) and
- read(2) returning the number of bytes that have
- been transferred. If PRN_TIMEOUTS is set, the
- driver supports this functionality and the time-
- out values can be retrieved and modified via the
+ PRNIOC_GET_IFCAP
+
+ Application can retrieve printer interface capabilities using this
+ command. The ioctl(2) argument is a pointer to uint_t, a bit field
+ representing a set of properties and services provided by a printer
+ driver. Set bit means supported capability. The following values
+ are defined:
+
+ PRN_BIDI When this bit is set, the interface operates in
+ a bidirectional mode, instead of forward-only
+ mode.
+
+
+ PRN_HOTPLUG If this bit is set, the interface allows device
+ hot-plugging.
+
+
+ PRN_1284_DEVID If this bit is set, the device is capable of re-
+ turning 1284 device ID (see PRNIOC_GET_1284_DE-
+ VID.)
+
+
+ PRN_1284_STATUS If this bit is set, the device driver can return
+ device status lines (see PRNIOC_GET_1284_STA-
+ TUS). Some devices support this ioctl in unidi-
+ rectional mode only.
+
+
+ PRN_TIMEOUTS If this bit is set the peripheral may stall dur-
+ ing the transfer phase and the driver can time-
+ out and return from the write(2) and read(2) re-
+ turning the number of bytes that have been
+ transferred. If PRN_TIMEOUTS is set, the driver
+ supports this functionality and the timeout val-
+ ues can be retrieved and modified via the
PRNIOC_GET_TIMEOUTS and PRNIOC_SET_TIMEOUTS
ioctls. Otherwise, applications can implement
their own timeouts and abort phase.
- PRN_STREAMS - This bit impacts the application
- abort phase behaviour. If the device claimed
- PRN_STREAMS capability, the application must is-
- sue an I_FLUSH ioctl(2) before close(2) to dis-
- miss the untransferred data. Only STREAMS dri-
- vers can support this capability.
-
-
- PRNIOC_SET_IFCAP This ioctl can be used to change interface capa-
- bilities. The argument is a pointer to uint_t bit
- field that is described in detail in the
- PRNIOC_GET_IFCAP section. Capabilities should be
- set one at a time; otherwise the command will re-
- turn EINVAL. The following capabilities can be
- changed by this ioctl:
- PRN_BIDI - When this capability is set, the in-
- terface operates in a bidirectional mode, in-
- stead of forward-only mode. Devices that sup-
- port only one mode will not return error; appli-
- cations should use PRNIOC_GET_IFCAP to check if
- the mode was successfully changed. Because some
- capabilities may be altered as a side effect of
- changing other capabilities, this command should
- be followed by PRNIOC_GET_IFCAP.
-
-
- PRNIOC_GET_IFINFO This command can be used to retrieve printer in-
- terface info string, which is an arbitrary format
- string usually describing the bus type. The argu-
- ment is a pointer to struct prn_interface_info as
- described below.
+ PRN_STREAMS This bit impacts the application abort phase be-
+ haviour. If the device claimed PRN_STREAMS capa-
+ bility, the application must issue an I_FLUSH
+ ioctl(2) before close(2) to dismiss the untrans-
+ ferred data. Only STREAMS drivers can support
+ this capability.
+
+
+
+ PRNIOC_SET_IFCAP
+
+ This ioctl can be used to change interface capabilities. The argu-
+ ment is a pointer to uint_t bit field that is described in detail
+ in the PRNIOC_GET_IFCAP section. Capabilities should be set one at
+ a time; otherwise the command will return EINVAL. The following ca-
+ pabilities can be changed by this ioctl:
+
+ PRN_BIDI When this capability is set, the interface operates in
+ a bidirectional mode, instead of forward-only mode. De-
+ vices that support only one mode will not return error;
+ applications should use PRNIOC_GET_IFCAP to check if
+ the mode was successfully changed. Because some capa-
+ bilities may be altered as a side effect of changing
+ other capabilities, this command should be followed by
+ PRNIOC_GET_IFCAP.
+
+
+
+ PRNIOC_GET_IFINFO
+
+ This command can be used to retrieve printer interface info string,
+ which is an arbitrary format string usually describing the bus
+ type. The argument is a pointer to struct prn_interface_info as de-
+ scribed below.
struct prn_interface_info {
@@ -131,46 +144,52 @@
char *if_data; /* buffer address */
};
+ The application allocates a buffer and sets if_data and if_len val-
+ ues to its address and length, respectively. The driver returns the
+ string to this buffer and sets if_len to its length. If if_len is
+ less than if_rlen, the driver must return the first if_len bytes of
+ the string. The application may then repeat the command with a big-
+ ger buffer.
+ Although prnio does not limit the contents of the interface info
+ string, some values are recommended and defined in <sys/prnio.h> by
+ the following macros:
- The application allocates a buffer and sets if_data and if_len values
- to its address and length, respectively. The driver returns the string
- to this buffer and sets if_len to its length. If if_len is less that
- if_rlen, the driver must return the first if_len bytes of the string.
- The application may then repeat the command with a bigger buffer.
+ PRN_PARALLEL Centronics or IEEE 1284 compatible devices
- Although prnio does not limit the contents of the interface info
- string, some values are recommended and defined in <sys/prnio.h> by the
- following macros:
- PRN_PARALLEL - Centronics or IEEE 1284 compatible devices
- PRN_SERIAL - EIA-232/EIA-485 serial ports
- PRN_USB - Universal Serial Bus printers
- PRN_1394 - IEEE 1394 peripherals
- Printer interface info string is for information only: no implica-
- tions should be made from its value.
-
- PRNIOC_RESET Some applications may want to reset the
- printer state during Setup and/or Cleanup
- phase using PRNIOC_RESET command. Reset seman-
- tics are device-specific, and in general, ap-
- plications using this command should be aware
- of the printer type.
-
- Each prnio compliant driver is required to ac-
- cept this request, although performed actions
- are completely driver-dependent. More informa-
- tion on the PRNIOC_RESET implementation for
- the particular driver is available in the cor-
- responding man page and printer manual.
-
-
- PRNIOC_GET_1284_DEVID This command can be used to retrieve printer
- device ID as defined by IEEE 1284-1994. The
- ioctl(2) argument is a pointer to struct
- prn_1284_device_id as described below.
+
+ PRN_SERIAL EIA-232/EIA-485 serial ports
+
+
+ PRN_USB Universal Serial Bus printers
+
+
+ PRN_1394 IEEE 1394 peripherals
+
+ The printer interface info string is for information only: no im-
+ plications should be made from its value.
+ PRNIOC_RESET
+
+ Some applications may want to reset the printer state during Setup
+ and/or Cleanup phase using PRNIOC_RESET command. Reset semantics
+ are device-specific, and in general, applications using this com-
+ mand should be aware of the printer type.
+
+ Each prnio compliant driver is required to accept this request, al-
+ though performed actions are completely driver-dependent. More in-
+ formation on the PRNIOC_RESET implementation for the particular
+ driver is available in the corresponding man page and printer man-
+ ual.
+
+
+ PRNIOC_GET_1284_DEVID
+
+ This command can be used to retrieve printer device ID as defined
+ by IEEE 1284-1994. The ioctl(2) argument is a pointer to struct
+ prn_1284_device_id as described below.
struct prn_1284_device_id {
@@ -179,46 +198,57 @@
char *id_data; /* buffer address */
};
+ For convenience, the two-byte length field is not considered part
+ of device ID string and is not returned in the user buffer. In-
+ stead, id_rlen value shall be set to (length - 2) by the driver,
+ where length is the ID length field value. If buffer length is less
+ than id_rlen, the driver returns the first id_len bytes of the ID.
+
+ The printer driver must return the most up-to-date value of the de-
+ vice ID.
+
+
+ PRNIOC_GET_STATUS
+
+ This command can be used by applications to retrieve current device
+ status. The argument is a pointer to uint_t, where the status word
+ is returned. Status is a combination of the following bits:
+
+ PRN_ONLINE For devices that support PRN_HOTPLUG capability, this
+ bit is set when the device is online, otherwise the
+ device is offline. Devices without PRN_HOTPLUG sup-
+ port should always have this bit set.
+
+
+ PRN_READY This bit indicates if the device is ready to re-
+ ceive/send data. Applications may use this bit for an
+ outbound flow control.
+
- For convenience, the two-byte length field is not considered part of
- device ID string and is not returned in the user buffer. Instead,
- id_rlen value shall be set to (length - 2) by the driver, where length
- is the ID length field value. If buffer length is less than id_rlen,
- the driver returns the first id_len bytes of the ID.
-
-
- The printer driver must return the most up-to-date value of the device
- ID.
-
- PRNIOC_GET_STATUS This command can be used by applications to re-
- trieve current device status. The argument is a
- pointer to uint_t, where the status word is re-
- turned. Status is a combination of the following
- bits:
-
- PRN_ONLINE - For devices that support PRN_HOTPLUG capability,
- this bit is set when the device is online, otherwise the de-
- vice is offline. Devices without PRN_HOTPLUG support should always
- have this bit set.
- PRN_READY - This bit indicates if the device is ready to receive/send
- data. Applications may use this bit for an outbound flow control
-
- PRNIOC_GET_1284_STATUS Devices that support PRN_1284_STATUS capabil-
- ity accept this ioctl to retrieve the device
- status lines defined in IEEE 1284 for use in
- Compatibility mode. The following bits may be
- set by the driver:
- PRN_1284_NOFAULT - Device is not in error
- state
- PRN_1284_SELECT - Device is selected
- PRN_1284_PE - Paper error
- PRN_1284_BUSY - Device is busy
-
-
- PRNIOC_GET_TIMEOUTS This command retrieves current transfer time-
- out values for the driver. The argument is a
- pointer to struct prn_timeouts as described
+ PRNIOC_GET_1284_STATUS
+
+ Devices that support PRN_1284_STATUS capability accept this ioctl
+ to retrieve the device status lines defined in IEEE 1284 for use in
+ Compatibility mode. The following bits may be set by the driver:
+
+ PRN_1284_NOFAULT Device is not in error state
+
+
+ PRN_1284_SELECT Device is selected
+
+
+ PRN_1284_PE Paper error
+
+
+ PRN_1284_BUSY Device is busy
+
+
+
+ PRNIOC_GET_TIMEOUTS
+
+ This command retrieves current transfer timeout values for the dri-
+ ver. The argument is a pointer to struct prn_timeouts as described
below.
@@ -227,18 +257,17 @@
uint_t tmo_reverse; /* reverse transfer timeout */
};
+ tmo_forward and tmo_reverse define forward and reverse transfer
+ timeouts in seconds. This command is only valid for drivers that
+ support PRN_TIMEOUTS capability.
+
+ PRNIOC_SET_TIMEOUTS
- tmo_forward and tmo_reverse define forward and reverse transfer time-
- outs in seconds. This command is only valid for drivers that support
- PRN_TIMEOUTS capability.
-
- PRNIOC_SET_TIMEOUTS This command sets current transfer timeout val-
- ues for the driver. The argument is a pointer to
- struct prn_timeouts. See PRNIOC_GET_TIMEOUTS for
- description of this structure. This command is
- only valid for drivers that support PRN_TIMEOUTS
- capability.
+ This command sets current transfer timeout values for the driver.
+ The argument is a pointer to struct prn_timeouts. See
+ PRNIOC_GET_TIMEOUTS for description of this structure. This command
+ is only valid for drivers that support PRN_TIMEOUTS capability.
ATTRIBUTES
@@ -247,7 +276,7 @@
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
- | Architecture |SPARC, IA |
+ | Architecture |SPARC, x86 |
+------------------------------+-----------------------------+
| Interface Stability |Committed |
+------------------------------+-----------------------------+
@@ -260,4 +289,4 @@
IEEE Std 1284-1994
-Oracle Solaris 11.4 27 Nov 2017 prnio(4I)
+Oracle Solaris 11.4 14 Jun 2024 prnio(4I)
diff -NurbBw 11.4.69/man4i/quotactl.4i 11.4.72/man4i/quotactl.4i
--- 11.4.69/man4i/quotactl.4i 2024-08-20 12:29:44.803183713 -0700
+++ 11.4.72/man4i/quotactl.4i 2024-08-20 12:30:01.930774710 -0700
@@ -1,7 +1,7 @@
quotactl(4I) Ioctls for a class of drivers or subsystems quotactl(4I)
NAME
- quotactl - manipulate disk quotas
+ quotactl - manipulate UFS disk quotas
SYNOPSIS
#include <sys/fs/ufs_quota.h>
@@ -9,11 +9,11 @@
int ioctl(int fd, Q_QUOTACTL, struct quotcl *qp);
DESCRIPTION
- This ioctl() call manipulates disk quotas. fd is the file descriptor
- returned by the open() system call after opening the quotas file (lo-
- cated in the root directory of the filesystem running quotas.) Q_QUO-
- TACTL is defined in /usr/include/sys/fs/ufs_quota.h. qp is the address
- of the quotctl structure which is defined as
+ This ioctl() call manipulates disk quotas on UFS filesystems. fd is the
+ file descriptor returned by the open() system call after opening the
+ quotas file (located in the root directory of the filesystem running
+ quotas). Q_QUOTACTL is defined in /usr/include/sys/fs/ufs_quota.h. qp
+ is the address of the quotctl structure which is defined as
struct quotctl {
int op;
@@ -79,8 +79,7 @@
EFAULT addr is invalid.
- EINVAL The kernel has not been compiled with the QUOTA option. op is
- invalid.
+ EINVAL op is invalid.
ENOENT The quotas file specified by addr does not exist.
@@ -116,11 +115,11 @@
SEE ALSO
- getrlimit(2), mount(2), privileges(7), quota(8), quotacheck(8), quo-
- taon(8)
+ getrlimit(2), mount(2), ufs(4FS), privileges(7), quota(8), quo-
+ tacheck(8), quotaon(8)
-BUGS
- There should be some way to integrate this call with the resource limit
- interface provided by setrlimit() and getrlimit(2).
+NOTES
+ ZFS has a different quota implementation that does not support these
+ ioctl calls.
-Oracle Solaris 11.4 3 Nov 2021 quotactl(4I)
+Oracle Solaris 11.4 14 Jun 2024 quotactl(4I)
diff -NurbBw 11.4.69/man4i/sesio.4i 11.4.72/man4i/sesio.4i
--- 11.4.69/man4i/sesio.4i 2024-08-20 12:29:44.839856935 -0700
+++ 11.4.72/man4i/sesio.4i 2024-08-20 12:30:01.974342865 -0700
@@ -4,7 +4,7 @@
sesio - enclosure services device driver interface
SYNOPSIS
- #include <sys/sesio.h>
+ #include <sys/scsi/targets/sesio.h>
DESCRIPTION
The ses device driver provides the following ioctls as a means to ac-
@@ -63,18 +64,19 @@
status = ioctl(fd, SES_IOCTL_GETSTATE, abuf);
-
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
+------------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+------------------------------+-----------------------------+
- | Architecture |SPARC |
+ | Architecture |SPARC, x86 |
+ +------------------------------+-----------------------------+
+ | Availability |driver/storage/ses |
+------------------------------+-----------------------------+
SEE ALSO
- ses(4D), ioctl(9E)
+ ioctl(2), ses(4D)
-Oracle Solaris 11.4 27 Nov 2017 sesio(4I)
+Oracle Solaris 11.4 14 Jun 2024 sesio(4I)
diff -NurbBw 11.4.69/man4i/sockio.4i 11.4.72/man4i/sockio.4i
--- 11.4.69/man4i/sockio.4i 2024-08-20 12:29:44.881844362 -0700
+++ 11.4.72/man4i/sockio.4i 2024-08-20 12:30:02.013457934 -0700
@@ -8,11 +8,11 @@
DESCRIPTION
The ioctls listed in this manual page apply directly to sockets, inde-
- pendent of any underlying protocol. The setsockopt() call (see getsock-
- opt(3C)) is the primary method for operating on sockets, rather than on
- the underlying protocol or network interface. ioctls for a specific
- network interface or protocol are documented in the manual page for
- that interface or protocol.
+ pendent of any underlying protocol. The setsockopt(3C) call is the pri-
+ mary method for operating on sockets, rather than on the underlying
+ protocol or network interface. ioctls for a specific network interface
+ or protocol are documented in the manual page for that interface or
+ protocol.
SIOCSPGRP The argument is a pointer to an int. Set the process-
group ID that will subsequently receive SIGIO or SIGURG
@@ -42,4 +42,4 @@
SEE ALSO
ioctl(2), getsockopt(3C)
-Oracle Solaris 11.4 8 Nov 1996 sockio(4I)
+Oracle Solaris 11.4 14 Jun 2024 sockio(4I)
diff -NurbBw 11.4.69/man4i/streamio.4i 11.4.72/man4i/streamio.4i
--- 11.4.69/man4i/streamio.4i 2024-08-20 12:29:44.936174602 -0700
+++ 11.4.72/man4i/streamio.4i 2024-08-20 12:30:02.096220742 -0700
@@ -11,8 +11,11 @@
int ioctl(int fildes, int command, ... /*arg*/);
DESCRIPTION
- STREAMS (see intro(3)) ioctl commands are a subset of the ioctl(2) com-
- mands and perform a variety of control functions on streams.
+ STREAMS is a set of kernel mechanisms that support the development of
+ network services and data communication drivers. It is composed of
+ utility routines, kernel facilities, and a set of data structures.
+ STREAMS ioctl commands are a subset of the ioctl(2) commands that per-
+ form a variety of control functions on STREAMS.
The fildes argument is an open file descriptor that refers to a stream.
@@ -595,7 +598,7 @@
It allocates a message block and inserts the file pointer in the
block. The user id and group id associated with the sending process
are also inserted. This message is placed directly on the read
- queue (see intro(3)) of the stream head at the other end of the
+ queue (see Intro(3)) of the stream head at the other end of the
stream pipe to which it is connected. On failure, errno is set to
one of the following values:
@@ -655,7 +658,7 @@
EFAULT arg points outside the allocated address space.
- EMFILE NOFILES file descriptors are currently open.
+ EMFILE {OPEN_MAX} file descriptors are currently open.
ENXIO Hangup received on fildes.
@@ -1021,9 +1024,9 @@
SEE ALSO
strconf(1), close(2), fcntl(2), getmsg(2), ioctl(2), open(2), poll(2),
- putmsg(2), read(2), write(2), signal(3C), signal.h(3HEAD), intro(3)
+ putmsg(2), read(2), write(2), signal(3C), signal.h(3HEAD), Intro(3)
STREAMS Programming Guide
-Oracle Solaris 11.4 11 May 2021 streamio(4I)
+Oracle Solaris 11.4 14 Jun 2024 streamio(4I)
diff -NurbBw 11.4.69/man4i/termio.4i 11.4.72/man4i/termio.4i
--- 11.4.69/man4i/termio.4i 2024-08-20 12:29:45.001926931 -0700
+++ 11.4.72/man4i/termio.4i 2024-08-20 12:30:02.155268212 -0700
@@ -42,10 +42,10 @@
put is occurring, and are only lost when the character input buffers of
the system become completely full, which is rare. For example, the num-
ber of characters in the line discipline buffer may exceed {MAX_CANON}
- and IMAXBEL (see below) is not set, or the user may accumulate {
- MAX_INPUT} number of input characters that have not yet been read by
- some program. When the input limit is reached, all the characters saved
- in the buffer up to that point are thrown away without notice.
+ and IMAXBEL (see below) is not set, or the user may accumulate {MAX_IN-
+ PUT} number of input characters that have not yet been read by some
+ program. When the input limit is reached, all the characters saved in
+ the buffer up to that point are thrown away without notice.
Session Management (Job Control)
A control terminal will distinguish one of the process groups in the
@@ -125,7 +125,7 @@
by all characters that have not been read. Reprinting also occurs auto-
matically if characters that would normally be erased from the screen
are fouled by program output. The characters are reprinted as if they
- were being echoed; consequencely, if ECHO is not set, they are not
+ were being echoed; consequently, if ECHO is not set, they are not
printed.
@@ -146,68 +146,56 @@
to timeout bursty and short-term data transmissions. The four possible
values for MIN and TIME and their interactions are described below.
- Case A: MIN > 0, TIME > 0 In this case, TIME serves as an interchar-
- acter timer and is activated after the
- first character is received. Since it is
- an intercharacter timer, it is reset after
- a character is received. The interaction
- between MIN and TIME is as follows: as
- soon as one character is received, the in-
- tercharacter timer is started. If MIN
- characters are received before the inter-
- character timer expires (note that the
- timer is reset upon receipt of each char-
- acter), the read is satisfied. If the
- timer expires before MIN characters are
- received, the characters received to that
- point are returned to the user. Note that
- if TIME expires, at least one character
- will be returned because the timer would
- not have been enabled unless a character
- was received. In this case (MIN > 0, TIME
- > 0), the read sleeps until the MIN and
- TIME mechanisms are activated by the re-
- ceipt of the first character. If the num-
- ber of characters read is less than the
- number of characters available, the timer
- is not reactivated and the subsequent read
- is satisfied immediately.
-
-
- Case B: MIN > 0, TIME = 0 In this case, since the value of TIME is
- zero, the timer plays no role and only MIN
- is significant. A pending read is not sat-
- isfied until MIN characters are received
- (the pending read sleeps until MIN charac-
- ters are received). A program that uses
- this case to read record based terminal
- I/O may block indefinitely in the read op-
- eration.
-
-
- Case C: MIN = 0, TIME > 0 In this case, since MIN = 0, TIME no
- longer represents an intercharacter timer:
- it now serves as a read timer that is ac-
- tivated as soon as a read is done. A read
- is satisfied as soon as a single character
- is received or the read timer expires.
- Note that, in this case, if the timer ex-
- pires, no character is returned. If the
- timer does not expire, the only way the
- read can be satisfied is if a character is
- received. In this case, the read will not
- block indefinitely waiting for a charac-
- ter; if no character is received within
- TIME *.10 seconds after the read is initi-
- ated, the read returns with zero charac-
- ters.
-
-
- Case D: MIN = 0, TIME = 0 In this case, return is immediate. The
- minimum of either the number of characters
- requested or the number of characters cur-
- rently available is returned without wait-
- ing for more characters to be input.
+ Case A: MIN > 0, TIME > 0
+
+ In this case, TIME serves as an intercharacter timer and is acti-
+ vated after the first character is received. Since it is an inter-
+ character timer, it is reset after a character is received. The in-
+ teraction between MIN and TIME is as follows: as soon as one char-
+ acter is received, the intercharacter timer is started. If MIN
+ characters are received before the intercharacter timer expires
+ (note that the timer is reset upon receipt of each character), the
+ read is satisfied. If the timer expires before MIN characters are
+ received, the characters received to that point are returned to the
+ user. Note that if TIME expires, at least one character will be re-
+ turned because the timer would not have been enabled unless a char-
+ acter was received. In this case (MIN > 0, TIME > 0), the read
+ sleeps until the MIN and TIME mechanisms are activated by the re-
+ ceipt of the first character. If the number of characters read is
+ less than the number of characters available, the timer is not re-
+ activated and the subsequent read is satisfied immediately.
+
+
+ Case B: MIN > 0, TIME = 0
+
+ In this case, since the value of TIME is zero, the timer plays no
+ role and only MIN is significant. A pending read is not satisfied
+ until MIN characters are received (the pending read sleeps until
+ MIN characters are received). A program that uses this case to read
+ record based terminal I/O may block indefinitely in the read opera-
+ tion.
+
+
+ Case C: MIN = 0, TIME > 0
+
+ In this case, since MIN = 0, TIME no longer represents an inter-
+ character timer: it now serves as a read timer that is activated as
+ soon as a read is done. A read is satisfied as soon as a single
+ character is received or the read timer expires. Note that, in this
+ case, if the timer expires, no character is returned. If the timer
+ does not expire, the only way the read can be satisfied is if a
+ character is received. In this case, the read will not block indef-
+ initely waiting for a character; if no character is received within
+ TIME *.10 seconds after the read is initiated, the read returns
+ with zero characters.
+
+
+ Case D: MIN = 0, TIME = 0
+
+ In this case, return is immediate. The minimum of either the number
+ of characters requested or the number of characters currently
+ available is returned without waiting for more characters to be in-
+ put.
Comparing Different Cases of MIN, TIME Interaction
@@ -606,21 +594,11 @@
TABDLY Select horizontal tab delays or tab expansion:
-
- o TAB0
-
-
- o TAB1
-
-
- o TAB2
-
-
- o TAB3 -- expand tabs to spaces
-
-
- o XTABS -- expand tabs to spaces
-
+ TAB0
+ TAB1
+ TAB2
+ TAB3 -- expand tabs to spaces
+ XTABS -- expand tabs to spaces
BSDLY Select backspace delays:
@@ -777,8 +754,8 @@
B460800 460800 baud
- CSIZE Character size:
+ CSIZE Character size:
CS5 5 bits
@@ -848,14 +823,14 @@
To store the output speed in the termios structure pointed to by
termios_p see the following code segment.
-
-
speed_t ospeed;
+
if (ospeed > CBAUD) {
termios_p->c_cflag |= CBAUDEXT;
ospeed -= (CBAUD + 1);
- } else
+ } else {
termios_p->c_cflag &= ~CBAUDEXT;
+ }
termios_p->c_cflag =
(termios_p->c_cflag & ~CBAUD) | (ospeed & CBAUD);
@@ -902,8 +873,9 @@
if ((ispeed << IBSHIFT) > CIBAUD) {
termios_p->c_cflag |= CIBAUDEXT;
ispeed -= ((CIBAUD >> IBSHIFT) + 1);
- } else
+ } else {
termios_p->c_cflag &= ~CIBAUDEXT;
+ }
termios_p->c_cflag =
(termios_p->c_cflag & ~CIBAUD) |
((ispeed << IBSHIFT) & CIBAUD);
@@ -1030,7 +1000,7 @@
If ICANON is set, canonical processing is enabled. This enables the
erase and kill edit functions, and the assembly of input characters
- into lines delimited by NL-c, EOF, EOL, and EOL. If ICANON is not set,
+ into lines delimited by NL-c, EOF, EOL, and EOL2. If ICANON is not set,
read requests are satisfied directly from the input queue. A read is
not satisfied until at least MIN characters have been received or the
timeout value TIME has expired between characters. This allows fast
@@ -1460,8 +1428,8 @@
"tv" is the system clock timestamp when the event
(pulse on the DCD pin) occurred. "serial" is the ordi-
- nal of the event, which each consecutive event being
- assigned the next ordinal. The first event registered
+ nal of the event, with each consecutive event being as-
+ signed the next ordinal. The first event registered
gets a "serial" value of 1. The TIOCGPPSEV returns the
last event registered; multiple calls will persistently
return the same event until a new one is registered. In
@@ -1477,6 +1445,6 @@
SEE ALSO
stty(1), fork(2), getpgid(2), getsid(2), ioctl(2), setsid(2), sigac-
tion(2), signal(3C), tcsetpgrp(3C), termios(3C), signal.h(3HEAD),
- streamio(4I)
+ streamio(4I), termiox(4I)
-Oracle Solaris 11.4 11 May 2021 termio(4I)
+Oracle Solaris 11.4 14 Jun 2024 termio(4I)
diff -NurbBw 11.4.69/man4i/termiox.4i 11.4.72/man4i/termiox.4i
--- 11.4.69/man4i/termiox.4i 2024-08-20 12:29:45.040171744 -0700
+++ 11.4.72/man4i/termiox.4i 2024-08-20 12:30:02.189591449 -0700
@@ -299,15 +299,12 @@
queued for input are discarded and then the change occurs.
-FILES
- /dev/*
-
SEE ALSO
stty(1), ioctl(2), termio(4I)
NOTES
- The termiox(4I) system call is provided for compatibility with previous
- releases and its use is discouraged. Instead, the termio(4I) system
- call is recommended. See termio(4I) for usage information.
+ The termiox(4I) ioctls are provided for compatibility with previous re-
+ leases and their use is discouraged. Instead, the termio(4I) ioctls are
+ recommended. See termio(4I) for usage information.
-Oracle Solaris 11.4 15 Apr 2019 termiox(4I)
+Oracle Solaris 11.4 14 Jun 2024 termiox(4I)
diff -NurbBw 11.4.69/man4i/uscsi.4i 11.4.72/man4i/uscsi.4i
--- 11.4.69/man4i/uscsi.4i 2024-08-20 12:29:45.087586252 -0700
+++ 11.4.72/man4i/uscsi.4i 2024-08-20 12:30:02.233385403 -0700
@@ -174,11 +172,11 @@
target.
- USCSI_RESET_ALL USCSI_RESET_ALL, USCSI_RESET/USCSI_RESET_TARGET
+ USCSI_RESET_ALL USCSI_RESET_ALL, USCSI_RESET/USCSI_RESET_TARGET,
and USCSI_RESET_LUN are mutually exclusive op-
tions and issuing them in any simultaneous combi-
nation will result in implementation-dependent
- behavior
+ behavior.
When a USCSI reset request is combined with other
SCSI commands, the following semantics take ef-
@@ -200,11 +198,10 @@
USCSI_RENEGOT Tells USCSI to renegotiate wide mode and synchro-
nous transfer speed before the transmitted SCSI
- command is executed. This flag in effects tells
- the target driver to pass the FLAG_RENEGOTI-
- ATE_WIDE_SYNC flag in the SCSI packet before
- passing the command to an adapter driver for
- transport.
+ command is executed. This flag tells the target
+ driver to pass the FLAG_RENEGOTIATE_WIDE_SYNC
+ flag in the SCSI packet before passing the com-
+ mand to an adapter driver for transport.
See the scsi_pkt(9S) flag FLAG_RENEGOTI-
ATE_WIDE_SYNC for more information.
@@ -285,4 +282,4 @@
same struct uscsi_cmd programming interface, but perform device associ-
ation in some other manner.
-Oracle Solaris 11.4 3 Nov 2021 uscsi(4I)
+Oracle Solaris 11.4 14 Jun 2024 uscsi(4I)
diff -NurbBw 11.4.69/man4i/vt.4i 11.4.72/man4i/vt.4i
--- 11.4.69/man4i/vt.4i 2024-08-20 12:29:45.120755308 -0700
+++ 11.4.72/man4i/vt.4i 2024-08-20 12:30:02.274455572 -0700
@@ -17,7 +17,7 @@
VT's are accessed in the same way as other devices. The open(2) system
- call is used to open the virtual console and read(2), write(2) and
+ call is used to open the virtual console and read(2), write(2), and
ioctl(2) are used in the normal way and support the functionality of
the underlying device. In addition, some virtual console-specific
ioctls are provided and described below.
@@ -40,17 +40,17 @@
virtual console 1-12. The sequence AltGraph + F# (where AltGraph repre-
sents the right Alt key and F# represent function keys 1 through 12) is
for virtual console 13-24. Alt + F1 chooses the system console (also
- known as virtual console 1). The sequence Alt + -> (where --> repre-
- sents the right directional arrow) selects the next VT in a circular
- ring fashion and Alt + <- ( where <- represents the left directional
- arrow) changes to the previous console in a circular fashion. The se-
- quence Alt + ^ (where ^ represents the up directional arrow) is for the
- last used console.
+ known as virtual console 1). The sequence Alt + -> (where -> represents
+ the right directional arrow) selects the next VT in a circular ring
+ fashion and Alt + <- (where <- represents the left directional arrow)
+ changes to the previous console in a circular fashion. The sequence Alt
+ + ^ (where ^ represents the up directional arrow) is for the last used
+ console.
Under graphics mode like Xorg, the sequence Ctrl-Alt + F# should be
used in place of Alt + F#. And the sequence Alt + <arrow> for VT
- switching don't work under Xorg, because this hotkey has been defined
+ switching doesn't work under Xorg, because this hotkey has been defined
as virtual workspace switching.
@@ -171,10 +168,7 @@
#define VT_AUTO 0 /* automatic VT switching */
#define VT_PROCESS 1 /* process controls switching */
-
- The structure is filled in with the current value
- for each field.
-
+ The structure is filled in with the current value for each field.
VT_GET_CONSUSER
@@ -237,7 +229,7 @@
sired mode. If process-control mode is specified, the signals used
to communicate with the process should be specified. If any signals
are not specified (value is zero), the signal default is SIGUSR1
- (for relsig and acqsig).
+ for relsig and acqsig.
VT_WAITACTIVE
@@ -255,6 +247,10 @@
ioctl(2), signal(3C), wscons(4D)
NOTES
+ Virtual terminals are managed by the service management facility,
+ smf(7), under the service identifier svc:/system/console-login.
+
+
By default, there are only five virtual console instance login prompts
running on /dev/vt/# (where "#" represents 2 to 6) in addition to the
system console running on /dev/console. Normally Xorg uses the seventh
@@ -272,15 +266,22 @@
online 17:49:11 svc:/system/console-login:vt5
online 17:49:11 svc:/system/console-login:vt6
- console-login:default is for the system console, others for
- virtual consoles.
- You can modify properties/disable/enable and remove/add
- virtual consoles using smf(7):
+
+ The console-login:default instance is for the system console, the rest
+ are for virtual consoles.
+
+
+ Administrative actions on this service, such as enabling, disabling, or
+ requesting restart, can be performed using svcadm(8). Property configu-
+ ration can be performed using svccfg(8).
+
+
+ For example, to add another text mode login prompt on vt8:
# svccfg -s console-login add vt8
# svccfg -s console-login:vt8 setprop ttymon/device=astring: "/dev/vt/8"
# svcadm enable console-login:vt8
-Oracle Solaris 11.4 13 Nov 2020 vt(4I)
+Oracle Solaris 11.4 14 Jun 2024 vt(4I)
diff -NurbBw 11.4.69/man4m/ldterm.4m 11.4.72/man4m/ldterm.4m
--- 11.4.69/man4m/ldterm.4m 2024-08-20 12:29:45.150180810 -0700
+++ 11.4.72/man4m/ldterm.4m 2024-08-20 12:30:02.325551050 -0700
@@ -201,12 +201,12 @@
HISTORY
Prior to Oracle Solaris 11.4, programs needed to push the ldterm module
- onto the slave side of a pseudo-terminal pair if open() was called from
- a program not linked for XPG4 or later standards. If called from a pro-
- gram linked with values-xpg4.o or values-xpg6.o, then open() would au-
- tomatically push ptem, ldterm, and ttcompat modules onto the slave
- side, and callers pushing them as well would encounter unexpected be-
- havior.
+ onto the subsidiary side of a pseudo-terminal pair if open() was called
+ from a program not linked for XPG4 or later standards. If called from a
+ program linked with values-xpg4.o or values-xpg6.o, then open() would
+ automatically push ptem, ldterm, and ttcompat modules onto the sub-
+ sidiary side, and callers pushing them as well would encounter unex-
+ pected behavior.
Oracle Solaris 11.4 added these modules to /etc/iu.system.ap for
@@ -214,4 +214,4 @@
of how the program is linked, and ensured that only one copy of each is
pushed onto each stream.
-Oracle Solaris 11.4 11 May 2021 ldterm(4M)
+Oracle Solaris 11.4 19 Jun 2024 ldterm(4M)
diff -NurbBw 11.4.69/man4m/pckt.4m 11.4.72/man4m/pckt.4m
--- 11.4.69/man4m/pckt.4m 2024-08-20 12:29:45.178001557 -0700
+++ 11.4.72/man4m/pckt.4m 2024-08-20 12:30:02.358169537 -0700
@@ -9,7 +9,7 @@
DESCRIPTION
pckt is a STREAMS module that may be used with a pseudo terminal to
packetize certain messages. The pckt module should be pushed (see
- I_PUSH on streamio(4I)) onto the master side of a pseudo terminal.
+ I_PUSH on streamio(4I)) onto the manager side of a pseudo terminal.
Packetizing is performed by prefixing a message with an M_PROTO mes-
@@ -22,19 +22,19 @@
packetized. All other message types are passed upstream unmodified.
- Since all unread state information is held in the master's stream head
+ Since all unread state information is held in the manager's stream head
read queue, flushing of this queue is disabled.
On the write-side, all messages are sent down unmodified.
- With this module in place, all reads from the master side of the pseudo
- terminal should be performed with the getmsg(2) or getpmsg() function.
- The control part of the message contains the message type. The data
- part contains the actual data associated with that message type. The
- onus is on the application to separate the data into its component
- parts.
+ With this module in place, all reads from the manager side of the
+ pseudo terminal should be performed with the getmsg(2) or getpmsg()
+ function. The control part of the message contains the message type.
+ The data part contains the actual data associated with that message
+ type. The onus is on the application to separate the data into its com-
+ ponent parts.
SEE ALSO
getmsg(2), ioctl(2), streamio(4I), termio(4I), ldterm(4M), ptem(4M)
@@ -42,4 +42,4 @@
STREAMS Programming Guide
-Oracle Solaris 11.4 3 Jul 1990 pckt(4M)
+Oracle Solaris 11.4 19 Jun 2024 pckt(4M)
diff -NurbBw 11.4.69/man4m/ptem.4m 11.4.72/man4m/ptem.4m
--- 11.4.69/man4m/ptem.4m 2024-08-20 12:29:45.227466266 -0700
+++ 11.4.72/man4m/ptem.4m 2024-08-20 12:30:02.385284932 -0700
@@ -11,9 +11,9 @@
discipline and pseudo terminal driver, emulates a terminal.
- The ptem module must be pushed (see I_PUSH, streamio(4I)) onto the
- slave side of a pseudo terminal STREAM, before the ldterm(4M) module is
- pushed. This is done automatically by autopush(8) on Oracle Solaris
+ The ptem module must be pushed (see I_PUSH, streamio(4I)) onto the sub-
+ sidiary side of a pseudo terminal STREAM, before the ldterm(4M) module
+ is pushed. This is done automatically by autopush(8) on Oracle Solaris
11.4 and later releases.
@@ -52,12 +52,12 @@
HISTORY
Prior to Oracle Solaris 11.4, programs needed to push the ptem module
- onto the slave side of a pseudo-terminal pair if open() was called from
- a program not linked for XPG4 or later standards. If called from a pro-
- gram linked with values-xpg4.o or values-xpg6.o, then open() would au-
- tomatically push ptem, ldterm, and ttcompat modules onto the slave
- side, and callers pushing them as well would encounter unexpected be-
- havior.
+ onto the subsidiary side of a pseudo-terminal pair if open() was called
+ from a program not linked for XPG4 or later standards. If called from a
+ program linked with values-xpg4.o or values-xpg6.o, then open() would
+ automatically push ptem, ldterm, and ttcompat modules onto the sub-
+ sidiary side, and callers pushing them as well would encounter unex-
+ pected behavior.
Oracle Solaris 11.4 added these modules to /etc/iu.system.ap for
@@ -65,4 +65,4 @@
of how the program is linked, and ensured that only one copy of each is
pushed onto each stream.
-Oracle Solaris 11.4 11 May 2021 ptem(4M)
+Oracle Solaris 11.4 19 Jun 2024 ptem(4M)
diff -NurbBw 11.4.69/man4m/ttcompat.4m 11.4.72/man4m/ttcompat.4m
--- 11.4.69/man4m/ttcompat.4m 2024-08-20 12:29:45.273910216 -0700
+++ 11.4.72/man4m/ttcompat.4m 2024-08-20 12:30:02.421184579 -0700
@@ -499,12 +499,12 @@
HISTORY
Prior to Oracle Solaris 11.4, programs needed to push the ttcompat mod-
- ule onto the slave side of a pseudo-terminal pair if open() was called
- from a program not linked for XPG4 or later standards. If called from a
- program linked with values-xpg4.o or values-xpg6.o, then open() would
- automatically push ptem, ldterm, and ttcompat modules onto the slave
- side, and callers pushing them as well would encounter unexpected be-
- havior.
+ ule onto the subsidiary side of a pseudo-terminal pair if open() was
+ called from a program not linked for XPG4 or later standards. If called
+ from a program linked with values-xpg4.o or values-xpg6.o, then open()
+ would automatically push ptem, ldterm, and ttcompat modules onto the
+ subsidiary side, and callers pushing them as well would encounter unex-
+ pected behavior.
Oracle Solaris 11.4 added these modules to /etc/iu.system.ap for
@@ -512,4 +512,4 @@
of how the program is linked, and ensured that only one copy of each is
pushed onto each stream.
-Oracle Solaris 11.4 11 May 2021 ttcompat(4M)
+Oracle Solaris 11.4 19 Jun 2024 ttcompat(4M)
diff -NurbBw 11.4.69/man5/nscd.conf.5 11.4.72/man5/nscd.conf.5
--- 11.4.69/man5/nscd.conf.5 2024-08-20 12:29:45.309165896 -0700
+++ 11.4.72/man5/nscd.conf.5 2024-08-20 12:30:02.467176260 -0700
@@ -201,6 +201,14 @@
value. See nsswitch.conf(5).
+ Restart nscd after any SMF service changes
+ The nscd process must be restarted for any SMF service changes to take
+ effect.
+
+ example# svcadm restart name-service/cache
+
+
+
EXAMPLES
Example 1 Setting the passwd Cache's negative_time_to_live Property
Value to Ten Seconds.
@@ -220,6 +228,114 @@
Note that you must add a property group before you can set the group's
properties.
+ Example 2 Disable the host and ipnode Cache
+
+
+ Disabling the host (or any other) cache may negatively impact perfor-
+ mance but is sometimes desired when using certain third party products.
+
+ example# svccfg -s name-service/cache
+ svc:/system/name-service/cache> addpg host application
+ svc:/system/name-service/cache> setprop host/enable_cache = false
+ svc:/system/name-service/cache> refresh
+
+
+
+ Note that you must add a property group before you can set the proper-
+ ties to that group.
+
+ Example 3 Re-enable a disabled host Cache
+
+
+ Re-enabling a previously disabled host (or any other) cache is straight
+ forward.
+
+ example# svccfg -s name-service/cache
+ svc:/system/name-service/cache> delcust host/enable_cache
+ svc:/system/name-service/cache> refresh
+
+
+
+ By default all caches are enabled, so this step is simply reversing a
+ previous administrator operation.
+
+ Example 4 Record minimal nscd diagnostics
+
+
+
+ Record minimal nscd diagnostics of incoming requests from processes and
+ report the success or failure of the requested lookups. Diagnostics
+ will be written to /usr/tmp/nscdlog. Setting the values in SMF causes
+ the diagnostics to be written indefinitely across reboots until dis-
+ abled.
+
+ example# svccfg -s name-service/cache
+ svc:/system/name-service/cache> setprop config/logfile = "/usr/tmp/nscdlog"
+ svc:/system/name-service/cache> setprop config/debug_level = "all"
+ svc:/system/name-service/cache> setprop config/debug_components = "(" "frontend" "cache" ")"
+ svc:/system/name-service/cache> refresh
+
+
+
+ Note this can be useful when attempting to track down which process is
+ performing unexpected or undesired lookups. See nscd(8) to enable diag-
+ nostics only on the active nscd process using nscd command line options
+ on a live system.
+
+
+ example# /usr/sbin/nscd -D all -C frontend,cache -L /usr/tmp/nscdlog
+
+
+ Example 5 Record full nscd diagnostics
+
+
+
+ Record full nscd diagnostics of all activity and details of all incom-
+ ing requests for all lookups. Diagnostics will be written to the file
+ /usr/tmp/nscdlog. Setting the values in SMF causes the diagnostics to
+ be written indefinitely across reboots until disabled. Depending on how
+ busy a system is, this amount of diagnostics can generate gigabytes
+ (GB) of output per second so caution should be used.
+
+ example# svccfg -s name-service/cache
+ svc:/system/name-service/cache> setprop config/logfile = "/usr/tmp/nscdlog"
+ svc:/system/name-service/cache> setprop config/debug_level = "all"
+ svc:/system/name-service/cache> setprop config/debug_components = "all"
+ svc:/system/name-service/cache> refresh
+
+
+
+ Note this may be useful in recording early boot naming problems. See
+ nscd(8) to enable diagnostics only on the active nscd process using
+ nscd command line options on a live system.
+
+
+ example# /usr/sbin/nscd -D all -C all -L /usr/tmp/nscdlog
+
+
+ Example 6 Disable nscd diagnostics
+
+
+
+ Disable previously enabled diagnostics by removing previously set prop-
+ erties.
+
+ example# svccfg -s name-service/cache
+ svc:/system/name-service/cache> delcust config/logfile
+ svc:/system/name-service/cache> delcust config/debug_level
+ svc:/system/name-service/cache> delcust config/debug_components
+ svc:/system/name-service/cache> refresh
+
+
+
+ Use this to turn off administrator enabled nscd diagnostics. See
+ nscd(8) to disable diagnostics only on the active nscd process using
+ nscd command line options on a live system.
+
+
+ example# /usr/sbin/nscd -D none -C none -L /dev/null
+
+
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
@@ -253,10 +369,11 @@
vice/cache service and replaced the /etc/nscd.conf administrative con-
figuration file. Starting with Oracle Solaris 11.4, the service must be
enabled and be online with the nscd daemon running for certain configu-
- rations to function correctly.
+ rations to function correctly. As of 11.4.63 nscd must be running for
+ lookups to any database backends other than files or DNS.
Starting with Oracle Solaris 11.4.57, the obsolete svc:/system/name-
service-cache was removed.
-Oracle Solaris 11.4 17 Jan 2024 nscd.conf(5)
+Oracle Solaris 11.4 11 Apr 2024 nscd.conf(5)
diff -NurbBw 11.4.69/man7/audit_syslog.7 11.4.72/man7/audit_syslog.7
--- 11.4.69/man7/audit_syslog.7 2024-08-20 12:29:45.340114870 -0700
+++ 11.4.72/man7/audit_syslog.7 2024-08-20 12:30:02.511543540 -0700
@@ -25,19 +25,24 @@
consists of two parts, a syslog header and a message.
- The syslog header contains the date and time the message was generated,
- the host name from which it was sent, auditd to indicate that it was
- generated by the audit daemon, an ID field used internally by the sys-
- log daemon, and audit.notice indicating the syslog facility and sever-
- ity values. The syslog header ends with the characters "] ", that is, a
+ The syslog header contains the date and time the message was processed
+ by syslog (this may be different to the actual audit event time) the
+ host name from which it was sent, auditd to indicate that it was gener-
+ ated by the audit daemon, an ID field used internally by the syslog
+ daemon, and audit.notice indicating the syslog facility and severity
+ values. The syslog header ends with the characters "] ", that is, a
closing square bracket and a space.
The message part starts with the event type from the header token. All
subsequent data appears only if contained in the original audit record
- and there is room in the 1024-byte maximum length syslog line. In the
- following example, the backslash (\) indicates a continuation; actual
- syslog messages are contained on one line:
+ and there is room in the 8192-byte maximum length syslog line. The plu-
+ gin can be configued to include the ISO:8601 format date and time from
+ the audit event as the first field of the message.
+
+
+ In the following example, the backslash (\) indicates a continuation;
+ actual syslog messages are contained on one line:
Oct 31 11:38:08 smothers auditd: [ID 917521 audit.notice] chdir(2) ok\
session 401 by joeuser as root:other from myultra obj /export/home
@@ -54,6 +59,15 @@
session <#> <#> is the session ID from the subject token.
+ proto <name> <name> is the remote access protocol name (ie NFS,
+ SMB). This field is generated only by remote per-
+ file access.
+
+
+ access <mode> <mode> is the mode used to access the obj. This
+ field is generated only by per-file access.
+
+
by <name> <name> is the audit ID from the subject token.
@@ -111,6 +125,10 @@
access(2) ok session 255 by janeuser as janeuser:staff from \
129.146.89.30 obj /etc/passwd
+ Nov 4 10:29:27 smothers auditd: [ID 521917 audit.notice] \
+ unlink(2) ok proto NFS access 0x10000 by janeuser as janeuser:staff from \
+ 129.146.89.30 obj /export/share/file1
+
OBJECT ATTRIBUTES
The p_flag attribute is used to further filter audit data being sent to
@@ -127,6 +145,13 @@
fault value is 1800 seconds, which is half the default cache ttl that
nscd(8) uses.
+
+ The p_event_ts attribute is used to enable the inclusion of the
+ ISO:8601 event data/time from the audit record. This is in addition to
+ any date/time information added by syslog in the header, note the sys-
+ log header date/time may differ from the event date/time as the message
+ is relayed through syslog servers.
+
EXAMPLES
Example 1 One Use of the plugin Line
@@ -166,6 +191,18 @@
that may be in multiple classes may still be included in the syslog
output.
+ Example 3 Include audit record time in syslog message
+
+
+
+ Timestamps added by syslog may not reflect the actual time the audit
+ record was generated. The plugin can be configured include the ISO8601
+ format date and time of the audit record:
+
+
+ auditconfig -setplugin audit_syslog active p_event_ts=1
+
+
ATTRIBUTES
See attributes(7) for a description of the following attributes:
@@ -225,4 +262,4 @@
HISTORY
The audit_syslog module was introduced in Solaris 10 3/05.
-Oracle Solaris 11.4 12 Sep 2023 au...g(7)
+Oracle Solaris 11.4 12 Mar 2024 au...g(7)
diff -NurbBw 11.4.69/man7/pam_krb5.7 11.4.72/man7/pam_krb5.7
--- 11.4.69/man7/pam_krb5.7 2024-08-20 12:29:45.379469186 -0700
+++ 11.4.72/man7/pam_krb5.7 2024-08-20 12:30:02.584917334 -0700
@@ -5,7 +5,7 @@
PAM modules for Kerberos V5
SYNOPSIS
- pam_krb5.so.1 [debug] [nowarn] [pkinit] [realm=realm_name]
+ pam_krb5.so.1 [debug] [nowarn] [warndays=] [pkinit] [realm=realm_name]
DESCRIPTION
The Kerberos V5 service module for PAM provides functionality for all
@@ -157,6 +157,11 @@
nowarn Turns off warning messages.
+ warndays=days Number of days to start warnings about password ex-
+ piry. Default if unspecified is 30 days. Applicable
+ only to the account PAM stack.
+
+
pkinit Indicates that the Kerberos V5 authentication mod-
ule should try Kerberos PKINIT authentication in-
stead of the default password-based Kerberos.
@@ -805,4 +810,4 @@
HISTORY
The pam_krb5 module was introduced in Solaris 8.
-Oracle Solaris 11.4 12 Sep 2023 pa...5(7)
+Oracle Solaris 11.4 27 Mar 2024 pa...5(7)
diff -NurbBw 11.4.69/man8/ikeadm.8 11.4.72/man8/ikeadm.8
--- 11.4.69/man8/ikeadm.8 2024-08-20 12:29:45.416626210 -0700
+++ 11.4.72/man8/ikeadm.8 2024-08-20 12:30:02.635593735 -0700
@@ -211,10 +211,11 @@
Door interface 0x00000100 door
Config file processing 0x00000200 config
Label processing 0x00000400 label
+ DPD processing 0x00000800 dpd
IKEv2 only
- Packet processing 0x00000800 packet
+ Packet processing 0x00001000 packet
Audit interaction 0x00002000 audit
Additional Notes 0x00004000 note
Threading issues 0x00008000 thread
@@ -739,4 +740,4 @@
As in.iked and in.ikev2d can run only in the global zone, kernel zones,
and exclusive-IP zones, this command is not useful in shared-IP zones.
-Oracle Solaris 11.4 21 Jun 2021 ikeadm(8)
+Oracle Solaris 11.4 16 Apr 2024 ikeadm(8)
diff -NurbBw 11.4.69/man8/in.rlogind.8 11.4.72/man8/in.rlogind.8
--- 11.4.69/man8/in.rlogind.8 2024-08-20 12:29:45.449827498 -0700
+++ 11.4.72/man8/in.rlogind.8 2024-08-20 12:30:02.678261610 -0700
@@ -36,9 +36,9 @@
Once the source port and address have been checked, in.rlogind allo-
cates a pseudo-terminal and manipulates file descriptors so that the
- slave half of the pseudo-terminal becomes the stdin, stdout, and stderr
- for a login process. The login process is an instance of the login(1)
- program, invoked with the -r.
+ subsidiary half of the pseudo-terminal becomes the stdin, stdout, and
+ stderr for a login process. The login process is an instance of the lo-
+ gin(1) program, invoked with the -r.
The login process then proceeds with the pam(3PAM) authentication
@@ -46,7 +46,7 @@
prompts the user to login.
- The parent of the login process manipulates the master side of the
+ The parent of the login process manipulates the manager side of the
pseudo-terminal, operating as an intermediary between the login process
and the client instance of the rlogin program. In normal operation, a
packet protocol is invoked to provide Ctrl-S and Ctrl-Q type facilities
@@ -214,4 +214,4 @@
the generic_limited_net.xml service profile. In Oracle Solaris 11.4, it
is disabled by default.
-Oracle Solaris 11.4 28 Jun 2023 in.rlogind(8)
+Oracle Solaris 11.4 19 Jun 2024 in.rlogind(8)
diff -NurbBw 11.4.69/man8/in.telnetd.8 11.4.72/man8/in.telnetd.8
--- 11.4.69/man8/in.telnetd.8 2024-08-20 12:29:45.507359510 -0700
+++ 11.4.72/man8/in.telnetd.8 2024-08-20 12:30:02.718306728 -0700
@@ -17,11 +17,11 @@
in.telnetd operates by allocating a pseudo-terminal device for a
- client, then creating a login process which has the slave side of the
- pseudo-terminal as its standard input, output, and error. in.telnetd
- manipulates the master side of the pseudo-terminal, implementing the
- TELNET protocol and passing characters between the remote client and
- the login process.
+ client, then creating a login process which has the subsidiary side of
+ the pseudo-terminal as its standard input, output, and error. in.tel-
+ netd manipulates the manager side of the pseudo-terminal, implementing
+ the TELNET protocol and passing characters between the remote client
+ and the login process.
When a TELNET session starts up, in.telnetd sends TELNET options to the
@@ -296,4 +296,4 @@
the generic_limited_net.xml service profile. In Oracle Solaris 11.4, it
is disabled by default.
-Oracle Solaris 11.4 12 May 2022 in.telnetd(8)
+Oracle Solaris 11.4 19 Jun 2024 in.telnetd(8)
diff -NurbBw 11.4.69/man8/ldmd.8 11.4.72/man8/ldmd.8
--- 11.4.69/man8/ldmd.8 2024-08-20 12:29:45.555595856 -0700
+++ 11.4.72/man8/ldmd.8 2024-08-20 12:30:02.753358264 -0700
@@ -387,7 +387,13 @@
waits for the domains to stop. The ldm stop-domain command issues
an error if the domain or domains do not stop after the specified
timeout expires. The shutdown_timeout value must be greater than
- zero. The default value is 100 seconds.
+ zero. The default value is 180 seconds.
+
+
+ ldmd/sstore_mapping_enabled
+
+ Enables ldmd to publish stats and mapping metadata to StatsStore.
+ The default value is true.
ldmd/tls_certificate
@@ -457,4 +463,4 @@
For more information about the ldmd SMF properties, see the Oracle VM
Server for SPARC 3.6 Administration Guide.
-Oracle Solaris 11.4 14 Jun 2023 ldmd(8)
+Oracle Solaris 11.4 29 May 2024 ldmd(8)
diff -NurbBw 11.4.69/man8/mount_nfs.8 11.4.72/man8/mount_nfs.8
--- 11.4.69/man8/mount_nfs.8 2024-08-20 12:29:45.595896121 -0700
+++ 11.4.72/man8/mount_nfs.8 2024-08-20 12:30:02.793874383 -0700
@@ -252,6 +252,15 @@
range locks held by other clients.
+ noresvport
+
+ Use randomized, non-privileged ports to contact NFS servers. By
+ default, mounts will use privileged ports (port numbers below
+ 1024), counting down from 1023. With this mount option set, use
+ ports 1024 and above picked at random. This can help avoid re-
+ connection delays and issues in virtualized environments.
+
+
port=n
The server IP port number. The default is NFS_PORT. If the port
diff -NurbBw 11.4.69/man8/vscanadm.8 11.4.72/man8/vscanadm.8
--- 11.4.69/man8/vscanadm.8 2024-08-20 12:29:45.630117451 -0700
+++ 11.4.72/man8/vscanadm.8 2024-08-20 12:30:02.825985699 -0700
@@ -126,6 +126,39 @@
+ use-tls
+
+ Specifies whether to use TLS when connecting to the scan en-
+ gines. Valid values are:
+
+ on Use TLS when connecting to the scan engines. This is the
+ default value.
+
+
+ off Do not use TLS when connecting to the scan engines.
+
+
+
+ host-match
+
+ Specifies whether to require that the certificate matches the
+ hostname supplied. Valid values are:
+
+ on Require that the certificate matches the hostname sup-
+ plied. This is the default value.
+
+
+ off Do not require that the certificate matches the hostname
+ supplied.
+
+
+
+ trusted-certs-path
+
+ Specifies the trusted certificates location. The default value
+ is /etc/openssl/certs.
+
+
vscanadm import -p property filename
@@ -313,7 +346,27 @@
# vscanadm set -p types=-doc,+*
- Example 4 Displaying the File Types List
+ Example 4 Using TLS when connecting to the scan engines.
+
+
+
+ To use TLS when connecting to the scan engines, enter
+
+
+ # vscanadm set -p use-tls=on
+
+
+ Example 5 Setting Trusted Certificates Location
+
+
+
+ To set trusted certificates location, enter
+
+
+ # vscanadm set -p trusted-certs-path=/var/my_trusted_certs_path
+
+
+ Example 6 Displaying the File Types List
@@ -323,7 +376,7 @@
# vscanadm get -p types
- Example 5 Adding the Scan Engine
+ Example 7 Adding the Scan Engine
@@ -333,7 +386,7 @@
# vscanadm add-engine my_eng
- Example 6 Disabling the Scan Engine
+ Example 8 Disabling the Scan Engine
@@ -343,7 +396,7 @@
# vscanadm set-engine -p enable=off my_eng
- Example 7 Displaying Scan Engine Properties
+ Example 9 Displaying Scan Engine Properties
@@ -353,7 +406,7 @@
# vscanadm get-engine my_eng
- Example 8 Removing Scan Engine
+ Example 10 Removing Scan Engine
@@ -363,7 +416,7 @@
# vscanadm remove-engine my_eng
- Example 9 Displaying Vscan Service General and Scan Engine Properties
+ Example 11 Displaying Vscan Service General and Scan Engine Properties
@@ -433,4 +486,4 @@
All of these authorizations are included in the "VSCAN Management" pro-
file.
-Oracle Solaris 11.4 27 Nov 2017 vscanadm(8)
+Oracle Solaris 11.4 30 Jan 2024 vscanadm(8)
diff -NurbBw 11.4.69/man8/zfs.8 11.4.72/man8/zfs.8
--- 11.4.69/man8/zfs.8 2024-08-20 12:29:45.726395174 -0700
+++ 11.4.72/man8/zfs.8 2024-08-20 12:30:02.924700225 -0700
@@ -247,13 +247,11 @@
Snapshots can have arbitrary names. Snapshots of volumes can be cloned
- or rolled back, but cannot be accessed independently.
+ or rolled back to, but cannot be accessed independently.
File system snapshots can be accessed under the .zfs/snapshot directory
- in the root of the file system. Snapshots are automatically mounted on
- demand and may be unmounted at regular intervals. The visibility of the
- .zfs directory can be controlled by the snapdir property.
+ in the root of the file system.
Clones
A clone is a writable volume or file system whose initial contents are
@@ -274,6 +272,11 @@
a clone of the specified file system, which makes it possible to de-
stroy the file system that the clone was created from.
+
+ Filesystem clones can be accessed under the .zfs/clone directory in the
+ root of the file system if the clone has its mountpoint property set to
+ clonedir.
+
Mount Points
Creating a ZFS file system is a simple operation, so the number of file
systems per system is likely to be numerous. To cope with this, ZFS au-
@@ -310,6 +313,34 @@
legacy, ZFS makes no attempt to manage the file system, and the admin-
istrator is responsible for mounting and unmounting the file system.
+ .zfs Directory
+ The .zfs directory in the root of the file system contains information
+ and access to some of that file system's features. This directory is
+ always accessible, however the visibility of the .zfs directory is con-
+ trolled by the snapdir property described below.
+
+
+ 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
+ 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.
+
+
+ When SMB shares are created, the SMB share name appears as an entry in
+ the .zfs/shares directory in the root of the file system. See
+ zfs_share(8) for more information.
+
Zones
The physical properties of an added file system are controlled by the
global administrator. However, the zone administrator can create, mod-
@@ -862,7 +893,7 @@
fault label (none) can be mounted.
- mountpoint=path | none | legacy
+ mountpoint=path | none | legacy | clonedir
Controls the mount point used for this file system. See the "Mount
Points" section for more information on how this property is used.
@@ -875,6 +906,12 @@
the property was changed. In addition, any shared file systems are
unshared and shared in the new location.
+ If the filesystem is a clone, then the mountpoint property may be
+ set to clonedir. You can determine whether a filesystem is a clone
+ by checking whether the origin property is non-NULL. In that case,
+ the filesysem will be mounted in the .zfs/clone directory of the
+ filesystem this is a clone of.
+
nbmand=on | off
@@ -1207,7 +1244,8 @@
Controls whether the .zfs directory is hidden or visible in the
root of the file system as discussed in the "Snapshots" section.
- The default value is hidden.
+ The default value is hidden. See the ".zfs Directory" section for
+ more information on the contents of this directory.
version=1 | 2 | current
@@ -3570,4 +3608,4 @@
modified in multiple ways. Any action that causes a change in the
st_ctim (see stat(2)) is a basis for reporting a modification.
-Oracle Solaris 11.4 21 Sep 2023 zfs(8)
+Oracle Solaris 11.4 13 Mar 2024 zfs(8)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment