incorporate comments from Mike Hibler

SCCS-vsn: share/doc/psd/05.sysman/1.2.t 8.7
SCCS-vsn: share/doc/psd/05.sysman/2.2.t 8.6
SCCS-vsn: share/doc/psd/05.sysman/2.5.t 8.5

diff --git a/usr/src/share/doc/psd/05.sysman/1.2.t b/usr/src/share/doc/psd/05.sysman/1.2.t
index 408aa16..13c8e06 100644 (file)
--- a/usr/src/share/doc/psd/05.sysman/1.2.t
+++ b/usr/src/share/doc/psd/05.sysman/1.2.t
@@ -3,7 +3,7 @@
 .\"
 .\" %sccs.include.redist.roff%
 .\"
 .\"
 .\" %sccs.include.redist.roff%
 .\"

-.\"    @(#)1.2.t       8.6 (Berkeley) %G%
+.\"    @(#)1.2.t       8.7 (Berkeley) %G%

 .\"
 .Sh 2 "Memory management
 .Sh 3 "Text, data, and stack
 .\"
 .Sh 2 "Memory management
 .Sh 3 "Text, data, and stack


@@ -113,8 +113,10 @@ unless the MAP_FIXED flag is given,
 in which case the exact address will be used or the call will fail.
 The \fIaddr\fP parameter
 must be a multiple of the pagesize (if MAP_FIXED is given).
 in which case the exact address will be used or the call will fail.
 The \fIaddr\fP parameter
 must be a multiple of the pagesize (if MAP_FIXED is given).

-If \fIpos\fP and \fIlen\fP are not a multiple of pagesize,
-they will be rounded by the system as necessary;
+The \fIpos\fP parameter must specify a file offset that is
+a multiple of the pagesize.
+If \fIlen\fP is not a multiple of pagesize,
+it will be rounded up to a multiple of pagesize by the system;

 the rounding may cause the mapped region to extend past the specified range.
 A successful
 .Fn mmap
 the rounding may cause the mapped region to extend past the specified range.
 A successful
 .Fn mmap

diff --git a/usr/src/share/doc/psd/05.sysman/2.2.t b/usr/src/share/doc/psd/05.sysman/2.2.t
index a539c96..9e2e586 100644 (file)
--- a/usr/src/share/doc/psd/05.sysman/2.2.t
+++ b/usr/src/share/doc/psd/05.sysman/2.2.t
@@ -3,7 +3,7 @@
 .\"
 .\" %sccs.include.redist.roff%
 .\"
 .\"
 .\" %sccs.include.redist.roff%
 .\"

-.\"    @(#)2.2.t       8.5 (Berkeley) %G%
+.\"    @(#)2.2.t       8.6 (Berkeley) %G%

 .\"
 .Sh 2 "Filesystem
 .Sh 3 "Overview
 .\"
 .Sh 2 "Filesystem
 .Sh 3 "Overview


@@ -227,6 +227,9 @@ see section
 for the semantics of
 .Fn flock
 style locks.
 for the semantics of
 .Fn flock
 style locks.

+The O_ASYNC flag enables the SIGIO signal to be sent to
+the process group of the opening process when I/O is possible,
+e.g., upon availability of data to be read.

 .Sh 4 "Creating references to devices
 .PP
 The filesystem allows entries which reference peripheral devices.
 .Sh 4 "Creating references to devices
 .PP
 The filesystem allows entries which reference peripheral devices.


@@ -282,7 +285,20 @@ Hard links and symbolic links have different
 properties.  A hard link ensures that the target
 file will always be accessible, even after its original
 directory entry is removed; no such guarantee exists for a symbolic link.
 properties.  A hard link ensures that the target
 file will always be accessible, even after its original
 directory entry is removed; no such guarantee exists for a symbolic link.

-Symbolic links can span filesystems boundaries.
+Unlike hard links,
+symbolic links can refernce directories and span filesystems boundaries.
+An
+.Fn lstat
+call on a hard link will return the information about the
+file (or directory) that the link references.
+A symbolic link does not have an owner,
+group, permissions, access and modification times, etc.
+The only attributes returned from an
+.Fn lstat
+that refer to the symbolic link itself
+are the file type (S_IFLNK), size, blocks, and link count (always 1).
+The other attributes are filled in from
+the directory that contains the link.

 .LP
 The following calls create a new link, named \fIpath2\fP,
 to \fIpath1\fP:
 .LP
 The following calls create a new link, named \fIpath2\fP,
 to \fIpath1\fP:

diff --git a/usr/src/share/doc/psd/05.sysman/2.5.t b/usr/src/share/doc/psd/05.sysman/2.5.t
index fac5420..2b71395 100644 (file)
--- a/usr/src/share/doc/psd/05.sysman/2.5.t
+++ b/usr/src/share/doc/psd/05.sysman/2.5.t
@@ -3,7 +3,7 @@
 .\"
 .\" %sccs.include.redist.roff%
 .\"
 .\"
 .\" %sccs.include.redist.roff%
 .\"

-.\"    @(#)2.5.t       8.4 (Berkeley) %G%
+.\"    @(#)2.5.t       8.5 (Berkeley) %G%

 .\"
 .Sh 2 "Process debugging
 .Sh 3 "Traditional debugging
 .\"
 .Sh 2 "Process debugging
 .Sh 3 "Traditional debugging


@@ -22,9 +22,6 @@ and examine and change its core image.
 Its primary use is for the implementation of breakpoint debugging.
 There are four arguments whose interpretation
 depends on a request argument.
 Its primary use is for the implementation of breakpoint debugging.
 There are four arguments whose interpretation
 depends on a request argument.

-Generally, pid is the process ID of the traced process,
-which must be a child (no more distant descendant)
-of the tracing process.

 A process being traced behaves normally until it
 encounters a signal (whether internally generated like
 ``illegal instruction'' or externally generated
 A process being traced behaves normally until it
 encounters a signal (whether internally generated like
 ``illegal instruction'' or externally generated