Page 1 of 1

Debian 32 shared folder in Win 7 x64

Posted: 23. Apr 2010, 14:22
by Takayuki
I am having trouble sharing files between Debian 5.0.4 i38 and win 7. Has anyone successfully shared a folder between the two and if so how did you do it?

Re: Debian 32 shared folder in Win 7 x64

Posted: 23. Apr 2010, 16:27
by dmcgraw
You really need to give more information.

What version of VB are you running?
Have you installed the Guest Additions?
What have you tried and what was the result?
Exact error messages?

Re: Debian 32 shared folder in Win 7 x64

Posted: 24. Apr 2010, 02:16
by Takayuki
dmcgraw wrote:You really need to give more information.

What version of VB are you running?
Have you installed the Guest Additions?
What have you tried and what was the result?
Exact error messages?
ver 3.1.6.r59338
Guest additions are installed as I can now adjust screen resolution in it
In order to share a folder in Win 7, I went to the virtual machine settings and set the folder that I want to share between the two.
When following this https://help.ubuntu.com/community/Virtu ... redFolders , I get to the point where I run "mount -t vboxsf share mountpoint" or "mount -t vboxfs share mountpoint" in the debian terminal and get the error "mount point mountpoint does not exist"
You might ask why am using Ubuntu instructions to share in Debian, thats because I have searched the net for Debian tutorial and cant find any.

Re: Debian 32 shared folder in Win 7 x64

Posted: 24. Apr 2010, 02:51
by Perryg
I get to the point where I run "mount -t vboxsf share mountpoint" or "mount -t vboxfs share mountpoint" in the debian terminal and get the error "mount point mountpoint does not exist"
See Chapter 4.7. Folder sharing in your VirtualBox users guide.

You need to create a mount point in the Linux guest as SU
  • Example: mkdir /mnt/myshare
then you run the mount statement.
mount -t vboxsf <share name> <mount point>
  • Example: mount -t vboxsf share /mnt/myshare

Re: Debian 32 shared folder in Win 7 x64

Posted: 24. Apr 2010, 14:10
by Takayuki
Perryg wrote:
I get to the point where I run "mount -t vboxsf share mountpoint" or "mount -t vboxfs share mountpoint" in the debian terminal and get the error "mount point mountpoint does not exist"
See Chapter 4.7. Folder sharing in your VirtualBox users guide.

You need to create a mount point in the Linux guest as SU
  • Example: mkdir /mnt/myshare
then you run the mount statement.
mount -t vboxsf <share name> <mount point>
  • Example: mount -t vboxsf share /mnt/myshare
After running mkdir /mnt/myshare

error: mkdir: cannot create directory '/' File exists
mkdir: cannot create directory ' mnt/myshare' : No such file or directory

After runnning mount -t vboxsf share /mnt/myshare

It gives me details on how mountpoint is used with various switches


Now what is the difference between myshare and share terms used here?

Re: Debian 32 shared folder in Win 7 x64

Posted: 24. Apr 2010, 14:53
by Perryg
/mnt/myshare
no spaces and it must be complete with the / at the front of the path.
As I said it is an example. You make a mount point where you need to.

Re: Debian 32 shared folder in Win 7 x64

Posted: 25. Apr 2010, 21:40
by Takayuki
Perryg wrote:/mnt/myshare
no spaces and it must be complete with the / at the front of the path.
As I said it is an example. You make a mount point where you need to.
Let me get this right. If share is the name of the folder I intend to use between the guest/host what is myshare?

Re: Debian 32 shared folder in Win 7 x64

Posted: 25. Apr 2010, 21:47
by Perryg
If share is the name you want to use then it would be /mnt/share
These are only examples. When you see something between <> that means to replace it with the exact name that you are using.
<share name> would then = share if that is what you want to use.
<mount point> = /mnt/share or /home/<your user name>/share If your user name was matt then it would be /home/matt/share.

Re: Debian 32 shared folder in Win 7 x64

Posted: 28. Apr 2010, 00:47
by Takayuki
Finally got it working!

The trouble was with damaged Linux headerfiles. I had them repaired with "apt-get install build-essential linux-headers-`uname -r`"
Now everything runs smoooth and easy