![]() 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. bat files, since they are indeed only "executable" on Windows. ![]() 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. 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. |