pyrox.dev
1From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
2From: Eelco Dolstra <eelco.dolstra@logicblox.com>
3Date: Tue, 8 Jan 2013 15:46:30 +0100
4Subject: [PATCH] Start device units for uninitialised encrypted devices
5
6This is necessary because the NixOS service that initialises the
7filesystem depends on the appearance of the device unit. Also, this
8makes more sense to me: the device is ready; it's the filesystem
9that's not, but taking care of that is the responsibility of the mount
10unit. (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
15diff --git a/rules.d/99-systemd.rules.in b/rules.d/99-systemd.rules.in
16index c0defc31de..8f80235731 100644
17--- a/rules.d/99-systemd.rules.in
18+++ b/rules.d/99-systemd.rules.in
19@@ -20,10 +20,6 @@ SUBSYSTEM=="block", TAG+="systemd"
20 SUBSYSTEM=="block", ENV{DM_SUSPENDED}=="1", IMPORT{db}="SYSTEMD_READY", GOTO="systemd_end"
21 SUBSYSTEM=="block", ACTION=="add", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"
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 # Explicitly set SYSTEMD_READY=1 for DM devices that don't have it set yet, so that we always have something to import above
28 SUBSYSTEM=="block", ENV{DM_UUID}=="?*", ENV{SYSTEMD_READY}=="", ENV{SYSTEMD_READY}="1"
29