"Microsoft's Windows Subsystem for Linux has become an important tool for developers and power users since it was introduced in the Windows 10 Anniversary Update back in 2016, giving them access to a built-in Linux command line and Linux applications from within Windows.
The company has steadily improved WSL since then, improving performance, making it easier to install and use, and adding features like GPU and audio support. But today as part of its Build developer conference, Microsoft announced that it would be making almost all of WSL open source, closing the very first issue that the then-new WSL project attracted on Github in 2016.
"WSL could never have been what it is today without its community," writes Microsoft Senior Software Engineer Pierre Boulay in the company's blog post. "We’ve seen how much the community has contributed to WSL without access to the source code, and we can’t wait to see how WSL will evolve now that the community can make direct code contributions to the project."
Only two elements of WSL remain closed-source for now: an lxcore.sys kernel driver used for WSL 1 (the initial version of WSL that is still supported, though new installs default to 2019's WSL 2); and the p9rdr.sys and p9np.dll files that handle filesystem redirection from Windows to Linux (in other words, making it so that Windows can easily access the Linux filesystem). Microsoft didn't close the door to open-sourcing those components but also didn't say if or when it planned to make them open source."
Are the "p9*" references …
『Only two elements of WSL remain closed-source for now: […] and the p9rdr.sys and p9np.dll files that handle filesystem redirection from Windows to Linux […]』
… mentioned in …
Microsoft closes 9-year-old feature request, open-sources #WindowsSubsystemForLinux [#WSL],
https://arstechnica.com/gadgets/2025/05/microsoft-takes-windows-subsystem-for-linux-open-source-after-nearly-a-decade/
… related to #Plan9?
My first #CyberSecurity class for #CollegeCreditPlus (college classes for high school students) credentialing at #FranklinUniversity in #Columbus #Ohio officially started today.
#Linux is not mentioned as a supported or even unsupported platform. (not their fault; it was prolly uni decision, not CS dept.)
Course has 1 or 2 "proctored" tests, which means spyware. I'm going to try to take them in front of live proctors. Alternative is #MSWindows in a virtual machine. Will that even work?
The documents will have rather private information; else would have just gone to local Office Depot to send #fax.
Anyone got a suggestion for fax software/service that works over internet (on #FreeBSD 13 VM or #MSWindows 10/11; do not think transferring documents to iPhone or iPad would work)?
Found some suggestions of subscription based software & online services (eg https://windowsreport.com/pc-fax-machine/ ) but they not even give a hint about privacy policies, data retention, and such.
I JUST FOUND OUT THAT MS WINDOWS HAS THE SEND-TO-BACK WINDOW MANAGEMENT FEATURE
All this time, I could just press Alt+Esc and my window would be sent to the back! If only I knew this back when I was a Windows user.
What if Windows also has always-on-top?
where we are going, we need no stinking new passwords ...
#MSWindows #RDP lets you log in using revoked passwords. #Microsoft_corp is OK with that: Researchers say the behavior amounts to a persistent #backdoor, 20250430,
by Dan G,
https://arstechnica.com/security/2025/04/windows-rdp-lets-you-log-in-using-revoked-passwords-microsoft-is-ok-with-that/
『Dormann said the only course of action is to configure RDP to authenticate against locally stored credentials only.』
All is good apparently if not using Microsoft|Azure account to sign in.
"Git.Git" (software ID for "winget" command) is rather bloaty for installing "Vim" along with #Git proper
, especially when I install "Vim" myself.
Wonder if choosing the components is possible; may need to re-install ...
Mastodon, j'en appelle à ta magie. J'ai quelques applications en gtk3 (dont l'émulateur Vice) sur mon MS-Windows 11 qui ne sont pas en thème sombre, contrairement au reste de l'interface.
Aurais-tu une solution pour harmoniser tout cela ?
Could anyone tell if #ugoogledChromium available for #MSWindows as "eloston.ungoogled-chromium" (ID via "winget") is the genuine one?
-- Other way to look at that question is if I need to ask, I shouldn't be installin'.
Thank you for delivering MULTIPLE talks here in #bloomingtonIN and for signing our books!
As you signed @pluralistic , "Disenshittify or die!"
So, a story about how I #disenshittify ... by force!
This story starts when I was working at #IndianaUniversity for #UITS in IT Client Services. My job was "Special Projects". I worked for a director and basically made magic happen.
Early November 2014, someone from a human interface robotics lab handed me a new piece of #hardware called the #ThalmicMyo . It was an upper armband with 8 myoelectric sensors that could measure electrical muscle function, and do stuff on a computer with that data! The base idea was that you could do the following: hand wave outward, inward, spread out, fist, and thumbs up.
So, being CrankyLinuxUser, I wanted a #FLOSS toolchain to get and do my own thing with it. Whoops, only worked for #MSWindows .
Forum requests were met with silence. "Sorry you cant get the data", was the refrain. Lies.
So I used my #IU account and requested academic access. They IMMEDIATELY chimed up and said that access could easily be granted at $5000/year . UH huh.
So, I made them a target.
Took a few weeks. BUT I eventually got a shitty BUT working toolchain on Linux to use really basic machine learning. This is just a linear regression k-nearest-neighbors. No LLM fuckery. Theirs could do 5 gestures. Mine could do 10.
I initially released it on #HackerNews or YCombinator, not realizing that Thalmic Myo was VC funded by YC. And holy shit that was a #MartinHench moment where I fell into a WHOLE LOT OF SHIT. My article was auto-killed. My account on HN was shadowbanned. Ruh roh.
I had some contacts at @hackaday and I sent them my findings, my responses from HN, and my repo... and a really hostile Youtube video (one of my gestures was a middle finger to Thalmic).
On Nov 18, 2014, at 730am eastern, my phone blew up, figuratively speaking. Ping. Ping ping. PIIIIIIINNNNNGGGGG until 12pm.
The page is still up on HaD, by the way. https://hackaday.com/2014/11/18/thalmic-labs-shuts-down-free-developer-access/
At 12pm or thereabouts, Thalmic Myo announced that they made an official decision to "allow raw data access"! I was not only successful for my hardware, but hardware freedom for EVERYONE with this platform.
Normally, the story would stop. I handed back the borrowed hardware to the lab that loaned it to me. I know they were able to do some cool prosthetic automation with it. But that's not my specialty. I made it so they could. My director permitted me to buy a few for our office to continue and loan them out as well.
...... 3 months later
I get a call on my office phone doing a customer survey. Told them that the hardware was great. "What about our API?" I told them that I made my own, and I was the one that forced your company to open source 3 months back. Ive never heard silence so LOUD. She asked me to stand by.
She transferred me to the CTO. We had a spirited conversation. I basically told him that I think ignoring the FLOSS and hacker community was your first and fatal mistake. You were a hardware business. You can do the VC thing and gatekeep, but that just angers people. And what you were in was a MASSIVE awesome piece of unique hardware nobody else had. He told me that their original idea was a powerpoint slide advance. I gave him perhaps 6 different major ideas to jump off on.
Nothing else happened, for a while.
3 more months later.......
I get a reddit DM out of the blue. Saw my name, and connected the dots. (S)He was an engineer at Thalmic during the time I released my Linux FLOSS code. They told me that I basically flip-turned the whole company upside down. I broke their business model of #Extraction and #enshittification and forced #FLOSS on them without a choice. They thanked me for my contribution.
Later n, the company got acquired or died. I'm not sure. I moved on and no longer had any of the hardware. Although, the basic idea is actually pretty cheap to construct these days. The only hard part is the AgCl electrode plating.
So when people ask what they can do, there's a LOT we can do. And a SINGLE PERSON can change the course of history. Sure, sometimes being in the right place at the right time is a big part, but there's so many of these moments.
Just wanted to contribute back @pluralistic to the movement you've founded.
@gamingonlinux feel for you, I tend to give support to those with #mswindows installed on their computer, as they accept my help, I begin with installing #Linux with a full format of the hard drive.
I usually don't need to give any more tech support to those people when they wasted money to buy a new computer
Dear #Microsoft , your #MSWindows #GUI insists on having window borders measuring 1px wide, which we get to grab to resize the windows. With a mouse that seems easy. Try again using a touch pad when cold and shivering, or tired, or in a dusty machine mill with a trembling floor. Don't even get me started on people suffering central tremors, cerebral palsy, or other physical limitations.
#usability #accessibility
shove your enhanced security & user experience up your collective asses, Amanda L & Brandon LeB ...
New #MSWindows11 build makes mandatory #Microsoft_corp Account sign-in even more mandatory: "#Bypassnro" is an easy MS Account workaround for Home and Pro Windows editions, 20250328,
by Andrew C,
https://arstechnica.com/gadgets/2025/03/new-windows-11-build-makes-mandatory-microsoft-account-sign-in-even-more-mandatory/
Of possible interest for some folks. #FYI #PSA
> How to restore access to classic Notepad on Windows 11 https://www.ghacks.net/2025/03/26/how-to-restore-access-to-classic-notepad-on-windows-11/
... Also, the one installed version of #LibreWolf "MSIX" package is old. Instructions to get the checksum for a updater file https://codeberg.org/ltguillaume/resources/src/branch/main/signing are not for #MSWindows.
Fuck this; far too much fiddly/non-working work.
Removed. Avoiding it like the measles (on the OS listed).
C 2023 issue 1285 of getting #MSWindows (stern) warning https://codeberg.org/librewolf/issues/issues/1285 (when trying to install #LibreWolf from its installer https://gitlab.com/api/v4/projects/44042130/packages/generic/librewolf/135.0.1-1/librewolf-135.0.1-1-windows-x86_64-setup.exe via https://librewolf.net/installation/windows/) is here.
No progress was being made when trying to install via "winget" (on Windows 11).
What?! I had installed it, currently v135.0-1, on a different 'puter (this one). How?
/Probably disregarded the warning./
So, the next person to tell me they don't like #Linux because it's not "user friendly", try installing #MSWindows using the latest ISO with an NVME drive that is only recognized with Intel Rapid Storage Technology drivers installed.
Or just give up and install #Ubuntu.
#AppleTV application for #MSWindows has terrible reviews: https://apps.microsoft.com/detail/9nm4t8b9jqz1?hl=en-us&gl=US
Now, can vouch for its crashy tendencies: crashed when trying to mark an episode as played or trying to navigate to another episode.
Well, phone it is then. As before.
#IndustrialGaslighting #BullshitEverywhere
#FWakeBullshit #FWakeGaslight /\
#DiaryOfRoundSparrow January 20, 2025 #FWakeFUD
#Gaslighting #Gaslight #ExecutiveFunctionManipulation
What did we call it back in the 1970's and 1980's,.. I heard the term "FUD" on social media when I started working with Microsoft and IBM over emerging #OS2 and #MSWindows