| 28 Jul 2025 |
 emily | (but I don't think we'll want to upstream scripted initrd support, since it's going to explicitly be on the deprecation/warning path very very soon) | 17:48:47 |
| emily | thankfully fixed by deprecating networking.interfaces | 17:49:03 |
 @marcel:envs.net | That's at least what I am currently doing. If you don't specify a initrd config and ifstatenis activated on initrd, it inherits the normal config | 17:49:10 |
| emily | I think it's easy to inherit if you want and annoying to disable automatic inheritance if you don't | 17:49:17 |
| emily | so IMO separate configs and letting people manually do explicit inheritance is the way to go | 17:49:27 |
| emily | initrd isn't the same as the booted machine | 17:49:37 |
| emily | (they even have different notions of machine-id by default) | 17:49:42 |
| @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 |
