Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Windows Subsystem for Linux 2 Moving into General Availability

infoq.com

Post reply on HN
Print view View original

401–410 of 420 posts

Re: Windows Subsystem for Linux 2 Moving into General Availability

#401

Post by tsimionescu »

jfkebwjsbx wrote: post #243
tsimionescu wrote: post #221

Earlier quoted context omitted.

Unfortunately Git on Windows is also extremely slow. Especially using Magit in emacs, which does a lot of git calls, works much, much faster for me if it's sshing to a Linux VM for each call then running natively on Windows.

That may have been the case in the past, but Microsoft put some effort into making Git faster in Windows. Also, remember to disable the antivirus for your Git folder!

If only that were up to me... Company laptop, company antivirus, company code...

Re: Windows Subsystem for Linux 2 Moving into General Availability

#402

Post by dman »

pjmlp wrote: post #270
dman wrote: post #217

Earlier quoted context omitted.

If you things to just keep on working Arch might not be the distro for you. Have you tried something like ubuntu?

Canonical broke wlan and OpenGL for many of us when they decided to replace fully working closed source drivers, with work in progress open source replacements. So even Ubuntu isn't necessarily a guarantee of stability.

Sigh - I hear you.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#403

Post by zaarn »

juped wrote: post #67
chx wrote: post #59

I am giving up. WSL1 was a great invention but Microsoft gave up on it, either because of the filesystem performance problems or because of the debuggers. https://github.com/microsoft/WSL/issues/2028 (lldb, rr, delve all affected). This looks like a dreaded case of the first 90% is easy, it's the second 90% that is hard. Imagine implementing a translator for a vast majority of Linux syscalls just to find certain flav…

WSL was very cool from a pure tech standpoint, but I've never been clear what the actual use case for it was. WSL2 seems to be more along the lines of coLinux, which I felt the same way about when it was new.

Development. At work we rely heavily on it to get work done because having an almost-linux-like environment is much better than having to run a WAMP stack or similar silly stuff.

It's made mine and my coworkers lives so much easier compared to before, so I'm certain use cases exist. Since WSL2 runs on HyperV, for some of my coworkers it's not an option, since they rely on VMware and similar for other essential work.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#404

Post by hemanta212 »

Karupan wrote: post #33

So WSL2 is supported on windows 10 Home as well, which is great. Does that mean Home also gets official Hyper V support?

been using it in home for months it works well.

Regarding hyper-v they are only making necessary component needed for wsl2 available.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#405

Post by bayesian_horse »

sullyj3 wrote: post #211
rossy wrote: post #100

Earlier quoted context omitted.

While similar in concept, Wine is better than WSL1 in a lot of ways due to supporting sound, graphics, and GPU acceleration. I've always been suspicious of WSL because it follows a narrative that benefits Microsoft - that Linux is primarily a command-line/server environment, and the graphical and audio applications for Linux are not worthwhile. It doesn't have to be like this. WSL1 was based on an Android environment…

The graphical and audio applications for linux aren't worthwhile, or at least they're not competitive with the top proprietary offerings. It's not really about the theoretical capacity of of linux to support audio and graphics. The low market share of desktop linux makes it not economically worthwhile for top proprietary software companies to port to linux. That's just an unfortunate fact. I don't really want to edit…

Blender is competitive in the industry and definitely "worthwhile". Not the market-leader, but being used increasingly in professional settings.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#406

Post by zhte415 »

chx wrote: post #166
LeoPanthera wrote: post #158

Earlier quoted context omitted.

Since you did not specify a laptop, you can plug in any arbitrary USB HID to desktop Mac. (MacBooks too - though I'm sure this isn't what you meant.) Most people choose their laptops based on the OS, not on the pointing device.

There are about 5000 of us who did choose a laptop for its keyboard and pointer: it's the ThinkPad 25 Anniversary Edition. I have an SK-8855 already and also ordered the new TEX Shinobi so my unwavering stance on my laptop needing a proper keyboard+pointer might change but for now my choice of weapon is the TP25.

Unfortunately I missed that.

However my T420 and X220 still perform excellently even after 9 years.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#407

Post by chx »

zhte415 wrote: post #406
chx wrote: post #166

Earlier quoted context omitted.

There are about 5000 of us who did choose a laptop for its keyboard and pointer: it's the ThinkPad 25 Anniversary Edition. I have an SK-8855 already and also ordered the new TEX Shinobi so my unwavering stance on my laptop needing a proper keyboard+pointer might change but for now my choice of weapon is the TP25.

Unfortunately I missed that. However my T420 and X220 still perform excellently even after 9 years.

I also have a T420 and a T420s , the latter hacked to full HD, yes. :)

Re: Windows Subsystem for Linux 2 Moving into General Availability

#408

Post by bad_user »

hectorchu wrote: post #385
bad_user wrote: post #323

Earlier quoted context omitted.

Hi, any article on the subject I could read? This is the first time I hear of rEFInd.

This is a good article: https://dea.nbird.com.au/2017/02/24/enabling-vt-x-on-mac-boo...

Thanks ´･ᴗ･`

Re: Windows Subsystem for Linux 2 Moving into General Availability

#409

Post by zamadatix »

souprock wrote: post #398
zamadatix wrote: post #342

Earlier quoted context omitted.

Type 2 hypervisors are going to be in an interesting state. The Windows bootloader already has a flag you can easily toggle (without removing the Hyper-V role or config) but the problem is more features are starting to depend on Hyper-V being there one layer up (it's a type 1 hypervisor). I'm surprised nested virtualization can't be used for the type 2 hypervisor since Hyper-V picked this feature up a few years back…

Nested virtualization only works when the outer hypervisor supports all the features that the inner hypervisor needs. If the outer hypervisor is Hyper-V, then that limits the inner hypervisor to the features that Hyper-V bothered to implement. In other words, you can't implement a hypervisor more advanced than Hyper-V. If you instead want to be on the outside, with Hyper-V on the inside, then you can't just write a d…

Hyper-V is able to nest ESXi and KVM (and Hyper-V of course) and vice versa ESXi and KVM are able to nest Hyper-V. I'm not sure what would be limited.

Yeah that's the difference between a type 1 and type 2 hypervisor. A type 1 runs on the bare metal, a type 2 runs via drivers underneath an existing OS. Since Hyper-V is a type 1 (like ESXi) you can't use a type 2 hypervisor on the root VM to escape being under Hyper-V you either have to do some sort of nesting or disable Hyper-V from loading and reboot.

Re: Windows Subsystem for Linux 2 Moving into General Availability

#410

Post by souprock »

zamadatix wrote: post #409
souprock wrote: post #398

Earlier quoted context omitted.

Nested virtualization only works when the outer hypervisor supports all the features that the inner hypervisor needs. If the outer hypervisor is Hyper-V, then that limits the inner hypervisor to the features that Hyper-V bothered to implement. In other words, you can't implement a hypervisor more advanced than Hyper-V. If you instead want to be on the outside, with Hyper-V on the inside, then you can't just write a d…

Hyper-V is able to nest ESXi and KVM (and Hyper-V of course) and vice versa ESXi and KVM are able to nest Hyper-V. I'm not sure what would be limited. Yeah that's the difference between a type 1 and type 2 hypervisor. A type 1 runs on the bare metal, a type 2 runs via drivers underneath an existing OS. Since Hyper-V is a type 1 (like ESXi) you can't use a type 2 hypervisor on the root VM to escape being under Hyper-V…

Heh, it's funny that I'm actually a hypervisor developer and I don't use that terminology. The whole team doesn't. I actually had to look up "type 1" and "type 2" to remind myself which was which. Those are terribly non-descriptive. Our terminology is "bare metal" or "OS" or "boot loader", and "VMX driver". Anyway...

Our hypervisor is far more demanding than ESXi, KVM, and Hyper-V. It needs to interact with low-level Intel processor details in a way that is not supported by any other hypervisor. It won't run correctly if nested inside any other hypervisor. If we supported running under another hypervisor, we would lose important functionality.

If it becomes impossible or impractical to disable Hyper-V, we'll need to do something strange and annoying. Perhaps we could load the driver very early in boot, before Hyper-V loads. Booting as an OS ("type 1", ugh) is an option too, but maintaining that and using it is a real pain. Probably we'd drop Windows host support before we did that.

Post reply on HN