3 ms·

> It took me forever to realise DHCP was overwriting resolv.conf, Always expected and well documented. > but that some sneaky bullshit was also overwriting pa

> It took me forever to realise DHCP was overwriting resolv.conf, Always expected and well documented. > but that some sneaky bullshit was also overwriting part of unbound’s config using DHCP config data too. Absolutely unacceptable and should never happen. I wish the author had actually shared details. That's a bug, and it should be reported, publicized and fixed. > This is your weekly reminder that cosplaying as a sysadmin can waste your Friday evening and Saturday morning, and to add your own time into the cost/benefit calculations of running servers at home or on a cloud service. This illustrates the value of OSes and OS projects that don't change gratuitously, that don't change to differentiate themselves because of their need to appeal to businesses, that don't make decisions about things based solely on usage and profits. This is why I use NetBSD. The BSDs are clean and quite consistent. If someone wants to pooh-pooh systems administration, they should at least direct their ire properly. Nobody's forcing you to use messy, inconsistent Linux distros :)

pxc 4y ago
> > but that some sneaky bullshit was also overwriting part of unbound’s config using DHCP config data too. > Absolutely unacceptable and should never happen. I wish the author had actually shared details. That's a bug, and it should be reported, publicized and fixed. Looks like they're talking about the feature of openresolv that lets you configure it to write to an extra config file for unbound which you can configure unbound to source/include from its main config file. The distro default configuration probably just included an include line with the path usually used by resolvconf for this file. https://roy.marples.name/projects/openresolv/configuration/ https://roy.marples.name/projects/openresolv/configuration/ > This is why I use NetBSD. The BSDs are clean and quite consistent. NetBSD's implementation of resolvconf is likewise openresolv; see the credits and link at the bottom of the resolvconf manpage from NetBSD: https://man.netbsd.org/resolvconf.8 https://man.netbsd.org/resolvconf.8
trynewideas 4y ago
> and someone with zero personal skills wades in with “that’s a dumb way, why aren’t you reading the docs and doing it correctly like this? You’ll break things”.

pxc 4y ago

> > but that some sneaky bullshit was also overwriting part of unbound’s config using DHCP config data too. > Absolutely unacceptable and should never happen. I wish the author had actually shared details. That's a bug, and it should be reported, publicized and fixed. Looks like they're talking about the feature of openresolv that lets you configure it to write to an extra config file for unbound which you can configure unbound to source/include from its main config file. The distro default configuration probably just included an include line with the path usually used by resolvconf for this file. https://roy.marples.name/projects/openresolv/configuration/ https://roy.marples.name/projects/openresolv/configuration/ > This is why I use NetBSD. The BSDs are clean and quite consistent. NetBSD's implementation of resolvconf is likewise openresolv; see the credits and link at the bottom of the resolvconf manpage from NetBSD: https://man.netbsd.org/resolvconf.8 https://man.netbsd.org/resolvconf.8

trynewideas 4y ago

> and someone with zero personal skills wades in with “that’s a dumb way, why aren’t you reading the docs and doing it correctly like this? You’ll break things”.