If you could release a wrap/net48xx version then am sure a lot of
people would love to test it, but am guessing the major sticking point
is most of those people aren't willing to set up a freebsd6 box to
build the image themselves. I know that I for one would be more than
happy to test it, even if there were some serious issues to be ironed
out, but setting up a freebsd6 box and trying to work out how exactly
to build the image is something I will need a bit more motivation to
On 28/07/06, Dinesh Nair <dinesh at alphaque dot com> wrote:
> On 07/28/06 01:05 Lee Sharp said the following:
> > It would be a good place to backport a lot of changes from. However, if
> > it was the solution you are claiming it is, we would all be over there.
> this is turning into a pfsense vs m0n0 thread, and while i'm still
> committed to making m0n0 work on freebsd 6.1, there are some things which
> we can take from pfsense. that's the beauty of open source projects and
> cross-pollination of code and features.
> m0n0 is still targetted at the embedded space with a smaller memory and
> disk/cf footprint and i think it excels in this role. other projects like
> freenas and pfsense have taken this theme and extended it to do other
> stuff, which isn't a bad thing either.
> so, as a plea to all, could we test the freebsd 6 branch of m0n0 and report
> back on bugs so we can expedite the transition ?
> Regards, /\_/\ "All dogs go to heaven."
> dinesh at alphaque dot com (0 0) http://www.openmalaysiablog.com/
> | for a in past present future; do |
> | for b in clients employers associates relatives neighbours pets; do |
> | echo "The opinions here in no way reflect the opinions of my $a $b." |
> | done; done |
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch