Today we’re very excited to announce the open-source release of the Windows Subsystem for Linux. This is the result of a multiyear effort to prepare for this, and a great closure to the first ever issue raised on the Microsoft/WSL repo:
Great! With this source code out, I can finally complete the port to Linux. I call it WSL24L, aka “Windows Subsystem For Linux 2, For Linux”
Do you name every FOSS project? This is uncannily close to what an actual open source project would be called, including the logic behind it.
Nah, needs more recursion. The ‘W’ in “WSL” stands for “WSL”
I still will never understand why it’s not called Linux Subsystem for Windows.
There’s a trademark for Linux so Microsoft can’t name a product starting with Linux.
So they can use Linux in the name, just not at the beginning? We’re so stupid. Can they do Windows Subsystem for Coke? Or Windows Subsystem for McDonald’s? Or Windows Subsystem for MacOs?
Good gravy.
Disney presents Good Gravy®️
Good Gravy®️ Presentation for Disney
Don’t you think this is another Embrace, Extend, and Extinguish strategy from Microsoft?
It could be another Embrace, Extend, and Extinguish strategy from Microsoft, because if the increase in Linux user share leads to an increase in malware, most of those users aren’t experts.
So there will be an increase in antivirus software for Linux, but that will also lead to DRM in Linux, and Linux may become what I swore to destroy. While BSD distributions, Redox OS, and other systems take over to become the new Linux as it was in its beginnings.
but… you need to run it on microsoft, which isn’t open source…
Only right now. I’m sure someone will have it running on Wine or Proton by next week. Steamdeck subsystem for proton for Windows subsystem for linux
brb running vim on windows subsystem for linux on proton on wine on linux.
Just to confuse any computer virus.
I don’t understand this.
Does this mean Windows programs and exe files will now run natively on linux?
Edit: unclear why someone asking a question gets a 50/50 downvote to upvote response…
“OOOOHHHH!!! THIS GUY DOESN’T KNOW ALL THE THINGS I KNOW!!! BOOOOO!!!”
In my view it’s a Linux subsystem for Windows.
Why the name is the other way around, I’ll never understand.
The original WSL doesn’t use the Linux kernel at all, it’s a Windows Subsystem for compatibility with Linux. WSL2 actually visualizes a complete Linux kernel, but the name stuck.
The original WSL DOES use the Linux kernel. Which runs as a native NT process (there’s a huge difference between NT and Win32 processes). But porting a Linux kernel into the NT binary is a maintenance nightmare, it’s much easier to run the original in a slim VM.
Yes, as long as your Linux distro is Windows.
fuck microsoft and windows so hard. had to reinstall that shitshow on my mothers computer because a driver update fucked the whole networkstack… they throw error codes and what not but give no help whatsoever. the conclusion of everyone for every problem is to reinstall windows… shitshow of an os, keep your dirty hands of linux!! can’t wait to nuke it and install linux there and have no windows machine left
If you’re having to reinstall windows regularly you’re not very good at being the tech guy. I say this as someone who manages a support team for 50+ Windows machines, and who has been the tech guy for all my friends and family for decades. I can count the number of times I had to reinstall windows on one hand, with a few fingers to spare.
If you’re having to reinstall windows regularly
says who? what’s the fix for code 56? what can i do in the registry do solve the botched update? which files to check and/or remove? logfiles that give me a clue? come on tech guy enlighten us
Strange cause like I said, I’ve been doing this for literal decades and can count the number of times I’ve had to reinstall windows on one hand, with a few fingers to spare. 50+ windows machines at any given time at work for 15+ years. Every family members computers for 25+ years.
Never had “code 56”, but doesn’t seem like a hard fix: https://answers.microsoft.com/en-us/windows/forum/all/solvedunable-to-update-network-drivers-error-code/e34e928d-53a1-4bfa-b2c9-7157352b728d
One hand.
With fingers to spare.
Reading comprehension my friend… but what do i know, you are so great and superb
Reading comprehension? Huh? Maybe you missed my edit:
Never had “code 56”, but doesn’t seem like a hard fix: https://answers.microsoft.com/en-us/windows/forum/all/solvedunable-to-update-network-drivers-error-code/e34e928d-53a1-4bfa-b2c9-7157352b728d
can some one ELI5… is this a way for me to run windows stuff using linux? OR is this for linux stuff to run in windows?
I really want an easier way to run windows stuff in linux, my hatred grows with every notification, update, attempt to advertise to me, and interference in my workspace. but trialing mint is great but the ultimate test is failing with a few programs not really playing nice with linux.
It’s to run Linux stuff on Windows.
Garbage on top of garbage. The true nature of macroshafts desperate grasp to get control of linux.
nice try. get fucked, microsoft.
