Where "basic" follows a highly nuanced alternate definition, where if you step out of line without realising it, you lose 3 days debugging a complex undocumented interaction between 4 enterprise crapware daemons only to find out the answer is "you're wrong and won't fix" buried in a 6 year old bug report, when all you did was plug in a USB mouse or try to set the default audio output device, or something else.
Total and utter propaganda, it's underdeveloped steaming garbage
The reason for seeing overcomplexity in systemd components is usually that you never considered the use cases of other people or proper server management - mostly because in the days of olde, everyone cobbled together their shell script Jenga towers in seclusion.
> The reason for seeing overcomplexity in systemd components is usually that you never considered the use cases of other people or proper server management
What use cases of "proper server management" does fucking with my resolv.conf(5) solve?
If I have a laptop I can perhaps see updating values per DHCP or IPv6 RAs, but once I set up a server up why the hell is it a link to /run? (I once had to use chattr +i because of brain dead "cleverness".)
In over thirty years of running Unix-y systems I never needed my resolv.conf "managed", so I have no idea why Ubuntu (for one) defaults to fiddling with it.
> What use cases of "proper server management" does fucking with my resolv.conf(5) solve?
For one, it avoids telling all processes and their mothers the IP of the DNS resolvers they should query, but hands them 127.53 instead. If you then update your resolvers using systemd-resolved, for example because the network changes to a failover line, or because puppet pushes an updated catalog, or you want split DNS for a VPN (like, send *.corp.local to the internal DNS server or something), that is all pretty easy. There are more use cases on servers, but of course you most obviously benefit from this on laptops that roam between WIFIs with different upstream DNS server config.
> For one, it avoids telling all processes and their mothers the IP of the DNS resolvers they should query, but hands them 127.53 instead.
What "all process" are you referring to? What kind of software on Unix-y systems is not using gethostbyname(3) (or similiar)?
(And the context of this sub-thread is "server management", which I'm not sure how often has VPN running on it and doing things like split (horizon) DNS.)
badatnames · · focus · HN ↗
Total and utter propaganda, it's underdeveloped steaming garbage
ux266478 · · focus · HN ↗
9dev · · focus · HN ↗
throw0101a · · focus · HN ↗
What use cases of "proper server management" does fucking with my resolv.conf(5) solve?
If I have a laptop I can perhaps see updating values per DHCP or IPv6 RAs, but once I set up a server up why the hell is it a link to /run? (I once had to use chattr +i because of brain dead "cleverness".)
In over thirty years of running Unix-y systems I never needed my resolv.conf "managed", so I have no idea why Ubuntu (for one) defaults to fiddling with it.
9dev · · focus · HN ↗
For one, it avoids telling all processes and their mothers the IP of the DNS resolvers they should query, but hands them 127.53 instead. If you then update your resolvers using systemd-resolved, for example because the network changes to a failover line, or because puppet pushes an updated catalog, or you want split DNS for a VPN (like, send *.corp.local to the internal DNS server or something), that is all pretty easy. There are more use cases on servers, but of course you most obviously benefit from this on laptops that roam between WIFIs with different upstream DNS server config.
throw0101a · · focus · HN ↗
What "all process" are you referring to? What kind of software on Unix-y systems is not using gethostbyname(3) (or similiar)?
(And the context of this sub-thread is "server management", which I'm not sure how often has VPN running on it and doing things like split (horizon) DNS.)