From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1VPaly-0000RD-EL for mharc-grub-devel@gnu.org; Fri, 27 Sep 2013 12:20:06 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38750) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VPalp-0000Lw-LQ for grub-devel@gnu.org; Fri, 27 Sep 2013 12:20:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VPalj-0004E1-2D for grub-devel@gnu.org; Fri, 27 Sep 2013 12:19:57 -0400 Received: from yes.iam.tj ([109.74.197.121]:34020 helo=iam.tj) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VPali-0004DY-SD for grub-devel@gnu.org; Fri, 27 Sep 2013 12:19:50 -0400 Received: from [10.254.251.50] (jeeves.iam.tj [82.71.24.87]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by iam.tj (Postfix) with ESMTPSA id 99E2D3407C for ; Fri, 27 Sep 2013 17:19:48 +0100 (BST) Message-ID: <5245B023.6070100@iam.tj> Date: Fri, 27 Sep 2013 17:19:47 +0100 From: TJ User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: grub-devel@gnu.org Subject: GRUB_ENABLE_CRYPTODISK vs GRUB_CRYPTODISK_ENABLE ? References: <20130329164335.6d89ab0a@opensuse.site> <20130924143933.2f133939@opensuse.site> <5241732F.1090100@gmail.com> In-Reply-To: <5241732F.1090100@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 109.74.197.121 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Sep 2013 16:20:04 -0000 What is the difference between GRUB_ENABLE_CRYPTODISK and GRUB_CRYPTODISK_ENABLE? GRUB_ENABLE_CRYPTODISK only seems to be used in an export in "util/grub-mkconfig.in" whereas GRUB_CRYPTODISK_ENABLE is used in "util/grub-{install,mkconfig_lib}.in". On Ubuntu 13.10 at least I found that I had to edit the export in 'grub-mkconfig' to be GRUB_CRYPTODISK_ENABLE in order for the installer scripts to correctly install for whole-disk encryption. Unless there's some Makefile or pre-processor magic going on which I've missed I believe this might be a bug.