Read-only GRASS ...

GRASS GRASS user
1

Peter?Halls??at?Sep?12??95?01?54?20?pm@bnr.ca>
content-type: text/plain; charset=US-ASCII
organization: University of Illinois at Urbana
mime-version: 1.0
reply-to: grassu-list@max.cecer.army.mil
newsgroups: info.grass.user
originator: daemon@ux1.cso.uiuc.edu

Is there any way of configuring grass to run from a read-only device?
I have a user with a non-networked workstation who wishes to run grass
off the CD ... but, obviously, grass/go/locks will then not be writable
... can this be worked around?

Thanks

Peter

Hello Peter,

        shure, there are possibilities to run GRASS form a ro-device. As
        example take my GRASS CD for Linux. A small runtime (approx 9-31Mb)
        has to installed on hard-disk, the rest remains on CD including
        the example databases.

Greetings

--------------------------------------------------------------------------
PPPPPH H | Peter Halls - University of York Computing Service -
P P H | GIS Advisor
P P H | Email: P.Halls@YORK.AC.UK
PPPPPJHHHHHH | Telephone: 01904 433806 FAX: 01904 433740
P J H | Smail: Computing Service,
P J H | University of York,
P J H | Heslington.
     J | YORK Y01 5DD
J J | England.
  JJJ This message has the status of a private & personal communication
--------------------------------------------------------------------------

2

Running GRASS 4.1.5 on an SGI Indy, IRIX 5.3.

Problem: g.access would change permissions appropriately, but access was
still denied to other users upon login.

I looked in the source code for libgis, and found that the check for
access (in file mapset_msc.c, line 91) looks at the *ownership* of the file,
rather than whether the current user can read (or perhaps write) to it.
I'd think this would prevent shared access to a mapset under any
circumstances.

Does anyone know why it would check the ownership of the directory rather
than the permissions?

-Eric