Hi,
On Fri, 07 Jul 2006 at 10:16 +0200, Michael 'buk' Scherer wrote:
> Hey freewrt guys and gals.
> 
> I read wbx blog a while back and noticed that he planned to fork openwrt.
> Good idea, though openwrt runs good on my asus I somehow wasn't that much
> satisfied with the project.
> 
> Now I'm curious about how you plan to make FreeWRT different to openwrt?
> Maybe some more detailed information and documentation?

FreeWRT is planned to be a general framework (meta Linux
distribution) for embedded systems. The support for Linksys WRT54G
and other WLAN-Routers is just a start. 

So the plan is to make it more generic and let us build images under
BSD, MacOS X, Windows (Cygwin), Linux and from the Web via an
ImageBuilder. 

FreeWRT should contain some useful default configuration for the
embedded system. And you should always have the choice, where it is
appropriated. Choice between GNU libc and uclibc is one of the tasks
I want to implement next. There should be no simple choice to change
other parameters of the toolchain, because we want to maintain only
one working and well tested combination of binutils, gcc and gdb for
all targets. I am looking forward to have a nice automatic regression
test of the toolchain, which works via ssh and run the tests on the
target. 

> Not just a wiki where you can point users onto with the words "if its not 
> in there write it"?
> 
> Really looking forward to that project.
> I would even help with various packages if you can make me switch and need
> some support ;)

I am looking forward to hear from you. The nearest next step is to
have a 1.0 release for a specific embedded system. (broadcom based
boards)

This will bring some more attraction to new users and developers.

See our more detailed development plans here:
http://www.freewrt.org/orga

best regards
    Waldemar

-- 
don't open your wrt, free it
http://www.freewrt.org
_______________________________________________
freewrt-users mailing list
[email protected]
https://www.freewrt.org/lists/listinfo/freewrt-users

Reply via email to