[asterisk-dev] A plea for Zap Sanity

Tzafrir Cohen tzafrir.cohen at xorcom.com
Sat Mar 3 03:01:38 MST 2007

On Sat, Mar 03, 2007 at 12:12:17AM +0100, Christian wrote:
> >Of course, this is silly, and not possible. But I had to ask!
> >
> >  
> This is certainly not silly, i bet most asterisk developers fixing bugs 
> in 1.2 / 1.4 / trunk would like to make this process of down/upgrading 
> easier.
> What about having multiple /lib/modules/$(uname -r) directories? like 
> let's say you have kernel 2.6.20 your /lib/modules/ - dir would look like:
> /lib/modules/2.6.20-zaptel-1.2
> /lib/modules/2.6.20-zaptel-1.4
> /lib/modules/2.6.20-zaptel-trunk
> /lib/modules/2.6.20 -> 2.6.20-zaptel-1.2

The zaptel modules are not needed to build Asterisk.

> so your kernel module directory is only a link to the real modules dir. 
> you could do the same for the /usr/include directory. Then you could 
> write a small script that changes your environment from 1.2 to 1.4  to 
> trunk.  This script would simply remove the symlinks and create new ones 
> regarding the corresponding versions.
> That would be pretty easy to do i think.

But then again, someone might be doing a couple of other things on the
system, such as installing nvidia modules. This generally breaks the
standard kernel installation mechanism.

               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir

More information about the asterisk-dev mailing list