On Wednesday, November 30, 2016 8:54:42 AM EST Michał Górny wrote: > On Tue, 29 Nov 2016 18:13:29 -0500 > > "William L. Thomson Jr." <wlt...@o-sinc.com> wrote: >> > > I think you mean enewgroup and enewuser > > FYI, enew* functions handle UID/GID collisions gracefully, and just > fallback to using next free UID/GID.
I would disagree with such and some what makes specifying a UID/GID pointless if it simply will use the next available in the event of a collision. Which available likely comes from the default allocation range > 500 or 1000. If system and was intended to be below that, not really ideal. > I'm not sure if you're aware that but most of tools doing backups > actually use usernames/group names. So does new enough tar. So does > ssh. tar can map users and groups via file, but why waste the time with such? > Are you specifically using some obsolete or braindead tools to prove > your point? If you don't sync UIDs/GIDs properly, then you don't use > them when moving data across systems. Simple as that. I start with consistent base images and have the same uid/gid all on all so syncing is not needed. Nor do I need to deal with it during restoration. > The only thing that you could worry about then are missing users/groups > on the target system. But then, so far none of your talk solved that > problem. A problem that should not exist with a proper setup. -- William L. Thomson Jr.
signature.asc
Description: This is a digitally signed message part.
