[xubuntu-users] virtualbox issue with linux/version.h and shared folders between guest and host

[Dan Hitt]

Thanks again Ralf, Roger, and Fred.

Just for reference, in case anybody is searching for what to do about
the VirtualBox tools and sees this thread:

Fred's idea for using sshfs is working out just fine for me, so that's
what i did.

Per Roger, i pinged the forum https://forums.virtualbox.org

They were very nice and got back to me by morning (i wrote in the
evening), but their response was that they could not support ubuntu's
forked version of VirtualBox.  And i certainly understand that,
because it's hard enough to support your own code let alone somebody
else's.

They also told me that i would have to purge the ubuntu version of
VirtualBox in order to install theirs.

So i'm just using the sshfs, which is actually a better solution
anyway as it doesn't require any extra kernel modules.

So that's the full story, and thanks again all for your help.

dan

On Tue, Jan 24, 2017 at 7:55 AM, Dan Hitt <dan.hitt at gmail.com> wrote:
> Hi Ralf and Fred, thanks for your replies.
>
> i actually made 2 guests, so that i could junk up one if desired, so
> maybe i'll try adding the symbolic links and compiling again.
>
> sshfs is also a good idea (and i'll bet other people use it as well,
> so that might be why this issue with the guest additions doesn't show
> up more on the net).
>
> thanks everybody for giving it some thought!!
>
> dan
>
> On Tue, Jan 24, 2017 at 7:03 AM, fred roller <fredroller66 at gmail.com> wrote:
>> Quick question on the share...  Why not a sshfs share between the host and
>> guest?  Both are Linux and don't need the extra load to communicate.  Since
>> my guest systems are bridged nics I can link via standard practice and sshfs
>> has been the best generic solution with only installing the ssh and sshfs
>> package.  If ssh is not desired then other Linux solutions to mount remote
>> folders should work as well since both systems are already on the same
>> network.  Hypothetically using the inet (internal network function of Vbox)
>> should still work if security is an issue.  Pardon my ignorance, but seems
>> like a lot of trouble here for something that is native to Linux so I am
>> just curious as to why?  To be sure, these share folder options did help
>> when I was working on Windows guests; however, Linux to Linux seemed best to
>> just use the tools available.
>>
>> On Tue, Jan 24, 2017 at 2:21 AM, Ralf Mardorf <silver.bullet at zoho.com>
>> wrote:
>>>
>>> On Mon, 23 Jan 2017 07:13:25 -0800, Dan Hitt wrote:
>>> >Is your recommendation then to edit VBoxLinuxAdditions.run to modify
>>> >the build path?
>>>
>>> You could add a link to the build tree or copy it to the other pass,
>>> but I don't know if this solves the issue. IIRC /lib/modules/*/ is a
>>> link against /usr/src/*/, so just add a link linux/version.h against
>>> the existing version.h.
>>>
>>>
>>> --
>>> xubuntu-users mailing list
>>> xubuntu-users at lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
>>
>>
>>
>> --
>> xubuntu-users mailing list
>> xubuntu-users at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
>>