Date: Fri, 7 Jul 2000 12:20:38 -0500 From: Dan Nelson <dnelson@emsphone.com> To: Robert Watson <rwatson@FreeBSD.ORG> Cc: Assar Westerlund <assar@sics.se>, freebsd-arch@FreeBSD.ORG Subject: Re: Procedure for introducing new errno values? Message-ID: <20000707122038.A8474@dan.emsphone.com> In-Reply-To: <Pine.NEB.3.96L.1000707123729.65777M-100000@fledge.watson.org>; from "Robert Watson" on Fri Jul 7 12:38:13 GMT 2000 References: <20000513224341.B5564@dan.emsphone.com> <Pine.NEB.3.96L.1000707123729.65777M-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jul 07), Robert Watson said: > On Sat, 13 May 2000, Dan Nelson wrote: > > > Don't forget the errno mappings for the Linux/iBSC2/SVR4 compatibility > > modules, and src/sys/nfs/nfs_subs.c as well. > > In both of these cases, what is the appropriate value to choose if the > local ENOATTR doesn't map into a convenient remote/emulated errno value? For nfs_subs, the comments say: * Maps errno values to nfs error numbers. * Use NFSERR_IO as the catch all for ones not specifically defined in * RFC 1094. For linux, there are a lot of -6's in bsd_to_linux_errno (which map to ENXIO), so I'd say use that, or maybe ENODATA or ENOTSUP. If this error isn't going to be returned by any syscall that Linux emaulation uses, it doesn't matter what you pick :) -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000707122038.A8474>