From owner-cvs-all Fri Mar 22 8: 5:56 2002 Delivered-To: cvs-all@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 720E537B419; Fri, 22 Mar 2002 08:05:32 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2MG5Uk43495; Fri, 22 Mar 2002 11:05:30 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 22 Mar 2002 11:05:30 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "David O'Brien" Cc: Garrett Wollman , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_linker.c vfs_syscalls.c In-Reply-To: <20020321233032.A21131@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 21 Mar 2002, David O'Brien wrote: > On Thu, Mar 21, 2002 at 11:38:06PM -0500, Garrett Wollman wrote: > > > I really do not know what "compile modules into your kernel" means. > > > A subsystem is either a module, or it is compiled statically into the > > > kernel. In the 2nd case, I've never heard things called a module. > > > > `kldstat -v' disagrees. > > *sigh* OK, I am speaking of the sysadmin POV -- there is a difference > between the objects that are built from sys/modules and putting "options > foo" in your kernel config. Many developers say "I don't use modules in > -CURRENT". I really doubt they are talking about not using any network > drivers (for instance). Also note that debugging the two are different > -- see the FAQ of how to gdb a module. Personally, I do use modules on -CURRENT frequently, as it permits me to load, test new code, and unload rapidly. Obviously, you can't do this for everything, but if you're not testing your code in the module form as well as the compiled-in form, you are at risk of developing serious bugs :-). I've found that most of my concerns with modules and live development were resolved when we moved to a model that kept modules with their associated kernel. Prior to that, I'd shoot myself in the foot by upgrading/downgrading kernels but not modules in some development scenarios, with much suffering immediately following. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message