From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: GuixSD encrypted root? Date: Sun, 24 Apr 2016 18:04:25 +0200 Message-ID: <20160424180425.69bbe050@scratchpost.org> References: <20160418230558.11a1c86f@scratchpost.org> <8760v7gk87.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59611) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1auMWO-0003NL-Da for guix-devel@gnu.org; Sun, 24 Apr 2016 12:04:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1auMWJ-0000iz-B5 for guix-devel@gnu.org; Sun, 24 Apr 2016 12:04:32 -0400 In-Reply-To: <8760v7gk87.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?UTF-8?B?Q291cnTDqHM=?= Cc: guix-devel@gnu.org On Sun, 24 Apr 2016 16:22:16 +0200 ludo@gnu.org (Ludovic Court=C3=A8s) wrote: > Encrypted root file systems are not supported yet (some people managed > to work around the lack of support, but that=E2=80=99s somewhat fragile.) >=20 > Good news is we=E2=80=99re getting there! You can track progress at > . 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 "mo= unt? #t" it hangs. I'm now using a workaround where it's specified using "mount? #f" and I mou= nt it using a autorun script in my homedir (using "mount /x"). That works f= ine. You're using an encrypted home, right? Does it work for you? It's always very broken when I try - both guix reconfigure and sometimes th= e next boot process (!) hang.