FreeLists / openbeosnetteam / [openbeosnetteam] Re: Design mess

["David Enderson" <DEnderson@xxxxxxxxxxxxxx>]

Team,

What I love about Be and what we are recreating with Haiku is how
modular and _clean_ it is.  I already use lots of daemons, scripts and
hidden config files on Linux and lots of bloated crud on Windows.  What
motivates me to donate time to this project is that we are creating
something _different_.

So please, lets try to make as few daemons, daemons, scripts, and config
files as humanly possible and make it as modular as possible.  Where
those modules should be executed from--I'm not as knowledgeable on such
things as you all, so I'll keep quiet.

Just...please.  As clean and modular and possible.  :-)

--David

> I would want us to take some time to consider what design we 
> should chose and/or stick to:
> 
> a) put all what's needed for a working stack into kernelland, 
> without user assistance, for the sake of performance and 
> self-dependency. Put all the rest in userland libs and 
> regular apps. I included inetd daemon as a regular app.
> 
> b) put less as possible (nothing being the best) into 
> kernelland, and make the network kit looking more like the R5 
> one, based on a net_server app + its add-ons + some libs and 
> command line tools.
> 
> What do you think?
> Does I overly react?
> Do you share my worries?
> What's your preferred design?
> Someone have a c) design to propose?
> 
> - Philippe
> 
>