astlinux-users — AstLinux Users Mailing List

[Astlinux-users] channel mISDN issues??

[Peter R. <pe...@ne...>]

Hello all

Yesterday I was at a customer try to install a soekris with an hfc-pci =
card installed
always connect BRI pmp but there it was BRI ptp so a change in rc.conf

ISDN_MODPROBE=3D"hfcpci protocol=3D0x2 layermask=3D0xf"


TO

ISDN_MODPROBE=3D"hfcpci protocol=3D0x22 layermask=3D0xf"

Then a reboot, and I look in misdn-init.conf unfortunately there is =
still the value te_ptmp=3D1 instead of te_ptp=3D1

Edit the misdn-init.conf to change it manually is out of the question =
because it is writing during the boot process

any suggestions hints?

Kind Regards,

Peter Roelandts

Re: [Astlinux-users] Question about fxo and fxs with astlinux

[Bryce C. <br...@rh...>]

The company I work for used to make a product called the Brickmail which 
did exactly this. The Panasonic's interface is FXS ports, so the 
Astlinux box will need FXO interfaces. When a call comes into the 
Panasonic, it will ring it directly through to the box, which will do 
the IVR etc; when a user presses an extension, Astlinux will then to a 
blind flash transfer back on its FXO port by doing a hook-flash, dialing 
the panasonic extension number (likely the same number), and then 
hanging up once the Panasonic has hung up on Astlinux. The Panasonic 
rings the phone according to its programming, then if there's no answer, 
it will send it back to the Astlinux box (again, according to 
programming) prefixing the extension it dials with something like a * to 
signify that the call should route directly to the voicemail for that 
extension.
Remember, the Astlinux box is acting just like an operator console, i.e. 
a telephone which is an FXO interface to the PSTN FXS, or in this case 
Panasonic PBX.

Just a reminder, please use the lists on SourceForge.

Regards,
Bryce Chidester
Rhino Equipment Corp.
br...@rh...
Tel: +1 (480) 940-1826 x6351
Fax: +1 (480) 961-1826
FWD: 633686 x6351
IP: asterisk.rhinoequipment.com x6351

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE  PROPRIETARY MATERIAL and is thus for use only by the intended  recipient. If you received this in error, please contact the sender  and delete the email and its attachments from all computers.



Erick Perez wrote:
> Hi, usually when I install an asterisk machine, the machine is alone,
> meaning no other pbx around.
>
> This new customer is asking  me to provide voicemail services and
> autoattendant to his old panasonic PBX.
>
> However im unfamiliar with the setup.
>
> The setup is like this:
> the panasonic gets the calls and it should transfer them to the
> asterisk box. I guess this means that on the asterisk side it should
> be FXS ports right?
>
> then, when the asterisk do the auto attendant stuff and transfers the
> calls to an extension in the panasonic, it will do ablind transfer
> right? freeing the channel.
>
> Now, when a user call the voicemail extension, this means that the
> asterisk should have another set of FXS ports for the users right?
>
> So at the end: 3fxs ports for autoattendant and let's say another 3fxs
> for voicemail right?
>
> the asterisk is not supposed to call anyone, so im not supposed to use
> fxo, right?
>
> thanks in advance for your guidance.
>
>
>
>   

Re: [Astlinux-users] (no subject)

[Lonnie A. <li...@lo...>]

'wget' is available on AstLinux

# wget
BusyBox v1.1.3 (2006.08.22-18:48+0000) multi-call binary

Usage: wget [-c|--continue] [-q|--quiet] [-O|--output-document file]
                 [--header 'header: value'] [-Y|--proxy on/off] [-P  
DIR] url

wget retrieves files via HTTP or FTP

Options:
         -c      continue retrieval of aborted transfers
         -q      quiet mode - do not print
         -P      Set directory prefix to DIR
         -O      save to filename ('-' for stdout)
         -Y      use proxy ('on' or 'off')

Lonnie

On Jan 27, 2007, at 4:51 PM, Thomas Thomsen wrote:

> Hi
>
> Does anyone have a compiled version of Curl ?? (http://curl.haxx.se )
>
> I will use it for a callerid lookup
>
> //Thomas
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV________________________________ 
> _______________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to  
> pa...@kr....

[Astlinux-users] (no subject)

[Thomas T. <tb...@nt...>]

Hi=20
=20
Does anyone have a compiled version of Curl ?? (http://curl.haxx.se )
=20
I will use it for a callerid lookup
=20
//Thomas

[Astlinux-users] Jitter Buffer

[Michael K. <mic...@ip...>]

I have an ASTLinux (development) system running at home of which I am quite
happy with, however even the slightest download from one of the devices on
the network causes voice degredation during a call due to packet loss.

Frustrated with this, I set a phone directly to the ITSP and was unable to
cause this packet loss issue, even with quite substantial downloads.

I suspected that this was a jitter buffer issue in Asterisk but when I began
looking at how to tune this, I was surprised to find that a dynamic jitter
buffer was not actually available in SIP until 1.4. I understand that a
dynamic jitter buffer has been available for IAX for a while.

Is there any way I can solve this problem (install patch etc) or do I need
to use 1.4. PS I would probably wait until it is included in ASTLinux, the
best Asterisk distribution.

Regards
Michael Knill


--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.8/649 - Release Date: 23/01/2007
8:40 PM

[Astlinux-users] OT: Where to learn

[Erick P. <eap...@gm...>]

Hi, I would like to learn how to transform a linux installation into
something that boots from a CF card and uses RAM to work (no hard
disk, no moving parts). Just like astlinux does, but I want to learn
how is being done, what do I need to transform my build into something
like that.

I already have astlinux 0.4.4 running in my mini-itx, but my next project
It's for an antispam antivirus appliance, thats why i marked this post OT.

I'm planning to use 1gb of ram in a mini-itx, 512 for the OS (or less)
and 512 for "ram"

Thanks and I apologize in advance for posting things unrelated to astlinux.

-- 
------------------------------------------------------------
Erick Perez
Panama Sistemas
Integradores de Telefonia IP y Soluciones Para Centros de Datos
Panama, Republica de Panama
Cel Panama. +(507) 6694-4780
------------------------------------------------------------

[Astlinux-users] FW: Ztdummy Instead of ZapRTC

[Kevin K. <Ast...@gt...>]

-----Original Message-----
From: Kristian Kielhofner [mailto:kri...@gm...] 
Sent: Sunday, January 21, 2007 10:37 PM
To: Discussion of AstLinux - Asterisk on Compact Flash
Subject: Re: [Astlinux-users] Ztdummy Instead of ZapRTC

On 1/21/07, ven...@sa... <ven...@sa...>
wrote:
>
> Sorry, mine was OHCI and not UHCI.  Is it still possible to use ztdummy?
> host/usb-ohci.c: USB OHCI at membase 0xc6a68000, IRQ 11
> host/usb-ohci.c: usb-00:13.0, Compaq Computer Corporation ZFMicro Chipset
USB
>
>

Veneraldo,

  Can you please ask on the new mailing list:

http://sourceforge.net/mail/?group_id=170462

Thanks!

-- 
Kristian Kielhofner
_______________________________________________
Astlinux-users mailing list
Ast...@li...
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....

REMEMBER: AstLinux mailing lists are moving soon:

http://sourceforge.net/mail/?group_id=170462

Please move any discussions ASAP!


-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.17.3/642 - Release Date: 1/20/2007
10:31 PM
 

[Astlinux-users] Astlinux Gumstix CF problems

[Daniel B. <dan...@ma...>]

All,

I've been running astlinux on a gumstix netstix 400 for over a month,  
works like a charm. However:

The build environment is still giving me problems, especially pcmcia-cs.
Build fails when I add the pcmcia-cs package. Need this to allow  
access to the CF slot for keydisk support.
Has anyone else come across this problem and developed a fix?

BTW: Build also always fails at packages iproute, iptables, and  
msmtp. This hasn't been a problem since
I don't need these packages for now. But pcmcia-cs is really needed.

Using revision 503 of the buildroot.

Thanks,

Dan

[Astlinux-users] Compile problems with i686 as theTargetArchitecture Variant

[Gary G. H. <GHe...@co...>]

Most of the ones I am dealing with here are VIA C3 1GHz machines on a
m'boards from LEX ... I use the standard i586 build and it seems to work
fine ... I think the last time the question came up, I was told that there
is no difference between the VIA and standard i586 build ... That was a
while ago so I am not sure if anything has changed since ...

I am not sure that the kernel in Astlinux takes advantage of the fancy
random number generator in the VIA chip ... I understand that this function
might improve performance on VIA machines when doing codec conversion or
when doing encryption as in VPN ... But the machines have performed well
enough for my scenario that I just don't worry about it ...  I would be more
concerned about making modifications to the build that might version updates
difficult ...

There are many on this list who report good results using 233MHz and 266MHz
CPU's ... I would assume that the VIA machines with 800MHz to 1.5GHz CPU's
should be able to handle most anything you might throw at them even without
using any unique VIA features ...

All that said, if you get SAMBA working under Astlinus, please take time to
put together a recipe of how you got it to work ... I would be interested in
playing with that ...  Not sure I would want to expose a SAMBA mahine to the
Internet though ... That scares me a bit ...  Would have to tweak up the
Arno firewall script to compensate for the security issues I suspect ...

G.Hendershot

Re: [Astlinux-users] Compile problems with i686 as the TargetArchitecture Variant

[olivier.taylor <oli...@gm...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
i used the generic i586 from distribution.<br>
<br>
Olivier<br>
<br>
Sebastian Auriol a &eacute;crit&nbsp;:
<blockquote
 cite="mid!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAAC4AAAAAAAAAvrTCuIsz1xGxNWiNbQAAAAEAUR1BVCzq0xGwsQCgzFqsgwAAAAGTZwAAEAAAANqgOy+RNyFOg1pHF56R8r8BAAAAAA==@syntec.co.uk"
 type="cite">
  <pre wrap="">Glad to hear it.  Did you specify a VIA device or a Generic i586 device
though?
 
P. S.  I finally got 0.4 branch and trunk to finish the make process.
*relief* :-)
 
Sebastian


  _____  

From: <a class="moz-txt-link-abbreviated" href="mailto:ast...@li...">ast...@li...</a>
[<a class="moz-txt-link-freetext" href="mailto:ast...@li...">mailto:ast...@li...</a>] On Behalf Of
olivier.taylor
Sent: 18 January 2007 19:22
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] Compile problems with i686 as the
TargetArchitecture Variant


Sebastian,

I have an HP 5500 thin client (Via chip) running perfectly here with the
I586 build, just Fyi.

Olivier

Sebastian Auriol a &eacute;crit : 

Kristian,



Thanks for the feedback and links. I have switched to i586 and Generic i586

device for now and it seems to be going OK, except that I ran out of disk

space at one point and I was missing uudecode. I had to basically start

again after the disk space problem: cp -r dl dl-bak ; make clean ; make

distclean ; rm -f -r toolchain_build_i586 ; svn update ; make

If I didn't delete toolchain_build_i586 it would just immediately bomb

again.



<a class="moz-txt-link-freetext" href="ftp://ftp.samba.org/">ftp://ftp.samba.org/</a> isn't working today but I found the file at

<a class="moz-txt-link-freetext" href="http://samba.org/ftp/ppp/ppp-2.4.3.tar.gz">http://samba.org/ftp/ppp/ppp-2.4.3.tar.gz</a> (btw, there is a newer version

available too). I copied the file into the dl directory manually, but it is

still retrying via FTP (try: 4) and the timeouts are extremely long. Is

there anyway to cancel the getter_script.sh without cancelling the make? The

server has spent so long getting to this point I don't want to have to start

it again.



Having said that, I would be willing to try VIA with i586. Is this likely to

work then? What are the differences between Generic i586 and VIA builds?

Presumably it will overwrite build_i586/root so I'd want to back that up...



I saw your svn changes. :)



Is trunk nearly ready for a release? Or more importantly for me right now,

should it be stable?



Thanks for your help. This is my first time trying to compile AstLinux. I

need to add support, i.e. drivers, for a device that is not supported in the

standard build. How do I go about doing this? Presumably I can do it after

the main make has finished...



Sebastian





-----Original Message-----

From: <a class="moz-txt-link-abbreviated" href="mailto:ast...@li...">ast...@li...</a>

[<a class="moz-txt-link-freetext" href="mailto:ast...@li...">mailto:ast...@li...</a>] On Behalf Of Kristian

Kielhofner

Sent: 18 January 2007 15:52

To: AstLinux Users Mailing List

Subject: Re: [Astlinux-users] Compile problems with i686 as the

TargetArchitecture Variant



On 1/18/07, Sebastian Auriol  <a class="moz-txt-link-rfc2396E" href="mailto:sp...@sy...">&lt;mailto:sp...@sy...&gt;</a>
<a class="moz-txt-link-rfc2396E" href="mailto:sp...@sy...">&lt;sp...@sy...&gt;</a> wrote:

  

Well trying to compile with i386/i686/Generic i586 doesn't work either (on

0.4 and trunk), with the same problems, so it looks like the i686 variant

may be the problem.  I'm going to try again now using i586 as the variant

for 0.4 branch and trunk...



Sebastian





    



Sebastian,



  Thank you for your comments.  A couple of things:



1) Almost all VIA processors have known problems when running with

"i686" compiled code:



<a class="moz-txt-link-freetext" href="http://lists.digium.com/pipermail/asterisk-dev/2003-July/001194.html">http://lists.digium.com/pipermail/asterisk-dev/2003-July/001194.html</a>

<a class="moz-txt-link-freetext" href="http://www.voip-info.org/wiki/view/Asterisk+hardware+mini-itx">http://www.voip-info.org/wiki/view/Asterisk+hardware+mini-itx</a>



  There are other examples all over the place.  On the VIA, stick with i586.



2) In general, if you select a specific device under AstLinux target

devices, you really shouldn't just change the processor architecture.

If you want to do this, create a new target device that will select

your intended target CPU.  Those devices are there (and work with 586)

because they are a specific piece of hardware with a known

configuration.



3) "make clean" is broken all over the place.  Myself and the other

devs know this.  I have submitted a patch to both 0.4 and trunk to fix

the few problems that you pointed out but there are certainly other

problems with make clean.



4) These days, almost all development is done in trunk.  0.4 isn't

updated and fixed nearly as often (your mISDN CVS problem, etc).



  


  </pre>
  <pre wrap="">
<hr size="4" width="90%">
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT &amp; business topics through brief surveys - and earn cash
<a class="moz-txt-link-freetext" href="http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV">http://www.techsay.com/default.php?page=join.php&amp;p=sourceforge&amp;CID=DEVDEV</a></pre>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Astlinux-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ast...@li...">Ast...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/astlinux-users">https://lists.sourceforge.net/lists/listinfo/astlinux-users</a>

Donations to support AstLinux are graciously accepted via PayPal to <a class="moz-txt-link-abbreviated" href="mailto:pa...@kr...">pa...@kr...</a>.</pre>
</blockquote>
</body>
</html>

Re: [Astlinux-users] Compile problems with i686 as the TargetArchitecture Variant

[Sebastian A. <sp...@sy...>]

Glad to hear it.  Did you specify a VIA device or a Generic i586 device
though?
=20
P. S.  I finally got 0.4 branch and trunk to finish the make process.
*relief* :-)
=20
Sebastian


  _____ =20

From: ast...@li...
[mailto:ast...@li...] On Behalf Of
olivier.taylor
Sent: 18 January 2007 19:22
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] Compile problems with i686 as the
TargetArchitecture Variant


Sebastian,

I have an HP 5500 thin client (Via chip) running perfectly here with the
I586 build, just Fyi.

Olivier

Sebastian Auriol a =E9crit :=20

Kristian,



Thanks for the feedback and links. I have switched to i586 and Generic =
i586

device for now and it seems to be going OK, except that I ran out of =
disk

space at one point and I was missing uudecode. I had to basically start

again after the disk space problem: cp -r dl dl-bak ; make clean ; make

distclean ; rm -f -r toolchain_build_i586 ; svn update ; make

If I didn't delete toolchain_build_i586 it would just immediately bomb

again.



ftp://ftp.samba.org/ isn't working today but I found the file at

http://samba.org/ftp/ppp/ppp-2.4.3.tar.gz (btw, there is a newer version

available too). I copied the file into the dl directory manually, but it =
is

still retrying via FTP (try: 4) and the timeouts are extremely long. Is

there anyway to cancel the getter_script.sh without cancelling the make? =
The

server has spent so long getting to this point I don't want to have to =
start

it again.



Having said that, I would be willing to try VIA with i586. Is this =
likely to

work then? What are the differences between Generic i586 and VIA builds?

Presumably it will overwrite build_i586/root so I'd want to back that =
up...



I saw your svn changes. :)



Is trunk nearly ready for a release? Or more importantly for me right =
now,

should it be stable?



Thanks for your help. This is my first time trying to compile AstLinux. =
I

need to add support, i.e. drivers, for a device that is not supported in =
the

standard build. How do I go about doing this? Presumably I can do it =
after

the main make has finished...



Sebastian





-----Original Message-----

From: ast...@li...

[mailto:ast...@li...] On Behalf Of =
Kristian

Kielhofner

Sent: 18 January 2007 15:52

To: AstLinux Users Mailing List

Subject: Re: [Astlinux-users] Compile problems with i686 as the

TargetArchitecture Variant



On 1/18/07, Sebastian Auriol  <mailto:sp...@sy...>
<sp...@sy...> wrote:

 =20

Well trying to compile with i386/i686/Generic i586 doesn't work either =
(on

0.4 and trunk), with the same problems, so it looks like the i686 =
variant

may be the problem.  I'm going to try again now using i586 as the =
variant

for 0.4 branch and trunk...



Sebastian





   =20



Sebastian,



  Thank you for your comments.  A couple of things:



1) Almost all VIA processors have known problems when running with

"i686" compiled code:



http://lists.digium.com/pipermail/asterisk-dev/2003-July/001194.html

http://www.voip-info.org/wiki/view/Asterisk+hardware+mini-itx



  There are other examples all over the place.  On the VIA, stick with =
i586.



2) In general, if you select a specific device under AstLinux target

devices, you really shouldn't just change the processor architecture.

If you want to do this, create a new target device that will select

your intended target CPU.  Those devices are there (and work with 586)

because they are a specific piece of hardware with a known

configuration.



3) "make clean" is broken all over the place.  Myself and the other

devs know this.  I have submitted a patch to both 0.4 and trunk to fix

the few problems that you pointed out but there are certainly other

problems with make clean.



4) These days, almost all development is done in trunk.  0.4 isn't

updated and fixed nearly as often (your mISDN CVS problem, etc).



 =20

Re: [Astlinux-users] Compile problems with i686 as the TargetArchitecture Variant

[olivier.taylor <oli...@gm...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Sebastian,<br>
<br>
I have an HP 5500 thin client (Via chip) running perfectly here with
the I586 build, just Fyi.<br>
<br>
Olivier<br>
<br>
Sebastian Auriol a &eacute;crit&nbsp;:
<blockquote
 cite="mid!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAAC4AAAAAAAAAvrTCuIsz1xGxNWiNbQAAAAEAUR1BVCzq0xGwsQCgzFqsgwAAAAGTZwAAEAAAADO2lXjA+91IvP7aWfG%2FAnIBAAAAAA==@syntec.co.uk"
 type="cite">
  <pre wrap="">Kristian,

Thanks for the feedback and links. I have switched to i586 and Generic i586
device for now and it seems to be going OK, except that I ran out of disk
space at one point and I was missing uudecode. I had to basically start
again after the disk space problem: cp -r dl dl-bak ; make clean ; make
distclean ; rm -f -r toolchain_build_i586 ; svn update ; make
If I didn't delete toolchain_build_i586 it would just immediately bomb
again.

<a class="moz-txt-link-freetext" href="ftp://ftp.samba.org/">ftp://ftp.samba.org/</a> isn't working today but I found the file at
<a class="moz-txt-link-freetext" href="http://samba.org/ftp/ppp/ppp-2.4.3.tar.gz">http://samba.org/ftp/ppp/ppp-2.4.3.tar.gz</a> (btw, there is a newer version
available too). I copied the file into the dl directory manually, but it is
still retrying via FTP (try: 4) and the timeouts are extremely long. Is
there anyway to cancel the getter_script.sh without cancelling the make? The
server has spent so long getting to this point I don't want to have to start
it again.

Having said that, I would be willing to try VIA with i586. Is this likely to
work then? What are the differences between Generic i586 and VIA builds?
Presumably it will overwrite build_i586/root so I'd want to back that up...

I saw your svn changes. :)

Is trunk nearly ready for a release? Or more importantly for me right now,
should it be stable?

Thanks for your help. This is my first time trying to compile AstLinux. I
need to add support, i.e. drivers, for a device that is not supported in the
standard build. How do I go about doing this? Presumably I can do it after
the main make has finished...

Sebastian


-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:ast...@li...">ast...@li...</a>
[<a class="moz-txt-link-freetext" href="mailto:ast...@li...">mailto:ast...@li...</a>] On Behalf Of Kristian
Kielhofner
Sent: 18 January 2007 15:52
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] Compile problems with i686 as the
TargetArchitecture Variant

On 1/18/07, Sebastian Auriol <a class="moz-txt-link-rfc2396E" href="mailto:sp...@sy...">&lt;sp...@sy...&gt;</a> wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">
Well trying to compile with i386/i686/Generic i586 doesn't work either (on
0.4 and trunk), with the same problems, so it looks like the i686 variant
may be the problem.  I'm going to try again now using i586 as the variant
for 0.4 branch and trunk...

Sebastian


    </pre>
  </blockquote>
  <pre wrap=""><!---->
Sebastian,

  Thank you for your comments.  A couple of things:

1) Almost all VIA processors have known problems when running with
"i686" compiled code:

<a class="moz-txt-link-freetext" href="http://lists.digium.com/pipermail/asterisk-dev/2003-July/001194.html">http://lists.digium.com/pipermail/asterisk-dev/2003-July/001194.html</a>
<a class="moz-txt-link-freetext" href="http://www.voip-info.org/wiki/view/Asterisk+hardware+mini-itx">http://www.voip-info.org/wiki/view/Asterisk+hardware+mini-itx</a>

  There are other examples all over the place.  On the VIA, stick with i586.

2) In general, if you select a specific device under AstLinux target
devices, you really shouldn't just change the processor architecture.
If you want to do this, create a new target device that will select
your intended target CPU.  Those devices are there (and work with 586)
because they are a specific piece of hardware with a known
configuration.

3) "make clean" is broken all over the place.  Myself and the other
devs know this.  I have submitted a patch to both 0.4 and trunk to fix
the few problems that you pointed out but there are certainly other
problems with make clean.

4) These days, almost all development is done in trunk.  0.4 isn't
updated and fixed nearly as often (your mISDN CVS problem, etc).

  </pre>
</blockquote>
</body>
</html>

Re: [Astlinux-users] Compile problems with i686 as the TargetArchitecture Variant

[Sebastian A. <sp...@sy...>]

Kristian,

Thanks for the feedback and links. I have switched to i586 and Generic i586
device for now and it seems to be going OK, except that I ran out of disk
space at one point and I was missing uudecode. I had to basically start
again after the disk space problem: cp -r dl dl-bak ; make clean ; make
distclean ; rm -f -r toolchain_build_i586 ; svn update ; make
If I didn't delete toolchain_build_i586 it would just immediately bomb
again.

ftp://ftp.samba.org/ isn't working today but I found the file at
http://samba.org/ftp/ppp/ppp-2.4.3.tar.gz (btw, there is a newer version
available too). I copied the file into the dl directory manually, but it is
still retrying via FTP (try: 4) and the timeouts are extremely long. Is
there anyway to cancel the getter_script.sh without cancelling the make? The
server has spent so long getting to this point I don't want to have to start
it again.

Having said that, I would be willing to try VIA with i586. Is this likely to
work then? What are the differences between Generic i586 and VIA builds?
Presumably it will overwrite build_i586/root so I'd want to back that up...

I saw your svn changes. :)

Is trunk nearly ready for a release? Or more importantly for me right now,
should it be stable?

Thanks for your help. This is my first time trying to compile AstLinux. I
need to add support, i.e. drivers, for a device that is not supported in the
standard build. How do I go about doing this? Presumably I can do it after
the main make has finished...

Sebastian


-----Original Message-----
From: ast...@li...
[mailto:ast...@li...] On Behalf Of Kristian
Kielhofner
Sent: 18 January 2007 15:52
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] Compile problems with i686 as the
TargetArchitecture Variant

On 1/18/07, Sebastian Auriol <sp...@sy...> wrote:
>
>
> Well trying to compile with i386/i686/Generic i586 doesn't work either (on
> 0.4 and trunk), with the same problems, so it looks like the i686 variant
> may be the problem.  I'm going to try again now using i586 as the variant
> for 0.4 branch and trunk...
>
> Sebastian
>
>

Sebastian,

  Thank you for your comments.  A couple of things:

1) Almost all VIA processors have known problems when running with
"i686" compiled code:

http://lists.digium.com/pipermail/asterisk-dev/2003-July/001194.html
http://www.voip-info.org/wiki/view/Asterisk+hardware+mini-itx

  There are other examples all over the place.  On the VIA, stick with i586.

2) In general, if you select a specific device under AstLinux target
devices, you really shouldn't just change the processor architecture.
If you want to do this, create a new target device that will select
your intended target CPU.  Those devices are there (and work with 586)
because they are a specific piece of hardware with a known
configuration.

3) "make clean" is broken all over the place.  Myself and the other
devs know this.  I have submitted a patch to both 0.4 and trunk to fix
the few problems that you pointed out but there are certainly other
problems with make clean.

4) These days, almost all development is done in trunk.  0.4 isn't
updated and fixed nearly as often (your mISDN CVS problem, etc).

-- 
Kristian Kielhofner

[Astlinux-users] Sending email from extensions.conf

[Lonnie A. <li...@lo...>]

Hi,

Several people have asked about sending an email for every incoming  
call in AstLinux.

I have a working example.

exten => 1198,1,Answer
exten => 1198,n,System(/mnt/kd/email_in.sh "${CALLERID(name)}" "$ 
{CALLERID(num)}")
exten => 1198,n,Hangup

Note: The double-quotes are very important.

----- email_in.sh -----
#!/bin/bash
TO_EMAIL=me...@fo...
FROM_EMAIL=pb...@fo...
echo -e "Subject: Incoming call from: $1 <$2>\n
Date: `date -R`\n
From: ${FROM_EMAIL}\n
To: ${TO_EMAIL}\n\n
Incoming call from: $1 <$2>"
| /usr/sbin/msmtp "${TO_EMAIL}" &
exit 0
---- email_in.sh -----
Note: the "echo" "msmtp" line should be one line, I added returns  
before the mailer did.  Join the lines without adding any spaces.

$ chmod 755 email_in.sh

Final Note: "msmtp" can take awhile to execute (a second to many  
seconds) depending on your mail relay, so I execute this as a  
separate process not to delay incoming calls. (note the trailing &)   
If there is a better way of doing this, let us know.

Lonnie

[Astlinux-users] Gumstix CF Keydisk instructions needed

[j Z. <jz...@gm...>]

Morning,
Are there any instructions on how to setup a keydisk using a CF module on a
Netstix computer?  I can see the CF card from uBoot but not from the
astlinux application.
Thanks!

Re: [Astlinux-users] Compile problems with i686 as the Target Architecture Variant

[Kristian K. <kri...@gm...>]

On 1/18/07, Sebastian Auriol <sp...@sy...> wrote:
>
>
> Well trying to compile with i386/i686/Generic i586 doesn't work either (on
> 0.4 and trunk), with the same problems, so it looks like the i686 variant
> may be the problem.  I'm going to try again now using i586 as the variant
> for 0.4 branch and trunk...
>
> Sebastian
>
>

Sebastian,

  Thank you for your comments.  A couple of things:

1) Almost all VIA processors have known problems when running with
"i686" compiled code:

http://lists.digium.com/pipermail/asterisk-dev/2003-July/001194.html
http://www.voip-info.org/wiki/view/Asterisk+hardware+mini-itx

  There are other examples all over the place.  On the VIA, stick with i586.

2) In general, if you select a specific device under AstLinux target
devices, you really shouldn't just change the processor architecture.
If you want to do this, create a new target device that will select
your intended target CPU.  Those devices are there (and work with 586)
because they are a specific piece of hardware with a known
configuration.

3) "make clean" is broken all over the place.  Myself and the other
devs know this.  I have submitted a patch to both 0.4 and trunk to fix
the few problems that you pointed out but there are certainly other
problems with make clean.

4) These days, almost all development is done in trunk.  0.4 isn't
updated and fixed nearly as often (your mISDN CVS problem, etc).

-- 
Kristian Kielhofner

[Astlinux-users] Compile problems with i686 as the Target Architecture Variant

[Sebastian A. <sp...@sy...>]

Well trying to compile with i386/i686/Generic i586 doesn't work either (on
0.4 and trunk), with the same problems, so it looks like the i686 variant
may be the problem.  I'm going to try again now using i586 as the variant
for 0.4 branch and trunk...
 
Sebastian
 


  _____  

From: ast...@li...
[mailto:ast...@li...] On Behalf Of Sebastian
Auriol
Sent: 18 January 2007 14:21
To: 'AstLinux Users Mailing List'
Subject: Re: [Astlinux-users] Compile problems when targetting VIA


Oh, also:  make cleans fail at this point both on 0.4 branch and on trunk:
 
rm
/usr/src/astlinix-trunk/build_i686/root/usr/lib/asterisk/modules/codec_g729a
.so
rm: cannot remove
`/usr/src/astlinix-trunk/build_i686/root/usr/lib/asterisk/modules/codec_g729
a.so': No such file or directory
make: *** [digiumg729-clean] Error 1

Kind regards,
 
Sebastian
 


  _____  

From: ast...@li...
[mailto:ast...@li...] On Behalf Of Sebastian
Auriol
Sent: 18 January 2007 14:04
To: ast...@li...
Subject: [Astlinux-users] Compile problems when targetting VIA



I have found several compile problems when targetting VIA (I'm trying again
now with Generic i586) both on the 0.4 branch and trunk. I chose i386 for
Target Architecture, i686 as the Target Architecture Variant and VIA for the
Target Device...

With astlinix/branches/0.4: 

First mISDN wouldn't compile. It might be due to this error... 

[seb@IVRA1 ~]$ cvs -d:pserver:anonymous:rea...@cv...:/i4ldev
co  mISDN mISDNuser 
cvs [checkout aborted]: connect to cvs.isdn4linux.de(217.160.76.191):2401
failed: Connection refused 

I got this command from the misdn/Makefile as it wasn't on my screen - I had
many pages of errors in misdn. I fixed the network firewall to allow port
2401 but then I got timeouts instead with this command, so I removed mISDN
from the Makefiles as I didn't need it and continued.

The next problem was here: 

mkdir -p /home/seb/astlinux-0.4/build_i686/root/stat/var/lib 
mv /home/seb/astlinux-0.4/build_i686/root/var/lib/asterisk
/home/seb/astlinux-0.4/build_i686/root/stat/var/lib/ 
rm -f /home/seb/astlinux-0.4/build_i686/root/stat/var/lib/asterisk/astdb 
ln -sf /tmp/astdb
/home/seb/astlinux-0.4/build_i686/root/stat/var/lib/asterisk/astdb 
mkdir -p /home/seb/astlinux-0.4/build_i686/root/stat/var/spool 
mv /home/seb/astlinux-0.4/build_i686/root/var/spool/asterisk
/home/seb/astlinux-0.4/build_i686/root/stat/var/spool/ 
mv: cannot overwrite directory
`/home/seb/astlinux-0.4/build_i686/root/stat/var/spool/asterisk' 
make: *** [/home/seb/astlinux-0.4/build_i686/root/usr/sbin/asterisk] Error 1

[seb@IVRA1 astlinux-0.4]$ 

I fixed this by deleting
/home/seb/astlinux-0.4/build_i686/root/stat/var/spool/asterisk (it contained
some gsm files in voicemail box 1234).

Then here: 

make ASTERISK_INCLUDE_DIR=/home/seb/astlinux-0.4/build_i686/asterisk/include
PROC=i686 OSARCH=Linux
CC=/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc \

APP_CONFERENCE_DEBUG=0 SILDET=0 -C
/home/seb/astlinux-0.4/build_i686/app_conference 
make[1]: Entering directory
`/home/seb/astlinux-0.4/build_i686/app_conference' 
/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc
-pipe -fPIC -Wall -Wmissing-prototypes -Wmissing-declarations -g
-I/home/seb/astlinux-0.4/build_i686/asterisk/include  -D_REENTRANT
-D_GNU_SOURCE -O3 -ffast-math -funroll-all-loops -fprefetch-loop-arrays
-fsingle-precision-constant  -DCRYPTO   -c -o app_conference.o
app_conference.c

app_conference.c:1: warning: -fprefetch-loop-arrays not supported for this
target (try -march switches) 
In file included from app_conference.c:19: 
app_conference.h:25:26: asterisk/pbx.h: No such file or directory 
app_conference.h:26:29: asterisk/module.h: No such file or directory 
app_conference.h:27:29: asterisk/logger.h: No such file or directory 
app_conference.h:28:27: asterisk/lock.h: No such file or directory 
app_conference.h:29:28: asterisk/frame.h: No such file or directory 
app_conference.h:30:30: asterisk/manager.h: No such file or directory 
app_conference.h:31:26: asterisk/dsp.h: No such file or directory 
app_conference.h:32:32: asterisk/translate.h: No such file or directory 
app_conference.h:33:30: asterisk/channel.h: No such file or directory 
app_conference.h:34:27: asterisk/file.h: No such file or directory 
app_conference.h:35:26: asterisk/cli.h: No such file or directory 
In file included from app_conference.c:19: 
app_conference.h:192: warning: "struct ast_channel" declared inside
parameter list 
app_conference.h:192: warning: its scope is only this definition or
declaration, which is probably not what you want 
In file included from common.h:26, 
                 from app_conference.c:20: 
conference.h:70: error: parse error before "ast_mutex_t" 
conference.h:70: warning: no semicolon at end of struct or union 
conference.h:86: error: parse error before '}' token 
In file included from common.h:27, 
                 from app_conference.c:20: 
member.h:29:26: asterisk/app.h: No such file or directory 
In file included from common.h:27, 
                 from app_conference.c:20: 
member.h:46: error: parse error before "ast_mutex_t" 
member.h:46: warning: no semicolon at end of struct or union 
member.h:106: error: conflicting types for 'next' 
conference.h:73: error: previous declaration of 'next' was here 
member.h:153: error: parse error before ':' token 
member.h:154: error: parse error before ':' token 
member.h:155: error: parse error before ':' token 
member.h:156: error: parse error before ':' token 
app_conference.c:51: warning: type defaults to `int' in declaration of
`STANDARD_LOCAL_USER' 
app_conference.c:51: warning: data definition has no type or storage class 
app_conference.c:52: warning: type defaults to `int' in declaration of
`LOCAL_USER_DECL' 
app_conference.c:52: warning: data definition has no type or storage class 
app_conference.c:55: warning: no previous prototype for 'unload_module' 
app_conference.c: In function `unload_module': 
app_conference.c:56: error: `STANDARD_HANGUP_LOCALUSERS' undeclared (first
use in this function) 
app_conference.c:56: error: (Each undeclared identifier is reported only
once 
app_conference.c:56: error: for each function it appears in.) 
app_conference.c:61: warning: implicit declaration of function
`ast_unregister_application' 
app_conference.c: At top level: 
app_conference.c:65: warning: no previous prototype for 'load_module' 
app_conference.c: In function `load_module': 
app_conference.c:72: warning: implicit declaration of function
`ast_register_application' 
app_conference.c: At top level: 
app_conference.c:76: warning: no previous prototype for 'description' 
app_conference.c:81: warning: no previous prototype for 'usecount' 
app_conference.c: In function `usecount': 
app_conference.c:83: warning: implicit declaration of function
`STANDARD_USECOUNT' 
app_conference.c: At top level: 
app_conference.c:88: warning: no previous prototype for 'key' 
app_conference.c: In function `key': 
app_conference.c:89: error: `ASTERISK_GPL_KEY' undeclared (first use in this
function) 
app_conference.c: In function `app_conference_main': 
app_conference.c:102: warning: implicit declaration of function
`LOCAL_USER_ADD' 
app_conference.c:108: warning: implicit declaration of function
`LOCAL_USER_REMOVE' 
make[1]: *** [app_conference.o] Error 1 
make[1]: Leaving directory
`/home/seb/astlinux-0.4/build_i686/app_conference' 
make: ***
[/home/seb/astlinux-0.4/build_i686/root/usr/lib/asterisk/modules/app_confere
nce.so] Error 2 

I fixed this by moving package/appconference to
package_disabled/appconference and continued. 

Then the next problem was here: 

make[2]: Leaving directory
`/home/seb/astlinux-0.4/build_i686/bash-3.0/builtins' 
rm -f make_cmd.o 
/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc
-DPROGRAM='"bash"' -DCONF_HOSTTYPE='"i686"' -DCONF_OSTYPE='"linux-gnu"'
-DCONF_MACHTYPE='"i686-pc-linux-gnu"' -DCONF_VENDOR='"pc"'
-DLOCALEDIR='"/usr/share/locale"' -DPACKAGE='"bash"' -DSHELL -DHAVE_CONFIG_H
-I.  -I. -I./include -I./lib   -Os -pipe  -c make_cmd.c

config.status: creating lib/termcap/Makefile 
config.status: creating lib/tilde/Makefile 
rm -f nojobs.o 
/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc
-DPROGRAM='"bash"' -DCONF_HOSTTYPE='"i686"' -DCONF_OSTYPE='"linux-gnu"'
-DCONF_MACHTYPE='"i686-pc-linux-gnu"' -DCONF_VENDOR='"pc"'
-DLOCALEDIR='"/usr/share/locale"' -DPACKAGE='"bash"' -DSHELL -DHAVE_CONFIG_H
-I.  -I. -I./include -I./lib   -Os -pipe  -c nojobs.c

config.status: creating doc/Makefile 
In file included from nojobs.c:57: 
shell.h:41:23: pathnames.h: No such file or directory 
config.status: creating support/Makefile 
make[1]: *** [nojobs.o] Error 1 
make[1]: *** Waiting for unfinished jobs.... 
config.status: creating po/Makefile.in 
config.status: creating examples/loadables/Makefile 
config.status: creating examples/loadables/perl/Makefile 
config.status: creating pathnames.h 
config.status: executing default-1 commands 
config.status: creating po/POTFILES 
config.status: creating po/Makefile 
config.status: executing default commands 
make[1]: Leaving directory `/home/seb/astlinux-0.4/build_i686/bash-3.0' 
make: *** [/home/seb/astlinux-0.4/build_i686/bash-3.0/bash] Error 2 



With astlinux/trunk (on another server - oops, I misspelt linux when I did
the checkout): 

make[1]: Leaving directory
`/usr/src/astlinix-trunk/build_i686/kexec-tools-1.101' 
install -D
/usr/src/astlinix-trunk/build_i686/kexec-tools-1.101/objdir-i586-linux/build
/sbin/kexec /usr/src/astlinix-trunk/build_i686/root/sbin/kexec

install: cannot stat
`/usr/src/astlinix-trunk/build_i686/kexec-tools-1.101/objdir-i586-linux/buil
d/sbin/kexec': No such file or directory

make: *** [/usr/src/astlinix-trunk/build_i686/root/sbin/kexec] Error 1 
[seb@IVRA6 astlinix-trunk]$ 


So finally, I am now trying to compile with i386/i686/Generic i586 instead
of targetting VIA. Hopefully this will work! 

Any suggestions / comments? 

Many thanks, 

Sebastian 

Re: [Astlinux-users] Compile problems when targetting VIA

[Sebastian A. <sp...@sy...>]

Oh, also:  make cleans fail at this point both on 0.4 branch and on trunk:
 
rm
/usr/src/astlinix-trunk/build_i686/root/usr/lib/asterisk/modules/codec_g729a
.so
rm: cannot remove
`/usr/src/astlinix-trunk/build_i686/root/usr/lib/asterisk/modules/codec_g729
a.so': No such file or directory
make: *** [digiumg729-clean] Error 1

Kind regards,
 
Sebastian
 


  _____  

From: ast...@li...
[mailto:ast...@li...] On Behalf Of Sebastian
Auriol
Sent: 18 January 2007 14:04
To: ast...@li...
Subject: [Astlinux-users] Compile problems when targetting VIA



I have found several compile problems when targetting VIA (I'm trying again
now with Generic i586) both on the 0.4 branch and trunk. I chose i386 for
Target Architecture, i686 as the Target Architecture Variant and VIA for the
Target Device...

With astlinix/branches/0.4: 

First mISDN wouldn't compile. It might be due to this error... 

[seb@IVRA1 ~]$ cvs -d:pserver:anonymous:rea...@cv...:/i4ldev
co  mISDN mISDNuser 
cvs [checkout aborted]: connect to cvs.isdn4linux.de(217.160.76.191):2401
failed: Connection refused 

I got this command from the misdn/Makefile as it wasn't on my screen - I had
many pages of errors in misdn. I fixed the network firewall to allow port
2401 but then I got timeouts instead with this command, so I removed mISDN
from the Makefiles as I didn't need it and continued.

The next problem was here: 

mkdir -p /home/seb/astlinux-0.4/build_i686/root/stat/var/lib 
mv /home/seb/astlinux-0.4/build_i686/root/var/lib/asterisk
/home/seb/astlinux-0.4/build_i686/root/stat/var/lib/ 
rm -f /home/seb/astlinux-0.4/build_i686/root/stat/var/lib/asterisk/astdb 
ln -sf /tmp/astdb
/home/seb/astlinux-0.4/build_i686/root/stat/var/lib/asterisk/astdb 
mkdir -p /home/seb/astlinux-0.4/build_i686/root/stat/var/spool 
mv /home/seb/astlinux-0.4/build_i686/root/var/spool/asterisk
/home/seb/astlinux-0.4/build_i686/root/stat/var/spool/ 
mv: cannot overwrite directory
`/home/seb/astlinux-0.4/build_i686/root/stat/var/spool/asterisk' 
make: *** [/home/seb/astlinux-0.4/build_i686/root/usr/sbin/asterisk] Error 1

[seb@IVRA1 astlinux-0.4]$ 

I fixed this by deleting
/home/seb/astlinux-0.4/build_i686/root/stat/var/spool/asterisk (it contained
some gsm files in voicemail box 1234).

Then here: 

make ASTERISK_INCLUDE_DIR=/home/seb/astlinux-0.4/build_i686/asterisk/include
PROC=i686 OSARCH=Linux
CC=/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc \

APP_CONFERENCE_DEBUG=0 SILDET=0 -C
/home/seb/astlinux-0.4/build_i686/app_conference 
make[1]: Entering directory
`/home/seb/astlinux-0.4/build_i686/app_conference' 
/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc
-pipe -fPIC -Wall -Wmissing-prototypes -Wmissing-declarations -g
-I/home/seb/astlinux-0.4/build_i686/asterisk/include  -D_REENTRANT
-D_GNU_SOURCE -O3 -ffast-math -funroll-all-loops -fprefetch-loop-arrays
-fsingle-precision-constant  -DCRYPTO   -c -o app_conference.o
app_conference.c

app_conference.c:1: warning: -fprefetch-loop-arrays not supported for this
target (try -march switches) 
In file included from app_conference.c:19: 
app_conference.h:25:26: asterisk/pbx.h: No such file or directory 
app_conference.h:26:29: asterisk/module.h: No such file or directory 
app_conference.h:27:29: asterisk/logger.h: No such file or directory 
app_conference.h:28:27: asterisk/lock.h: No such file or directory 
app_conference.h:29:28: asterisk/frame.h: No such file or directory 
app_conference.h:30:30: asterisk/manager.h: No such file or directory 
app_conference.h:31:26: asterisk/dsp.h: No such file or directory 
app_conference.h:32:32: asterisk/translate.h: No such file or directory 
app_conference.h:33:30: asterisk/channel.h: No such file or directory 
app_conference.h:34:27: asterisk/file.h: No such file or directory 
app_conference.h:35:26: asterisk/cli.h: No such file or directory 
In file included from app_conference.c:19: 
app_conference.h:192: warning: "struct ast_channel" declared inside
parameter list 
app_conference.h:192: warning: its scope is only this definition or
declaration, which is probably not what you want 
In file included from common.h:26, 
                 from app_conference.c:20: 
conference.h:70: error: parse error before "ast_mutex_t" 
conference.h:70: warning: no semicolon at end of struct or union 
conference.h:86: error: parse error before '}' token 
In file included from common.h:27, 
                 from app_conference.c:20: 
member.h:29:26: asterisk/app.h: No such file or directory 
In file included from common.h:27, 
                 from app_conference.c:20: 
member.h:46: error: parse error before "ast_mutex_t" 
member.h:46: warning: no semicolon at end of struct or union 
member.h:106: error: conflicting types for 'next' 
conference.h:73: error: previous declaration of 'next' was here 
member.h:153: error: parse error before ':' token 
member.h:154: error: parse error before ':' token 
member.h:155: error: parse error before ':' token 
member.h:156: error: parse error before ':' token 
app_conference.c:51: warning: type defaults to `int' in declaration of
`STANDARD_LOCAL_USER' 
app_conference.c:51: warning: data definition has no type or storage class 
app_conference.c:52: warning: type defaults to `int' in declaration of
`LOCAL_USER_DECL' 
app_conference.c:52: warning: data definition has no type or storage class 
app_conference.c:55: warning: no previous prototype for 'unload_module' 
app_conference.c: In function `unload_module': 
app_conference.c:56: error: `STANDARD_HANGUP_LOCALUSERS' undeclared (first
use in this function) 
app_conference.c:56: error: (Each undeclared identifier is reported only
once 
app_conference.c:56: error: for each function it appears in.) 
app_conference.c:61: warning: implicit declaration of function
`ast_unregister_application' 
app_conference.c: At top level: 
app_conference.c:65: warning: no previous prototype for 'load_module' 
app_conference.c: In function `load_module': 
app_conference.c:72: warning: implicit declaration of function
`ast_register_application' 
app_conference.c: At top level: 
app_conference.c:76: warning: no previous prototype for 'description' 
app_conference.c:81: warning: no previous prototype for 'usecount' 
app_conference.c: In function `usecount': 
app_conference.c:83: warning: implicit declaration of function
`STANDARD_USECOUNT' 
app_conference.c: At top level: 
app_conference.c:88: warning: no previous prototype for 'key' 
app_conference.c: In function `key': 
app_conference.c:89: error: `ASTERISK_GPL_KEY' undeclared (first use in this
function) 
app_conference.c: In function `app_conference_main': 
app_conference.c:102: warning: implicit declaration of function
`LOCAL_USER_ADD' 
app_conference.c:108: warning: implicit declaration of function
`LOCAL_USER_REMOVE' 
make[1]: *** [app_conference.o] Error 1 
make[1]: Leaving directory
`/home/seb/astlinux-0.4/build_i686/app_conference' 
make: ***
[/home/seb/astlinux-0.4/build_i686/root/usr/lib/asterisk/modules/app_confere
nce.so] Error 2 

I fixed this by moving package/appconference to
package_disabled/appconference and continued. 

Then the next problem was here: 

make[2]: Leaving directory
`/home/seb/astlinux-0.4/build_i686/bash-3.0/builtins' 
rm -f make_cmd.o 
/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc
-DPROGRAM='"bash"' -DCONF_HOSTTYPE='"i686"' -DCONF_OSTYPE='"linux-gnu"'
-DCONF_MACHTYPE='"i686-pc-linux-gnu"' -DCONF_VENDOR='"pc"'
-DLOCALEDIR='"/usr/share/locale"' -DPACKAGE='"bash"' -DSHELL -DHAVE_CONFIG_H
-I.  -I. -I./include -I./lib   -Os -pipe  -c make_cmd.c

config.status: creating lib/termcap/Makefile 
config.status: creating lib/tilde/Makefile 
rm -f nojobs.o 
/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc
-DPROGRAM='"bash"' -DCONF_HOSTTYPE='"i686"' -DCONF_OSTYPE='"linux-gnu"'
-DCONF_MACHTYPE='"i686-pc-linux-gnu"' -DCONF_VENDOR='"pc"'
-DLOCALEDIR='"/usr/share/locale"' -DPACKAGE='"bash"' -DSHELL -DHAVE_CONFIG_H
-I.  -I. -I./include -I./lib   -Os -pipe  -c nojobs.c

config.status: creating doc/Makefile 
In file included from nojobs.c:57: 
shell.h:41:23: pathnames.h: No such file or directory 
config.status: creating support/Makefile 
make[1]: *** [nojobs.o] Error 1 
make[1]: *** Waiting for unfinished jobs.... 
config.status: creating po/Makefile.in 
config.status: creating examples/loadables/Makefile 
config.status: creating examples/loadables/perl/Makefile 
config.status: creating pathnames.h 
config.status: executing default-1 commands 
config.status: creating po/POTFILES 
config.status: creating po/Makefile 
config.status: executing default commands 
make[1]: Leaving directory `/home/seb/astlinux-0.4/build_i686/bash-3.0' 
make: *** [/home/seb/astlinux-0.4/build_i686/bash-3.0/bash] Error 2 



With astlinux/trunk (on another server - oops, I misspelt linux when I did
the checkout): 

make[1]: Leaving directory
`/usr/src/astlinix-trunk/build_i686/kexec-tools-1.101' 
install -D
/usr/src/astlinix-trunk/build_i686/kexec-tools-1.101/objdir-i586-linux/build
/sbin/kexec /usr/src/astlinix-trunk/build_i686/root/sbin/kexec

install: cannot stat
`/usr/src/astlinix-trunk/build_i686/kexec-tools-1.101/objdir-i586-linux/buil
d/sbin/kexec': No such file or directory

make: *** [/usr/src/astlinix-trunk/build_i686/root/sbin/kexec] Error 1 
[seb@IVRA6 astlinix-trunk]$ 


So finally, I am now trying to compile with i386/i686/Generic i586 instead
of targetting VIA. Hopefully this will work! 

Any suggestions / comments? 

Many thanks, 

Sebastian 

[Astlinux-users] Compile problems when targetting VIA

[Sebastian A. <sp...@sy...>]

I have found several compile problems when targetting VIA (I'm trying again
now with Generic i586) both on the 0.4 branch and trunk. I chose i386 for
Target Architecture, i686 as the Target Architecture Variant and VIA for the
Target Device...

With astlinix/branches/0.4:

First mISDN wouldn't compile. It might be due to this error...

[seb@IVRA1 ~]$ cvs -d:pserver:anonymous:rea...@cv...:/i4ldev
co  mISDN mISDNuser
cvs [checkout aborted]: connect to cvs.isdn4linux.de(217.160.76.191):2401
failed: Connection refused

I got this command from the misdn/Makefile as it wasn't on my screen - I had
many pages of errors in misdn. I fixed the network firewall to allow port
2401 but then I got timeouts instead with this command, so I removed mISDN
from the Makefiles as I didn't need it and continued.

The next problem was here:

mkdir -p /home/seb/astlinux-0.4/build_i686/root/stat/var/lib
mv /home/seb/astlinux-0.4/build_i686/root/var/lib/asterisk
/home/seb/astlinux-0.4/build_i686/root/stat/var/lib/
rm -f /home/seb/astlinux-0.4/build_i686/root/stat/var/lib/asterisk/astdb
ln -sf /tmp/astdb
/home/seb/astlinux-0.4/build_i686/root/stat/var/lib/asterisk/astdb
mkdir -p /home/seb/astlinux-0.4/build_i686/root/stat/var/spool
mv /home/seb/astlinux-0.4/build_i686/root/var/spool/asterisk
/home/seb/astlinux-0.4/build_i686/root/stat/var/spool/
mv: cannot overwrite directory
`/home/seb/astlinux-0.4/build_i686/root/stat/var/spool/asterisk'
make: *** [/home/seb/astlinux-0.4/build_i686/root/usr/sbin/asterisk] Error 1
[seb@IVRA1 astlinux-0.4]$ 

I fixed this by deleting
/home/seb/astlinux-0.4/build_i686/root/stat/var/spool/asterisk (it contained
some gsm files in voicemail box 1234).

Then here:

make ASTERISK_INCLUDE_DIR=/home/seb/astlinux-0.4/build_i686/asterisk/include
PROC=i686 OSARCH=Linux
CC=/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc \
APP_CONFERENCE_DEBUG=0 SILDET=0 -C
/home/seb/astlinux-0.4/build_i686/app_conference
make[1]: Entering directory
`/home/seb/astlinux-0.4/build_i686/app_conference'
/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc
-pipe -fPIC -Wall -Wmissing-prototypes -Wmissing-declarations -g
-I/home/seb/astlinux-0.4/build_i686/asterisk/include  -D_REENTRANT
-D_GNU_SOURCE -O3 -ffast-math -funroll-all-loops -fprefetch-loop-arrays
-fsingle-precision-constant  -DCRYPTO   -c -o app_conference.o
app_conference.c
app_conference.c:1: warning: -fprefetch-loop-arrays not supported for this
target (try -march switches)
In file included from app_conference.c:19:
app_conference.h:25:26: asterisk/pbx.h: No such file or directory
app_conference.h:26:29: asterisk/module.h: No such file or directory
app_conference.h:27:29: asterisk/logger.h: No such file or directory
app_conference.h:28:27: asterisk/lock.h: No such file or directory
app_conference.h:29:28: asterisk/frame.h: No such file or directory
app_conference.h:30:30: asterisk/manager.h: No such file or directory
app_conference.h:31:26: asterisk/dsp.h: No such file or directory
app_conference.h:32:32: asterisk/translate.h: No such file or directory
app_conference.h:33:30: asterisk/channel.h: No such file or directory
app_conference.h:34:27: asterisk/file.h: No such file or directory
app_conference.h:35:26: asterisk/cli.h: No such file or directory
In file included from app_conference.c:19:
app_conference.h:192: warning: "struct ast_channel" declared inside
parameter list
app_conference.h:192: warning: its scope is only this definition or
declaration, which is probably not what you want
In file included from common.h:26,
                 from app_conference.c:20:
conference.h:70: error: parse error before "ast_mutex_t"
conference.h:70: warning: no semicolon at end of struct or union
conference.h:86: error: parse error before '}' token
In file included from common.h:27,
                 from app_conference.c:20:
member.h:29:26: asterisk/app.h: No such file or directory
In file included from common.h:27,
                 from app_conference.c:20:
member.h:46: error: parse error before "ast_mutex_t"
member.h:46: warning: no semicolon at end of struct or union
member.h:106: error: conflicting types for 'next'
conference.h:73: error: previous declaration of 'next' was here
member.h:153: error: parse error before ':' token
member.h:154: error: parse error before ':' token
member.h:155: error: parse error before ':' token
member.h:156: error: parse error before ':' token
app_conference.c:51: warning: type defaults to `int' in declaration of
`STANDARD_LOCAL_USER'
app_conference.c:51: warning: data definition has no type or storage class
app_conference.c:52: warning: type defaults to `int' in declaration of
`LOCAL_USER_DECL'
app_conference.c:52: warning: data definition has no type or storage class
app_conference.c:55: warning: no previous prototype for 'unload_module'
app_conference.c: In function `unload_module':
app_conference.c:56: error: `STANDARD_HANGUP_LOCALUSERS' undeclared (first
use in this function)
app_conference.c:56: error: (Each undeclared identifier is reported only
once
app_conference.c:56: error: for each function it appears in.)
app_conference.c:61: warning: implicit declaration of function
`ast_unregister_application'
app_conference.c: At top level:
app_conference.c:65: warning: no previous prototype for 'load_module'
app_conference.c: In function `load_module':
app_conference.c:72: warning: implicit declaration of function
`ast_register_application'
app_conference.c: At top level:
app_conference.c:76: warning: no previous prototype for 'description'
app_conference.c:81: warning: no previous prototype for 'usecount'
app_conference.c: In function `usecount':
app_conference.c:83: warning: implicit declaration of function
`STANDARD_USECOUNT'
app_conference.c: At top level:
app_conference.c:88: warning: no previous prototype for 'key'
app_conference.c: In function `key':
app_conference.c:89: error: `ASTERISK_GPL_KEY' undeclared (first use in this
function)
app_conference.c: In function `app_conference_main':
app_conference.c:102: warning: implicit declaration of function
`LOCAL_USER_ADD'
app_conference.c:108: warning: implicit declaration of function
`LOCAL_USER_REMOVE'
make[1]: *** [app_conference.o] Error 1
make[1]: Leaving directory
`/home/seb/astlinux-0.4/build_i686/app_conference'
make: ***
[/home/seb/astlinux-0.4/build_i686/root/usr/lib/asterisk/modules/app_confere
nce.so] Error 2

I fixed this by moving package/appconference to
package_disabled/appconference and continued.

Then the next problem was here:

make[2]: Leaving directory
`/home/seb/astlinux-0.4/build_i686/bash-3.0/builtins'
rm -f make_cmd.o
/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc
-DPROGRAM='"bash"' -DCONF_HOSTTYPE='"i686"' -DCONF_OSTYPE='"linux-gnu"'
-DCONF_MACHTYPE='"i686-pc-linux-gnu"' -DCONF_VENDOR='"pc"'
-DLOCALEDIR='"/usr/share/locale"' -DPACKAGE='"bash"' -DSHELL -DHAVE_CONFIG_H
-I.  -I. -I./include -I./lib   -Os -pipe  -c make_cmd.c
config.status: creating lib/termcap/Makefile
config.status: creating lib/tilde/Makefile
rm -f nojobs.o
/home/seb/astlinux-0.4/build_i686/staging_dir/bin/i686-linux-uclibc-gcc
-DPROGRAM='"bash"' -DCONF_HOSTTYPE='"i686"' -DCONF_OSTYPE='"linux-gnu"'
-DCONF_MACHTYPE='"i686-pc-linux-gnu"' -DCONF_VENDOR='"pc"'
-DLOCALEDIR='"/usr/share/locale"' -DPACKAGE='"bash"' -DSHELL -DHAVE_CONFIG_H
-I.  -I. -I./include -I./lib   -Os -pipe  -c nojobs.c
config.status: creating doc/Makefile
In file included from nojobs.c:57:
shell.h:41:23: pathnames.h: No such file or directory
config.status: creating support/Makefile
make[1]: *** [nojobs.o] Error 1
make[1]: *** Waiting for unfinished jobs....
config.status: creating po/Makefile.in
config.status: creating examples/loadables/Makefile
config.status: creating examples/loadables/perl/Makefile
config.status: creating pathnames.h
config.status: executing default-1 commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
config.status: executing default commands
make[1]: Leaving directory `/home/seb/astlinux-0.4/build_i686/bash-3.0'
make: *** [/home/seb/astlinux-0.4/build_i686/bash-3.0/bash] Error 2



With astlinux/trunk (on another server - oops, I misspelt linux when I did
the checkout):

make[1]: Leaving directory
`/usr/src/astlinix-trunk/build_i686/kexec-tools-1.101'
install -D
/usr/src/astlinix-trunk/build_i686/kexec-tools-1.101/objdir-i586-linux/build
/sbin/kexec /usr/src/astlinix-trunk/build_i686/root/sbin/kexec
install: cannot stat
`/usr/src/astlinix-trunk/build_i686/kexec-tools-1.101/objdir-i586-linux/buil
d/sbin/kexec': No such file or directory
make: *** [/usr/src/astlinix-trunk/build_i686/root/sbin/kexec] Error 1
[seb@IVRA6 astlinix-trunk]$


So finally, I am now trying to compile with i386/i686/Generic i586 instead
of targetting VIA. Hopefully this will work!

Any suggestions / comments?

Many thanks,

Sebastian

Re: [Astlinux-users] astmanproxy

[olivier.taylor <oli...@gm...>]

Kristian,

Thanks for the info.

Quiet easy in fact, they add an option on the command line for the use=20
of SSL

in /etc/init.d/asterisk I have modified the line 69 as followed :

host =3D localhost, 5038, $ASTMANPROXY_USER, $ASTMANPROXY_PASS, on, off

just added off to the host line.

Olivier

Kristian Kielhofner a =E9crit :
> On 1/13/07, olivier.taylor <oli...@gm...> wrote:
>> Aborting: server spec incomplete : 127.0.0.1,5038,user,password,on
>>
>> Checked the config file and don't see any errors
>>
>> user, password and port are conform to manager.conf
>>
>> any idea?
>>
>> Olivier
>>
>
> Olivier,
>
>  The newer version of astmanproxy probably uses different config file
> syntax.  I don't use it as much anymore (astmanproxy).  Any way you
> could take a look at the astmanproxy docs and get a working config
> file?  That way I could upgrade the init script so that it will
> actually work!
>

Re: [Astlinux-users] astmanproxy

[Kristian K. <kri...@gm...>]

On 1/13/07, olivier.taylor <oli...@gm...> wrote:
> Aborting: server spec incomplete : 127.0.0.1,5038,user,password,on
>
> Checked the config file and don't see any errors
>
> user, password and port are conform to manager.conf
>
> any idea?
>
> Olivier
>

Olivier,

  The newer version of astmanproxy probably uses different config file
syntax.  I don't use it as much anymore (astmanproxy).  Any way you
could take a look at the astmanproxy docs and get a working config
file?  That way I could upgrade the init script so that it will
actually work!

-- 
Kristian Kielhofner

[Astlinux-users] astmanproxy

[olivier.taylor <oli...@gm...>]

when i try to start astmanproxy from rc.conf I get:

Aborting: server spec incomplete : 127.0.0.1,5038,xxx,yyy,on

Checked the config file and don't see any errors

user, password and port are conform to manager.conf

any idea?

Olivier

[Astlinux-users] boot logs and klogd

[Sebastian A. <sp...@sy...>]

Hello all,

I would like to be able to see the logs from when AstLinux boots.
*	The dmesg command just seems to read from a small buffer in memory
(dmesg -s SIZE doesn't seem to work) and there are no actual boot log files
that I can find, other than just a few messages in /var/log/messages.
*	I was thinking of making syslogd start earlier in the boot process.
However, if I am logging to an external syslog server with syslogd, does
that mean that syslogd has to start after the network, or will those UDP
packets just silently fail until the network comes up?  Will this even help
to log all the boot process?
*	I noticed that klogd is installed, but it is not set to run.
Normally (on other distributions of Linux), /etc/init.d/syslog incorporates
code to stop and start klogd as well as syslogd. Should it work it I either
put this code into /etc/init.d/syslog or create a new init script for klogd
on AstLinux?
*	Is there a better way to see the boot logs that I am missing?

Many thanks,

Sebastian 
 
 
___________________________________________
Sebastian Auriol

Re: [Astlinux-users] new image format

[Kristian K. <kri...@gm...>]

On 1/15/07, Terry Markovich <tm...@be...> wrote:
>
> Kristian,
>
> It sounds pretty interesting.  I took a look at the SF site, it looks
> similar to what I did for my initrd image, just configure buildroot2 for
> a minimal set of packages and then build the image.  Are the files in
> SF's svn repository the latest you are using?
>
> So does the AstLinux image that gets loaded by runnix get loop mounted?
>
> Terry
>

Terry,

  Yes, they are the "latest", which like I said, isn't saying much
because I haven't worked on it in quite some time.

  I used a slightly modified initrd.img from the AstLinux live CD to
make this work.  I use losetup and then I copy the entire image to
RAM, then I switch to the new root.  I didn't like the idea of having
the FAT fs mounted all of the time just for the loop image...

  What do you think?

-- 
Kristian Kielhofner

Re: [Astlinux-users] new image format

[Terry M. <tm...@be...>]

On Mon, 2007-01-15 at 17:29 -0500, Kristian Kielhofner wrote:
> On 1/15/07, Terry Markovich <tm...@be...> wrote:
> >
> > Kristian,
> >
> > Really just wondering if you had something imminent.  For upgrading my
> > appliance, I think I will have a boot partition with a kernel (with all
> > needed drivers builtin) and a filesystem in an initrd, which will
> > immediately execute an upgrade script.  That way I can then overwrite my
> > CF disk with a new partition image (leaving the boot partition in
> > place).
> >
> > Terry
> >
> 
> Terry,
> 
>   Star2Star is (and has been using) a runnix/astlinux/syslinux/kexec
> based bootloader for quite some time.  However, I haven't made the
> specific configuration available because a) I want to make some
> improvments first and b) because we control the entire appliance and
> network, I can be much more certain that I'm not forgetting something
> and someone's data might go missing, etc.
> 
>   It's been working quite well.
> 
>   Here is what we are doing:
> 
> - Partition CF card with one 128mb FAT16 partition.  This holds
> syslinux, runnix, and full ext2 AstLinux disk images (actually more
> than that - they are identical to the .img files already created)
> 
> - CF boots, syslinux boots runnix
> 
> - runnix looks for a "good" AstLinux image and boots it.  If none is
> found, it connects to our provisioning server (runnix supports
> dhcp/ssh/wget/etc/etc) and downloads, verifies, installs and boots the
> new AstLinux image.  It oarses a config file for this info.
> 
>   Runnix has been at 0.1 since I created it in August last year.  I
> need some more time to work on it!  Maybe you'd like to help? :)
> 

Kristian,

It sounds pretty interesting.  I took a look at the SF site, it looks
similar to what I did for my initrd image, just configure buildroot2 for
a minimal set of packages and then build the image.  Are the files in
SF's svn repository the latest you are using?

So does the AstLinux image that gets loaded by runnix get loop mounted?

Terry