Path: utzoo!attcan!uunet!steinmetz!vdsvax!barnett From: barnett@vdsvax.steinmetz.ge.com (Bruce G. Barnett) Newsgroups: comp.sys.apollo Subject: Re: Apollo's NFS !! Message-ID: <4646@vdsvax.steinmetz.ge.com> Date: 18 Jun 88 11:08:52 GMT References: <3c80c931.4653@apollo.uucp> <292@sdrc.UUCP> <3c9567ba.d858@apollo.uucp> Reply-To: barnett@vdsvax.steinmetz.ge.com (Bruce G. Barnett) Organization: General Electric CRD, Schenectady, NY Lines: 36 In article <3c9567ba.d858@apollo.uucp> heinzl_c@apollo.UUCP (Carl Heinzl - Apollo Computer, Chelmsford, MA) writes: | Do you actually want to try and run a binary on an Apollo that |lives on a SUN, sorry - it just won't work. Try running a VAX binary on your |SUN and see what results you get there. Sorry for the flame but your statement shows real ignorance. I can't believe you said it. You are missing the point/advantage of NFS. Try running a Vax binary STORED on a sun ON a VAX. This works fine. Or run a Sun binary on a Sun that is on a Vax NFS server. It doesn't matter what type of architecture the NFS server is. The semantics are the same. We have an NFS server that is cheaper and faster than a Sun or VAX. It has more disk space and mutliple ethernet controllers so it can connect to several different segments. Great place for home directories. We can log onto a VAX, Sun, Encore, Convex, Alliant and perhaps HP or Tektronix, and have the same/single home directory. If we include $HOME/bin/`arch` in our search path, we can have binaries for EACH architecture in our SINGLE home directory. Except Apollo. It seems that only Apollo NFS servers can be transparently used for Apollo machines, while all of the other implementations (that I am aware of) can provide 'heterogeniality'. :-) -- Bruce G. Barnett uunet!steinmetz!barnett