Hey Florian. On Sun, 2023-08-27 at 21:41 +0200, Florian Weimer wrote: > To what degree is this dependent on the file system? Does the VFS > layer > restrict these error codes for anything else? I don't think so. THB, no idea what the various filesystems or the VFS do - I merely tried to clarify between what's already documented as of now and what POSIX specifies. > Maybe > strictly speaking, the added wording is still accurate, but the > conclusion that ENXIO means socket would be incorrect draw, I think. Well, strictly speaking, I think that my wording doesn't say that... but I see that one could easily conclude that. If I add something like > … > ENXIO, which Linux uses to indicate (amongst others) that the file is > a UNIX domain socket. ? But the same possible ambiguity might come up in the future for POSIX/EOPNOTSUPP. Should POSIX add further semantics to that error (like it also already does for ENXIO), a reader could conclude that in POSIX EOPNOTSUPP would only be used to indicate a socket (which would then no longer be the case). OTOH, I think it might get a bit overkill if we describe all these details. Cheers, Chris
