Your message dated Fri, 3 Jan 2020 09:19:15 +0100
with message-id <[email protected]>
and subject line Re: Bug#947807: systemd: can't install systemd when
/etc/machine-id is a symbolic link to /dev/null
has caused the Debian Bug report #947807,
regarding systemd: can't install systemd when /etc/machine-id is a symbolic
link to /dev/null
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
947807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947807
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 241-7~deb10u2
Severity: normal
Dear Maintainer,
/etc/machine-id should not be used on workstations anymore due to privacy
reasons. The way to
disable it was announced as rm /etc/machine-id ; ln -s /dev/null
/etc/machine-id at the time.
systemd's configuration script can't handle it.
-- Package-specific info:
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE=en_US
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.53-4
ii libapparmor1 2.13.2-10
ii libaudit1 1:2.8.4-3
ii libblkid1 2.33.1-0.1
ii libc6 2.28-10
ii libcap2 1:2.25-2
ii libcryptsetup12 2:2.1.0-5+deb10u2
ii libgcrypt20 1.8.4-5
ii libgnutls30 3.6.7-4
ii libgpg-error0 1.35-1
ii libidn11 1.33-2.2
ii libip4tc0 1.8.2-4
ii libkmod2 26-1
ii liblz4-1 1.8.3-1
ii liblzma5 5.2.4-1
ii libmount1 2.33.1-0.1
ii libpam0g 1.3.1-5
ii libseccomp2 2.3.3-4
ii libselinux1 2.8-1+b1
ii libsystemd0 241-7~deb10u2
ii mount 2.33.1-0.1
ii util-linux 2.33.1-0.1
Versions of packages systemd recommends:
ii dbus 1.12.16-1
ii libpam-systemd-apt-holepunch [libpam-systemd] 1
Versions of packages systemd suggests:
ii policykit-1 0.105-25
pn systemd-container <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.133+deb10u1
ii udev 241-7~deb10u2
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 31.12.19 um 17:09 schrieb Joshua Hudson:
> # apt-get install systemd-sysv
> [lots of junk]
> Initializing machine ID from random generator.
> Failed to truncate /etc/machine-id: Invalid argument
>
> This is trivially verified by
>
> # dpkg-reconfigure systemd
> Initializing machine ID from random generator.
> Failed to truncate /etc/machine-id: Invalid argument
> #
>
I checked the existing documentation and symlinking /etc/machine-id to
/dev/null is not a supported configuration (not sure where you got that
information).
The machine-id is required at various places (one is the journal) and
symlinking that to /dev/null will break that.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
