The output from "nroff" and "groff" is unchanged. Signed-off-by: Bjarni Ingi Gislason <bjarniig@xxxxxxxxx> --- man2/link.2 | 18 +++++++++--------- man2/lseek.2 | 20 ++++++++++---------- 2 files changed, 19 insertions(+), 19 deletions(-) diff --git a/man2/link.2 b/man2/link.2 index 649ba00c7..db1407a6f 100644 --- a/man2/link.2 +++ b/man2/link.2 @@ -128,7 +128,7 @@ The following values can be bitwise ORed in If .I oldpath is an empty string, create a link to the file referenced by -.IR olddirfd +.I olddirfd (which may have been obtained using the .BR open (2) .B O_PATH @@ -138,12 +138,12 @@ In this case, can refer to any type of file except a directory. This will generally not work if the file has a link count of zero (files created with -.BR O_TMPFILE +.B O_TMPFILE and without -.BR O_EXCL +.B O_EXCL are an exception). The caller must have the -.BR CAP_DAC_READ_SEARCH +.B CAP_DAC_READ_SEARCH capability in order to use this flag. This flag is Linux-specific; define .B _GNU_SOURCE @@ -263,7 +263,7 @@ does not support the creation of hard links. .BR EPERM " (since Linux 3.6)" The caller does not have permission to create a hard link to this file (see the description of -.IR /proc/sys/fs/protected_hardlinks +.I /proc/sys/fs/protected_hardlinks in .BR proc (5)). .TP @@ -337,12 +337,12 @@ and .I newdirfd .TP .B EPERM -.BR AT_EMPTY_PATH +.B AT_EMPTY_PATH was specified in .IR flags , .I oldpath is an empty string, and -.IR olddirfd +.I olddirfd refers to a directory. .SH VERSIONS .BR linkat () @@ -409,11 +409,11 @@ and .I newpath are relative pathnames, glibc constructs pathnames based on the symbolic links in -.IR /proc/self/fd +.I /proc/self/fd that correspond to the .I olddirfd and -.IR newdirfd +.I newdirfd arguments. .SH BUGS On NFS filesystems, the return code may be wrong in case the NFS server diff --git a/man2/lseek.2 b/man2/lseek.2 index dfb819427..1c2f217d9 100644 --- a/man2/lseek.2 +++ b/man2/lseek.2 @@ -135,12 +135,12 @@ mapping the storage space actually allocated to a file. to the underlying storage may not be reported as a hole.) In the simplest implementation, a filesystem can support the operations by making -.BR SEEK_HOLE +.B SEEK_HOLE always return the offset of the end of the file, and making -.BR SEEK_DATA +.B SEEK_DATA always return -.IR offset +.I offset (i.e., even if the location referred to by .I offset is a hole, @@ -150,18 +150,18 @@ it can be considered to consist of data that is a sequence of zeros). .\" http://blogs.oracle.com/bonwick/entry/seek_hole_and_seek_data .PP The -.BR _GNU_SOURCE +.B _GNU_SOURCE feature test macro must be defined in order to obtain the definitions of -.BR SEEK_DATA +.B SEEK_DATA and -.BR SEEK_HOLE +.B SEEK_HOLE from .IR <unistd.h> . .PP The -.BR SEEK_HOLE +.B SEEK_HOLE and -.BR SEEK_DATA +.B SEEK_DATA operations are supported for the following filesystems: .IP * 3 Btrfs (since Linux 3.1) @@ -222,9 +222,9 @@ is associated with a pipe, socket, or FIFO. .SH CONFORMING TO POSIX.1-2001, POSIX.1-2008, SVr4, 4.3BSD. .PP -.BR SEEK_DATA +.B SEEK_DATA and -.BR SEEK_HOLE +.B SEEK_HOLE are nonstandard extensions also present in Solaris, FreeBSD, and DragonFly BSD; they are proposed for inclusion in the next POSIX revision (Issue 8). -- 2.20.1 -- Bjarni I. Gislason
