Date: Wed, 30 Aug 2000 15:27:00 -0500 From: "Jacques A. Vidrine" <n@nectar.com> To: John DeBoskey <jwd@unx.sas.com> Cc: freebsd-arch@FreeBSD.ORG, "Daniel C. Sobral" <dcs@newsguy.com> Subject: Re: Request for review: nsswitch Message-ID: <20000830152700.E15458@hamlet.nectar.com> In-Reply-To: <20000830142617.B86368@unx.sas.com>; from jwd@unx.sas.com on Wed, Aug 30, 2000 at 02:26:17PM -0400 References: <20000830071347.A1167@hamlet.nectar.com> <39AD222B.CE9A26B5@newsguy.com> <20000830132053.A15387@hamlet.nectar.com> <20000830142617.B86368@unx.sas.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 30, 2000 at 02:26:17PM -0400, John DeBoskey wrote: > How about a simple compromise? > > While the internal defaults may be sane, they are `invisible' to > the average user. What if we put the defaults into a > /etc/defaults/nsswitch.conf file. If they need to be overridden > locally, then a /etc/nsswitch.conf file is created and the > defaults version is ignored.. ?? I think I'll just be careful to document the defaults in the man page, unless I hear a good argument for putting another file in /etc/defaults. I don't think it is worth the effort or diverging from the NetBSD code to provide defaults for a file that will typically have maybe two lines, and at most five (with the current feature set). -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org 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?20000830152700.E15458>