From owner-freebsd-config Thu Apr 23 13:32:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20869 for freebsd-config-outgoing; Thu, 23 Apr 1998 13:32:29 -0700 (PDT) (envelope-from owner-freebsd-config@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20864 for ; Thu, 23 Apr 1998 13:32:18 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id NAA01940; Thu, 23 Apr 1998 13:32:04 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Wes Peters - Softweyr LLC cc: allen@xmission.xmission.com, campbell@xmission.xmission.com (Chris Campbell), allenc@verinet.com, config@FreeBSD.ORG Subject: Re: Config Databases In-reply-to: Your message of "Thu, 23 Apr 1998 14:24:43 MDT." <199804232024.OAA18834@xmission.xmission.com> Date: Thu, 23 Apr 1998 13:32:04 -0700 Message-ID: <1937.893363524@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-config@FreeBSD.ORG Precedence: bulk > 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. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-config" in the body of the message