astlinux-devel Mailing List for AstLinux

Lonnie Abelbeck wrote:
> On Dec 3, 2008, at 12:57 PM, Philip Prindeville wrote:
>
>   
>> I'd like to follow up with a 0.7 release before too long (say by
>> Valentine's Day).
>>     
>
> Would my wife consider this present as something special?  :-)
>
> I'd be happy helping with the 1.9 arno, let me propose a mapping of  
> the files based on RC5 and present it.
>
> Is the Hostap a personal wish for you Philip?  I'm more of a fan of an  
> access point on a wire, not any more expensive and more flexible.
>   

I'm a fan of single-box solutions...  especially if you can have an 
exact h/w clone of the box configured and ready to go for a warm-swap in 
case of failure...

But more to your point:  Wifi has some sophisticated QoS management 
built-in that works very nicely with Wifi-enabled SIP phones, that you 
only find on really expensive enterprise-level Wifi WAP's.  Your average 
D-Link or Netgear or Linksys router won't be able to do this.

One of the things that you can do with hostap is set up mappings from 
DSCP to Wifi QoS.

Short of a Cisco AP1200, I don't know many other boxes that can do 
that...  certainly none under $400...

A lot of consumer-grade Wifi boxes also don't allow multiple SSID's and 
VLAN's...

So from my perspective, Astlinux+hostap properly configured is both 
cheaper and more feature-rich.

-Philip


> Anyway, a great list.
>
> Lonnie
>
>   
>> Here's what we could shoot for:
>>
>> * have "memtest" and "recover" boot targets (which probably implies
>> putting dosfsck into initrd);
>>
>> * get IPSec "road warrior" configuration working
>>
>> * get Hostap configuration scripts working
>>
>> * move to Arno's firewall 1.9.0 if it ever gets released?  (including
>> getting a good traffic shaper running) -- this probably implies  
>> killing
>> off astfw.
>>
>> * get all the other platforms running the same kernel, and being  
>> stable,
>> of course
>>
>> * I'd also like to see about making $ASTURW mandatory, and getting rid
>> of the symlink foo to /tmp/etc/xxx ...
>>
>> What to do about pf_ring and nistnet?  And are there any currently
>> "experimental" features that we think might be ready for prime-time?
>>
>> Let's set our list of goals, and see who wants to put their names on
>> some of them.
>>
>> I can do #2 and #4 (though I'd like a little help on #4 from Lonnie if
>> he has the time).
>>
>> -Philip
>>     

On Dec 3, 2008, at 12:57 PM, Philip Prindeville wrote:

> I'd like to follow up with a 0.7 release before too long (say by
> Valentine's Day).

Would my wife consider this present as something special?  :-)

I'd be happy helping with the 1.9 arno, let me propose a mapping of  
the files based on RC5 and present it.

Is the Hostap a personal wish for you Philip?  I'm more of a fan of an  
access point on a wire, not any more expensive and more flexible.

Anyway, a great list.

Lonnie

> Here's what we could shoot for:
>
> * have "memtest" and "recover" boot targets (which probably implies
> putting dosfsck into initrd);
>
> * get IPSec "road warrior" configuration working
>
> * get Hostap configuration scripts working
>
> * move to Arno's firewall 1.9.0 if it ever gets released?  (including
> getting a good traffic shaper running) -- this probably implies  
> killing
> off astfw.
>
> * get all the other platforms running the same kernel, and being  
> stable,
> of course
>
> * I'd also like to see about making $ASTURW mandatory, and getting rid
> of the symlink foo to /tmp/etc/xxx ...
>
> What to do about pf_ring and nistnet?  And are there any currently
> "experimental" features that we think might be ready for prime-time?
>
> Let's set our list of goals, and see who wants to put their names on
> some of them.
>
> I can do #2 and #4 (though I'd like a little help on #4 from Lonnie if
> he has the time).
>
> -Philip
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> 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... 
> .
>

Michael Keuter wrote:
>> I'd like to follow up with a 0.7 release before too long (say by
>> Valentine's Day).
>>
>> Here's what we could shoot for:
>>
>> * have "memtest" and "recover" boot targets (which probably implies
>> putting dosfsck into initrd);
>>     
>
> Hi Philip,
>
> I got memtest working on my net4801/net5501 (and also with pxeboot 
> for testing purposes) with this howto:
>
> http://www.bernoullinetworks.com/memtest.html
>
> and a syslinux.cfg like that:
> -----------------------------------------
> serial 0 19200
> default memtest
> timeout 5
> prompt 5
>
> label memtest
>      kernel memtest
> -----------------------------------------
>
> That should be no problem for the devs to integrate that in the 
> Astlinux build environment.
>
> Michael
>
>   

Only problem would be time, of course.  :-(

If you could come up with diff's, we can commit them...

-Philip

>I'd like to follow up with a 0.7 release before too long (say by
>Valentine's Day).
>
>Here's what we could shoot for:
>
>* have "memtest" and "recover" boot targets (which probably implies
>putting dosfsck into initrd);

Hi Philip,

I got memtest working on my net4801/net5501 (and also with pxeboot 
for testing purposes) with this howto:

http://www.bernoullinetworks.com/memtest.html

and a syslinux.cfg like that:
-----------------------------------------
serial 0 19200
default memtest
timeout 5
prompt 5

label memtest
     kernel memtest
-----------------------------------------

That should be no problem for the devs to integrate that in the 
Astlinux build environment.

Michael

--
Email: mailto:mk...@we...

I'd like to follow up with a 0.7 release before too long (say by 
Valentine's Day).

Here's what we could shoot for:

* have "memtest" and "recover" boot targets (which probably implies 
putting dosfsck into initrd);

* get IPSec "road warrior" configuration working

* get Hostap configuration scripts working

* move to Arno's firewall 1.9.0 if it ever gets released?  (including 
getting a good traffic shaper running) -- this probably implies killing 
off astfw.

* get all the other platforms running the same kernel, and being stable, 
of course

* I'd also like to see about making $ASTURW mandatory, and getting rid 
of the symlink foo to /tmp/etc/xxx ...

What to do about pf_ring and nistnet?  And are there any currently 
"experimental" features that we think might be ready for prime-time?

Let's set our list of goals, and see who wants to put their names on 
some of them.

I can do #2 and #4 (though I'd like a little help on #4 from Lonnie if 
he has the time).

-Philip

Philip Prindeville wrote:
> I noticed that if I did a kernel bump from 2.6.25.19 to 2.6.25.20 in 
> target/device/net5501/linux.mk and rebuilt, then some toolchain file 
> failed to compile... but fails silently... or at least non-fatally as 
> the rest of the build process continues anyway.
> 
> Unfortunately, the built image dies somewhere in /etc/rc or one of the 
> /etc/init.d/* scripts... can't tell where without building instrumentation.
> 
> Anyone have a chance to poke around in this?
> 
> Thanks,
> 
> -Philip

Anytime you upgrade the kernel, you also need to completely blow away 
the toolchain_build_i586 directory too.

I noticed that if I did a kernel bump from 2.6.25.19 to 2.6.25.20 in 
target/device/net5501/linux.mk and rebuilt, then some toolchain file 
failed to compile... but fails silently... or at least non-fatally as 
the rest of the build process continues anyway.

Unfortunately, the built image dies somewhere in /etc/rc or one of the 
/etc/init.d/* scripts... can't tell where without building instrumentation.

Anyone have a chance to poke around in this?

Thanks,

-Philip