From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 33422@debbugs.gnu.org
Subject: bug#33422: /etc/passwd on GuixSD can end up containing default home directories
Date: Sun, 18 Nov 2018 17:44:48 -0500 [thread overview]
Message-ID: <20181118224448.GB25252@jasmine.lan> (raw)
In-Reply-To: <87wopam47t.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Sun, Nov 18, 2018 at 11:05:26PM +0100, Ludovic Courtès wrote:
> On IRC, fps reported this issue: their user account was declared like
> this:
>
> 26 (users (cons (user-account
> 27 (name "fps")
> 28 (comment "fps")
> 29 (group "users")
> 30 (supplementary-groups '("wheel" "netdev"
> 31 "audio" "video"))
> 32 (home-directory "/home/bob")) ;<--- notice “bob”!
>
> … yet /etc/passwd would refer to /home/fps for user “fps” (this is on a
> fresh GuixSD 0.15.0 install.)
>
> This in turn would prevent logging in as “fps” because /home/fps didn’t
> exist (meaning the ‘user-homes’ Shepherd service created /home/bob, not
> /home/fps.)
It slightly obscures a part of config.scm that is otherwise
straightforward, but I do this:
(home-directory (string-append "/home/" name))
... which would have avoided the issue. Maybe the value of
home-directory should be implicit when unspecified.
But, that is missing the point, which I think is that home directories
are not being handled in a consistent and unified way.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-18 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 22:05 bug#33422: /etc/passwd on GuixSD can end up containing default home directories Ludovic Courtès
2018-11-18 22:43 ` Ludovic Courtès
2018-11-18 22:44 ` Leo Famulari [this message]
2018-11-19 16:19 ` 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
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=20181118224448.GB25252@jasmine.lan \
--to=leo@famulari.name \
--cc=33422@debbugs.gnu.org \
--cc=ludo@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).