From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] Tracing origins of errno names/numbers
Date: Thu, 24 Mar 2011 10:24:01 +1000 [thread overview]
Message-ID: <20110324002401.GA15851@minnie.tuhs.org> (raw)
Hi all,
PJ from groklaw.net has asked me to trace the origin of
the errno names and values in recent versions of Linux. Attached
is where I am up to. The columns are:
- errno name
- errno value in Linux, and its original value if different
- system which originally defined it
- release date of that system
There are a few errno names which I don't think I have the
correct original system:
EDOTDOT, ENOMEDIUM, EMEDIUMTYPE, ECANCELED,
ENOKEY, EKEYEXPIRED, EKEYREVOKED, EKEYREJECTED,
EOWNERDEAD, ENOTRECOVERABLE, ERFKILL
Can anybody shed some light on these ones, that would be
great, especially if they come from SysV or Unixware.
Also, if you can spot any other mistakes, let me know!
Many thanks in advance,
Warren
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20110324/260be8c0/attachment.html>
next reply other threads:[~2011-03-24 0:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 0:24 Warren Toomey [this message]
2011-03-31 23:41 ` Random832
2011-04-01 2:23 ` Michael Davidson
2011-04-01 2:51 ` Nick Downing
2011-04-01 3:26 Michael Davidson
2011-04-01 3:38 ` John Cowan
2011-04-01 3:40 ` Larry McVoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110324002401.GA15851@minnie.tuhs.org \
--to=wkt@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).