X-Git-Url: http://git.osdn.net/view?p=linuxjm%2FLDP_man-pages.git;a=blobdiff_plain;f=original%2Fman2%2Ftruncate.2;h=eb3c1cd382392d396808ca276849f02727dc8042;hp=4d12683889eb5a263dcc3dfe1f0bc64a86b1fd59;hb=4ea6bb24817f6f049d6bbc90ecd77a869876f9b0;hpb=e9e6c106d11bd9cca5f4a6585364b93f5ae3007a

diff --git a/original/man2/truncate.2 b/original/man2/truncate.2
index 4d126838..eb3c1cd3 100644
--- a/original/man2/truncate.2
+++ b/original/man2/truncate.2
@@ -40,7 +40,7 @@
 .\" Modified 2002-04-06 by Andries Brouwer <aeb@cwi.nl>
 .\" Modified 2004-06-23 by Michael Kerrisk <mtk.manpages@gmail.com>
 .\"
-.TH TRUNCATE 2 2011-09-08 "Linux" "Linux Programmer's Manual"
+.TH TRUNCATE 2 2015-01-22 "Linux" "Linux Programmer's Manual"
 .SH NAME
 truncate, ftruncate \- truncate a file to a specified length
 .SH SYNOPSIS
@@ -123,7 +123,8 @@ or the named file is not writable by the user.
 .BR path_resolution (7).)
 .TP
 .B EFAULT
-.I Path
+The argument
+.I path
 points outside the process's allocated address space.
 .TP
 .B EFBIG
@@ -163,13 +164,17 @@ The named file does not exist.
 A component of the path prefix is not a directory.
 .TP
 .B EPERM
-.\" This happens for at least MSDOS and VFAT file systems
+.\" This happens for at least MSDOS and VFAT filesystems
 .\" on kernel 2.6.13
-The underlying file system does not support extending
+The underlying filesystem does not support extending
 a file beyond its current size.
 .TP
+.B EPERM
+The operation was prevented by a file seal; see
+.BR fcntl (2).
+.TP
 .B EROFS
-The named file resides on a read-only file system.
+The named file resides on a read-only filesystem.
 .TP
 .B ETXTBSY
 The file is a pure procedure (shared text) file that is being executed.
@@ -218,8 +223,8 @@ exceeds the file length
 is not specified at all in such an environment):
 either returning an error, or extending the file.
 Like most UNIX implementations, Linux follows the XSI requirement
-when dealing with native file systems.
-However, some nonnative file systems do not permit
+when dealing with native filesystems.
+However, some nonnative filesystems do not permit
 .BR truncate ()
 and
 .BR ftruncate ()
@@ -240,6 +245,11 @@ system calls that handle large files.
 However, these details can be ignored by applications using glibc, whose
 wrapper functions transparently employ the more recent system calls
 where they are available.
+
+On some 32-bit architectures,
+the calling signature for these system calls differ,
+for the reasons described in
+.BR syscall (2).
 .SH BUGS
 A header file bug in glibc 2.12 meant that the minimum value of
 .\" http://sourceware.org/bugzilla/show_bug.cgi?id=12037
@@ -252,3 +262,12 @@ This has been fixed in later glibc versions.
 .BR open (2),
 .BR stat (2),
 .BR path_resolution (7)
+.SH COLOPHON
+This page is part of release 3.79 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.