Earlier quoted context omitted.
Then why they develop GNU/Linux software to start with?
Because their needs aren't met by developing Windows or macOS software?
Then again why they don't support GNU/Linux vendors?
WSL2 corrupting Git repositories and shell history
51–60 of 423 posts
Re: WSL2 corrupting Git repositories and shell history
#52Earlier quoted context omitted.
> Running a virtual machine often means accessing the UEFI to be sure they have virtualization extensions enabled. Likewise for WSL2. I hope modern computers with a capable processor are all shipped with virtualization enable at firmware level, because Hyper-V can be used for tons of things in recent Windows.
Enabling hardware virtualisation opens up a significant and deep attack surface. Considering the vanishingly small percentage of users which benefit from it, I hope it stays off by default.
Windows is moving to a model where Windows itself is run as a virtualized OS. I believe this is enabled by default in new installs.
So having a Linux VM in Hyper-V isn't opening up much new attack surface.
Re: WSL2 corrupting Git repositories and shell history
#53Earlier quoted context omitted.
Keep the Mac handy. I just went the other way to you because of a thousand paper cuts.
Same here. I want to like Windows but MS just makes it impossible. The MBP M1 has blown me away, I don't think I'll try to go back any time soon.
Yeah M1 Mini here. Total game changer.
Re: WSL2 corrupting Git repositories and shell history
#54I think calling it WSL2 was a mistake. The predecessor, WSL, "just worked" and it was more a less a linux experience for most practical purposes-- and certainly better than hoary old cygwin. This caused a lot of people to believe they could just transition to WSL2, lead on by the promise of an even more performant linux experience. The documentation didn't say anything about complications from attempting this, so a l…
Rushing half-finished products out, offering little/zero support is the new Microsoft. The reason $MSFT loves open source is because they can get press hype over projects that are 75% complete (which is the main goal), and they don't even need to support it, document it, or make it actually work.
New? Windows 95 comes to mind.
Re: WSL2 corrupting Git repositories and shell history
#55Earlier quoted context omitted.
> Running a virtual machine often means accessing the UEFI to be sure they have virtualization extensions enabled. Likewise for WSL2. I hope modern computers with a capable processor are all shipped with virtualization enable at firmware level, because Hyper-V can be used for tons of things in recent Windows.
Enabling hardware virtualisation opens up a significant and deep attack surface. Considering the vanishingly small percentage of users which benefit from it, I hope it stays off by default.
Erm, explain? What attack can you do with hardware virtualization enabled that you cannot otherwise do?
Re: WSL2 corrupting Git repositories and shell history
#56I think calling it WSL2 was a mistake. The predecessor, WSL, "just worked" and it was more a less a linux experience for most practical purposes-- and certainly better than hoary old cygwin. This caused a lot of people to believe they could just transition to WSL2, lead on by the promise of an even more performant linux experience. The documentation didn't say anything about complications from attempting this, so a l…
Rushing half-finished products out, offering little/zero support is the new Microsoft. The reason $MSFT loves open source is because they can get press hype over projects that are 75% complete (which is the main goal), and they don't even need to support it, document it, or make it actually work.
Half-finished releases haven been Microsofts SOP since forever. And especially for payware, bugs are only fixed in the next release, so you need to buy the subscription or the new release.
Re: WSL2 corrupting Git repositories and shell history
#57Reading through the issues it seems like the problem is occuring when opening the same files from directly inside the WSL2 container and also through the network device that exposes them to Windows at the same time. I'm not very familiar with how WSL2 exposes files but that seems to be the problem
Re: WSL2 corrupting Git repositories and shell history
#58I think calling it WSL2 was a mistake. The predecessor, WSL, "just worked" and it was more a less a linux experience for most practical purposes-- and certainly better than hoary old cygwin. This caused a lot of people to believe they could just transition to WSL2, lead on by the promise of an even more performant linux experience. The documentation didn't say anything about complications from attempting this, so a l…
I was using WSL to do esp8266 development so I could use linux tools. The official esp8266 windows toolchain is based on cygwin. If I'm using something that needs a unix environment anyway, why use cygwin when you have WSL? I upgraded to WSL2 because well 2 is bigger than 1 so it must be better. But no, nothing worked. Serial ports are not supported in WSL2.
I literally spent the last couple of days getting ESP32 to work under WSL. Was not painless.
You can have WSL1 and WSL2 side by side IIRC. And there are scripts out there to pipe serial into WSL2.
Re: WSL2 corrupting Git repositories and shell history
#59Earlier quoted context omitted.
File system corruption is unforgivable mistake, but FS work is really hard to get right. Even stuff like VMware corrupts shared folders ... wherever they try to bypass a driver translation layer. Just Google for “vmware shared folder corruption”
Is this the reason why they have deprecated shared folders in Workstation 16?
I don't think they deprecated shared folders, only shared VMs (a function that enables Workstation to act as a virtualization server).
Source: https://en.wikipedia.org/wiki/VMware_Workstation#Version_his...
Re: WSL2 corrupting Git repositories and shell history
#60I think calling it WSL2 was a mistake. The predecessor, WSL, "just worked" and it was more a less a linux experience for most practical purposes-- and certainly better than hoary old cygwin. This caused a lot of people to believe they could just transition to WSL2, lead on by the promise of an even more performant linux experience. The documentation didn't say anything about complications from attempting this, so a l…
I was using WSL to do esp8266 development so I could use linux tools. The official esp8266 windows toolchain is based on cygwin. If I'm using something that needs a unix environment anyway, why use cygwin when you have WSL? I upgraded to WSL2 because well 2 is bigger than 1 so it must be better. But no, nothing worked. Serial ports are not supported in WSL2.
http://matevarga.github.io/esp32/m5stack/esp-idf/wsl2/2020/0...
Here's how you can flash ESP devices under WSL2.