From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Mon, 13 Nov 2006 09:00:36 -0800 (PST) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.168.28]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id kADH0QaG032654 for ; Mon, 13 Nov 2006 09:00:28 -0800 Received: from moving-picture.com (mpc-26.sohonet.co.uk [193.203.82.251]) by cuda.sgi.com (Spam Firewall) with ESMTP id E03D251BCCD for ; Mon, 13 Nov 2006 08:59:30 -0800 (PST) Message-ID: <4558A456.8070806@moving-picture.com> Date: Mon, 13 Nov 2006 16:59:02 +0000 From: James Pearson MIME-Version: 1.0 Subject: Re: Update for the RHEL4 XFS module? References: <455893BE.4010208@moving-picture.com> <45589A06.7040503@sandeen.net> In-Reply-To: <45589A06.7040503@sandeen.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: Eric Sandeen Cc: xfs@oss.sgi.com 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? >> >> Thanks >> >> James Pearson >> >> > > 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....) Thanks - that's good to know. James Pearson