<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18783">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>After a kernel update (but before rebooting)
</FONT><FONT size=2 face=Arial>Is there a way to recompile Zap/Dahdi against the
new kernel?</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>
<DIV><FONT size=2 face=Arial>My objective is to eliminate the additional
downtime that occurs while recompiling/installing zap/dahdi after booting
into the new kernel.</FONT></DIV></FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Please correct me if I'm wrong: </FONT></DIV>
<DIV><FONT size=2 face=Arial>My understanding is that until you reboot (after a
kernel update), recompiling zap/dahdi still compiles against the OLD kernel, and
that's why zap/dahdi doesn't start after rebooting into the new kernel
(even if you recompiled it just before rebooting). </FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>So my question is: </FONT></DIV>
<DIV><FONT size=2 face=Arial>Is there a method to recompile dahdi/zap against
the new kernel such that the only downtime is the actual server bounce
itself? OR is the current best practice just to simply to reboot,
recompile, restart? </FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Thanks in advance.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>-Karl </FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV></BODY></HTML>