Date: Thu, 31 Aug 2000 17:47:13 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: arch@freebsd.org Cc: n@nectar.com Subject: Re: Request for review: nsswitch Message-ID: <200009010047.RAA43862@vashon.polstra.com> In-Reply-To: <20000831130504.A26641@hamlet.nectar.com> References: <20000830071347.A1167@hamlet.nectar.com> <20000830132053.A15387@hamlet.nectar.com> <39AE970A.30208A56@newsguy.com> <20000831130504.A26641@hamlet.nectar.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20000831130504.A26641@hamlet.nectar.com>, Jacques A. Vidrine <n@nectar.com> wrote: > On Fri, Sep 01, 2000 at 02:34:02AM +0900, Daniel C. Sobral wrote: > > The reason is the following: when upgrading, merging changes to defaults > > against user modifications is not only very hard, but we have no support > > for it at all with our tools. > > The defaults for nsswitch.conf will not change, ever. They have been > chosen to emulate the traditional behavior. I have to agree with Daniel here. The whole point of nsswitch.conf is so you can customize it, right? Otherwise why bother with it? We are moving toward using immutable default versions in /etc/defaults with customizable overrides in /etc. That has made dealing with rc.conf and make.conf much, much easier. I think the ultimate goal should be that the admin can customize his /etc directory without the need to do _any_ merging. That means the defaults and the overrides have to be separated. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200009010047.RAA43862>