Karl Fife
2009-Jun-19 04:24 UTC
[asterisk-users] Recompiling dahdi-linux after kernel update - To minimize downtime
After a kernel update (but before rebooting) Is there a way to recompile Zap/Dahdi against the new kernel? My objective is to eliminate the additional downtime that occurs while recompiling/installing zap/dahdi after booting into the new kernel. Please correct me if I'm wrong: 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). So my question is: 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? Thanks in advance. -Karl -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090618/642a7b59/attachment.htm
Alex Samad
2009-Jun-19 05:50 UTC
[asterisk-users] Recompiling dahdi-linux after kernel update - To minimize downtime
On Thu, Jun 18, 2009 at 11:24:40PM -0500, Karl Fife wrote:> After a kernel update (but before rebooting) Is there a way to recompile Zap/Dahdi against the new kernel? > > My objective is to eliminate the additional downtime that occurs while recompiling/installing zap/dahdi after booting into the new kernel. > > Please correct me if I'm wrong: > 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). > > So my question is: > 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?without trying to start a distro war under debian you can do m-a -t build -l <kernel version> dahdi aslong as you have the headers installed it will build a module against it. I think if you use the tgz tar ball you can actually specify KDIR to point to the directory with the headers in it.> > Thanks in advance. > > -Karl> _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users-- "I also understand how tender the free enterprise system can be." - George W. Bush 07/08/2002 White House press conference, Washington, D.C. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20090619/d72b10ef/attachment.pgp
Tzafrir Cohen
2009-Jun-19 08:03 UTC
[asterisk-users] Recompiling dahdi-linux after kernel update - To minimize downtime
On Thu, Jun 18, 2009 at 11:24:40PM -0500, Karl Fife wrote:> After a kernel update (but before rebooting) Is there a way to recompile Zap/Dahdi against the new kernel? > > My objective is to eliminate the additional downtime that occurs while recompiling/installing zap/dahdi after booting into the new kernel. > > Please correct me if I'm wrong: > 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). > > So my question is: > 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? > > Thanks in advance.1. install new kernel (but don't reboot yet) 2. in the dahdi-linux source directory: make KVERS=<new version> make KVERS=<new version> install or: make KSRC=/path/to/kernel/source/tree make KSRC=/path/to/kernel/source/tree install 3. reboot -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
Seemingly Similar Threads
- Cross compiling Asterisk, Dahdi..
- fc3 build after kernel update?
- error during dahdi installation on centos
- DISA() fails to recognize dtmf where WaitExten() succeeds (DAHDI-PRI)
- DAHDI FXO calls and the 's' extension. No, Jackie-O doesn't work here--it's just an example. Sheesh!