| 30 Jun 2025 |
 hexa | oh, with the nm daemon | 07:47:10 |
| hexa | I thought you meant polkit itself | 07:47:33 |
| hexa | anyway, only rules are properly inspectable from the filesystem sadly | 07:48:10 |
 emily | pipewire also uses polkit I think, really basically everything in the fd.o stack as well as systemd does | 07:48:28 |
| emily | but it may not be essential for your use case | 07:48:34 |
| hexa | given that most of my config is not done interactively and if in doubt i can elevate, yeah | 07:49:39 |
 clerie | I found out that with scripted networking some interfaces aren't set up when systemd-resolved is enabled. I would appreciate feedback to my proposal of fixing this. Especially considering additional side effects that could arise: https://github.com/NixOS/nixpkgs/pull/421010 | 14:46:00 |
| emily | we might not want to do stuff to scripted networking that might be backwards-incompatible (though I don't know if these service ordering changes would be, but they can be subtle) since we were just working on finally starting to deprecate it | 14:47:49 |
| clerie | To my understanding the change should not break anything, but I'm not sure if there is anything outside this file that might be influenced by this.
(The irony is that I encountered this issue while being in the process of migrating my stuff the networkd)
| 14:55:04 |
| hexa | Yeah, the reason we want to get rid of scripted networking that it is hard to reason about it. 😬 | 15:00:37 |
 Molly Miller | is there any kind of concrete plan for the deprecation of scripted networking, or is that currently work in progress? | 15:02:03 |
| emily | we just started the process of not making it the default option any more | 15:02:41 |
| emily | it will probably be timed roughly around the systemd stage 1 transition | 15:02:57 |
| emily | expect 25.11 to ship with different defaults and deprecations/removals around 26.05, 26.11, say | 15:03:14 |
| emily | though we were meant to flip some of those defaults releases ago already :) | 15:03:25 |
| Molly Miller | okay | 15:03:40 |
| Molly Miller | with my work hat on: we rely really heavily on scripted networking internally, though i've long been expecting that it'll eventually be removed | 15:04:36 |
| Molly Miller | one of my colleagues has suggested that we (flying circus) might be able to take over maintainership of the scripted networking support, though i have the impression that having more than one network configuration subsystem in the tree is an ongoing maintenance headache | 15:05:55 |
| clerie | You don't want this, really /o\ | 15:06:46 |
| emily | I don't think there's the appetite for it – if anything it seems like the path is likely to be deprecating the networking.* interfaces entirely | 15:07:11 |
| emily | in favour of NM or direct use of systemd.network.* | 15:07:18 |
| emily | rather than maintaining our own abstraction layers | 15:07:24 |
| emily | OTOH I think that means there's nothing preventing maintenance of an identical not-networking.* interface out of tree? | 15:07:42 |
| Molly Miller | true, that's an option to bear in mind | 15:08:05 |
| emily | I think the focus right now is more on getting new users off it and explicitly signalling deprecation than immediate removal though | 15:08:19 |
| emily | but given that useNetworkd is a seamless switch for probably >95% of existing users of the interface I'm also not sure there'll be much desire to keep the scripted code around for too long after flipping the default backend for that stuff | 15:09:04 |
 K900 | Honestly | 15:09:51 |
| Molly Miller | my colleagues are a little skeptical of networkd given that in the past the official answer from upstream regarding online reconfiguration has been "just reboot", which is a bit impractical when you have several racks full of servers which each take several minutes to boot, though i'm aware that networkd has grown much better online reconfiguration functionality in recent years | 15:09:52 |
| K900 | I don't even know the size of your org | 15:09:56 |
| emily | (Matrix ID is a hint :p) | 15:10:08 |
