I installed Turnkey Linux on Virtualbox (LAMP flavor), on Windows 7 host. I wanted to do away with XAMPP and use some stuff which are not available on Windows. The guest is using a bridged network. The motive is to use Linux as the server.

So, I have a shared folder from Windows where I want to do my work. But on the browser, some directories are not showing. I checked the file permissions and they are okay. (755 for directories and 644 for files). I get a 500 error when I visit those directories.

I also turned off EnableSendfile but that's of no use as well. Could someone please help me?

I'm not clear on the layout of your virtual network, so I'm going to ask some followup questions:

What kind of shared folder is this? SMB/CIF or something else?

Why are you accessing the shared folder in a web browser?

Can the Linux VM ping the Windows machine?

Hello notKlaatu,
Thanks for the reply.
1. Plain windows folder. I don't how to find the type. In case you need more info, please let me know how to find that out.
2. I am using the Guest os as a server, which runs LAMP. I want to access it from windows, via browser.
3. Yes, VM can ping windows machine. It's not a network issue.
To add more info, I can view some of the files but not all. For example, 192.168.1.x/abcd is accessible but 192.168.1.x/abcd/xyz is not accessible. When I visit the latter, I get a 500. Also, the shared folder serves as documentroot for XAMPP on windows. (XAMPP is not running when VM runs). So, on windows, file permissions are correct.

I'm still not understanding the role of the shared folder...unless... is that Windows shared folder set as the webroot of Apache on the Linux vm? If so, that's certainly an interesting way to run a web server. Didn't even know that would work at all.

Anyway, assuming I'm correct about your set up, if the files in, for instance, abcd folder are not accessible, it sounds like Group or Other permissions could be wrong for abcd folder but correct for the webroot. What happens if you do an `ls -lh` on the webroot, from the Linux machine? what kinds of ownership:group and file permissions does that reveal?

And also, could you be persuaded to store those files on the Linux VM? I mean, in real life you would probably not have such a setup; serving files from a windows shared directory via a LAMP stack. You would just have the files on the web server. So is there a disadvantage to doing that now, in your VM? it seems more realistic to me, and it would probably make things easier. I am not familiar with Windows, but it would make me nervous to have to OS's fighting over management of the same set of files.

Yes, actually, Windows shared folder set as the webroot of Apache on the Linux vm. I wanted to unload a lot of stuff from windows. (The only reason I _have_ to use Windows is Photoshop.)
Here's the output:
codes is accessible but shops isn't.

In that you have it backwards; you ought to be running Linux on bare metal, hosting a Windows+Photoshop VM ;-)

I see no reason why shops/ should not be accessible compared to code/. It is odd that code/ shows up with a 0 total size, while shops is 4.0k

What if you place shops into code, just temporarily, to see what happens?

Another thing I'd try is to make a new directory, maybe `shop` and put the contents of shops into it, and see if it is available.

The glaring variable here is the Windows shared directory itself; unfortunately I know next to nothing how Windows does permissions, or how it shares files, or how its shared permissions are converted by other OS's. So unless someone else chimes in with more knowledge of that, the only angle I can really come from is from the Linux side, troubleshooting as if it was just a quirky edge case.

Personally I prefer to instead host the files on the server and access them from Windows (or better still like notKlaatu suggests!).

Have a look in the TKL Docs for options...

1 members found this post helpful.

Jeremy: It was never about uploading files. It's about not being able to access files. Thanks, anyway.

After trying different options and alternatives for days, I finally gave up on Turnkeylinux and switched to Arch. It works like charm. Sharing and accessing them never caused any problem. My main reason to switch was to try another type of distro -- different from Debian flavors. Feels good to see everything works perfectly. :-)

Thanks everyone!