Thanks for finding the XtoX_syserr_conv() functions. I was sure that
AFS had *some* story for this, but it was eluding me.
Excerpts from transarc.external.info-afs: 15-May-96 Re: AMDS problem
with AFS3.4a Jeffrey [EMAIL PROTECTED] (2326*)
> com_err already reserves the first 255 error codes for "system" errors
> (i.e. errno values). My suggestion would be to take _all_ errors that
> can occur between the fileserver and client, and define "standard"
> names for them, in a separate block of com_err error codes. Doing this
> right would require changes across a couple of versions of AFS, but it
> is doable. I would continue to reserve the first 255 for errors actually
> generated on the local system.
I believe that DFS got at least this much right, though it doesn't
really help the AFS situation. *All* 1-255 errno values are always made
system-independent before being returned from the file server and are
always converted to system-dependent form in the client. To do this
with AFS you'd indeed need to rev all the clients before revving the
servers.
DFS also has a different mechanism for doing advisory file locking, and
the exchanged error codes for any conflicts come from com_err-like error
numbers so they're platform-independent, and they're thus translated to
local semantics on each platform.
Craig
