| 13 Nov 2022 |
 K900 | So uh | 17:00:47 |
| K900 | Pro tip | 17:00:48 |
| K900 | Make sure you escape backslashes in your .wslconfig | 17:01:00 |
| K900 | Or you'll end up with swap in %TEMP% and no disk space again | 17:01:11 |
| K900 | Also for the love of god please don't write any more software that uses loosely defined .ini files as config | 17:01:38 |
| K900 | At least use TOML | 17:01:47 |
 nzbr (they/it) | That is good to know (i may or may not have just put some extra backslashes in there) | 17:02:40 |
| K900 | To clarify | 17:14:10 |
| K900 | The failure mode for "swap location is not a valid path" is "whatever just stick it in %TEMP% who cares lmao" | 17:14:24 |
| K900 | Which is not a good failure mode | 17:14:31 |
| K900 | Honestly I am still very impressed by the fact that WSL somehow does not have an out of band error log | 17:15:42 |
| K900 | Like this feels like a thing that should have been there | 17:15:54 |
| nzbr (they/it) | They should validate that file, when you try to boot the WSL VM, but probably decided that the don't want it to not boot if there's something wrong. But like - at least print a warning or something like that | 17:16:33 |
| nzbr (they/it) | You can enable a debug console, but every time I tried, it just instantly closed itself | 17:17:06 |
| K900 | The debug console is just dmesg from the VM | 17:17:56 |
| nzbr (they/it) | In reply to @k900:0upti.me
Honestly I am still very impressed by the fact that WSL somehow does not have an out of band error log If there is, I guess its buried deeeeep in event viewer | 17:19:54 |
| K900 | I couldn't find anything there last time I made it not boot | 17:20:06 |
| nzbr (they/it) | Microsofts Troubleshooting website is rather lacking - a lot of the things on there only apply to ubuntu anyway | 17:26:41 |
| 15 Nov 2022 |
|  michael_j_ward joined the room. | 12:38:00 |
| michael_j_ward | I am fairly novice at windows, so apologies. Is there a way to have windows start my nixos WSL distribution on powerup
I have a desktop box in an office which unfortunately loses power frequently, and I would like the WSL to start-up automatically when power recovers.
| 12:53:43 |
| nzbr (they/it) | Not officially as far as I am aware | 12:54:54 |
| michael_j_ward | gracias | 12:55:19 |
| nzbr (they/it) | But it is possible | 12:55:39 |
| K900 | You can just add wsl -e true to startup | 12:57:42 |
| nzbr (they/it) | -e bypasses the user shell (and thus syschdemd) | 12:58:55 |
| nzbr (they/it) | distrod has a working solution, I'm looking into it right now | 12:59:31 |
| nzbr (they/it) | Ok, you need to grab this file from distrod | 13:02:54 |
| nzbr (they/it) | In there replace {{USER_NAME}} with your Windows username, \{{TASK_NAME}} with \StartNixOS (the name doesn't matter as long as it contains no spaces and you keep the backslash) and {{DISTRO_NAME}} with the name you imported NixOS as (probably NixOS). Each of these should appear exacly once in the file | 13:05:45 |
| nzbr (they/it) | Then you should be able to add it to Task Scheduler by running
schtasks.exe /create /ru YOURUSERNAMEHERE /tn StartNixOS /xml .\distrod_autostart.xml
in an admin powershell
| 13:08:13 |
| nzbr (they/it) | I hope that works, haven't tested it myself yet | 13:09:41 |
