In my Ubuntu VM, if I'm cd'd to a dir that's shared (a dir that's native to my host OS, and mounted on the Ubuntu VM through /media/psf), I cannot copy a read-only file from one location to another. If I give the file write permissions, I can copy it. This only seems to be an issue under Ubuntu, and is only an issue with Parallels.
Here's a repeatable test:
So when the permissions of "foo" don't contain the write bit, I can't copy correctly - the file gets there, but it is 0 bytes. But when foo is writable, I can copy it.
Is this a bug or some sort of setting problem? I'm running Build 9.0.24217 (Revision 979618; Tuesday, February 25, 2014)
Here's a repeatable test:
Code:
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ echo "test file" > foo && chmod a-w foo
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ mkdir bar
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ ls -l
[COLOR="#0000FF"]total 0
drwxr-xr-x 1 briank 68 May 22 16:52 bar/
-r--r--r-- 1 briank 10 May 22 16:52 foo[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ cat foo
[COLOR="#0000FF"]test file[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ cp foo bar
[COLOR="#FF0000"]cp: cannot create regular file `bar/foo': Cannot allocate memory[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ ls -l bar
[COLOR="#0000FF"]total 0
-r--r--r-- 1 briank 0 May 22 16:53 foo[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ cat bar/foo
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ rm -fv bar/foo
[COLOR="#0000FF"]removed `bar/foo'[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ chmod -v u+w foo
[COLOR="#0000FF"]mode of `foo' changed from 0444 (r--r--r--) to 0644 (rw-r--r--)[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ cp -v foo bar/
[COLOR="#0000FF"]`foo' -> `bar/foo'[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ cat bar/foo
[COLOR="#0000FF"]test file[/COLOR]
briank@Ubuntu-1204-x64-01:/media/psf/Home/test$ ls -l bar/foo
[COLOR="#0000FF"]-rw-r--r-- 1 briank 10 May 22 16:54 bar/foo[/COLOR]
So when the permissions of "foo" don't contain the write bit, I can't copy correctly - the file gets there, but it is 0 bytes. But when foo is writable, I can copy it.
Is this a bug or some sort of setting problem? I'm running Build 9.0.24217 (Revision 979618; Tuesday, February 25, 2014)