Path: utzoo!utgpu!cunews!bnrgate!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: gld@cunixb.cc.columbia.edu (Gary L Dare)
Newsgroups: comp.sys.sun
Subject: How to best provide X/OpenWindows to clients?
Keywords: Windows
Message-ID: <2730@brchh104.bnr.ca>
Date: 30 Apr 91 23:00:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 23
Approved: Sun-Spots@rice.edu
X-Original-Date: Sun, 28 Apr 1991 18:22:05 GMT
X-Sun-Spots-Digest: Volume 10, Issue 97, message 5
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

We are running a subnetwork with 3 SS 1's, each containing 2x104 MB of
disk space and thus able to locally handle OpenWindows, and 2 SS-1+'s with
only 1x104 MB on board for which we'll need access to X/OpenWin.

We have two alternatives:

1. Buy a 210 MB internal drive from, say, Box Hill Systems; install it on
   one of the SS-1+ and move its 104 MB drive to the other SS-1+.

2. Put a copy of /usr/openwin on our server (a 3/60) to handle the two
   SS-1+'s.  Access via network.  (This 3/60 could be upgraded to a SS-1+ in
   the near future, but traffic would still be an issue despite speed.)

Since we've only installed OpenWindows with the 4.1.1 release less than a
week ago and have no experience, we have no idea of what the traffic
pattern would be like if we went for solution #2.  If you use either of
the two alternatives we're looking at, could you please share some of your
experiences?  Thanks.

Gary L. Dare				Trumps Split! (p.1) - NY Post,
> gld@cunixD.cc.columbia.EDU		Tyson KO'd! (p.3)	Monday
> gld@cunixc.BITNET			Mandela Freed! (p.7) Feb.11/90