From owner-freebsd-hackers  Sun Apr  2 19:57:19 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA19969 for hackers-outgoing; Sun, 2 Apr 1995 19:57:19 -0700
Received: from ix4.ix.netcom.com (ix4.ix.netcom.com [199.182.120.7]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA19963 for <hackers@freebsd.org>; Sun, 2 Apr 1995 19:57:14 -0700
Received: from  by ix4.ix.netcom.com (8.6.12/SMI-4.1/Netcom)
	id TAA03079; Sun, 2 Apr 1995 19:53:49 -0700
Date: Sun, 2 Apr 1995 19:53:49 -0700
Message-Id: <199504030253.TAA03079@ix4.ix.netcom.com>
From: PVinci@ix.netcom.com (Paul Vinciguerra)
Subject: Config wishlist.
To: hackers@FreeBSD.org
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

How difficult would it be to change the system, so that the whole kermel 
doesn't need to be rebuilt whenever you change a jumper setting?

Can't we get the kernel to scan the GENERIC (or whatever) file at boot 
time to resolve the addresses, etc.  ??

Don't we only need to know which devices are going to be present to 
build the kernel?  If we don't tell the system until boot time where the 
devices are, won't we move millenia ahead toward achieving plug-n-play? 

I know that -c will let me do it by hand, but then I have to recompile 
to make the changes permanent, or have I missed something?

Paul