[openbeosnetteam] Re: Progress report

  • From: <dreid@xxxxxxxxxxxx>
  • To: openbeosnetteam@xxxxxxxxxxxxx
  • Date: Thu, 14 Mar 2002 16:35:07 -0000 (GMT/BST)

<snip>

> Next step: install BeOS into my office computer, and try to hide this 
> fact 
> to the sysadmin... :-)

Hmmm, that'll be fun!

> 
>> will i need a "normal" BeOS 5.03 install to test this ? (ie not BONE) 
> 
> As we don't base the new network stack code on any previous BeOS net 
> stuffs, 
> it should works same in vanilla BeOS (R5.0.x) and BONified BeOS 
>systems.
> Compilation, however, may have some difference, because of differents 
> public include files/path...
> 
> The only problem I could see is the select() support offer by the 
> kernel.
> Manuel Jesus Petit de Gabriel, former BeOS kernel engineer tell me 
> that, 
> if he recall correctly, the vfs select implementation in vanilla r5 has
>  some memory 
> corruptions bugs, which were fixed for BONE. It could have impact the 
> stability 
> of our select() support for sockets with the vaniall kernel. 
> We will see...

Oh. Well, what does the select() hook in the driver do anyways? If it 
passes calls into our stack there shouldn't be any issues...

> 
> Some here code under R5.0.x (David, I guess), others have BONE (you, I 
> guess! ;-) ), 
>some have both (me). Same things for SMP hardware machines.

I have both as well, though my laptop (BONE) only has one NIC unless I add 
my wireless card.

david


Other related posts: