Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Brian Murphy <brian.murphy@eicon.com>, linux-mips@oss.sgi.com
Subject: Re: glibc
Date: Thu, 16 Aug 2001 18:14:19 +0200	[thread overview]
Message-ID: <20010816181419.B30997@bacchus.dhis.org> (raw)
In-Reply-To: <E15XNl1-0005C7-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Aug 16, 2001 at 03:04:23PM +0100

On Thu, Aug 16, 2001 at 03:04:23PM +0100, Alan Cox wrote:

> > We use 2.0.6 here because it is half the size of the newer glibcs and it
> > seems to work fine for us.
> 
> It trust someone patched the holes in it for things like DNS lookups ?

The latest glibc 2.0.6 I was spreading only has MIPS-specific bug fixes.
All the other big holes which are indeed big enough to drive a nice shipload
of trucks through are unfixed.  I haven't noticed that any other glibc
2.0 variant floating around has additional fixes.

Nice for Cobalt boxen ...

  Ralf

  parent reply	other threads:[~2001-08-16 17:49 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <no.id>
2001-07-26  0:20 ` Replacing the Console driver Alan Cox
2001-07-26  0:20   ` Alan Cox
2001-07-26  1:32   ` Ralf Baechle
2001-07-26  1:51     ` William Jhun
2001-08-10 15:59 ` about mips IDE DMA disk problem Alan Cox
2001-08-10 15:59   ` Alan Cox
2001-08-10 18:05   ` Ilya Volynets
2001-08-10 18:05     ` Ilya Volynets
2001-08-10 18:23     ` Ralf Baechle
2001-08-10 18:26       ` Ilya Volynets
2001-08-10 18:41         ` Hartvig Ekner
2001-08-10 19:58           ` Ilya Volynets
2001-08-15 20:58 ` glibc Alan Cox
2001-08-15 20:58   ` glibc Alan Cox
2001-08-16  8:50   ` glibc Brian Murphy
2001-08-16 14:04     ` glibc Alan Cox
2001-08-16 14:04       ` glibc Alan Cox
2001-08-16 16:14       ` Ralf Baechle [this message]
2001-08-16 19:09         ` glibc Martin Michlmayr
2001-08-16 20:05           ` glibc James Simmons
2001-08-16 20:10           ` glibc Soeren Laursen
2001-08-16 16:04     ` glibc H . J . Lu
2001-08-16 17:00       ` glibc Brian Murphy
2001-08-16 21:15         ` glibc H . J . Lu
2002-01-08 23:04 ` Galileo 64240 ellis
2002-03-25 20:37 ` Mips16 toolchain? Hartvig Ekner
2002-05-30 19:36 ` cross-compiler for MIPS_RedHat7.1_Release-01.00 on Atlas/4Kc using RH7.3-i386 host Hartvig Ekner
2002-05-30 19:36   ` Hartvig Ekner
2002-05-30 20:06   ` David Christensen
2002-05-30 20:06     ` David Christensen
2002-05-30 21:05     ` Muthukumar Ratty
2002-05-30 21:05       ` Muthukumar Ratty
2002-05-30 21:25       ` cross-compiler for MIPS_RedHat7.1_Release-01.00 on Atlas/4Kc Hartvig Ekner
2002-05-30 21:25         ` Hartvig Ekner
2002-05-31  0:23       ` cross-compiler for MIPS_RedHat7.1_Release-01.00 on Atlas/4Kc using RH7.3-i386 host David Christensen
2002-05-31  0:23         ` David Christensen
2001-08-15 22:03 glibc Siders, Keith
  -- strict thread matches above, loose matches on Subject: below --
2001-08-15 21:37 glibc Siders, Keith
2001-08-15 21:31 glibc Siders, Keith
2001-08-15 21:38 ` glibc Ilya Volynets
2001-08-15 20:45 glibc Steven Liu
2001-08-15 20:45 ` glibc Steven Liu
2001-08-15 21:05 ` glibc Pete Popov

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=20010816181419.B30997@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=brian.murphy@eicon.com \
    --cc=linux-mips@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