all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Akshay Khobragade <akshaykhobragade@tuta.io>
Cc: 39713@debbugs.gnu.org
Subject: bug#39713: Was told on IRC (#guix at freenode) to share the details of my problem with Guix (SD) via email
Date: Fri, 21 Feb 2020 18:56:56 +0100	[thread overview]
Message-ID: <877e0fygbb.fsf@nckx> (raw)
In-Reply-To: <M0bCu7e--3-2@tuta.io>

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

Akshay,

Akshay Khobragade via Bug reports for GNU Guix 写道：
> This is my first ever installation of Guix where I chose:
>
> 1. Separate Boot (/boot) and EFI (/boot/efi) partitions
> 2. Encrypted root (having used it in Debian for the last 10 
> months, I am comfortable)

This just isn't possible (yet).

There's no support in Guix System for a separate, unencrypted, 
/boot partition.  If you want a Guix System with full disk 
encryption you'll have to keep /boot as a regular subdirectory and 
enter your passphrase twice.

Both of these limitations could be removed by someone sufficiently 
motivated and/or annoyed :-)

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2020-02-21 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 10:09 bug#39713: Was told on IRC (#guix at freenode) to share the details of my problem with Guix (SD) via email Akshay Khobragade via Bug reports for GNU Guix
2020-02-21 16:59 ` bug#39713: reply to the original report Akshay Khobragade via Bug reports for GNU Guix
2020-02-21 17:56 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-02-21 18:03 ` bug#39713: Akshay Khobragade via Bug reports for GNU Guix
2020-02-21 20:34 ` bug#39713: Akshay Khobragade via Bug reports for GNU Guix
2020-02-22  0:02   ` bug#39713: Ludovic Courtès

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=877e0fygbb.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=39713@debbugs.gnu.org \
    --cc=akshaykhobragade@tuta.io \
    --cc=me@tobias.gr \
    /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.