On Thu, 14 May 2015, Robert LeBlanc wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Thu, May 14, 2015 at 10:08 AM, Sage Weil wrote: > > The above should have no impact on other distros where a fixed UID/GID > > is already set in the package. > > This sounds pretty reasonable to me! Perhaps there can be a 'default' > (but still opt-in) uid that is reserved and won't conflict going forward, > but may conflict with legacy environments? That at least minimizes > complexity/pain for fresh environments (which I suspect will > be the bulk of the install base)? > > > Since there is no guarantee, can we just default to the same UID/GID that wa > s received from Debian, or is there a known conflict in RH/Cent/SUSE/etc? The Fedora UID is 167. - fedora: 0-200 = fixed allocations - debian: 100-999 = dynamically allocated - suse: 100-499 = dyamically allocated system users The Debian UID is likely to be 64045. - fedora: undefined (1000-60000 = user accounts, nothing above that) - debian: 60000-64999 = reserved fixed uids, dynamically created - suse: undefined (1000-60000 = user accounts, nothing above that) I'm not sure which is less likely: colliding with a dynamically allocated system user (how many of those are there?) or a regular user (64045 is a very large uid). sage
