Live data from Hacker News

Windows Subsystem for Linux 2 Moving into General Availability

infoq.com

231–240 of 420 posts

Re: Windows Subsystem for Linux 2 Moving into General Availability

#231

Earlier quoted context omitted.

Restored? That's a weird line. I don't think it ever lost it since the feature was added in 6.0 (released December 18 2018), it was just annoying to activate.

I couldn't get it work, so it was broken as I saw it... not sure who could actually get it to work then.

You had to manually set "VBoxInternal/NEM/UseRing0Runloop" to 0. The default settings were broken, but the actual functionality was fine.

Though I remember it working at some point before that, too...

Re: Windows Subsystem for Linux 2 Moving into General Availability

#233

Earlier quoted context omitted.

I couldn't get it work, so it was broken as I saw it... not sure who could actually get it to work then.

You had to manually set "VBoxInternal/NEM/UseRing0Runloop" to 0. The default settings were broken, but the actual functionality was fine. Though I remember it working at some point before that, too...

Wow I see. I'm tempted to try it now and see if it works...

Re: Windows Subsystem for Linux 2 Moving into General Availability

#234

In WSL1, running "wsl git status" on a moderately sized repo on an NTFS (Windows side) drive or SMB file share is nearly instantaneous. In WSL2, running the same command takes over 30 seconds. WSL2 is a massive hit to the seemless experience between the two operating systems with filesystem performance from Linux to Windows files orders of magnitude worse. Yes, unzipping tarballs or manipulating and stat syscalls are…

I believe WSL2 was designed to keep your files inside on ext4 instead of outside on NTFS.

But what's the point of that? If I wanted my files to be on Linux I'd use Linux. I'm on Windows exactly because of things like this: the ability to use proper UI tools like Explorer to manage my files. How do I do that with WSL2?

Re: Windows Subsystem for Linux 2 Moving into General Availability

#235
post #197

In genuine amazement at a lot of the comments here - why not just dual boot Linux instead of using it in a VM? Productivity on a Linux machine can be so far ahead of Windows, especially if you've got a terminal-based workflow an maybe a tiling WM

My workflow is mostly terminal based, and I used to use tiling WMs, yet I am now back to Windows + WSL.

Why? Because GPU driver compatibility is still so bad on Linux that I can't get any of the popular distros to work properly on my setup (laptop with hybrid Intel/nVidia GPU setup, thunderbolt dock, external display with different scaling than laptop display).

And yes, if I spend a weekend fiddling with Nouveau drivers I might get it to run somewhat decently, but really I don't want to spend that time on my work setup. Window + WSL works out of the box, so I'll use that.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#236
post #202

Earlier quoted context omitted.

This seems like comment from early 2000s. I don't remember last time I head problems with BT or sound, and I went through dozen of installations in last 3 years (for me and others). I had to give up on Nvidia drivers but Intel graphics serves me great.

Bluetooth broke on me: https://bbs.archlinux.org/viewtopic.php?id=204875 2015 November https://bbs.archlinux.org/viewtopic.php?id=206032 2015 December https://bbs.archlinux.org/viewtopic.php?id=210685 2016 March. And these were times when I needed community help, most of the time I could get it working by pairing again or some such nonsense. It never worked reliably, in general. Note I switched to Windows as my daily…

I have fairly linux friendly laptop (Thinkpad T480) with Fedora, and GPU driver was broken for whole 5.3 kernel tree...

Re: Windows Subsystem for Linux 2 Moving into General Availability

#237
post #56
post #50

Earlier quoted context omitted.

WSL (1) was what the BSD people call a "kernel personality", which allows one kernel to emulate another at the syscall and ABI level.

So WSL1 on Windows is similar to Wine on Linux?

DanielK posted good points already, this is another perspective.

WSL1 shows off a character of the Windows kernel, Environment Subsystems: https://en.wikipedia.org/wiki/File:Windows_2000_architecture... (top right)

When you boot into Windows 10 normally, you are interacting with applications run by one of these subsystems.

WSL1 is now another of these subsystem.

Like wine, you are getting an API that looks just like Linux.

But, unlike wine, that Linux is a first-class citizen as far as the OS is concerned. It would be straightforward for the Windows devs to connect the Linux subsystem across to the Windows security module (see diagram). There is no analogy for that with Wine on Linux.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#238
post #235
post #197

In genuine amazement at a lot of the comments here - why not just dual boot Linux instead of using it in a VM? Productivity on a Linux machine can be so far ahead of Windows, especially if you've got a terminal-based workflow an maybe a tiling WM

My workflow is mostly terminal based, and I used to use tiling WMs, yet I am now back to Windows + WSL. Why? Because GPU driver compatibility is still so bad on Linux that I can't get any of the popular distros to work properly on my setup (laptop with hybrid Intel/nVidia GPU setup, thunderbolt dock, external display with different scaling than laptop display). And yes, if I spend a weekend fiddling with Nouveau driv…

Sounds fair, I didn't mean to come off snarky or anything.

I've got Nvidia too and Nouveau works only well enough to download the proprietary drivers

Re: Windows Subsystem for Linux 2 Moving into General Availability

#239
post #225
post #159

Earlier quoted context omitted.

None, as I stay away from them as far I can avoid them, Java and .NET are perfectly fine and IDEs have docker support in case I really need to deal with it.

Oh cool, we can just abandon all other languages and toolchains so we can switch to windows native. Why didn't I think of that?

Nah, you just target Windows with toolchains that support Windows natively, like I am expected to target UNIX with toolchains that support UNIX natively.

Your statement goes into both directions.

Guess why "Year of Linux Desktop" has failed to happen, and no, ChromeOS and Android aren't really GNU/Linux, the kernel is irrelevant to userspace languages and public APIs.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#240
post #77

Earlier quoted context omitted.

What Electron-related problems have you had with VSCode? I've been using it as my primary for a few years now and it's been nothing but stellar. And that integration sounds incredibly cool.

Font rendering is a bit blurry.

When did you last see this? I ask because VSCode fixed some blurry font rendering bugs a couple of months back.
Post reply on HN