VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (907 - 909 of 16363)

Ticket Resolution Summary Owner Reporter
#929 fixed Upgrading Win XP guest additions doesn't upgrade VBoxMRXNP.dll Rune Kock
Description

I used to have VBox 1.4, and then upgraded to 1.5.2. I started my Win XP guest, and asked it to install the guest additions again. Seemed to go fine, but shared folders didn't work. It turns out that the VBoxMRXNP.dll file wasn't upgraded.

I attach an install log from installing the new guest additions.

#930 fixed Crashed unexpectedly at restart Paolo Marini
Description

I created and used for a couple of times a test VM with just Firefox 3 Beta 1 installed on top of a patched Windows XP SP2. Today I created and added a second (virtual) hard disk and also changed the default NAT to be a host network interface and moved the NAT as the second interface. Now each time that I start the VM it crashed after a few seconds during boot, and even if I switch back to previous settings or create a new machine with the same main (virtual) disk it does the same... Thanks

#931 fixed The mode option mentioned in the user manual is missing from vboxsf Paul Siu
Description

At the end of section 4.4, the manual states "The generic mount options (documented in the mount manual page) apply also.Especially useful are the options uid, gid and mode, as they allow access by normal users (in read/write mode, depending on the settings) even if root has mounted the filesystem." However, when you attempt to mount using the "mode" option, it tells you that "mode" is not a valid option.

Side effects Without the ability to change mode, a shared directory is always mounted with the permission of rwxr-xr-x. Basically, the owner can read, write and execute, while group and others can only read and execute.

When you mount a vboxsf volume, mount will mounted it as a owner of root and a group of root by default. As a result, no one except root will have write access. On distros like Ubuntu, you are normally not allowed to be root, so no one can write to the drive.

To get around the issue, you can mount it using the uid option so you are the owner of the shared folder, but that means any share folder will only have access by one person.

In addition, the gid option in mount is essentially useless since you cannot change mode. Your group will always only have read-execute access to the shared folder.

I propose that mode be an option of vboxsf as stated in the user manual.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy