Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!csus.edu!ucdavis!csusac!unify!openlook!openlook-request
From: elling@eng.auburn.edu (Richard Elling)
Newsgroups: comp.windows.open-look
Subject: Re: Openwin or X11R4
Message-ID: <lp3sssw@openlook.Unify.Com>
Date: 1 Jun 91 15:26:25 GMT
Lines: 27

>	From: root@fstc-chville.army.mil (Operator)
>	
>	I don't like the /usr/openwin stuff...    I want includes to be in /usr/include/X11
>	(not /usr/openwin/include/X11) and I want binaries in /usr/bin (not /usr/openwin/bin)
>	etc...

This may be fine for a single machine.  Or even a small network.  But
for large networks with multiple servers it is an administration
nightmare.  Consider the advantages of having one mount point
(/usr/openwin) rather than 4 mount points (/usr/bin/X11, /usr/lib/X11,
/usr/include/X11, and /usr/man/X11).  With a single mount point,
there is only one filesystem to worry about mounting.  This is a 
good thing.

At Auburn, we use the automounter for mounting /vol/openwin.  On machines
with only 104Mb drives, /usr/openwin is a symbolic link to /vol/openwin.
On machines which have 207Mb drives, /usr/openwin has the goodies in
it.  This works out very well for network and server load balancing.
(We also mount X11 as /vol/X11 with symoblic links from /usr/bin/X11 etc.
which looks kinda funny since you have a link from /usr/bin/X11 to
/vol/X11/bin :-).  It works.  We have one mount point.  Everyone is
happy.

 Richard Elling                         Manager of Network Support
 Auburn University                      Engineering Administration
 relling@eng.auburn.edu     KB4HB [44.100.0.72]      (205)844-2280
    "I am not an animal!  I am a human bean!"  -- Peanutman