On 06/08/2018 12:01 PM, Carlos E. R. wrote:
That's my understanding as well.
Unless the installer could be told to import an external /etc/passwd and /etc/group files.
That's not correct for system UID/GID's. I agree for user UID/GID combos. User UID/GIDs are not necessarily semi-random, they generally start at 1000 on a first-come, first-served basis (some distros start the user range at 500). While the system UID/GIDs are distro/implementation defined to some extent -- they should always be consistent within a distribution between releases -- otherwise, that would break configs and applications. Requiring no end of user-interaction required to re-map the system UID/GID's to work with existing data on each new update. While there can/will always be new UID/GID's introduced by upstream changes (e.g. cups is a good recent example), as a rule, the distro should not remap, or semi-randomize system UID/GID between releases. Now TW is somewhat a different animal than Leap, so I suspect what happened is that as TW begin development, there wasn't any effort made to map the opensuse/Leap system UID/GID values and the devs just starting building somewhat of a new distro to become TW. By the time this issue became apparent, it was probably a bit too late to coordinate them again without a whole lot of effort. (they would be running into the same problems the original poster here did) -- David C. Rankin, J.D.,P.E.