From owner-freebsd-current Sun Aug 3 14:31:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA19051 for current-outgoing; Sun, 3 Aug 1997 14:31:36 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA19044 for ; Sun, 3 Aug 1997 14:31:34 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA02371; Sun, 3 Aug 1997 14:30:23 -0700 From: Terry Lambert Message-Id: <199708032130.OAA02371@phaeton.artisoft.com> Subject: Re: Some thoughts and ideas, and quirks To: garbanzo@hooked.net (Alex) Date: Sun, 3 Aug 1997 14:30:23 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: from "Alex" at Aug 3, 97 00:30:42 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 6.) Also, while tinkering with Debian, I really liked the menu config for > the kernel vs the text file that *bsd* uses. IMO this would be great to > integrate into FreeBSD. Also due to the nature of Linux, I really did like > the ability to easily keep multiple kernel source configurations, along > with multiple kernel sources. Perhaps something with libdialog could be > worked out. 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. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.