[GRASS-user] [SOLVED] was Moving GISBASE box2box

[Cassiel]

2009/4/9 Moritz Lennert <mlennert at club.worldonline.be>

> On 09/04/09 12:24, Cassiel wrote:
>
>>
>>
>> 2009/4/9 Moritz Lennert <mlennert at club.worldonline.be <mailto:
>> mlennert at club.worldonline.be>>
>>
>>
>>    On 09/04/09 11:17, Cassiel wrote:
>>
>>        Hi,
>>
>>        each and every location dir belong to my user, which in turn is the
>>        same on every machine I am allowed to log in.
>>
>>        WINDOWS file are there with the same permissions
>>
>>        ... I can't figure out why this worked in past and now it seems
>>        broken
>>
>>        Other hints?
>>
>>
>>    In your first post you wrote:
>>
>>        At grass startup, once I select the gisbase dir, every mapset I try
>>        to access results in this error message "this is not a valid
>>        mapset".
>>
>>
>>    If this is the exact error message, then the only place I can find
>>    this in the source code is in lib/init/gis_set.tcl as a result of a
>>    failed CheckMapset, which is just:
>>
>>    proc CheckMapset {} {
>>           global database location mapset
>>
>>           if { $mapset == "" } { return 0; }
>>
>>           if { [file exists "$database/$location/$mapset/WIND"] } {
>>                   return 1
>>           }
>>           return 0
>>    }
>>
>>    So, it fails either if the mapset variable is empty, or if there is
>>    no WIND file in the mapset (or at least if file exists returns 0 -
>>    don't know in which cases it does this).
>>
>>    Are you sure that the gis-database is correclty defined ?
>>    Have you tried accessing the mapsets directly on the command line
>>    without going through the GUI ?
>>
>>    Moritz
>>
>>
>> Hi,
>>
>> I finally solved looking the location dirs side by side with mc.
>>
>> Moving from the old machine on the removable drive and from the latter to
>> the newer machine changed the case of the VAR and WIND file inside the
>> location dirs. What sounds very strange to me is why only those two files
>> plus a MYNAME one...
>>
>
> Did you have other upper-case names which remained upper-case ?
> Maybe an issue with a fat filesystem on the removable drive ?
>
> Moritz
>

Yes, DEFAULT_WIND, PROJ_INFO, PROJ_UNITS remained upper case while (I
checked the rest of locations) all wind and var files were converted to
lower case.

The removable drive is fat32 and file permissions are all 755 on the older
linux box...

r
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-user/attachments/20090409/6d775cd2/attachment.html