Hi, > On 12 Sep 2025, at 09:09, Olivier Certner <o...@freebsd.org> wrote: > >> That should certainly be done. I'll try to do it this weekend, if I have >> time. However, the need to revert this change will remain. FreeBSD 15 >> needs the ability to run both current and old Rust toolchains. > > Yes, and adding to that that I don't see any pressing reason to get rid of > readdir_r(), knowing a bit or two on that topic, irrespective of what Rust > will or will not do in the short/middle-term. Not detailing anything more > here, as I already did in https://reviews.freebsd.org/D52474 where I think > this discussion should continue. > Thanks and regards.
+1 And while I’m here, POSIX.1 defines for readdir_r (and readdir): [EOVERFLOW] One of the values in the structure to be returned cannot be represented correctly. …which I think would cover the case of indeterminate NAME_MAX/PATH_MAX for readdir_r. Also while I’m here, isn’t ESTALE a possibility for readdir/readdir_r on an NFS volume? > -- > Olivier Certner -- Bob Bishop r...@gid.co.uk
