Date: Tue, 4 Nov 2014 18:29:55 -0500 From: Manas Bhatnagar <b.manas.88@gmail.com> To: freebsd-virtualization@freebsd.org Subject: Re: VIMAGE and VirtualBox networking question Message-ID: <CAN5odxBsgYuBPRdm%2B3w0wnhcVTWdDY8-A6vBC34PgwDA3WH5FQ@mail.gmail.com> In-Reply-To: <54595CB9.1050907@gmx.com> References: <5458F7ED.4030205@gmx.com> <54590971.9080800@freebsd.org> <54595CB9.1050907@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >> > I just tried with GENERIC and everything works. I don't know why I > expected a normal module to work with a VIMAGE kernel since VIMAGE modules > are erm... virtualized:) > > What I really wonder now is whether I could somehow avoid having to > install the ports tree for a single port. Something like, a package that > contains the source of the VirtualBox module which one could build. > > Or virtualbox-ose-kmod-vnet package:) > > Thoughts? Install ports tree in a temporary location (another computer or something), grab the required folder and move it to the computer that you want to install the port on and do 'make install clean' ? probably won't work like that, you would need to make sure the directories for dependencies are there too :o)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN5odxBsgYuBPRdm%2B3w0wnhcVTWdDY8-A6vBC34PgwDA3WH5FQ>