On Wed, 30 Sep 2020, Zbigniew Jędrzejewski-Szmek wrote:
the systemd package is getting a systemd-networkd subpackage split out that will contain systemd-networkd, networkctl, and the associated data files. This was requested by coreos maintainers: NetworkManager is used and skipping systemd-networkd allows the installation footprint and potential user confusion to be reduced a bit. (By 1.6 MB and an unknown amount, respectively.)
The main systemd systemd package Obsoletes the -standalone- packages, so it should smoothly replace them whenever it is pulled in.
In which package will systemd-resolved be? With enterprise server deployments, DNS will be managed by the network via resolve.conf to enterprise DNS servers. These servers tend to have "bind views" for different category of deployments. These deployments will have no VPN, no mDNS requirements etc. They also do not need (and most likely do not want) DNS caching. I believe it would be useful for kickstart installs to not install systemd-resolved for these kind of typical server deployments. I think this is an important use case to support. For Desktop systems, it could default to installing systemd-resolved. It could even default to it for all installs including Server, as long as the administrator has the option to not install it via a kickstart file. It also allows those Destop users that want to use their own validating resolvers on the end node to uninstall systemd-resolved. If there are strong reasons not to split systemd-resolved in its own package, I would like to better understand these reasons. Paul _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
