linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Funderburg (at home)" <Chris@Funderburg.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Matt Reppert <arashi@yomerashi.yi.org>,
	Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c
Date: Thu, 06 Feb 2003 00:37:52 +0000	[thread overview]
Message-ID: <3E41AE60.1060106@Funderburg.com> (raw)
In-Reply-To: <20030205233115.GB14131@work.bitmover.com>

On 2/5/2003 11:31 PM, Larry McVoy wrote:
 >>(BTW, Larry, the bk binaries segfault on my (glibc 2.3.1) i686 
system. Any
 >>chance we could see binaries linked against 2.3.x? There's NSS 
badness between
 >>2.2 and 2.3 that causes even static binaries to segfault ... )
 >
 >
 > Yes, NSS in glibc is the world's worst garbage.  Glibc segfaults if there
 > is no /etc/nsswitch.conf.  Nice.
 >
 > We can go buy another machine for glibc2.3, I just need to know what 
redhat
 > release uses that.  If there isn't one, what distro uses that?

Matt,

I _think_ the RedHat glibc2.3 has the NSS patch to avoid this problem.
If you're into rolling your own you can find some info here:

http://www.linuxfromscratch.org/view/cvs/chapter06/glibc.html

I wanted to to run the newest version of glibc on my LFS machine, and
had to start from scratch (again) because of this.



  parent reply	other threads:[~2003-02-06  0:29 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           ` Chris Funderburg (at home) [this message]
2003-02-06  0:45           ` 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c Alan Cox
2003-02-05 23:51             ` Larry McVoy
2003-02-06  0:02               ` Mitch Adair
2003-02-06  0:08                 ` Larry McVoy
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=3E41AE60.1060106@Funderburg.com \
    --to=chris@funderburg.com \
    --cc=akpm@digeo.com \
    --cc=arashi@yomerashi.yi.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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;
as well as URLs for NNTP newsgroup(s).