pkgs/os-specific/linux/systemd/0001-Start-device-units-for-uninitialised-encrypted-devic.patch

   1 From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
   2 From: Eelco Dolstra <eelco.dolstra@logicblox.com>
   3 Date: Tue, 8 Jan 2013 15:46:30 +0100
   4 Subject: [PATCH] Start device units for uninitialised encrypted devices
   5
   6 This is necessary because the NixOS service that initialises the
   7 filesystem depends on the appearance of the device unit.  Also, this
   8 makes more sense to me: the device is ready; it's the filesystem
   9 that's not, but taking care of that is the responsibility of the mount
  10 unit.  (However, this ignores the fsck unit, so it's not perfect...)
  11 ---
  12  rules.d/99-systemd.rules.in | 4 ----
  13  1 file changed, 4 deletions(-)
  14
  15 diff --git a/rules.d/99-systemd.rules.in b/rules.d/99-systemd.rules.in
  16 index ad0c7e2fb5..79f3086e78 100644
  17 --- a/rules.d/99-systemd.rules.in
  18 +++ b/rules.d/99-systemd.rules.in
  19 @@ -26,10 +26,6 @@ SUBSYSTEM=="block", ACTION=="add", KERNEL=="dm-*", ENV{DM_NAME}!="?*", ENV{SYSTE
  20  # Import previous SYSTEMD_READY state.
  21  SUBSYSTEM=="block", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}=="", IMPORT{db}="SYSTEMD_READY"
  22
  23 -# Ignore encrypted devices with no identified superblock on it, since
  24 -# we are probably still calling mke2fs or mkswap on it.
  25 -SUBSYSTEM=="block", ENV{DM_UUID}=="CRYPT-*", ENV{ID_PART_TABLE_TYPE}=="", ENV{ID_FS_USAGE}=="", ENV{SYSTEMD_READY}="0"
  26 -
  27  # add symlink to GPT root disk
  28  SUBSYSTEM=="block", ENV{ID_PART_GPT_AUTO_ROOT}=="1", ENV{ID_FS_TYPE}!="crypto_LUKS", SYMLINK+="gpt-auto-root"
  29  SUBSYSTEM=="block", ENV{ID_PART_GPT_AUTO_ROOT}=="1", ENV{ID_FS_TYPE}=="crypto_LUKS", SYMLINK+="gpt-auto-root-luks"