Hi, systemd has a tendency to grow in size with each new release (and I mean installed Mb on disk here).
Looking at the size of a couple of binaries, I'm really suprised they are so huge: 36K bin/systemd-notify 36K usr/bin/systemd-cat 36K usr/bin/systemd-detect-virt 40K bin/systemd-escape 44K usr/bin/systemd-path 48K bin/systemd-machine-id-setup 52K bin/systemd-ask-password 64K bin/systemd-hwdb 64K usr/bin/systemd-delta 68K bin/systemd-tty-ask-password-agent 76K usr/bin/bootctl 132K bin/systemd-tmpfiles 140K usr/bin/coredumpctl 276K bin/systemd-inhibit 288K usr/bin/hostnamectl 292K usr/bin/systemd-cgls 296K usr/bin/localectl 296K usr/bin/timedatectl 304K usr/bin/systemd-cgtop 328K usr/bin/systemd-resolve 344K usr/bin/systemd-stdio-bridge 364K usr/bin/busctl 368K usr/bin/systemd-run 436K bin/udevadm 444K bin/loginctl 476K bin/machinectl 488K bin/journalctl 572K usr/bin/systemd-nspawn 648K bin/systemctl 656K bin/networkctl 1,5M usr/bin/systemd-analyze Any ideas, why simple tools like loginctl, busctl, hostnamectl require 300K+ ? What's up with systemd-analyze? Could we move more common functionality into a shared, private library to counter the constant growth? I'm really concerned that a simple "make install" here takes up more then 30M here. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel