From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 33422@debbugs.gnu.org
Subject: bug#33422: /etc/passwd on GuixSD can end up containing default home directories
Date: Mon, 19 Nov 2018 17:19:24 +0100 [thread overview]
Message-ID: <87muq5yr8z.fsf@gnu.org> (raw)
In-Reply-To: <20181118224448.GB25252@jasmine.lan> (Leo Famulari's message of "Sun, 18 Nov 2018 17:44:48 -0500")
Leo Famulari <leo@famulari.name> skribis:
> 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.
Exactly, that home directory was a typo, but the point of this bug is
that non-default home directories were not correctly handled.
Ludo’.
prev parent reply other threads:[~2018-11-19 16:20 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
2018-11-19 16:19 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87muq5yr8z.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33422@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.