From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v3] glep-0081: User and group management via dedicated packages
Date: Thu, 20 Jun 2019 10:15:08 -0400 [thread overview]
Message-ID: <b5c0115b-3d14-abfa-67c3-4cd07b19b02b@gentoo.org> (raw)
In-Reply-To: <8d6601e6-a295-778e-5dc8-5d9f01701c7d@gentoo.org>
On 6/20/19 9:53 AM, Brian Evans wrote:
>> +
>> +Following the acceptance of this GLEP, all new users and groups must
>> +be created via user/group packages as defined in this GLEP. The old
>> +method may still be used for existing users/groups, in existing
>> +packages.
>> +
>> +All new users and groups must have unique UIDs/GIDs assigned
>> +by developers. The developer adding them is responsible for checking
>> +for collisions.
>
> What significance will such numbers have when a daemon uses a new
> UID/GID and really doesn't care what it is? Why do we have to go
> through the effort of assigning fixed IDs at random?
>
People want this. Here's the thread from 2017:
https://archives.gentoo.org/gentoo-dev/message/2355afd4f5b72651e2ff47ea8b10c1fe
Selectively quoting:
* I might be not following correctly, but due to how filesystems/etc
work it is probably desirable to have consistent UID/GIDs as much as
reasonably possible. -rich0
* I don't think we need to have stable UIDs/GIDs in the "normal" case
of standalone users with a single Gentoo system at home. The people
who need predictable UIDs/GIDs are the "enterprise" users or the
home users who use things such as NFS. I work for a company that
uses Gentoo, we have a bunch of workarounds to make sure that UIDs
and GIDs are stable. -chutzpah
* I for one am more than willing to do whatever shell commands
necessary to make all my Gentoo installs agree on UIDs and get
[fixed UID proposal] now, but I realise most people are not.
-A. Wilcox
* YES! I think after [fixed UIDs] is finalized, it should be part of
the handbook installation as a default, but selectable. -james
* If the user does not exist then create it. Preferably use a pre-
assigned UID/GID so there is some consistency with most other
Gentoo things out there. -Alan McKinnon
This will make a lot of peoples' lives easier, and is very easy to do.
next prev parent reply other threads:[~2019-06-20 14:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 11:39 [gentoo-dev] [PATCH v3] glep-0081: User and group management via dedicated packages Michał Górny
2019-06-13 2:21 ` Michael Orlitzky
2019-06-13 5:37 ` Michał Górny
2019-06-20 13:53 ` Brian Evans
2019-06-20 14:15 ` Michael Orlitzky [this message]
2019-06-20 14:32 ` Michał Górny
2019-06-21 5:59 ` Andrew Savchenko
2019-06-21 7:18 ` David Seifert
2019-06-21 12:02 ` Andrew Savchenko
2019-06-21 12:18 ` David Seifert
2019-06-21 13:09 ` Michał Górny
2019-06-21 8:31 ` Jaco Kroon
2019-06-21 6:03 ` Andrew Savchenko
2019-06-22 17:34 ` Andrey Utkin
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=b5c0115b-3d14-abfa-67c3-4cd07b19b02b@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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