* Bruno Haible: > Pádraig Brady wrote: >> https://sourceware.org/ml/libc-alpha/2019-06/msg00873.html > > In the NEWS entry, Florian writes: > > Applications which use the > copy_file_range function will have to be run on kernels which implement > the copy_file_range system call. > > I find this misleading. Coreutils will want to continue to use > copy_file_range whenever the libc provides this function, and at the > same time be able to run on all Linux kernel versions.
What's misleading about it? If you want copy_file_range functionality, you will need an implementation of it, and since glibc no longer contains one after this change, you need one from the kernel. You can still call the function, of course, but it's use is really limited because it sets errno ENOSYS and returns -1. Thanks, Florian
