From owner-freebsd-afs@FreeBSD.ORG Wed Jul 16 05:19:41 2008 Return-Path: Delivered-To: afs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC56B1065671 for ; Wed, 16 Jul 2008 05:19:40 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id AD71F8FC16 for ; Wed, 16 Jul 2008 05:19:40 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so6731376rvf.43 for ; Tue, 15 Jul 2008 22:19:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=qttyKtLJOmT8cQOcqM8pK4q5z4Y45Vjryb9Kg3dmKwc=; b=lkFOvv6OkoA25pvtJ9e7OBt84wd52miWYQyqew9dQZMN+1pSz+90T6VE2c0ScRkbEE W0LVjZnZdVezS9Jya8hScrQaYKK4deGy9FRKnJXcvybull9tOCHOQJUhohl6UsDEm3GO KINegwaE43I67IOf0M94VqsrMsas7IZghPg/c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=UPF287EKXvvZoyE+lt70nhYvQ/yRpEnZbgd2PGh4Q7oZv9nM+baJ7Jm38+ZlkOOh4v CpJ6R/q2xAjzjqkb4RUSqMcwkEWEuxAUey7alGGHLbphYAOF0dA+wm4EzlLUwqNxTCBv 0BsniOik1H32y7ydlbtElcmiVm1pfRsy4eA1E= Received: by 10.140.193.16 with SMTP id q16mr7992573rvf.173.1216183963022; Tue, 15 Jul 2008 21:52:43 -0700 (PDT) Received: by 10.140.225.1 with HTTP; Tue, 15 Jul 2008 21:52:42 -0700 (PDT) Message-ID: <47d0403c0807152152j7c452b3cp275f8015da783542@mail.gmail.com> Date: Wed, 16 Jul 2008 00:52:42 -0400 From: "Ben Kaduk" To: "Alec Kloss" In-Reply-To: <20080226061140.GI28956@hamlet.SetFilePointer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080216035658.W93919@fledge.watson.org> <20080218012608.V96329@fledge.watson.org> <20080222125207.GD38141@hamlet.setfilepointer.com> <20080223092516.O23969@fledge.watson.org> <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> Cc: afs@freebsd.org, Robert Watson , Garance A Drosehn , arla-drinkers@stacken.kth.se Subject: Re: Patches to get Arla running on FreeBSD 8-CURRENT X-BeenThere: freebsd-afs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: The Andrew File System and FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2008 05:19:41 -0000 On Tue, Feb 26, 2008 at 2:11 AM, Alec Kloss wrote: > On 2008-02-25 22:23, Garance A Drosehn wrote: >> At 9:38 PM -0400 2/25/08, Marc G. Fournier wrote: >> >-----BEGIN PGP SIGNED MESSAGE----- >> >Hash: SHA1 >> > >> >Can we commit these patches to ports itself, maybe with the make >> >file setup so 6.x is marked BROKEN while dealing with the problems >> >there? Might get more testers involved ... ? >> >> Or create a new port, "arla8", or "arla-dev". > > To the best of my knowledge, the port I made > (http;//setfilepointer.com/pub/afs/FreeBSD) works for 6.3, 7.0 and > -current, except maybe for changes in the last few days in -current > which may have broken the port. If there's sufficient interest, > I'll add 5.x support (via arla 0.43) to the port as well, but I was > hoping to avoid that, as it's a lot of overhead and arla's newish > block-by-block cache (thanks Thomas) which isn't available in arla > 0.43 makes arla highly competitive with the OpenAFS client > available elsewhere. > > As for getting the port into the ports tree, I think everyone's all > for it, but Thomas is volunteering to help merge our patch into the > arla sources which I'd prefer over maintaining a jumbo patch like > what we have now. I'm optimistic that we can probably have > everything ready by/after the weekend. > > So, please do test the port, and whine at me and/or Robert about > issues with it. I'm trying to shelter him from the details as long > as he shelters me from VFS. :) Sorry to reply to such an old thread, but I see that there have been recent contributions to the AFS page on the FreeBSD wiki (such as testing on 7.0-release), but the port still hasn't made it into the FreeBSD Ports Collection. Is this in the works? Is it merely lacking for manpower? Thanks, Ben Kaduk From owner-freebsd-afs@FreeBSD.ORG Wed Jul 16 12:08:00 2008 Return-Path: Delivered-To: afs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18FDB106566B for ; Wed, 16 Jul 2008 12:08:00 +0000 (UTC) (envelope-from alec-keyword-arla.4d43de@SetFilePointer.com) Received: from hamlet.setfilepointer.com (hamlet.SetFilePointer.com [63.224.10.2]) by mx1.freebsd.org (Postfix) with SMTP id A05AE8FC23 for ; Wed, 16 Jul 2008 12:07:59 +0000 (UTC) (envelope-from alec-keyword-arla.4d43de@SetFilePointer.com) Received: (qmail 89183 invoked by uid 4250); 16 Jul 2008 06:41:18 -0500 Received: by hamlet.SetFilePointer.com (tmda-sendmail, from uid 4250); Wed, 16 Jul 2008 06:41:18 -0500 Date: Wed, 16 Jul 2008 06:41:18 -0500 To: Robert Watson , Ben Kaduk Message-ID: <20080716114118.GJ71954@hamlet.SetFilePointer.com> References: <20080218012608.V96329@fledge.watson.org> <20080222125207.GD38141@hamlet.setfilepointer.com> <20080223092516.O23969@fledge.watson.org> <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> <47d0403c0807152152j7c452b3cp275f8015da783542@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pMCBjikF2xGw87uL" Content-Disposition: inline In-Reply-To: <47d0403c0807152152j7c452b3cp275f8015da783542@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-Delivery-Agent: TMDA/1.1.12 (Macallan) From: Alec Kloss X-Primary-Address: alec@SetFilePointer.com Cc: afs@freebsd.org, Garance A Drosehn , arla-drinkers@stacken.kth.se Subject: Re: Patches to get Arla running on FreeBSD 8-CURRENT X-BeenThere: freebsd-afs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: The Andrew File System and FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2008 12:08:00 -0000 --pMCBjikF2xGw87uL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-07-16 00:52, Ben Kaduk wrote: [chop] >=20 > Sorry to reply to such an old thread, but I see that there have been > recent contributions to the AFS page on the FreeBSD wiki (such > as testing on 7.0-release), but the port still hasn't made it into > the FreeBSD Ports Collection. Is this in the works? Is it merely lacking > for manpower? >=20 > Thanks, >=20 > Ben Kaduk >=20 No problem on the old thread... I was hoping there might be a Arla release to use instead of my homemade tarball that the arla-devel port is using for making an official PR. There are also some stability issues with arla on FreeBSD which I haven't been able to track down successfully. And finally, arla no longer seems to compile against -CURRENT. All of these things, plus a lack of time as you mention, have kept me from making a PR for a port. =20 Robert, my -CURRENT box needs a power supply which is on it's way; when I get it running, do you mind if I ask for some assistance getting a newer arla snapshot going on -CURRENT? Once that's working I'll commit to writing up a PR to get the arla-devel port (and openafs-devel too) committed. --=20 Alec Kloss alec@SetFilePointer.com IM: angryspamhater@yahoo.com PGP key at http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xA241980E "No Bunny!" -- Simon, from Frisky Dingo --pMCBjikF2xGw87uL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFIfd5e2s33paJBmA4RAgKWAJ0UBnP8SJIp18fW8fYiSEcxpjKsJQCfbCv/ XVr2J/KigciPxoa/6hfvcVY= =6ofn -----END PGP SIGNATURE----- --pMCBjikF2xGw87uL-- From owner-freebsd-afs@FreeBSD.ORG Wed Jul 16 21:43:41 2008 Return-Path: Delivered-To: afs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84981106564A for ; Wed, 16 Jul 2008 21:43:41 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id 356538FC2B for ; Wed, 16 Jul 2008 21:43:41 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so2407104ywe.13 for ; Wed, 16 Jul 2008 14:43:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=wZCjyPwjVjxMyRoV1GpCNfVGxZDuB9KIH2mgDJLMVX4=; b=Mmk/tlBHlG6zDxf2Y7BO5Qf4HfP4lNjNjump9IXodmVdASYKKZ0eK4o10G5aUsLG4E sLhMnrAaROMXmDBADY+vvRu0Xhkv7spwKH7DPoGXoRqTbmX2mLsN0FijSSJ67+quCsqH nz3+6HMK9BaYufSFmM+/eCbVQ6P2TTod9+/XI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=oE9IimAR19ojzAbvXp3Pr+y8rzgZn24OCDhZWVTZZfP6tgR2tKAqhjVCYlnpDMISmF Q+ThgyK/Mve1h2lcG+kC3ZGUCsn/sB//vWv1K1rO7R4M1fmAVDi5GQpHwVJke7QchtKu vLmxbmVA6kCwxp/Q7MCf0itpko89PZIl4qlpA= Received: by 10.140.202.21 with SMTP id z21mr719110rvf.81.1216244619645; Wed, 16 Jul 2008 14:43:39 -0700 (PDT) Received: by 10.140.225.1 with HTTP; Wed, 16 Jul 2008 14:43:39 -0700 (PDT) Message-ID: <47d0403c0807161443l4f002f17ibc1e5bfea4b925cd@mail.gmail.com> Date: Wed, 16 Jul 2008 17:43:39 -0400 From: "Ben Kaduk" To: "Alec Kloss" In-Reply-To: <20080716114118.GJ71954@hamlet.SetFilePointer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080218012608.V96329@fledge.watson.org> <20080223092516.O23969@fledge.watson.org> <20080223102922.GF38141@hamlet.setfilepointer.com> <20080223110549.GG38141@hamlet.setfilepointer.com> <20080223161249.GH38141@hamlet.setfilepointer.com> <90334B40754BEDC2991E0147@ganymede.hub.org> <20080226061140.GI28956@hamlet.SetFilePointer.com> <47d0403c0807152152j7c452b3cp275f8015da783542@mail.gmail.com> <20080716114118.GJ71954@hamlet.SetFilePointer.com> Cc: afs@freebsd.org, Robert Watson , arla-drinkers@stacken.kth.se Subject: Re: Patches to get Arla running on FreeBSD 8-CURRENT X-BeenThere: freebsd-afs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: The Andrew File System and FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2008 21:43:41 -0000 On Wed, Jul 16, 2008 at 7:41 AM, Alec Kloss wrote: > On 2008-07-16 00:52, Ben Kaduk wrote: > [chop] >> >> Sorry to reply to such an old thread, but I see that there have been >> recent contributions to the AFS page on the FreeBSD wiki (such >> as testing on 7.0-release), but the port still hasn't made it into >> the FreeBSD Ports Collection. Is this in the works? Is it merely lacking >> for manpower? >> >> Thanks, >> >> Ben Kaduk >> > > No problem on the old thread... > > I was hoping there might be a Arla release to use instead of my > homemade tarball that the arla-devel port is using for making an > official PR. There are also some stability issues with arla on > FreeBSD which I haven't been able to track down successfully. > And finally, arla no longer seems to compile against -CURRENT. All > of these things, plus a lack of time as you mention, have kept me > from making a PR for a port. > I'm glad that you're still thinking about it, even if you don't have enough time to do a whole lot with it. If I was to try to get arla running on -current again, would you recommend starting from your tarball or from a snapshot from upstream arla? Thanks, Ben Kaduk