unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 23220@debbugs.gnu.org, request@debbugs.gnu.org
Subject: bug#23220: Users' home is not created when initializing with a LUKS /home
Date: Tue, 5 Apr 2016 15:06:12 -0400	[thread overview]
Message-ID: <20160405190612.GA8332@jasmine> (raw)
In-Reply-To: <87pou4wgdk.fsf@gnu.org>

On Tue, Apr 05, 2016 at 11:32:07AM +0200, Ludovic Courtès wrote:
> merge 23220 21108
> thanks
> 
> Leo Famulari <leo@famulari.name> skribis:
> 
> > When initializing a new GuixSD system with /home on an encrypted
> > partition (as described in the manual), unprivileged users' home
> > directories are not created.
> >
> > I initialized the system with the encrypted partition locked and
> > unmounted, but <kyamashita> from #guix had the same problem even though
> > they had unlocked and mounted the partition.
> 
> Right, see <http://bugs.gnu.org/21108>.
> 
> > Of course, root can create the directories once the new system has
> > booted, but none of the configuration files are there, which means the
> > environment is not what is expected (my PATH was '/bin:/usr/bin').
> 
> In which case did you get this value of PATH?

I now realize that I had used, as root, `su leo`. When using `su -l leo`
I get the correct PATH. I'm not sure if getting the login shell would
have helped or not in that situation, but I think this part of my
complaint is invalid for now.

> > I worked around the problem by removing my user from the operating
> > system configuration, reconfiguring, putting my user back in the
> > configuration, and reconfiguring again.
> 
> Definitely not great.
> 
> Thanks,
> Ludo’.

      reply	other threads:[~2016-04-05 19:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05  0:48 bug#23220: Users' home is not created when initializing with a LUKS /home Leo Famulari
2016-04-05  9:32 ` Ludovic Courtès
2016-04-05 19:06   ` Leo Famulari [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160405190612.GA8332@jasmine \
    --to=leo@famulari.name \
    --cc=23220@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=request@debbugs.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).