Kernel Security update

[Brian Densmore]

This is true only if you are really using a new level of the kernel.
make modules_install install the modules into the proper directories. If
for instance a module has been unloaded by the system, you recompile
your kernel, then the existing kernel loads the module, then ...

Ok, so it doesn't matter which order you do it in. Unless make install
is looking for installed modules to do linkages on, or build
dependencies on, or create module tables, or ...

Maybe either order is fine, but I'm too paranoid to risk it, because I
haven't analyzed the entire build process to determine if there are or
are not dependencies. I have had too many applications blow up because
of some interdependency that didn't get met. Like I said before, if it
works for you, go for it. It's just not the recommended path.

> -----Original Message-----
> From: Duston, Hal [mailto:hdusto01 at sprintspectrum.com]
> Sent: Wednesday, November 14, 2001 3:02 PM
> To: kclug at kclug.org
> Subject: RE: Kernel Security update
> 
> 
> You don't need the new modules until you actually begin 
> _using_ the new kernel.  Which doesn't happen until you 
> reboot.  So either order is fine.
> 
> Hal Duston
>