Just came across this formatting issue in copy_file_range(2). I went
ahead and wrote a quick fix and also did some searching for similar bugs
across the rest of the manuals with awk(1), but didn’t come across
anything.
Fixes: b983fe3a (2025-11-09; "man/man2/copy_file_range.2: glibc no longer provides fallback after 2.30")
Signed-off-by: Thomas Voss <mail@tvoss.eu>
Message-ID: <
b9f152d28bcff7ae45189138485e122d696defe6.
1778709713.git.mail@tvoss.eu>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
implement this system call.
.\" glibc.git 5a659ccc0ec2 (2019-06-28; "io: Remove copy_file_range emulation [BZ #24744]")
Since glibc 2.30, that fallback has been removed; the function now
-fails with ENOSYS if the kernel lacks support for .BR copy_file_range ().
+fails with ENOSYS if the kernel lacks support for
+.BR copy_file_range ().
.SH NOTES
If
.I fd_in