Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!umich!terminator!pisa.citi.umich.edu!rees From: rees@pisa.citi.umich.edu (Jim Rees) Newsgroups: comp.sys.apollo Subject: Re: Unable to update /etc/passwd or registry. Not owner Message-ID: <50a91684.1bc5b@pisa.citi.umich.edu> Date: 29 Mar 91 21:22:47 GMT References: <738@bcstec.boeing.com> <508085fb.20b6d@apollo.HP.COM> <509e3823.20b6d@apollo.HP.COM> Sender: usenet@terminator.cc.umich.edu (usenet news) Reply-To: rees@citi.umich.edu (Jim Rees) Organization: University of Michigan IFS Project Lines: 18 In article , rpj@echo.canberra.edu.au (Ross Johnson) writes: 2 After a backup: Copy your /etc/{passwd,group} files to somewhere and then rename your /sys/registry directory and recreate your master registry. Use import_passwd to import the old saved passwd and group files... [WARNING: This will destroy your current UUID -> UID rgy mappings and require you to run syncids then comb your filesystem to re-chown lots of files and directories... We had to do this here once. The secret to making it work right is that you first have to "adopt" all your old person, group, and org ids into the new registry, so you can get the old uids as well as the old Unix ids. We got a list of all the entries in the old registry and edited this to make a script to re-create the entries in the new registry. This worked fine, and is easier than trying to track down and chown every file in the network!