From owner-freebsd-hackers Fri Sep 19 22:39:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA07944 for hackers-outgoing; Fri, 19 Sep 1997 22:39:21 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA07910 for ; Fri, 19 Sep 1997 22:39:13 -0700 (PDT) Received: (qmail 23820 invoked by uid 1000); 20 Sep 1997 05:39:27 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha-091897 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199709192006.NAA29936@usr03.primenet.com> Date: Fri, 19 Sep 1997 22:39:27 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Terry Lambert Subject: Re: Higher-level kernel config? Cc: hackers@FreeBSD.ORG, (Harlan Stenn) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Terry Lambert; On 19-Sep-97 you wrote: > > I was just noticing that I have 3 or 4 customized config files here for > > various FreeBSD machines, and that stuff changes in the GENERIC and > > LINT > > files *much* more often than I change hardware in my machines. > > > I'm curious: could there ever be a case where you would not want to > include a driver for hardware that was actually in your machine? If > not, then I think dynamic autoconfiguration is the way to go. Absolutely yes. Consider a test bench machine where there is some known to be bad hardware you may want activated only if you choose to. Auto config is still excellent there. I put an entry in /boot.conf that specifies a deny list, as well as an allow list. Then I allow the boot prompt to specify the file name of the ``boot.conf'' I want related to and presto! A truely managable system. Oh, somewhere along the line, we will make a /boot and throw all these kernels, config files, etc. into that directory, so / looks readable again. --- Sincerely Yours, (Sent on 19-Sep-97, 22:30:39 by XF-Mail) Simon Shapiro Atlas Telecom Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005 Shimon@i-Connect.Net Voice: 503.643.5559, Emergency: 503.799.2313