| 28 Jul 2025 |
 @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 |
| @marcel:envs.net | 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:envs.net | so boot.initrd.networking? ;D | 19:20:22 |
| emily | yeah, but it's probably too confusing to do that | 19:20:37 |
| @marcel:envs.net | yeah unserstand that | 19:20:42 |
