3 ms·

Now someone make a Linux Subsystem for Windows GUI.

rubyn00bie 5y ago
Isn't that pretty much what Wine does? Having been using Linux as my daily workstation for a year now, I've been blown away how easy it is (and generally transparent) to install and use Windows applications on Linux.
- spijdar 5y ago
  Actually, not quite. Wine is closer to what WSL1 was. The closest equivalent to "Windows Subsystem for Linux GUI" on WSL2 for Linux would just be ... running Windows in a VM, with FreeRDP doing per-app tunneling to the Linux host. I think there's even some software for automating this somewhere out there.
  - edgyquant 5y ago
    >Wine is closer to what WSL1 was Not quite. Wine just translates windows syscalls to linux ones but WSL actually reimplemented the linux api inside the NT kernel (which was designed with the ability to use multiple OS apis.)
    - spijdar 5y ago
      Well, I said "closer", not an exact analogue. They're pretty close equivalents, though, as most Windows programs don't actually call syscalls directly, but link in an OS-provided DLL and call an exported symbol from it, with the userspace to kernel bits abstracted away from most user programs. Wine (mostly) re-implements those DLLs, effectively re-implementing the Win32 API (a userspace API) in Linux's userland. (programs are allowed to call the kernel directly, though, and Wine has to handle those cases esp. for DRM/anti-cheat code in games that poke at the kernel directly, recently Linux was patched to allow userspace programs to directly handle syscalls [0][1], making Wine ... closer to a WSL1 equivalent?) [0] https://lkml.org/lkml/2020/8/10/1323 https://lkml.org/lkml/2020/8/10/1323 [1] https://github.com/torvalds/linux/blob/master/include/linux/syscall_user_dispatch.h https://github.com/torvalds/linux/blob/master/include/linux/...
    - zamadatix 5y ago
      Neither reimplemented the other syscalls directly in the kernel. In WSL1 the NT kernel kicked Linux syscalls to an lxcore.sys driver to convert them into equivalent NT calls and objects. In WINE most things don't make direct syscalls (they make userspace Win32 calls and WINE reimplements that and many other Windows APIs in a way that calls Linux syscalls directly) but for those that do (e.g. game DRM) the Linux kernel added a SECCOMP_MODE_MMAP mode to seccomp() to trap unknown syscalls to a handler (in this case WINE) to do the same thing.
    - emilsedgh 5y ago
      As far as I understand Wine does way, way more than that. Wine actually re-implements all Windows API's. Not syscalls, but higher level libraries like DirectX and whatnot.
teddyfrozevelt 5y ago
I guess it would be this: https://github.com/Fmstrat/winapps https://github.com/Fmstrat/winapps
- b215826 5y ago
  Thanks, this sounds like an interesting project. Will look into it.

Isn't that pretty much what Wine does? Having been using Linux as my daily workstation for a year now, I've been blown away how easy it is (and generally transparent) to install and use Windows applications on Linux.

spijdar 5y ago
Actually, not quite. Wine is closer to what WSL1 was. The closest equivalent to "Windows Subsystem for Linux GUI" on WSL2 for Linux would just be ... running Windows in a VM, with FreeRDP doing per-app tunneling to the Linux host. I think there's even some software for automating this somewhere out there.
- edgyquant 5y ago
  >Wine is closer to what WSL1 was Not quite. Wine just translates windows syscalls to linux ones but WSL actually reimplemented the linux api inside the NT kernel (which was designed with the ability to use multiple OS apis.)
  - spijdar 5y ago
    Well, I said "closer", not an exact analogue. They're pretty close equivalents, though, as most Windows programs don't actually call syscalls directly, but link in an OS-provided DLL and call an exported symbol from it, with the userspace to kernel bits abstracted away from most user programs. Wine (mostly) re-implements those DLLs, effectively re-implementing the Win32 API (a userspace API) in Linux's userland. (programs are allowed to call the kernel directly, though, and Wine has to handle those cases esp. for DRM/anti-cheat code in games that poke at the kernel directly, recently Linux was patched to allow userspace programs to directly handle syscalls [0][1], making Wine ... closer to a WSL1 equivalent?) [0] https://lkml.org/lkml/2020/8/10/1323 https://lkml.org/lkml/2020/8/10/1323 [1] https://github.com/torvalds/linux/blob/master/include/linux/syscall_user_dispatch.h https://github.com/torvalds/linux/blob/master/include/linux/...
  - zamadatix 5y ago
    Neither reimplemented the other syscalls directly in the kernel. In WSL1 the NT kernel kicked Linux syscalls to an lxcore.sys driver to convert them into equivalent NT calls and objects. In WINE most things don't make direct syscalls (they make userspace Win32 calls and WINE reimplements that and many other Windows APIs in a way that calls Linux syscalls directly) but for those that do (e.g. game DRM) the Linux kernel added a SECCOMP_MODE_MMAP mode to seccomp() to trap unknown syscalls to a handler (in this case WINE) to do the same thing.
  - emilsedgh 5y ago
    As far as I understand Wine does way, way more than that. Wine actually re-implements all Windows API's. Not syscalls, but higher level libraries like DirectX and whatnot.

teddyfrozevelt 5y ago

I guess it would be this: https://github.com/Fmstrat/winapps https://github.com/Fmstrat/winapps

b215826 5y ago
Thanks, this sounds like an interesting project. Will look into it.