From owner-cvs-all Thu Sep 23 7:29:33 1999 Delivered-To: cvs-all@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 348B615E65; Thu, 23 Sep 1999 07:29:29 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA88988; Thu, 23 Sep 1999 10:29:04 -0400 (EDT) (envelope-from wollman) Date: Thu, 23 Sep 1999 10:29:04 -0400 (EDT) From: Garrett Wollman Message-Id: <199909231429.KAA88988@khavrinen.lcs.mit.edu> To: Greg Lehey Cc: Warner Losh , Matt Dillon , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: Building klds (was: cvs commit: src/sys/i386/include param.h src/sys/alpha/include param.h src/sys/conf options src/sys/i386/conf LINT) In-Reply-To: <19990923141749.U42271@freebie.lemis.com> References: <19990923093300.W7337@freebie.lemis.com> <199909220548.WAA71309@freefall.freebsd.org> <199909230446.WAA38327@harmony.village.org> <19990923141749.U42271@freebie.lemis.com> Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk < said: > The one with which they're associated. The way I see it, they should > get built along with the kernel. The way I see it, if you're frobbing something central enough to matter, then you should statically compile all modules into your kernel. Once people are actually using custom kernels, there's little point in having mandatory (for that configuration) functionality not be compiled in. We went around this back in '93-'94 with the first loadable module implementation. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message