From: Ulrich Mueller <ulm@gentoo.org>
To: Luke Dashjr <luke@dashjr.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: GID/UID assignment for Bitcoin services (493)
Date: Wed, 25 Sep 2019 10:05:18 +0200 [thread overview]
Message-ID: <w6gmuesn6m9.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <201909250355.43146.luke@dashjr.org> (Luke Dashjr's message of "Wed, 25 Sep 2019 03:55:42 +0000")
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
>>>>> On Wed, 25 Sep 2019, Luke Dashjr wrote:
> There is no standard UID number for this purpose, and other distros
> don't appear to have it assigned in their lists either. 493 was just
> the highest one <500 available.
Archlinux uses 492 and 493 for packages that we also have, so we skipped
these two, for the time being.
AFAICS 483 would be the next one available.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2019-09-25 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 3:55 [gentoo-dev] RFC: GID/UID assignment for Bitcoin services (493) Luke Dashjr
2019-09-25 8:05 ` Ulrich Mueller [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=w6gmuesn6m9.fsf@kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=luke@dashjr.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