I figured so, but searching for "upgrade" and "kernel" returned so many irrelevant hits I threw in the towel. ;P
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > brian k. west > Sent: Friday, May 21, 2004 7:23 PM > To: [EMAIL PROTECTED] > Subject: Re: [Asterisk-Users] Asterisk upgrade on production box > > > Yes you will need to recompile zaptel also. This is comonly > talked about on the mailing list. > > bkw > > ----- Original Message ----- > From: "Nik Martin" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, May 21, 2004 5:17 PM > Subject: RE: [Asterisk-Users] Asterisk upgrade on production box > > > > Is it normal for asterisk to have to be recompiled when you upgrade > > your kernel? I fetched a new kernel yesterday, taking me > from 2.4.25 > > to 2.4.26 I built yesterday, and rebooted this afternoon. After > > upgrading, none of > the > > asterisk modules would load. I assume they are dependent on the > > kernel > they > > were compiled against? > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf Of Brian > > > Cuthie > > > Sent: Friday, May 21, 2004 3:52 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: [Asterisk-Users] Asterisk upgrade on production box > > > > > > > > > > > > I'm sure there are better ways, but I usually do the following: > > > > > > 1) make sure my current source directory is named something else > > > (see step 3) > > > > > > 2) fetch cvs head > > > > > > 3) mv asterisk to something like asterisk_cvs_head_5_21. > This keeps > > > all the old source trees around so that I can easily roll back to > > > any version I've installed previously. > > > > > > 4) cd to the new asterisk directory (whatever you called > it in step > > > 3) > > > > > > 5) make > > > > > > 7) asterisk -r > > > > > > 8) show channels to make sure nobody's using it > > > > > > 9) stop now > > > > > > 10) exit asterisk > > > > > > 11) make install > > > > > > 12) restart asterisk > > > > > > Note that if you don't 'make samples' the stuff in /etc/asterisk > > > won't get torched. This should be fine, assuming that the new > > > version doesn't > > > require any config changes. Naturally, you'll want to > poke around in > > > asterisk/configs to see what kind of new options are available. > > > > > > -brian > > > > > > > > > > _______________________________________________ > > Asterisk-Users mailing list > > [EMAIL PROTECTED] > > http://lists.digium.com/mailman/listinfo/asterisk-users > > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-users > > > > > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
