From: Leo Famulari <leo@famulari.name>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: GuixSD encrypted root?
Date: Sun, 24 Apr 2016 14:51:34 -0400 [thread overview]
Message-ID: <20160424185134.GB7737@jasmine> (raw)
In-Reply-To: <20160424180425.69bbe050@scratchpost.org>
On Sun, Apr 24, 2016 at 06:04:25PM +0200, Danny Milosavljevic wrote:
> On Sun, 24 Apr 2016 16:22:16 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>
> > Encrypted root file systems are not supported yet (some people managed
> > to work around the lack of support, but that’s somewhat fragile.)
> >
> > Good news is we’re getting there! You can track progress at
> > <http://bugs.gnu.org/21843>.
>
> Thanks!
>
> Yeah, but even using a non-required-for-boot encrypted filesystem (i.e. not an encrypted root, just encrypted home) doesn't work. As soon as I add "mount? #t" it hangs.
>
> I'm now using a workaround where it's specified using "mount? #f" and I mount it using a autorun script in my homedir (using "mount /x"). That works fine.
>
> You're using an encrypted home, right? Does it work for you?
This works for me, with an encrypted /home on ext4. The boot process
stops and waits for me to decrypt /home, but otherwise there are no
complications.
>
> It's always very broken when I try - both guix reconfigure and sometimes the next boot process (!) hang.
>
next prev parent reply other threads:[~2016-04-24 18:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 21:05 GuixSD encrypted root? Danny Milosavljevic
2016-04-18 21:24 ` Danny Milosavljevic
2016-04-19 7:51 ` Danny Milosavljevic
2016-04-19 8:13 ` Danny Milosavljevic
2016-04-23 7:31 ` Danny Milosavljevic
2016-04-24 14:22 ` Ludovic Courtès
2016-04-24 16:04 ` Danny Milosavljevic
2016-04-24 18:51 ` Leo Famulari [this message]
2016-04-24 20:22 ` Ludovic Courtès
2016-04-24 21:23 ` Ludovic Courtès
2016-04-25 1:24 ` Danny Milosavljevic
2016-04-25 8:02 ` 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=20160424185134.GB7737@jasmine \
--to=leo@famulari.name \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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.