From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Audio/sound (ALSA) in guix environment --container
Date: Wed, 27 Mar 2019 16:03:57 +0100 [thread overview]
Message-ID: <87bm1wcqaq.fsf@gnu.org> (raw)
In-Reply-To: <87y350376g.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 27 Mar 2019 12:10:03 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Pierre Neidhardt <mail@ambrevar.xyz> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> I suppose /etc/pam.d/ also needs to be in the container.
>>
>> Tried it, same error.
>>
>>>> What about defaulting to 1000? It's rather common, so I guess that
>>>> would be anonymous enough and "just work".
>>>
>>> Would it make sense to map the current user’s UID into the container
>>> instead of using a fixed UID?
>>
>> We have a "--user" option, so we could use the current user's UID when
>> --user is not specified, 1000 otherwise.
>> Or better: add a --uid CLI option.
>
> I can see confusion coming from the existence of both “--user” and
> “--uid”. Maybe “--user” could take an optional argument, with the
> default being the current user. Without “--user” we’d use UID 1000.
Currently, without --user, we keep the current user’s name. So it would
actually be consistent to inherit its UID as well. And with ‘--user’,
we’d use the given user name and UID 1000. (Essentially what Pierre
proposed above.)
Thoughts? :-)
Ludo’.
next prev parent reply other threads:[~2019-03-27 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 19:50 Audio/sound (ALSA) in guix environment --container Pierre Neidhardt
2019-03-26 17:15 ` Ludovic Courtès
2019-03-26 17:21 ` Ricardo Wurmus
2019-03-27 10:11 ` Pierre Neidhardt
2019-03-27 10:38 ` Ricardo Wurmus
2019-03-27 11:05 ` Pierre Neidhardt
2019-03-27 11:10 ` Ricardo Wurmus
2019-03-27 15:03 ` Ludovic Courtès [this message]
2019-03-27 15:14 ` Ricardo Wurmus
2019-04-02 16:17 ` Ludovic Courtès
2019-04-03 8:01 ` Pierre Neidhardt
2019-03-27 11:14 ` 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=87bm1wcqaq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.