From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Ram Natarajan <ram@arohisystems.com>, xfs@oss.sgi.com
Subject: Re: Help with xfs and Fedora 8
Date: Thu, 13 Oct 2011 06:35:04 -0400 [thread overview]
Message-ID: <20111013103504.GA16466@infradead.org> (raw)
In-Reply-To: <20111012231424.GK3159@dastard>
On Thu, Oct 13, 2011 at 10:14:24AM +1100, Dave Chinner wrote:
> > For various technical reasons, I cannot move to a
> > later kernel, but it would be great if I can build the latest xfs modules
> > and xfs support code for 2.6.23. Does anybody know if this is possible, and
> > if it is possible, will it work reliably?
>
> The kernel code is not so simple. Indeed, if you're not a kernel
> programmer and familiar with the XFS code, then I'd put it in the
> impossible basket. It'll take at least 3 months to do the backport
> and adequately test it for production use, and that's if you pay an
> expert to do it.
>
> It's far, far simpler to just upgrade your machines to a more recent
> distribution that it is to backport code to kernels that old....
Indeed. If you insist on an old kernel version with a semi recent XFS
please get a RHEL/Centos 5 kernel. That one is actually labelled 2.6.18
but contains many fixes and updated components, including a relatively
new XFS codebase.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-10-13 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 1:23 Help with xfs and Fedora 8 Ram Natarajan
2011-10-12 23:14 ` Dave Chinner
2011-10-13 10:35 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111013103504.GA16466@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=ram@arohisystems.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox