From: "Clément Lassieur" <clement@lassieur.org>
To: Benjamin Slade <beoram@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: LUKS-encrypted root and unencrypted /boot ?
Date: Fri, 03 Aug 2018 20:53:40 +0200 [thread overview]
Message-ID: <878t5n8eob.fsf@lassieur.org> (raw)
In-Reply-To: <87a7q3fkji.fsf@jnanam.net>
Benjamin Slade <beoram@gmail.com> writes:
> > Do you use Libreboot?
>
> Yes, I'm using Libreboot. Does this make a great difference over the
> manufacturer firmware in this case?
It might, because the GRUB used is the one shipped with Libreboot. So
it has nothing to do with Guix. I think talking to the libreboot people
would help you more. (Disclaimer: I have the same issue, I find that
pressing 'c' and typing 'cryptomount ahci0,gpt3' makes the process
faster.)
> > I'm unsure [using an unencrypted /boot] would help, because GRUB
> > would still have to unencrypt / to access the kernel (the kernel is
> > in /gnu/store).
>
> Ah, I see. Is this an immutable design decision? It would seem good to
> be able to keep the kernel in a separate space in order to avoid the
> issue of extremely long unlocking times when booting.
Nothing is immutable, but it's a strong design decision that all
packages data are put in /gnu/store. Linux is just one of them. Plus,
a characteristic of GuixSD is that you can revert to previous
configurations. Those configurations appear as GRUB lines. Each
configuration could have a different kernel and kernels take space, so
it wouldn't scale well. Plus, I think some other stuff is needed as
well, like the initrd, which is large too, etc.
There are probably reasons I don't know about too :-)
Good luck!
Clément
next prev parent reply other threads:[~2018-08-03 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 18:59 LUKS-encrypted root and unencrypted /boot ? Benjamin Slade
2018-08-02 6:59 ` Clément Lassieur
2018-08-03 17:05 ` Benjamin Slade
2018-08-03 18:53 ` Clément Lassieur [this message]
2018-08-04 15:30 ` Benjamin Slade
2018-08-04 15:48 ` Clément Lassieur
2018-08-04 21:14 ` Benjamin Slade
2018-08-05 5:26 ` Chris Marusich
2018-08-02 8:24 ` Chris Marusich
2018-08-03 17:07 ` Benjamin Slade
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=878t5n8eob.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=beoram@gmail.com \
--cc=help-guix@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.