Skip to content
Snippets Groups Projects
  1. Apr 02, 2019
  2. Apr 01, 2019
  3. Mar 29, 2019
  4. Mar 28, 2019
  5. Mar 27, 2019
  6. Mar 26, 2019
  7. Mar 22, 2019
  8. Mar 21, 2019
  9. Mar 20, 2019
  10. Mar 18, 2019
  11. Mar 15, 2019
  12. Mar 14, 2019
  13. Mar 13, 2019
    • Emanuele Aina's avatar
      Clarify the actual reason machine-id can't be truncated earlier · e8691e70
      Emanuele Aina authored
      Even after fixing https://github.com/systemd/systemd/issues/11925
      
       we
      would still have issues by truncating the /etc/machine-id earlies, as
      the actual problem is that the systemd-boot tools rely on it being set
      for dual-boot scenarios:
      * to avoid conflicts when creating entries, see the `90-loaderentry` kernel
        install trigger
      * to set the entries for the currently booted installation as default in
        the loader.conf generated by `bootctl install`
      
      In our image this is not useful, as the actual machine-id is supposed to be
      uniquely generated on the first boot. However the impact is negligible, as
      things still work albeit the code used to potentially disambiguate entries
      doesn't match a real machine-id.
      
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      e8691e70
Loading