Date: Thu, 23 Apr 1998 14:45:45 -0600 (MDT) From: Wes Peters - Softweyr LLC <softweyr@xmission.com> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: config@FreeBSD.ORG Subject: Re: Config Databases Message-ID: <199804232045.OAA22676@xmission.xmission.com> In-Reply-To: <1937.893363524@time.cdrom.com> from "Jordan K. Hubbard" at Apr 23, 98 01:32:04 pm
index | next in thread | previous in thread | raw e-mail
>
> > Keep in mind that the configfs can return whatever error necessary;
>
> I know, but deciding *which errors* to return could consume a lot of
> time. I really do think one would save a considerable amount of time
> and contraversy by simply implementing it as I suggested. Some errno
> returns *will* suggest themselves so obviously that there's no reason
> not to return them (ENOENT certainly being one :-), but I'd just shy
> completely away from the whole "I/O error" class and just write that off
> as something to grapple with (maybe, haha) in the 2nd version.
I see what you're saying. ENOENT, EPERM, EROFS where they make sense,
and ESCREWED (well, EIO) for everything else? ;^)
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
http://www.xmission.com/~softweyr softweyr@xmission.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-config" in the body of the message
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804232045.OAA22676>
