[Slackbuilds-users] tinc

[B. Watson]

On Mon, 7 Sep 2026, Ruben Schuller wrote:

> I think it would be nice to have a UID/GID assigned, tinc can setuid to
> another user. An own UID and GID are not a hard requirement, but would
> be nice for it IMO.

OK, UID/GID 403 are now tinc/tinc:

https://slackbuilds.org/uid_gid.txt

> Side question, there are some programs (postfix, dovecot) which are
> now included in Slackware. What is supposed to happen with the UID/GID
> assignments of those?

That's a good question. During the development cycle (when submissions
are closed and we're fixing everything for 16.0), we'll remove those
from our uid_gid.txt, and renumber anything there that collides with
the new Slackware's new users/groups.

The numbers can change as needed. Changing the number that a build
uses *does* mean that build needs to be rebuilt on any system where
it's installed (you can't keep using the old .tgz package)... but when
upgrading to a new Slackware version, you *really* want to rebuild all
your SBo stuff anyway.

> Eventually we'll run out of UIDs < 1000, we are already above 400.

Well... We started at 200 (with a couple of exceptions before that),
and we're now at 403. It took us 20 years to use up 204 numbers... and
we still have 597 available ones. So it shouldn't be a problem any
time soon.

Some of those older numbers are no longer needed, and could be
recycled. For instance, we no longer have "apache2" or "ntop" builds
on SBo, so numbers 207 and 212 could be reused. Looks like "halevt"
(224) could go, too.