Date: Wed, 11 Jul 2007 14:26:39 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Eric Anderson <anderson@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: Coda-client and kernel panic Message-ID: <20070711142332.M64621@fledge.watson.org> In-Reply-To: <46943C70.1080500@freebsd.org> References: <2c84c1de0707060800t21f3f993mfb53f7975a881ed4@mail.gmail.com> <2c84c1de0707100453j9570769vfd19fea05ae11f76@mail.gmail.com> <20070711005300.V8913@fledge.watson.org> <20070711014204.GE5824@delft.aura.cs.cmu.edu> <46943C70.1080500@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 10 Jul 2007, Eric Anderson wrote: >>> The FreeBSD Project has a long history of granting commit rights to Coda >>> developers in order to allow Coda developers to maintain the in-kernel >>> Coda module -- Bob Baron, myself, and later Shafeeq Sinnamohideen. I >>> believe Shafeeq may still be affiliated with, or at least in the general >>> physical vicinity of, the Coda Project. I sent him e-mail in early June >>> asking what the status of the Coda work was, and what, if anything, to do >>> about the kernel module--I didn't hear back. I see Jan has just submitted >>> a number >> >> I bump into Shafeeq once in a while around campus, but nowadays he is >> pretty much in full thesis writing mode, which may explain why he has >> dropped off of the face of the earth. This is good to know :-). >>> 7.0 beta series starts. There has been discussion of removing the Coda >>> module from the kernel tree on the basis that it has been, until the last >>> day or so, effectively unmaintained for several years. However, if it's >> >> I hadn't heard those rumours, is there some other list besides freebsd-fs >> that I should subscribe to? > > Jan - I think it was on -current, and it was a brief discussion if I recall. > > Jan actually sent me the patches back in May, but I had some initial issues > with them (from some changes in -CURRENT), and then I had two major things > happen (new baby and new job at a startup) so I had *zero* time to finish > looking at the patches (sorry Jan!). > > If it's worth anything, I can try to at least do some quick testing with it, > and then I think it should be committed - at least it can't be as bad as > what's in the tree already. :) Sounds good -- I installed a new VM for this purpose also last night, but as the port for Coda is still at 6.1.2 and the 6.9.1 version is required now, I haven't had a chance to put the Coda bits together yet. If you can do the testing on the patches, I can commit them after getting release engineering approval (since we're in the 7.0 freeze). It sounds like we also need to get the Coda port up-to-date, which is not something I'm set up to do. Shafeeq may still have his ports commit bit, although I think I saw word that it was being expired due to non-use, so we may need to draft someone else in. The right way forward is, if there's no convenient ports committer on hand, is to file a PR with the port update. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070711142332.M64621>