Yes, mv works with the test dbf and the dbf from v.in.ascii. I can move both
and they have the -rw-rw-rw- permissions. Can I solve the problem when I
move the *.dbf into the /home/.../topo/dbf/ folder manually with the mv
command?
Jan
-----Ursprüngliche Nachricht-----
Von: Moritz Lennert [mailto:mlennert@club.worldonline.be]
Gesendet: Dienstag, 15. Februar 2005 16:04
An: Jan Bartholdy
Betreff: Re: AW: [GRASSLIST:5781] Re: v.in.ascii, grass6.0 binary version
for cygwinOn Tue, February 15, 2005 15:44, Jan Bartholdy said:
> Thanks, Moritz. I had no problems to create the test.dbf with touch
test.dbf
> and the permissions are as follow: the /.tmp/Jan1 directory drwxr-xr-x+
and
> the test.dbf -rw-rw-rw- and I am the owner of the files...try doing the mv command described below... can you do that ? What are the
permissions and owner settings of the 5164.dbf ?Moritz
>
> ??
>
>> -----Ursprüngliche Nachricht-----
>> Von: owner-GRASSLIST@baylor.edu [mailto:owner-GRASSLIST@baylor.edu] Im
>> Auftrag von Moritz Lennert
>> Gesendet: Dienstag, 15. Februar 2005 14:55
>> An: Jan Bartholdy
>> Cc: English Grasslist
>> Betreff: [GRASSLIST:5781] Re: v.in.ascii, grass6.0 binary version for
>> cygwin
>>
>> On Tue, February 15, 2005 14:46, Jan Bartholdy said:
>> > Dear All,
>> > I have imported an ASCII table (tab's as field separators) into grass
>> > without problems using v.in.ascii input= output= without any
arguments
>> > (using arguments like columns="...", the problem is the same).
>> > All coordinates are imported and the correct number of colums and
their
>> type
>> > was recognized. After that, an error message occur: mv: cannot move
>> > /home../../.tmp/Jan1/5164.dbf to /home/.../topo/dbf/species_1.dbf:
>> > permission denied.
>> > After that, the module building topology etc.
>> >
>> > The 5164.dbf file remains in the .temp/Jan1 folder.
>> >
>> > With d.vect, I can display the points, but the labels are not
present.
>> > Db.colums gives an error : DBMI-DBF driver error: Table species_1
>> does'nt
>> > exist
>> >
>>
>> This looks like you do not have permission to write to the second
>> directory.
>> Try to go to the directory and do a "touch test.dbf" or could you do an
ls
>> -ld
>> on the second directory (and its parents) to show the permission
settings
>> ?
>>
>> Moritz
>
>
> ____________
> Virus checked by G DATA AntiVirusKit
> Version: AVK 15.0.2975 from 09.02.2005
>
>
____________
Virus checked by G DATA AntiVirusKit
Version: AVK 15.0.2975 from 09.02.2005