astlinux-users — AstLinux Users Mailing List

Re: [Astlinux-users] sqlite cdr

[walter t. <sta...@gm...>]

Thanks a lot. I see that maybe there is some errors on sqlite compiling,
when I run sqlite3 there are some errors.

2007/3/5, Darrick Hartman <dha...@dj...>:
>
> walter trucci wrote:
> > Hi I'm testing latest branch image, there is sqlite3 and I want to use
> > it for CDR, but... no cdr_sqlite.so is created in modules, and this
> > document
> > http://www.voip-info.org/wiki/view/Asterisk+cdr+SQLite explain that if
> > sqlite is installed, cdr_sqlite.so is created automatically. Any idea
> > how to solve this problem? And is there a good way to menage CDR on
> > astlinux?
> Walter,
>
> I'll look into that.  I need to force sqlite to be compiled before
> asterisk.
>
> Darrick
>
> --
> Darrick Hartman
> DJH Solutions, LLC
> http://www.djhsolutions.com
>
>
> -------------------------------------------------------------------------
> 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....
>

Re: [Astlinux-users] sqlite cdr

[Darrick H. <dha...@dj...>]

walter trucci wrote:
> Hi I'm testing latest branch image, there is sqlite3 and I want to use 
> it for CDR, but... no cdr_sqlite.so is created in modules, and this 
> document 
> http://www.voip-info.org/wiki/view/Asterisk+cdr+SQLite explain that if 
> sqlite is installed, cdr_sqlite.so is created automatically. Any idea 
> how to solve this problem? And is there a good way to menage CDR on 
> astlinux?
Walter,

I'll look into that.  I need to force sqlite to be compiled before asterisk.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

[Astlinux-users] sqlite cdr

[walter t. <sta...@gm...>]

Hi I'm testing latest branch image, there is sqlite3 and I want to use it
for CDR, but... no cdr_sqlite.so is created in modules, and this document
http://www.voip-info.org/wiki/view/Asterisk+cdr+SQLite explain that if
sqlite is installed, cdr_sqlite.so is created automatically. Any idea how to
solve this problem? And is there a good way to menage CDR on astlinux?
Best Regards
Walter

Re: [Astlinux-users] trunk compile error - flite

[Darrick H. <dha...@dj...>]

ast...@el... wrote:
>> ast...@el... wrote:
>>     
>>> Seems like flite is unhappy. This is being compiled with the ALSA stuff.
>>>
>>>       
>> Flite is not maintained.  There are likely missing libraries that are
>> causing it to fail on compiling.  I don't see us including flite as a
>> standard package just because of the cpu horsepower required.  Feel free
>> to fix the compile errors and contribute a fixed package.
>>
>> Darrick
>>     
>
> Is there a convenient list of unmaintained/unsupported packages? Or will
> there be a demarcation in the make menuconfig for unsupported/deprecated
> packages/options?
>   
Basically, the maintained packages are those that are included in the 
standard astlinux.config file.  For a little bit of history, several 
packages that are currently in the development environment are there 
because they were part of the original buildroot tree.  Some packages 
(such as wget) would provide functionality that is already present in 
busybox.  There are no real plans to mark packages as unsupported or 
unmaintained, but that would not be too difficult to do.  It's just not 
going to be near the top of the priority list.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] trunk compile error stuff

[<ast...@el...>]

> ast...@el... wrote:
>> Just some minor stuff really. When downloading, it seems ftp.digium.com
>> gets cranky. They seem to loadbalance between ftp1 and ftp2. When ftp1
>> is
>> being cranky, ftp2 is reliable. ftp2.digium.com is not quite as up to
>> date
>> sometimes though.
>>
> This is expected when Digium announces a release (as they did today).
> This will likely be just fine in a day or so after the initial surge
> that a site can expect with a new release.
>
> Darrick

Actually, this has been a recurring problem for me before today. That's
why I mentioned it.

Re: [Astlinux-users] trunk compile error - flite

[<ast...@el...>]

> ast...@el... wrote:
>> Seems like flite is unhappy. This is being compiled with the ALSA stuff.
>>
> Flite is not maintained.  There are likely missing libraries that are
> causing it to fail on compiling.  I don't see us including flite as a
> standard package just because of the cpu horsepower required.  Feel free
> to fix the compile errors and contribute a fixed package.
>
> Darrick

Is there a convenient list of unmaintained/unsupported packages? Or will
there be a demarcation in the make menuconfig for unsupported/deprecated
packages/options?

Re: [Astlinux-users] trunk compile error stuff

[Darrick H. <dha...@dj...>]

ast...@el... wrote:
> Just some minor stuff really. When downloading, it seems ftp.digium.com
> gets cranky. They seem to loadbalance between ftp1 and ftp2. When ftp1 is
> being cranky, ftp2 is reliable. ftp2.digium.com is not quite as up to date
> sometimes though.
>   
This is expected when Digium announces a release (as they did today).  
This will likely be just fine in a day or so after the initial surge 
that a site can expect with a new release.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] trunk compile error - flite

[Darrick H. <dha...@dj...>]

ast...@el... wrote:
> Seems like flite is unhappy. This is being compiled with the ALSA stuff.
>   
Flite is not maintained.  There are likely missing libraries that are 
causing it to fail on compiling.  I don't see us including flite as a 
standard package just because of the cpu horsepower required.  Feel free 
to fix the compile errors and contribute a fixed package.

Darrick

>
> /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
> -Os -pipe  -Wall    -o ../bin/flite_time flite_time_main.o
> -L../build/i386-linux-gnu/lib -lflite_cmu_time_awb -lflite_usenglish
> -lflite_cmulex -L../build/i386-linux-gnu/lib -lflite -lm
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_open':
> audio.c:(.text+0x2b): undefined reference to `audio_open_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_write':
> audio.c:(.text+0x3ab): undefined reference to `audio_write_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_close':
> audio.c:(.text+0x88): undefined reference to `audio_close_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_drain':
> audio.c:(.text+0x3db): undefined reference to `audio_drain_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_flush':
> audio.c:(.text+0x3e4): undefined reference to `audio_flush_oss'
> collect2: ld returned 1 exit status
> make[2]: *** [../bin/flite] Error 1
> make[2]: *** Waiting for unfinished jobs....
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_open':
> audio.c:(.text+0x2b): undefined reference to `audio_open_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_write':
> audio.c:(.text+0x3ab): undefined reference to `audio_write_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_close':
> audio.c:(.text+0x88): undefined reference to `audio_close_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_drain':
> audio.c:(.text+0x3db): undefined reference to `audio_drain_oss'
> ../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_flush':
> audio.c:(.text+0x3e4): undefined reference to `audio_flush_oss'
> collect2: ld returned 1 exit status
> make[2]: *** [../bin/flite_time] Error 1
> make[1]: *** [build/i386-linux-gnu/obj//.make_build_dirs] Error 2
> make[1]: Leaving directory
> `/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/flite-1.3-release'
> make: ***
> [/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/flite-1.3-release/bin/flite]
> Error 2
>
> -------------------------------------------------------------------------
> 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....
>   


-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

[Astlinux-users] trunk compile error stuff

[<ast...@el...>]

Just some minor stuff really. When downloading, it seems ftp.digium.com
gets cranky. They seem to loadbalance between ftp1 and ftp2. When ftp1 is
being cranky, ftp2 is reliable. ftp2.digium.com is not quite as up to date
sometimes though.

Also, the PostgreSQL version being used, 8.1.4 , doesn't seem to be
available at the download sites anymore. Closest match is 8.1.7 which
seems to compile alright.

[Astlinux-users] trunk compile error - flite

[<ast...@el...>]

Seems like flite is unhappy. This is being compiled with the ALSA stuff.


/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
-Os -pipe  -Wall    -o ../bin/flite_time flite_time_main.o
-L../build/i386-linux-gnu/lib -lflite_cmu_time_awb -lflite_usenglish
-lflite_cmulex -L../build/i386-linux-gnu/lib -lflite -lm
../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_open':
audio.c:(.text+0x2b): undefined reference to `audio_open_oss'
../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_write':
audio.c:(.text+0x3ab): undefined reference to `audio_write_oss'
../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_close':
audio.c:(.text+0x88): undefined reference to `audio_close_oss'
../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_drain':
audio.c:(.text+0x3db): undefined reference to `audio_drain_oss'
../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_flush':
audio.c:(.text+0x3e4): undefined reference to `audio_flush_oss'
collect2: ld returned 1 exit status
make[2]: *** [../bin/flite] Error 1
make[2]: *** Waiting for unfinished jobs....
../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_open':
audio.c:(.text+0x2b): undefined reference to `audio_open_oss'
../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_write':
audio.c:(.text+0x3ab): undefined reference to `audio_write_oss'
../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_close':
audio.c:(.text+0x88): undefined reference to `audio_close_oss'
../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_drain':
audio.c:(.text+0x3db): undefined reference to `audio_drain_oss'
../build/i386-linux-gnu/lib/libflite.a(audio.o): In function `audio_flush':
audio.c:(.text+0x3e4): undefined reference to `audio_flush_oss'
collect2: ld returned 1 exit status
make[2]: *** [../bin/flite_time] Error 1
make[1]: *** [build/i386-linux-gnu/obj//.make_build_dirs] Error 2
make[1]: Leaving directory
`/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/flite-1.3-release'
make: ***
[/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/flite-1.3-release/bin/flite]
Error 2

Re: [Astlinux-users] RFC: IMPORTANT astfw changes

[<ast...@el...>]

>
>   I have been using MASQPORTS=30000-60000 and it has been working
> quite well.  I am thinking that this should be the default in
> AstLinux.  The only problem is that #2 (from above) is there for a
> reason.  Some applications need to use the same port number.  I have
> yet to run into such an application, but you never know...
>
>   Should MASQPORTS=30000-60000 be default on new AstLinux systems?


As long as it you can tweak it in rc.conf, I'm not going to complain.
There are places that ask for 10k-30k so people need to adjust pretty
easily. This will actually be a sticking point for some people
potentially, when they aren't quite sure what their range should be, and
have to experiment/tweak (such as when their provider doesn't officially
support other hardware and don't feel like telling you the range).


Actually, this brings up an ugly point I ran across while fooling around
with my WRAP, though maybe I was being dumb. I had it attached to two
different networks, one for primary service, and a second network to be a
branch office PBX below some other SIP server. The problem is, both
primary and office networks required DHCP, and the office network SIP
server was on another subnet. I did an ugly hack where I set eth0 to be
EXTIF, and I did not set eth2 as a INTIF. Instead I tweaked the iptables
setup so I had a third option for the DMZ setup I called intme, which
created an internal use connection that linked exclusively to the WRAP and
couldn't go downstream into the eth1 internal network, or back upstream
and out through eth0. In rc.conf I defined a static IP and associated
information. Unfortunately, this did solve all my problems, as I
periodically had to undo the setup and set eth2 as EXTIF just to tickle
the office DHCP server (it doesn't behave and check an IP before
assigning, so I had my IP address stolen before). That, and I had to
manually add a route to the office SIP server through the office network
gateway, otherwise the WRAP would use the default route and never connect.

Is there a cleaner way of setting up a second network link that isn't a
failover link, being a DHCP client? I was connecting to a trusted network
on the office link so things were okay, but in the future I would want to
apply the astfw firewall rules to that second link. It would also be nice
to be able to define the additional route information in rc.conf for the
office link.

I suppose this is unique to devices with three or more interfaces, but it
seems like you have the situation of above/below/sideways, and the link
situation of "talk to only me"/"talk to me and stuff below"/"talk to only
stuff below"/"talk to only above"/"talk to me and above"/"talk to
everybody"/"talk to everybody but me".

Re: [Astlinux-users] is there possibility to use PC with astlinux PBX, also as a print server and file server

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

Actually, one would only need CUPS. I agree with Darrick though that 
this isn't really on the devs scopes and it's probably not good practice 
- imagine if an inexperienced admin didn't put a printjob size limit in 
place, then a user could very easily crash the phones just by printing 
out their CAD drawings and thereby depleting all RAM.

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.



Darrick Hartman wrote:
> nedi wrote:
>   
>> Hi, all
>> is there possibility to use PC with astlinux PBX,also as a print server and 
>> file server
>>   
>>     
> Not currently.  You'd have to build samba (and the required packages) 
> and cups.  It's possible, but the current developers don't have those 
> functions on their radar.
>
> Darrick
>
>   

Re: [Astlinux-users] is there possibility to use PC with astlinux PBX, also as a print server and file server

[Darrick H. <dha...@dj...>]

nedi wrote:
> Hi, all
> is there possibility to use PC with astlinux PBX,also as a print server and 
> file server
>   
Not currently.  You'd have to build samba (and the required packages) 
and cups.  It's possible, but the current developers don't have those 
functions on their radar.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

[Astlinux-users] is there possibility to use PC with astlinux PBX, also as a print server and file server

[nedi <ne...@gm...>]

Hi, all
is there possibility to use PC with astlinux PBX,also as a print server and 
file server
best regards
nedi
 

Re: [Astlinux-users] Compile errors

[Manuel D. <man...@te...>]

Ok, I think Kristian say that the new version will be ready soon. I can =
wait
until he finishes it. Meantime I will try to make a package to include
lcd4linux.=20

--
Manuel

-----Mensaje original-----
De: ast...@li...
[mailto:ast...@li...] En nombre de =
Darrick
Hartman
Enviado el: s=E1bado, 03 de marzo de 2007 20:09
Para: AstLinux Users Mailing List
Asunto: Re: [Astlinux-users] Compile errors

Manuel Dominguez wrote:
> Darrick,
>
> Thanks for your explanation. I need trunk because the NIC cards in my
> motherboard are not supported in 0.4. I am trying to get enough
information
> about trunk to be ready when Kristian finishes it and to test my new
> motherboard with last version. I will try to give information to all =
about
> my problems and tests. I am very new in linux but during my tests I am
> learning a lot of things about builroot, packages, compile... Sorry if =
I
> make many trivial questions.
>
> In reference to compile trunk in this moment I don=92t have problems. =
My
> problem is how to boot from my compact flash. By the moment I can use =
the
> iso file burning a DVD or CD and start in livecd.=20
> Following the procedure that livecd use to install image in hard =
drive, I
> have found the file linuxrc. I have tried to follow all steps in this =
file
> but I think something is wrong. I don=92t know!!
>  =20
We may be able to add support for that nic to 0.4 as long as it is=20
supported in the 2.6.16.12 kernel. I really don't want to bump the=20
kernel version in the 0.4 branch. You can look back in trunk svn changes =

and see where Kristian removed the grub files. It's possible to add=20
those back in on your local svn copy and compile using grub as a target=20
instead of the iso stuff.

Darrick

> As was mentioned before, there are major changes going on in trunk. =20
> Some things will be broken from time to time.
>
> Kristian is removing grub from trunk.  He's moving to a system that =
will=20
> take a bit for the transition, but will be better in the long run for=20
> upgrades.  He's mentioned this in the past (you may have seen mention =
of=20
> runnix).  The reason the image you built hangs at the grub menu, it's=20
> because those components were removed.  Unless you want to be on the=20
> cutting edge, you will be happier running the 0.4 branch (although I'm =

> sure Kristian appreciates any help he can get with testing and =
debugging).
>  =20



--=20
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com


-------------------------------------------------------------------------=

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=3Djoin.php&p=3Dsourceforge&CID=3D=
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....

Re: [Astlinux-users] 0.4 branch svn 692 images available

[Darrick H. <dha...@dj...>]

Darrick Hartman wrote:
> Just wanted to announce a new series of images built from branch 0.4.  
> SVN revision 692 includes several minor enhancements.
>
> 1).  Updates to the web interface to reflect the mailing list change.
> 2).  Change to dnsmasq init script.  Now possible to restart dnsmasq 
> without recreating the dnsmasq.conf file.
> 3).  Version bump on wanpipe--someone please report back on wanpipe 
> results.  I don't have the hardware to do the testing.
>
> If there are no major issues, expect what is in this version to become 
> 0.4.5 within the next week
Here's the link to the images:

http://www.djhsolutions.com/astlinux

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

[Astlinux-users] 0.4 branch svn 692 images available

[Darrick H. <dha...@dj...>]

Just wanted to announce a new series of images built from branch 0.4.  
SVN revision 692 includes several minor enhancements.

1).  Updates to the web interface to reflect the mailing list change.
2).  Change to dnsmasq init script.  Now possible to restart dnsmasq 
without recreating the dnsmasq.conf file.
3).  Version bump on wanpipe--someone please report back on wanpipe 
results.  I don't have the hardware to do the testing.

If there are no major issues, expect what is in this version to become 
0.4.5 within the next week.

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] Compile errors

[Darrick H. <dha...@dj...>]

Manuel Dominguez wrote:
> Darrick,
>
> Thanks for your explanation. I need trunk because the NIC cards in my
> motherboard are not supported in 0.4. I am trying to get enough information
> about trunk to be ready when Kristian finishes it and to test my new
> motherboard with last version. I will try to give information to all about
> my problems and tests. I am very new in linux but during my tests I am
> learning a lot of things about builroot, packages, compile... Sorry if I
> make many trivial questions.
>
> In reference to compile trunk in this moment I don’t have problems. My
> problem is how to boot from my compact flash. By the moment I can use the
> iso file burning a DVD or CD and start in livecd. 
> Following the procedure that livecd use to install image in hard drive, I
> have found the file linuxrc. I have tried to follow all steps in this file
> but I think something is wrong. I don’t know!!
>   
We may be able to add support for that nic to 0.4 as long as it is 
supported in the 2.6.16.12 kernel. I really don't want to bump the 
kernel version in the 0.4 branch. You can look back in trunk svn changes 
and see where Kristian removed the grub files. It's possible to add 
those back in on your local svn copy and compile using grub as a target 
instead of the iso stuff.

Darrick

> As was mentioned before, there are major changes going on in trunk.  
> Some things will be broken from time to time.
>
> Kristian is removing grub from trunk.  He's moving to a system that will 
> take a bit for the transition, but will be better in the long run for 
> upgrades.  He's mentioned this in the past (you may have seen mention of 
> runnix).  The reason the image you built hangs at the grub menu, it's 
> because those components were removed.  Unless you want to be on the 
> cutting edge, you will be happier running the 0.4 branch (although I'm 
> sure Kristian appreciates any help he can get with testing and debugging).
>   



-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] Compile errors

[Manuel D. <man...@te...>]

Darrick,

Thanks for your explanation. I need trunk because the NIC cards in my
motherboard are not supported in 0.4. I am trying to get enough =
information
about trunk to be ready when Kristian finishes it and to test my new
motherboard with last version. I will try to give information to all =
about
my problems and tests. I am very new in linux but during my tests I am
learning a lot of things about builroot, packages, compile... Sorry if I
make many trivial questions.

In reference to compile trunk in this moment I don=92t have problems. My
problem is how to boot from my compact flash. By the moment I can use =
the
iso file burning a DVD or CD and start in livecd.=20
Following the procedure that livecd use to install image in hard drive, =
I
have found the file linuxrc. I have tried to follow all steps in this =
file
but I think something is wrong. I don=92t know!!

Regards,

--
Manuel =20

-----Mensaje original-----
De: ast...@li...
[mailto:ast...@li...] En nombre de =
Darrick
Hartman
Enviado el: s=E1bado, 03 de marzo de 2007 19:04
Para: AstLinux Users Mailing List
Asunto: Re: [Astlinux-users] Compile errors

Manuel Dominguez wrote:
> Kristian,
>
> I have selected "bootloader syslinux" and "create bootable iso". With =
this
> iso (DVD) my system boots. With livecd option works without problems
> starting asterisk and all the system but when I select to install to =
my
> compact flash I receive the next data:
>
> Created Ramdisk successfully=20
> 56200+0 records in
> 56200+0 records out
> Installation successful!! Restart machine.
> Kernel panic-not syncing: Attempted to kill init.
> =20
> When system restart appears "disk boot failure".
>
> It's necessary to prepare before compact flash? What is the actual
procedure
> to install Astlinux in a compact flash? =20
>
> If I select "bootloader grub" and run makeimage procedure my compact =
flash
> boot but remains in grub menu waiting for parameters to boot.
>
> Not all are problems. When start with livecd option the new kernel =
detect
my
> RealteK RTL8110SC!! Thanks Kristian.
>  =20
Manuel,

As was mentioned before, there are major changes going on in trunk. =20
Some things will be broken from time to time.

Kristian is removing grub from trunk.  He's moving to a system that will =

take a bit for the transition, but will be better in the long run for=20
upgrades.  He's mentioned this in the past (you may have seen mention of =

runnix).  The reason the image you built hangs at the grub menu, it's=20
because those components were removed.  Unless you want to be on the=20
cutting edge, you will be happier running the 0.4 branch (although I'm=20
sure Kristian appreciates any help he can get with testing and =
debugging).

Darrick

--=20
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com


-------------------------------------------------------------------------=

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=3Djoin.php&p=3Dsourceforge&CID=3D=
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....

Re: [Astlinux-users] Compile errors

[Darrick H. <dha...@dj...>]

Manuel Dominguez wrote:
> Kristian,
>
> I have selected "bootloader syslinux" and "create bootable iso". With this
> iso (DVD) my system boots. With livecd option works without problems
> starting asterisk and all the system but when I select to install to my
> compact flash I receive the next data:
>
> Created Ramdisk successfully 
> 56200+0 records in
> 56200+0 records out
> Installation successful!! Restart machine.
> Kernel panic-not syncing: Attempted to kill init.
>  
> When system restart appears "disk boot failure".
>
> It's necessary to prepare before compact flash? What is the actual procedure
> to install Astlinux in a compact flash?  
>
> If I select "bootloader grub" and run makeimage procedure my compact flash
> boot but remains in grub menu waiting for parameters to boot.
>
> Not all are problems. When start with livecd option the new kernel detect my
> RealteK RTL8110SC!! Thanks Kristian.
>   
Manuel,

As was mentioned before, there are major changes going on in trunk.  
Some things will be broken from time to time.

Kristian is removing grub from trunk.  He's moving to a system that will 
take a bit for the transition, but will be better in the long run for 
upgrades.  He's mentioned this in the past (you may have seen mention of 
runnix).  The reason the image you built hangs at the grub menu, it's 
because those components were removed.  Unless you want to be on the 
cutting edge, you will be happier running the 0.4 branch (although I'm 
sure Kristian appreciates any help he can get with testing and debugging).

Darrick

-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com

Re: [Astlinux-users] Compile errors

[Manuel D. <man...@te...>]

Kristian,

I have selected "bootloader syslinux" and "create bootable iso". With this
iso (DVD) my system boots. With livecd option works without problems
starting asterisk and all the system but when I select to install to my
compact flash I receive the next data:

Created Ramdisk successfully 
56200+0 records in
56200+0 records out
Installation successful!! Restart machine.
Kernel panic-not syncing: Attempted to kill init.
 
When system restart appears "disk boot failure".

It's necessary to prepare before compact flash? What is the actual procedure
to install Astlinux in a compact flash?  

If I select "bootloader grub" and run makeimage procedure my compact flash
boot but remains in grub menu waiting for parameters to boot.

Not all are problems. When start with livecd option the new kernel detect my
RealteK RTL8110SC!! Thanks Kristian.

--
Manuel


-----Mensaje original-----
De: ast...@li...
[mailto:ast...@li...] En nombre de Manuel
Dominguez
Enviado el: viernes, 02 de marzo de 2007 19:17
Para: 'AstLinux Users Mailing List'
Asunto: Re: [Astlinux-users] Compile errors

Thanks Kristian,

Yes, with zlib and nasm Astlinux trunk compile without errors. My new
problem is with the image. I have used makeimage.sh like in 0.4 but the
image file not boot. I have used physdiskwrite.exe to write to compact flash
but my system only say Disk boot failure. Some ideas?

Regards,

Manuel

 

-----Mensaje original-----
De: ast...@li...
[mailto:ast...@li...] En nombre de Kristian
Kielhofner
Enviado el: viernes, 02 de marzo de 2007 18:12
Para: AstLinux Users Mailing List
Asunto: Re: [Astlinux-users] Compile errors

On 3/2/07, Manuel Dominguez <man...@te...> wrote:
> Thank you Kristian, you find the problem. This problem disappears but
> appears another one with squashfs. Sorry, I don't like to send so many
> questions but it's the first time that I use buildroot:
>
>
>
> toolchain/patch-kernel.sh /home/astlinux/trunk/build_i586/squashfs3.2-r2
> target/squashfs/ squashfs\*.patch
> touch /home/astlinux/trunk/build_i586/squashfs3.2-r2/.unpacked
> make -j2 -C /home/astlinux/trunk/build_i586/squashfs3.2-r2/squashfs-tools;
> make[1]: Entering directory
> `/home/astlinux/trunk/build_i586/squashfs3.2-r2/squashfs-tools'
> cc -I. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -O2   -c -o mksquashfs.o
> mksquashfs.c
> cc -I. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -O2   -c -o read_fs.o
> read_fs.c
> mksquashfs.c:38:18: zlib.h: No such file or directory
> read_fs.c:35:18: zlib.h: No such file or directory
> read_fs.c: In function `read_block':
> read_fs.c:88: error: `Z_OK' undeclared (first use in this function)
> read_fs.c:88: error: (Each undeclared identifier is reported only once
> read_fs.c:88: error: for each function it appears in.)
> read_fs.c:89: error: `Z_MEM_ERROR' undeclared (first use in this function)
> read_fs.c:91: error: `Z_BUF_ERROR' undeclared (first use in this function)
> mksquashfs.c:562: error: syntax error before '*' token
> mksquashfs.c: In function `mangle2':
> mksquashfs.c:566: error: `z_stream' undeclared (first use in this
function)
> mksquashfs.c:566: error: (Each undeclared identifier is reported only once
> mksquashfs.c:566: error: for each function it appears in.)
> mksquashfs.c:566: error: `stream' undeclared (first use in this function)
> mksquashfs.c:566: error: `strm' undeclared (first use in this function)
> mksquashfs.c:568: error: `uncompressed' undeclared (first use in
>

Manuel,

  You need to install the zlib development package on your host.


-- 
Kristian Kielhofner

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


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

Re: [Astlinux-users] RFC: IMPORTANT astfw changes

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

On Mar 2, 2007, at 3:12 PM, Kristian Kielhofner wrote:

>   In this scenario, the NAT code in the Linux kernel will attempt to
> use port 5060 on the external interface of the AstLinux machine.  It
> does this for three reasons:
>
> 1)  5060 is above 1023
> 2)  It defaults to using the same port that is used on the internal
> side (if possible)
> 3)  It doesn't know that there is something listening on that port  
> locally.

Kristian,

I don't understand your #3.
If you want your asterisk box to 'listen' on 5060, you have to port  
forward 5060 to your asterisk box (192.168.1.10)

using "ipnat" on FreeBSD
rdr sis1 0/0 port 5060 -> 192.168.1.10 port 5060 udp

This would make port 5060 on the WAN interface unavailable, when a  
SIP phone registered out the WAN, correct?

I instincts say your suggested changes are unnecessary,

but then again, I use m0n0wall. <smile>

Lonnie

[Astlinux-users] RFC: IMPORTANT astfw changes

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

Hello Everyone,

  I know that it is a Friday but I have recently discovered an
important issue in AstLinux.

  Many people use AstLinux machines as both router/firewalls and
Asterisk machines.  This can be a problem if you try to use a SIP
device behind the AstLinux machine IF it registers to a SIP endpoint
on the other side of local nat:
                         (NAT)
SIP Phone -> AstLinux box -> SIP Server

  This does not effect setups where the SIP Phone registers to
Asterisk and Asterisk maintains the connection to the SIP Server.

  In this scenario, the NAT code in the Linux kernel will attempt to
use port 5060 on the external interface of the AstLinux machine.  It
does this for three reasons:

1)  5060 is above 1023
2)  It defaults to using the same port that is used on the internal
side (if possible)
3)  It doesn't know that there is something listening on that port locally.

  This has the effect of blocking access (via the external interface)
to the instance of Asterisk that is running on the AstLinux machine.

BAD!

  The solution is to use the --to-ports argument for the MASQUERADE
target on tcp and udp connections:

what was:

iptables -t nat -A POSTROUTING -s $IPBASE.0/$INTNM -o $EXTIF -j MASQUERADE

is now:
iptables -t nat -A POSTROUTING -s $IPBASE.0/$INTNM -o $EXTIF -p udp -j
MASQUERADE --to-ports $MASQPORTS
iptables -t nat -A POSTROUTING -s $IPBASE.0/$INTNM -o $EXTIF -p tcp -j
MASQUERADE --to-ports $MASQPORTS
iptables -t nat -A POSTROUTING -s $IPBASE.0/$INTNM -o $EXTIF -j MASQUERADE

  This configuration will masquerade connections on the external
interface just like the old example.  The only difference is that on
tcp and udp connections it will only use the ports defined by
MASQPORTS for the outgoing port number on the external interface.

  I have been using MASQPORTS=30000-60000 and it has been working
quite well.  I am thinking that this should be the default in
AstLinux.  The only problem is that #2 (from above) is there for a
reason.  Some applications need to use the same port number.  I have
yet to run into such an application, but you never know...

  Should MASQPORTS=30000-60000 be default on new AstLinux systems?

Thanks!

-- 
Kristian Kielhofner

Re: [Astlinux-users] Compile errors

[Manuel D. <man...@te...>]

Thanks Kristian,

Yes, with zlib and nasm Astlinux trunk compile without errors. My new
problem is with the image. I have used makeimage.sh like in 0.4 but the
image file not boot. I have used physdiskwrite.exe to write to compact flash
but my system only say Disk boot failure. Some ideas?

Regards,

Manuel

 

-----Mensaje original-----
De: ast...@li...
[mailto:ast...@li...] En nombre de Kristian
Kielhofner
Enviado el: viernes, 02 de marzo de 2007 18:12
Para: AstLinux Users Mailing List
Asunto: Re: [Astlinux-users] Compile errors

On 3/2/07, Manuel Dominguez <man...@te...> wrote:
> Thank you Kristian, you find the problem. This problem disappears but
> appears another one with squashfs. Sorry, I don't like to send so many
> questions but it's the first time that I use buildroot:
>
>
>
> toolchain/patch-kernel.sh /home/astlinux/trunk/build_i586/squashfs3.2-r2
> target/squashfs/ squashfs\*.patch
> touch /home/astlinux/trunk/build_i586/squashfs3.2-r2/.unpacked
> make -j2 -C /home/astlinux/trunk/build_i586/squashfs3.2-r2/squashfs-tools;
> make[1]: Entering directory
> `/home/astlinux/trunk/build_i586/squashfs3.2-r2/squashfs-tools'
> cc -I. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -O2   -c -o mksquashfs.o
> mksquashfs.c
> cc -I. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -O2   -c -o read_fs.o
> read_fs.c
> mksquashfs.c:38:18: zlib.h: No such file or directory
> read_fs.c:35:18: zlib.h: No such file or directory
> read_fs.c: In function `read_block':
> read_fs.c:88: error: `Z_OK' undeclared (first use in this function)
> read_fs.c:88: error: (Each undeclared identifier is reported only once
> read_fs.c:88: error: for each function it appears in.)
> read_fs.c:89: error: `Z_MEM_ERROR' undeclared (first use in this function)
> read_fs.c:91: error: `Z_BUF_ERROR' undeclared (first use in this function)
> mksquashfs.c:562: error: syntax error before '*' token
> mksquashfs.c: In function `mangle2':
> mksquashfs.c:566: error: `z_stream' undeclared (first use in this
function)
> mksquashfs.c:566: error: (Each undeclared identifier is reported only once
> mksquashfs.c:566: error: for each function it appears in.)
> mksquashfs.c:566: error: `stream' undeclared (first use in this function)
> mksquashfs.c:566: error: `strm' undeclared (first use in this function)
> mksquashfs.c:568: error: `uncompressed' undeclared (first use in
>

Manuel,

  You need to install the zlib development package on your host.


-- 
Kristian Kielhofner

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

Re: [Astlinux-users] Compile errors

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

On 3/2/07, Manuel Dominguez <man...@te...> wrote:
> Thank you Kristian, you find the problem. This problem disappears but
> appears another one with squashfs. Sorry, I don't like to send so many
> questions but it's the first time that I use buildroot:
>
>
>
> toolchain/patch-kernel.sh /home/astlinux/trunk/build_i586/squashfs3.2-r2
> target/squashfs/ squashfs\*.patch
> touch /home/astlinux/trunk/build_i586/squashfs3.2-r2/.unpacked
> make -j2 -C /home/astlinux/trunk/build_i586/squashfs3.2-r2/squashfs-tools;
> make[1]: Entering directory
> `/home/astlinux/trunk/build_i586/squashfs3.2-r2/squashfs-tools'
> cc -I. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -O2   -c -o mksquashfs.o
> mksquashfs.c
> cc -I. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -O2   -c -o read_fs.o
> read_fs.c
> mksquashfs.c:38:18: zlib.h: No such file or directory
> read_fs.c:35:18: zlib.h: No such file or directory
> read_fs.c: In function `read_block':
> read_fs.c:88: error: `Z_OK' undeclared (first use in this function)
> read_fs.c:88: error: (Each undeclared identifier is reported only once
> read_fs.c:88: error: for each function it appears in.)
> read_fs.c:89: error: `Z_MEM_ERROR' undeclared (first use in this function)
> read_fs.c:91: error: `Z_BUF_ERROR' undeclared (first use in this function)
> mksquashfs.c:562: error: syntax error before '*' token
> mksquashfs.c: In function `mangle2':
> mksquashfs.c:566: error: `z_stream' undeclared (first use in this function)
> mksquashfs.c:566: error: (Each undeclared identifier is reported only once
> mksquashfs.c:566: error: for each function it appears in.)
> mksquashfs.c:566: error: `stream' undeclared (first use in this function)
> mksquashfs.c:566: error: `strm' undeclared (first use in this function)
> mksquashfs.c:568: error: `uncompressed' undeclared (first use in
>

Manuel,

  You need to install the zlib development package on your host.


-- 
Kristian Kielhofner