Xref: utzoo comp.unix.questions:6453 comp.unix.wizards:7614
Path: utzoo!mnetor!uunet!husc6!mit-eddie!minya!jc
From: jc@minya.UUCP (John Chambers)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: RFS vs. NFS
Message-ID: <555@minya.UUCP>
Date: 7 Apr 88 05:24:14 GMT
References: <326@ivory.SanDiego.NCR.COM> <275@ksr.UUCP> <7556@brl-smoke.ARPA> <10219@steinmetz.steinmetz.ge.com>
Distribution: na
Organization: home
Lines: 30

> Even under RFS, exec'ing a VAX executeable on a Sun doesn't work very
> well, so it can matter whether the file is local or remote.  RFS thus
> does not support full UNIX file system semantics according to the
> definition ekrell gave.

Hey, wait a minute, exec isn't really a file-system operation, except
in the trivial sense that everything is a file-system operation.  (After
all, /dev/mem exists, so a store operation changes a file...:-)  File
operations are things like open(), read(), .... 
 
> I have my doubts whether there is any adequate definition of UNIX file
> system semantics for a heterogeneous distributed environment.

Well, an interesting argument is that most Unix systems have file
systems made up of multiple disks and/or partitions mounted together.
The only thing new in a 'distributed' system is that the disks or
partitions are owned by different processors.  This is a rather
irrelevant matter as far as the file systems are concerned.  There
should be no difference between one computer that owns two disks
and two computers, each of which owns one disk.  The Unix model
works just fine in either case.

As for exec problems, you can easily get them in an isolated Unix
system.  Just install a cross-compiler.  For instance, port the
VAX C compiler to your Sun, and see how well the Sun execs the
output.  Lots of people do things like this.  The distributed case 
adds no extra complexity.

-- 
John Chambers <{adelie,ima,maynard,mit-eddie}!minya!{jc,root}> (617/484-6393)