On 2013-01-10 00:45, Alexey V. Panfilov wrote:
Hi.
After update virtualbox from 4.1.22 to 4.2.6 vboxnetflt module can't
load:
[work-book]# /usr/local/etc/rc.d/vboxnet start
/usr/local/etc/rc.d/vboxnet: WARNING: Can't load vboxnetflt module.
And /var/log/messages contains
Jan 10 10:36:06 wor
10.01.2013 17:14, Rusty Nejdl wrote:
> On 2013-01-10 00:45, Alexey V. Panfilov wrote:
>> Hi.
>>
>> After update virtualbox from 4.1.22 to 4.2.6 vboxnetflt module can't
>> load:
>>
>> [work-book]# /usr/local/etc/rc.d/vboxnet start
>> /usr/local/etc/rc.d/vboxnet: WARNING: Can't load vboxnetflt module
emulators/virtualbox-ose-kmod puts the built kernel modules in
/boot/kernel along with all the system kernel modules.
However, somewhere in the buildworld/kernel/installworld process, these
modules are deleted. Deinstalling the port shows this:
# make deinstall
===> Deinstalling for emu
On 2013-01-10 20:34, Warren Block wrote:
emulators/virtualbox-ose-kmod puts the built kernel modules in
/boot/kernel along with all the system kernel modules.
However, somewhere in the buildworld/kernel/installworld process,
these modules are deleted. Deinstalling the port shows this:
# make
As I recall, a make installkernel will first mv /boot/kernel
/boot/kernel.old
Should ports put modules in /boot/modules to avoid this kind of thing?
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulatio
On Thu, 10 Jan 2013, Ryan Stone wrote:
As I recall, a make installkernel will first mv /boot/kernel /boot/kernel.old
Should ports put modules in /boot/modules to avoid this kind of thing?
I thought so, but the Porter's Handbook doesn't say anything about it.
multimedia/cuse4bsd-kmod installs
