| 29 Jun 2025 |
 emily | the average user has fairly dynamic networking configuration anyway | 04:43:56 |
| emily | WiFi etc. | 04:43:59 |
 hexa | we ship with mutableUsers = false as well 😛 | 04:44:00 |
| emily | well that's unforgivable | 04:44:08 |
| emily | also the source of more new user confusion than benefit probably :p | 04:44:23 |
| hexa | we should just stateVersion that tbh 😛 | 04:44:29 |
| emily | just today I had to tell someone why they couldn't change their password in their config | 04:44:35 |
| hexa | yes, abuse of stateVersion, but. | 04:44:36 |
 ElvishJerricco | so, do we just add networking.networkmanager.enable = true; to configuration.nix in nixos-generate-config? | 04:44:56 |
 uep | usedhcp is a fine default for a generic system with wired interfaces, regardless of which dhcp mechanism delivers the implementation. On a server, maybe you want static on at least some interfaces, so sure, you add config for those.
The issue is wireless. If a wireless interface appears, adding a dhcp client gets in the way of whatever mechanism the user is going to use to set ssid and keys, and so it has to get out of the way | 04:45:16 |
| emily | In reply to @elvishjerricco:matrix.org
so, do we just add networking.networkmanager.enable = true; to configuration.nix in nixos-generate-config? this is still a footgun if you use scripted networking options though | 04:45:54 |
| hexa | we are talking about new installs here | 04:46:10 |
| emily | I know | 04:46:25 |
| emily | I mean we still have to kill scripted networking | 04:46:34 |
| hexa | users who are not on scripted stuff to begin with don't need to migrate 🙂 | 04:46:48 |
| hexa | so this is a good change | 04:46:57 |
| emily | yes but the options are right there for them to set and when we flip useNetworkd it'll get turned on for new users too | 04:47:15 |
| emily | is my point | 04:47:18 |
| ElvishJerricco | Yea I'm pretty sure the scripted networking stuff is basically a noop if there is no networking.* configuration | 04:47:21 |
| emily | does useNetworkd avoid enabling networkd in that case? | 04:47:48 |
| ElvishJerricco | I mean this is already a threat with graphical installs since they enable networkmanager by default | 04:48:07 |
| emily | I think every ten years we should get a flag day jubilee where we can break anything we want arbitrarily and existing users just kind of have to figure it out | 04:48:08 |
| ElvishJerricco | and it's not been a problem | 04:48:11 |
| hexa | we ship with networkd either way | 04:48:11 |
| hexa | and it will have no config files, so it will not match anything | 04:48:19 |
| emily | In reply to @hexa:lossy.network
we ship with networkd either way not enabled | 04:48:21 |
| emily | but fair | 04:48:26 |
| hexa | yeah, not sure about enable toggle, but it will be a noop | 04:48:40 |
| emily | In reply to @uep:matrix.org
usedhcp is a fine default for a generic system with wired interfaces, regardless of which dhcp mechanism delivers the implementation. On a server, maybe you want static on at least some interfaces, so sure, you add config for those.
The issue is wireless. If a wireless interface appears, adding a dhcp client gets in the way of whatever mechanism the user is going to use to set ssid and keys, and so it has to get out of the way I thought our useDHCP default for networkd was wired only | 04:50:23 |
| ElvishJerricco | nope | 04:50:29 |
