Linked by Thom Holwerda on Mon 17th Aug 2009 09:34 UTC, submitted by moochris
Thread beginning with comment 379048
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
It means I know what I'm talking about (I do)...
Please, help make Haiku better by submitting patches to:
http://dev.haiku-os.org
We will then all believe you.
"It means I know what I'm talking about (I do)...
Please, help make Haiku better by submitting patches to:
http://dev.haiku-os.org
We will then all believe you.
" I guess you missed the part where I said I was.
the PCNetII driver locks up, and I know why (this is the patch I was talking about.) Generally, that driver is extremly badly written and serves as another example.
Just to set this straight: The PCNetII driver that is present in Haiku is an unmodified copy of the FreeBSD driver (originally it is a NetBSD one though). It is one of the network drivers that make use of the FreeBSD network compatibility layer to use unmodified FreeBSD sources. The copy in our repository is two years old now and should most probably be updated. In any case, this driver does obviously not reflect the quality of the Haiku code base.




Member since:
2009-08-17
Uh, ok. It sure sounds like it thought.
Not really. It means I know what I'm talking about (I do). To be clear: I have tried Haiku on two physical machines, along with VMWare. In VMWare with a two-cpu setup on my core2duo, the PCNetII driver locks up, and I know why (this is the patch I was talking about.) Generally, that driver is extremly badly written and serves as another example.
The code as a whole doesn't necessarily suck, but there are serious issues with the subsystems I have looked at regard security and stability. I can provide details why your TCP/IP stack is full of holes in both those camps (and I intend to submit this as PR's.)
Edited 2009-08-17 16:56 UTC