Custom Query (16363 matches)
Results (1570 - 1572 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1603 | fixed | mount vboxsf filesystems automatically => Fixed in 1.6.2 | ||
| Description |
Please add code like the following to /etc/init.d/vboxvfs inside a Linux guest. This will mount and umount the 'vboxsf' filesystems mentioned in /etc/fstab whenever the vboxvfs kernel module is inserted or removed. Thanks. --- vboxvfs-ORG 2008-05-22 17:24:00.000000000 +0200
+++ vboxvfs 2008-05-23 16:14:16.000000000 +0200
@@ -140,16 +140,21 @@
fail "modprobe $modname failed"
}
}
+ # Now we can mount vboxsf filesystems mentioned in /etc/fstab
+ mount -a -t vboxsf
+
succ_msg
return 0
}
stop() {
begin "Stopping VirtualBox Additions shared folder support ";
- if running; then
- rmmod $modname || fail "Cannot unload module $modname"
- fi
- succ_msg
+ # must umount vboxsf filesystems first
+ umount -a -t vboxsf &&
+ if running; then
+ rmmod $modname || fail "Cannot unload module $modname"
+ fi &&
+ succ_msg
return 0
}
|
|||
| #1604 | wontfix | Shared Folders: Windows NT4 SP6 guest on Windows XP SP3 host. | ||
| Description |
According to the changelog: Shared Folders: made them work for NT4 guests But it did not work. After a fresh install of NT4 + SP6 + guest additions, the mouse integration was OK. Display enhancement was OK, but Shared Folders was not. The usual "net use X: \vboxsvr\..." command reported "System Error 53." I clicked Control Panel -> Devices, and "VirtualBox Shared Folders" entry was there, but wasn't started. When I tried to start it, I saw this: The C:\Windows\System32\drivers\VBoxSFNT.sys device driver could not locate the entry point ExFreePoolWithTag in driver ntoskrnl.exe" |
|||
| #1605 | fixed | Crash when coming out of fullscreen mode on Mac OS X | ||
| Description |
See attached Apple crash report. This only happened once, and I don't know how to reproduce it. |
|||

