WSL
WSL
Our great sponsors
WSL | WSL | |
---|---|---|
25 | 406 | |
1,848 | 16,652 | |
1.9% | 1.5% | |
8.9 | 8.6 | |
10 days ago | 2 days ago | |
PowerShell | PowerShell | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
WSL
- Windows VBS
- [Bashonubuntuonwindows] \"Veuillez activer la fonctionnalité Windows Virtual Machine Platform et vous assurer que la virtualisation est activée dans le BIOS.\ »
- Why do I get two different results from different PCs
-
can't use WSL2 despite virtualization and Windows machine platform feature enabled, and error message says thye're not.
I have found some documentation here https://github.com/MicrosoftDocs/WSL/issues/536 and here https://learn.microsoft.com/en-us/windows/wsl/faq#will-i-be-able-to-run-wsl-2-and-other-3rd-party-virtualization-tools-such-as-vmware--or-VirtualBox and intend to read them fully including the links inside them tomorrow or the day after when I have time.
-
There are literally no reasons to choose an iPhone over an Android smartphone
Off the top of my head was this bug that caused a lot of people using vbox to swap to vmware. Just a bunch of really annoying compatibility bugs that made it a nightmare if you were trying to use it like a native linux instance.
-
Is Microsoft's CBL-Mariner Going to Become Microsoft Linux?
>and I’m almost certain that when you run multiple wsl distros they are all in one VM, though that may be wrong
Yes, they run as containers.
From https://github.com/MicrosoftDocs/WSL/issues/1573#issuecommen...:
WSL distributions (instances) are not VMs. They are best described as "containers" running inside the WSL2 VM. Each WSL2 distribution/instance has its own isolated:
PID namespace
-
Unable to run any docker container using WSL2
(As I've understood, Hyper-V Management Tools should not be needed when using WSL2, based on: https://github.com/MicrosoftDocs/WSL/issues/899)
-
Kernel Panic when trying to install AlmaLinux 9 in VirtualBox
Here https://github.com/MicrosoftDocs/WSL/issues/536
- Docker for Windows failing to start: "WSL system related access rights are not set correctly"
- AlmaLinux / WSL2 / Start Apache
WSL
-
GoboLinux
It absolutely 100% can be true.
As an example: Windows Services for Linux 2 used a special init daemon to interact with the host OS.
That meant no systemd. That meant that the `systemctl` program wasn't there.
This baffled legions, armies, of wannabe sysadmins.
https://stackoverflow.com/questions/55579342/why-systemd-is-...
https://superuser.com/questions/1785697/systemd-in-wsl-on-wi...
https://github.com/microsoft/WSL/issues/9477
https://askubuntu.com/questions/1132230/unable-to-run-any-sy...
People on the whole have no idea how this stuff works, and they just copy magic incantations from StackOverflow to get stuff to happen. If that doesn't work, then this OS is broken. The end.
For these guys, WSL was broken.
Result:
MS hired Lennart Poettering.
https://www.theregister.com/2022/07/07/lennart_poettering_re...
He "fixed" it. Systemd now works in WSL2. All those guides for noobs now work. Everyone is happy.
In a world where tools like Flatpak and Snap are proliferating and it's driving deep divisions between Linux distros, if you think the average person struggling with Linux is going to use `ldd` to work out where the dependencies for something live, I'm afraid you are a deep guru who lives on a different plane of existence.
We now have widely-used packaging systems which simply embed an apps entire dependency tree into a package to avoid people having to work out the difference between `apt` and `rpm`. Thousands of terabytes of disk are being burned to make this stuff go away.
Yes, this is too hard. Way too hard.
-
Why Linux utilities tend to run poorly on Windows
Better source: https://github.com/Microsoft/WSL/issues/873#issuecomment-425...
- Weird graphical glitch/problem in Ubuntu WSLg (OpenGL)
-
RamRamRamEveryoneSleepingOnDocker
One of the bugs where on the Docker side. As I have said, there have been several since release with a lot of impact period overlap. The latest and greatest is not resolved.
-
Laravel dev in Windows - Laragon vs Docker?
It's the issue of abysmal I/O performance in communication between the mounted WSL2 virtual hard disk and Windows mounts inside the WSL2 distro.
- WSL freeze seems fixed in 2.0.12
-
What's the right way to open files in the system's default program from Ubuntu 22.04 in WSL 2 please?
I found this github page and I was able to reproduce this from the answer
-
Ask HN: Best Docker open source alternative?
* Docker engine and not Docker Desktop in a VM. WSL2 works well after some configuration: https://github.com/microsoft/WSL/issues/6655#issuecomment-11...
-
Broadcom to Cut Almost 1,300 VMware Jobs in California After Takeover
Seems to more of a Defender issue than a WSL one, see https://github.com/microsoft/WSL/issues/8995
After adding exclusions for the fsnotifier-wsl process and and both variants of the WSL distro path my disk performance was improved.
Adding the idea64.exe process also helped since I was trying to run IntelliJ against projects inside WSL.
- Bricked WSL 2 after 2.0.9 / Windows 10
What are some alternatives?
Chocolatey - Chocolatey - the package manager for Windows
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
toolchains_llvm - LLVM toolchain for bazel
genie - A quick way into a systemd "bottle" for WSL
dnf - Package manager based on libdnf and libsolv. Replaces YUM.
Scoop - A command-line installer for Windows.
noclip.website - A digital museum of video game levels
Single-GPU-Passthrough
sorbet - A fast, powerful type checker designed for Ruby
setup-msys2 - GitHub Action to setup MSYS2
ipe-wiki - A Wiki for tips and tricks related to Ipe
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.