astlinux-devel Mailing List for AstLinux (Page 2)

Darrick Hartman wrote:
> David Kerr wrote:
>   
>> Found a bug building generic i586 with serial console. If you select 
>> this build option for target device in menuconfig then the 
>> astlinux-0.6-xxxx.run.conf file contains the line...
>>
>> KCMD="root=/dev/ram0 rw init=/linuxrc console=ttyS0,19200n8 
>> astlinux=geni586 astimg=astlinux-0.6-2415.run astkd=/dev/sda1 astlive 
>> ide=nodma"
>>
>> when built without serial console selected you get...
>>
>> KCMD="root=/dev/ram0 rw init=/linuxrc astlinux=geni586 
>> astimg=astlinux-0.6-2415.run astkd=auto asturw=auto astlive ide=nodma"
>>
>> Notice that the asturw= is missing and that the astkd= is pointing at 
>> /dev/sda1 instead of auto. Not surprisingly this causes problems after 
>> boot !
>>
>>
>> Can someone look into a fix please?
>>     
>
> Done.  Update your svn copy and you should be good to go.
>   

Is that needed in trunk?

-Philip

David Kerr wrote:
> Found a bug building generic i586 with serial console. If you select 
> this build option for target device in menuconfig then the 
> astlinux-0.6-xxxx.run.conf file contains the line...
> 
> KCMD="root=/dev/ram0 rw init=/linuxrc console=ttyS0,19200n8 
> astlinux=geni586 astimg=astlinux-0.6-2415.run astkd=/dev/sda1 astlive 
> ide=nodma"
> 
> when built without serial console selected you get...
> 
> KCMD="root=/dev/ram0 rw init=/linuxrc astlinux=geni586 
> astimg=astlinux-0.6-2415.run astkd=auto asturw=auto astlive ide=nodma"
> 
> Notice that the asturw= is missing and that the astkd= is pointing at 
> /dev/sda1 instead of auto. Not surprisingly this causes problems after 
> boot !
> 
> 
> Can someone look into a fix please?

Done.  Update your svn copy and you should be good to go.

Found a bug building generic i586 with serial console. If you select this
build option for target device in menuconfig then the
astlinux-0.6-xxxx.run.conf file contains the line...
KCMD="root=/dev/ram0 rw init=/linuxrc console=ttyS0,19200n8 astlinux=geni586
astimg=astlinux-0.6-2415.run astkd=/dev/sda1 astlive ide=nodma"

when built without serial console selected you get...

KCMD="root=/dev/ram0 rw init=/linuxrc astlinux=geni586
astimg=astlinux-0.6-2415.run astkd=auto asturw=auto astlive ide=nodma"

Notice that the asturw= is missing and that the astkd= is pointing at
/dev/sda1 instead of auto. Not surprisingly this causes problems after boot
!


Can someone look into a fix please?

Thanks
David

The problem is resolved... a build from scratch was required.

I'm running 2420 without any issues.

-Philip


Philip A. Prindeville wrote:
> Err....  Hmmm.  "svn update -r 2412 package/openssl" I should have said.
>
> Philip A. Prindeville wrote:
>   
>> If you're going to build trunk, do:
>>
>> svn update
>> svn revert -r 2397 package/openssl
>> make ...
>>
>> for now.  I wanted to checkpoint my work, as I've done a partial bump to 
>> openssl-0.9.8j from 'i'.
>>
>> There is still some damage, and I suspect it's from 
>> non-cross-compilation friendly makefiles.
>>
>> Still investigating.
>>
>> -Philip
>>   
>>     

That's right, most newer cameras have it built in. But I've got one that is
several years old and its motion detection is passive infrared based, with a
separate sensor. The "motion" has to be pretty close to the camera for it to
trigger and for my application did not work (would not register a car
pulling into front drive for example).  So I have to resort to a s/w
solution (or buy a new camera, which is a couple of hundred dollars at
least).
For my application I only have the one camera, and it is network based.  USB
cameras would almost certainly increase CPU load, which I have no interest
in doing.

David

On Mon, Jan 26, 2009 at 1:43 AM, Philip A. Prindeville <
phi...@re...> wrote:

> Most PoE MPEG-4 cameras have motion detection built in, since it's a
> degenerate function of X-frame calculation, right?
>
> -Philip
>
>
>
> David Kerr wrote:
>
>> Do you think it is possible to compile the Motion package for astlinux? (
>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome )
>>
>> According to the instructions it needs the following libraries:  libm,
>> libresolv, libdl, libpthread, libc, ld-linux, libcrypt, libnsl, libjpeg,
>> libz   and it looks like astlinux has all except ld-linux. I'm guessing that
>> this is replaced with ld-uClibc.  So, question is how hard would it be to
>> get Motion to run on astlinux?
>>
>> Thanks,
>> David
>>
>
>
>

And how common is having only one camera?

-Philip


David Kerr wrote:
> That was my first thought... but I compiled it on my CentOS system and 
> had it monitoring a 320x240 mjpeg streaming from a panasonic 
> network-attached camera and the Motion process is using 2% of my CPU. 
> It may use more during "motion" in the image, but just monitoring is 
> using very little.
>
> David
>
> On Sun, Jan 25, 2009 at 9:22 PM, Darrick Hartman 
> <dha...@dj... <mailto:dha...@dj...>> wrote:
>
>     David,
>
>     Motion detection is a VERY cpu intensive operation.  Not a good
>     fit for an Astlinux type device.
>
>     Darrick
>
>
>     David Kerr wrote:
>
>         Do you think it is possible to compile the Motion package for
>         astlinux? ( http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome )
>
>         According to the instructions it needs the following
>         libraries:  libm, libresolv, libdl, libpthread, libc,
>         ld-linux, libcrypt, libnsl, libjpeg, libz   and it looks like
>         astlinux has all except ld-linux. I'm guessing that this is
>         replaced with ld-uClibc.  So, question is how hard would it be
>         to get Motion to run on astlinux?
>
>         Thanks,
>         David
>
>

Most PoE MPEG-4 cameras have motion detection built in, since it's a 
degenerate function of X-frame calculation, right?

-Philip


David Kerr wrote:
> Do you think it is possible to compile the Motion package for 
> astlinux? ( http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome )
>
> According to the instructions it needs the following libraries:  libm, 
> libresolv, libdl, libpthread, libc, ld-linux, libcrypt, 
> libnsl, libjpeg, libz   and it looks like astlinux has all except 
> ld-linux. I'm guessing that this is replaced with ld-uClibc.  So, 
> question is how hard would it be to get Motion to run on astlinux?
>
> Thanks,
> David

Philip A. Prindeville wrote:
> I've updated a couple of hours ago, and building from scratch I see:
>
> ...
> make[1]: Entering directory `/home/philipp/0.6/build_i586/linux-2.6.20.21-astlinux'
>   CHK     include/linux/version.h
>   CHK     include/linux/utsrelease.h
>   HOSTCC  scripts/genksyms/genksyms.o
>   SHIPPED scripts/genksyms/lex.c
>   SHIPPED scripts/genksyms/parse.h
>   SHIPPED scripts/genksyms/keywords.c
>   CC      arch/i386/kernel/asm-offsets.s
>   SHIPPED scripts/genksyms/parse.c
>   HOSTCC  scripts/genksyms/lex.o
> scripts/genksyms/lex.c:1230: warning: ‘input’ defined but not used
>   HOSTCC  scripts/genksyms/parse.o
>   HOSTLD  scripts/genksyms/genksyms
>   GEN     include/asm-i386/asm-offsets.h
>   CC      scripts/mod/empty.o
>   HOSTCC  scripts/mod/mk_elfconfig
>   HOSTCC  scripts/kallsyms
>   MKELF   scripts/mod/elfconfig.h
>   HOSTCC  scripts/mod/file2alias.o
>   HOSTCC  scripts/mod/modpost.o
>   HOSTCC  scripts/mod/sumversion.o
> scripts/mod/sumversion.c: In function ‘get_src_version’:
> scripts/mod/sumversion.c:384: error: ‘PATH_MAX’ undeclared (first use in this function)
> scripts/mod/sumversion.c:384: error: (Each undeclared identifier is reported only once
> scripts/mod/sumversion.c:384: error: for each function it appears in.)
> scripts/mod/sumversion.c:384: warning: unused variable ‘filelist’
> make[3]: *** [scripts/mod/sumversion.o] Error 1
> make[2]: *** [scripts/mod] Error 2
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [scripts] Error 2
> make[1]: Leaving directory `/home/philipp/0.6/build_i586/linux-2.6.20.21-astlinux'
> make: *** [/home/philipp/0.6/build_i586/linux-2.6.20.21-astlinux/arch/i386/boot/bzImage] Error 2
>
>
> This is on an FC9-x86_64 platform.
>
> Anyone else seeing this?
>
> -Philip
>   
Philip,

Yes I have seen this same issue while building the 0.6 branch.  I 
*temporarily* fixed it by *manually* adding "#include <limits.h>" to the 
headers section of the scripts/mod/sumversion.c linux source file.  This 
should probably get turned into a patch.

-Steve

I've updated a couple of hours ago, and building from scratch I see:

...
make[1]: Entering directory `/home/philipp/0.6/build_i586/linux-2.6.20.21-astlinux'
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  HOSTCC  scripts/genksyms/genksyms.o
  SHIPPED scripts/genksyms/lex.c
  SHIPPED scripts/genksyms/parse.h
  SHIPPED scripts/genksyms/keywords.c
  CC      arch/i386/kernel/asm-offsets.s
  SHIPPED scripts/genksyms/parse.c
  HOSTCC  scripts/genksyms/lex.o
scripts/genksyms/lex.c:1230: warning: ‘input’ defined but not used
  HOSTCC  scripts/genksyms/parse.o
  HOSTLD  scripts/genksyms/genksyms
  GEN     include/asm-i386/asm-offsets.h
  CC      scripts/mod/empty.o
  HOSTCC  scripts/mod/mk_elfconfig
  HOSTCC  scripts/kallsyms
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/file2alias.o
  HOSTCC  scripts/mod/modpost.o
  HOSTCC  scripts/mod/sumversion.o
scripts/mod/sumversion.c: In function ‘get_src_version’:
scripts/mod/sumversion.c:384: error: ‘PATH_MAX’ undeclared (first use in this function)
scripts/mod/sumversion.c:384: error: (Each undeclared identifier is reported only once
scripts/mod/sumversion.c:384: error: for each function it appears in.)
scripts/mod/sumversion.c:384: warning: unused variable ‘filelist’
make[3]: *** [scripts/mod/sumversion.o] Error 1
make[2]: *** [scripts/mod] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [scripts] Error 2
make[1]: Leaving directory `/home/philipp/0.6/build_i586/linux-2.6.20.21-astlinux'
make: *** [/home/philipp/0.6/build_i586/linux-2.6.20.21-astlinux/arch/i386/boot/bzImage] Error 2


This is on an FC9-x86_64 platform.

Anyone else seeing this?

-Philip

That was my first thought... but I compiled it on my CentOS system and had
it monitoring a 320x240 mjpeg streaming from a panasonic network-attached
camera and the Motion process is using 2% of my CPU. It may use more during
"motion" in the image, but just monitoring is using very little.
David

On Sun, Jan 25, 2009 at 9:22 PM, Darrick Hartman
<dha...@dj...>wrote:

> David,
>
> Motion detection is a VERY cpu intensive operation.  Not a good fit for an
> Astlinux type device.
>
> Darrick
>
>
> David Kerr wrote:
>
>> Do you think it is possible to compile the Motion package for astlinux? (
>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome )
>>
>> According to the instructions it needs the following libraries:  libm,
>> libresolv, libdl, libpthread, libc, ld-linux, libcrypt, libnsl, libjpeg,
>> libz   and it looks like astlinux has all except ld-linux. I'm guessing that
>> this is replaced with ld-uClibc.  So, question is how hard would it be to
>> get Motion to run on astlinux?
>>
>> Thanks,
>> David
>>
>
>

David,

Motion detection is a VERY cpu intensive operation.  Not a good fit for 
an Astlinux type device.

Darrick

David Kerr wrote:
> Do you think it is possible to compile the Motion package for astlinux? 
> ( http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome )
> 
> According to the instructions it needs the following libraries:  libm, 
> libresolv, libdl, libpthread, libc, ld-linux, libcrypt, 
> libnsl, libjpeg, libz   and it looks like astlinux has all except 
> ld-linux. I'm guessing that this is replaced with ld-uClibc.  So, 
> question is how hard would it be to get Motion to run on astlinux?
> 
> Thanks,
> David

Do you think it is possible to compile the Motion package for astlinux? (
http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome )

According to the instructions it needs the following libraries:  libm,
libresolv, libdl, libpthread, libc, ld-linux, libcrypt,
libnsl, libjpeg, libz   and it looks like astlinux has all except ld-linux.
I'm guessing that this is replaced with ld-uClibc.  So, question is how hard
would it be to get Motion to run on astlinux?

Thanks,
David

Err....  Hmmm.  "svn update -r 2412 package/openssl" I should have said.

Philip A. Prindeville wrote:
> If you're going to build trunk, do:
>
> svn update
> svn revert -r 2397 package/openssl
> make ...
>
> for now.  I wanted to checkpoint my work, as I've done a partial bump to 
> openssl-0.9.8j from 'i'.
>
> There is still some damage, and I suspect it's from 
> non-cross-compilation friendly makefiles.
>
> Still investigating.
>
> -Philip
>   

If you're going to build trunk, do:

svn update
svn revert -r 2397 package/openssl
make ...

for now.  I wanted to checkpoint my work, as I've done a partial bump to 
openssl-0.9.8j from 'i'.

There is still some damage, and I suspect it's from 
non-cross-compilation friendly makefiles.

Still investigating.

-Philip

Guys,

To elaborate...

The general consensus to integrate OpenVPN with Arno was to use

TRUSTED_IF="tun+"

which basically allows all routed traffic over the OpenVPN tunnel to  
go anywhere locally.

Like you, this was not too appealing.

So, I implemented the OpenVPN subnet as another LAN subnet, with the  
same inherited Arno defaults of LAN subnets... all traffic allowed out  
through EXT_IF, all traffic allowed to the Local box and all traffic  
allowed to the DMZ.  But firewall rules can be defined to Deny (or  
limit) any of these defaults (unlike using TRUSTED_IF="tun+").

Also, by default Arno does not allow any LAN <-> LAN traffic via  
different interfaces.

If Arno supported rules to allow LAN <-> LAN traffic via different  
interfaces, that would be the way to go, but as far as I can tell Arno  
does not support this feature.  The only method LAN's can talk is via  
the INT_IF_TRUST variable, and then it is all or nothing.

Obviously, there must be an easy way for the user to access a LAN  
subnet via OpenVPN, but a choice that is 'off' by default is fine by  
me.  I was pondering this for awhile this afternoon.

Question: Given the scenario above, simply yes/no allowing OpenVPN to  
INTIF is all we need?  Note that this is no way I know to allow  
OpenVPN to access both INTIF and INT2IF without also allowing INTIF  
and INT2IF to talk directly.

I had thought about placing the OpenVPN subnet in the DMZ, more  
restrictive and rules to the LAN, but more trouble to get working from  
a user's point of view.

Lonnie


On Jan 24, 2009, at 5:58 PM, Darrick Hartman wrote:

> I agree.  Off by default, but perhaps a checkbox or flag which would
> allow routing to the default LAN if set.
>
> Darrick
>
>
> Philip A. Prindeville wrote:
>> Not sure how I feel about this.  First rule of security is  
>> "everything
>> that is not explicitly permitted is forbidden".
>>
>>
>> abe...@us... wrote:
>>> Revision: 2407
>>>          http://astlinux.svn.sourceforge.net/astlinux/?rev=2407&view=rev
>>> Author:   abelbeck
>>> Date:     2009-01-24 21:21:51 +0000 (Sat, 24 Jan 2009)
>>>
>>> Log Message:
>>> -----------
>>> Automatically allow OpenVPN subnet to 1st LAN subnet, if it is  
>>> defined
>>>
>>> Modified Paths:
>>> --------------
>>>    trunk/package/arno-fw/arnofw.wrapper
>>>
>>> Modified: trunk/package/arno-fw/arnofw.wrapper
>>> ===================================================================
>>> --- trunk/package/arno-fw/arnofw.wrapper	2009-01-24 04:01:53 UTC  
>>> (rev 2406)
>>> +++ trunk/package/arno-fw/arnofw.wrapper	2009-01-24 21:21:51 UTC  
>>> (rev 2407)
>>> @@ -106,6 +106,13 @@
>>>       ovpnIF="$OVPN_DEV"
>>>     fi
>>>     addINTERNALnet "$ovpnIF" "$ovpnIP" "$ovpnNM"
>>> +    # Automatically allow OpenVPN subnet to 1st LAN subnet, if it  
>>> is defined
>>> +    for intf in $INT_IF; do
>>> +      if [ "$intf" = "$INTIF" ]; then
>>> +        INT_IF_TRUST="$INTIF $ovpnIF"
>>> +        break;
>>> +      fi
>>> +    done
>>>   else
>>>     # Failsafe if /mnt/kd/openvpn/openvpn.conf is used
>>>     # and OVPN_SERVER is not defined.
>>>
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>
>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr... 
>> .
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr... 
> .
>
>

OK,

Lonnie

On Jan 24, 2009, at 5:58 PM, Darrick Hartman wrote:

> I agree.  Off by default, but perhaps a checkbox or flag which would
> allow routing to the default LAN if set.
>
> Darrick
>
>
> Philip A. Prindeville wrote:
>> Not sure how I feel about this.  First rule of security is  
>> "everything
>> that is not explicitly permitted is forbidden".
>>
>>
>> abe...@us... wrote:
>>> Revision: 2407
>>>          http://astlinux.svn.sourceforge.net/astlinux/?rev=2407&view=rev
>>> Author:   abelbeck
>>> Date:     2009-01-24 21:21:51 +0000 (Sat, 24 Jan 2009)
>>>
>>> Log Message:
>>> -----------
>>> Automatically allow OpenVPN subnet to 1st LAN subnet, if it is  
>>> defined
>>>
>>> Modified Paths:
>>> --------------
>>>    trunk/package/arno-fw/arnofw.wrapper
>>>
>>> Modified: trunk/package/arno-fw/arnofw.wrapper
>>> ===================================================================
>>> --- trunk/package/arno-fw/arnofw.wrapper	2009-01-24 04:01:53 UTC  
>>> (rev 2406)
>>> +++ trunk/package/arno-fw/arnofw.wrapper	2009-01-24 21:21:51 UTC  
>>> (rev 2407)
>>> @@ -106,6 +106,13 @@
>>>       ovpnIF="$OVPN_DEV"
>>>     fi
>>>     addINTERNALnet "$ovpnIF" "$ovpnIP" "$ovpnNM"
>>> +    # Automatically allow OpenVPN subnet to 1st LAN subnet, if it  
>>> is defined
>>> +    for intf in $INT_IF; do
>>> +      if [ "$intf" = "$INTIF" ]; then
>>> +        INT_IF_TRUST="$INTIF $ovpnIF"
>>> +        break;
>>> +      fi
>>> +    done
>>>   else
>>>     # Failsafe if /mnt/kd/openvpn/openvpn.conf is used
>>>     # and OVPN_SERVER is not defined.
>>>
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>
>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr... 
>> .
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr... 
> .
>
>

I agree.  Off by default, but perhaps a checkbox or flag which would 
allow routing to the default LAN if set.

Darrick


Philip A. Prindeville wrote:
> Not sure how I feel about this.  First rule of security is "everything 
> that is not explicitly permitted is forbidden".
> 
> 
> abe...@us... wrote:
>> Revision: 2407
>>           http://astlinux.svn.sourceforge.net/astlinux/?rev=2407&view=rev
>> Author:   abelbeck
>> Date:     2009-01-24 21:21:51 +0000 (Sat, 24 Jan 2009)
>>
>> Log Message:
>> -----------
>> Automatically allow OpenVPN subnet to 1st LAN subnet, if it is defined
>>
>> Modified Paths:
>> --------------
>>     trunk/package/arno-fw/arnofw.wrapper
>>
>> Modified: trunk/package/arno-fw/arnofw.wrapper
>> ===================================================================
>> --- trunk/package/arno-fw/arnofw.wrapper	2009-01-24 04:01:53 UTC (rev 2406)
>> +++ trunk/package/arno-fw/arnofw.wrapper	2009-01-24 21:21:51 UTC (rev 2407)
>> @@ -106,6 +106,13 @@
>>        ovpnIF="$OVPN_DEV"
>>      fi
>>      addINTERNALnet "$ovpnIF" "$ovpnIP" "$ovpnNM"
>> +    # Automatically allow OpenVPN subnet to 1st LAN subnet, if it is defined
>> +    for intf in $INT_IF; do
>> +      if [ "$intf" = "$INTIF" ]; then
>> +        INT_IF_TRUST="$INTIF $ovpnIF"
>> +        break;
>> +      fi
>> +    done
>>    else
>>      # Failsafe if /mnt/kd/openvpn/openvpn.conf is used
>>      # and OVPN_SERVER is not defined.
>>
>>
>>   
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Not sure how I feel about this.  First rule of security is "everything 
that is not explicitly permitted is forbidden".


abe...@us... wrote:
> Revision: 2407
>           http://astlinux.svn.sourceforge.net/astlinux/?rev=2407&view=rev
> Author:   abelbeck
> Date:     2009-01-24 21:21:51 +0000 (Sat, 24 Jan 2009)
>
> Log Message:
> -----------
> Automatically allow OpenVPN subnet to 1st LAN subnet, if it is defined
>
> Modified Paths:
> --------------
>     trunk/package/arno-fw/arnofw.wrapper
>
> Modified: trunk/package/arno-fw/arnofw.wrapper
> ===================================================================
> --- trunk/package/arno-fw/arnofw.wrapper	2009-01-24 04:01:53 UTC (rev 2406)
> +++ trunk/package/arno-fw/arnofw.wrapper	2009-01-24 21:21:51 UTC (rev 2407)
> @@ -106,6 +106,13 @@
>        ovpnIF="$OVPN_DEV"
>      fi
>      addINTERNALnet "$ovpnIF" "$ovpnIP" "$ovpnNM"
> +    # Automatically allow OpenVPN subnet to 1st LAN subnet, if it is defined
> +    for intf in $INT_IF; do
> +      if [ "$intf" = "$INTIF" ]; then
> +        INT_IF_TRUST="$INTIF $ovpnIF"
> +        break;
> +      fi
> +    done
>    else
>      # Failsafe if /mnt/kd/openvpn/openvpn.conf is used
>      # and OVPN_SERVER is not defined.
>
>
>   

Philip or Lonnie,

Can one of you commit this to 0.6?  I'm skiing for the weekend. 
------Original Message------
From: ppr...@us...
To: ast...@li...
ReplyTo: ast...@li...
Subject: [Astlinux-commits] SF.net SVN: astlinux:[2397]trunk/package/dnsmasq/dnsmasq.init
Sent: Jan 23, 2009 6:17 PM

Revision: 2397
          http://astlinux.svn.sourceforge.net/astlinux/?rev=2397&view=rev
Author:   pprindeville
Date:     2009-01-24 00:17:28 +0000 (Sat, 24 Jan 2009)

Log Message:
-----------
Do the right thing if the hostname contains both the unqualified and fqdn names.

Modified Paths:
--------------
    trunk/package/dnsmasq/dnsmasq.init

Modified: trunk/package/dnsmasq/dnsmasq.init
===================================================================
--- trunk/package/dnsmasq/dnsmasq.init	2009-01-23 18:21:35 UTC (rev 2396)
+++ trunk/package/dnsmasq/dnsmasq.init	2009-01-24 00:17:28 UTC (rev 2397)
@@ -132,7 +132,8 @@
   
   IFS=$'\n'
   for i in $STATICHOSTS; do              
-    name="`echo "$i" | awk -F~ '{ print $1; }'`"
+    # might have fqdn<space>hostname, etc.
+    name="`echo "$i" | awk -F~ '{ print $1; }' | awk -F' ' '{ print $1; }'`"
     ip="`echo "$i" | awk -F~ '{ print $2; }'`"
     mac="`echo "$i" | awk -F~ '{ print $3; }'`"
     if [ -n "$name" -a -n "$ip" -a -n "$mac" ]; then


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Astlinux-commits mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-commits

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


Sent from my BlackBerry® wireless device from U.S. Cellular

You mean like the:

ifeq ($(strip $(BR2_PACKAGE_VIM)),y)
        $(SED) "s/^.*CONFIG_VI[ =].*/CONFIG_VI=n/" $(BUSYBOX_DIR)/.config
endif


that's in there now?  :-)


Darrick Hartman wrote:
> <soapbox>
> The vi/vim issue is your personal preference and not a standard Astlinux 
> option.  If you want vim enabled, then you'll either have to have a 
> special option to disable it from the busybox .config file or delete the 
> sym link before building vim.  IMHO vim is a hog and not needed on an 
> embedded system.
> </soapbox>
>
> Darrick
>
> Philip A. Prindeville wrote:
>   
>> Well, this will require some careful testing.
>>
>> Certain things like "bash" and "vi" don't play well with busybox, and we 
>> had to do things to remove links that couldn't be configured off/on as 
>> part of the package makefiles...  (perhaps the new version allows us to 
>> set these?)
>>
>> Also, Arno's firewall 1.9.0 has certain issues with busybox's modprobe 
>> and sysctl (which aren't 100% option compatible with their standalone 
>> binaries).
>>
>> -Philip
>>
>>
>> Lonnie Abelbeck wrote:
>>     
>>> Darrick,
>>>
>>> Busybox 1.12.4 looks good with your updated config. Thanks!
>>>
>>> Lonnie
>>>
>>>
>>> On Jan 23, 2009, at 12:29 PM, Darrick Hartman wrote:
>>>
>>>   
>>>       
>>>> I've updated the base busybox config.  I still need to do the initrd
>>>> version.  The cool thing is findfs is now part of busybox so we can
>>>> ditch some of the stuff from the initrd in trunk.
>>>>
>>>> We need to revisit whether we need standalone versions of certain
>>>> functions or if we want to move to busybox versions.
>>>>
>>>> Darrick
>>>>
>>>> Darrick Hartman wrote:
>>>>     
>>>>         
>>>>> Might as well keep it at 1.12.4, but update the .config.
>>>>>
>>>>> Lemme see if I can update it.
>>>>>
>>>>> Darrick
>>>>>
>>>>> Lonnie Abelbeck wrote:
>>>>>       
>>>>>           
>>>>>> Thanks Darrick, but there are problems...
>>>>>>
>>>>>> tar does not have the -z option anymore
>>>>>>
>>>>>> Does the "busybox-astlinux.config" need to be completely rebuilt for
>>>>>> 1.12.4?
>>>>>>
>>>>>> Maybe 1.10.4 is a better version?
>>>>>>
>>>>>> Lonnie
>>>>>>
>>>>>> On Jan 23, 2009, at 9:20 AM, Darrick Hartman wrote:
>>>>>>
>>>>>>         
>>>>>>             
>>>>>>> Lonnie,
>>>>>>>
>>>>>>> I bumped busybox to 1.12.4.  (can't go to 1.13.x until we go to  
>>>>>>> uClibc
>>>>>>> 0.9.30).
>>>>>>>
>>>>>>> The .config file needs to be updated to use (or not use) new  
>>>>>>> busybox
>>>>>>> features.
>>>>>>>
>>>>>>> Darrick
>>>>>>>
>>>>>>> Lonnie Abelbeck wrote:
>>>>>>>           
>>>>>>>               
>>>>>>>> Bumping this open item...
>>>>>>>>
>>>>>>>> On Dec 25, 2008, at 11:07 PM, Lonnie Abelbeck wrote:
>>>>>>>>
>>>>>>>>             
>>>>>>>>                 
>>>>>>>>> Trunk's current BusyBox v1.11.2 has a nasty 'vi' bug
>>>>>>>>>
>>>>>>>>> type 'vi', then / then RETURN
>>>>>>>>>
>>>>>>>>> Dec 25 22:03:43 pbx user.info kernel: vi[2706]: segfault at 0 ip
>>>>>>>>> 08094772 sp bfc6a89c error 4
>>>>>>>>> Dec 25 22:03:43 pbx user.info kernel:  in busybox[8048000+6c000]
>>>>>>>>>
>>>>>>>>> Supposedly, BusyBox 1.12.2 solves this problem.
>>>>>>>>>
>>>>>>>>> Lonnie

Philip,

I suggest that you build with the new options turned on, then cd into 
the build_i586/busybox directory (and build_i586/busybox_initrd) then 
run make menuconfig to review the selected options.  I enabled findfs in 
busybox which should allow us to remove it from the standalone package 
(if it works as expected).  I did NOT enable brctl but that's a 
possibility.  I have no idea how compatible it is with the standalone 
utility.

<soapbox>
The vi/vim issue is your personal preference and not a standard Astlinux 
option.  If you want vim enabled, then you'll either have to have a 
special option to disable it from the busybox .config file or delete the 
sym link before building vim.  IMHO vim is a hog and not needed on an 
embedded system.
</soapbox>

Darrick

Philip A. Prindeville wrote:
> Well, this will require some careful testing.
> 
> Certain things like "bash" and "vi" don't play well with busybox, and we 
> had to do things to remove links that couldn't be configured off/on as 
> part of the package makefiles...  (perhaps the new version allows us to 
> set these?)
> 
> Also, Arno's firewall 1.9.0 has certain issues with busybox's modprobe 
> and sysctl (which aren't 100% option compatible with their standalone 
> binaries).
> 
> -Philip
> 
> 
> Lonnie Abelbeck wrote:
>> Darrick,
>>
>> Busybox 1.12.4 looks good with your updated config. Thanks!
>>
>> Lonnie
>>
>>
>> On Jan 23, 2009, at 12:29 PM, Darrick Hartman wrote:
>>
>>   
>>> I've updated the base busybox config.  I still need to do the initrd
>>> version.  The cool thing is findfs is now part of busybox so we can
>>> ditch some of the stuff from the initrd in trunk.
>>>
>>> We need to revisit whether we need standalone versions of certain
>>> functions or if we want to move to busybox versions.
>>>
>>> Darrick
>>>
>>> Darrick Hartman wrote:
>>>     
>>>> Might as well keep it at 1.12.4, but update the .config.
>>>>
>>>> Lemme see if I can update it.
>>>>
>>>> Darrick
>>>>
>>>> Lonnie Abelbeck wrote:
>>>>       
>>>>> Thanks Darrick, but there are problems...
>>>>>
>>>>> tar does not have the -z option anymore
>>>>>
>>>>> Does the "busybox-astlinux.config" need to be completely rebuilt for
>>>>> 1.12.4?
>>>>>
>>>>> Maybe 1.10.4 is a better version?
>>>>>
>>>>> Lonnie
>>>>>
>>>>> On Jan 23, 2009, at 9:20 AM, Darrick Hartman wrote:
>>>>>
>>>>>         
>>>>>> Lonnie,
>>>>>>
>>>>>> I bumped busybox to 1.12.4.  (can't go to 1.13.x until we go to  
>>>>>> uClibc
>>>>>> 0.9.30).
>>>>>>
>>>>>> The .config file needs to be updated to use (or not use) new  
>>>>>> busybox
>>>>>> features.
>>>>>>
>>>>>> Darrick
>>>>>>
>>>>>> Lonnie Abelbeck wrote:
>>>>>>           
>>>>>>> Bumping this open item...
>>>>>>>
>>>>>>> On Dec 25, 2008, at 11:07 PM, Lonnie Abelbeck wrote:
>>>>>>>
>>>>>>>             
>>>>>>>> Trunk's current BusyBox v1.11.2 has a nasty 'vi' bug
>>>>>>>>
>>>>>>>> type 'vi', then / then RETURN
>>>>>>>>
>>>>>>>> Dec 25 22:03:43 pbx user.info kernel: vi[2706]: segfault at 0 ip
>>>>>>>> 08094772 sp bfc6a89c error 4
>>>>>>>> Dec 25 22:03:43 pbx user.info kernel:  in busybox[8048000+6c000]
>>>>>>>>
>>>>>>>> Supposedly, BusyBox 1.12.2 solves this problem.
>>>>>>>>
>>>>>>>> Lonnie
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Can someone see if they can figure out how to get tcpdump to build with 
--with-crypto?

Being able to decrypt IPSec traffic would make VPN debugging a lot easier.

Thanks,

-Philip

Well, this will require some careful testing.

Certain things like "bash" and "vi" don't play well with busybox, and we 
had to do things to remove links that couldn't be configured off/on as 
part of the package makefiles...  (perhaps the new version allows us to 
set these?)

Also, Arno's firewall 1.9.0 has certain issues with busybox's modprobe 
and sysctl (which aren't 100% option compatible with their standalone 
binaries).

-Philip


Lonnie Abelbeck wrote:
> Darrick,
>
> Busybox 1.12.4 looks good with your updated config. Thanks!
>
> Lonnie
>
>
> On Jan 23, 2009, at 12:29 PM, Darrick Hartman wrote:
>
>   
>> I've updated the base busybox config.  I still need to do the initrd
>> version.  The cool thing is findfs is now part of busybox so we can
>> ditch some of the stuff from the initrd in trunk.
>>
>> We need to revisit whether we need standalone versions of certain
>> functions or if we want to move to busybox versions.
>>
>> Darrick
>>
>> Darrick Hartman wrote:
>>     
>>> Might as well keep it at 1.12.4, but update the .config.
>>>
>>> Lemme see if I can update it.
>>>
>>> Darrick
>>>
>>> Lonnie Abelbeck wrote:
>>>       
>>>> Thanks Darrick, but there are problems...
>>>>
>>>> tar does not have the -z option anymore
>>>>
>>>> Does the "busybox-astlinux.config" need to be completely rebuilt for
>>>> 1.12.4?
>>>>
>>>> Maybe 1.10.4 is a better version?
>>>>
>>>> Lonnie
>>>>
>>>> On Jan 23, 2009, at 9:20 AM, Darrick Hartman wrote:
>>>>
>>>>         
>>>>> Lonnie,
>>>>>
>>>>> I bumped busybox to 1.12.4.  (can't go to 1.13.x until we go to  
>>>>> uClibc
>>>>> 0.9.30).
>>>>>
>>>>> The .config file needs to be updated to use (or not use) new  
>>>>> busybox
>>>>> features.
>>>>>
>>>>> Darrick
>>>>>
>>>>> Lonnie Abelbeck wrote:
>>>>>           
>>>>>> Bumping this open item...
>>>>>>
>>>>>> On Dec 25, 2008, at 11:07 PM, Lonnie Abelbeck wrote:
>>>>>>
>>>>>>             
>>>>>>> Trunk's current BusyBox v1.11.2 has a nasty 'vi' bug
>>>>>>>
>>>>>>> type 'vi', then / then RETURN
>>>>>>>
>>>>>>> Dec 25 22:03:43 pbx user.info kernel: vi[2706]: segfault at 0 ip
>>>>>>> 08094772 sp bfc6a89c error 4
>>>>>>> Dec 25 22:03:43 pbx user.info kernel:  in busybox[8048000+6c000]
>>>>>>>
>>>>>>> Supposedly, BusyBox 1.12.2 solves this problem.
>>>>>>>
>>>>>>> Lonnie

-CONFIG_FEATURE_TAR_BZIP2=y
-# CONFIG_FEATURE_TAR_LZMA is not set
-# CONFIG_FEATURE_TAR_FROM is not set
-CONFIG_FEATURE_TAR_GZIP=y
-# CONFIG_FEATURE_TAR_COMPRESS is not set


Eh?



dha...@us... wrote:
> Revision: 2396
>           http://astlinux.svn.sourceforge.net/astlinux/?rev=2396&view=rev
> Author:   dhartman
> Date:     2009-01-23 18:21:35 +0000 (Fri, 23 Jan 2009)
>
> Log Message:
> -----------
> updated busybox config
>
> Modified Paths:
> --------------
>     trunk/package/busybox/busybox-astlinux.config
>
> Modified: trunk/package/busybox/busybox-astlinux.config
> ===================================================================
> --- trunk/package/busybox/busybox-astlinux.config	2009-01-23 15:19:16 UTC (rev 2395)
> +++ trunk/package/busybox/busybox-astlinux.config	2009-01-23 18:21:35 UTC (rev 2396)
> @@ -1,7 +1,7 @@
>  #
>  # Automatically generated make config: don't edit
> -# Busybox version: 1.8.2
> -# Mon Jan  7 11:38:01 2008
> +# Busybox version: 1.12.4
> +# Fri Jan 23 12:20:47 2009
>  #
>  CONFIG_HAVE_DOT_CONFIG=y
>  
> @@ -12,8 +12,9 @@
>  #
>  # General Configuration
>  #
> -CONFIG_NITPICK=y
>  # CONFIG_DESKTOP is not set
> +# CONFIG_EXTRA_COMPAT is not set
> +# CONFIG_FEATURE_ASSUME_UNICODE is not set
>  # CONFIG_FEATURE_BUFFERS_USE_MALLOC is not set
>  # CONFIG_FEATURE_BUFFERS_GO_ON_STACK is not set
>  CONFIG_FEATURE_BUFFERS_GO_IN_BSS=y
> @@ -39,20 +40,25 @@
>  # Build Options
>  #
>  # CONFIG_STATIC is not set
> +# CONFIG_PIE is not set
> +# CONFIG_NOMMU is not set
>  # CONFIG_BUILD_LIBBUSYBOX is not set
>  # CONFIG_FEATURE_INDIVIDUAL is not set
>  # CONFIG_FEATURE_SHARED_BUSYBOX is not set
>  CONFIG_LFS=y
> +CONFIG_CROSS_COMPILER_PREFIX=""
>  
>  #
>  # Debugging Options
>  #
>  # CONFIG_DEBUG is not set
> +# CONFIG_DEBUG_PESSIMIZE is not set
>  # CONFIG_WERROR is not set
>  CONFIG_NO_DEBUG_LIB=y
>  # CONFIG_DMALLOC is not set
>  # CONFIG_EFENCE is not set
>  CONFIG_INCLUDE_SUSv2=y
> +# CONFIG_PARSE is not set
>  
>  #
>  # Installation Options
> @@ -65,7 +71,7 @@
>  # CONFIG_INSTALL_SH_APPLET_SYMLINK is not set
>  # CONFIG_INSTALL_SH_APPLET_HARDLINK is not set
>  # CONFIG_INSTALL_SH_APPLET_SCRIPT_WRAPPER is not set
> -CONFIG_PREFIX="/home/kris/projects/astlinux-trunk/build_i586/root"
> +CONFIG_PREFIX="/home/dhartman/astlinux/trunk/build_i586/root"
>  
>  #
>  # Busybox Library Tuning
> @@ -76,15 +82,17 @@
>  # CONFIG_FEATURE_ETC_NETWORKS is not set
>  # CONFIG_FEATURE_EDITING is not set
>  CONFIG_FEATURE_EDITING_MAX_LEN=
> -# CONFIG_FEATURE_EDITING_FANCY_KEYS is not set
>  # CONFIG_FEATURE_EDITING_VI is not set
>  CONFIG_FEATURE_EDITING_HISTORY=
>  # CONFIG_FEATURE_EDITING_SAVEHISTORY is not set
>  # CONFIG_FEATURE_TAB_COMPLETION is not set
>  # CONFIG_FEATURE_USERNAME_COMPLETION is not set
>  # CONFIG_FEATURE_EDITING_FANCY_PROMPT is not set
> +# CONFIG_FEATURE_VERBOSE_CP_MESSAGE is not set
> +CONFIG_FEATURE_COPYBUF_KB=4
>  CONFIG_MONOTONIC_SYSCALL=y
>  CONFIG_IOCTL_HEX2STR_ERROR=y
> +CONFIG_FEATURE_HWIB=y
>  
>  #
>  # Applets
> @@ -93,45 +101,38 @@
>  #
>  # Archival Utilities
>  #
> +CONFIG_FEATURE_SEAMLESS_LZMA=y
> +CONFIG_FEATURE_SEAMLESS_BZ2=y
> +CONFIG_FEATURE_SEAMLESS_GZ=y
> +CONFIG_FEATURE_SEAMLESS_Z=y
>  # CONFIG_AR is not set
>  # CONFIG_FEATURE_AR_LONG_FILENAMES is not set
>  CONFIG_BUNZIP2=y
>  CONFIG_BZIP2=y
>  # CONFIG_CPIO is not set
> +# CONFIG_FEATURE_CPIO_O is not set
>  # CONFIG_DPKG is not set
>  # CONFIG_DPKG_DEB is not set
>  # CONFIG_FEATURE_DPKG_DEB_EXTRACT_ONLY is not set
>  CONFIG_GUNZIP=y
> -# CONFIG_FEATURE_GUNZIP_UNCOMPRESS is not set
>  CONFIG_GZIP=y
>  # CONFIG_RPM2CPIO is not set
>  # CONFIG_RPM is not set
> -# CONFIG_FEATURE_RPM_BZ2 is not set
>  CONFIG_TAR=y
>  CONFIG_FEATURE_TAR_CREATE=y
> -CONFIG_FEATURE_TAR_BZIP2=y
> -# CONFIG_FEATURE_TAR_LZMA is not set
> -# CONFIG_FEATURE_TAR_FROM is not set
> -CONFIG_FEATURE_TAR_GZIP=y
> -# CONFIG_FEATURE_TAR_COMPRESS is not set
> +# CONFIG_FEATURE_TAR_AUTODETECT is not set
> +CONFIG_FEATURE_TAR_FROM=y
>  # CONFIG_FEATURE_TAR_OLDGNU_COMPATIBILITY is not set
>  # CONFIG_FEATURE_TAR_OLDSUN_COMPATIBILITY is not set
>  CONFIG_FEATURE_TAR_GNU_EXTENSIONS=y
> -# CONFIG_FEATURE_TAR_LONG_OPTIONS is not set
> +CONFIG_FEATURE_TAR_LONG_OPTIONS=y
> +# CONFIG_FEATURE_TAR_UNAME_GNAME is not set
>  # CONFIG_UNCOMPRESS is not set
>  # CONFIG_UNLZMA is not set
>  # CONFIG_FEATURE_LZMA_FAST is not set
>  CONFIG_UNZIP=y
>  
>  #
> -# Common options for cpio and tar
> -#
> -# CONFIG_FEATURE_UNARCHIVE_TAPE is not set
> -# CONFIG_FEATURE_DEB_TAR_GZ is not set
> -# CONFIG_FEATURE_DEB_TAR_BZ2 is not set
> -# CONFIG_FEATURE_DEB_TAR_LZMA is not set
> -
> -#
>  # Coreutils
>  #
>  CONFIG_BASENAME=y
> @@ -152,6 +153,7 @@
>  CONFIG_FEATURE_DD_SIGNAL_HANDLING=y
>  # CONFIG_FEATURE_DD_IBS_OBS is not set
>  CONFIG_DF=y
> +# CONFIG_FEATURE_DF_INODE is not set
>  CONFIG_DIRNAME=y
>  CONFIG_DOS2UNIX=y
>  CONFIG_UNIX2DOS=y
> @@ -160,7 +162,7 @@
>  CONFIG_ECHO=y
>  CONFIG_FEATURE_FANCY_ECHO=y
>  CONFIG_ENV=y
> -# CONFIG_FEATURE_ENV_LONG_OPTIONS is not set
> +CONFIG_FEATURE_ENV_LONG_OPTIONS=y
>  # CONFIG_EXPAND is not set
>  # CONFIG_FEATURE_EXPAND_LONG_OPTIONS is not set
>  CONFIG_EXPR=y
> @@ -168,7 +170,7 @@
>  CONFIG_FALSE=y
>  # CONFIG_FOLD is not set
>  CONFIG_HEAD=y
> -# CONFIG_FEATURE_FANCY_HEAD is not set
> +CONFIG_FEATURE_FANCY_HEAD=y
>  CONFIG_HOSTID=y
>  CONFIG_ID=y
>  CONFIG_INSTALL=y
> @@ -191,7 +193,7 @@
>  # CONFIG_MKFIFO is not set
>  CONFIG_MKNOD=y
>  CONFIG_MV=y
> -# CONFIG_FEATURE_MV_LONG_OPTIONS is not set
> +CONFIG_FEATURE_MV_LONG_OPTIONS=y
>  CONFIG_NICE=y
>  CONFIG_NOHUP=y
>  # CONFIG_OD is not set
> @@ -203,10 +205,12 @@
>  CONFIG_REALPATH=y
>  CONFIG_RM=y
>  CONFIG_RMDIR=y
> +# CONFIG_FEATURE_RMDIR_LONG_OPTIONS is not set
>  CONFIG_SEQ=y
>  CONFIG_SHA1SUM=y
>  CONFIG_SLEEP=y
>  # CONFIG_FEATURE_FANCY_SLEEP is not set
> +# CONFIG_FEATURE_FLOAT_SLEEP is not set
>  CONFIG_SORT=y
>  CONFIG_FEATURE_SORT_BIG=y
>  # CONFIG_SPLIT is not set
> @@ -216,6 +220,7 @@
>  CONFIG_STTY=y
>  # CONFIG_SUM is not set
>  CONFIG_SYNC=y
> +# CONFIG_TAC is not set
>  CONFIG_TAIL=y
>  CONFIG_FEATURE_FANCY_TAIL=y
>  CONFIG_TEE=y
> @@ -277,8 +282,10 @@
>  # CONFIG_FEATURE_RESIZE_PRINT is not set
>  # CONFIG_SETCONSOLE is not set
>  # CONFIG_FEATURE_SETCONSOLE_LONG_OPTIONS is not set
> +# CONFIG_SETFONT is not set
>  # CONFIG_SETKEYCODES is not set
>  # CONFIG_SETLOGCONS is not set
> +# CONFIG_SHOWKEY is not set
>  
>  #
>  # Debian Utilities
> @@ -308,6 +315,7 @@
>  CONFIG_SED=y
>  CONFIG_VI=y
>  CONFIG_FEATURE_VI_MAX_LEN=1024
> +CONFIG_FEATURE_VI_8BIT=y
>  CONFIG_FEATURE_VI_COLON=y
>  CONFIG_FEATURE_VI_YANKMARK=y
>  CONFIG_FEATURE_VI_SEARCH=y
> @@ -361,6 +369,8 @@
>  CONFIG_INIT=y
>  # CONFIG_DEBUG_INIT is not set
>  CONFIG_FEATURE_USE_INITTAB=y
> +CONFIG_FEATURE_KILL_REMOVED=y
> +CONFIG_FEATURE_KILL_DELAY=0
>  # CONFIG_FEATURE_INIT_SCTTY is not set
>  CONFIG_FEATURE_INIT_SYSLOG=y
>  # CONFIG_FEATURE_EXTRA_QUIET is not set
> @@ -373,13 +383,16 @@
>  # Login/Password Management Utilities
>  #
>  CONFIG_FEATURE_SHADOWPASSWDS=y
> +# CONFIG_USE_BB_PWD_GRP is not set
>  # CONFIG_USE_BB_SHADOW is not set
> -# CONFIG_USE_BB_PWD_GRP is not set
> +CONFIG_USE_BB_CRYPT=y
>  CONFIG_ADDGROUP=y
>  CONFIG_FEATURE_ADDUSER_TO_GROUP=y
>  CONFIG_DELGROUP=y
>  CONFIG_FEATURE_DEL_USER_FROM_GROUP=y
> +# CONFIG_FEATURE_CHECK_NAMES is not set
>  CONFIG_ADDUSER=y
> +# CONFIG_FEATURE_ADDUSER_LONG_OPTIONS is not set
>  CONFIG_DELUSER=y
>  CONFIG_GETTY=y
>  CONFIG_FEATURE_UTMP=y
> @@ -409,25 +422,30 @@
>  #
>  # Linux Module Utilities
>  #
> -CONFIG_INSMOD=y
> +# CONFIG_MODPROBE_SMALL is not set
> +# CONFIG_FEATURE_MODPROBE_SMALL_OPTIONS_ON_CMDLINE is not set
> +# CONFIG_FEATURE_MODPROBE_SMALL_CHECK_ALREADY_LOADED is not set
> +# CONFIG_DEPMOD is not set
> +# CONFIG_FEATURE_DEPMOD_PRUNE_FANCY is not set
> +# CONFIG_FEATURE_DEPMOD_ALIAS is not set
> +# CONFIG_INSMOD is not set
>  # CONFIG_FEATURE_INSMOD_VERSION_CHECKING is not set
>  # CONFIG_FEATURE_INSMOD_KSYMOOPS_SYMBOLS is not set
>  # CONFIG_FEATURE_INSMOD_LOADINKMEM is not set
>  # CONFIG_FEATURE_INSMOD_LOAD_MAP is not set
>  # CONFIG_FEATURE_INSMOD_LOAD_MAP_FULL is not set
> -CONFIG_RMMOD=y
> -CONFIG_LSMOD=y
> -CONFIG_FEATURE_LSMOD_PRETTY_2_6_OUTPUT=y
> -CONFIG_MODPROBE=y
> -CONFIG_FEATURE_MODPROBE_MULTIPLE_OPTIONS=y
> -CONFIG_FEATURE_MODPROBE_FANCY_ALIAS=y
> -
> -#
> -# Options common to multiple modutils
> -#
> -CONFIG_FEATURE_CHECK_TAINTED_MODULE=y
> +# CONFIG_RMMOD is not set
> +# CONFIG_LSMOD is not set
> +# CONFIG_FEATURE_LSMOD_PRETTY_2_6_OUTPUT is not set
> +# CONFIG_MODPROBE is not set
> +# CONFIG_FEATURE_MODPROBE_MULTIPLE_OPTIONS is not set
> +# CONFIG_FEATURE_MODPROBE_FANCY_ALIAS is not set
> +# CONFIG_FEATURE_MODPROBE_BLACKLIST is not set
> +# CONFIG_FEATURE_CHECK_TAINTED_MODULE is not set
>  # CONFIG_FEATURE_2_4_MODULES is not set
> -CONFIG_FEATURE_2_6_MODULES=y
> +# CONFIG_FEATURE_2_6_MODULES is not set
> +CONFIG_DEFAULT_MODULES_DIR=""
> +CONFIG_DEFAULT_DEPMOD_FILE=""
>  # CONFIG_FEATURE_QUERY_MODULE_INTERFACE is not set
>  
>  #
> @@ -448,38 +466,67 @@
>  # CONFIG_FEATURE_SUN_LABEL is not set
>  # CONFIG_FEATURE_OSF_LABEL is not set
>  # CONFIG_FEATURE_FDISK_ADVANCED is not set
> +CONFIG_FINDFS=y
>  # CONFIG_FREERAMDISK is not set
>  # CONFIG_FSCK_MINIX is not set
>  # CONFIG_MKFS_MINIX is not set
>  # CONFIG_FEATURE_MINIX2 is not set
>  CONFIG_GETOPT=y
>  CONFIG_HEXDUMP=y
> +# CONFIG_FEATURE_HEXDUMP_REVERSE is not set
> +# CONFIG_HD is not set
>  CONFIG_HWCLOCK=y
> -# CONFIG_FEATURE_HWCLOCK_LONG_OPTIONS is not set
> +CONFIG_FEATURE_HWCLOCK_LONG_OPTIONS=y
>  CONFIG_FEATURE_HWCLOCK_ADJTIME_FHS=y
>  # CONFIG_IPCRM is not set
>  # CONFIG_IPCS is not set
>  CONFIG_LOSETUP=y
>  # CONFIG_MDEV is not set
>  # CONFIG_FEATURE_MDEV_CONF is not set
> +# CONFIG_FEATURE_MDEV_RENAME is not set
> +# CONFIG_FEATURE_MDEV_RENAME_REGEXP is not set
>  # CONFIG_FEATURE_MDEV_EXEC is not set
>  # CONFIG_FEATURE_MDEV_LOAD_FIRMWARE is not set
>  CONFIG_MKSWAP=y
>  # CONFIG_FEATURE_MKSWAP_V0 is not set
>  CONFIG_MORE=y
>  CONFIG_FEATURE_USE_TERMIOS=y
> +CONFIG_VOLUMEID=y
> +CONFIG_FEATURE_VOLUMEID_EXT=y
> +# CONFIG_FEATURE_VOLUMEID_REISERFS is not set
> +CONFIG_FEATURE_VOLUMEID_FAT=y
> +# CONFIG_FEATURE_VOLUMEID_HFS is not set
> +# CONFIG_FEATURE_VOLUMEID_JFS is not set
> +# CONFIG_FEATURE_VOLUMEID_XFS is not set
> +# CONFIG_FEATURE_VOLUMEID_NTFS is not set
> +# CONFIG_FEATURE_VOLUMEID_ISO9660 is not set
> +# CONFIG_FEATURE_VOLUMEID_UDF is not set
> +# CONFIG_FEATURE_VOLUMEID_LUKS is not set
> +# CONFIG_FEATURE_VOLUMEID_LINUXSWAP is not set
> +# CONFIG_FEATURE_VOLUMEID_CRAMFS is not set
> +# CONFIG_FEATURE_VOLUMEID_ROMFS is not set
> +# CONFIG_FEATURE_VOLUMEID_SYSV is not set
> +# CONFIG_FEATURE_VOLUMEID_OCFS2 is not set
> +# CONFIG_FEATURE_VOLUMEID_LINUXRAID is not set
>  CONFIG_MOUNT=y
> +# CONFIG_FEATURE_MOUNT_FAKE is not set
> +# CONFIG_FEATURE_MOUNT_VERBOSE is not set
>  # CONFIG_FEATURE_MOUNT_HELPERS is not set
> +CONFIG_FEATURE_MOUNT_LABEL=y
>  CONFIG_FEATURE_MOUNT_NFS=y
>  CONFIG_FEATURE_MOUNT_CIFS=y
>  CONFIG_FEATURE_MOUNT_FLAGS=y
>  CONFIG_FEATURE_MOUNT_FSTAB=y
>  CONFIG_PIVOT_ROOT=y
>  CONFIG_RDATE=y
> +# CONFIG_RDEV is not set
>  # CONFIG_READPROFILE is not set
> +# CONFIG_RTCWAKE is not set
> +CONFIG_SCRIPT=y
>  # CONFIG_SETARCH is not set
>  CONFIG_SWAPONOFF=y
> -# CONFIG_SWITCH_ROOT is not set
> +# CONFIG_FEATURE_SWAPON_PRI is not set
> +CONFIG_SWITCH_ROOT=y
>  CONFIG_UMOUNT=y
>  CONFIG_FEATURE_UMOUNT_ALL=y
>  
> @@ -494,6 +541,14 @@
>  #
>  # CONFIG_ADJTIMEX is not set
>  # CONFIG_BBCONFIG is not set
> +# CONFIG_CHAT is not set
> +# CONFIG_FEATURE_CHAT_NOFAIL is not set
> +# CONFIG_FEATURE_CHAT_TTY_HIFI is not set
> +# CONFIG_FEATURE_CHAT_IMPLICIT_CR is not set
> +# CONFIG_FEATURE_CHAT_SWALLOW_OPTS is not set
> +# CONFIG_FEATURE_CHAT_SEND_ESCAPES is not set
> +# CONFIG_FEATURE_CHAT_VAR_ABORT_LEN is not set
> +# CONFIG_FEATURE_CHAT_CLR_ABORT is not set
>  # CONFIG_CHRT is not set
>  CONFIG_CROND=y
>  # CONFIG_DEBUG_CROND_OPTION is not set
> @@ -506,14 +561,19 @@
>  # CONFIG_DEVFSD_VERBOSE is not set
>  # CONFIG_FEATURE_DEVFS is not set
>  # CONFIG_EJECT is not set
> +# CONFIG_FEATURE_EJECT_SCSI is not set
> +# CONFIG_FBSPLASH is not set
> +# CONFIG_INOTIFYD is not set
>  CONFIG_LAST=y
> +CONFIG_FEATURE_LAST_SMALL=y
> +# CONFIG_FEATURE_LAST_FANCY is not set
>  CONFIG_LESS=y
>  CONFIG_FEATURE_LESS_MAXLINES=9999999
>  CONFIG_FEATURE_LESS_BRACKETS=y
>  CONFIG_FEATURE_LESS_FLAGS=y
>  # CONFIG_FEATURE_LESS_FLAGCS is not set
>  # CONFIG_FEATURE_LESS_MARKS is not set
> -# CONFIG_FEATURE_LESS_REGEXP is not set
> +CONFIG_FEATURE_LESS_REGEXP=y
>  CONFIG_HDPARM=y
>  CONFIG_FEATURE_HDPARM_GET_IDENTITY=y
>  CONFIG_FEATURE_HDPARM_HDIO_SCAN_HWIF=y
> @@ -524,15 +584,16 @@
>  CONFIG_MAKEDEVS=y
>  # CONFIG_FEATURE_MAKEDEVS_LEAF is not set
>  CONFIG_FEATURE_MAKEDEVS_TABLE=y
> -# CONFIG_MICROCOM is not set
> +# CONFIG_MAN is not set
> +CONFIG_MICROCOM=y
>  # CONFIG_MOUNTPOINT is not set
>  CONFIG_MT=y
>  # CONFIG_RAIDAUTORUN is not set
>  # CONFIG_READAHEAD is not set
>  # CONFIG_RUNLEVEL is not set
>  # CONFIG_RX is not set
> +# CONFIG_SETSID is not set
>  CONFIG_STRINGS=y
> -# CONFIG_SETSID is not set
>  # CONFIG_TASKSET is not set
>  # CONFIG_FEATURE_TASKSET_FANCY is not set
>  CONFIG_TIME=y
> @@ -543,9 +604,13 @@
>  # Networking Utilities
>  #
>  CONFIG_FEATURE_IPV6=y
> +CONFIG_FEATURE_PREFER_IPV4_ADDRESS=y
>  CONFIG_VERBOSE_RESOLUTION_ERRORS=y
>  CONFIG_ARP=y
>  CONFIG_ARPING=y
> +# CONFIG_BRCTL is not set
> +# CONFIG_FEATURE_BRCTL_FANCY is not set
> +# CONFIG_FEATURE_BRCTL_SHOW is not set
>  # CONFIG_DNSD is not set
>  CONFIG_ETHER_WAKE=y
>  CONFIG_FAKEIDENTD=y
> @@ -573,6 +638,7 @@
>  CONFIG_FEATURE_IFCONFIG_MEMSTART_IOADDR_IRQ=y
>  CONFIG_FEATURE_IFCONFIG_HW=y
>  CONFIG_FEATURE_IFCONFIG_BROADCAST_PLUS=y
> +# CONFIG_IFENSLAVE is not set
>  CONFIG_IFUPDOWN=y
>  CONFIG_IFUPDOWN_IFSTATE_PATH="/var/run/ifstate"
>  # CONFIG_FEATURE_IFUPDOWN_IP is not set
> @@ -589,34 +655,38 @@
>  CONFIG_FEATURE_INETD_SUPPORT_BUILTIN_DAYTIME=y
>  CONFIG_FEATURE_INETD_SUPPORT_BUILTIN_CHARGEN=y
>  # CONFIG_FEATURE_INETD_RPC is not set
> -CONFIG_IP=y
> -CONFIG_FEATURE_IP_ADDRESS=y
> -CONFIG_FEATURE_IP_LINK=y
> -CONFIG_FEATURE_IP_ROUTE=y
> -CONFIG_FEATURE_IP_TUNNEL=y
> -CONFIG_FEATURE_IP_RULE=y
> -CONFIG_FEATURE_IP_SHORT_FORMS=y
> +# CONFIG_IP is not set
> +# CONFIG_FEATURE_IP_ADDRESS is not set
> +# CONFIG_FEATURE_IP_LINK is not set
> +# CONFIG_FEATURE_IP_ROUTE is not set
> +# CONFIG_FEATURE_IP_TUNNEL is not set
> +# CONFIG_FEATURE_IP_RULE is not set
> +# CONFIG_FEATURE_IP_SHORT_FORMS is not set
>  # CONFIG_FEATURE_IP_RARE_PROTOCOLS is not set
> -CONFIG_IPADDR=y
> -CONFIG_IPLINK=y
> -CONFIG_IPROUTE=y
> -CONFIG_IPTUNNEL=y
> -CONFIG_IPRULE=y
> +# CONFIG_IPADDR is not set
> +# CONFIG_IPLINK is not set
> +# CONFIG_IPROUTE is not set
> +# CONFIG_IPTUNNEL is not set
> +# CONFIG_IPRULE is not set
>  CONFIG_IPCALC=y
>  CONFIG_FEATURE_IPCALC_FANCY=y
>  # CONFIG_FEATURE_IPCALC_LONG_OPTIONS is not set
>  CONFIG_NAMEIF=y
> +# CONFIG_FEATURE_NAMEIF_EXTENDED is not set
>  CONFIG_NC=y
>  CONFIG_NC_SERVER=y
>  # CONFIG_NC_EXTRA is not set
>  CONFIG_NETSTAT=y
>  CONFIG_FEATURE_NETSTAT_WIDE=y
> +# CONFIG_FEATURE_NETSTAT_PRG is not set
>  CONFIG_NSLOOKUP=y
>  CONFIG_PING=y
>  CONFIG_PING6=y
> +CONFIG_FEATURE_FANCY_PING=y
>  # CONFIG_PSCAN is not set
> -CONFIG_FEATURE_FANCY_PING=y
>  CONFIG_ROUTE=y
> +# CONFIG_SENDMAIL is not set
> +# CONFIG_FETCHMAIL is not set
>  # CONFIG_SLATTACH is not set
>  CONFIG_TELNET=y
>  CONFIG_FEATURE_TELNET_TTYPE=y
> @@ -624,6 +694,7 @@
>  CONFIG_TELNETD=y
>  # CONFIG_FEATURE_TELNETD_STANDALONE is not set
>  CONFIG_TFTP=y
> +# CONFIG_TFTPD is not set
>  CONFIG_FEATURE_TFTP_GET=y
>  CONFIG_FEATURE_TFTP_PUT=y
>  CONFIG_FEATURE_TFTP_BLOCKSIZE=y
> @@ -636,15 +707,22 @@
>  # CONFIG_APP_DHCPRELAY is not set
>  # CONFIG_APP_DUMPLEASES is not set
>  # CONFIG_FEATURE_UDHCPD_WRITE_LEASES_EARLY is not set
> +CONFIG_DHCPD_LEASES_FILE=""
>  CONFIG_APP_UDHCPC=y
> +CONFIG_FEATURE_UDHCPC_ARPING=y
> +# CONFIG_FEATURE_UDHCP_PORT is not set
>  # CONFIG_FEATURE_UDHCP_DEBUG is not set
>  # CONFIG_FEATURE_RFC3397 is not set
> +CONFIG_DHCPC_DEFAULT_SCRIPT="/usr/share/udhcpc/default.script"
> +CONFIG_UDHCPC_SLACK_FOR_BUGGY_SERVERS=80
>  CONFIG_VCONFIG=y
>  CONFIG_WGET=y
>  CONFIG_FEATURE_WGET_STATUSBAR=y
>  CONFIG_FEATURE_WGET_AUTHENTICATION=y
> -# CONFIG_FEATURE_WGET_LONG_OPTIONS is not set
> +CONFIG_FEATURE_WGET_LONG_OPTIONS=y
>  CONFIG_ZCIP=y
> +# CONFIG_TCPSVD is not set
> +# CONFIG_UDPSVD is not set
>  
>  #
>  # Process Utilities
> @@ -662,6 +740,8 @@
>  CONFIG_PKILL=y
>  CONFIG_PS=y
>  CONFIG_FEATURE_PS_WIDE=y
> +# CONFIG_FEATURE_PS_TIME is not set
> +# CONFIG_FEATURE_PS_UNUSUAL_SYSTEMS is not set
>  CONFIG_RENICE=y
>  CONFIG_BB_SYSCTL=y
>  CONFIG_TOP=y
> @@ -677,7 +757,6 @@
>  #
>  CONFIG_FEATURE_SH_IS_ASH=y
>  # CONFIG_FEATURE_SH_IS_HUSH is not set
> -# CONFIG_FEATURE_SH_IS_LASH is not set
>  # CONFIG_FEATURE_SH_IS_MSH is not set
>  # CONFIG_FEATURE_SH_IS_NONE is not set
>  CONFIG_ASH=y
> @@ -685,6 +764,7 @@
>  #
>  # Ash Shell Options
>  #
> +CONFIG_ASH_BASH_COMPAT=y
>  CONFIG_ASH_JOB_CONTROL=y
>  # CONFIG_ASH_READ_NCHARS is not set
>  # CONFIG_ASH_READ_TIMEOUT is not set
> @@ -693,6 +773,7 @@
>  CONFIG_ASH_MATH_SUPPORT_64=y
>  # CONFIG_ASH_GETOPTS is not set
>  # CONFIG_ASH_BUILTIN_ECHO is not set
> +CONFIG_ASH_BUILTIN_PRINTF=y
>  CONFIG_ASH_BUILTIN_TEST=y
>  # CONFIG_ASH_CMDCMD is not set
>  # CONFIG_ASH_MAIL is not set
> @@ -706,6 +787,7 @@
>  # CONFIG_HUSH_TICK is not set
>  # CONFIG_HUSH_IF is not set
>  # CONFIG_HUSH_LOOPS is not set
> +# CONFIG_HUSH_CASE is not set
>  # CONFIG_LASH is not set
>  # CONFIG_MSH is not set
>  
> @@ -714,6 +796,7 @@
>  #
>  CONFIG_FEATURE_SH_EXTRA_QUIET=y
>  # CONFIG_FEATURE_SH_STANDALONE is not set
> +# CONFIG_FEATURE_SH_NOFORK is not set
>  CONFIG_CTTYHACK=y
>  
>  #
> @@ -722,6 +805,7 @@
>  CONFIG_SYSLOGD=y
>  CONFIG_FEATURE_ROTATE_LOGFILE=y
>  CONFIG_FEATURE_REMOTE_LOG=y
> +CONFIG_FEATURE_SYSLOGD_DUP=y
>  CONFIG_FEATURE_IPC_SYSLOG=y
>  CONFIG_FEATURE_IPC_SYSLOG_BUFFER_SIZE=16
>  CONFIG_LOGREAD=y
> @@ -755,9 +839,11 @@
>  # CONFIG_SETFILES is not set
>  # CONFIG_FEATURE_SETFILES_CHECK_OPTION is not set
>  # CONFIG_SETSEBOOL is not set
> +# CONFIG_SESTATUS is not set
>  
>  #
> -# ipsvd utilities
> +# Print Utilities
>  #
> -# CONFIG_TCPSVD is not set
> -# CONFIG_UDPSVD is not set
> +# CONFIG_LPD is not set
> +# CONFIG_LPR is not set
> +# CONFIG_LPQ is not set
>
>
>   

The initrd version needs updating yet...

Lonnie Abelbeck wrote:
> Darrick,
> 
> Busybox 1.12.4 looks good with your updated config. Thanks!
> 
> Lonnie
> 
> 
> On Jan 23, 2009, at 12:29 PM, Darrick Hartman wrote:
> 
>> I've updated the base busybox config.  I still need to do the initrd
>> version.  The cool thing is findfs is now part of busybox so we can
>> ditch some of the stuff from the initrd in trunk.
>>
>> We need to revisit whether we need standalone versions of certain
>> functions or if we want to move to busybox versions.
>>
>> Darrick
>>
>> Darrick Hartman wrote:
>>> Might as well keep it at 1.12.4, but update the .config.
>>>
>>> Lemme see if I can update it.
>>>
>>> Darrick
>>>
>>> Lonnie Abelbeck wrote:
>>>> Thanks Darrick, but there are problems...
>>>>
>>>> tar does not have the -z option anymore
>>>>
>>>> Does the "busybox-astlinux.config" need to be completely rebuilt for
>>>> 1.12.4?
>>>>
>>>> Maybe 1.10.4 is a better version?
>>>>
>>>> Lonnie
>>>>
>>>> On Jan 23, 2009, at 9:20 AM, Darrick Hartman wrote:
>>>>
>>>>> Lonnie,
>>>>>
>>>>> I bumped busybox to 1.12.4.  (can't go to 1.13.x until we go to  
>>>>> uClibc
>>>>> 0.9.30).
>>>>>
>>>>> The .config file needs to be updated to use (or not use) new  
>>>>> busybox
>>>>> features.
>>>>>
>>>>> Darrick
>>>>>
>>>>> Lonnie Abelbeck wrote:
>>>>>> Bumping this open item...
>>>>>>
>>>>>> On Dec 25, 2008, at 11:07 PM, Lonnie Abelbeck wrote:
>>>>>>
>>>>>>> Trunk's current BusyBox v1.11.2 has a nasty 'vi' bug
>>>>>>>
>>>>>>> type 'vi', then / then RETURN
>>>>>>>
>>>>>>> Dec 25 22:03:43 pbx user.info kernel: vi[2706]: segfault at 0 ip
>>>>>>> 08094772 sp bfc6a89c error 4
>>>>>>> Dec 25 22:03:43 pbx user.info kernel:  in busybox[8048000+6c000]
>>>>>>>
>>>>>>> Supposedly, BusyBox 1.12.2 solves this problem.
>>>>>>>
>>>>>>> Lonnie
>>>>>> ------------------------------------------------------------------------------
>>>>>> This SF.net email is sponsored by:
>>>>>> SourcForge Community
>>>>>> SourceForge wants to tell your story.
>>>>>> http://p.sf.net/sfu/sf-spreadtheword
>>>>>> _______________________________________________
>>>>>> Astlinux-devel mailing list
>>>>>> Ast...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>>>>>
>>>>>> Donations to support AstLinux are graciously accepted via PayPal  
>>>>>> to pa...@kr...
>>>>>> .
>>>>> ------------------------------------------------------------------------------
>>>>> This SF.net email is sponsored by:
>>>>> SourcForge Community
>>>>> SourceForge wants to tell your story.
>>>>> http://p.sf.net/sfu/sf-spreadtheword
>>>>> _______________________________________________
>>>>> Astlinux-devel mailing list
>>>>> Ast...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>>>>
>>>>> Donations to support AstLinux are graciously accepted via PayPal  
>>>>> to pa...@kr...
>>>>> .
>>>>>
>>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.net email is sponsored by:
>>>> SourcForge Community
>>>> SourceForge wants to tell your story.
>>>> http://p.sf.net/sfu/sf-spreadtheword
>>>> _______________________________________________
>>>> Astlinux-devel mailing list
>>>> Ast...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>>>
>>>> Donations to support AstLinux are graciously accepted via PayPal  
>>>> to pa...@kr....
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by:
>>> SourcForge Community
>>> SourceForge wants to tell your story.
>>> http://p.sf.net/sfu/sf-spreadtheword
>>> _______________________________________________
>>> Astlinux-devel mailing list
>>> Ast...@li...
>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>>
>>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr... 
>>> .
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>
>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr... 
>> .
>>
>>
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....