From owner-freebsd-config Thu Apr 23 13:45:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22580 for freebsd-config-outgoing; Thu, 23 Apr 1998 13:45:57 -0700 (PDT) (envelope-from owner-freebsd-config@FreeBSD.ORG) Received: from xmission.xmission.com (softweyr@xmission.xmission.com [198.60.22.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22573 for ; Thu, 23 Apr 1998 13:45:51 -0700 (PDT) (envelope-from softweyr@xmission.xmission.com) Received: (from softweyr@localhost) by xmission.xmission.com (8.8.8/8.7.5) id OAA22676; Thu, 23 Apr 1998 14:45:46 -0600 (MDT) From: Wes Peters - Softweyr LLC Message-Id: <199804232045.OAA22676@xmission.xmission.com> Subject: Re: Config Databases To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 23 Apr 1998 14:45:45 -0600 (MDT) Cc: config@FreeBSD.ORG In-Reply-To: <1937.893363524@time.cdrom.com> from "Jordan K. Hubbard" at Apr 23, 98 01:32:04 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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. 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