Kernel Security update

[Duston, Hal]

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

Brian Densmore [mailto:DensmoreB at ctbsonline.com] wrote:
> 
> I'm sorry you lost me here.
> 
>  You need to do make modules (if you use modules)
>  then  make modules_install (see above)
>  then make install.
> 
> If you don't do these things, in this order, the new 
> kernel won't work right. Unless of course all the 
> modules are already installed, in which case make 
> install is all you need. I personally wouldn't risk 
> it, but hey whatever floats your boat.
> 
> Brian
> 
> Jeremy Fowler [mailto:jfowler at westrope.com] wrote:
> > 
> > Well it appears "make install" does everything "make" 
> > does and then runs /sbin/installkernel afterwards. So 
> > I guess doing a "make" and a "make install" are 
> > somewhat redundant.
> > 
> > make modules_install copies the modules to 
> > /lib/modules/<kernel-version>/
> > 
> > Standard practice is to copy the new kernel image over 
> > to the /boot partition  and then  build the kernel 
> > modules and install them. However, I'm sure you could 
> > do it however you like, I doubt it makes any difference.
> > 
> > -Jeremy