[racket] DrRacket Can Not Read Shared File System Under VMWare Fusion
Operating System(s): Ubuntu 10.04 running as a guest on VMWare Fusion
3.1.0 on Mac OS X 10.6.4
Hardware: MacBook Pro, 2.66 GHz Intel Core i7, 4GB memory
Running DrRacket from the prebuilt Ubuntu package available at
www.racket-lang.org
VMWare has a feature by which the guest OS (Ubuntu 10.04) may read files
from the host (Mac OS X 10.6.4) file system. When asked to open a file
in the shared file system (known as /mnt/hgfs/... from the perspective
of Ubuntu) DrRacket issues the following error:
file-or-directory-permissions: file or directory not found:
"/mnt/hgfs/mgorlick/Projects/accomplice/compiler/dissect.ss"
=== context ===
/usr/plt/racket3m/collects/framework/private/text.rkt:1836:4:
after-load-file method in ...ork/private/text.rkt:1804:2
/usr/plt/racket3m/collects/framework/private/text.rkt:358:4:
after-load-file method in ...ork/private/text.rkt:87:2
/usr/plt/racket3m/collects/drracket/private/unit.rkt:2230:8:
change-to-file method in ...ket/private/unit.rkt:1419:6
/usr/plt/racket3m/collects/drracket/private/unit.rkt:4678:8
/usr/plt/racket3m/collects/racket/contract/private/arrow.rkt:1434:3
/usr/plt/racket3m/collects/racket/contract/private/arrow.rkt:1434:3
/usr/plt/racket3m/collects/mred/private/mrmenu.rkt:244:17: command
method in basic-selectable-menu-item%
/usr/plt/racket3m/collects/racket/private/more-scheme.rkt:158:2:
call-with-break-parameterization
/usr/plt/racket3m/collects/racket/private/more-scheme.rkt:274:2:
call-with-exception-handler
It is interesting to note that the command line tools (such as racket)
as well as all of the standard Ubuntu utilities and applications (for
example, any of the many text editors, be they terminal-based editors or
GUI-based) read/write the files in question flawlessly. [Note: For those
familiar with Linux under VMWare Fusion there was a bug in VMWare Fusion
versions 1.x and 2.x regarding user and group ids that prevented guest
applications from reading the shared host files. That bug has been fixed
in versions 3.x of VMWare Fusion and is not the issue at fault here.]
If anyone has questions or can offer assistance please email me directly
as I do not read this mailing list regularly. Thanks in advance.