| 28 Jul 2025 |
 @marcel:envs.net | In reply to @emilazy:matrix.org
I think it's easy to inherit if you want and annoying to disable automatic inheritance if you don't Just the default, the pint you start configuring initrd stuff it is replaced and not merged | 17:50:40 |
| @marcel:envs.net | If you want to merge it, you have to do it yourself as the consumer | 17:51:01 |
 emily | I think that's not ideal (because if you import a module that only intends to extend the initrd network config, it unexpectedly blows away the inherited config) | 17:51:15 |
| @marcel:envs.net | Ok, I'll leave the default initrd config:) | 17:51:50 |
| emily | I think it should match boot.initrd.system.network by being separate (and in a separate hierarchy) and you can always boot.initrd.networking.ifstate = config.networking.ifstate; or such | 17:51:53 |
| emily | (admittedly the boot.initrd.* hierarchy is a bit of a mess currently) | 17:52:06 |
| @marcel:envs.net | In reply to @emilazy:matrix.org
I would personally probably go for services.ifstate.* IMO, it's comparable to services.network-manager.* in that you have a systemd service managing the config, but I'm ambivalent you are still with services.ifstate? in your last message you used networking.ifstate? | 19:16:08 |
| emily | I have no consistent opinion 😅 NM is under networking.* right? | 19:16:59 |
| emily | I'd match NM | 19:17:01 |
| @marcel:envs.net | yeah | 19:17:21 |
| @marcel:envs.net | allrigh | 19:17:23 |
