From owner-freebsd-hackers  Fri Sep 19 13:06:19 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id NAA04619
          for hackers-outgoing; Fri, 19 Sep 1997 13:06:19 -0700 (PDT)
Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA04612
          for <hackers@FreeBSD.ORG>; Fri, 19 Sep 1997 13:06:17 -0700 (PDT)
Received: (from tlambert@localhost)
	by usr03.primenet.com (8.8.5/8.8.5) id NAA29936;
	Fri, 19 Sep 1997 13:06:08 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199709192006.NAA29936@usr03.primenet.com>
Subject: Re: Higher-level kernel config?
To: Harlan.Stenn@pfcs.com (Harlan Stenn)
Date: Fri, 19 Sep 1997 20:06:07 +0000 (GMT)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <18987.874643267@mumps.pfcs.com> from "Harlan Stenn" at Sep 19, 97 00:27:47 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 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.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.