Custom Query (16363 matches)
Results (2335 - 2337 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2264 | fixed | Shared My Documents folder not writable by non-root Linux guest | ||
| Description |
Host: Windows XP Pro SP2, Guest: Xubuntu 8.04
Non-root users can't write to a shared Windows 'My Documents' folder
regardless of the 'uid' and 'gid'. Here's a transcript that
illustrates the problem (the shared folder named
$ ls -ld shared/ $ sudo mount -t vboxsf -o uid=srackham,gid=srackham mydocs shared
$ ls -ld shared/
$ touch shared/t $ sudo touch shared/t
$ ls shared/t Note how the user write bit on the mounted directory has been turned off so the user can't write but root can. The problem seems to be related to the special properties imbued in the 'My Documents' folder by Windows. Same applies to the Windows 'Shared Documents' folder (`C:\Documents and Settings\All Users\Documents`). |
|||
| #2265 | invalid | Directory names clash with shared folder names | ||
| Description |
If you have a folder in the same directory as your mount directory that has the same name as the VirtualBox shared folder name you will get a 'mounting failed with the error: Protocol error' error. Here's a transcript that illustrates the problem -- the first mount works fine, but the second (after creating a directory with the same name as the shared folder) fails:
$ ls -l $ sudo mount -t vboxsf -o uid=srackham,gid=srackham host shared/
$ mount -t vboxsf $ sudo umount shared/ $ mkdir host
$ ls -l
$ sudo mount -t vboxsf -o uid=srackham,gid=srackham host shared/ I don't know if this is the right place for unsolicited praise but a big thank you to everyone involved for this absolutely amazing piece of software. |
|||
| #2266 | fixed | need to recompile modules after each system restart | ||
| Description |
whenever I try to start the vboxSDL after a system restart, it complains that modules are not there
fixes it. Kernel: 2.6.27-3-generic Distro: Ubuntu 8.10 Alpha |
|||

