From owner-freebsd-current Sun Aug 3 17:04:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA28043 for current-outgoing; Sun, 3 Aug 1997 17:04:01 -0700 (PDT) Received: from zippy.dyn.ml.org (root@nepal-16.ppp.hooked.net [206.80.8.208]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA28013 for ; Sun, 3 Aug 1997 17:03:53 -0700 (PDT) Received: from zippy.dyn.ml.org (zippy.dyn.ml.org [127.0.0.1]) by zippy.dyn.ml.org (8.8.5/8.8.5) with SMTP id RAA01379; Sun, 3 Aug 1997 17:03:48 -0700 Date: Sun, 3 Aug 1997 17:03:47 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Some thoughts and ideas, and quirks In-Reply-To: <199708032130.OAA02371@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 3 Aug 1997, Terry Lambert wrote: > Personally, I would prefer to make all configuration runtime with > demand-loaded kernel modules. > > It is my considered opinion that *any* user driven kernel > configuration (text file *or* menu based) is antiquated > baloney. > > So you can guess that I'm not really a fan of replacing one type > of baloney with another type of baloney, regardless of it's > pedigree. > That brings me to another thought or 5 ;) . What about an rc.modules? Also, some things are lacking, like for instance it appears to me that you don't need to statically compile ccd or ppp devices. However the uid filesystem thing does need to be statically compiled as does ext2, both typos in the lint, and man pages, etc. - alex