Date: Thu, 10 Jan 2013 21:31:45 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Ryan Stone <rysto32@gmail.com> Cc: freebsd-emulation@freebsd.org Subject: Re: VirtualBox kernel modules Message-ID: <alpine.BSF.2.00.1301102130150.23661@wonkity.com> In-Reply-To: <CAFMmRNw%2B%2BdNNhYfUUWH4P1pUoO3koC%2BdTKR_PFVbkJCA2p0YMA@mail.gmail.com> References: <alpine.BSF.2.00.1301101929430.23007@wonkity.com> <CAFMmRNw%2B%2BdNNhYfUUWH4P1pUoO3koC%2BdTKR_PFVbkJCA2p0YMA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1301102130150.23661>