To view parent comment, click here.
To read all comments associated with this story, please click here.
TinyKrnl is clearly a copyright violation, by Alex's own admission. Nobody has permission to distribute Microsoft's code in any form except for Microsoft, yet TinyKrnl is doing just that. I'd expect Microsoft's legal department to be interested.
Secondly, Alex, a self admitted "good reverser", has been working on ReactOS for two years prior to turning to TinyKrnl, what do you think he's been doing? Shouldn't you be auditing Alex's ReactOS patches first in your code audit?
Rather than censoring emails, pointing the finger back here and putting your head in the sand about Alex's dubious code, why not fix the problem? Is it because you're not willing to take propper action that would "which would remove most of ReactOS's recent kernel code in the last 2 years"?
Perhaps there's more than just Alex's 2 years worth of "work" in there that is problematic?
We are auditing everyone's code (except shared with Wine, responsibility on which is on Wine and not ReactOS) - this is the only fair solution. How would you feel if Wine/CW send an auditing questionnaire only to you and another dev? Wouldn't it be a little suspicious?
Wine is really putting the head in the sand, because it doesn't let ANY information about audit out. ReactOS instead has a full transparency (what I am proud about). You could read up each file's history: why, who, and when considered it as a legally-clean code. We have even per-function documentation of some kernel files too, in SVN repository.
Also, if you care that much about our legal ground (which I greatly appreciate), then you would just come to us and speak with us, I would be your best friend in this work. We could review Alex's code together, and see what's good, what is not.
It's a lot more pleasant and useful thing to do than writing lying posts to the forum.







Member since:
2006-07-15
And your point is what exactly? TinyKRNL is a Windows Kernel documentation project. TinyKRNL shares no, and I repeat -NO- code with ReactOS.
And, btw, mike_m in his attempts to shine a bad light on ReactOS, has quoted Alex_Ionescu out of context. Here is a link to the full conversation (In case anybody is interested in the truth, rather than propaganda).
http://pastecode.com/1515
One only needs to search the Wine Mailing list archives or join their IRC channel to see that they are clearly lying about their own use of Reverse Engineering, and fabricating lies about ReactOS.
I will leave that up to the readers.