[asterisk-dev] useless modprobe.conf entries

[Tzafrir Cohen]

Hi

Many of the setup bugs I see related to Zaptel seems to be cause by the
attempt to run ztcfg at module load time automatically.

Here is where it fails:

1. 
You need to modprobe zaptel manually. This is because on some systems
(RHEL4?) it takes time for the udev nodes to be generated. And thus 
the modprobe of of any module the ztcfg will fail because /dev/zap/ctl
is not there yet.

2. 
On a setup with more than one hardware type, a modprobe of the 
first card will always fail (because /etc/zaptel.conf cannot yet be
fully applied).

3.
If zaptel.conf has some errors in it, they appear to be module loading
errors. 

(genzaptelconf moves aside the current zaptel.conf for the time of
hardware probing and replaces it with an empty one. Otherwise no
automatic module detection would be possible)

4. 
The Astribank drivers are not ready immediely after modprobe time. They
not only take a small while to initialize, but also optionally will only
register by a specific instruction from userspace. This allows
preserving the order of diveces regardless of the arbitrary load order.


Suggestion: 

A. Don't install anything to the modprobe configu file.
Recommend to existing users to remove that file.

B. Provide a simple and working zaptel init.d script (for examples, look
at xpp/utils/zaptel-helper ).

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