[ previous ] [ next ] [ threads ]
 
 From:  "Jonathan De Graeve" <Jonathan dot De dot Graeve at imelda dot be>
 To:  "Peter Allgeyer" <allgeyer at web dot de>, "Manuel Kasper" <mk at neon1 dot net>, "Peter Curran" <peter at closeconsultants dot com>
 Cc:  <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall-dev] RE: [m0n0wall] The future
 Date:  Wed, 12 Oct 2005 23:23:27 +0200
Am Mittwoch, den 12.10.2005, 18:59 +0200 schrieb lola:
> to be honest, i like m0n0wall because it uses php! it makes changes to
> m0n0wall or the gui simple and easy. i think this is a great feature.
i
> wouldnt give that up.
>There's almost nothing I can add to this opinion.

Agree

Am Mittwoch, den 12.10.2005, 18:41 +0100 schrieb Peter Curran:
> 3.  Can I offer Python as a possibility?  It is naturally OO
(literally the 
> whole thing is a bunch of objects).  It compiles down to a .pyc
bytecode ala 
> java and is becoming well supported and used
>Thanks for mentioning, Peter. If OO is a "must have" there's IMHO no
>other language than python which gives us more flexibility. It's widely
>used for web apps as it is for standalone programs. The availibility to
>precompile the code gives us small and fast programs. The language
>itself was designed as true OO (do I here Smalltalk anywhere ;-)).

>Perl? The OO part is the same as in PHP: only added afterwards. No, if
>someone says Perl, then we can stay by using PHP.

>Java? Convince me that it's not as slow and memory hungry as I know it
>(especially on low end HW like our net4501).

>C(++). Yes, for the backend (daemon part).

Agree too, but if we need to change our core unit in 'readable' format
=> I agree to python.

>Linux (which I'm using for 13 years now) is surely one of the famous
>OSes in our time. There is still rumour that the network code isn't as
>stable and fast as that of the BSDish ones, but that's nonsense and not
>true anymore. Even the filtering language (netfilter) has become a
>global player. It's really amazing what we can do with netfilter in
>combination with iproute2. Another good point for linux is the embedded
>part of the kernel, but please keep in mind: Actually we have images
for
>four platforms: wrap net4801, nbet4501 and generic-pc (not mentioned
the
>cd image as fifth one); do we really want to support one for mips, one
>for xscale, one for ...

Agree too :) used linux/iptables/iproute 3years ago on our own embedded
internet router using different routing tables and an enhanced firewall.
But...

>My vote goes to OpenBSD, too. Why?

Mine too

Summarize:

1)
IF!!! We really need to change the programming language I'm for python
because the not that difficult programming style and the option to
compile it into executable. Could be used for core AND frontend...

2) Openbsd for obvious reasons

3) need to have open standard for communication between all the
'services'.




--
Jonathan De Graeve
Network/System Administrator
Imelda vzw
Informatica Dienst
015/50.52.98
Jonathan dot de dot graeve at imelda dot be