From owner-freebsd-current Tue Nov 2 13:42:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C5208154B1 for ; Tue, 2 Nov 1999 13:42:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA52978; Tue, 2 Nov 1999 13:42:33 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Nov 1999 13:42:33 -0800 (PST) From: Matthew Dillon Message-Id: <199911022142.NAA52978@apollo.backplane.com> To: Garance A Drosihn Cc: Doug Barton , freebsd-current@FreeBSD.ORG Subject: Re: minor heads up - /etc/make.conf{,.local} being moved References: <199910271928.MAA35915@apollo.backplane.com> <381F1722.3F85DA1@simplenet.com> <199911021703.JAA51793@apollo.backplane.com> <381F1B08.AF4E0585@gorean.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :At 9:10 AM -0800 11/2/99, Doug Barton wrote: :>Matthew Dillon wrote: :> > I think it is necessary to make it exit for now, because what we are :> > really doing is a net-0 gain in files... turning what used to be :> > functionality in /etc/make.conf.local into /etc/make.conf. The :> > intent is not to add a third file. :> :> Ok, well put me on record as wanting three files. : :Sounds like it would be fine to have three files, you just shouldn't :use /etc/make.conf.local as the name of that third file. Your site's :own /etc/make.conf (with "local to your site" changes) could include :logic to pick up "machine-specific" settings via some other filename. :Maybe /etc/make.conf.hostname, or /etc/hostdefs/make.conf : :I'm not quite sure what filename is best, I'm just saying that you :should be able to get the flexibility you want even though we "choke" :on /etc/make.conf.local (just to catch those people who don't realize :these first two files have been moved around) : :--- :Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Yes, precisely. What I do for site distribution is have a /conf directory hierarchy. The machine autoconfigures itself by any number of means to determine which subdirectory to use and creates a softlink /conf/ME which points to the subdirectory, /conf/. All the major files in /etc then become softlinks to /conf/ME/. For make.conf, a three-file version would have /etc/defaults/make.conf, /etc/make.conf which contains the installation-wide parameters, and it would include /conf/ME/make.conf for the platform-specific parameters. And there you have it... -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message