From owner-freebsd-ports@FreeBSD.ORG Sat Jan 29 01:04:38 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6E9D16A4CE for ; Sat, 29 Jan 2005 01:04:38 +0000 (GMT) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id B526C43D54 for ; Sat, 29 Jan 2005 01:04:38 +0000 (GMT) (envelope-from craig@yekse.gank.org) Received: from aldaris.auir.gank.org (arbiter.gank.org [64.81.113.221]) by ion.gank.org (mail) with ESMTP id 2B5952D1D4; Fri, 28 Jan 2005 19:04:38 -0600 (CST) From: Craig Boston To: freebsd-ports@freebsd.org Date: Fri, 28 Jan 2005 19:04:33 -0600 User-Agent: KMail/1.7.2 References: <20050126025125.GA44297@nowhere> <200501260932.57528.josemi@freebsd.jazztel.es> In-Reply-To: <200501260932.57528.josemi@freebsd.jazztel.es> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501281904.33810.craig@yekse.gank.org> cc: Jose M Rodriguez Subject: Re: Kernel module path for ports? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jan 2005 01:04:39 -0000 On Wednesday 26 January 2005 2:32 am, Jose M Rodriguez wrote: > > $PREFIX/lib/$PORTNAME > better ${PREFIX}/libexec/... libexec seems like the logical choice, but so far I've not found any ports that put kernel modules there. (to make things easier I'm only looking at ones that have static pkg-plist files) > > $PREFIX/modules > Not an option By far the majority of ports use this location. I don't particularly like it because it's not there in a fresh install, nor is it mentioned in BSD.local.dist or hier(7). > > $PREFIX/share/$PORTNAME > modules are arch-specific. Can't go under ${PREFIX}/share/ ltmdm uses this, which is the port I initially used as a skeleton. There are a couple others as well: comms/mwavem and sysutils/pmap. I'll go with lib/$PORTNAME for now as it seems to be a decent compromise. It's easy enough to change should a clear standard emerge. NOTE: I previously said I was using an rcNG script to load the module. Upon further thought, that's unworkable for this particular port. It's a USB device driver -- if the device is plugged in at boot, ugen will grab it before the script ever gets a chance to load the driver. So the install script must copy it to /boot/modules and print a note on how to set up loader.conf. Thanks for your input! Craig