FreeLists / openbeosnetteam / [openbeosnetteam] Re: Me as well...

[Evan Knop <argent@xxxxxxxxxxxxxxxxxx>]

Hi.  I'm a lurker who's pretty interested in making OpenBeOS succeed
in the areas where Be left off - networking and unix compatibility
without sacrificing the simplicity of the Be tools and installation.

on Wed, Jan 16 20:48, Mark Hellegers was heard to have remarked:
>>It'd also be nice to offer a range of daemons, via inetd, though with
>them
>>all switched off by default I suspect
>
>Definately switched off. I'm always annoyed with linux distributions
>enabling sendmail by default.

Yes.  OpenBeOS shouldn't ship with any network services running by
default.  Open services are a security hole, and we shouldn't be
providing users with easy ways to get into trouble.

>Full fledged ftpd and sendmail are surely going to hurt other apps.

Well, we should make it so that ftpd and sendmail can be compiled
without any problems with the network sections of the code.

>>> Fair enough.  I suspect we'll get leaned on from the rest of the
>OpenBeOS
>>> team to have binary compatibility, which is really the only reason I
>say
>>it. :P
>>
>>I think we should aim for a kick ass network kit and then pander for
>>backwards compatibility as a second priority :)
>
>It would be good to catalog which current apps use the network in such a
>way that they would be broken and see if the authors want to update them.
>That way, we don't have to worry about backwards compatibility. From what
>I heard, most apps needed a recompile too, to work correctly on BONE.

Would it be possible to build a libnet.so that's compatible with our
network interface after we've built the libnet2 and network stack.

-- 
Evan Knop <argent@xxxxxxxxxxx>      http://lore.dartmouth.edu/~argent/

Uncompensated overtime?  Just Say No.