FreeLists / openbeosnetteam / [openbeosnetteam] Re: libbind.so status

["Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx>]

Hi,

> > Unfortunately, there are more problems to solve:
> > 
> > Ping resolved the host name correctly, but then it tries to send an 
> > IP packet with most values set to zero (version and header length are 
> both zero, for example, although they should be 4 and 5, respectively).
> 
> Is it a new bug?
> We never saw this behavior before, right?

Yes, it worked before my commit. This is due to all our tools now linking 
against libsocket and libbind.

> > I'd bet we have some places in our source that use immediate values 
> > instead of constants and after I changed our headers to be more BONE-
> like (for example: our shutdown() constants were different from ours) 
> they are wrong, too. The route bin command used shutdown(sock, 0), 
> although it should have been shutdown(sock, SHUTDOWN_RECV).
> 
> Well, in fact in POSIX sys/socket.h standard, it should be SHUT_RD, not 
> SHUTDOWN_RECV:
> http://www.opengroup.org/onlinepubs/007904975/basedefs/sys/
> socket.h.html

Oh, then BONE has wrong names here. I will add the other constants, too.

> But SO_NONBLOCK is a BeOS R5-specific socket option when 
> SO_BINDTODEVICE is a BONE-specific one...
> Anyway, there is a real mess on non blocking mode support in the stack, 
> that right.
> Several confusion between file descriptor FIONBIO ioctl() opcode, BeOS 
> specifig B_SET_[NON_]BLOCKING_IO opcode and SO_NONBLOCK...

And we cannot remove three of them? :)
I saw SO_NONBLOCK in the BONE socket.h header, so I put into ours, too.

> > Let's make our netstack a complete BONE replacement until Waltercon 
> > (stability does not matter, only functionality-wise).
> 
> Again... what!?
> When is WalterCon already? In June, right?
> 
> There's still several BONE features missing, like DHCP, BoneYard, 
> libpcap support, and boot network configuration...
> And... there is some choice to make before.
> I know I'm not enough active, but we didn't even discuss about the best 
> way to bring both R5 and BONE compatibility, I was expecting we could 
> find a cleaner way than duplicating code.
> Anyway...

Okay, a more realistic aim: Get Mozilla for BONE working with our netstack. 
This would be cool.

> > Every time I put such a cool task up you run away like Philippe. ;) 
> 
> Eh eh, they've learn from the best... runner away.
> Sorry, can't resist.

:)

> > Philippe, where are you? I thought you have time now. 
> 
> I thought too. But in fact I only have one or two hour max per day, not 
> very enough to dive deep in code.
> I forgot how time consuming/wasting can be job. It's even worse when 
> they're not paid.

Yes, that's the huge problem here. We need donations to get some full-time 
programmers.

> I understand you can feel a loonely coder. But, as in the past, every 
> time one is highly productive, the others can follow him, even if they 
> would have find time to try.

As you can see it did not work as expected. ;)

Bye,
Waldemar