LOGNAME, USER, and get-uid; NIS John Cowan (12 Aug 2019 16:30 UTC)
Re: LOGNAME, USER, and get-uid; NIS Lassi Kortela (12 Aug 2019 18:33 UTC)
Re: LOGNAME, USER, and get-uid; NIS hga@xxxxxx (12 Aug 2019 20:17 UTC)
Re: LOGNAME, USER, and get-uid; NIS Lassi Kortela (13 Aug 2019 09:13 UTC)
Re: LOGNAME, USER, and get-uid; NIS hga@xxxxxx (13 Aug 2019 11:26 UTC)
Re: LOGNAME, USER, and get-uid; NIS Lassi Kortela (13 Aug 2019 11:33 UTC)
Re: LOGNAME, USER, and get-uid; NIS hga@xxxxxx (13 Aug 2019 11:37 UTC)
Naming of "real" and "effective" ID procedures Lassi Kortela (14 Aug 2019 14:18 UTC)
(missing)
(missing)
Fwd: Naming of "real" and "effective" ID procedures John Cowan (14 Aug 2019 20:57 UTC)
Re: Fwd: Naming of "real" and "effective" ID procedures Lassi Kortela (14 Aug 2019 21:07 UTC)
Re: Naming of "real" and "effective" ID procedures hga@xxxxxx (14 Aug 2019 14:24 UTC)

Naming of "real" and "effective" ID procedures Lassi Kortela 14 Aug 2019 14:18 UTC

> Scsh calls the syscalls get-uid and get-effective-uid, but I think we
> should make it get-real-uid instead of get-uid for clarity's sake.
>
> The same applies to gids, of course.

In the current SRFI 170 draft, as well as scsh, these are named:

* user-(real-)uid
* user-(real-)uid
* user-effective-uid
* user-effective-gid

Should we use "get-" or "user-" for the prefix?

I always thought the term "real user ID" is misleading: it sounds like
the exact opposite of what it is. I would think the "real" ID is what's
really used to check permissions. "Effective" is not misleading, and
clarifies the meaning of "real", but that word is not used much anywhere
else.

These have the advantage that they are standard Unix terminology, but
IMHO it would be nice if some more appropriate words can be found. The
gist of it is identity vs permissions.