From owner-freebsd-hackers Thu Jul 11 15:12:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA09860 for hackers-outgoing; Thu, 11 Jul 1996 15:12:38 -0700 (PDT) Received: from dorsai.dorsai.org (infi@amanda.dorsai.org [206.127.32.130]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA09849 for ; Thu, 11 Jul 1996 15:12:33 -0700 (PDT) Received: by dorsai.dorsai.org (5.67b/23Dec93-Dorsai Embassy) id AA16930; Thu, 11 Jul 1996 18:11:09 -0400 Date: Thu, 11 Jul 1996 18:11:09 -0400 (edt) From: Igigi International To: freebsd-hackers@freefall.freebsd.org Subject: Re: Kernel Config (Was: GENERIC Kernel Debate) In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 11 Jul 1996, Narvi wrote: > > PS. I do understand having precompiled modules for the kernel would not > be to everyones taste - but remeber we are not discussing removing the > source distribution... > For those of us with slower computers making kernel binaries reusable would be a GREAT thing. Certian parts of the kernel are rarely reconfigured by most people and can just be relinked in rather than compiled wholesale for each kernel config. This feature is in config -n although it sometimes doesn't do the job right, it doesn't seem to know how to deal with every change. As a practical example of what people have been saying about device tables I've been changing sio and ethernet settings and using config -n, only 5 or so files need to be recompiled that way, most notably ioconf.c. If doing this was made into a stable policy we'd be halfway to linking in various driver modules, no?