On Wed, Aug 16, 2006 at 08:38:49PM -0400, Robert La Ferla wrote:
I found an init.d script for asterisk BUT not for asterisk/zaptel
modules. I'm still looking for a good solution. It seems to me that
the correct solution would involve /etc/modprobe.d/modpobe.conf.
Have you noticed the
Below is a good example of misusing init.d scripts with the obvious
results of the need for ugly workarounds. Why do you fight against the
design of your system?
See specific comments below,
On Wed, Aug 16, 2006 at 08:20:55AM -0400, Steven wrote:
rc.local:
touch /var/lock/subsys/local
I just reread the post I replied to.
I thought that they were asking for a ref. rc.local.
I didn't notice that it said modprobe.conf.
alias eth0 e1000
alias eth1 e1000
alias scsi_hostadapter megaraid_mbox
alias usb-controller ehci-hcd
alias usb-controller1 uhci-hcd
options torisa base=0xd
rc.local:
touch /var/lock/subsys/local
setpci -v -s 00:1f.1 LATENCY_TIMER=4
setpci -v -s 02:0e.0 LATENCY_TIMER=4
setpci -v -s 0b:07.0 LATENCY_TIMER=4
setpci -v -s 0c:08.0 LATENCY_TIMER=4
setpci -v -s 10:0d.0 LATENCY_TIMER=0
setpci -v -s 06:02.0 LATENCY_TIMER=ff
sleep 5
echo UnLoading wct4xxp
I found an init.d script for asterisk BUT not for asterisk/zaptel
modules. I'm still looking for a good solution. It seems to me that
the correct solution would involve /etc/modprobe.d/modpobe.conf.
___
--Bandwidth and Colocation provided by
Can someone send me their modprobe.conf file? I think that may be
the problem. A zaptel file is created during install in /etc/
modprobe.d but modprobe.conf must need to reference it...
___
--Bandwidth and Colocation provided by Easynews.com --
