From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <67ce99a249859a0d4c3cd4502752ea7a@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: Error reporting (Was: [9fans] GNU Make)
Date: Thu,  3 Jun 2004 17:38:34 +0100
From: rog@vitanuova.com
In-Reply-To: <843a3575a6a686d2a306c699dc686407@terzarima.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 9444df30-eacd-11e9-9e20-41e7f4b1d025

EIO might be better for unknown error codes than ENOENT.

as far as i remember, most error codes in unix were
either EINVAL or EIO...

a brief glance at the read(2) man page under bsd:

[EINVAL]		The pointer associated with d was negative.
[EINVAL]		Iovcnt was less than or equal to 0, or greater than 16.
[EINVAL]		One of the iov_len values in the iov array was negative.
[EINVAL]		The sum of the iov_len values in the iov array overflowed a 32-bit integer.
[EINVAL]		The specified file offset is invalid.

oh joy.