summaryrefslogtreecommitdiffstats
path: root/master/debian/mkconfig_skip_dmcrypt.patch
blob: 4e746526a97e57487a7847e336e154e8641d2fd2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Description: Warn and return without error if /boot is a dm-crypt device
 With any luck the administrator knows what they're doing; in any event, we
 probably can't improve matters by having update-grub exit non-zero.
Author: Marc Haber <mh+debian-bugs@zugschlus.de>
Author: Colin Watson <cjwatson@debian.org>
Origin: other, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542165#25
Bug-Debian: http://bugs.debian.org/542165
Forwarded: no
Last-Update: 2010-06-05

Index: b/util/grub-mkconfig_lib.in
===================================================================
--- a/util/grub-mkconfig_lib.in
+++ b/util/grub-mkconfig_lib.in
@@ -105,6 +105,15 @@
 {
   device="$1"
 
+  if dmsetup status $device 2>/dev/null | grep -q 'crypt[[:space:]]$'; then
+    grub_warn \
+      "$device is a crypto device, which GRUB cannot read directly.  Some" \
+      "necessary modules may be missing from /boot/grub/grub.cfg.  You may" \
+      "need to list them in GRUB_PRELOAD_MODULES in /etc/default/grub.  See" \
+      "http://bugs.debian.org/542165 for details."
+    return 0
+  fi
+
   # Abstraction modules aren't auto-loaded.
   abstraction="`"${grub_probe}" --device "${device}" --target=abstraction`"
   for module in ${abstraction} ; do