| 14 Feb 2023 |
 JoelMcCracken | thx | 20:17:37 |
| 16 Feb 2023 |
 Sandro 🐧 | https://github.com/microsoft/WSL/releases/tag/1.1.3 | 00:11:00 |
 K900 | FYI: https://github.com/msteen/nixos-vscode-server/pull/51 | 18:20:33 |
| 17 Feb 2023 |
| K900 | In reply to@k900:0upti.me
FYI: https://github.com/msteen/nixos-vscode-server/pull/51 OK, that was actually wrong, the real issue is worse | 09:22:29 |
| K900 | Something is going very wrong with its attempt to race vscode | 09:22:45 |
| K900 | services.vscode-server.enableFHS gets it working | 09:23:58 |
| K900 | Because there's less racing | 09:24:09 |
 Arson Copperflame | I just switched to nix-ld and so far that seems like the more stable approach to me | 10:06:18 |
| K900 | I should really set that up at some point | 10:25:19 |
| K900 | OK wow | 10:39:20 |
| K900 | It's just programs.nix-ld.enable now huh | 10:39:28 |
| K900 | Noice | 10:39:29 |
| Sandro 🐧 | and a second option to add packages | 13:37:26 |
| 18 Feb 2023 |
 henrik-ch | I am continuing my adventures in nixos wsl and discovered something that I want to get your advice on:
This command seems to always work in PowerShell: wsl -d nixos
On the other hand, when I try and run with a specified user, like wsl -d nixos -u i97henka, it only works if I have logged in with the nixos user first.
Is that expected behaviour, or does it point at something being wrong with my setup?
Here a small PS extract:
PS C:\Users\i97he> wsl -d nixos -u i97henka <3>WSL (10) ERROR: CreateProcessEntryCommon:570: execvpe /run/current-system/sw/bin/bash failed 2 <3>WSL (10) ERROR: CreateProcessEntryCommon:579: Create process not expected to return PS C:\Users\i97he> wsl -d nixos -u i97henka
[i97henka@nixos:/mnt/c/Users/i97he]$
| 16:35:44 |
| K900 | Use native systemd | 16:36:08 |
| K900 | Don't use not native systemd | 16:36:20 |
| henrik-ch | * I am continuing my adventures in nixos wsl and discovered something that I want to get your advice on:
This command seems to always work in PowerShell: wsl -d nixos
On the other hand, when I try and run with a specified user, like wsl -d nixos -u i97henka, it only works if I have logged in with the nixos user first.
Is that expected behaviour, or does it point at something being wrong with my setup?
Here a small PS extract:
PS C:\Users\i97he> wsl -d nixos -u i97henka <3>WSL (10) ERROR: CreateProcessEntryCommon:570: execvpe /run/current-system/sw/bin/bash failed 2 <3>WSL (10) ERROR: CreateProcessEntryCommon:579: Create process not expected to return PS C:\Users\i97he> wsl -d nixos -u i97henka
[i97henka@nixos:/mnt/c/Users/i97he\]$
| 16:37:20 |
| henrik-ch | * I am continuing my adventures in nixos wsl and discovered something that I want to get your advice on:
This command seems to always work in PowerShell: wsl -d nixos
On the other hand, when I try and run with a specified user, like wsl -d nixos -u i97henka, it only works if I have logged in with the nixos user first.
Is that expected behaviour, or does it point at something being wrong with my setup?
Here a small PS extract:
PS C:\Users\i97he> wsl -d nixos -u i97henka
<3>WSL (10) ERROR: CreateProcessEntryCommon:570: execvpe /run/current-system/sw/bin/bash failed 2
<3>WSL (10) ERROR: CreateProcessEntryCommon:579: Create process not expected to return
PS C:\Users\i97he> wsl -d nixos -u i97henka
[i97henka@nixos:/mnt/c/Users/i97he\]$
| 16:38:02 |
| K900 | Can we please just drop syschdemd already, I genuinely don't care about the three people stuck on <=20H2 | 16:38:39 |
| henrik-ch | Thanks for reply @K900 - am I on the right track here you think? - https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/ | 16:40:37 |
| K900 | No | 16:40:49 |
| K900 | Just set wsl.nativeSystemd = true in your config, rebuild, then restart your WSL VM | 16:41:33 |
| henrik-ch | That works - thanks a lot 👍️🙂👍️ 🙏 | 16:45:05 |
|  cycyone3 changed their profile picture. | 17:08:58 |
|  Biswa96 joined the room. | 19:25:40 |
| 19 Feb 2023 |
| Biswa96 left the room. | 09:10:35 |
|  Andreas Weinzierl joined the room. | 23:22:46 |
| 20 Feb 2023 |
| henrik-ch | Download configuration.nix | 20:45:12 |
| henrik-ch | I am trying to change my nixos-wsl configuration.nix to add nixvim - as described here:
https://github.com/pta2002/nixvim#without-flakes
what confuses me is that in the nixvim example, lib is an input, whereas in my configuration.nix it is not. As a starting point, I just added lib as an input, and that worked, but when I tried the import it failed sayint there is no lib.fetchGit function.
Attached my current non-working nixos-wsl configuration.nix
| 20:45:18 |
| henrik-ch | * I am trying to change my nixos-wsl configuration.nix to add nixvim - as described here:
https://github.com/pta2002/nixvim#without-flakes
what confuses me is that in the nixvim example, lib is an input, whereas in my configuration.nix it is not. As a starting point, I just added lib as an input, and that worked, but when I tried the import it failed saying there is no lib.fetchGit function.
Attached my current non-working nixos-wsl configuration.nix
| 20:45:44 |
