| 29 Jun 2025 |
 emily | it's fine for desktop users at least | 04:58:06 |
 hexa | that's why I proposed shipping with examples for a declarative networkd config, that matches an explicit interface and shows a dhcp/ra and static example | 04:58:07 |
| emily | I don't know if it's the right onramp for servers | 04:58:16 |
| emily | In reply to @hexa:lossy.network
that's why I proposed shipping with examples for a declarative networkd config, that matches an explicit interface and shows a dhcp/ra and static example as in NM enabled but commented out networkd example? | 04:58:30 |
 uep | sure, even if it's commented out or wahtever | 04:58:33 |
| hexa | we don't want it to be networking.interfaces | 04:58:33 |
| emily | I worry about bitrot with that kind of thing but seems reasonable enough | 04:58:47 |
| emily | I don't think it solves @elvishjerricco:matrix.org's scariness complaint though | 04:59:03 |
| emily | or we could just ship it as the actual config | 04:59:11 |
 ElvishJerricco | I'd keep that stuff in the manual, not in a generated comment | 04:59:23 |
| hexa | we need to confront people more with network config, not less 🙂 | 04:59:33 |
| ElvishJerricco | I don't really agree | 04:59:41 |
| ElvishJerricco | most people setting up nixos don't want to think twice about networking | 04:59:50 |
| hexa | its something you want to have when you don't have network though | 04:59:52 |
| hexa | and making changes to something you already have in your config is easier than copying it from the manual, badly | 05:00:18 |
| ElvishJerricco | I think explaining to the user how to do something more interesting is very much the job of the manual | 05:00:55 |
| hexa | I'd say the same about initrd related options, but here we are | 05:00:59 |
| ElvishJerricco | Hm? | 05:01:19 |
| uep | there's another aspect too, for installers (including generate-config).
A bit like it discovers and embeds the partition uuid's for filesystem mountpoints, perhaps it could capture some of what is configured for networking during install. | 05:01:22 |
| uep | i kind of assume to gooey installer does that already, but i've never used it | 05:01:46 |
| ElvishJerricco | I think file systems are considered a more permanent feature than a networking configuration | 05:03:10 |
| ElvishJerricco | which is why NM is the goto for most distros | 05:03:17 |
| ElvishJerricco | because it handles it dynamically | 05:03:22 |
| uep | agree | 05:03:22 |
| hexa | we already agreed on nm 😄 | 05:03:42 |
| hexa | lalala | 05:03:45 |
| ElvishJerricco | well my point is that I think that's good reason not to "capture some of what is configured for networking during install" | 05:04:09 |
| hexa | yeah, we can consider declarative network configuration a fun adventure people can embark on | 05:04:48 |
| hexa | * yeah, we can consider declarative network configuration an optional fun adventure people can embark on | 05:05:05 |
| ElvishJerricco | On the subject of nixos-generate-config, we should probably make it generate configs that are nixfmt compliant :P | 05:05:57 |
