> Until complicated Linux stuff gets in the way. I mean all that stuff that tries to manage network connections and alter the sacred resolv.conf file. At what p

> Until complicated Linux stuff gets in the way. I mean all that stuff that tries to manage network connections and alter the sacred resolv.conf file. At what point did people decide one Linux package should poke itself into the config of another package in a way that seemingly nobody knows about when you’re Googling? > Well, until you find some random post online where some poor person is being berated for daring to suggest a slightly hacky way to fix things, 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”. I guess that one reason might be that when I installed Slackware from floppies on a 486 there wasn’t that much stuff in that Linux system. Few things worked, but the way I remember it, the error messages were immediate and clear. Nowadays things break suddenly without even error messages. Some times I do get some hint in one of the log files, often I get no clue. I’ve developed a conspiracy theory that people don’t want to be the ones that report an error because that makes their software look bad when the cause might be someone else’s code, so they just catch an exception or ignore an error code and go on, until so many things have failed that there are no workarounds left.