On Tue, Dec 13, 2005 at 05:21:42PM +0000, Karl O. Pinc wrote: > > On 12/13/2005 07:32:10 AM, Kevin P. Fleming wrote: > > > >This script is completely unnecessary on Debian; just add the modules > >you wish to load into /etc/modules and they will be loaded at boot > >time. > > FYI the list. Using debian with linux 2.6 you don't do anything, > the requsite module information is installed in /etc/modprobe.d/zaptel > and it just works.
Allow me to correct this: Here is something frm an Asterisk 1.0 system. It has not radically changedin Asterisk 1.2: # chat that specific file for the format... $ grep e159 /lib/modules/`uname -r`/modules.pcimap wct1xxp 0x0000e159 0x00000001 0x00006159 0xffffffff 0x00000000 0x00000000 0x0 wcfxs 0x0000e159 0x00000001 0x0000a159 0xffffffff 0x00000000 0x00000000 0x0 wcfxs 0x0000e159 0x00000001 0x0000e159 0xffffffff 0x00000000 0x00000000 0x0 wcfxs 0x0000e159 0x00000001 0x0000b100 0xffffffff 0x00000000 0x00000000 0x0 wcfxs 0x0000e159 0x00000001 0x0000b1d9 0xffffffff 0x00000000 0x00000000 0x0 wcfxs 0x0000e159 0x00000001 0x0000b119 0xffffffff 0x00000000 0x00000000 0x0 wcfxs 0x0000e159 0x00000001 0x0000a9fd 0xffffffff 0x00000000 0x00000000 0x0 wcfxs 0x0000e159 0x00000001 0x0000a8fd 0xffffffff 0x00000000 0x00000000 0x0 wcfxs 0x0000e159 0x00000001 0x0000a800 0xffffffff 0x00000000 0x00000000 0x0 wcfxs 0x0000e159 0x00000001 0x0000a801 0xffffffff 0x00000000 0x00000000 0x0 wcfxs 0x0000e159 0x00000001 0x0000a908 0xffffffff 0x00000000 0x00000000 0x0 wcfxs 0x0000e159 0x00000001 0x0000a901 0xffffffff 0x00000000 0x00000000 0x0 wcfxo 0x0000e159 0x00000001 0x00008085 0xffffffff 0x00000000 0x00000000 0x0 wcfxo 0x0000e159 0x00000001 0x00008086 0xffffffff 0x00000000 0x00000000 0x0 wcfxo 0x0000e159 0x00000001 0x00008087 0xffffffff 0x00000000 0x00000000 0x0 wcte11xp 0x0000e159 0x00000001 0x000071fe 0xffffffff 0x00000000 0x00000000 0x0 wcte11xp 0x0000e159 0x00000001 0x000079fe 0xffffffff 0x00000000 0x00000000 0x0 wcte11xp 0x0000e159 0x00000001 0x0000795e 0xffffffff 0x00000000 0x00000000 0x0 wcte11xp 0x0000e159 0x00000001 0x000079de 0xffffffff 0x00000000 0x00000000 0x0 wcte11xp 0x0000e159 0x00000001 0x0000797e 0xffffffff 0x00000000 0x00000000 0x0 hisax 0x0000e159 0x00000002 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 hisax 0x0000e159 0x00000001 0xffffffff 0xffffffff 0x00000000 0x00000000 0x0 This information is generated by depmod even in 2.4 . It is extracted from the declerations inside kernel modules code. discover and kudzu use that information to load the relevant modules when they are run. They scan the bus in a generally predictable order at boot time. They don't require any special 2.6 features. But they don't support hotplugging. hotplug takes this to th next level: the kernel notifies userspace of new events. This allows hotplugging. The default configuration of zaptel from the tarball is to try to run ztcfg (with too many v flags, mind you) after every zaptel module gets loaded (even ztdummy, ztdynamic and zaptel, IIRC). As a result, modprobe will fail many times due to ztcfg being run with an incomplete configuration. The solution to that is to have a simple init.d script that modpobes ztdummy if no other span is discovered and then runs ztcfg. As it has no problems running twice, it needs no lock file. Regarding the stop action: There is no need to rmmod those modules at shutdown time, IMHO. Hence removing them should not be the default stop action, should this be an init.d script. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il | | a Mutt's [EMAIL PROTECTED] | | best ICQ# 16849755 | | friend _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
