From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Mon, 13 Nov 2006 10:07:52 -0800 (PST) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id kADI7iaG007555 for ; Mon, 13 Nov 2006 10:07:45 -0800 Received: from evaldomino.Falconstor.com (mail1.falconstor.com [216.223.47.230]) by cuda.sgi.com (Spam Firewall) with ESMTP id E5A7CD1D2CDE for ; Mon, 13 Nov 2006 09:48:00 -0800 (PST) Message-ID: <4558AFC9.3010009@falconstor.com> Date: Mon, 13 Nov 2006 12:47:53 -0500 From: "Geir A. Myrestrand" Reply-To: geir.myrestrand@falconstor.com MIME-Version: 1.0 Subject: Re: Update for the RHEL4 XFS module? References: <455893BE.4010208@moving-picture.com> <45589A06.7040503@sandeen.net> <4558AE11.2030108@falconstor.com> <4558AEFE.10108@sandeen.net> In-Reply-To: <4558AEFE.10108@sandeen.net> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: Eric Sandeen Cc: James Pearson , xfs@oss.sgi.com Eric Sandeen wrote: > Geir A. Myrestrand wrote: >> Eric Sandeen wrote: >>> James Pearson wrote: >>>> The RHEL4 XFS module code at >>>> is now about a year old. >>>> >>>> Is there any chance that it could be updated with something based on >>>> more recent code? >>>> >>> Funny you should ask, I just started looking at this last night :) >>> >>> It was originally based on the SLES9 xfs code; my plan is to simply >>> update it to the latest sles9 xfs codebase, as that has been tended to >>> with a goal of stability by the fine folks at sgi.... so, no >>> bleeding-edge xfs for now (I don't particularly want to backport 2.6.18 >>> xfs code to 2.6.9....) >>> >> Eric, please notify us via the list when it has been updated. >> I would like this module updated too... > > Will do. Are there particular issues you're having, or is your code > just feeling a bit old in general. ;-) No particular issue in my case, but there tend to be some bug fixes in any given 12-month time-span... ;-) -- Geir A. Myrestrand