From owner-freebsd-fs@FreeBSD.ORG Wed Mar 10 06:51:27 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83D1216A4CE for ; Wed, 10 Mar 2004 06:51:27 -0800 (PST) Received: from citi.umich.edu (citi.umich.edu [141.211.133.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 675F643D41 for ; Wed, 10 Mar 2004 06:51:27 -0800 (PST) (envelope-from rees@citi.umich.edu) Received: from citi.umich.edu (dsl093-001-248.det1.dsl.speakeasy.net [66.93.1.248]) by citi.umich.edu (Postfix) with ESMTP id 76DE520820; Wed, 10 Mar 2004 09:51:26 -0500 (EST) To: freebsd-fs@freebsd.org, openafs-devel@openafs.org From: Jim Rees In-Reply-To: Garrett Wollman, Tue, 09 Mar 2004 22:08:25 EST Date: Wed, 10 Mar 2004 09:51:27 -0500 Sender: rees@citi.umich.edu Message-Id: <20040310145126.76DE520820@citi.umich.edu> Subject: Re: [OpenAFS-devel] OpenAFS for FreeBSD 5.2 patch X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2004 14:51:27 -0000 I suppose in the short term we need yet another configure (or make) option to specify the location of the kernel build. But I really detest this solution. I would much rather be able to build a single module that would work with any kernel built from a given set of sources.