[openbeosnetteam] Re: Me as well...

Quoth "David Reid":
>>
>> Forgive me for looking like a fool, but what are teams, and shutdown? :)
>> (I have done socket code on unix before, just don't recognize the terms,
>> haven't done anything to rough.)
>
>shutdown is a call to shutdown a socket...
>
>teams are what beos calls threads under a particular process, if that makes
>it any clearer :)  Look in the bebook!

Makes sense. Thanks! :)

>>
>> >Would be Nice To Haves
>> >
>> >- IPv6
>>
>> I'm definitely interested in this, as well as a few other IP specs such as
>> bridging and tunneling using a few different methods(especially IPSec!).
>> I think BeOS already did NAT?
>
>Yes, but I think we need to look at that.  It would be cool to add
>hooks/support for pf as well...

Definitely some form of packet filtering.  Is there a tcpdump for BeOS 
currently?

>> Now, I don't have a lot of experience with deep OS stuff, but wouldn't it
>be
>> possible to have a set of 'emulation' libraries or something, which could
>be
>> written on top of our OpenBeOS library in order to provide binary
>compatibility,
>> but still let us advance R1 in small ways?
>
>I guess so.  I wouldn't be interested in writing them, but no doubt some
>other people in need of self flagellation will be.

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

Other related posts: