We are happy to announce that we have open sourced a WSL (Windows Subsystem for Linux) sample for Linux distribution maintainers. This sample allows distro maintainers to build WSL distro packages for the Microsoft Store and developers to create custom Linux distro packages for sideloading.
SSH is one of the most important tools in the *NIX world, through which users communicate with shells, applications, and services running on remote machines, devices, VM’s and containers. Windows users most often remotely access Windows machines, devices, VM’s and Containers via the amazingly powerful Remote Desktop Protocol (RDP) which,
Hey WSL users—we have more features to share with you! Our latest Windows Insider build lets you share environment variables between WSL and Windows. Starting with Build 17063, let’s look at how you can leverage the new “WSLENV” to enhance environmental variable interop between Win32/WSL.
Beginning in Insider Build 17063, you’ll be able to use the unix socket (AF_UNIX) address family on Windows to communicate between Win32 processes. Unix sockets allow inter-process communication (IPC) between processes on the same machine.
Support for the unix socket has existed both in BSD and Linux for the longest time,
There are a variety of ways to invoke the Windows Subsystem for Linux from Windows commandlines and they all behave a little differently. Let’s get to the bottom of it.
The first (and recommended!) method will start up your default distro.
Dear friends of WSL (Windows Subsystem for Linux, nee “Bash on [Ubuntu on] Windows”) & Windows Console:
I would like to share with you some changes to our org’ that will benefit WSL, Windows Console and the Windows command-line in general moving forward.
With Windows 10 Fall Creators Update (FCU) releasing on October 17th 2017, we thought it time to post the list of improvements coming to Windows Console in FCU.
Note: For fans of our sister project, Windows Subsystem for Linux (WSL), please also read our post on “What’s New in WSL in FCU“.