From owner-freebsd-afs Fri Mar 30 12:23:15 2001 Delivered-To: freebsd-afs@freebsd.org Received: from mercury.ccmr.cornell.edu (mercury.ccmr.cornell.edu [128.84.231.97]) by hub.freebsd.org (Postfix) with ESMTP id 4A00A37B71C for ; Fri, 30 Mar 2001 12:23:13 -0800 (PST) (envelope-from mitch@ccmr.cornell.edu) Received: from ruby.ccmr.cornell.edu (IDENT:0@ruby.ccmr.cornell.edu [128.84.231.115]) by mercury.ccmr.cornell.edu (8.9.3/8.9.3) with ESMTP id PAA02917; Fri, 30 Mar 2001 15:23:11 -0500 Received: from localhost (mitch@localhost) by ruby.ccmr.cornell.edu (8.9.3/8.9.3) with ESMTP id PAA12034; Fri, 30 Mar 2001 15:23:07 -0500 X-Authentication-Warning: ruby.ccmr.cornell.edu: mitch owned process doing -bs Date: Fri, 30 Mar 2001 15:23:07 -0500 (EST) From: Mitch Collinsworth To: Tom Maher Cc: freebsd-afs@FreeBSD.ORG, port-freebsd@openafs.org Subject: Re: afs port In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-afs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 30 Mar 2001, Tom Maher wrote: > Rob is right, though, that the priority should be getting a working > server before getting a "real" client. However, given the sheer ammount > of stuff that OpenAFS does in kernelspace rather than userland, I'm not > sure that the server doesn't depend on the kernel module. I don't know the internals enough to answer that, but judging from the AFS Installation Guide, the kernel mods are pre-requisite to running the server processes. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-afs" in the body of the message