4 ms·
Wine and ReactOS are practically sister-projects at this point that share a ton of code. ReactOS does replicate the NT Kernel, so in theory (if it ever gets th
by dragontamer 9y ago
Wine and ReactOS are practically sister-projects at this point that share a ton of code.
ReactOS does replicate the NT Kernel, so in theory (if it ever gets there), ReactOS would be able to run Windows Drivers. IE: the "real" NVidia and AMD Drivers or any other kernel-level drivers that exist in Windows land.
These days, AMD (and even NVidia) have decent Linux drivers. And WiFi drivers have Windows->Linux translators as well. But full compatibility to any Windows binary (including device drivers) is certainly a noble goal. There are a lot of little hardware devices that are written for Windows only (ie: specialized medical equipment, CAM / CNC Mill programs, etc. etc.) ReactOS would allow a smooth transition to Open Source if they achieve their goals.
------------
EDIT:
It should be noted that there are a ton of Windows OS-level details that Microsoft does much better than Linux too. IE: I'd argue that Microsoft's security model (SIDs + ACLs) is superior to Unix-style Users + Groups. A large group of open-source developers who strongly understand the low-level internals of Windows is certainly a good thing in any case.
- finchisko 9y agoLinux has ACL too.
- mkesper 9y agoYou know you can use ACLs on Linux kernels and filesystems? https://wiki.archlinux.org/index.php/Access_Control_Lists https://wiki.archlinux.org/index.php/Access_Control_Lists
- dragontamer 9y agoYeah. But Windows NT's ACL is kernel level and applies to any object that the NT kernel can make. (aka: anything with a "Handle" can be controlled with Window's security core). MMaps (called "Sections" in Windows), Threads, Processes, Mutexes, and more are covered by Window's ACL security model. Even then, ACLs are just part of the picture. Windows NT's "SID" system for identifying user permissions is far more flexible than users / groups. WinVista and later also adds mandatory access control on top of that, in particular event logging / auditing guaranteed by the kernel and "integrity levels". Anything that is "drive by downloaded" by Chrome for example has an integrity level of "untrusted" and thus is locked out of all kernel objects. (IE: "untrusted" integrity in Windows prevents access to files, processes, threads, mmaps, all services, etc. etc.). ---------- Linux's security model is too weak to be used in a modern operating system. That's why Google extended it with all of the Android App stuff. Android's security model is closer to what modern Windows can do. And if you know anything about Android (despite being built on top of Linux), its security model is quite different. Windows basically offers Android-level security at the kernel level. (maybe a bit more: major services on Windows, such as LSASS aka Login / Password service, can run in an isolated VM for example)
- amaccuish 9y agoYes but it certainly isn't as flexible and for networking computers requires ensuring uids and gids don't clash with local users. There's talk of replacing posix acls with nfs4 acls, which were modelled on Windows ACLs.