realpath.3: Remove ancient Linux libc details

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-06-29 11:33:06 +02:00
parent 875aad4841
commit 788b19a299
1 changed files with 10 additions and 10 deletions

View File

@ -175,10 +175,10 @@ A typical source fragment would be
.\" Solaris may return a relative pathname when the
.\" .I path
.\" argument is relative.
The prototype of
.BR realpath ()
is given in \fI<unistd.h>\fP in libc4 and libc5,
but in \fI<stdlib.h>\fP everywhere else.
.\" The prototype of
.\" .BR realpath ()
.\" is given in \fI<unistd.h>\fP in libc4 and libc5,
.\" but in \fI<stdlib.h>\fP everywhere else.
.SS GNU extensions
If the call fails with either
.BR EACCES
@ -215,12 +215,12 @@ The
.I "resolved_path\ ==\ NULL"
feature, not standardized in POSIX.1-2001,
but standardized in POSIX.1-2008, allows this design problem to be avoided.
.LP
The libc4 and libc5 implementation contained a buffer overflow
(fixed in libc-5.4.13).
Thus, set-user-ID programs like
.BR mount (8)
needed a private version.
.\" .LP
.\" The libc4 and libc5 implementation contained a buffer overflow
.\" (fixed in libc-5.4.13).
.\" Thus, set-user-ID programs like
.\" .BR mount (8)
.\" needed a private version.
.SH SEE ALSO
.BR readlink (2),
.BR canonicalize_file_name (3),