summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorJamey Sharp <jamey@minilop.net>2018-09-29 11:35:00 -0700
committerJamey Sharp <jamey@minilop.net>2018-09-30 10:45:35 -0700
commit8d40083690c2d20d20c32d7d90b9fd7b7f559042 (patch)
treeec7c212d074a9d26298110cabcfb9969e49bbf53 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parentf449242e83bd441300f009321157dd308326cfcc (diff)
nixos/stage-2: create empty machine-id at boot
Previously, the activation script was responsible for ensuring that /etc/machine-id exists. However, the only time it could not already exist is during stage-2-init, not while switching configurations, because one of the first things systemd does when starting up as PID 1 is to create this file. So I've moved the initialization to stage-2-init. Furthermore, since systemd will do the equivalent of systemd-machine-id-setup if /etc/machine-id doesn't have valid contents, we don't need to do that ourselves. We _do_, however, want to ensure that the file at least exists, because systemd also uses the non-existence of this file to guess that this is a first-boot situation. In that case, systemd tries to create some symlinks in /etc/systemd/system according to its presets, which it can't do because we've already populated /etc according to the current NixOS configuration. This is not necessary for any other activation script snippets, so it's okay to do it after stage-2-init runs the activation script. None of them declare a dependency on the "systemd" snippet. Also, most of them only create files or directories in ways that obviously don't need the machine-id set.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions