Since there’s almost always comments from people saying how they’re happy on Windows whenever there’s news about some fuckup on macOS, I’d like to balance it by saying that shit like this is why I’m never going back to Windows.
WSL2 corrupting Git repositories and shell history
361–370 of 423 posts
Re: WSL2 corrupting Git repositories and shell history
#362Re: WSL2 corrupting Git repositories and shell history
#363Earlier 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.
Cool. I'll use WSL though.
Re: WSL2 corrupting Git repositories and shell history
#364Earlier quoted context omitted.
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 a…
The only situation when BTRFS breaked badly to me, was when we run guests on Hyper-V .
Re: WSL2 corrupting Git repositories and shell history
#365Earlier quoted context omitted.
What a horrible amount of overhead. Why does Defender need to scan the contents of a bunch of non-executable files? I suspect the answer runs deep and is at least somewhat horrifying.
because windows has no concept of an executable bit, so a rename could make it runnable? or a benign looking program has a built-in interpreter run code from external file?
> because windows has no concept of an executable bit, so a rename could make it runnable
This much I understand - but why can something so tightly integrated into the OS not instead intercept a file rename event and scan at that point?
I seem to be lacking sufficient information as to what specifically about Windows necessitates scanning everything on the filesystem when macOS and the various common Linux distros seem to do fine without it. It's not as if Windows is the only OS with interpreters, either.
Re: WSL2 corrupting Git repositories and shell history
#366Earlier quoted context omitted.
What a horrible amount of overhead. Why does Defender need to scan the contents of a bunch of non-executable files? I suspect the answer runs deep and is at least somewhat horrifying.
Virus do abuse non executables like js, vbs, or whatever script file. Antivirus can't really know if it is the case without open it.
What is it about Windows that makes this a problem where macOS and Linux seem to be fine? The same mechanisms exist in all three major operating systems, which is to say that technically any executable I choose to run on my computer can load a file and interpret it.
Is it really just that Windows users download and run random junk? It's been so long that I've seen a virus of any kind anywhere at all that I genuinely have no clue how people become infected with them or indeed whether it still really happens at all.
It certainly feels to me that the era of random toolbars and clearly visible desktop malware is over, but at the same time I live in a different bubble than in the past.
Re: WSL2 corrupting Git repositories and shell history
#367Earlier quoted context omitted.
But why? WSL1 was something like wine but reverse, but WSL2 is actually linux.
The problem is likely not in the Ext4 code, but in the block I/O driver (which is Hyper-V specific, IIRC) or even in Hyper-V itself. Several reports mention Windows shutdowns, sleep or hibernation, so it may be a simple unclean shutdown of the VM. A bigger problem would be if Hyper-V is either ignoring memory barriers, or caching writes to the disk and losing them when the Hyper-V service is shutdown. But that would…
> Hyper-V service is shutdown
as far as I know when wsl2 is actiavted, hyper-v runs as type-1 and linux, windows are virtual after activating it.
thus if it crashes, you get a bsod
Re: WSL2 corrupting Git repositories and shell history
#368Re: WSL2 corrupting Git repositories and shell history
#369WSL2 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…
between apple silicon and x86 container performance issues from emulation and wsl2 being what sounds like a pretty big regression... drum roll
...maybe 2021 is finally the year of the linux desktop...
Re: WSL2 corrupting Git repositories and shell history
#370Earlier quoted context omitted.
Oh you need to fucking disable Window's Defender though, or add exclusions for your Linux distro/WSL2 folder, because when installing "node_modules" it will attempt to do realtime scans for threat-protection which absolutely cripples the speed. https://www.cicoria.com/improving-windows-subsystem-for-linu... https://www.reddit.com/r/bashonubuntuonwindows/comments/eok7... "I noticed a significant performance difference…
Why do you even need a Windows workstation as a Ruby or Node developer? That doesn't make any sense.
You don't need it but it's 1/3 the price of an Apple workstation and just runs with all hardware compared to Linux.
Plus, some people just like Windows and/or don't like macOS.