Code: Select all
vboxguest_enable="YES"
vboxservice_enable="YES"
Code: Select all
# mount_smbfs -I 192.168.56.1 //<NETBIOS NAME>/<SHARENAME> <MOUNT POINT>
Code: Select all
vboxguest_enable="YES"
vboxservice_enable="YES"
Code: Select all
# mount_smbfs -I 192.168.56.1 //<NETBIOS NAME>/<SHARENAME> <MOUNT POINT>
I cannot make sense of what you wrote. There is no way a new kernel can be installed as part of a package install or a port install.mechanic wrote:Well I installed the virtualbox-ose-additions port - which incidentally included a LOT of extra download including the full kernel
This it is very important, as he is saying. I destroyed versions of differents BSDs by doing this. If you go packages I recommend you to stay with it, do not mix.ASX wrote:It is strongly advised to not mix "ports" and "packages", this is especially true when they are out of sync, like in the case of pkgs quarterly repo vs. head branch of ports.mechanic wrote:Well I installed the virtualbox-ose-additions port - which incidentally included a LOT of extra download including the full kernel
Difficult to be brief and clear. When I ran 'make' in the port directory, it stopped pretty quickly with the instruction to download the kernel source into some src directory. After all that during the 'make' operation several dependencies were also installed. Hope that's now clear enough.ASX wrote:I cannot make sense of what you wrote. There is no way a new kernel can be installed as part of a package install or a port install.mechanic wrote:Well I installed the virtualbox-ose-additions port - which incidentally included a LOT of extra download including the full kernel
OK, I tried again with just packages (actually just the one on top of the basic 10.3 install) but with no luck. Networking doesn't seem to be working, no shares appear in the Windows Network tab/folder in the file manager. smb services don't appear to be installed? I'll try pinging host/guest later when I have some free time.Anyway, for your info:
packages, as shipped in a default GhostBSD install, are fetched from "quarterly" repository. (as opposed to "latest" repository).
"ports", as obtained from "portsnap fetch extract" refer to the "head" branch of ports repository, which can be considered (nearly) in sync with "latest" repository.
It is strongly advised to not mix "ports" and "packages", this is especially true when they are out of sync, like in the case of pkgs quarterly repo vs. head branch of ports.
~~~
Is networking working properly between host and guest ?
can you ping the host from the guest ?
can you ping the guest from the host ?
Yes, that make sense, building virtualbox-ose-additions require kernel sources, because it make use of some kernel data structure. (and kernel sources are an optional component of FreeBSD/GhostBSD os).mechanic wrote: Difficult to be brief and clear. When I ran 'make' in the port directory, it stopped pretty quickly with the instruction to download the kernel source into some src directory. After all that during the 'make' operation several dependencies were also installed. Hope that's now clear enough.
Could you please put the full command line that you are using?mechanic wrote:Today the same problem. I can ping both the guest (G-BSD) from the Windows machine and windows from the Guest system. The response to the mount_smb command is "unable to open connection: syserror = operation timed out"
Sure:adripillo12 wrote:
Could you please put the full command line that you are using?
Code: Select all
# mount_smbfs -I 192.168.56.1 //user@RASPBERRY/sharing /mnt/shares