Linked by Thom Holwerda on Mon 19th Mar 2007 00:25 UTC, submitted by Z98
ReactOS The latest ReactOS newsletter is out. "Reactions have varied in regard to 0.3.1, though one response was consistent. The difficulty in getting it to work on real hardware. As mentioned many times, 0.3.1 was branched in the middle of a kernel rewrite."
Thread beginning with comment 222456
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Real hardware Issue
by Coviti on Mon 19th Mar 2007 01:32 UTC in reply to "Real hardware Issue"
Coviti
Member since:
2006-07-15

>OK sure, ReactOS is getting to the stage that major >jumps have to be done to go to the next stage of >it's evolution (for lack of a better word) and many >of other OS's have had to go though the same thing, >but why not hang back for a few more weeks until >this was sorted before committing?

The release was already about two months late, and most critical bugs had been fixed. The 0.3.1 branch was also getting old in relation to trunk, so further delays would have caused even more merging issues between the two.

>Just one question to anyone out there who might >know: Is there a general rule that nothing can be >taken from the Linux / BSD code base?

Absolutely not. From what I understand, ReactOS' (and windows' as well) TCP/IP implementation is borrowed from FreeBSD. Basically, ReactOS's audio architecture has to be compatible with windows's, which linux or BSD is not.

(Anyone care to correct the numerous technical errors I've no doubt made? :p)

Edited 2007-03-19 01:34

Reply Parent Bookmark Score: 1

RE[2]: Real hardware Issue
by rayiner on Mon 19th Mar 2007 02:41 in reply to "RE: Real hardware Issue"
rayiner Member since:
2005-07-06

NT's TCP/IP stack is not borrowed from FreeBSD's. It had at one point a BSD-derived stack, and still ships with some BSD-derived tools, but the stack was rewritten for NT 3.5.

EDIT: Linky - http://www.kuro5hin.org/?op=displaystory;sid=2001/6/19/05641/7357

Edited 2007-03-19 02:44

Reply Parent Bookmark Score: 4

RE[3]: Real hardware Issue
by ameasures on Mon 19th Mar 2007 09:30 in reply to "RE[2]: Real hardware Issue"
ameasures Member since:
2006-01-09

The TCP/IP stack may have been rewritten for NT3.5; however the NT4 stack was problematic for heavy network use and the Windows 2000 TCP/IP stack fingerprinted as a BSD stack....

Times have changed.

Personally I think it would be great if a shared driver model allowed well written drivers to be shared across the range of open source operating systems.

Reply Parent Bookmark Score: 4