From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <005901c449a3$71ff2520$637f7d50@SOMA> From: "boyd, rounin" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> References: Subject: Re: Error reporting (Was: [9fans] GNU Make) Date: Thu, 3 Jun 2004 21:46:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 9484cac8-eacd-11e9-9e20-41e7f4b1d025 > > bzzzzt! no > > well, i might have exaggerated a little, but a quick poke around the > bsd man pages gives me the following percentages (of all error codes > mentioned, 1129 total): checking my _physical_ 9th Ed manual there are/were 37 [EGREG]. 8/9th Ed was based on 4.1BSD, for the record. > so EINVAL and EIO are definitely up there. former yes, but it means BUGGERED. latter, as forsyth said, can mean many things (i think its intention was to indicate a physical i/o error). i think probably dennis is the best reference, to clear up this stupid ephemera. > EFAULT pretty much always means the same thing, so it doesn't count. it does count. it means BUGGERED. it's a good one; it means you fucked up and there is NO recovery (unless you loop over user mode addresses until you smash somewhere with something). you get EFAULT? you have a bug.