Linked by Thom Holwerda on Thu 28th May 2009 12:08 UTC, submitted by lemur2
Linux There are several ways to run Windows programs on Linux (virtualisation, WINE) and vice versa really isn't a problem either with Cygwin, or better yet, native ports thanks to the Windows variants of Gtk+ and Qt. Still, what if Windows support was built straight into the Linux kernel? Is something like that even possible? Sure it is, and the Chinese figured it'd be an interesting challenge, and called it the Linux Unified Kernel.
Thread beginning with comment 365784
To read all comments associated with this story, please click here.
by werfu on Thu 28th May 2009 14:03 UTC
Member since:

I think it would be much more easier, well if somebody know how to do it, to add a Linux-personality to the NT kernel than adding the whole NT kernel to Linux. Its a bit like the Linux personality for the Mach kernel

Reply Score: 1

RE: NT-Personality?
by Xaero_Vincent on Thu 28th May 2009 14:19 in reply to "NT-Personality?"
Xaero_Vincent Member since:

That has already been done with coLinux and there are there are several distributions that support coLinux.

Reply Parent Score: 2

RE[2]: NT-Personality?
by lemur2 on Thu 28th May 2009 23:20 in reply to "RE: NT-Personality?"
lemur2 Member since:

That has already been done with coLinux and there are there are several distributions that support coLinux.

LUK would be a sort-of "inverse coLinux", wherein Linux was the core OS and the NT kernel extensions were the tacked-on bits.

The major, major difference in these approaches would be that LUK would still give you an open source kernel, whereas coLinux only gives you the Linux add-ons as open source.

That has major implications from a licensing perspective. You would no longer require a Windows license to be able to run applications designed for Windows. You wouldn't have to put up with WGA. There wouldn't have to be a "Windows Update" backdoor. Updates to LUK itself could be delivered via Linux distribution repositories.

Finally, software vendors who wanted to easily extend their customer base could prepare additional (binary only if they wanted) repositories for their applications (without having to re-write anything), so that all applications on LUK machines could still auto-update via the one updater.

Edited 2009-05-28 23:34 UTC

Reply Parent Score: 3