On Aug 16, 2019, at 01:31, Gerben Wierda wrote:
> So, what I need is build macports from source if I want to change this
> behaviour?
Yes... the MIN_USABLE_UID / MIN_USABLE_GID configure script variables are
referenced in src/pextlib1.0/Pextlib.c, which gets compiled into a library,
which
> On 16 Aug 2019, at 01:13, Ryan Schmidt wrote:
>
>
>
> On Aug 14, 2019, at 17:49, Gerben Wierda wrote:
>
>> If this is a bug, I suggest using 600, not 500 for the fix.100 local users
>> on a mac seems adequate (like 640kB…) and server starts at 1025, so ample
>> room for services.
>
> As
On Aug 14, 2019, at 17:49, Gerben Wierda wrote:
> If this is a bug, I suggest using 600, not 500 for the fix.100 local users on
> a mac seems adequate (like 640kB…) and server starts at 1025, so ample room
> for services.
As I said, I believe our intention was to use the same range of UIDs
If this is a bug, I suggest using 600, not 500 for the fix.100 local users on a
mac seems adequate (like 640kB…) and server starts at 1025, so ample room for
services.
I’d rather not create my own macports port, it is complex enough as it is.
Gerben Wierda
Chess and the Art of Enterprise
On Aug 14, 2019, at 16:36, Gerben Wierda wrote:
> If you create local userson macOS, it starts with uid 501 and then goes up.
> (for network users it always (still?) started with 1025 and then goes up.
>
> MacPorts, when it creates users, starts with 500 and then goes up.
I noticed that
If you create local userson macOS, it starts with uid 501 and then goes up.
(for network users it always (still?) started with 1025 and then goes up.
MacPorts, when it creates users, starts with 500 and then goes up.
So, depending on the order of creation, the same user has different uid (same
