News for hackers. Stuff that matters.
Re:Microsoft's Linux Kernel by SteveNuts on Friday June 28, 2019 @07:18PM (#20309623)
WSL version 2 uses the Hyper-V Virtualization API but is not a VM.

The first version of WSL is just another process in task manager, with all the syscalls and filesystems emulated.

Re:Microsoft's Linux Kernel by chrismorgan on Friday June 28, 2019 @08:58PM (#20310089)
Well, each WSL1 process is a Windows process. If you’re running vim in bash, for example, you’ll see “vim” and “bash” as separate processes in Task Manager. WSL is all about ELF binaries natively, just as Win32 runs PE executables natively.
Re:Microsoft's Linux Kernel by kevingadd on Friday June 28, 2019 @10:03PM (#20310345)
"windows process" is misleading, WSL uses a separate "linux subsystem" with its own syscalls, process/thread data structures, etc. It also uses its own file system (albeit with all the state stored in NTFS and affected by filter drivers, which is why its I/O is slow)
Re:Microsoft's Linux Kernel by chrismorgan on Saturday June 29, 2019 @01:27AM (#20310945)
They are Windows processes, just as the Win32 subsystem also spawns Windows processes.
Re:Microsoft's Linux Kernel by dblohm7 on Saturday June 29, 2019 @08:09PM (#20315626)
Probably best to refer to them as NT processes for the sake of clarity.
Re:Microsoft's Linux Kernel by chrismorgan on Sunday June 30, 2019 @02:52AM (#20316778)
True, I thought that a few hours after I wrote my last comment but couldn’t update it by that point and didn’t respond to it. Windows NT is the kernel, Win32 is the Windows subsystem that everyone’s used to (including kernel32.dll), WSL is a subsystem that runs ELF binaries and implements the Linux syscalls. It’s not yet obvious to me how much WSL2 is actually even a Windows subsystem, given that it’s running it as an actually separate OS.