[ previous ] [ next ] [ threads ]
 
 From:  Ron Rosson <ron dot rosson at gmail dot com>
 To:  m0n0wall-dev <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall-dev] Re: [m0n0wall] The future
 Date:  Fri, 14 Oct 2005 07:27:24 -0500
> From: Kris Maglione <bsdaemon at comcast dot net>
> Date: Thu, 13 Oct 2005 16:40:10 -0400
> To: Ron Rosson <ron dot rosson at gmail dot com>
> Cc: m0n0wall-dev <m0n0wall dash dev at lists dot m0n0 dot ch>
> Subject: Re: [m0n0wall-dev] Re: [m0n0wall] The future
> 
> Ron Rosson wrote:
> 
>> 
>> Which both came from OpenBSD.
>>  
>> 
> They all came from OpenBSD. The point is that FreeBSD has them also,
> now, and an improved network stack to match. If you have evidence that
> they work better on OpenBSD, however, that would be useful.
> 

One more point on OpenBSD and these services. These services where written
into the KERNEL of OpenBSD for the getgo, they were not done to an existing
kernel as "That would be nice to have in ours" and merge it in. "ie Reason
for breakage in 6 when adding CARP"

On topic from other messages the core system should use the best langauge
for the job that can be supported by the community as well for the GUI. If a
Soekris could handle AJAX web pages then let it but only if it is the best
thing to get the job done.

-Ron

P.S. The whole system needs to be modular. That way when a new feature is
added the community just has to right the hooks to integrate it and not
rewrite the whole thing.. So the API in the beginning is going to be highly
critical.