Live data from Hacker News

Windows Subsystem for Linux Architectural Overview

blogs.msdn.microsoft.com

11–20 of 43 posts

Re: Windows Subsystem for Linux Architectural Overview

#11
post #8

Earlier quoted context omitted.

I created an account just to reply to this. You said, "It's often weirdly hard to find out what's going on with some particular Microsoft project or technology..." I was just thinking that very thing today. Why is that?

It's not as bad as Amazon, apparently. I've known people there who say everything is compartmentalized. At Microsoft, it's typically only the bleeding edge stuff they keep secret internally.

I'd be interested in specifics on either side.

Re: Windows Subsystem for Linux Architectural Overview

#13
post #6

Earlier quoted context omitted.

Delete the directory. And don't touch it from the Windows side ... don't copy anything into it. It's definitely early alpha quality.

By delete, do you mean I can delete %APPDATA%\Local\Lxss from the Windows side? I don't think that will work, as I've already tried that.

Have you stopped lxssmanager?

https://msdn.microsoft.com/en-us/commandline/wsl/faq#how-do-...

Re: Windows Subsystem for Linux Architectural Overview

#15
post #12

I tried to use bash on my windows machine... signed up for insider preview etc. My machine consistently states a restart will force an update that will allow me to use bash, but it doesn't happen. I gave up and went back to my ubuntu.

Not to be a dick, but you're probably not doing it correctly. It asks you to reboot on the spot, for one. When I first tried to do it, I couldn't figure it out without instruction. It's a fairly long process considering it's just a simple item. It should be as easy as switching on Hyper-V...but it's not. Granted it's still in beta.

http://www.howtogeek.com/249966/how-to-install-and-use-the-l...

Re: Windows Subsystem for Linux Architectural Overview

#16
post #12

I tried to use bash on my windows machine... signed up for insider preview etc. My machine consistently states a restart will force an update that will allow me to use bash, but it doesn't happen. I gave up and went back to my ubuntu.

I've had the update issue with a "normal" Windows 10 installation (upgraded from 7 without reinstall, which went well, seemingly). It always found updates but then failed (silently) to install them, and so on.

Re: Windows Subsystem for Linux Architectural Overview

#17
> The primary role of SUA was to encourage applications to get ported to Windows without significant rewrites.

Is this a supported use of the Linux subsystem?

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.

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.

Re: Windows Subsystem for Linux Architectural Overview

#18

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. 1: http://research.microsoft.com/en-us/projects/drawbridge/

A UWP sandboxing solution was demoed at Build this year and will ship as part of the Anniversary Update (SDK?). Apparently even Age of Empires II worked under it.

Re: Windows Subsystem for Linux Architectural Overview

#19
post #17

> The primary role of SUA was to encourage applications to get ported to Windows without significant rewrites. Is this a supported use of the Linux subsystem? 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-Win…

Microsoft are insane about providing compatibility when it suits them. It will work - if they see a business case for it.
Post reply on HN