The Drawbridge[1] stuff is pretty interesting looking. I really wish MS would ship a simple sandboxing solution, so I can run arbitrary binaries and restrict them. The new Metro app stuff is cute, but doesn't help with the millions of existing binaries. Nor does it seem very user-friendly or useful, for that matter.<p>1: <a href="http://research.microsoft.com/en-us/projects/drawbridge/" rel="nofollow">http://research.microsoft.com/en-us/projects/drawbridge/</a>
This is fascinating :-) I was wondering if they leveraged their environment subsystem framework - nice to have this confirmed!<p>A long time ago I wrote the Wikipedia article on the architecture of Windows NT. It obviously needs an update, but I think it's still quite relevant and explains in a vastly simplified manner how Windows Fitz together.<p>It can be found here:<p><a href="https://en.m.wikipedia.org/wiki/Architecture_of_Windows_NT" rel="nofollow">https://en.m.wikipedia.org/wiki/Architecture_of_Windows_NT</a><p>There is a block diagram that I think is also helpful:<p><a href="https://en.m.wikipedia.org/wiki/Architecture_of_Windows_NT#/media/File%3AWindows_2000_architecture.svg" rel="nofollow">https://en.m.wikipedia.org/wiki/Architecture_of_Windows_NT#/...</a>
It's interesting that this was enabled by the Drawbridge work. I was somewhat under the impression that Drawbridge was dead and/or superseded by other container-related projects. It's often weirdly hard to find out what's going on with some particular Microsoft project or technology, even for those of us who are employees. I was pretty excited about Drawbridge ~3 years ago when I was working with it but it subsequently seemed to have vanished.
While this is an interesting technical overview, could anyone give me an idea of how to reinstall lxrun? The blasted thing doesn't work for me anymore and there's basically no documentation on how to fix it other than reinstalling Windows 10. Yes, I've tried lxrun /uninstall /full followed by lxrun /install.<p>Edit: in fact, I think the problem with my installation has to deal with Windows' NTFS not natively being capable of understanding the lxss file attributes...
> The primary role of SUA was to encourage applications to get ported to Windows without significant rewrites.<p>Is this a supported use of the Linux subsystem?<p>Running native Linux apps directly is great if it works but there are going to be cases where the app would 99% work except for that one thing Linux has and the Linux subsystem doesn't. Maybe Microsoft doesn't provide a tun/tap driver so you need to use TAP-Windows.<p>It would be convenient to be able to change only that without having to worry about the subtle differences in the Windows version of inet_ntop() and the call to make a socket non-blocking and that Unicode on Windows is UTF-16 instead of UTF-8 and so on.
I tried to use bash on my windows machine... signed up for insider preview etc.<p>My machine consistently states a restart will force an update that will allow me to use bash, but it doesn't happen.<p>I gave up and went back to my ubuntu.