Slashdot Mirror
WLinux, the First Paid-for Linux Distro for Windows 10, Goes On Sale on Microsoft Store (techrepublic.com)
puddingebola shares a report: WLinux is a $20 open-source, Debian-based distribution, designed to run on Windows 10's Windows Subsystem for Linux (WSL). The WSL allows Windows 10 to run various GNU/Linux distros inside Windows as Microsoft Store apps, providing access to Ubuntu, openSUSE, Debian, Fedora, Kali Linux, and others. The WSL has disadvantages over a running a dedicated GNU/Linux system. For example, there's no official support for desktop environments or graphical applications, and I/O performance bottlenecks, but it is being improved over time. The developers of WLinux describe it as a "fast Linux terminal environment for developers", saying it is the first distribution to be "pre-configured and optimized to run specifically on Windows Subsystem for Linux". Announcing WLinux's availability, Microsoft program manager Tara Raj, called out the wlinux-setup tool, "which allows users to easily set up common developer toolchains, and removes unsupported features like systemd."
While the other distros have systemd in the repository, it doesn't actually run under WSL.
So while this one is unambiguously systemd-free, the other distros are effectively systemd-free while under WSL.
Working around the systemd-isms without being able to run systemd has been a big part of the whole WSL endeavor.
XML is like violence. If it doesn't solve the problem, use more.
Exactly. Installing VirtualBox with any of the great Linux distros works like a charm. I almost don't understand why would someone pay for this crippled solution.
Because it's faster and better in certain scenario's to do it like this.
Faster because:
A. To start it up, it's one click or one word away from a CLI. Virtualbox needs to be installed, spun up, wait till it's booted or restored, and taking up a truckload of RAM and CPU power. Just for running a simple command line tool. VB is total overkill when all you need is a simple CLI tool.
B. The executable runs natively. There's no virtualization overhead. This means full or better speed for execution and network (and other i/o) access.
Also, it works right on your own filesystem. No need for a 'shared folder' with you VM. Your drives are available as-is. And so are your gnu tools. So i can do anything with my files i want, no matter where they reside, without the hassle of copying them around to this shared-with-VM-folder.
Then, as far as security goes.. A VM not really adds any security here, i trust my ubuntu (or whatever) distro the same as on any native linux box. Why would i want to virtualize my gnu/linux environment.
There's other reasons as well, probably others will fill you in here. But to me just the ease and the speed are saving my sanity. Running anything in a VM still sux, even in 2018.
You can also reverse the argument, and compare it with using wine on gnu/linux. That's a pretty fair comparison as WSL and wine actually work in a very similar way. Yes, you could run anything you run with wine in a VM. Sometimes you even have to. But you'd rather not, for various reasons, but mostly because wine usually performs better and is less hassle.
A glitch a day keeps the bugs away.
No, they certainly did not.
Others may be confused over what WSL is, so it's worth repeating. No init system of any kind (sysv or systemd) make any sense in the WSL as it's currently designed. Windows itself is the init system for WSL. The Window kernel and the WSL is process 1 (calls itself init in the emulated Linux process list) and spawns linux binaries directly.
Actually, I use 'links' for that....
No, no. The OTHER stupid router :p
But seriously, Lynx is better for security because it doesn't support graphics and it can white/black list cookies, or totally disable cookies altogether. Lynx is still being developed, so don't forget about it.
Politics; n. : A religion whereby man is god.
I use Cygwin, but not on Windows 10 because I use WSL for that. Cygwin and WSL are very similar - the difference is the level they interface at. Cygwin is a translation layer between POSIX (or really SUS) APIs and the Win32 API. As far as Windows is concerned, every Cygwin application is just a console Win32 application.
WSL is lower level, and basically implements the Linux syscall interface on the Windows kernel. So applications talk to Linux based libraries which make system calls as Linux would expect, except they're being trapped by the Windows kernel and executed there. They are not technically Win32 applications and don't really have the interactions with Win32 that Cygwin applications would have. This would be the closest to "GNU/kWindows" you can get
Note that the Windows kernel is still enforcing security and other things, so WSL cannot be used to bypass permissions since the kernel is still involved with regular enforcements.
WSL is actually more like the BSD Linux personality - where the base kernel pretends to be Linux to run Linux binaries.
basically, desktop/workstation is the single niche that Microsoft is still holding)
Not true in north america at least.
They are still a major player for email servers through exchange server. https://www.quora.com/What-is-...
They still have one of the best on premise server OS with over 70% of the market cornered: https://www.computerprofile.co...
They are remaining strong in the virtualization server area with about 35% of the market. Note their market share of this was 0% until 2008 so 35% is not bad.
They still have the best office suite available for corporate use. Home use is a different story but that could be debated either way.
some of the logic going in the heads of microsoft is that wsl can be a bit of anti-gateway drug
Opinion more than fact. They actually believe in providing the tools required to do the job. As a multi platform developer I appreciate the ability to create Linux environments in my environment of choice.
the problem (for them, but advantage for us) is that it might end up the other way around:
You make it an "us versus them" argument. I don't understand why any tech professional would think that way. Maybe you're just a kid that hasn't been in the real world yet. If so, you've already closing your mind to a number of possibilities.