From owner-freebsd-config Fri Apr 24 16:51:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28840 for freebsd-config-outgoing; Fri, 24 Apr 1998 16:51:08 -0700 (PDT) (envelope-from owner-freebsd-config@FreeBSD.ORG) Received: from const. (willow18.verinet.com [199.45.181.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28823 for ; Fri, 24 Apr 1998 16:50:59 -0700 (PDT) (envelope-from allenc@verinet.com) Received: (from allenc@localhost) by const. (8.8.8/8.8.8) id RAA18027 for config@FreeBSD.ORG; Fri, 24 Apr 1998 17:52:24 -0600 (MDT) (envelope-from allenc) Date: Fri, 24 Apr 1998 17:52:24 -0600 (MDT) From: allen campbell Message-Id: <199804242352.RAA18027@const.> To: config@FreeBSD.ORG Subject: Re: Config Databases In-Reply-To: <19980424093259.13767@deepo.prosa.dk> Sender: owner-freebsd-config@FreeBSD.ORG Precedence: bulk > Case 1: vi /etc/group && insert garbage -> something breaks, the user > might/will notice -> in any case, he can track down and look in > /etc/group and _see_ the mistakes > > Case 2: vipw && insert garbage -> feedback on what's wrong right away > > In the first suggestion (silently bouncing) means there's not even > _trace_ of the mods, right ? Hmmm.. The overwhelming consensus is to support a writable configfs. I agree with you but because of the results of the feedback, I am going along with the writable configfs, provided we can find an acceptable method of reporting errors. Allen Campbell allenc@verinet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-config" in the body of the message