From: Martin Schlemmer <azarah@gentoo.org>
To: Christopher Li <chrisl@vmware.com>
Cc: KML <linux-kernel@vger.kernel.org>,
akpm@digeo.com, adilger@clusterfs.com, ext3-users@redhat.com,
x86-kernel@gentoo.org
Subject: RE: [2.6] Perl weirdness with ext3 and HTREE
Date: 06 Aug 2003 00:08:23 +0200 [thread overview]
Message-ID: <1060121303.8355.47.camel@nosferatu.lan> (raw)
In-Reply-To: <68F326C497FDB743B5F844B776C9B1460976FD@pa-exch4.vmware.com>
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
On Tue, 2003-08-05 at 23:53, Christopher Li wrote:
> >
> > I cannot really see that it is a Gentoo specific problem, but
> > who knows.
> > I will try to get a CD of another distro somewhere, and get that on a
> > box to test - currently work/whatnot just keeps me pretty tied up :(
> > Another reason why I posted, is now that 2.6 is more widely
> > used/tested,
> > its not only me that gets this, but other users as well - thus I hoped
> > that somebody with more time wanted to have a crack at it.
>
> I am not claiming it is a gentoo issue. I just want to duplicate
> this bug with minimal damage to my box.
>
Yep, I know, I just 'clarified' it in case somebody was wondering.
> >
> > If it works fine (with a 2.6 kernel), I will go and bang my
> > head against
> > a wall, and shutup until I can make time to try and track
> > this - if not,
> > any ideas as to creating it outside the perl install (or
> > rather the man
> > page part of the install process) would be great.
> >
>
> You can do a strace on the perl install, then grep for all
> the file changes happen on that directory. There is a good
> chance follow the strace log can duplicate the bug also.
Yep, did that. I had a simple c program once that tried to
simulate all file operations on that file, and the 'real'
man page that gets installed. Did not have the same effect
however. Might be that I was off by something. Don't have
it however anymore, as it was some months before, just before
I mailed the first time.
Thanks,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-05 22:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 21:53 [2.6] Perl weirdness with ext3 and HTREE Christopher Li
2003-08-05 22:08 ` Martin Schlemmer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-08 19:50 Christopher Li
2003-08-06 20:22 Christopher Li
2003-08-06 22:28 ` Martin Schlemmer
2003-08-05 22:40 Christopher Li
2003-08-02 20:37 Martin Schlemmer
2003-08-03 7:01 ` Danek Duvall
[not found] ` <m365lfgpob.fsf@bzzz.home.net>
2003-08-03 12:51 ` Martin Schlemmer
2003-08-05 18:28 ` Christopher Li
2003-08-05 19:23 ` Martin Schlemmer
2003-08-06 1:03 ` Patrick McLean
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=1060121303.8355.47.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=adilger@clusterfs.com \
--cc=akpm@digeo.com \
--cc=chrisl@vmware.com \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86-kernel@gentoo.org \
/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