Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 (Tek) 9/28/84 based on 9/17/84; site tekcrl.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!tekcrl!terryl
From: terryl@tekcrl.UUCP ()
Newsgroups: net.unix-wizards
Subject: re: contributed RFS
Message-ID: <457@tekcrl.UUCP>
Date: Sat, 18-Jan-86 17:42:40 EST
Article-I.D.: tekcrl.457
Posted: Sat Jan 18 17:42:40 1986
Date-Received: Mon, 20-Jan-86 05:41:59 EST
References: <1697@brl-tgr.ARPA>
Lines: 14

> I applaud the contribution of RFS (which should be given some
> other name to avoid confusion with AT&T's "RFS"), but I take
> issue with the claim that one does not want "find / -print"
> to cross over to remote file systems as it traverses the
> directory.  To the contrary, that is the whole point of RFS
> transparency.  There are some good examples (such as grepping
> for "rnj" in /n/*/etc/passwd) in a Bell Labs paper published
> one or two USENIXes ago.

     Ah, but probably not. Suppose two systems were linked by an RFS.
Then, a "find / -print" would go into an infinite loop traversing both
systems' file systems. Thus, you don't want find to cross over remote
file systems. This (and similar) arguments are the same for symbolic
links.