Releasing these apps allows them to basically get more development done and help also teach others how to program (it's a win-win situation for Microsoft). Still, they realize that there are a lot more benefits to open-source platforms on their actual software.įor quite a while now, they've learned to release numerous different Windows Apps on the GitHub platform for open source development. Over the years, their prices have skyrocketed (unless you buy OEM keys for everything – such as Microsoft Office 2019). Microsoft has been more than well known to have nothing but products that you had to pay for when it came to professional services. The downside is not only doing this often takes up more space, but it also needs a lot more customization and eats up system memory a lot more.īy having a WSL server set up on your Windows 10 machine, you don't need the VM, so you can do everything right from the command line of your Linux kernel installation without having to install third-party software. Having the ability to use a console command line on a Windows workstation can allow the use of installing and running the PBX server software that goes with your YeaLink phone.Īnother great benefit of using the Windows Subsystem for Linux is that many people have to install a virtual machine onto their computers to run Linux kernel apps and programs and even access a console solution. Well, what if you could do it all on one computer? The downside? Many users have to resort to additional software on their Windows PCs to connect to the PBX server to access certain features remotely. Linux gives the PBX server more added protection since the filesystems are a lot different than they are on a Windows computer, and they're less likely to be attacked. Some people prefer to have added security for their VoIP systems, and therefore, they prefer to install software like 3CX on a Linux kernel computer. With one of the recent Windows Updates, though, they were a – WSL v2 – which allows users even more flexibility, and also allows you to update your Linux kernel right along with your Windows Updates. Windows 10 released the Windows Subsystem for Linux kernel in the past, which allowed Windows 10 users to have a Linux kernel on their computers while running Windows, but it was extremely buggy. However, in the past, Windows users had to often have a separate "Linux" distribution on their computers or server. Or you can download and compile yourself from the provided source.Most programmers know that Linux is one of the most secure ways to not only build code but also have added protection from their data. It should be available soon for wsl -update (or via Automatic Windows updates). Last week saw the release of linux-msft-wsl-5.10.74.3. I'm sure many of these are optimizations (or even requirements) on the WSL end.ītw, it appears that there is a slightly newer release of the Microsoft supplied kernel. There are a huge number of other differences between the two. If the power management subsystem (ACPI) puts the system to sleep under WSL, there's no "waking it up". There's no "Power on", no "Suspend", etc. But one things that did stand out to me is that a stock Ubuntu kernel is, of course, expecting physical or even virtual "hardware" that supports power management. Things like virtualization are already enabled in the stock Ubuntu kernel, so that's not an issue. I spent a bit of time scanning a vimdiff of the two out of curiosity, but I'm not an expert in kernel configuration by any means. config is very different than that of the Ubuntu stock kernel configuration. Note that Microsoft does maintain its own WSL2 kernel repository with the modifications needed to optimize for WSL2. So I could have attempted to uncompress the Ubuntu kernel.īut regardless, I just didn't have high-hopes of this paying off (or being very useful). Looking at the existing WSL kernels, they appear to be uncompressed. I say "half-heartedly" because I could go further with this. No error, just locked up the wsl command until I issued another wsl -shutdown in another PowerShell session. Edited my %userprofile%\.wslconfig to add the appropriate kernel pointerĪttempting to start any of my WSL instances (any distribution) failed.Copied the vmlinuz-5.15.0-051500-generic over to a directory in my Windows user profile.I did try (half-heartedly) to run the 5.15 kernel under WSL: At the best, you'd get an extremely unoptimized WSL system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |