From: James Cloos <cloos@jhcloos.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Alec Warner <antarus@gentoo.org>, gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: allow -1 for ACCT_USER_ID and ACCT_GROUP_ID in ::gentoo
Date: Mon, 29 Nov 2021 19:49:28 -0500 [thread overview]
Message-ID: <m37dcqeacn.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <w6gmtlntg26.fsf@kph.uni-mainz.de> (Ulrich Mueller's message of "Mon, 29 Nov 2021 11:24:49 +0100")
>>>>> "UM" == Ulrich Mueller <ulm@gentoo.org> writes:
UM> Also, why would one allocate UIDs in the 500..999 range (1000 is fine,
UM> actually)? Gentoo always had UID_MIN=1000 and SYS_UID_MAX=999.
why do you thing gentoo is everyone's first or only dist on their
network?
or even on any given box?
forcing existing boxen to change just because a new dist is added
is also unacceptable.
for me though, it would be enough if there is something i can add to
make.conf to ensure that the acct-user and acct-group builds avoid the
ranges i already use.
that may also work for others.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next prev parent reply other threads:[~2021-11-30 0:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 22:31 [gentoo-dev] rfc: allow -1 for ACCT_USER_ID and ACCT_GROUP_ID in ::gentoo William Hubbs
2021-11-28 23:26 ` Michael Orlitzky
2021-11-28 23:39 ` Sam James
2021-11-29 0:06 ` Michael Orlitzky
2021-11-29 5:05 ` Sam James
2021-11-29 13:25 ` Michael Orlitzky
2021-11-29 4:07 ` Michał Górny
2021-11-29 6:58 ` Alec Warner
2021-11-29 10:24 ` Ulrich Mueller
2021-11-30 0:49 ` James Cloos [this message]
2021-11-30 11:59 ` Ulrich Mueller
2021-11-30 21:08 ` James Cloos
2021-12-01 1:32 ` William Hubbs
2021-12-01 1:42 ` Michael Orlitzky
2021-12-01 6:16 ` Jaco Kroon
2021-12-01 6:45 ` Alec Warner
2021-12-01 7:51 ` Jaco Kroon
2021-12-01 12:22 ` Michael Orlitzky
2021-12-01 16:52 ` A Schenck
2021-11-30 0:55 ` Alec Warner
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=m37dcqeacn.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=antarus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ulm@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