On Wed, May 15, 2024 at 1:14 AM Philip Guenther <guent...@gmail.com> wrote:
> On Tue, May 14, 2024 at 11:59 AM Walter Alejandro Iglesias < > w...@roquesor.com> wrote: > >> Hi Philip, >> >> On Tue May 14 19:40:04 2024 Philip Guenther wrote: >> > If you like, you could try the following patch to pax to more gracefully >> > handle filesystems with time resolution more granular than nanoseconds. >> >> After applying your patch, as I'd done before reporting the issue, I >> sycronized my home directory to an external ext2fs drive with the >> command showed by the man page: >> >> $ pax -rw -v -Z -Y source target >> >> This time only one file stays updating again an again, a soft link I >> have in my ~/bin folder of /usr/local/bin/prename. > > > I think you've managed to hit a spot where the POSIX standard doesn't > provide a way for a program to find the information it needs to do its job > correctly. I've filed a ticket there > https://austingroupbugs.net/view.php?id=1831 > > We'll see if my understanding of pathconf() is incorrect or if someone has > a great idea for how to get around this... > So yeah, what's needed is pathconfat(2)** but whether this winding loose end ("That poor yak.") merits that much code and surface is yet to be examined deeply. Philip Guenther ** or lpathconf(2), but pathconfat(2) is better
