From owner-freebsd-ports Mon Apr 2 3: 0:54 2001 Delivered-To: freebsd-ports@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id F210537B72B for ; Mon, 2 Apr 2001 03:00:48 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 2111 invoked by uid 1000); 2 Apr 2001 09:59:40 -0000 Date: Mon, 2 Apr 2001 12:59:40 +0300 From: Peter Pentchev To: Neil Blakey-Milner Cc: ports@FreeBSD.org Subject: Re: Port startup scripts configuration data - /etc/rc.conf? Message-ID: <20010402125940.K462@ringworld.oblivion.bg> Mail-Followup-To: Neil Blakey-Milner , ports@FreeBSD.org References: <20010319111737.B515@ringworld.oblivion.bg> <20010402122940.F462@ringworld.oblivion.bg> <20010402114259.E44609@rapier.smartspace.co.za> <20010402124505.G462@ringworld.oblivion.bg> <20010402115312.F44609@rapier.smartspace.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010402115312.F44609@rapier.smartspace.co.za>; from nbm@mithrandr.moria.org on Mon, Apr 02, 2001 at 11:53:12AM +0200 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Apr 02, 2001 at 11:53:12AM +0200, Neil Blakey-Milner wrote: > On Mon 2001-04-02 (12:45), Peter Pentchev wrote: > > On Mon, Apr 02, 2001 at 11:42:59AM +0200, Neil Blakey-Milner wrote: > > > On Mon 2001-04-02 (12:29), Peter Pentchev wrote: > > > > Absolutely no opinions? :) I gather, then, that it would not be considered > > > > a Bad Thing (tm) to do ports configs that way? :) > > > > > > It's ok, but it'll need a change for 5.x sometime soon too, if my > > > prescience is correct. (: > > > > You mean the NetBSD rc.d/ thing? Weeell.. wouldn't source_rc_confs > > still work? Please please please make it still work! ;) > > Yeah. I suspect that we'll end up with a "/etc/sourceconf", which will > return the configuration without any special magic functions and stuff. > It'll by default just read in /etc/defaults/rc.conf and /etc/rc.conf as > per the function. Hmmm that could be nice, assuming it still honors $rc_conf_files :) > I'm reasonably sure that we can leave in the function, and work around > the function itself in /etc/defaults/rc.conf when writing non-sh tools > to read resource configuration. Well, this is my guess as how things > will continue, since it'll allow expansion to using netinfo, ldap, or > whatever for configuration. About non-sh tools.. wouldn't that involve also exporting all the env vars? I believe none of the rc.conf scripts currently export any.. G'luck, Peter -- This sentence claims to be an Epimenides paradox, but it is lying. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message