Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #690525 > unrolled thread

Microsoft Open-Sources WSL2

Back to article view | Back to comp.os.linux.advocacy

Contents

  Microsoft Open-Sources WSL2 Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-05-20 00:17 +0000
    Re: Microsoft Open-Sources WSL2 Paul <nospam@needed.invalid> - 2025-05-19 22:11 -0400
      Re: Microsoft Open-Sources WSL2 "Bill Bradshaw" <bradshaw@gci.net> - 2025-05-20 08:18 -0800
    Re: Microsoft Open-Sources WSL2 🇵🇱Jacek Marcin Jaworski🇵🇱 <jaworski1978@adres.pl> - 2025-05-20 05:12 +0200
    Re: Microsoft Open-Sources WSL2 Chris <ithinkiam@gmail.com> - 2025-05-20 06:50 +0000
      Re: Microsoft Open-Sources WSL2 Paul <nospam@needed.invalid> - 2025-05-20 09:46 -0400

#690525 — Microsoft Open-Sources WSL2

Windows Subsystem for Linux (WSL2) is the hacked-up pile of glue code
that lets a Linux kernel run on a Windows installation. Now Microsoft
is open-sourcing (nearly) all of that.

<https://www.theverge.com/news/669286/microsoft-windows-subsystem-for-linux-open-source>

So, do you think this is a good sign or a bad one, in terms of the
future of WSL2 and Windows itself? I see that the GitHub repo already
has about 1000 open issues ...

[toc] | [next] | [standalone]

#690529

On Mon, 5/19/2025 8:17 PM, Lawrence D'Oliveiro wrote:
> Windows Subsystem for Linux (WSL2) is the hacked-up pile of glue code
> that lets a Linux kernel run on a Windows installation. Now Microsoft
> is open-sourcing (nearly) all of that.
> 
> <https://www.theverge.com/news/669286/microsoft-windows-subsystem-for-linux-open-source>
> 
> So, do you think this is a good sign or a bad one, in terms of the
> future of WSL2 and Windows itself? I see that the GitHub repo already
> has about 1000 open issues ...
> 

We don't have any documentation for how it works, so it is hard
to make a comment about "what has been given away". for example,
if I installed a Linux Guest as a Guest of the Inverted Hypervisor,
how would that differ from how a Linux kernel would normally get
to run on W10/W11 ?

Even VirtualBox, does not do its own virtualization any more.
It uses the Hypervisor, and your Guest runs on the Hypervisor,
not as a VirtualBox instance. VirtualBox had to add code, so VirtualBox
would be "allowed" to run on W10/W11. That's why the installer stopped
at one point, and I had to replace VBOX 5 with VBOX 6, just so I would
be allowed to finish a Windows Upgrade run.

The scheme could be made more complicated, by some sort of additional
partitioning story. So if anything, what is going on in WSLg is more
interesting that what is going on in WSL2. You probably won't get open
source for WSLg.

The first Terminal Services rootless windows that I know of, was
on WinXP Mode on Windows 7 which uses a special version of VirtualPC.
VirtualPC had Terminal Services added, and the WinXP image talked
to Terminal Services. If you installed any "ordinary" Guest OSes
on the special version of VirtualPC, there was graphical instability
noted. I even had a Guest crash once, because the instability was
too much at one point. What is done in WSLg, bears some similaries,
but the difference is, there's none of the flashing and blinking
that was going in in WinXP Mode. The WSLg stack is not hardware
accelerated, so it's like a MESA fallback code in some ways. And the
Terminal Services is a layer of gravy on top or something.

But unless we see an updated diagram (it would be *very* complicated),
we won't have confirmation of how any of it works. There is one diagram showing
how an Inverted Hypervisor works, and you then have to use your vivid imagination
to guess how various things (the Sandbox) are shoehorned into the framework.

   Paul

[toc] | [prev] | [next] | [standalone]

#690572

Paul wrote:
> On Mon, 5/19/2025 8:17 PM, Lawrence D'Oliveiro wrote:
>> Windows Subsystem for Linux (WSL2) is the hacked-up pile of glue code
>> that lets a Linux kernel run on a Windows installation. Now Microsoft
>> is open-sourcing (nearly) all of that.
>>
>> <https://www.theverge.com/news/669286/microsoft-windows-subsystem-for-linux-open-source>
>>
>> So, do you think this is a good sign or a bad one, in terms of the
>> future of WSL2 and Windows itself? I see that the GitHub repo already
>> has about 1000 open issues ...
>>
>
> Even VirtualBox, does not do its own virtualization any more.
> It uses the Hypervisor, and your Guest runs on the Hypervisor,
> not as a VirtualBox instance. VirtualBox had to add code, so
> VirtualBox
> would be "allowed" to run on W10/W11. That's why the installer stopped
> at one point, and I had to replace VBOX 5 with VBOX 6, just so I would
> be allowed to finish a Windows Upgrade run.
>

I have VirtualBox 7.18 installed and am running several operating systems 
including Win 11 and I do not have any of the Hyper stuff enabled.  I am not 
looking forward to having to convert to Win 11.
-- 
<Bill>

Brought to you from Anchorage, Alaska 

[toc] | [prev] | [next] | [standalone]

#690536

W dniu 20.05.2025 o 02:17, Lawrence D'Oliveiro pisze:
> I see that the GitHub repo already
> has about 1000 open issues ...

But on the other hand, quote: "Closed 10 395".

[toc] | [prev] | [next] | [standalone]

#690541

Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
> Windows Subsystem for Linux (WSL2) is the hacked-up pile of glue code
> that lets a Linux kernel run on a Windows installation. Now Microsoft
> is open-sourcing (nearly) all of that.
> 
> <https://www.theverge.com/news/669286/microsoft-windows-subsystem-for-linux-open-source>
> 
> So, do you think this is a good sign or a bad one, in terms of the
> future of WSL2 and Windows itself? I see that the GitHub repo already
> has about 1000 open issues ...

In the first instance it is a good thing, however, it may indicate that MS
is going cease/ slow down development and let it become a "community"
project. Probably because it hasn't been able to monetise WSL. 

[toc] | [prev] | [next] | [standalone]

#690565

On Tue, 5/20/2025 2:50 AM, Chris wrote:
> Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
>> Windows Subsystem for Linux (WSL2) is the hacked-up pile of glue code
>> that lets a Linux kernel run on a Windows installation. Now Microsoft
>> is open-sourcing (nearly) all of that.
>>
>> <https://www.theverge.com/news/669286/microsoft-windows-subsystem-for-linux-open-source>
>>
>> So, do you think this is a good sign or a bad one, in terms of the
>> future of WSL2 and Windows itself? I see that the GitHub repo already
>> has about 1000 open issues ...
> 
> In the first instance it is a good thing, however, it may indicate that MS
> is going cease/ slow down development and let it become a "community"
> project. Probably because it hasn't been able to monetise WSL. 
> 

The team who did that project are pretty sharp.

And not to be wasted by sitting on their ass.

If there is no one working on Visual Studio right now,
why would there be someone working on WSL2 ? It's all
pretty now, has a command line utility for install and
launch, and has recently incorporated a couple more distro.
There may be a maintenance person, but the people who set up
up and tuned it in only one week, they're in the AI department
now, making "Vibes for Clippy" or something.

They could add hardware acceleration, to the WSLg graphics
stack. But what are the odds of that happening ?

   Paul

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.advocacy

csiph-web