Re:Sudo buffer overflow explained, and how to patch (WSL and...
by jelly on Friday January 29, 2021 @04:37PM
(#25962960)
In my experience there's a performance hit in filesystem-heavy work like opening and closing a lot of small files.
Still, its more than offset by the convenience of performing bash operations on Windows; remembering `du -csh ./* | sort -h` (sort directories by size) is easier than whatever Powershell would have me type.
Re:Sudo buffer overflow explained, and how to patch (WSL and...
by tyingq on Friday January 29, 2021 @05:52PM
(#25963869)
There's WSL1 and WSL2. Both have areas where performance isn't great, but the areas are different for each. Most of the issues are filesystem related, especially cross Win/Linux.
Try a 'git clone' of a reasonably large remote repo to see what it's like. Into both the windows fs and the Linux one.
Re:Sudo buffer overflow explained, and how to patch (WSL and...
by vmception on Saturday January 30, 2021 @05:06AM
(#25967822)
WSL2 is what I’m wondering about
Should I submit hashes with geth linux on wsl2 or geth windows native
I guess I could just benchmark it, havent gotten around to it.
Re:Sudo buffer overflow explained, and how to patch (WSL and...
by tyingq on Saturday January 30, 2021 @11:04AM
(#25970114)
WSL2 has reasonable performance inside the Linux filesystem, but is very slow (slower than WSL1) if you're in /mnt/c, for example. https://github.com/microsoft/WSL/issues/4197
Getting X11 up and running is a little tricky also, because localhost is not the same as localhost on the Windows box. You have to set DISPLAY to the external IP on the Windows box.
Re:Sudo buffer overflow explained, and how to patch (WSL and...
by batch12 on Friday January 29, 2021 @04:37PM
(#25962958)
Not only that, but it lets you launch windows executables too.
Re:Sudo buffer overflow explained, and how to patch (WSL and...
by jawzz on Wednesday February 03, 2021 @01:38PM
(#26017332)
Hey, I just want to apologize for my reply here [1]. Looking back I realize it was rude and simply incorrect, and I regret sending it.
Sorry to intrude on this unrelated thread but it's the only way to get in touch with you.
I sometimes can't decide if I want to use a familiar linux version of a program or a Windows version, but I like how WSL lets you access the windows file system