| 12 Mar 2025 |
|  Adam Neverwas set their display name to Adam Neverwas. | 14:27:30 |
| 13 Mar 2025 |
 mornix | Hi, I saw this is the place to talk about boot counting (via #330017). Is https://github.com/NixOS/nixpkgs/issues/337089 still seen as the way forward? And if so how can I help with boot counting? | 01:16:26 |
| 17 Mar 2025 |
 antifuchs | well this is unpleasant: it seems that systemd-networkd is now starting after zfs filesystems get unlocked, which makes it difficult for my ssh server to get online so I can remotely enter the encryption password | 13:11:46 |
| antifuchs | also, huh, did boot.initrd.systemd start setting networking.usePredictableInterfaceNames to off? I had to set up a rule for eno1 but that device isn't present, only eno1np0 and eno1np1 | 13:32:23 |
| antifuchs | * also, huh, did boot.initrd.systemd change interface naming schemes? I had to set up a rule for eno1 but that device isn't present, only eno1np0 and eno1np1 | 13:34:53 |
| antifuchs | * also, huh, did boot.initrd.systemd change interface naming schemes in nixos-unstable? I had to set up a rule for eno1 but that device isn't present, only eno1np0 and eno1np1 | 13:35:02 |
 gdamjan | that seems to be kernel dependent | 13:41:16 |
| antifuchs | yeah, seems so. I should make up my own names for netdevs | 13:52:11 |
| antifuchs | still, what a damn trap to run into /: | 13:52:20 |
| antifuchs | ok, here's a really annoying thing I don't know how to handle: when critical bootup things fail (or when prompting for my zfs unlock password), systemd kills and re-starts the password prompt every ~2-3 seconds, which makes it impossible to enter the password | 14:54:06 |
| antifuchs | (can baaarely type a 60-char password fast enough, plus the IPMI web console doesn't allow me to type that fast at all) | 14:55:41 |
| gdamjan | also sometimes a BIOS update can mangle the names (happened to me once) | 16:36:43 |
| antifuchs | yeah - I ended up using matchConfig.MACAddress in addition to a name glob, that seems to have fixed the issue | 16:37:11 |
| antifuchs | (the "in addition to" was the key, otherwise child interfaces got the parent interface config which made things look right but behave extremely wrong) (: | 16:37:44 |
 ElvishJerricco | those two shouldn't have any sort of ordering constraints against each other I don't think | 17:58:43 |
| ElvishJerricco | that's.... odd | 17:58:49 |
| antifuchs | I think on the first one, I misread that ethernet card renaming thing as another | 18:02:48 |
| antifuchs | * I think on the first one, I misread that ethernet card renaming thing as another: now that networking is straightened out, I have managed to get the ssh server to start and unlock zfs through there | 18:03:15 |
| antifuchs | but yeah, those repeating password prompts are really really annoying | 18:03:27 |
| antifuchs | it would even print "Login failed" while I was typing | 18:03:42 |
| ElvishJerricco | .... what? | 18:06:13 |
| ElvishJerricco | login failed? | 18:06:16 |
| ElvishJerricco | that's not a thing that happens in stage 1 | 18:06:32 |
| antifuchs | sorry, I'm being unclear. this is the emergency mode password prompt. Initially, that works alright: a critical unit fails, it prompts for root password, I enter it. Then I tried starting that unit again and it entered emergency mode again, this time prompting over and over | 18:09:39 |
| antifuchs | could this be a Restart="on-failure"; type thing? huh | 18:10:17 |
| ElvishJerricco | antifuchs: I'm still not quite following. What unit is failing? | 18:26:39 |
| antifuchs | that was my initrd ssh server, due to that network misconfiguration on my part. The ssh server has Restart="on-failure", which is what I suspect causes the password prompt to also restart | 18:27:59 |
| antifuchs | (restart without a rate limit, critically) | 18:28:40 |
| ElvishJerricco | That doesn't sound like what ought to be happening, huh | 18:28:40 |
| antifuchs | yea, it's not amazing ((: | 18:29:10 |
