Bug#900366: postinst creation of /etc/machine-id breaks CustomFirstBoot unit parameter
Michael Biebl
biebl at debian.org
Tue May 29 17:17:39 BST 2018
Am 29.05.2018 um 16:53 schrieb Matthew Richardson:
> Package: systemd
> Version: 238-5
>
> The postinst for the systemd deb pkg contains the following:
>
> # Create /etc/machine-id
> systemd-machine-id-setup
>
> This generates /etc/machine-id as the package is installed.
>
> However the systemd unit option ConditionFirstBoot uses the presence or
> absence of this file to detect whether or not this is the first boot.
> From 'man systemd.unit'
>
> "ConditionFirstBoot= takes a boolean argument. This condition may be
> used to conditionalize units on whether the system is booting up with an
> unpopulated /etc directory (specifically: an /etc with no
> /etc/machine-id). This may be used to populate /etc on the first boot
> after factory reset, or when a new system instance boots up for the
> first time."
>
> Since no unit can start until after systemd is installed, and the
> install always creates this file, this test will always be False which
> renders this option useless.
Well, if you remove /etc/machine-id as part of your debootstrap process,
then /etc/machine-id will not be present during boot.
Or if you use a stateless system, then /etc might be empty as well.
So the Condition still makes sense.
Can you elaborate, what this bug report is supposed to achieve?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180529/bd141419/attachment-0002.sig>
More information about the Pkg-systemd-maintainers
mailing list