From owner-freebsd-ports@FreeBSD.ORG Sat Oct 2 17:56:54 2004 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 9289716A4CE for ; Sat, 2 Oct 2004 17:56:54 +0000 (GMT) Received: from s1.stradamotorsports.com (ip30.gte215.dsl-acs2.sea.iinet.com [209.20.215.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2303743D2F for ; Sat, 2 Oct 2004 17:56:54 +0000 (GMT) (envelope-from jcw@highperformance.net) Received: from [192.168.1.16] ([192.168.1.16])i92HuO8m037134; Sat, 2 Oct 2004 10:56:24 -0700 (PDT) (envelope-from jcw@highperformance.net) Date: Sat, 02 Oct 2004 10:56:30 -0700 From: "Jason C. Wells" To: Robin Schoonover Message-ID: In-Reply-To: <20041002011611.4a2eae96@zork> References: <20041002011611.4a2eae96@zork> X-Mailer: Mulberry/3.1.5 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Status: No, hits=-2.0 required=4.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-ports@freebsd.org Subject: Re: Proper Way to Install OpenAFS Kernel Module 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, 02 Oct 2004 17:56:54 -0000 --On Saturday, October 02, 2004 1:16 AM -0600 Robin Schoonover wrote: > On Fri, 01 Oct 2004 19:17:18 -0700 > "Jason C. Wells" wrote: >> Is there a pre-existing means in the ports system for installing a >> kernel module? > Take a look at how x11/nvidia-driver and net/nvnet do it. > (@cwd in pkg-plist in particular) Those ports do pretty much exactly the > same thing you want to do. (So you can see that there isn't much > for preexisting functionality). This sounds like an appropriate avenue. I'll look into it. > Don't forget to put your kernel module in /boot/modules, not > /boot/kernel, otherwise it'll get nuked on kernel install (nvnet does > this wrong) I figured that one out already. (Hey, where'd my module go?) Later, Jason C. Wells