Date: Thu, 21 Mar 2002 23:30:32 -0800 From: "David O'Brien" <obrien@FreeBSD.org> To: Garrett Wollman <wollman@lcs.mit.edu> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_linker.c vfs_syscalls.c Message-ID: <20020321233032.A21131@dragon.nuxi.com> In-Reply-To: <200203220438.g2M4c6Y78946@khavrinen.lcs.mit.edu>; from wollman@lcs.mit.edu on Thu, Mar 21, 2002 at 11:38:06PM -0500 References: <200203211527.g2LFRec54938@freefall.freebsd.org> <20020321183815.A890@dragon.nuxi.com> <20020322025759.GA1650@kanpc.gte.com> <20020321202820.A19570@dragon.nuxi.com> <200203220438.g2M4c6Y78946@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020321233032.A21131>