Answer the question
In order to leave comments, you need to log in
Shared folders errors in Fedora on VirtualBox?
It just so happens that I work under Windows, and the server is set to virtualbox, so that it only turns on when it is needed. I made a shared folder in which Apache looks, my virtual servers are there. It turned out something like a folder on wines C: \ web in which I work as an IDE, a folder / web in fedora, which is mounted as vboxsf and where Apache is configured.
Previously, I had a virtual server on centos and everything worked fine, including shared folders. Then I needed software, the packages for which were only in fedora, and I switched to it.
When I edit existing files in the project, everything works as expected. But if I delete / create / rename files, it's not clear what starts.
[[email protected] application]# ls -l<br/>
ls: cannot access _Environment.PHP: No such file or directory<br/>
total 28<br/>
-rwxrwx--- 1 root vboxsf 5325 Nov 21 03:01 Bootstrap.php<br/>
drwxrwx--- 1 root vboxsf 4096 Nov 21 02:52 configs<br/>
?????????? ? ? ? ? ? _Environment.php<br/>
-rwxrwx--- 1 root vboxsf 943 Nov 21 02:32 Environment.temp.php<br/>
drwxrwx--- 1 root vboxsf 4096 Nov 20 13:52 forms<br/>
-rwxrwx--- 1 root vboxsf 1458 Nov 21 13:04 Init.php<br/>
...<br/>
Answer the question
In order to leave comments, you need to log in
It was decided by deploying a server on CentOS 5.7 (kernel 2.6.18). Because Fedora uses newer versions of the kernel, I suspect that this is the gag. Thanks to all.
To tell the truth I am confused by access rights. The file will be rooted - there can always be problems with this. In general, it seems to me that when you change a file from Windows, something incomprehensible is going on with access rights.
Although, there is still a suspicion of a buggy file system.
Try to do the opposite: raise a samba server in the guest system, and connect to it in Windows. This should get rid of such glitches.
Another option: Apache looks at a local folder, into which rsync periodically copies files from a shared folder with a forced change in file ownership and rights.
It is very similar to the problem described here habrahabr.ru/qa/13272/
If I understand you correctly, then the internal VirtualBox SharedFolder is not a very reliable solution.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question