| 10 Aug 2024 |
 K900 | Not currently | 06:01:35 |
| K900 | I believe aarch64 WSL is kind of a mess | 06:01:42 |
 Riley Cat | well, i was expecting issues like what i got with wsl/ubuntu, like nested virtualization being a bit of a trash fire | 15:27:16 |
| Riley Cat | not hello world being completely borked | 15:27:28 |
| Riley Cat | ah, well. do you think contributions from these devices will help? or is it more of a waiting for kernel updates thing | 15:36:12 |
| K900 | I mean, you'd have to troubleshoot it yourself | 15:37:25 |
| K900 | But if you find fixes, please submit them | 15:37:31 |
 nzbr (they/it) | I'd love to support it officially, but we don't have access to aarch64 github runners and the only windows on arm device I have myself is a VM on an M1 Mac, which can't do nested virtualisation at all, so no Hyper-V in the VM | 15:59:50 |
| Riley Cat | i have a current gen surface laptop but i'm afraid i wouldn't even begin to know where to look about proc/self throwing up like that | 17:55:43 |
| K900 | https://github.com/microsoft/WSL/releases/tag/2.3.17 | 18:49:57 |
| K900 | Great | 18:49:57 |
| 11 Aug 2024 |
 Gleydar | Huh, there goes the cgroupsV2 | 13:43:50 |
| 13 Aug 2024 |
| Gleydar | I was wondering, how do the specialisations work with nixos-wsl exactly? 😄
I created a specialisation to set a proxy server. Switching to the specialisation works like expected via sudo /run/current-system/specialisations/<name>/bin/switch-to-configuration test, and the proxy is set e.g. in the nix-daemon override file.
However, I sadly have some issues switching back to my base config... I tried using sudo /run/current-system/bin/switch-to-configuration test however, in that case the proxy server is still set in the nix-daemon override...
| 11:04:33 |
| Gleydar | * I was wondering, how do the specialisations work with nixos-wsl exactly? 😄
I created a specialisation to set a proxy server. Switching to the specialisation works like expected via sudo /run/current-system/specialisations/<name>/bin/switch-to-configuration test, and the proxy is set e.g. in the nix-daemon override file.
However, I sadly have some issues switching back to my base config... I tried using sudo /run/current-system/bin/switch-to-configuration test however, in that case the proxy server is still set in the nix-daemon override...
| 11:04:42 |
| Gleydar | * I was wondering, how do the specialisations work with nixos-wsl exactly? 😄
I created a specialisation to set a proxy server. Switching to the specialisation works like expected via sudo /run/current-system/specialisations/<name>/bin/switch-to-configuration test, and the proxy is set e.g. in the nix-daemon override file.
However, I sadly have some issues switching back to my base config... I tried using sudo /run/current-system/bin/switch-to-configuration test however, in that case the proxy server is still set in the nix-daemon override... Only when I do a wsl --shutdown can I switch back to my base config.
Could anyone point me to the right command to use for switching from specialisation to base?
| 11:05:33 |
| nzbr (they/it) | We don't do anything to handle specialisations specifically. You can probably do it the same way as on bare-metal NixOS. I haven't used the feature much though, so I can't say how that would look exactly | 14:37:39 |
| 15 Aug 2024 |
|  ~ajhalili2006 [tildeverse / backup of @ajhalili2006:andreijiroh.dev] changed their display name from ~ajhalili2006 [ recaptime.eu.org / sr.ht / tildeverse ] to ~ajhalili2006 [ recaptime.dev / sr.ht / tildeverse ]. | 17:25:51 |
| 16 Aug 2024 |
|  @nebucatnetzer13:matrix.org set a profile picture. | 11:06:00 |
| Gleydar | In reply to @nzbr:nzbr.de
We don't do anything to handle specialisations specifically. You can probably do it the same way as on bare-metal NixOS. I haven't used the feature much though, so I can't say how that would look exactly Sadly, this seems a bit broken... It is mentioned in the wiki that some things only reset on boot. Even though adding variables to the service works (in my case adding the proxy), apparently removing variables isn't supported when using test... | 11:26:05 |
|  Aurora Ennie Seidr (she / her) joined the room. | 14:55:12 |
| Aurora Ennie Seidr (she / her) | Yay! | 14:55:22 |
| Aurora Ennie Seidr (she / her) | It worked | 14:55:29 |
| K900 | But yeah, basically, you can set up an SSH server on your Windows | 14:55:49 |
| K900 | Then run wsl inside that | 14:55:53 |
| K900 | And get dropped into a WSL shell | 14:55:59 |
| Aurora Ennie Seidr (she / her) | I'm so sorry. I literally hate used windows only enough for work and limited professional troubleshooting. All of my stuff went the cloud vm route
Kudos for them and not mandating "Windows terminal server" any more I guess? | 14:57:21 |
| K900 | Windows is honestly a lot better now | 14:57:37 |
| Aurora Ennie Seidr (she / her) | In reply to @k900:0upti.me
Windows is honestly a lot better now Yeah I thought people were on metaphorical acid when they told me about all the good Microsoft did.
I remember when the documents got leaked from their engineering team where they wanted to totally kill Linux | 14:58:50 |
| Aurora Ennie Seidr (she / her) | In reply to @k900:0upti.me
Windows is honestly a lot better now Yeah I noticed actually | 14:59:04 |
| Aurora Ennie Seidr (she / her) | Okay so install the openssh server via the link you provided. Start the WSL 2 instance via wsl -d NixOs and then it drops me into the system with full access from there?
My only issue now is getting connected to this openssh port from my zerotier network? Since it's going to be powershell I have no idea if they have it for that | 15:02:22 |
