From owner-freebsd-config  Thu Apr 23 14:04:26 1998
Return-Path: <owner-freebsd-config@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA25250
          for freebsd-config-outgoing; Thu, 23 Apr 1998 14:04:26 -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 OAA25243
          for <config@freebsd.org>; Thu, 23 Apr 1998 14:04:15 -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 OAA02200;
	Thu, 23 Apr 1998 14:04:01 -0700 (PDT)
	(envelope-from jkh@time.cdrom.com)
To: Wes Peters - Softweyr LLC <softweyr@xmission.com>
cc: config@FreeBSD.ORG
Subject: Re: Config Databases 
In-reply-to: Your message of "Thu, 23 Apr 1998 14:45:45 MDT."
             <199804232045.OAA22676@xmission.xmission.com> 
Date: Thu, 23 Apr 1998 14:04:01 -0700
Message-ID: <2195.893365441@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-config@FreeBSD.ORG
Precedence: bulk

> I see what you're saying.  ENOENT, EPERM, EROFS where they make sense,
> and ESCREWED (well, EIO) for everything else?  ;^)

No, ENOTHING.  As I said, the operations should just silently
"succeed" in the cases where the user has attempted to do a bonehead
file operation but not reflect the change.  "Never check for an error
condition you don't know how to handle." :-)

				Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-config" in the body of the message