Date: Fri, 11 Jan 2013 09:19:56 -0600 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: Warren Block <wblock@wonkity.com> Cc: freebsd-emulation@freebsd.org Subject: Re: VirtualBox kernel modules Message-ID: <CALBk6yJH4P1jSkSR-rOc5st1jWu_jrR1C2JBK_ebbVnnNi%2B%2BEw@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1301102130150.23661@wonkity.com> References: <alpine.BSF.2.00.1301101929430.23007@wonkity.com> <CAFMmRNw%2B%2BdNNhYfUUWH4P1pUoO3koC%2BdTKR_PFVbkJCA2p0YMA@mail.gmail.com> <alpine.BSF.2.00.1301102130150.23661@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 10, 2013 at 10:31 PM, Warren Block <wblock@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALBk6yJH4P1jSkSR-rOc5st1jWu_jrR1C2JBK_ebbVnnNi%2B%2BEw>