Date: Sun, 11 Oct 1998 21:36:33 -0700 From: Mike Smith <mike@smith.net.au> To: "Robert V. Baron" <rvb@cs.cmu.edu> Cc: Doug Rabson <dfr@nlsystems.com>, Peter Wemm <peter@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys kernel.h Message-ID: <199810120436.VAA03290@dingo.cdrom.com> In-Reply-To: Your message of "11 Oct 1998 19:54:16 EDT." <yzsbtniy7rr.fsf@sicily.odyssey.cs.cmu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
I actually also preferred this terminology; to me a module is a pluggable unit component, which may serve multiple functions but is effectively the atomic unit when it comes to mobility and connection. This is something that can be argued endlessly; I'm not sure that a debate would help at all. > > I like the model that I lump a bunch of files into a "module" and then > the module initializes a bunch of "services/resources". > > Doug Rabson <dfr@nlsystems.com> writes: > > > This is directly addressed by the KLD system. The terminology is that a > > 'file' (ELF or a.out) is loaded by the kernel linker. The file contains a > > number of 'modules', each of which is initialised and has an event handler > > (similar to lkmdispatch). The kernel in many ways is a file which > > contains all the statically linked modules. > > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com 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?199810120436.VAA03290>