Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!hsdndev!husc6!purdue!haven!mimsy!chris From: chris@mimsy.umd.edu (Chris Torek) Newsgroups: comp.unix.admin Subject: Re: Single site-wide uid space Message-ID: <28039@mimsy.umd.edu> Date: 28 Nov 90 04:38:12 GMT References: <151@sleepy.UUCP> <1990Nov27.202949.29121@decuac.dec.com> Distribution: na Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 21 In article <1990Nov27.202949.29121@decuac.dec.com> mjr@hussar.dco.dec.com (Marcus J. Ranum) writes: >There's a utility called 'zap' (now something like unify_uids) >that was written at University of Maryland that is useful for doing the >mapping over to your unified user-id space once you've sorted out the >administration. It reads a map of uids, opens the superblock, and frobs >the inodes - fast, sure, and deadly - superblock death from above. Actually, `unify_uids' is the name of the whole package, which includes two programs called `mp' and `zap'. mp takes one `special' passwd file, N `regular' passwd files, and produces N new passwd files with unified uids and gids, along with N `map' files. zap applies one of these map files to the disk. The special file assigns particular IDs, such as `root = 0'; people not in the special file get IDs starting at 256 (or some other value of your choice). The package also includes a few programs for fixing up quota files and such. I wrote mp and zap, others wrote the others. -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 405 2750) Domain: chris@cs.umd.edu Path: uunet!mimsy!chris