[GRLUG] Meeting agenda?

[Michael Mol]

On 10/11/06, Roberto Villarreal <rvillarreal at mktec.com> wrote:
> > 1) The only reason I can think of to be weary of modules is a
> > bordering-on-paranoia fear of rootkits...  quite a few load as
> > modules.  However, a few that I know of use only /dev/kmem or similar
> > to bootstrap themselves into kernel-space - no module support needed.
> > Otherwise, modules are functionally identical to compiled-in drivers.
>
> Another reason is because, like in my above scenario, if you *do* have to
> compile your kernel, it will save you a whole lot of compile time!!!

Not really.  The kernel build system does a decent job in keeping
compile times light.  If you've compiled the kernel before, and you
change a couple of options, the build system will compile only the
parts that have changed.

>
> > 2) Unless you, for some crazy reason :), buy it.  Hard to tell a year
> > or three in advance.
>
> Very valid for desktops, but typically not for a laptop...

An interesting point.  However, if you're using Linux on a laptop,
there's a good chance you might need to install ATI's or NVidia's
drivers, which are separate modules.  They won't work in a
non-modular. kernels.

-- 
:wq