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

WSL2 corrupting Git repositories and shell history

github.com

Post reply on HN
Print view View original

81–90 of 423 posts

Re: WSL2 corrupting Git repositories and shell history

#81

Post by ncphil »

uncledave wrote: post #31
delduca wrote: post #2

More: - WSL2 sometime corrupt .zsh_history and git https://github.com/microsoft/WSL/issues/5026 - WSL2 corrupts ext4 filesystem https://github.com/microsoft/WSL/issues/5895

This is probably HyperV. I’ve seen exactly this ext4 corruption in production on windows server 2012R2 with CentOS 7. Even to the point that the machine remounts root read only. Unfortunately our windows operations guys are severely lacking in diagnostic savvy and just reboot the machine over and over again or blast it and provision a new one and don’t analyse the problem. From what I’ve seen it’s a combination of th…

Had a serious talk a Unix manager over a decade ago who was convinced Windows ops didn't require as much expertise as Unix/Linux. It was a common misconception that MS seemed to encourage. As someone who came over from Windows, I knew better. That attitude continues to influence standard practices, hiring and, most importantly, training and education opportunities for Windows admins -- to the detriment of all. I've also had my collisions with Hyper V, and have come away with the same impressions as you have.

Re: WSL2 corrupting Git repositories and shell history

#82

Post by andrew_ »

hvdijk wrote: post #76
zamadatix wrote: post #74

Earlier quoted context omitted.

You can say "fixed in " regardless if the name is numerically sequential.

True, but if MS hadn't presented WSL2 as a variant of WSL, any issues fixed in WSL2 wouldn't count as fixed in the WSL issue tracker. I would prefer it if their issue tracker marked these, more honestly in my opinion, as "This issue is will not be fixed in WSL, you can migrate to HVL instead" (using HVL as a hypothetical name for WSL2) with a separate HVL issue tracker.

A poor argument IMHO. A naming change for the sake of an issue tracker that appears to be a net negative for users is not a wise choice. Naming and branding doesn't exist to serve the project's management tools.

Re: WSL2 corrupting Git repositories and shell history

#83

Post by zamadatix »

hvdijk wrote: post #76
zamadatix wrote: post #74

Earlier quoted context omitted.

You can say "fixed in " regardless if the name is numerically sequential.

True, but if MS hadn't presented WSL2 as a variant of WSL, any issues fixed in WSL2 wouldn't count as fixed in the WSL issue tracker. I would prefer it if their issue tracker marked these, more honestly in my opinion, as "This issue is will not be fixed in WSL, you can migrate to HVL instead" (using HVL as a hypothetical name for WSL2) with a separate HVL issue tracker.

Whether they are counted as fixed in the WSL tracker is completely up to them. "Fixed, use HVL" is just as valid way to close a WSL1 issue ticket as "Fixed, use WSL2".

Re: WSL2 corrupting Git repositories and shell history

#84

Post by uncledave »

robbyt wrote: post #41
crispyambulance wrote: post #23

I 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.

Yeah I think you nailed it there actually. That's exactly their modus operandi.

What's even worse is they have managed to abstract most of the support away in this cycle. You can't get enterprise support now because they gutted that entirely. You can't get them to do anything on github because they keep moving all the projects around and erasing them all or auto closing the tickets and no one on first line support knows anything now other than how to reset a Microsoft account password.

Re: WSL2 corrupting Git repositories and shell history

#85

Post by pjmlp »

pram wrote: post #63
pjmlp wrote: post #46

Earlier quoted context omitted.

Then why they develop GNU/Linux software to start with?

People might get paid money to develop (proprietary!) software that deploys to Linux. That doesn't mean they enjoy using Linux.

Indeed, I have been doing that for years and am yet to install WSL.

Re: WSL2 corrupting Git repositories and shell history

#87

Post by pjmlp »

_glsb wrote: post #71
pjmlp wrote: post #46

Earlier quoted context omitted.

Then why they develop GNU/Linux software to start with?

One reason might be, is that they might need to in part work with a server-side system that runs on Linux and it’s easier this way. But maybe they also need to work with stuff thats Windows only. Say they need to produce media assets with the Adobe suite. Not everything is vimmable.

SSH and X Windows servers also exist for Windows.

Re: WSL2 corrupting Git repositories and shell history

#88

Post by microtonal »

proactivesvcs wrote: post #39
temac wrote: post #20

Earlier 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.

In Windows, enabling virtualization actually reduces attack surface. E.g. it is used to protect against kernel-level malware:

https://www.techrepublic.com/article/how-virtualisation-is-c...

Re: WSL2 corrupting Git repositories and shell history

#89

Post by Kwpolska »

sam_lowry_ wrote: post #64
umvi wrote: post #9

Earlier quoted context omitted.

When I launch my WSL2 Ubuntu shell, I have a CLI prompt in Getting that same quality of experience under VirtualBox was nightmarish. Longer boot times, shared clipboard/filesystems were always breaking, random stuff related to hardening made update difficult.

>Clipboard works perfectly Which one? Secondary? And the primary does not work at all?

The Windows clipboard just works, because WSL2 terminals are just regular Windows apps.

Re: WSL2 corrupting Git repositories and shell history

#90

Post by javajosh »

johnchristopher wrote: post #86

> Feel like booting Linux on a separate disk because of these issues. It always seemed strange to me that people would rather use WSL than the real thing when Windows doesn't bring much advantage. What am I missing ?

You are missing Office, Outlook, Visual Studio, and any enterprise nonsense IT requires on company computers. All of that requires Windows.
Post reply on HN