<br><br><div class="gmail_quote">On Mon, Oct 20, 2008 at 9:16 PM, Glynn Clements <span dir="ltr"><<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
Matt B wrote:<br>
<br>
> I'm using Grass on ubuntu 8.04. Weird thing is that unless I run it "sudo<br>
> grass" I get a bunch of errors (and it's unusable) related to grass not<br>
> having the correct permissions to write to where I keep the data (ie the<br>
> users home directory). It's not a show stoppper at the moment and only<br>
> slightly annoying. I'm not sure why this is but I have some ideas to hunt<br>
> down when I get time. I used the standard ubuntu install and assume its<br>
> something to do with the ubuntu setup script.<br>
<br>
</div>Note that GRASS won't let you select a mapset as the current mapset<br>
(where new files are stored) unless you own it. Write permission isn't<br>
sufficient.<br>
<br>
If you are creating a location which is to be shared by multiple<br>
users, you either need to create a mapset directory for each user,<br>
owned by the user, or grant all such users write permission on the<br>
location directory so that they can create their own mapset directory<br>
(which they will own).<br>
<font color="#888888"><br>
--<br>
Glynn Clements <<a href="mailto:glynn@gclements.plus.com">glynn@gclements.plus.com</a>></font></blockquote><div> </div></div>Thanks for the heads up on this Glynn, my problem is that I'm on a dual boot system and I'm storing mapsets/data on an NTFS drive. It's being automatically mounted with the owner set as root and read/write permission for everyone. If I put the data on the ext3 filesystem, it works. I'll mess around with fstab and mount the data drive as the appropriate user. Having said that.... it does seem to me that this sort of check is doubling up. File permissions are usually run by the file system/OS. While having a sanity check for "read/write" access is a good idea, checking for ownership seems a little over the top. <insert newby user disclaimer here>.<br>
<br>Thanks<br>Matt<br>