| 28 Jul 2025 |
 magic_rb | In reply to @emilazy:matrix.org
well,
message = "ifstate.nix does not currently implement a systemd unit for initrd. Please continue to use the scripted stage one for the time being.";
I dont see why it couldnt, at least v1, i havent used v2 | 17:45:37 |
 emily | (we are hoping to flip the default to systemd initrd within the month) | 17:45:38 |
| emily | I didn't say couldn't :P I'm just talking about what the module actually says, in the context of upstreaming it | 17:45:52 |
| magic_rb | In reply to @emilazy:matrix.org
(we are hoping to flip the default to systemd initrd within the month) (Finally) | 17:45:55 |
| magic_rb | In reply to @emilazy:matrix.org
I didn't say couldn't :P I'm just talking about what the module actually says, in the context of upstreaming it Ah okay | 17:46:01 |
 @marcel:envs.net | In reply to @emilazy:matrix.org
so yeah we'd want to drop the initrd support for upstreaming or else implement systemd initrd support (and probably only systemd initrd support) i've just never came to create a unit, because all my sytems still use scrypted stage 1 - allthough thats something, that i will definitely add | 17:47:14 |
| emily | the initrd stuff should also probably be under boot.initrd.* so you can have distinct config in initrd, that's how it works for repart and networkd though not 100% sure | 17:47:25 |
| emily | (I think maybe networkd might inherit config from stage 2 or something weird like that, I forget) | 17:47:52 |
