[ previous ] [ next ] [ threads ]
 From:  Kris Maglione <bsdaemon at comcast dot net>
 To:  m0n0wall dash dev at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall-dev] The future - summary
 Date:  Thu, 13 Oct 2005 16:55:10 -0400
Manuel Kasper wrote:

>It was never proposed to use anything else but PHP for the webGUI.
It was proposed by others :)

>This has generated an outcry - many developers and even users don't
>want to see m0n0wall using anything else but PHP. A few possible
>candidates for the daemon were mentioned (Python, Ruby, Perl, ...),
>but apparently most people would rather see things stay the way they
>are now.
I think that it can be done in PHP without too much trouble, but would
be easier (to write/maintain) in Python/Ruby/Perl. I'm strongly for the
option of writing the core in one of those languages. Otherwise, a
daemon could be written in PHP, or just an abstracted library. I'd like
to see the idea of a core implimented either way, though.

>This is going to be a difficult question, and I'd appreciate if
>someone (Chris? ;) could put together some kind of feature matrix so
>that all the advantages and disadvantages are clear and can be
>weighed up.
Don't forget religion, in this case. There are a good few people who
would likely jump ship if Linux is chosen. The rivlary between the
separate BSDs isn't quite as strong as between the general BSD camp and
the Linux camp.

If noone else steps up to do this, I'll do it.

>However, if we continue using the MFS approach, we're still limited by available
We should be able to get away with a hybrid approach. FreeBSD has
support for file-backed filesystems. The majority of the filesystem
could be mounted read-only with MFSs mounted where needed. Otherwise,
parts of the FS could be overlayed with a memory-backed unionfs, which
would only take up space when a file was changed, and throw away changes
when it's unmounted.

>Finally, about the upcoming survey: I've started a collection of
>questions that we could ask on
><http://wiki.m0n0.ch/wikka.php?wakka=SurveyQuestions> (in blatant
>abuse of the documentation wiki - please forgive me, Chris). 
I was going to suggest that. :) (although I had summaries in mind, aside
from survey questions).