Systemd: Difference between revisions

Revision as of 09:43, 2 August 2019

Revision as of 23:14, 3 September 2019

Line 329:

In a September 2014 [[ZDNet]] interview, prominent Linux kernel developer [[Theodore Ts'o]] expressed his opinion that the dispute over systemd's centralized design philosophy, more than technical concerns, indicates a dangerous general trend toward uniformizing the Linux ecosystem, alienating and marginalizing parts of the open-source community, and leaving little room for alternative projects. He cited similarities with the attitude he found in the GNOME project toward non-standard configurations.<ref name="zdnet-20140919" /> On social media, Ts'o also later compared the attitudes of Sievers and his co-developer, Lennart Poettering, to that of GNOME's developers.<ref name="Tso" />

On 6 July 2015, an issue was raised on the systemd GitHub page expressing concerns about the [[hard coding]] of DNS servers in the systemd code. Poettering responded that it is not the actual DNS but rather the fallback DNS that is hard coded. He added that the fallback DNS is only used if "...&nbsp;nobody configured anything&nbsp;..." and to prevent connectivity issues due to catastrophic failure of configuration files or a lack of DHCP on the network. As Poettering described, the system "...&nbsp;should do the right thing&nbsp;..." if, as an example, the /etc directory were missing or empty. Poettering also noted that the /etc/systemd/resolved.conf file installed with systemd contains exactly the same DNS servers as the fallback DNS, thereby resulting in the same operation regardless of the /etc directory being empty or present.<ref>{{cite web |title="FallbackDNS shouldn't have values set at compile time"|url = https://github.com/systemd/systemd/issues/494|date=6 June 2015|access-date=3 June 2018}}</ref>

== Forks and alternative implementations ==