Paul Eggert wrote: > So possibly this behavior is also kernel-dependent > (AT_EMPTY_PATH was introduced in Linux 2.6.39, maybe the kernels are > buggy before that?).
That's well possible. I haven't investigated whether the unexpected behaviour comes from glibc vs. from the kernel. Bruno
