Index of /grass50/binary/solaris7intel

[ICO]NameLast modifiedSizeDescription

[PARENTDIR]Parent Directory  -  
[   ]COPYING2000-12-07 09:03 1.8K 
[TXT]README.html2007-12-10 22:29 2.6K 
[TXT]volunteer_wanted.txt2002-01-23 10:19 114  

This directory contains the Solaris7 (x86/Intel) binary code for
GRASS 5.0 beta X in gzipped tar format.  

Installation:

1. get the large (33 mb) file 
     grass5.0betaX_sol7i.tar.gz 
   which is the whole binary in a single file.  
2. get the installation script
     grass5install.sh

Then you only need to type the following after
you ftp it (example!):

  sh grass5install.sh grass5beta11_sol7i.tar.gz

This will create the necessary directories and
files for you to run GRASS. The default install path is
/usr/local/grass5/

To install in a different directory, specify it in the
command line:

  sh grass5install.sh grass5beta11_sol7i.tar.gz /opt/grass5


After installation start GRASS with

   grass5

The user interface is started within GRASS:
   tcltkgrass&

Note: If you are starting from beginning, you have 
to define your project area within GRASS before 
accessing the "tcltkgrass" user interface.

***************************************************
Paint driver notes:

1) If you have local paint devices, you will need 
move the appropriate files from 
$GISBASE/etc/paint/driver.uninst to the driver.sh 
in the same directory.  In addition, you must create 
a symbolic link (using the 'ln -s' command) from 
/dev/[paint driver name] to /dev/ttya or /dev/ttyb 
(or whichenver system device your print device is 
plugged in too).  For example, if you have a 
xerox4020 connected to /dev/ttya, use

        % cd $GISBASE/etc/paint/driver.uninst
        % mv xerox4020 ../driver.sh
        % ln -s /dev/ttya /dev/xerox4020
        % chmod 0666 /dev/xerox4020

You will have to be root to create the symbolic 
link in /dev.


2) If you have a paint device which exists on a 
remote host whose GISBASE is difference from the 
local GISBASE you will need to update the value 
of GISBASE in etc/paint/driver.rsh.


3) If you plan to use v.digspline and have any  
digitizers copy the file etc/digcap.sampl to 
etc/digcap and edit it accordingly.


USING THE BINARY VERSION
------------------------

The binary version does not come with any data or 
documentation (except for on-line man pages).  You will
need to acquire whatever documents you like from the GRASS 
Research Group FTP server.  Sample data is also available 
from the FTP site, or you may use data from previous
versions of GRASS if you have it available.

***********************************************

If you experience any problems, please email
us at:    

  grass@baylor.edu

Pleasehelp us and report eventually bugs:
Bug report form:
go here!

Get this file.