A Word about Systemd

Re:A Word about Systemd by theamk on Tuesday September 17, 2024 @11:09PM (#41575374)

For resolve.conf, I think it is fundamentally bad design that is hard to get right. Before systemd, I've spent plenty of time trying to get networkmanager and resolvconf to play together. And then there was those dhcp scripts which would edit the files directly.

Also, what do you mean my "standardizing dnsmasq behaviour?" From my recollection of using it (and from manpage[0]), it's pretty basic. You (1) manually edit /etc/resolve.conf to point to localhost dnsmasq instance (2) use app-specific ways to configure nameservers, in dnsmasq's case it's an ad-hoc list of secondary resolv.conf files specified on command line, with no defaults. I don't think this is worth standardizing, as this scheme cannot even represent network interface -> dns entry associations.

https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html

[ Parent | on HN ]

Re:A Word about Systemd by viraptor on Tuesday September 17, 2024 @11:45PM (#41575568)

I didn't say standardizing dnsmasq behaviour. I said multi home/interface which was one of the big reasons to write resolved. They could've added the missing feature to the 2 most popular daemons and use one of them as a default, but instead went with a whole new system written from scratch.

[ Parent | on HN ]