Ok, I only have 15 years experience in administering GNU/Linux boxes, so obviously I'm a n00b, but how the fsck does one add a nameserver on a systemd-infested system in a way that it's going to be used regardless of the DNS servers gotten from DHCP, for *every and any* connection?

Without editing every. single. network. connection on my system, that is.

I tried adding it to /etc/resolvconf/resolv.conf.d/head but systemd-resolve happily ignores it (dig digs it though).

#FsckSystemd #Linux

I mean, it used to be "add to resolv.conf, you're done". Then it used to be "add to resolvconf config file head, you're done". Now it's "nobody really knows, users usually don't need that *shrug*".

This fscking thing really starts to feel like Windows.

#FsckSystemd #Linux

SYNOPSIS
/etc/systemd/resolved.conf

/etc/systemd/resolved.conf.d/*.conf

/run/systemd/resolved.conf.d/*.conf

/usr/lib/systemd/resolved.conf.d/*.conf

Because not having 4 different locations to configure one thing is so 1990s.

#FsckSystemd #Linux

@rysiek the Great Unlearning experiment that is systemd is probably mostly invented by people who weren’t here for the 90s. They’re not troubled with the annoying burden of memory or the wisdom of lessons learned.

It would not be tolerated in any other industry.

“Why do our planes even *need* wings? Let’s remove those, but only once we’re in the air”

@mig5 @rysiek I wasn't there for the 90s having fell out of love with computers when I stopped working on Acorn and started working with Windows. I haven't yet figured the systemd debates. I can only agree on principle on the basis that many of most of the principled people I observer in tech put systemd in the same category as ie. Windows. Still, "wouldn't be tolerated in any other industry?" That I'm not sure. Politics, journalism, law, economics: The Great Unlearning is, for me, upstream.

@krozruch @mig5 fair enough, but in most other industries it takes a generation or more.

In IT, it's 2-3 years and we're busy reinventing a perfectly decent wheel.

@rysiek @mig5 Yes. I don't know what the f I'm talking about as far as systemd goes, but follow your (and others') observations on the linux ecosystem etc., github, etc etc. as somebody who wants to know more and learn from others. I can see what the change from free software to open source has done (having rediscovered computing with the later). The problem is that one feeds into the other. When those broken systems feedback into IT, we get a hockey stick curve of accelerated unfreedom.

Follow

@rysiek Ie. I'm not arguing that systemd (and understanding systemd, which I don't) is not important.. The opposite, I think. I run systemd on all of the linux systems I now run. I understand no others so far. The Great Unlearning in Linux has happened because Microsoft-style methods have been successful. When the year of the Linux desktop comes (!), it will look like Microsoft or Apple & track the shit out of us. Breaking journalism & breaking linux is a win for the same people.

· · Web · 2 · 3 · 0

@rysiek In all instances all that is needed is to not know what a wheel looks like or to hate it on sight. IT in the way it has developed in the last quarter of a century or so seems to make it possible to convince 52% of the people consistently that round wheels are the work of the devil. So yes, I imagine you're all right that systemd is a bag of boke and all. That needs to be tackled. All I'm saying is it's a symptom of a civilisational antipattern iterating like a fractal everywhere we look.

Sign in to participate in the conversation
Mastodon

This Mastodon instance is dedicated to all people interested in a united Europe, a post-national and truly democratic Europe. But even if you are not so interested in European politics you are welcome.

Diese Mastodon-Instanz ist für alle, die interessiert sind an einem vereinten Europa, einem post-nationalen und wirklich demokratischen Europa.

Impressum dieser Instanz