In the past I have used exceed on Windows to connect to a Unix server and start a CDE session. I don't currently have exceed and I looked at cygwin but after several hours the simple task of connecting to a Linux server and starting a xfce client session, running xterm/xclock seems beyond it's capabilities.
[blah blah]I stand corrected. Just launched Furmark from GpuTest, and I'm impressed.
It can also use GPU for compute task (e.g. tensorflow)but not for graphic acceleration.
on win10 I use X410 and run an ubuntu in WSL
Your goal is not 100% clear to me, so pardon me f I'm suggesting something that is not what you're after.
I think you're not after a complete X desktop environment though you mentioned CDE and xfce?
And you need to run the client on the same machine.
That's actually quite an interesting solution, had not considered MS app for WSL.WSL remains the easiest way to run user space Linux binaries on a Windows machine.
That's actually quite an interesting solution, had not considered MS app for WSL.WSL remains the easiest way to run user space Linux binaries on a Windows machine.
The available distros are just a few, but if you are sufficiently determined, you can build your own (https://docs.microsoft.com/en-us/windows/wsl/build-custom-distro).
I want to run the client on my windows 10 workstation without running a Linux client in a VM, and I want to start the session by clicking a icon on the windows taskbar.May I ask why not a VM?
I want to run the client on my windows 10 workstation without running a Linux client in a VM, and I want to start the session by clicking a icon on the windows taskbar.May I ask why not a VM?
It's is also not as convenient. Working on a PCIe driver generally I just need ssh.Yep, no argument from me. I've often worked the same way, especially when developing web service backends. (Some hate nano, but I used pine and then alpine for well over a decade, so the interface is comfy for me... and it performs OK when editing syntax-highlighted code over an SSH connection.)
WSL is an imperfect emulation layer. (Just like Wine in Linux is an imperfect emulation layer for Windows.)Not since WSL2 (available in W10 1903, and later) where it's a real VM running a real kernel (https://docs.microsoft.com/en-us/windows/wsl/compare-versions) that includes Microsoft patches to play nice(r) with the Hyper-V based hosting environment (something more with respect to the "regular" Hyper-V support that has been there since a long time):
newbrain@MUON:~$ uname -a
Linux MUON 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/LinuxThat is only the kernel, not the whole OS. It still suffers from Microsoft bugs in the OS services that do not occur in "real" Linux distributions.WSL is an imperfect emulation layer. (Just like Wine in Linux is an imperfect emulation layer for Windows.)Not since WSL2 (available in W10 1903, and later) where it's a real VM running a real kernel (https://docs.microsoft.com/en-us/windows/wsl/compare-versions) that includes Microsoft patches to play nice(r) with the Hyper-V based hosting environment (something more with respect to the "regular" Hyper-V support that has been there since a long time):Code: [Select]newbrain@MUON:~$ uname -a
Linux MUON 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
But I hope you agree that the wine analogy was quite misleading, and easy to understand as a WSL1 reference.Is it? I mean, WSL2 does run the Linux kernel in a VM, letting the kernel interact with Windows using various protocols, so technically a large part of WSL is a genuine Linux kernel. But, the kernel is not the same as the OS. For example, Android is not Linux, even though both run the Linux kernel. WSL2 still largely relies on emulation.
I was honestly surprised you could have missed WSL2!Like I said, I don't personally use Windows at all, and although I had heard that a new version of WSL had come out a year or two back (had to check; WSL2 was announced in May 2019), I haven't had any reason to check what the differences were. The reports of incompatibilities I've heard about (nginx config and getaddrinfo() immediately come to mind) didn't really specify version either (they just say WSL, not WSL1/WSL2), and the same seem to still be an issue a year later.
If I wanted to run Windows stuff, I would definitely use a VM, instead of relying on Wine.
What? I genuinely do not understand. That is definitely not the case when I use VMs.QuoteIf I wanted to run Windows stuff, I would definitely use a VM, instead of relying on Wine.I wouldn't. With the VM it's like starting your computer up just to run calculator or something, then shutting it down until you want to run that app again and waiting for the cold boot to happen again. And it's taking up huge resources to do that. Plus it's a remote machine so the local resources are meaningless to it.
The only reason I would run a VM normally (as opposed to irregular stuff) would be to run OtherOS instead of whatever this host it. That is, safer and simpler than doing dual-boot.Ah, but Windows is OtherOS to me. In the post you quoted, I did say I don't use Windows at all. I know, I'm too verbose.
When I start a VM, I start from a snapshot
My VMs never boot/shutdown/reboot
The cost is disk space.
Ah, but Windows is OtherOS to me. In the post you quoted, I did say I don't use Windows at all.
Ah, but Windows is OtherOS to me. In the post you quoted, I did say I don't use Windows at all. I know, I'm too verbose.
It's mind blowing to think about the cavalier attitude to system resources when I think back to the systems I started out on.I agree, and that's one reason why I like using virtual machines.
I usually hibernate mine (suspend to disk, with power off). But that has no impact on what you do with your VMs!QuoteWhen I start a VM, I start from a snapshotConversely, I don't :)QuoteMy VMs never boot/shutdown/rebootMine do, so I know they are starting clean. But I shut down my PC every night (or morning, as the case may be) and I understand that's not common nowadays.
Well, I don't use VMs to isolate a process, actually. I rarely have more than one VM running at the time.QuoteThe cost is disk space.Which is not insignificant. And since one reason for using a VM is to isolate some process, one tends to end up with several to many VMs since there is never one process.
Which is not to mention that if it's a serious VM then it would take up the same amount of space as one's working machine. That would double the resources, would it not?No, only storage space. Typical serious VM images I use have 8 GiB to 16 GiB images, but those are sparse (i.e., only used chunks take actual storage space). To do the stuff I want to do, I typically have about 256 GiB of unused disk space –– some things I play with take a lot of space, temporarily.
QuoteQuote from: dunkemhigh on Today at 00:24:34
Which is not to mention that if it's a serious VM then it would take up the same amount of space as one's working machine. That would double the resources, would it not?
No, only storage space.
but those are sparse
Ah, okay. To me, storage is not an expensive resource, given that I use so much of it anyway, at least temporarily.QuoteNo, only storage space.Er, that's what I was talking about there, storage space.
VirtualBox supports sparse images (otherwise known as dynamic) but they only increase in size (up to the max you've set) unless you go around zeroing out sectors and then running arcane CLI commands.Yeah, that is an user interface problem that should be fixed for sure.