From: Larry McVoy <lm@bitmover.com>
To: Mitch Adair <mitch@theneteffect.com>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c
Date: Wed, 5 Feb 2003 16:08:58 -0800 [thread overview]
Message-ID: <20030206000858.GC21064@work.bitmover.com> (raw)
In-Reply-To: <200302060002.SAA28514@mako.theneteffect.com>
> "I will let someone know so they can fix it. Shazam!"
Hmm, while I think that glibc should be fixed my general response is that
you shouldn't be running a statically linked version, which is probably
the cause of the guy's problems. Both our experience and lots of user
experience is that if you run the glibc2.2 version on a glibc2.3 system
it works fine.
The only reason we made a statically linked version available was for
Richard Gooch who insisted on maintaining his own a.out based distro.
I haven't heard from him in months so I'll nuke that image and maybe
the problem is gone.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-02-05 23:59 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 17:40 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c Andrea Arcangeli
2003-02-05 18:23 ` Andrew Morton
2003-02-05 18:45 ` Andrea Arcangeli
2003-02-05 19:42 ` Dave Jones
2003-02-05 20:06 ` Andrea Arcangeli
2003-02-05 19:43 ` Andrew Morton
2003-02-05 19:51 ` Andrea Arcangeli
2003-02-05 20:09 ` Andrew Morton
2003-02-05 20:18 ` Andrea Arcangeli
2003-02-05 20:33 ` Andrew Morton
2003-02-05 23:29 ` Larry McVoy
2003-02-05 20:11 ` Matt Reppert
2003-02-05 20:24 ` Andrea Arcangeli
2003-02-05 20:56 ` Linus Torvalds
2003-02-05 20:25 ` Linus Torvalds
2003-02-05 23:31 ` Larry McVoy
2003-02-05 23:37 ` Christoph Hellwig
2003-02-05 23:57 ` Larry McVoy
2003-02-06 0:22 ` Robert Love
2003-02-06 16:58 ` Andreas Dilger
2003-02-06 17:30 ` Larry McVoy
2003-02-06 17:55 ` Matt Reppert
2003-02-07 16:18 ` glibc-2.3 [Was: Re: 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c] Horst von Brand
2003-02-07 18:06 ` Larry McVoy
2003-02-06 0:37 ` 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c Chris Funderburg (at home)
2003-02-06 0:45 ` Alan Cox
2003-02-05 23:51 ` Larry McVoy
2003-02-06 0:02 ` Mitch Adair
2003-02-06 0:08 ` Larry McVoy [this message]
2003-02-06 10:02 ` Nick Craig-Wood
2003-02-09 18:37 ` Kenneth Johansson
2003-02-05 19:46 ` Sam Ravnborg
2003-02-05 20:04 ` Dave Kleikamp
2003-02-05 20:10 ` Andrea Arcangeli
2003-02-05 20:16 ` Dave Kleikamp
2003-02-05 20:34 ` Sam Ravnborg
2003-02-05 20:51 ` Andrea Arcangeli
2003-02-05 22:09 ` Linus Torvalds
2003-02-06 10:46 ` Roman Zippel
2003-02-06 11:09 ` Andreas Schwab
2003-02-05 21:56 ` Linus Torvalds
2003-02-07 14:56 ` Pavel Machek
2003-02-08 18:28 ` Larry McVoy
2003-02-08 19:36 ` Martin J. Bligh
2003-02-09 10:57 ` Pavel Machek
2003-02-09 14:15 ` Andrea Arcangeli
2003-02-13 1:50 ` Jamie Lokier
2003-02-13 1:57 ` Jamie Lokier
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=20030206000858.GC21064@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitch@theneteffect.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