xgrass answer

Jim Westervelt westerve at zorro.cecer.army.mil
Mon Aug 17 16:53:53 EDT 1992

> From: Conn Copas <C.V.Copas at lut.ac.uk>
> More queries of the network variety, I am afraid.
> GRASS and its data lives on a HP-9000, and we are using Sparcs as display
> systems. For a variety of reasons, we would like to place xgrass on a Sparc
> for examination purposes, and then call the application through a remote shell.
> I have pulled the Sparc binaries, but the installation script which builds
> config.sh, and which validates the paths for GRASS and its data, cannot check
> directories on a remote machine. Questions :
> 1. To achieve the above, do we need to alter the source of xgrass, or can we
> get away with altering the installation script?

You should be able to alter the installation script. I would comment out
the places where the script does checking on paths and run it to reflect
your needs. For example, when it asks you for data, it looks for the
PERMANENT mapset. You should comment out this check.

> 2. Presuming the latter, will any other changes be required to config.sh
> other than path names? At the moment, we cannot even generate a config.sh in
> order to look at it.

Not that I can think of at the moment.

> --
> Loughborough University of Technology          tel : (0509)263171  ext 4164
> Computer-Human Interaction Research Centre     fax : (0509)610815
> Leicestershire  LE11 3TU           e-mail - (Janet):C.V.Copas at uk.ac.lut
> G Britain                 (Internet):C.V.Copas%lut.ac.uk at nsfnet-relay.ac.uk

Kurt Buehler,  Spatial Analysis and Systems Team
USACERL, P.O. Box 9005, Champaign, IL 61826-9005
1-800-USA-CERL x449,   kurt at zorro.cecer.army.mil

More information about the grass-dev mailing list