On Tue, 29 Nov 2016 18:13:29 -0500 "William L. Thomson Jr." <wlt...@o-sinc.com> wrote:
> On Wednesday, November 30, 2016 12:49:44 AM EST Alan McKinnon wrote: > > > > Why would you end up with duplicated UIDs and GIDs? The only real ways > > that can happen is > > - ebuild "edits" passwd and group directly using echo/sed and the like. > > - ebuild runs useradd|groupadd specifying the uid/gid as arguments > > I think you mean enewgroup and enewuser FYI, enew* functions handle UID/GID collisions gracefully, and just fallback to using next free UID/GID. > > Who cares what the uid/gid is? There's a range of about 950 to chose > > from. The way to ensure a filesystem object has the correct owner and > > group is by using chown/chgrp. > > See above, any administrator moving files between systems, restoring backups, > etc. > > Say you do a fresh install. What if all your UID/GID differ from your backup? > HUGE MESS!!!! 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. 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. 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. Furthermore, I should add that neither repeating the same argument thrice, nor adding some random caps and exclamations marks, won't make it any more valid. -- Best regards, Michał Górny <http://dev.gentoo.org/~mgorny/>
pgp7QoTXwfj8C.pgp
Description: OpenPGP digital signature
