9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/include/ape/errno.h
Date: Tue,  6 Jan 2004 15:04:43 +0000	[thread overview]
Message-ID: <6fdd2cff904f7a990a9d30b28786019b@terzarima.net> (raw)
In-Reply-To: <E1AdrDL-000JNk-Ng@t40.swtch.com>

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

they certainly differ between Unix system variants
they differ between xBSD and Linux.

finding them on Linux is fun:
	errno.h -> bits/errno.h + ifdefs + defs -> linux/errno.h -> asm/errno.h [whew!]

which i note in passing has
	#define EWOULDBLOCK EAGAIN

amongst other values, i find for example on FreeBSD:

#define	ENETDOWN	50		/* Network is down */
#define	ENETUNREACH	51		/* Network is unreachable */
#define	ENETRESET	52		/* Network dropped connection on reset */

but on Linux:

#define	ENETDOWN	100	/* Network is down */
#define	ENETUNREACH	101	/* Network is unreachable */
#define	ENETRESET	102	/* Network dropped connection because of reset */

and on Irix5.3 and Solaris

#define ENETDOWN        127             /* Network is down */
#define ENETUNREACH     128             /* Network is unreachable */
#define ENETRESET       129             /* Network dropped connection because

so all in all it seems a relative waste of time
and effort to make Plan 9's match
one rather than the other.

[-- Attachment #2: Type: message/rfc822, Size: 2519 bytes --]

From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/include/ape/errno.h
Date: Tue, 06 Jan 2004 08:25:42 -0500
Message-ID: <E1AdrDL-000JNk-Ng@t40.swtch.com>

> What would be safe here?  Renumber all the error codes to match
> NetBSD (I'm sure all *BSDs are identical, but I guess I ought to
> check) and submit the changed header file to Bell Labs so that a
> new copy of libap.a can be generated to match?

down that path lies madness.  use the names, that's what they're for.
the numbers aren't supposed to matter!

russ

  reply	other threads:[~2004-01-06 15:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06 10:24 Lucio De Re
2004-01-06 10:29 ` Charles Forsyth
2004-01-06 10:47   ` Lucio De Re
2004-01-06 10:56     ` Charles Forsyth
2004-01-06 11:19       ` Lucio De Re
2004-01-06 12:30     ` David Presotto
2004-01-06 12:48       ` [9fans] Newbie Question: Plan 9 for a windows file server? Chris Lamrock
2004-01-06 13:03       ` [9fans] /sys/include/ape/errno.h Lucio De Re
2004-01-06 13:15         ` David Presotto
2004-01-06 13:25         ` Russ Cox
2004-01-06 15:04           ` Charles Forsyth [this message]
2004-01-06 17:24           ` Lucio De Re
2004-01-06 12:42 ` David Presotto
2004-01-06 12:59   ` Lucio De Re
2004-01-06 15:22 ` ron minnich
2004-01-06 16:41   ` Nigel Roles
2004-01-06 18:19 Richard C Bilson

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=6fdd2cff904f7a990a9d30b28786019b@terzarima.net \
    --to=forsyth@terzarima.net \
    --cc=9fans@cse.psu.edu \
    /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).