Microsoft Open Source Tool Lets You 'Bring Your Own Linux' To Windows (microsoft.com)

Long-time Slashdot reader Billly Gates writes: Debian is now available in the Windows app store. It joins Ubuntu, Suse Leap, SuSe enterprise, and Kali Linux for those who cannot or do not want to bother with a virtual machine or a full install of the OS. However, it included stable 9.3. 9.4 is available from the repository if you run apt-get update and apt-get upgrade.
"Fedora is not yet available, although Microsoft has stated openly that it is working to make it so," reports Computer Weekly. And there's more: Microsoft has also provided an open source tool called Microsoft WSL/DistroLauncher for users who want to build their own Linux package where a particular distribution is either a) not available yet or b) is available, but the user wants to apply a greater degree of customisation to it than comes as standard.

Comments

Missing Linux Feature: Seamless OS Crossing

[rea1l1]

I'd really appreciate the ability to switch between OSes like I can virtual desktops. Modern hardware certainly supports this potential.

I hope someone within the Linux community returns with a competing feature, enabling a seamless OS transition, founded upon Linux, an OS that doesn't invade your privacy, while eventually providing additional sand boxing & integration features around Windows, locking it into it's own little garden.

Could an authentic Microsoft Windows installation be forced into becoming a mere compatibility layer built on top of Linux?

The best of both worlds: Windows compatibility coupled with Linux security.

Permissions?

[BronsCon]

Have they fixed permissions mapping when accessing files on the Windows partition yet? If so, I'm excited for the update, because it's an issue I deal with daily.

Their excuse is that they don't want to change Windows ACLs, and that's fine, I get that, but it's a poor excuse; WSL applies 0777 to all Windows files currently and, to add to it, doesn't seem to use Windows ACLs for the files within the lxss directory, which strongly implies that they're already storing Linux file permissions as metadata elsewhere, which is what they should be doing for Linux file permissions for Windows files -- defaulting to values mapped from Windows ACLs, of course.