Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!bellcore!faline!ulysses!sfmag!mjp
From: mjp@sfmag.UUCP (M.J.Purdome)
Newsgroups: comp.sys.att
Subject: Re: Root equivalence over RFS
Message-ID: <1127@sfmag.UUCP>
Date: Mon, 7-Sep-87 19:14:48 EDT
Article-I.D.: sfmag.1127
Posted: Mon Sep  7 19:14:48 1987
Date-Received: Wed, 9-Sep-87 07:22:54 EDT
References: <7211@e.ms.uky.edu> <6406@brl-smoke.ARPA>
Organization: AT&T Information Systems, Summit, NJ
Lines: 25

> In article <7211@e.ms.uky.edu> eric@ms.uky.edu (Eric Herrin) writes:
> >My solution was to hack the DU module so it allows root equivalence.
> 
> I thought you could achieve this with existing facilities (e.g. the
> rules files used by idload(1M))?  What am I missing?

Right.  The ID mapping rules files used by idload allow all sorts of 
mapping between users.  I think the typical default configuration has
files that say something like
	global	
	default transparent
	exclude 0-99
which allows all users to be mapped except 0-99 (the administrative
logins), which become MAXUID+1.  If you delete the last line, all users,
including root, are mapped transparently.

Check the rules files, located in /usr/nserve/auth.info/?id.rules, 
the man page for idload(1M), or the _Administrator's Guide_, which has an
RFS tutorial.
-- 

    Mark Purdome      AT&T UNIX System Development Laboratory
                      190 River Road A-130, Summit, NJ  07901
                      {ihnp4,allegra}!attunix!mjp
    disclaimer: these statements do not represent AT&T policies or opinions