WSL2 corrupting Git repositories and shell history
1–10 of 423 posts
Re: WSL2 corrupting Git repositories and shell history
#2- 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
Re: WSL2 corrupting Git repositories and shell history
#3Re: WSL2 corrupting Git repositories and shell history
#4More: - 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
Re: WSL2 corrupting Git repositories and shell history
#5I don't really understand the use case for WSL. What are the advantages? You could run a full Linux VM and do everything on it on any machine these days. Which is what I do, but I'm just an old school hack. Anyone who uses WSL care to enlighten me? Thanks!
Re: WSL2 corrupting Git repositories and shell history
#6I don't really understand the use case for WSL. What are the advantages? You could run a full Linux VM and do everything on it on any machine these days. Which is what I do, but I'm just an old school hack. Anyone who uses WSL care to enlighten me? Thanks!
Microsoft understood that they only care about having some kind of POSIX support, and nowadays being Linux compatible is more relevant than straight POSIX, as the BSDs and IllumniOS also found out with their compatibility layers.
Re: WSL2 corrupting Git repositories and shell history
#7I don't really understand the use case for WSL. What are the advantages? You could run a full Linux VM and do everything on it on any machine these days. Which is what I do, but I'm just an old school hack. Anyone who uses WSL care to enlighten me? Thanks!
Setup is much less hassle, startup is much faster (one or two seconds) and resource usage is much lower than running Linux in a VM.
Also little things like VScode (running as Windows UI application) automatically detecting WSL and setting itself up to connect to the WSL side. To do the same for a VM requires at least to configure the SSL ports on the VM.
Re: WSL2 corrupting Git repositories and shell history
#8I don't really understand the use case for WSL. What are the advantages? You could run a full Linux VM and do everything on it on any machine these days. Which is what I do, but I'm just an old school hack. Anyone who uses WSL care to enlighten me? Thanks!
I guess you'll have to use it to "believe" ;) Setup is much less hassle, startup is much faster (one or two seconds) and resource usage is much lower than running Linux in a VM. Also little things like VScode (running as Windows UI application) automatically detecting WSL and setting itself up to connect to the WSL side. To do the same for a VM requires at least to configure the SSL ports on the VM.
Re: WSL2 corrupting Git repositories and shell history
#9I don't really understand the use case for WSL. What are the advantages? You could run a full Linux VM and do everything on it on any machine these days. Which is what I do, but I'm just an old school hack. Anyone who uses WSL care to enlighten me? Thanks!
Re: WSL2 corrupting Git repositories and shell history
#10Nonetheless I hope this gets fixed before it hits me.