Our great sponsors
-
wslg
Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
winapps
Run Windows apps such as Microsoft Office/Adobe in Linux (Ubuntu/Fedora) and GNOME/KDE as if they were a part of the native OS, including Nautilus integration.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
It's so weird to see Teams on the Windows Desktop next to a Linux Desktop Window... [0]
[0] https://github.com/microsoft/wslg/raw/main/docs/WSLg_Integra...
>But I mean come on, they're Microsoft. If they really wanted filesystem access to be efficient across systems, we'd have it by now.
Here's one of the developers saying it is hard back in the WSL days.
https://github.com/Microsoft/WSL/issues/873#issuecomment-391...
The reason makes sense to me, but I'm not an expert. Maybe you could expand on why you think they could do it but chose not to?
I don't think he is referring to an i3 processor, but rather https://i3wm.org/
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/...
I haven't personally done much with VFIO but I have looked at it. From my initial look it seemed as if it would require two gpus, one for the host and one for the guest but it looks like some people have single gpu setups working
https://github.com/joeknock90/Single-GPU-Passthrough
You might want to try this tool.
https://github.com/rvaiya/keyd
That's not NV related sadly, but applies for all Android TV devices. It's beyond their control...
And for PCIe VFs for virtualized GPUs, AMD does _not_ provide it either outside of their datacenter line.
(btw, for some NV cards, there is: https://github.com/DualCoder/vgpu_unlock to crack that protection)