![]() ![]() ![]() I checked that the folder is mounted I can see what is there using. I used the following command to mount the folder: Code: sudo mount -t vboxsf ShareDocuments /MacShare/. Code: drwx- 1 root root 1088 10:18 MacShare/. Re: File permissions of shared folder using virtualbox There aren't any option that help in System > Administration > Users and Groups I would like to change the owner of the directory from root to a user. Having said that, I don't know what the "right" solution to permissions mappings for Linux-on-Windows would be. However the file permissions for the shared folder are owned by root. If you manually mount the shared folder, then you need to use the relevant options on the mount command to set the folder with the right ownership (i.e. But I don't think it necessarily translates well when you've got a UNIX guest (i.e., Linux) running on Windows, given that NTFS has no concept of the execute *permission* and instead has its own idea of what it means for a file to be "executable" (where the file name must end in. For this, the guest systems must have a version of the VirtualBox. I agree that this permissions mapping approach probably makes sense, and is by design, for UNIX-on-UNIX hosts/guests - e.g., a Linux guest on a Mac OS X host, and vice versa. This command allows you to share folders on the host computer with guest operating systems. bat files, since they are indeed only "executable" on Windows. It is not necessary to change the permissions on the host system, just easily mount the shared folder for the normal user: sudo mount -t vboxsf folder share -o uid1000,gid1000 1000 is the default ID of the default user. After all, on the Linux guest, it's not like you're going to be able to run those. However, I'm not convinced how practical this is. exe, etc.) into executable files (+x) on the Linux guest. I understand why this is happening from a technical standpoint: basically, VBox's shared folders implementation is mapping what the Windows host considers to be "executable" files (.bat. The solution is easy, just mount the shared folder for the standard user: sudo mount -t vboxsf folder share -o uid1000,gid1000 1000 is the default ID of the default user. com files, and so on all show up with +x permissions on the Linux guest. Also, I've noticed that in 2.0.6, in a Linux guest running on a Windows host, the only files that _do_ show up as executable are those file types that are thought of as "executables" on Windows itself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |