News for hackers. Stuff that matters.
Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @09:44AM (#23712991)
> I will block discussions here now, since I don't think we need the input from the script kiddie peanut gallery here.

How not to interact with your community 101.

Defaults matter, because even if they are changeable via a build-time flag, most of the time they won't (how many people knew this was a default before now?)

Re:Systemd: Don’t fallback to Google NTP and DNS by theevilsharpie on Thursday July 02, 2020 @10:24AM (#23713407)
> How _not_ to interact with your community 101.

On the contrary, I think he handled it perfectly.

I've become exhausted with most discussions on social media, because conversations frequently get hijacked by loud people with strong opinions that don't express them in good faith. Without strict moderation, it can become impossible to have a rational discussion on certain topics. For example, pretty much anything on HN involving Google devolves into worthless noise.

In the case discussed in the OP, Poettering clearly has no intention of changing the default configuration (at least based on the reasons given in the issue), and has provided a way of modifying the configuration for those that care enough to change it. There's no value in further debate, and closing the issue to further discussion keeps Poettering and other contributors from getting distracted/burned out by unproductive conversation.

If people don't like it, they're free to fork Systemd or start up their own competing software project, and then they can handle community interaction for their own project in whatever way suits them.

Frankly, I wish more discussion were handled this efficiently.

Re:Systemd: Don’t fallback to Google NTP and DNS by KaiserPro on Thursday July 02, 2020 @10:30AM (#23713476)
Its not really efficiently.

Something like: "we've discussed this a number of times, see #12345" closing now

would have closed the ticket and not made the front page.

By being a top draw dick about it (when the originator was at least being earnest) the debate rolls on.

He had given a full answer, he could have left it there, but chose not to.

its this kind of "rock star" and cheerleaders that give IT a bad smell.

Re:Systemd: Don’t fallback to Google NTP and DNS by bad_user on Thursday July 02, 2020 @10:35AM (#23713576)
Are you talking about the comment that closed the ticket [1]? Are we not seeing the same thing, because that's not a "top draw dick" I'm seeing.

He was perfectly reasonable. And I don't know if you've ever managed any popular open source projects, however it's best to close tickets fast instead of letting them linger on, especially when you have over 1000 opened issues and especially if, as a maintainer, you know that you won't change your mind about that issue.

Then he got accused of being funded by Google. He actually showed restraint.

[1] https://github.com/systemd/systemd/issues/12499#issuecomment...

Re:Systemd: Don’t fallback to Google NTP and DNS by wtallis on Thursday July 02, 2020 @10:45AM (#23713730)
> Are we not seeing the same thing, because that's not a "top draw dick" I'm seeing.

> He was perfectly reasonable.

The original complaint had the form "this default should be changed for reason X". Poettering's response was "our defaults are Y, and you can change them". That's not perfectly reasonable. It's a non sequitur. Poettering's response passively-aggressively ignores what the original complaint was all about, instead of simply issuing a direct rejection.

Re:Systemd: Don’t fallback to Google NTP and DNS by bad_user on Thursday July 02, 2020 @11:06AM (#23714010)
It isn't a non-sequitur, he offered a solution for users that would like different settings, while choosing not to engage in pointless arguments.

While professional courtesy is recommended, maintainers don't really owe an explanation for their work when provided for free. Put that man on a payroll and you might deserve a more detailed answer.

Re:Systemd: Don’t fallback to Google NTP and DNS by wtallis on Thursday July 02, 2020 @11:17AM (#23714185)
It is absolutely a non-sequitur to tell someone what the defaults are when they are complaining that they do not like what the defaults are. "Choosing not to engage in pointless arguments" would be not responding at all, rather than responding in a manner that is implicitly insulting. Poettering phrased his response as if he was answering a different issue than the one he was actually responding to. Deliberately misinterpreting someone's question instead of directly saying he didn't want to get into that matter is poor behavior.
Re:Systemd: Don’t fallback to Google NTP and DNS by growse on Thursday July 02, 2020 @04:23PM (#23717603)
If they don't like the defaults, they could just fork the project.
Re:Systemd: Don’t fallback to Google NTP and DNS by KaiserPro on Thursday July 02, 2020 @11:17AM (#23714186)
Its more basic than that. He chose not to give a _detailed_ answer, and diverted from the original point. Thats perfectly fine

then to go off on one here: https://github.com/systemd/systemd/issues/12499#issuecomment... its just being a dick. Its not even entertaining.

Re:Systemd: Don’t fallback to Google NTP and DNS by KaiserPro on Thursday July 02, 2020 @11:15AM (#23714148)
yes, and he would have been able to close it again, instead he wrote this:

https://github.com/systemd/systemd/issues/12499#issuecomment...

Re:Systemd: Don’t fallback to Google NTP and DNS by bad_user on Thursday July 02, 2020 @11:22AM (#23714260)
After being insulted with that comment on Google finding?

As I said, he showed restraint.

Re:Systemd: Don’t fallback to Google NTP and DNS by laumars on Thursday July 02, 2020 @11:54AM (#23714647)
It’s sad times when “showing restraint” means insulting an entire community because one person asked a stupid question first.
Re:Systemd: Don’t fallback to Google NTP and DNS by cycloptic on Thursday July 02, 2020 @12:17PM (#23714871)
He probably should have worded it better but the comment does not refer to the entire community. Unfortunately there absolutely is a collection of anti-systemd trolls within the community that have been egging him on for quite some time now and will gladly dog-pile on these github issues with insults and conspiracy theories. I honestly did not even know who he was before I saw lots of this type of toxic and hateful post being directed at him on reddit.
Re:Systemd: Don’t fallback to Google NTP and DNS by bad_user on Thursday July 02, 2020 @10:30AM (#23713483)
It is regrettable that this comment got down-voted (at the moment of writing this).

I very much agree — and I would add that there's a strong entitlement complex among loud non-contributors.

If you don't contribute anything but opinions, then be respectful, respect the author's choices, or start your own fork, which is what open source is about.

Re:Systemd: Don’t fallback to Google NTP and DNS by ghostpepper on Thursday July 02, 2020 @12:24PM (#23714946)
Name calling is never productive, and the maintainer of a project sets the tone for the interaction of the entire community.
Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @11:04AM (#23713984)
Handled perfectly would be "No, reference bug #X, closing" and closing/locking the thread. Question gets answered, nobody gets insulted.

Denigrating your community as the "script kiddie peanut gallery" is, at best going to piss off your community and at worse make them less likely to work with you in the future.

Re:Systemd: Don’t fallback to Google NTP and DNS by esgwpl on Thursday July 02, 2020 @11:13AM (#23714094)
To be fair to Poettering, someone accused the systemd devs of being on Google's payroll, if I were him I'd be annoyed as well.
Re:Systemd: Don’t fallback to Google NTP and DNS by wtallis on Thursday July 02, 2020 @11:20AM (#23714220)
> if I were him I'd be annoyed as well.

Especially when he had to answer in the affirmative, that there is indeed a conflict of interest, but it's a really tiny one that hardly anyone would be bothered by.

Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @01:24PM (#23715640)
Google has a well known, and well documented history of donating to open source projects to get their own products added as defaults. Combine with a for-profit company (RedHat) who does not disclose all of their financials (and that’s their prerogative), and it’s a perfectly reasonable question to ask.
Re:Systemd: Don’t fallback to Google NTP and DNS by laumars on Thursday July 02, 2020 @12:00PM (#23714711)
The original question was stupid. We all get that. We’ve all suffered that on occasions at work. But that doesn’t justify his grossly unprofessional response.
Re:Systemd: Don’t fallback to Google NTP and DNS by wtallis on Thursday July 02, 2020 @10:31AM (#23713504)
> In the case discussed in the OP, Poettering clearly has no intention of changing the default configuration (at least based on the reasons given in the issue),

Poettering never even acknowledged that there are privacy concerns. Simply saying "if you don't like the defaults, change it yourself" is in no way equivalent to saying "I don't care about or share your privacy concerns, but here's how to override the defaults if they bother you".

Re:Systemd: Don’t fallback to Google NTP and DNS by packetlost on Thursday July 02, 2020 @09:58AM (#23713138)
Defaults matter, but he's right to say each distro should be the ones setting the default. Most people aren't compiling systemd themselves, they're using the one compiled by their distro maintainer(s). I don't think this is anything to worry about and he's right to shut out pointless conversation from people who misunderstand the actual situation. Accusations of being paid by Google (or any other entity) is ludicrous and can easily be interpreted as insulting too.
Re:Systemd: Don’t fallback to Google NTP and DNS by vonmoltke on Thursday July 02, 2020 @10:07AM (#23713225)
> Defaults matter, but he's right to say each distro should be the ones setting the default. Most people aren't compiling systemd themselves, they're using the one compiled by their distro maintainer(s).

In that case, the final comment in the discussion is correct: systemd itself should not have a default, and should require the distro maintainer to explicitly set these values to whatever default they want to use.

Re:Systemd: Don’t fallback to Google NTP and DNS by djsumdog on Thursday July 02, 2020 @10:50AM (#23713818)
I agree. There shouldn't be any hardcoded DNS/NTP fallbacks. I don't use systemd on any of my personal systems or my dedicated server (Gentoo/Void), so I don't have to worry about this. But on my Ubuntu VMs, I guess there's a fallback DNS/NTP in my startup process I never knew about.

I agree. The default should be set (and required; without defaults) by the distro maintainers downstream. Just leave them out here.

Re:Systemd: Don’t fallback to Google NTP and DNS by packetlost on Thursday July 02, 2020 @10:19AM (#23713345)
I'm inclined to agree, though without being familiar with systemd's codebase and infrastructure, there may be technical reasons why that hasn't been done
Re:Systemd: Don’t fallback to Google NTP and DNS by mrighele on Thursday July 02, 2020 @10:19AM (#23713338)
If the distro is supposed set a default, don't provide one.
Re:Systemd: Don’t fallback to Google NTP and DNS by Kaze404 on Thursday July 02, 2020 @10:08AM (#23713230)
There were no accusations. Someone asked a fair question. The maintainer clearly overreacted.
Re:Systemd: Don’t fallback to Google NTP and DNS by packetlost on Thursday July 02, 2020 @10:17AM (#23713322)
No, that question was asked in bad faith. By asking the question, you implying that there's a conflict of interest or some monetary motivation for the decision. If they truly wanted to ask a neutral question, something like "Given the for-profit nature and potential privacy concerns, why is Google's DNS the default instead of some other non-profit entity?"
Re:Systemd: Don’t fallback to Google NTP and DNS by wtallis on Thursday July 02, 2020 @10:24AM (#23713403)
> No, that question was asked in bad faith. By asking the question, you implying that there's a conflict of interest or some monetary motivation for the decision.

It's not bad faith to ask that question, when raising the issue previously got a complete non-answer that failed to acknowledge that there was a reason behind wanting different defaults. "Why didn't you answer the question the first time?" is fair game; Poettering provoked that response.

Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @11:00AM (#23713933)
Been poorly worded doesn't make the question bad. Your example makes the exact same assumptions.

And they're fair assumptions - Google is well known for giving funding to open source projects to get their products set as defaults.

Re:Systemd: Don’t fallback to Google NTP and DNS by packetlost on Thursday July 02, 2020 @11:20AM (#23714216)
> Your example makes the exact same assumptions

My example does not make the assertion that Google donated/bribed the systemd project, so no, it does not make the same assumptions. It intentionally leaves any implied motivations open ended.

> And they're fair assumptions - Google is well known for giving funding to open source projects to get their products set as defaults.

The only case I'm aware of is Firefox, which had a contract with Mozilla to have the Google search engine be the default. I'm curious to hear about more though.

The privacy concerns with Google DNS seem to be partially unfounded too [1]. Granted, that is coming from Google themselves, but privacy policies are legally binding. For the record, I don't think there should be a default at all, but I have no problems with how Poettering handled this.

[1]: https://developers.google.com/speed/public-dns/faq#privacy

Re:Systemd: Don’t fallback to Google NTP and DNS by KaiserPro on Thursday July 02, 2020 @10:26AM (#23713420)
The defaults have kicked me in the genitals a number of times

Stuff magically failing, with no obvious reason why. The I realise that someone has cocked up the DNS config, its been silently rejected and is now defaulting back to the default DNS config.

I want it to fail, and fail loudly, not limp on and cause odd errors.

Re:Systemd: Don’t fallback to Google NTP and DNS by Semaphor on Thursday July 02, 2020 @10:18AM (#23713337)
> With the above response, might I ask the developers a question: has this project received any donations from Google?

That sounds very accusatory to me. It’s just worded as a question.

Re:Systemd: Don’t fallback to Google NTP and DNS by edoceo on Thursday July 02, 2020 @10:33AM (#23713543)
Don't sound accusatory to me and only requires a one word response: No

Just mentioning Google or money does not an accusation make.

Re:Systemd: Don’t fallback to Google NTP and DNS by fredfjohnsen on Thursday July 02, 2020 @11:14AM (#23714107)
Uh... RedHat is owned by IBM.
Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @10:58AM (#23713914)
Given:

1) how broadly Google spreads its money to open source projects to get its products set as defaults

2) that Redhat is a private company who does not disclose their funding sources

I think it's a perfectly reasonable question, given the situation (Google product set as a default in an open source project).

Re:Systemd: Don’t fallback to Google NTP and DNS by wtallis on Thursday July 02, 2020 @11:23AM (#23714282)
> that Redhat is a private company who does not disclose their funding sources

Red Hat's IPO was in 1999, and they were bought by IBM in 2019.

Re:Systemd: Don’t fallback to Google NTP and DNS by teddyh on Thursday July 02, 2020 @10:39AM (#23713633)
Re:Systemd: Don’t fallback to Google NTP and DNS by Kaze404 on Thursday July 02, 2020 @11:32AM (#23714393)
Did you read the link you posted? There's no shift of burden of proof, as all the maintainer would have to do is answer "No". I agree that there are people who do this in bad faith, but the question seemed totally reasonable to me.
Re:Systemd: Don’t fallback to Google NTP and DNS by josephcsible on Thursday July 02, 2020 @12:01PM (#23714722)
> all the maintainer would have to do is answer "No"

That would technically be a lie. The answer is actually a qualified "yes".

Re:Systemd: Don’t fallback to Google NTP and DNS by tomxor on Thursday July 02, 2020 @10:19AM (#23713339)
> How not to interact with your community 101.

Maybe, but lowering a discussion to accusations of bribery is also not how to interact with project members.

Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @10:30AM (#23713479)
No, it's not.

But one person is a paid maintainer for the project, the other an (admittedly paranoid) non-paid user. The standards for a paid employee are (and should be) higher.

Re:Systemd: Don’t fallback to Google NTP and DNS by scrollaway on Thursday July 02, 2020 @10:38AM (#23713622)
You don't get to be an asshole to waiters just because they're "paid" and it's "their job".

You don't get to be an asshole to open source maintainers just because they're "paid" and it's "their job".

If in either situation, a person is an asshole to the paid employee, said employee most definitely has a right to defend themselves.

Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @10:53AM (#23713857)
If a waiter said something like this, they would likely have been fired. What was said was only a bit rude, not even remotely abusive, and hardly justifies the attitude expressed towards the community as a whole (the so-called "script kiddy peanut gallery").
Re:Systemd: Don’t fallback to Google NTP and DNS by scrollaway on Thursday July 02, 2020 @02:24PM (#23716362)
If a waiter said something like this to a client being an asshole, some restaurants may fire them if the client is "important" enough, primarily because waiters are easily replaced.

But nowadays, a lot of restaurants will side with the waiter on such issues and they're damn right to do so.

I'll add that what you're seeing here is but the tip of the iceberg of abuse that Lennart has to deal with every day. I challenge you to put up with 1/100th of what he's putting up with without "raising your voice" or what have you.

Re:Systemd: Don’t fallback to Google NTP and DNS by threatofrain on Thursday July 02, 2020 @09:46AM (#23713000)
This isn't something normally set by the end-user but by vendors, and I do presume that distro teams absolutely have enough opinion and energy to set DNS defaults.
Re:Systemd: Don’t fallback to Google NTP and DNS by michaelcampbell on Thursday July 02, 2020 @10:26AM (#23713421)
Poettering being insulting and smug? Who'd've guessed.
Re:Systemd: Don’t fallback to Google NTP and DNS by nine_k on Thursday July 02, 2020 @10:41AM (#23713674)
BTW Linus also used to be pretty insulting, but somehow avoided being smug, AFAICT.
Re:Systemd: Don’t fallback to Google NTP and DNS by protomyth on Thursday July 02, 2020 @10:45AM (#23713733)
Linus acted as that inner code voice that you should of had in the first place. Poettering is just better than you and you should known that.
Re:Systemd: Don’t fallback to Google NTP and DNS by akerro on Thursday July 02, 2020 @10:14AM (#23713299)
This is why Linux and SystemD will struggle to find maintainers in the future: https://www.theregister.com/2020/06/30/hard_to_find_linux_ma...
Re:Systemd: Don’t fallback to Google NTP and DNS by offbyone on Thursday July 02, 2020 @10:22AM (#23713374)
I'm not sure I agree; Poettering isn't being harsh to his collaborators, here. He's protecting them against the implicit accusation of a hostile community member. I'd be _more_, not less likely to want to work on a project with someone who does that.
Re:Systemd: Don’t fallback to Google NTP and DNS by akerro on Thursday July 02, 2020 @10:26AM (#23713425)
>I'm not sure I agree; Poettering isn't being harsh to his collaborators

Not accepting any discussion by blocking all community efforts is quite bad imo. Would like still like to start any discussion, put effort into making even smallest change, to be blocked? This is strong sign of ignorance.

I often contribute to OSS on gitlab and github. When a single/first MR is not merged OR commented on within a week I don't even try there again, waste of time.

Re:Systemd: Don’t fallback to Google NTP and DNS by ocdtrekkie on Thursday July 02, 2020 @11:18AM (#23714190)
In open source, today's community member is tomorrow's collaborator. If you are a tool to your community members, you will end up getting less new collaborators.
Re:Systemd: Don’t fallback to Google NTP and DNS by tobyhinloopen on Thursday July 02, 2020 @10:53AM (#23713855)
It was called for. The commenters were pretty toxic IMO.
Re:Systemd: Don’t fallback to Google NTP and DNS by Hnrobert42 on Thursday July 02, 2020 @11:05AM (#23714007)
Yeah. That was very rude. I’d heard the systemd developers severely lack social skills. The way he went from 0 - EXASPERATED was surprising and uncalled for.
Re:Systemd: Don’t fallback to Google NTP and DNS by offbyone on Thursday July 02, 2020 @05:03PM (#23718052)
Almost as if he'd been the target of a nearly-non-stop decade of constant hostility and abuse or something.
Re:Systemd: Don’t fallback to Google NTP and DNS by finnthehuman on Thursday July 02, 2020 @01:45PM (#23715916)
Lennart is not that good at the human-facing parts of maintainership. That's fine, he doesn't have to be.

I'm just surprised that people don't see how his communication style (in general and in the linked thread) makes interactions harder than it needs to be for himself and everyone involved.

Re:Systemd: Don’t fallback to Google NTP and DNS by joana035 on Thursday July 02, 2020 @10:42AM (#23713700)
> How not to interact with your community 101.

Give Poettering a break! You have no clue what is to be in his shoes. ;)

Re:Systemd: Don’t fallback to Google NTP and DNS by yadco on Thursday July 02, 2020 @09:50AM (#23713045)
Whoever knows how to build systemd should know about this build-time flag
Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @09:53AM (#23713084)
I have to picture that systemd has hundreds, if not thousands, of build time flags. Is it reasonable to expect all non-systemd builders to grok every flag? My opinion is that it is not - that pushing it back on the individual distros is a cop out on Red Hat's side.

EDIT: 172 distinct build-time options, in today's master. Not all appear to be used as part of the build, since the build script only references 142 of the options set in meson_options.txt.

Re:Systemd: Don’t fallback to Google NTP and DNS by ckastner on Thursday July 02, 2020 @10:04AM (#23713199)
systemd plays a crucial role on systems that use it. Whoever builds systemd for a distribution should definitely be aware of those flags; if you don’t understand them, then you are not qualified sufficiently to ship systemd for others to use.

Edit: Speaking as a package maintainer myself.

Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @10:15AM (#23713312)
How many packages do you, as a package maintainer, maintain? Can you say with high confidence that you are aware of all of the flags offered by all of those packages, including changes to the defaults between package releases?

I expect that package maintainers are human, and put a fair bit of trust in the upstream developers, and will only tinker with build flags for issues which are specific to the distro. I also expect that they will miss changes to defaults, or new flags, or deprecated flags, quite often.

I looked at the systemd defaults to see this issue for myself, and the fact that Google's nameservers are in the DNS defaults didn't immediately pop out to me (it's a list of 8 mixed IPv4 and IPv6 addresses).

Re:Systemd: Don’t fallback to Google NTP and DNS by ckastner on Thursday July 02, 2020 @10:25AM (#23713412)
> How many packages do you, as a package maintainer, maintain? Can you say with high confidence that you are aware of all of the flags offered by all of those packages, including changes to the defaults between package releases?

Absolutely. For a responsible package maintainer, reading changelogs and release notes of new releases is a must. For sensitive software (eg: key system libraries), I usually also look at the full diff between releases. I also run tests with dependent software before uploading my version, lest I break any packages that depend on mine. etc.

And this is quite typical of your average distribution package maintainer.

Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @10:31AM (#23713506)
Fair enough - thank you!
Re:Systemd: Don’t fallback to Google NTP and DNS by jschwartzi on Thursday July 02, 2020 @10:49AM (#23713798)
Usually if I'm building something from source I read the entire set of configuration flags and take notes on which configurations I might like, which configurations I might want to turn off, and which configurations I don't understand. So yes I would read all the options in the meson_options.txt and decide how I want to configure systemd before beginning the cross-compile.

Someone posted the other day that an autotools/automake should canonically be run like this:

  ./configure
  make
  make install
But really the best workflow is like this:

  ./configure  --help
  (read "help" intently)
  mkdir build_output_dir
  cd build_output_dir
  ../configure [huge list of options for the build]
  make
  make install
I would do the same thing here.
Re:Systemd: Don’t fallback to Google NTP and DNS by megous on Thursday July 02, 2020 @10:08AM (#23713237)
> (how many people knew this was a default before now?)

Pretty much everyone who ever opened /etc/systemd/resolved.conf

Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @10:26AM (#23713418)
Did you know that there are at least four different file locations that resolvers can be set in for systemd-resolved?

The defaults being in a commented-out section in one of these four locations (and in a file whose name does not match the linux standard of resolv.conf) is, frankly, not a big help in identifying what's really being used.

https://jlk.fjfi.cvut.cz/arch/manpages/man/systemd-resolved....

Re:Systemd: Don’t fallback to Google NTP and DNS by JdeBP on Thursday July 02, 2020 @04:54PM (#23717952)
Actually, it's five, or even six. systemd doco is bad at including /usr/local/ .

You are pointing to the wrong manual page, incidentally. It's resolved.conf(5). This fails to list /usr/local/lib/systemd/resolved.conf.d/ , which is scanned before /usr/lib/systemd/resolved.conf.d/ (and if configured /lib/systemd/resolved.conf.d/).

Re:Systemd: Don’t fallback to Google NTP and DNS by megous on Thursday July 02, 2020 @12:44PM (#23715137)
How do any of those 4 resolv.conf location variants change where the compiled-in fallback is configured/visible?

If user wants to know what's really being used for name resolution he should go to /etc/nsswtich.conf and /etc/hosts and /etc/resolv.conf as usual.

Re:Systemd: Don’t fallback to Google NTP and DNS by JdeBP on Thursday July 02, 2020 @05:11PM (#23718115)
If systemd-resolved is actually being used, /etc/resolv.conf will list only 127.0.0.53, and to find out what systemd-resolved itself is using one has to visit the resolved.conf configuration files, which is what falcolas is apparently talking about.

But then if one is using, say, dnscache or dnsmasq or MaraDNS or BIND or PowerDNS or any other such software, one has to do the same thing. /etc/resolv.conf will list simply 127.0.0.1 or some such, and one has to go further to the configuration files of those softwares to find out what they are using for resolution/forwarding.

DNS softwares having their own configuration files is normal. falcolas is apparently getting at the fact that systemd-resolved uses the same style of configuration as the other systemd programs do: files and drop-in directories in /etc/systemd, /run/systemd, /usr/local/lib/systemd, /usr/lib/systemd, and (if configured) /lib/systemd, meaning that one has to read all of this together.

Re:Systemd: Don’t fallback to Google NTP and DNS by megous on Thursday July 02, 2020 @06:36PM (#23718905)
It would be clearer if he linked to https://jlk.fjfi.cvut.cz/arch/manpages/man/resolved.conf.5.e... then.

Anyway, in default config, there will be only the file I mentioned. And whole this issue is about default configuration.

Re:Systemd: Don’t fallback to Google NTP and DNS by JdeBP on Thursday July 02, 2020 @07:20PM (#23719192)
Actually, no. The headlined issue is about what the fallback is when there is no file, or a file that doesn't specify a setting.
Re:Systemd: Don’t fallback to Google NTP and DNS by megous on Friday July 03, 2020 @12:30PM (#23725333)
There's always /etc/systemd/resolved.conf in default installation/build.
Re:Systemd: Don’t fallback to Google NTP and DNS by JdeBP on Sunday July 05, 2020 @03:46PM (#23741329)
... which does not specify a setting. As falcolas explained at the start. Have you caught up now?
Re:Systemd: Don’t fallback to Google NTP and DNS by djsumdog on Thursday July 02, 2020 @10:56AM (#23713892)
Wow. I never realized there was a DNS server listening at 127.0.0.53 on systemd based distros.
Re:Systemd: Don’t fallback to Google NTP and DNS by creeble on Thursday July 02, 2020 @12:00PM (#23714709)
Just try using a system on a "captive portal" wifi connection. You will soon learn "apt purge systemd-resolvd".
Re:Systemd: Don’t fallback to Google NTP and DNS by munchbunny on Thursday July 02, 2020 @10:11AM (#23713272)
Pretty much everyone who ever opened /etc/systemd/resolved.conf

That's a vanishingly small percentage of people who use systemd.

Re:Systemd: Don’t fallback to Google NTP and DNS by megous on Thursday July 02, 2020 @10:15AM (#23713305)
Perhaps, but still larger than the set of people who compile their own systemd builds.

Also it's the answer to the question. The defaults are visible in config files as commented out lines. No need to check build scripts, etc.

Re:Systemd: Don’t fallback to Google NTP and DNS by hedora on Thursday July 02, 2020 @10:39AM (#23713646)
If you are correct, Poettering doesn’t understand how to configure the last resort fallback.

He says the easiest way is to recompile systemd from source.

Presumably he knows more about systemd then the average Linux user.

Re:Systemd: Don’t fallback to Google NTP and DNS by megous on Thursday July 02, 2020 @12:32PM (#23715019)
You're assuming a lot of things. That I'm an average user (I'm not) and that thing about Poettering.
Re:Systemd: Don’t fallback to Google NTP and DNS by hedora on Thursday July 02, 2020 @10:33AM (#23713540)
Also, “work with your downstream” rings hollow coming from a RedHat employee.

Anyway, per his advice, here is how I worked with my Linux distribution to fix the problem: I switched away, and donated to ones that don’t use systemd.

Re:Systemd: Don’t fallback to Google NTP and DNS by raverbashing on Thursday July 02, 2020 @09:50AM (#23713042)
Does it matter now (that the maintainers can't dialogue with the community)?

In one side major linux distros took in systemd (as, ok, granted, the "less worse" of the options) so the point is moot. I mean everybody should know how LPs management of the project works.

At the same time I can understand trying to cut down on drama in online discussions (though I agree that default might make more sense as a run-time configurable, not as a build-time one).

(And yes defaults are important)

Re:Systemd: Don’t fallback to Google NTP and DNS by falcolas on Thursday July 02, 2020 @09:57AM (#23713128)
Systemd being the default init system in the distro, and google being a default resolver in systemd, are separate issues.

Yes, it does matter. It's being pushed out as the init system for a lot of linux systems, and I believe it's perfectly reasonable to expect that your fallback DNS resolver is not set to a for-profit data-collection organization.