loading zaptel modules on startup

[Tzafrir Cohen]

Hi

One place where the zaptel package currently deviates from upstream is
that upstream's init.d script loads modules in the "start" target.

The reason the Debian script doesn't do that is that in a case of a
system with multiple devices handled by multiple module, the order
listed in MODULES in /etc/default/zaptel is not guaranteed to be the
real order in which modules will load, as modules may load in advance
through hotplug/udev/whatever.

The order of modules loading is significant because most Zaptel modules
register their spans when they load and thus the order of modules
loading sets the order of channel numbers.

A way to override the hotplugged order is in /etc/modules .

But then, what do you do if you need to unload and load the zaptel
modules? The asterisk init.d script has a target called "zaptel-fix":

        echo "Unloading and reloading loading Asterisk and Zaptel:"
        $0 stop
        /etc/init.d/zaptel unload
        # load modules from /etc/modules. This will break if you count on       
        # discover/hotplug
        /etc/init.d/module-init-tools
        /etc/init.d/zaptel start
        $0 start 

At least one module (qozap) will not load through the standard 
hotplugging  mechanisms: it does not declare PCI device IDs it support, 
and implements its own bus scanning :-(

Should we keep this change?

-- 
               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