| 28 Jul 2025 |
 emily | (they even have different notions of machine-id by default) | 17:49:42 |
 Marcel | 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 | 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 | 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 | 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 | yeah | 19:17:21 |
| Marcel | allrigh | 19:17:23 |
| Marcel | shoult the initrd options then be unser boot.initrd.network.ifstate? | 19:17:43 |
 Sandro 🐧 | that's what we are doing in the hackspace. Marcel knows that part, too. | 19:19:42 |
| emily | I'm not totally sure as it is possible (but not guaranteed) that we will deprecate that hierarchy. I'd say boot.initrd.network.ifstate or boot.initrd.ifstate are both fine | 19:19:46 |
| emily | ideally boot.initrd would mirror the top level hierarchy | 19:20:04 |
| emily | but alas :) | 19:20:07 |
| Marcel | so boot.initrd.networking? ;D | 19:20:22 |
| emily | yeah, but it's probably too confusing to do that | 19:20:37 |
| Marcel | yeah unserstand that | 19:20:42 |
| Marcel | i'll use networking | 19:20:49 |
| Marcel | * | 19:20:54 |
| Marcel | I've build an assertion like this:
IfState and networking.useDHCP cannot be used at the same time, as both configure the network. Please look into IfState hooks to integrate DHCP: https://codeberg.org/liske/ifstate/issues/111
The problem is that useDHCP is per default set to true. That means that every user first using ifstate gets this error, is this bad? Should ifstate set useDHCP to false?
| 20:25:45 |
 hexa | please bring ifstate upstream | 20:27:00 |
| hexa | it's one more thing we can point people to, to escape scripted networking | 20:27:10 |
 ElvishJerricco | hexa (clat on linux when): (that is what they're working on :P) | 20:27:23 |
| hexa | and e.g. if they require network namespaces | 20:27:24 |
| Marcel | In reply to @hexa:lossy.network
please bring ifstate upstream I am currenlty in the process ;D | 20:27:25 |
| hexa | was only aware of the flake 🙂 | 20:27:33 |
| hexa | backlog is hard | 20:27:40 |
