From owner-freebsd-config Thu Apr 23 00:48:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23838 for freebsd-config-outgoing; Thu, 23 Apr 1998 00:48:01 -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 AAA23816 for ; Thu, 23 Apr 1998 00:47:58 -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 AAA28587; Thu, 23 Apr 1998 00:47:42 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: allen campbell cc: config@FreeBSD.ORG Subject: Re: Config Databases In-reply-to: Your message of "Thu, 23 Apr 1998 00:30:18 MDT." <199804230630.AAA15142@const.> Date: Thu, 23 Apr 1998 00:47:41 -0700 Message-ID: <28583.893317661@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-config@FreeBSD.ORG Precedence: bulk > Now our portal process is expected to parse the buffer and put the > result in our configuration database. Fortunately, the portal > process in question was implemented very well and the login shell > omission is noticed. > > Now what? What is the portal file system supposed to do with this? Silently refuse the operation. Bob would be able to save the passwd file, but when he looked at it again he'd see it was as if he'd never touched it. Confusing? Sure, at least until people get the idea, but I think it's the only paradigm which makes sense. Your /etc is made of rubber - you hit it in the wrong place and it simply bounces back like nothing ever happened. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-config" in the body of the message