[DISCUSSION] Windows Subsystem for Linux (WSL)

I installed win-kex 2.0 for Kali WSL2; it's changelog says that now it can be run as root, but if I run

sudo su
kex

I get this error:
unable to connect to socket. (10061)

It work if I run it with my non-root user

 

err I may be wrong but at least for me or I use WINDOWS or I go to any Linux distribution or at least for me never mix them

 

How to install Pop os or Manjaro on WSL 2? guide

 

You need to login to view this posts content.

 

Yes, I watched that video on Youtube. Looked quite impressive, actually. I am looking forward to trying this out, but I think I will wait until they finish testing and release it for real.

 

Has anyone tested wslg 21h2 (19044)
I failed

 

I don't understand why they don't add any ext support directly into Windows instead of using this stuff. I mean, even a read-only option would be nice.

 

You need to login to view this posts content.

 

Is WSLg still unavailable for latest "public" build - 21H2 (19044.1586)?

 

Thank you Tito, your comment made me review my WSL settings.

I issued

wsl.exe --update​

and

wsl.exe --version​

gives

WSL-version: 1.0.3.0
Kernelversion: 5.15.79.1
WSLg-version: 1.0.47
MSRDC-version: 1.2.3575
Direct3D-version: 1.606.4
DXCore-version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows: 10.0.19045.2364
​

Bash shows a blue penguinhead and

lsb_release -d​

gives

Description: Ubuntu 22.04.1 LTS​

To me, it seems unfortunate that WSL1 is going out of favour for the virtual machine version or WSL2. Since I use the developer tools in WSL on the regular Windows native filesystem, WSL1 is faster and better suited - as I understand it. I guess WSL1 was too complicated and expensive to maintain but it is a pity it's going away. Using WSL2 means I have to move my developer tree into the distribution filesystem which is not a good solution for several reasons.

edit:
Yes, I might add wsl.exe --update did not change my distribution in any way like installation path etc.

 

You need to login to view this posts content.

 

I installed WSL on Windows 11 and installed Ubuntu. Got to the command prompt, updated and upgraded, all fine.
Now I want to shutdown.
Have spent the last 40 minutes looking for the command to shutdown. The system is using svsinit I think. Using shutdown -h tells me:

The system has not been booted using systemd as init system (PID1). Can't operate.
Failed to connect to bus: Host is down.

Someone please help.
Also please tell me how to move from svsinit to systemd, as all the documentation seems to be based on systemd.

[EDIT]
After 3 hours of searching, opened another powershell window, typed wsl --shutdown
Then created a wsl.conf file in /etc/ and put the following lines in it:
[boot]
systemd=true
Shutdown and restarted wsl again. Now the sudo poweroff command works.

 

You need to login to view this posts content.