From owner-freebsd-emulation@FreeBSD.ORG Tue Jan 15 01:36:17 2013 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B027C9E0; Tue, 15 Jan 2013 01:36:17 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 5826EA40; Tue, 15 Jan 2013 01:36:17 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.6/8.14.6) with ESMTP id r0F1aFIA086128; Mon, 14 Jan 2013 18:36:15 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.6/8.14.6/Submit) with ESMTP id r0F1aFIx086125; Mon, 14 Jan 2013 18:36:15 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 14 Jan 2013 18:36:15 -0700 (MST) From: Warren Block To: =?ISO-8859-15?Q?Bernhard_Fr=F6hlich?= Subject: Re: VirtualBox kernel modules In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3512871622-1044595091-1358213775=:86014" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Mon, 14 Jan 2013 18:36:15 -0700 (MST) Cc: freebsd-emulation@freebsd.org X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2013 01:36:17 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3512871622-1044595091-1358213775=:86014 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Fri, 11 Jan 2013, Bernhard Fröhlich wrote: > On Fri, Jan 11, 2013 at 4:19 PM, Brandon Gooch > wrote: >> On Thu, Jan 10, 2013 at 10:31 PM, Warren Block 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. > > I think this is an unwanted side effect. In fact I changed the defintion of > where the kernel module should be installed in virtualbox-ose-kmod/Makefile > from KMODDIR=/boot/modules to KMODDIR?=/boot/modules to allow > overwriting the KMODDIR in case you want to have a non default directory > for your kernel modules (like in a jail). > > I haven't found yet where KMODDIR is set to /boot/kernel but it obviously is > defined somewhere. I'm also not sure if that is really a virtualbox > problem or if > we better should fix that in Mk and set KMODDIR or create a new variable for > ports kernel modules. > > In the meantime overwriting KMODDIR to /boot/modules in your make.conf > should help. Except that if you set KMODDIR=/boot/modules, then all the OS kernel modules are put there also. And building or installing the kernel still wipes out that directory and the Virtualbox modules. --3512871622-1044595091-1358213775=:86014--