From owner-freebsd-afs Thu Mar 29 19: 0:29 2001 Delivered-To: freebsd-afs@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 006FB37B71B for ; Thu, 29 Mar 2001 19:00:23 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA39882; Thu, 29 Mar 2001 22:00:20 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Thu, 29 Mar 2001 19:20:28 -0500 To: George.Giles@mcmail.vanderbilt.edu, freebsd-afs@FreeBSD.ORG From: Garance A Drosihn Subject: Re: afs port Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-afs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Feb 8/2001, George.Giles@mcmail.vanderbilt.edu wrote: >Has the openAFS from IBM been ported to FreeBSD yet? Did anyone reply to this yet? There is a mailing list at the openafs site for the freebsd port, but there hasn't been a lot of activity on it. I know someone was looking over the openafs code for freebsd, but I don't know what the current status is. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-afs" in the body of the message From owner-freebsd-afs Fri Mar 30 11:52:48 2001 Delivered-To: freebsd-afs@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id A6F2E37B718 for ; Fri, 30 Mar 2001 11:52:45 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2UJpah44952; Fri, 30 Mar 2001 14:51:36 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 30 Mar 2001 14:51:36 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Garance A Drosihn Cc: George.Giles@mcmail.vanderbilt.edu, 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 Thu, 29 Mar 2001, Garance A Drosihn wrote: > On Feb 8/2001, George.Giles@mcmail.vanderbilt.edu wrote: > >Has the openAFS from IBM been ported to FreeBSD yet? > > Did anyone reply to this yet? > > There is a mailing list at the openafs site for the freebsd port, but > there hasn't been a lot of activity on it. I know someone was looking > over the openafs code for freebsd, but I don't know what the current > status is. Last I heard, Tom Maher had a large (130kb+) patch to get the userland code working. However, that doesn't address the issue of the kernel module, or whether the patch was complete (unlikely given the scale of the task). With regards to the kernel module, the best starting point is probably to select the platform with the closest VFS layer to FreeBSD's, and work from there. In my view, the highest priority is really getting the server-side working, given that Arla provides a quite workable AFS client on FreeBSD already, and is well-maintained. Unfortunately, I have plenty on my plate already so am unlikely to make any forward progress in active development. Given semi-working code, I'd be glad to help debug it and attempt to track nasty kernel bugs, of which I am sure there will be plenty :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-afs" in the body of the message From owner-freebsd-afs Fri Mar 30 12: 5:55 2001 Delivered-To: freebsd-afs@freebsd.org Received: from zaphod.ece.cmu.edu (ZAPHOD.ECE.CMU.EDU [128.2.236.35]) by hub.freebsd.org (Postfix) with ESMTP id 4F41337B71A for ; Fri, 30 Mar 2001 12:05:52 -0800 (PST) (envelope-from tardis@watson.org) Received: (from tardis@localhost) by zaphod.ece.cmu.edu (8.11.0/8.8.8) id f2UK5nj16648; Fri, 30 Mar 2001 15:05:49 -0500 (EST) X-Authentication-Warning: zaphod.ece.cmu.edu: tardis set sender to tardis@watson.org using -f To: freebsd-afs@FreeBSD.ORG, port-freebsd@openafs.org Subject: Re: afs port References: From: Tom Maher Date: 30 Mar 2001 15:05:49 -0500 In-Reply-To: Robert Watson's message of "Fri, 30 Mar 2001 14:51:36 -0500 (EST)" Message-ID: Lines: 45 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-afs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert Watson writes: > On Thu, 29 Mar 2001, Garance A Drosihn wrote: > > > On Feb 8/2001, George.Giles@mcmail.vanderbilt.edu wrote: > > >Has the openAFS from IBM been ported to FreeBSD yet? > > > > Did anyone reply to this yet? > > > > There is a mailing list at the openafs site for the freebsd port, but > > there hasn't been a lot of activity on it. I know someone was looking > > over the openafs code for freebsd, but I don't know what the current > > status is. > > Last I heard, Tom Maher had a large (130kb+) patch to get the userland > code working. However, that doesn't address the issue of the kernel > module, or whether the patch was complete (unlikely given the scale of the > task). With regards to the kernel module, the best starting point is > probably to select the platform with the closest VFS layer to FreeBSD's, > and work from there. In my view, the highest priority is really getting > the server-side working, given that Arla provides a quite workable AFS > client on FreeBSD already, and is well-maintained. Unfortunately, I have > plenty on my plate already so am unlikely to make any forward progress in > active development. Given semi-working code, I'd be glad to help debug > it and attempt to track nasty kernel bugs, of which I am sure there will > be plenty :-). You and your nagging memory, Rob. Yeah, I've been off-and-on working on getting the kernelspace code to work, basing it off of the Digital Unix code, the closest VFS layer. The problem that's been keeping me from doing much more is lack of understanding the buffer cache, which is completely different from the Digital Unix buffer cache. I should probably make what code I do have up on the web. No, I haven't tested it. 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. -- Tom Maher To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-afs" in the body of the message 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 From owner-freebsd-afs Fri Mar 30 15:15: 6 2001 Delivered-To: freebsd-afs@freebsd.org Received: from blubb.pdc.kth.se (blubb.pdc.kth.se [130.237.221.147]) by hub.freebsd.org (Postfix) with ESMTP id 72B3337B71A for ; Fri, 30 Mar 2001 15:15:04 -0800 (PST) (envelope-from joda@pdc.kth.se) Received: from joda by blubb.pdc.kth.se with local (Exim 3.13 #1) id 14j85r-0004po-00; Sat, 31 Mar 2001 01:14:11 +0200 To: Mitch Collinsworth Cc: Tom Maher , freebsd-afs@FreeBSD.ORG, port-freebsd@openafs.org Subject: Re: afs port References: From: joda@pdc.kth.se (Johan Danielsson) Date: 31 Mar 2001 01:14:11 +0200 In-Reply-To: Mitch Collinsworth's message of "Fri, 30 Mar 2001 15:23:07 -0500 (EST)" Message-ID: Lines: 11 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-afs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mitch Collinsworth writes: > 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. That's because the fileserver uses special system calls to bypass the ufs namespace when allocating files. Any first, sane, implementation should probably go the linux way and circumvent this problem. /Johan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-afs" in the body of the message