grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: mchang@suse.com
Subject: Re: GRUB_CRYPTODISK_ENABLE undocumented
Date: Tue, 24 Sep 2013 14:39:33 +0400	[thread overview]
Message-ID: <20130924143933.2f133939@opensuse.site> (raw)
In-Reply-To: <CAOx4COUZq=_7sXjJhf=NH5sezXYJ8gEiFuGuH1D5OtA2HqP_ig@mail.gmail.com>

В Wed, 28 Aug 2013 15:04:44 +0800
Michael Chang <mchang@suse.com> пишет:

> Hi Andrey,
> 
> 2013/3/29 Andrey Borzenkov <arvidjaar@gmail.com>:
> > Is it intentional? I hit it when testing grub on encrypted partition.
> > When no, I'll submit a patch.
> 
> Do you have any progress on this? Besides document it, IMHO why not we
> consider to remove it or make it default enable to receive more
> testing from downstream ? Is there any consequence to enable it or
> because it's not officially supported yet?
> 
> Even if it's immature, more testing is welcome to get all bugs sorted
> and resolved.
> 

Well, I'm not sure which progress can be. I do not have any preference
whether it should be default or not, I just think it should be
documented.

Vladimir, is it OK?

From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: [PATCH] document GRUB_ENABLE_CRYPTODISK configuration option

Signed-off-by: Andrey Borzenkov <arvidjaar@gmail.com>

---
 docs/grub.texi | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/grub.texi b/docs/grub.texi
index 574f602..9903a36 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -1354,6 +1354,12 @@ Normally, @command{grub-mkconfig} will try to use the external
 systems installed on the same system and generate appropriate menu entries
 for them.  Set this option to @samp{true} to disable this.
 
+@item GRUB_ENABLE_CRYPTODISK
+If set to @samp{y}, @command{grub-mkconfig} and @command{grub-install} will
+check for encrypted disks and generate additional commands needed to access
+them during boot.  Note that in this case unattended boot is not possible
+because GRUB will wait for passphrase to unlock encrypted container.
+
 @item GRUB_INIT_TUNE
 Play a tune on the speaker when GRUB starts.  This is particularly useful
 for users unable to see the screen.  The value of this option is passed
-- 
tg: (321e011..) u/crypto_eable (depends on: master)


  reply	other threads:[~2013-09-24 10:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 12:43 GRUB_CRYPTODISK_ENABLE undocumented Andrey Borzenkov
2013-08-28  7:04 ` Michael Chang
2013-09-24 10:39   ` Andrey Borzenkov [this message]
2013-09-24 11:10     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-09-27 16:19       ` GRUB_ENABLE_CRYPTODISK vs GRUB_CRYPTODISK_ENABLE ? TJ
2013-09-27 16:43         ` Andrey Borzenkov
2013-08-28  7:05 ` GRUB_CRYPTODISK_ENABLE undocumented Michael Chang
2013-08-28 14:51   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-29  7:37     ` Michael Chang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130924143933.2f133939@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=mchang@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).