5 ms·

Instead of exposing students to Windows kernel code[1], it would be better to consider to read the ReactOS source code - an open source clean room re-implementa

• iso8859-1 13y ago
  Is the ReactOS kernel clean?
  • frik 13y ago
    Read the comment above by coldpie about WineHQ project. The same is true for the ReactOS project. In 2006, an overenthusiastic contributor caused troubles. The aftermath slash back the project for several months and stressed the relationship with Wine for some time. Since then, every possible effort is made to keep the code clean and disallow tainted developers. (that's why I wrote the comment above, to warn others) You can read a short summary on Wikipedia: http://en.wikipedia.org/wiki/ReactOS#Internal_audit http://en.wikipedia.org/wiki/ReactOS#Internal_audit
  • jeditobe 13y ago
    Yes, it is clean 100%
• scott_karana 13y ago
  I had the impression that the Win2000 code he's talking about was the leaked source code. I didn't know the Microsoft source NDA was so evil though; good warning. :)
  • _wmd 13y ago
    Microsoft have been making their source code available to academia to study for at least a decade.
    • 4ad 13y ago
      Yes, this program started a long time ago. Unfortunately, I was under the impression that it stopped not so long ago (~1year)?
• 4ad 13y ago
  There is no single NDA, all NDAs are different. The NDAs I've managed to negotiate regarding this issue have no such clauses. That being said, you are right that this is a valid concern and people should be careful.
  • coldpie 13y ago
    Over at the Wine project, we forbid contributions from anyone known to have looked at Windows source code or even done significant "white box" reverse-engineering (decompiling, etc). The intellectual property law landscape is far too frightening to be worth the risk of allowing contributions from "tainted" individuals.
    • userbinator 13y ago
      Statements like these are "legally reassuring" but it's very likely that you can get the same functionality but implemented very differently even if you looked at Windows' code. In the end it's probably another thing like piracy: everyone does it, but few would admit.
• pjmlp 13y ago
  Also read the "Inside Windows" book series, they are full of valuable information.
  • sixothree 13y ago
    Do you know the author or have a link to the book?
    • pjmlp 13y ago
      The original author was Mark E. Russinovich from "Sysinternals fame", nowadays other developers continue the new editions. http://www.amazon.com/Windows-Internals-Edition-Developer-Reference/dp/0735648735/ref=sr_1_1?ie=UTF8&qid=1397068554&sr=8-1&keywords=Windows+Internals http://www.amazon.com/Windows-Internals-Edition-Developer-Re... http://www.amazon.com/Windows-Internals-Edition-Developer-Reference/dp/0735665877/ref=sr_1_2?ie=UTF8&qid=1397068554&sr=8-2&keywords=Windows+Internals http://www.amazon.com/Windows-Internals-Edition-Developer-Re... Additionally the books for user mode programming from Jeffrey Richter and Charles Petzold tend to be quite good and full of valuable information as well.
      • sixothree 13y ago
        Thank you.
• fulafel 13y ago
  A NDA'd operating systems course where you had to submit to Microsoft, I'd love to see the headlines...