Changes between Version 1 and Version 2 of Ticket #10085, comment 16

Ticket #10085, comment 16

-              v1
+              v2
 I think I have the right extradata set:
 {{{
 $ VBoxManage.exe getextradata UbuntuServer1 enumerate
+$ VBoxManage.exe getextradata UbuntuServer2 enumerate
 Key: VBoxInternal2/SharedFoldersEnableSymlinksCreate/z, Value: 1
 }}}
-And the file system is mounted ok:
-{{{
-$ mount
-z on /mnt/z type vboxsf (uid=1000,gid=1000,rw)
-}}}
 But I get the following when trying to do links:
 {{{
+reesd@ubuntu:/mnt/z/dgr$ ln a b
+reesd@ubuntu2:/media/sf_z$ touch a
+reesd@ubuntu2:/media/sf_z$ ln -s a b
+ln: failed to create symbolic link `b': Read-only file system
+reesd@ubuntu2:/media/sf_z$ ln a b
 ln: failed to create hard link `b' => `a': Operation not permitted
+reesd@ubuntu:/mnt/z/dgr$ ln -s a b
+ln: failed to create symbolic link `b': Protocol error
+reesd@ubuntu2:/media/sf_z$
 }}}
+Am I missing another trick? One thing I do see that is different is was getting "Read-only file system" for ln -s in 4.1.14, then I tried reverting back to 4.1.6 where I got "Protocol error", then I saw this fix so I went back to 4.1.14 but I am still getting "Protocol error".
+This is on a new install of 4.1.14 with a newly created Ubuntu vm. Am I missing another trick?
 Thanks,