On Tue, 15 Jul 2025 12:45:25 -0600, "Theo de Raadt" wrote:

> The vague POSIX number/name for EREMOTE has nothing to do with the
> error condition in inteldrm(4).

I didn't see it in IEEE Std 1003.1-2024, maybe I missed it?

> It has to do with path handling, probably NFS, it is very unclear.

It appears related to NFSERR_REMOTE (which is also 71) and comes
from NFS v3 apparently.  So this originated with Solaris.  However,
System V also defined EREMOTE as "Object is remote".  That appears
to be the meaning that the drm code is expecting and is how it is
documentd on Linux.

We could adopt the System V meaning of EREMOTE if we chose to do
so.  We are not using it anywhere other than the drm code.

 - todd