Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!sdd.hp.com!apollo!apollo.hp.com!pato From: pato@apollo.HP.COM (Joe Pato) Newsgroups: comp.sys.apollo Subject: Re: Merging Registries and Unix Id's Message-ID: <4e1ef446.20b6d@apollo.HP.COM> Date: 20 Nov 90 14:44:00 GMT References: <9011191805.AA12801@richter.mit.edu> Sender: root@apollo.HP.COM Reply-To: pato@apollo.HP.COM (Joe Pato) Organization: Hewlett-Packard Apollo Division - Chelmsford, MA Lines: 32 In article <9011191805.AA12801@richter.mit.edu>, krowitz@RICHTER.MIT.EDU (David Krowitz) writes: |> I believe the ACL's are stored as text (ie. "joe.somegroup.someorg") |> rather than as UID/GID pairs, so that you will not have to re-acl the |> files ... however, you *will* have to change the ownership of all |> of his files, since the file's ownership (is* stored as a UID/GID |> pair. If all of joe's files are stored in one location, this is |> fairly easy (if time consuming). Just use the "chown -R" command |> on joe's directory. If the files are scattered about the disk, it |> gets much harder. ZI suspose you could use the "find" command to search |> the entire disk for files with a UID of 150 and pipe their names into |> "chown" to change them to joe's new UID (do this *prior* to merging |> the registries or you may find some of Ann's files by mistake!). |> |> |> -- David Krowitz |> |> krowitz@richter.mit.edu (18.83.0.109) |> krowitz%richter.mit.edu@eddie.mit.edu |> krowitz%richter.mit.edu@mitvma.bitnet |> (in order of decreasing preference) This is essentially all wrong. Refer to Jim Rees' response for a description of what really goes in an acl and the "inode" equivalent (64-bit UIDs) and how to "fix" the unix id "hint" using /etc/syncids. David's advice is close to what you would have to do on a conventional UNIX file system - and it should NOT be followed on a Domain/OS file system. -- Joe Pato Cooperative Object Computing Operation Hewlett-Packard Company pato@apollo.hp.com