On Tue, 16 Jul 2024 at 14:46, Daniel Gröber <d...@darkboxed.org> wrote: > > Hi Luca, > > On Mon, Jul 15, 2024 at 02:50:17PM +0100, Luca Boccassi wrote: > > Let's put some hard numbers on the table given this is an important > > detail. The following is all starting from a default debootstrapped > > unstable. > > > > With networkd only we can drop ifupdown, net changes: > > > > REMOVING: > > ifupdown > > > > Summary: > > Upgrading: 0, Installing: 0, Removing: 1, Not Upgrading: 0 > > Freed space: 207 kB > > > > > > Using network-manager in headless mode (no GUI) brings in: > > [...] > > > > Summary: > > Upgrading: 0, Installing: 69, Removing: 0, Not Upgrading: 0 > > Download size: 28.2 MB > > Space needed: 110 MB / 8295 MB available > > > > > > Installing netplan.io instead brings in: > > [...] > > > > Summary: > > Upgrading: 0, Installing: 42, Removing: 0, Not Upgrading: 0 > > Download size: 25.2 MB > > Space needed: 101 MB / 8340 MB available > > > > > > So we have a net gain of ~200K when using networkd, a net loss of > > ~110M when using network-manager, and a net loss of ~101M when using > > netplan. > > For completeness let me turn that arguemnt around on you as systemd > maintainer. Why is systemd-networkd, a component currently disabled by > default mind you bloating our base system? :)
Because it is used commonly enough in servers/containers, and doesn't bring in any additional dependencies
