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

251–260 of 423 posts

Re: WSL2 corrupting Git repositories and shell history

#251

Post by larrik »

chrisandchris wrote: post #139
larrik wrote: post #104

Earlier quoted context omitted.

The web version of Outlook has come a long way, and in my opinion has become the superior product (for my use cases, at least).

The web version does work until you need to sign into more than 2 accounts per day (1 in regular, 1 in private). If you need more than 2 accounts, it does not work anymore. Edit: it does work, but it will sign you out from all M365 services which requires a lot of logins for nothing.

Fair, I'm only using it on one account. Also, I have a special Firefox plugin to make notifications louder.

Re: WSL2 corrupting Git repositories and shell history

#252

Post by craftinator »

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…

> Unfortunately our windows operations guys are severely lacking in diagnostic savvy and just reboot the machine over and over again

What are you talking about, that is how you diagnose a Windows box...

Re: WSL2 corrupting Git repositories and shell history

#253

Post by whenitrains »

pjmlp wrote: post #152
jevgeni wrote: post #128

Earlier quoted context omitted.

It takes me 2 minutes to install WSL Ubuntu. Or I could spend half a day on figuring out a hacky solution to a Windows/SSH/XWindows workflow that offers even a comparable level of integration. It will grow into weeks of obsessive tweaking until I feel compelled to write a blog post for HN where I show my sick setup and hours and hours I dumped into this, while meaningful work piled up in my TODOs. ... Or I could just…

Or just install Humming Bird, working just fine for me since 2000.

Or just install WSL?

What's the problem with Microsoft having an answer to this?

Re: WSL2 corrupting Git repositories and shell history

#255

Post by [deleted] »

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…

[deleted]

Re: WSL2 corrupting Git repositories and shell history

#257

Post by birdyrooster »

Dylan16807 wrote: post #187
pydry wrote: post #98

Earlier quoted context omitted.

I mean, why not do that? I tried WSL because I thought it would be faster than a heavyweight VM. Turned out it's dog slow in comparison. Honestly don't see a use for it.

WSL1 is much better integrated, which is useful for some things, especially when networking is involved. And it wastes less memory as a consequence. The root partition is slower, but I'm usually manipulating windows files anyway so both versions are similarly slow. I use WSL2 right now, but only because I need to mount a vhd that's formatted with BTRFS.

You can’t compile anything with WSL1, did you notice that?

Re: WSL2 corrupting Git repositories and shell history

#258

Post by gavinray »

madeofpalk wrote: post #241
mrharshley wrote: post #225

WSL2 was promised as a good working extension for a Linux dev environment on windows by my peers. Sadly, a whole host of issues specific to my dev environment meant that it was useless as I’d spend more time fixing it than getting any valuable use out of it. More importantly, this became the very reason I switched to arch full time, and haven’t looked back since. I still hope that it becomes what it was promised to b…

Opposite anecdata - I got a gaming PC and i migrated all my development to it and WSL(2) has been a godsend. VS Code has a "WSL Remote" mode that works really well (where a vscode server runs in Linux and the windows GUI access it "remotely"). I even use the Windows Github app for the occasional GUI-assisted commit, and apart from being slow its fine. I've had only two problems with this set up: - Occasionally VS Cod…

Also opposite anecdote, I switched from Pop!_OS to Windows after getting into music production recently as a hobby (MIDI controller driver software doesn't always play well, even with WINE-devel) after over a decade on Linux.

I expected to hate it, but I'm asking myself why I didn't do this sooner.

It's the same sort of scenario as before -- I have Windows running the games I occasionally play, and music stuff, and I do all of my code stuff in WSL2/Ubuntu.

But this way, I never have to fiddle with weird WINE patches or googling bugs, everything "just works". Asking myself why I didn't do this sooner to be honest.

I had one big complaint which is that copying files from Windows to WSL2 would create ".ZoneInfo" file copies of every file, that was downloaded from the web, but they patched this recently too.

With the support for Linux GUI apps that launched with Windows Insider Preview recently, I have a hard time making arguments against it now. The taste of crow is a little bitter, eh.

Linux + WINE/Proton basically felt like shittier, more bug-ridden Windows + WSL2. With the one notable exception that as an OS/host, Windows 10 "feels" a bit slower in general.

Re: WSL2 corrupting Git repositories and shell history

#259

Post by bonzini »

loeg wrote: post #243
dehrmann wrote: post #237

Earlier quoted context omitted.

FreeBSD has native support for Linux binaries by mapping system calls, and it's fairly reliable when it works. What's nice is that when it works, it works, adding support for system calls improves coverage, and since underlying things like the FS aren't virtualized, it tends to be pretty reliable.

Yeah; Windows had something like that, too. It was WSL1 (or just "WSL"). I also tend to think that was the better approach.

It didn't extend to use cases like containers, that would have basically required MS to rewrite large parts of the Linux kernel's core code for namespaces, mount points etc.

Re: WSL2 corrupting Git repositories and shell history

#260

Post by shrimp_emoji »

trinovantes wrote: post #168

Another funny interaction I found with WSL2 and Windows is file case sensitivity leading to all sorts of weird error messages I wish I can use a real Linux installation but their display drivers don't work well with my multiple displays with different resolutions

>their display drivers don't work well with my multiple displays with different resolutions

Unless you're writing through a time warp from 2004, this is not true at all, IME.

But the statement is vague. "Work well" can mean some esoteric DPI scaling stuff that I think is only noticeable with 4K combinations. What distribution? What's "their display driver"? Nouveau, the open-source Nvidia one, is pretty bad, and everyone uses the proprietary Nvidia driver (this may be hard to come by on some distros, like Debian, but don't use those; use Ubuntu or Manjaro). The AMD open-source one is great and everyone on AMD GPUs uses that. I've been running triple monitor, diagonally-aligned 1080p/1440p configurations for years on several distros and DEs with both Nvidia and AMD drivers.

Post reply on HN