From 6a8780971a4b6b09543a8b543a3ef599e425b95c Mon Sep 17 00:00:00 2001 From: Pawel Jakub Dawidek Date: Sun, 7 Jan 2007 17:32:16 +0000 Subject: Prefer "to be modified" over "to be opened for writing". This is quite tricky situation, because we allow to open a file with O_RDONLY|O_TRUNC. O_TRUNC modifies a file, but we actually don't open it for writing. EISDIR is also returned when we try to open a directory O_RDONLY|O_TRUNC, which is correct. POSIX says that "The result of using O_TRUNC with O_RDONLY is undefined.", we choose to accept it (Solaris did the same), that's why "to be modified" seems more accurate to me. --- lib/libc/sys/open.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lib/libc') diff --git a/lib/libc/sys/open.2 b/lib/libc/sys/open.2 index 0496ce0a8506..e56ddc0cb12a 100644 --- a/lib/libc/sys/open.2 +++ b/lib/libc/sys/open.2 @@ -238,7 +238,7 @@ does not permit writing. Too many symbolic links were encountered in translating the pathname. .It Bq Er EISDIR The named file is a directory, and the arguments specify -it is to be opened for writing. +it is to be modified. .It Bq Er EROFS The named file resides on a read-only file system, and the file is to be modified. -- cgit v1.2.3