| 29 Jun 2025 |
 hexa | * we agreed on enabling NM earlier | 04:56:00 |
| hexa | but if you deploy a server having an example config for static/dynamic interface configuration with network in the example configuration.nix will be helpful | 04:56:28 |
 emily | In reply to @hexa:lossy.network
kindly, let's not scuff up that module, thanks if the constraints are "no scary networkd details in default configs" and "plugging in an Ethernet cable out of the box works" and "networking.useDHCP is busted actually"... | 04:56:36 |
| emily | then it's either NM or we add an option to achieve the basic sane config for networkd | 04:56:52 |
| hexa | we agreed on NM 😄 | 04:56:59 |
| hexa | can we not walk that back? | 04:57:04 |
| hexa | * can we not walk that back w/o a good reason? | 04:57:10 |
| emily | In reply to @emilazy:matrix.org
because I feel like "oh yeah to declaratively configure that you want to turn off NM that the generated config has and switch to this" is maybe not actually better well, ^ | 04:57:33 |
| emily | it was more a flippant reaction to the no networkd config constraint | 04:57:52 |
| 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 |
