all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Sloan <steve@stevesloan.com>
To: help-guix@gnu.org
Subject: Libreboot + WDE + GuixSD: Need some advice
Date: Tue, 11 Apr 2017 22:05:36 -0700	[thread overview]
Message-ID: <CAMK_J09EKe5WP-8wUxQS+wBxAsbrirWimZtDoYNp+DxJrRch4g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

I am looking for some advice.

I'm am setting up a libreboot + whole disk encryption + guixsd laptop.
Libreboot has grub in the BIOS, which allows for encrypting the whole disk.

According to the libreboot docs, I can make the grub config available at
/boot/grub/libreboot_grub.cfg and the grub installed on the BIOS will load
and use that config file.  I've installed guixsd with --no-grub, I have
libreboot installed, and the disk encrypted, now I just need to make it
bootable!

I think I need to make the correct grub config file available at that
location whenever I reconfigure.  I can manage the coding, but I'd like
hints on the best way to go about this with guix.

There are some other options I've considered.  I could reflash my BIOS as
part of the reconfiguration process.  Or maybe I could chain-load two grub
installations, possibly with an unencrypted /boot.

What do people do when they don't have GuixSD manage their grub
configuration?

ref: https://libreboot.org/docs/gnulinux/grub_cbfs.html,
      https://libreboot.org/docs/gnulinux/encrypted_parabola.html

Thanks!

[-- Attachment #2: Type: text/html, Size: 1453 bytes --]

             reply	other threads:[~2017-04-12  5:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  5:05 Stephen Sloan [this message]
2017-04-12 15:21 ` Libreboot + WDE + GuixSD: Need some advice Marius Bakke
2017-04-13  4:08   ` Stephen Sloan
2017-04-13  7:31     ` Chris Marusich

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=CAMK_J09EKe5WP-8wUxQS+wBxAsbrirWimZtDoYNp+DxJrRch4g@mail.gmail.com \
    --to=steve@stevesloan.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.