VirtualBox kernel modules

[Brandon Gooch]

On Thu, Jan 10, 2013 at 10:31 PM, Warren Block <wblock at wonkity.com> wrote:

> 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 a module there.


 The previous versions of this port did indeed install the modules into
/boot/modules; only with the most recent version (4.2.6) has this changed.
For example:

$ tar tvf /usr/ports/packages/All/virtualbox-ose-kmod-4.1.22.txz
[...]
-r-xr-xr-x  0 root   wheel  297288 Sep 19 09:19 /boot/modules/vboxdrv.ko
-r-xr-xr-x  0 root   wheel    9544 Sep 19 09:19 /boot/modules/vboxnetadp.ko
-r-xr-xr-x  0 root   wheel   26648 Sep 19 09:19 /boot/modules/vboxnetflt.ko
[...]

$ tar tvf /usr/ports/packages/All/virtualbox-ose-kmod-4.2.6.txz
[...]
-r-xr-xr-x  0 root   wheel  337912 Jan  6 13:13 /boot/kernel/vboxdrv.ko
-r-xr-xr-x  0 root   wheel    9696 Jan  6 13:13 /boot/kernel/vboxnetadp.ko
-r-xr-xr-x  0 root   wheel   26808 Jan  6 13:13 /boot/kernel/vboxnetflt.ko
[...]

I don't know WHY this changed, or if it was just an oversight during the
update -- perhaps it by (re)design...

-Brandon