From owner-freebsd-current Wed Jul 26 11:34:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id LAA07173 for current-outgoing; Wed, 26 Jul 1995 11:34:01 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id LAA07165 for ; Wed, 26 Jul 1995 11:33:59 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id LAA20174; Wed, 26 Jul 1995 11:32:58 -0700 To: asami@cs.berkeley.edu (Satoshi Asami) cc: wollman@halloran-eldar.lcs.mit.edu, rgrimes@gndrsh.aac.dev.com, current@freebsd.org Subject: Re: Knobs in /etc/sysconfig In-reply-to: Your message of "Wed, 26 Jul 1995 04:57:37 PDT." <199507261157.EAA10190@silvia.HIP.Berkeley.EDU> Date: Wed, 26 Jul 1995 11:32:58 -0700 Message-ID: <20172.806783578@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > This isn't any different from my proposal as far as I can tell, except > that everything gets started in one chunk. If there is one place in > the bootup sequence that we can reliably start all the ports stuff, > that's all fine for me. Well, it's also different in that a port will be required to add itself to the appropriate category startup rather than creating its own file. I'm not sure what happens if the startup file isn't there yet - maybe it gets created and added to the list in sysconfig? Hmmmm. Bleah.. I think I would prefer a fixed number of categories and some prototype files that essentially do nothing out of the box. That would at least narrow the number of things needing to be changed to one file. Jordan