I spent some time tracing what version of Linux itself each one was added in. Note: This doesn't necessarily show that they originated with linux (the opposite in some cases), but it should help get a good handle on dates (for where to look in other OSes' history). And, date/version added to linux might itself be an interesting column to include. V7 - this is where EFAULT changed from 106 to 14 http://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/include/errno.h Minix 1.1 http://minnie.tuhs.org/cgi-bin/utree.pl?file=Minix1.1/usr/include/errno.h Minix 1.5 - where 0.1 apparently took its numeric assignments from http://minnie.tuhs.org/cgi-bin/utree.pl?file=Minix1.5/include/errno.h 0.01 - first errno.h - interesting comment. http://lxr.linux.no/linux-old+v0.01/include/errno.h 0.95 - adds ELOOP http://lxr.linux.no/linux-old+v0.95/include/errno.h 0.96c - last errno.h http://lxr.linux.no/linux-old+v0.96c/include/errno.h 0.97.0 has first linux/errno.h, and a whole pile of new error numbers http://lxr.linux.no/linux-old+v0.97.0/include/linux/errno.h 0.99.0 - EWOULDBLOCK vaue changed http://lxr.linux.no/linux-old+v0.99.0/include/linux/errno.h 0.99.14 - adds 122 EDQUOT http://lxr.linux.no/linux-old+v0.99.14/include/linux/errno.h 2.1.34 - adds 123 and 124 http://lxr.linux.no/linux-old+v2.1.34/include/asm-i386/errno.h 2.6.10 - 125 through 129 added http://lxr.linux.no/linux-bk+v2.6.10/include/asm-generic/errno.h Still haven't spent the time to find: Where 45-47 went, 51, value change of EDEADLOCK 2005-05-01 Addition of EOWNERDEAD and ENOTRECOVERABLE: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h… (This says it was done to support an external patch, so linux is probably not the originating system) 2009-06-03 Addition of ERFKILL http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h… 2011-03-17 EHWPOISON http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h… EDOTDOT caught my eye for some reason - maybe because it's the only one you attributed to linux in a long list of SVr1 ones... what were 72 through 76 in SVR1?

I also looked up EDOTDOT and found reference to RFS but not much info about it. Why was it not used? Not reliable enough? I have often thought that the stateless, idempotent NFS protocol leaves a lot to be desired due to its inability to implement unix semantics (as discussed in the wikipedia stub article on RFS), has this been improved with NFS4? Should RFS be revived and used? Some of its features sounded quite attractive (location transparency, etc). It does appear to have the ability to execute a program remotely?? What happens with regard to PIDs, home directory etc in this case? Does anyone know? cheers, Nick On Fri, Apr 1, 2011 at 1:23 PM, Michael Davidson < michael_davidson(a)pacbell.net&gt; wrote: