1
Description: Warn and return without error if /boot is a dm-crypt device
2
With any luck the administrator knows what they're doing; in any event, we
3
probably can't improve matters by having update-grub exit non-zero.
4
Author: Marc Haber <mh+debian-bugs@zugschlus.de>
5
Author: Colin Watson <cjwatson@debian.org>
6
Origin: other, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542165#25
7
Bug-Debian: http://bugs.debian.org/542165
9
Last-Update: 2010-06-05
11
Index: b/util/grub-mkconfig_lib.in
12
===================================================================
13
--- a/util/grub-mkconfig_lib.in
14
+++ b/util/grub-mkconfig_lib.in
19
+ if dmsetup status $device 2>/dev/null | grep -q 'crypt[[:space:]]$'; then
21
+ "$device is a crypto device, which GRUB cannot read directly. Some" \
22
+ "necessary modules may be missing from /boot/grub/grub.cfg. You may" \
23
+ "need to list them in GRUB_PRELOAD_MODULES in /etc/default/grub. See" \
24
+ "http://bugs.debian.org/542165 for details."
28
# Abstraction modules aren't auto-loaded.
29
abstraction="`"${grub_probe}" --device "${device}" --target=abstraction`"
30
for module in ${abstraction} ; do