From: Craig Andrews <candrews@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, paolo.pedroni@iol.it
Subject: Re: [gentoo-dev] RFC: UID/GID assignment for deluge (545/545)
Date: Thu, 10 Oct 2019 07:30:10 -0400 [thread overview]
Message-ID: <c196358bf7510a5ba5913876c6ade7a7@gentoo.org> (raw)
In-Reply-To: <w6ga7a9gem4.fsf@kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
On 10.10.2019 04:59, Ulrich Mueller wrote:
>>>>>> On Wed, 09 Oct 2019, Craig Andrews wrote:
>
>> I would like to reserve UID/GID 545 for deluge (net-p2p/deluge).
>> We currently use dynamic UID/GIDs.
>
>> As far as I can tell, UID/GID 545 is free [1]
>> [1] https://api.gentoo.org/uid-gid.txt
>
> No, there's this line:
>
> - 500..999 500..999 reserved
I noticed that just after sending the email.
Thank you for pointing it out.
454/454 is free, let's go with that.
I've updated the PR as well.
Thanks,
~Craig
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-10-10 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 20:14 [gentoo-dev] RFC: UID/GID assignment for deluge (545/545) Craig Andrews
2019-10-10 8:59 ` Ulrich Mueller
2019-10-10 11:30 ` Craig Andrews [this message]
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=c196358bf7510a5ba5913876c6ade7a7@gentoo.org \
--to=candrews@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=paolo.pedroni@iol.it \
--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