[asterisk-users] Modprobe Zaptel

[Eric "ManxPower" Wieling]

Then the "make install" in the Zaptel directory didn't work or installed 
it in the wrong location.

Julian Varanini wrote:
> Hi Eric,
>  
> Tried that but I am still getting the same error.
>  
> Thanks
>  
> Julian
> 
> 
> 
>> Date: Thu, 9 Nov 2006 17:25:02 -0600> From: eric at fnords.org> To: asterisk-users at lists.digium.com> Subject: Re: [asterisk-users] Modprobe Zaptel> > Julian Varanini wrote:> > Hi,> > > > Can someone walk me through compiling and loading the Zaptel 1.2.10 driver for Mandriva 2006 kernel 2.6.12-12? When I compile and attempt a modprobe I get "module zaptel not found"> > You need to edit /usr/src/linux/Makefile to remove make the EXTRAVERSION > variable equal to "-12" rather than the "-12somethingsomethingsomething" > it is now. No need to recompile the kernel, just change the make file > and recompile and reinstall zaptel.> _______________________________________________> --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
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> --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
>>
>> ------------------------------------------------------------------------
>>
>> This message has been 'sanitized'.  This means that potentially
>> dangerous content has been rewritten or removed.  The following
>> log describes which actions were taken.
>>
>> Sanitizer (start="1163120369"):
>>   Part (pos="2680"):
>>     Part (pos="130"):
>>       SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
>>         Match (names="unnamed.txt", rule="1"):
>>           Enforced policy: accept
>>
>>     Part (pos="1237"):
>>       SanitizeFile (filename="unnamed.html, filetype.html", mimetype="text/html"):
>>         Match (names="unnamed.html, filetype.html", rule="3"):
>>           ScanFile (file="/tmp/att-4553cef1-BWK-unnamed.html"):
>>             Scan succeeded, file is clean.
>>
>>           Enforced policy: unknown
>>
>>         Match (names="unnamed.html, filetype.html", rule="4"):
>>           Enforced policy: accept
>>
>>       Note: Styles and layers give attackers many tools to fool the
>>       user and common browsers interpret Javascript code found
>>       within style definitions.
>>       
>>       Rewrote HTML tag: >>_style P { margin:0px; padding:0px } body { FONT-SIZE: 10pt; FONT-FAMILY:Tahoma } _<<
>>                     as: >>_DEFANGED_style P { margin:0px; padding:0px } body { FONT-SIZE: 10pt; FONT-FAMILY:Tahoma } _<<
>>       Rewrote HTML tag: >>_/style_<<
>>                     as: >>_/DEFANGED_style_<<
>>
>>   Part (pos="5440"):
>>     SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
>>       Match (names="unnamed.txt", rule="1"):
>>         Enforced policy: accept
>>
>>   Total modifications so far: 2
>>
>>
>> Anomy 0.0.0 : Sanitizer.pm
>> $Id: Sanitizer.pm,v 1.94 2006/01/02 16:43:10 bre Exp $