All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Christoph Hellwig <hch@infradead.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	rdunlap@xenotime.net
Subject: Re: RFC: Schedule EFS for removal.
Date: Tue, 22 May 2007 18:49:00 -0400	[thread overview]
Message-ID: <20070522224900.GE22628@redhat.com> (raw)
In-Reply-To: <20070522210152.GM943@1wt.eu>

On Tue, May 22, 2007 at 11:01:54PM +0200, Willy Tarreau wrote:

 > >  > > "Under 2.4.21, it doesnt do this."
 > >  > 
 > >  > Randy mentioned in bugzilla that 2.4.22 didn't work either, so I'd
 > >  > be very surprised if 2.4.21 works.
 > > 
 > > good point.  I don't see anything obvious in 2.4.22 that would have
 > > caused a regression, so this sounds suspect.
 > > I'll close the bugzilla out based on your comments, thanks for looking at it.
 > 
 > In my experience, often when people speak about 2.4.21 (which is quite old),
 > they in fact refer to an RHEL3 kernel, which has a "few" addon patches :-)
 > While I don't think that anything related to EFS might be changed in RHEL,
 > may it be possible that it works as a side effect of a patch in this
 > kernel ?
 > 
 > That's just pure guess anyway.

not unless it's a recompiled version.  As shipped, RHEL3 has..

# CONFIG_EFS_FS is not set

	Dave

-- 
http://www.codemonkey.org.uk

      reply	other threads:[~2007-05-22 22:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 14:46 RFC: Schedule EFS for removal Dave Jones
2007-05-21 15:02 ` Christoph Hellwig
2007-05-21 15:09   ` Dave Jones
2007-05-21 15:12     ` Christoph Hellwig
2007-05-21 15:20       ` Dave Jones
2007-05-21 15:46         ` Christoph Hellwig
2007-05-21 17:11           ` Dave Jones
2007-05-21 17:12             ` Christoph Hellwig
2007-05-21 17:25               ` Randy Dunlap
2007-05-22 21:01             ` Willy Tarreau
2007-05-22 22:49               ` Dave Jones [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=20070522224900.GE22628@redhat.com \
    --to=davej@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=w@1wt.eu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.