Extend.
> Weston is the Wayland project reference compositor and the heart of WSLg. For WSLg, we've EXTENDED the existing RDP backend of libweston to teach it how to remote applications rather than monitor/desktop.
It has been admitted.
Windows Subsystem for Linux GUI
51–60 of 473 posts
Re: Windows Subsystem for Linux GUI
#52I wonder what Linux exclusive software they are hoping to support. Everything I use in my Ubuntu daily driver has a Windows build or corollary app. I get how ‘you never have to leave Windows’ is a nice thing for their business, but I don’t see this being a reason I would stop dual-booting. The only reason I run windows in the first place is for a few apps, mostly games. Otherwise I really enjoy the bloat-free, ad-fre…
Whenever you want to natively operate on files within WSL instead of going through the network share abstraction, this is definitely helpful. I'm running my git GUI (Sublime Merge) on the Linux side and am currently piping the UI through to Windows using VcxServe. If I can remove another dependency using this - great.
Re: Windows Subsystem for Linux GUI
#53Now someone make a Linux Subsystem for Windows GUI.
I guess it would be this: https://github.com/Fmstrat/winapps
Re: Windows Subsystem for Linux GUI
#54WSL2 is essentially just.. Windows + Linux. I tried it and it is awesome. Cannot wait to see further progress that comes out of this. I really cannot leave Windows to be honest. The network effect is too strong. Coupled with recent Microsoft effort such as Visual Code, its looking like they are doing nothing but going towards the better direction than the old days. Who would have thought. Would you believe it if anyo…
> its looking like they are doing nothing but going towards the better direction than the old days
Re: Windows Subsystem for Linux GUI
#55Amazingly this seems better integrated than Mac's XQuartz which I always find awkward and buggy. If it weren't for the forced ads and updates I would consider switching back to Windows.
Re: Windows Subsystem for Linux GUI
#56Will I be able to use i3?
This will be available in Windows 11, so your processor does have to be able to upgrade to that. If you're fine with an OS reinstall there are ways to force the install.
I don't think he is referring to an i3 processor, but rather https://i3wm.org/
Re: Windows Subsystem for Linux GUI
#57Earlier quoted context omitted.
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.
>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.)
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
[1] https://github.com/torvalds/linux/blob/master/include/linux/...
Re: Windows Subsystem for Linux GUI
#58I just might switch to linux instead.
You can always fall back on the Linux Subsystem for Windows GUI, aka WINE/DOSBox/VMW/VBX/QEMU, with varying levels of integration/fiddle/config.
Re: Windows Subsystem for Linux GUI
#59I already asked this in the past, and want to ask again. Is Microsoft a corporation of goodness now?
Microsoft has just shifted to being what IBM was in that late 90s for all intents and purposes. IBM didn't care what you ran on their platforms, even at the OS level. They just wanted that sweet sweet support contract and computer leasing money. "You want to run Linux on our mainframes? Hell yeah, sign here." Now with Azure, Microsoft gets money of the same shape, and correspondingly makes some of the same strategic choices.
Re: Windows Subsystem for Linux GUI
#60Earlier quoted context omitted.
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.
>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.)
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.