Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: xbps-triggers: make system-accounts behave in altroots
Date: Thu, 17 Sep 2020 03:15:04 +0200	[thread overview]
Message-ID: <20200917011504.SMeauxccTzJ7cTq_bVaL6JV1g3GlWvhkkq5RoDCj5A0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24812@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 933 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/24812#issuecomment-693749172

Comment:
The latest push attempts to better accommodate NIS/LDAP directories; if the canonical target prefix is `/`, the `--prefix` option is omitted from `useradd`, `groupadd` and `usermod`, which means these utilities should refuse to create accounts that conflict with entries in the remote directories. When the target prefix is something other than the system root, the `--prefix` argument is used, which ignores NIS/LDAP and creates accounts in the local databases for that root. I believe this to be the most sane option because any assumptions about remote directories for an alternate root are bound to be problematic, and if the user is aware of an intent to configure special NSS behavior in the altroot, leaving packages unconfigured until the full environment is ready seems appropriate.

  parent reply	other threads:[~2020-09-17  1:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 18:37 [PR PATCH] " ahesford
2020-09-15 19:32 ` ericonr
2020-09-17  1:04 ` [PR PATCH] [Updated] " ahesford
2020-09-17  1:15 ` ahesford [this message]
2020-09-17  5:18 ` the-maldridge
2020-09-18 13:44 ` [PR PATCH] [Updated] " ahesford
2020-09-18 14:00 ` [PR PATCH] [Closed]: " ahesford

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=20200917011504.SMeauxccTzJ7cTq_bVaL6JV1g3GlWvhkkq5RoDCj5A0@z \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).