Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!csn!ub!uhura.cc.rochester.edu!rochester!kodak!uupsi!sunic!infolog!infolog.se
From: rabbe@infolog.se (Rabbe Fogelholm)
Newsgroups: comp.sys.apollo
Subject: Stretching a Domain file system
Message-ID: <396@infolog.se>
Date: 14 Feb 91 23:37:55 GMT
Sender: rabbe@infolog.se
Organization: Infologics, Sollentuna, Sweden
Lines: 30

We are considering an extension of our Domain file system, but I wonder
if it is really feasible.

Today we have two disked and a few diskless nodes on a Token Ring.  One
of the disked nodes is also connected to a general-purpose local
Ethernet so that we can do ftp to Suns and the like.

First of all, would it be possible to set up another disked DN3000,
connect it to the Ethernet, and thus have it become a member of the
existing Domain file system? I. e., users on the Token Ring nodes
should be able to access the new disk by descending from the network
root (//) as usual.

Second, we would like to move the new DN3000 to another city and put
some suitable communications link between the DN3000 and our local
Ethernet. This should be invisible to the users, except that
slower-than-usual file accesses would be tolerable.

Any comments are welcome. If the idea seems sound, what kind of
communications link should we use?


(Some technical details: We run 9.7 today but plan for 10.3 soon. The
node that speaks Token Ring and Ethernet at the same time is a DN4500.
The rtsvc command currently returns the following:

    Controller        Net ID     Service offered
==================   ========   ====================
RING                        0   Own traffic only
ETH802.3_AT                 0   Own traffic only        )