Windows 10 Insider Preview Fast Build 19592.1001 - March 25 Insider

Hi there

@martyfelker

I think this works for you from Windows (This release) too logon to Linux Desktop FROM Windows

1) on Linux side install these packages x2goserver sqlite fuse and ensure openssl or similar is running and start the server.



2) on the Windows side ensure you can ssh into the linux system -- install the ssh client AND x2goclient.

Have fun !!!! --you need to mess around with a couple of config files but these depend on the distro you are using

Cheers
jimbo

Wish he had another forum for his usage. Pretty boring and irrelevant for most insiders.

Kari said:

I do not know what Marty's issue is, as he is (and will remain) on my ignore list, so I do not see his posts. Anyway, if this is about getting desktop experience on WIndows Bash / WSL, please see this tutorial: Windows Subsystem for Linux - Add desktop experience to Ubuntu

Kari

Hi there
@Kari
Thanks for the tutorial info :

However with the new kernels and WAYLAND as the "X-Server" issue instead of the XORG system it's possible only to get some GUI applications to run e.g file manager, etc. Full desktop doesn't work . The WSL though is fine for running Bash scripts etc but still needs a few improvments such as making it easy to read native formatted Linux HDD's etc.

The other issue of course is that you have to use the distro supplied from the store --it's not yet possible to run your own distros and the kernel isn't a "Stock" kernel but one specifically written for the WSL.

The issue was trying to login to the desktop of a ubuntu VM from a Windows system which isn't that easy to do these days -- of course logging in to any sort of Windows VM FROM Linux isn't a problem at all -- even things like xrdp etc (works as RDP on Linux) will connect TO windows without issue (other than the security and slow speed of RDP if doing over a remote network --I.e the VM isn't on the same machine that your Windows system is running on.

Cheers
jimbo

Hi folks

there's some confusion then as to what 20H2 is / will be -- maybe should be called 21Hxx since it's probably unlikely to be released this year.

Surely the only testing cycles they need to bring out is - future enhancements (?) to current release (before passing the updates to users), next release / version and a possible development "alpha" release to try out experimental new features and things which probably will break but it's an "alpha" so people using it would be prepared for this.

The other alternative would be to go to two sorts of Windows -- a Long Term version with minimal changes for corporate users and those who value stability apart from serious security issues, and a rolling release for those who want "leading edge" updates etc. Probably easier all round, easier to manage development teams and rollouts and get some type of sensible change management in place.

@f14tomcat : Beer time -- at least there's plenty of booze around !!!!! still deemed "Necessary" in shopping for essentials !!!!!!

Cheers
jimbo