!apXxbtexmNGJaAryzM:nixos.org

NixOS on WSL

332 Members
https://github.com/nix-community/NixOS-WSL55 Servers

Load older messages


SenderMessageTime
18 Aug 2024
@whovian9369:matrix.orgWhovian9369 wsl.exe --shutdown, add that, and try again? 21:00:00
@k900:0upti.meK900Thank Microsoft for not shipping a cgv2-by-default kernel like three months after Ubuntu shipped it as a requirement21:00:16
@k900:0upti.meK900(and like multiple years after everyone else decided it was a good idea)21:00:28
@whovian9369:matrix.orgWhovian9369
╭─whovian@nixos-wsl ~
╰─$  sudo whoami
root

Okay cool, this is a good sign

21:02:34
@whovian9369:matrix.orgWhovian9369And the errors on every tab are magically gone, which means that all of the services are starting as I'd expect again. Thank you so so much for the help and time, K900. 21:03:12
@k900:0upti.meK900I just realized we can probably get better errors if we actually dup systemd logs to kmsg21:04:57
@k900:0upti.meK900 CC @nzbr:nzbr.de 21:05:02
@k900:0upti.meK900Oh never mind 21:10:06
@k900:0upti.meK900systemd is trying to be smart 21:10:10
@k900:0upti.meK900And write to /dev/console21:10:18
@k900:0upti.meK900And guess what WSL does to that 21:10:23
@whovian9369:matrix.orgWhovian9369 Then as a followup question, do you know if there's a way to automatically check for the .wslconfig entry (without reading the file directly) to warn a user to add it? 21:11:49
@k900:0upti.meK900No 21:11:58
@k900:0upti.meK900We basically have no user facing communication until after systemd21:12:13
@k900:0upti.meK900And when there's no systemd, there's also no after 21:12:29
@k900:0upti.meK900Hopefully Microsoft will just fix it 21:14:04
@k900:0upti.meK900 After enough people update to Ubuntu 24.04 and explode 21:14:16
@whovian9369:matrix.orgWhovian9369
In reply to @k900:0upti.me
We basically have no user facing communication until after systemd
I was thinking on nixos-rebuild or something. (Or other tests after systemd would launch to print "Hey, you may want to fix this...")
21:15:36
@k900:0upti.meK900See the problem is all of those things work after systemd has launched 21:17:57
@k900:0upti.meK900Which doesn't happen when things break21:18:08
@whovian9369:matrix.orgWhovian9369Fair enough, I guess that I was mistaken on what you initially meant.21:18:38
@k900:0upti.meK900There's also some group policy nonsense so it's hard to get the final config21:22:38
@k900:0upti.meK900We could try to detect it on upgrade 21:22:48
@k900:0upti.meK900But that won't help new installs 21:22:54
@k900:0upti.meK900Basically it's fucked 21:23:00
@k900:0upti.meK900Microsoft is one kconfig line away from fixing it and they just haven't 21:23:47
@nzbr:nzbr.denzbr (they/it)
In reply to @k900:0upti.me
I just realized we can probably get better errors if we actually dup systemd logs to kmsg
I had that working on my canceled syschdemd rust-rewrite, so it should probably also be possible to pass the relevant option through the shim. I'll make an issue to look into that
23:49:30
20 Aug 2024
@shymega:one.ems.host@shymega:one.ems.host left the room.13:17:44
22 Aug 2024
@asmundesen:matrix.orgArtur Manuel joined the room.12:57:59
@asmundesen:matrix.orgArtur Manuel changed their profile picture.14:53:06

Show newer messages


Back to Room ListRoom Version: 9