Re: Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)
Control: severity -1 normal
Hello,
On Sun, Feb 18, 2024 at 01:09:56PM -0800, Flavio Veloso Soares wrote:
> So I just want to clarify what's the current status quo regarding
> systemd-resolved/-networkd in cloud images so I can file bug reports
> properly.
Not a bug - it was done in [1]. ifupdown uses ISC's dhcp client, which was
abandoned upstream. The cloud team decided it wouldn't be responsible to ship
a new stable release with an unsupported dhcp client.
Since this differs from the default, we probably should've put something in the
release notes - that seems like an oversight.
> p.s.: same for polkitd -- not sure if we need a daemon "intended to be
$ apt-cache rdepends --installed polkitd
polkitd
Reverse Depends:
systemd
systemd-resolved
> used by privileged programs offering service to unprivileged programs
> often through some form of inter-process communication mechanism"
> installed NOT TO SAY RUNNING on a purposedly minimal network server
> that virtually can only be acessed via ssh.
It sounds like your sense of "minimal" is not part of the cloud team's goals.
The repo at [2] makes it easy to build your own images, if you'd prefer to
avoid systemd.
Ross
[1] https://salsa.debian.org/cloud-team/debian-cloud-images/-/merge_requests/284
[2] https://salsa.debian.org/cloud-team/debian-cloud-images/
Reply to: