GWSL: Run graphical Linux apps in WSL

Post by folkrav » Fri, Dec 18, 2020, 6:46 PM UTC

Dylan16807 wrote: post #120

folkrav wrote: post #100

Earlier quoted context omitted.

WSL1 was more or less the reverse-equivalent of WINE as I understood it, more or less a translation layer for a subset of syscalls, the approach is awfully limited from the get go. Not sure how using a VHDX or partition would solve that. We'd be back to square one, with things like containers being unusable again.

It's not all that limited. VHDX/partition would help significantly by not being NTFS and/or enabling a linux-style dentry cache.

I wouldn't call having only a subset of system calls, no containerization, no background services, no proper init system, no kernel modules, "not all that limited". But maybe that's just my use case.

Post by Dylan16807 » Sat, Dec 19, 2020, 1:19 AM UTC

folkrav wrote: post #131

Dylan16807 wrote: post #120

Earlier quoted context omitted.

It's not all that limited. VHDX/partition would help significantly by not being NTFS and/or enabling a linux-style dentry cache.

I wouldn't call having only a subset of system calls, no containerization, no background services, no proper init system, no kernel modules, "not all that limited". But maybe that's just my use case.

I've never hit a system call I wanted but wasn't available on WSL. In fact the couple times I've been disappointed at the lack of a system call it was when I was booting linux.

No containerization: Agreed, this is a significant limit.

Background services work just fine, I don't know what you're getting at. I have cron and stuff going.

What's improper about the init system? I start services, I stop services, it seems fine.

No kernel modules: I feel like this is pretty niche.

Re: GWSL: Run graphical Linux apps in WSL

Re: GWSL: Run graphical Linux apps in WSL