On Fri, Jan 27, 2017 at 1:52 PM, Rich Freeman <ri...@gentoo.org> wrote:
> On Fri, Jan 27, 2017 at 12:54 PM, Michael Orlitzky <m...@gentoo.org> wrote:
> >
> > You don't really have to care what UID/GID is assigned, because each
> > user/group will only be created once and referenced by name (as $PN). By
> > default, we could pick the first available UID in most packages.
>
> 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. Things like NFS, chroots, containers, and so on
> can be a bit simpler if these are consistent, because they involve one
> system having visibility into a filesystem hosted on another, and
> usually in these cases the UID/GID is what is kept constant, not the
> name. (IMO UID/GID namespace is one of those areas where
> Linux/POSIX/etc has some weaknesses.)
>
> This doesn't really seem like a problem though. Just have a table
> somewhere (wiki?) to track who is using what UID/GID and encode those
> defaults into the ebuild that creates those users.--
>
There should be a division of the system managed UID space:
1) constant/consistent UID/GID for major things (portage, etc.)
2) variable space for per package groups/users that generally don't care
about consistency
A quick look at /etc/passwd shows that many of the system UIDs are
under 250 (portage) and a few scattered above 400. GIDs are similar,
though some are "fixed" and some are assigned going down from 999.
Some eclasses may need to be scrutinized for what behavior they are using.
--
G.Wolfe Woodbury
redwo...@gmail.com
