From: Charles Cazabon <linux@discworld.dyndns.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Mitchell Blank Jr <mitch@sfgoth.com>,
"Giacomo A. Catenazzi" <cate@pixelized.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Eric S. Raymond" <esr@thyrsus.com>
Subject: Re: SCO's infringing files list
Date: Tue, 23 Dec 2003 12:40:24 -0600 [thread overview]
Message-ID: <20031223124024.A30934@discworld.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0312230914090.14184@home.osdl.org>; from torvalds@osdl.org on Tue, Dec 23, 2003 at 09:25:53AM -0800
Linus Torvalds <torvalds@osdl.org> wrote:
>
> Bingo!
[...]
> Can anybody find the actual libc _sources_? Not the kernel headers that
> hjl mentions (those are the old ones from _before_ the change), but the
> file "libc-2.2.2.tar.Z"?
Well, it's been recompressed with gzip, but it's here (among other places):
ftp://ftp.uni-kassel.de/Mirrors/prep.ai.mit.edu/pub/gnu/glibc/glibc-2.2.2.tar.gz
I haven't checked the original GNU/MIT site it was apparently mirrored from,
but it might be there.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <linux@discworld.dyndns.org>
GPL'ed software available at: http://www.qcc.ca/~charlesc/software/
-----------------------------------------------------------------------
next prev parent reply other threads:[~2003-12-23 18:36 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 20:42 SCO's infringing files list Stan Bubrouski
2003-12-22 21:14 ` Joseph Pingenot
2003-12-22 21:23 ` Stan Bubrouski
2003-12-22 21:19 ` Tom Felker
2003-12-22 21:55 ` Linus Torvalds
2003-12-23 0:26 ` jw schultz
2003-12-23 1:17 ` Stan Bubrouski
2003-12-23 9:28 ` Florian Weimer
2003-12-23 9:58 ` Giacomo A. Catenazzi
2003-12-23 12:34 ` Linus Torvalds
2003-12-23 13:17 ` viro
2003-12-23 15:44 ` Giacomo A. Catenazzi
2003-12-23 16:04 ` Mitchell Blank Jr
2003-12-23 16:39 ` Mitchell Blank Jr
2003-12-23 17:25 ` Linus Torvalds
2003-12-23 18:40 ` Charles Cazabon [this message]
2003-12-23 18:44 ` viro
2003-12-23 18:45 ` Mitchell Blank Jr
2003-12-23 18:52 ` Matti Aarnio
2003-12-23 19:58 ` Shawn
2003-12-23 20:08 ` Stan Bubrouski
2003-12-23 20:25 ` John Shifflett
2004-01-02 19:45 ` Bill Davidsen
2003-12-23 18:47 ` Steven Cole
2003-12-23 20:06 ` Mitchell Blank Jr
2003-12-23 17:44 ` Mitchell Blank Jr
2003-12-23 17:56 ` Linus Torvalds
2003-12-23 18:12 ` Stan Bubrouski
2003-12-23 18:14 ` Harry McGregor
2003-12-23 18:27 ` Stan Bubrouski
2003-12-23 18:40 ` Disconnect
2003-12-23 18:14 ` Stan Bubrouski
2003-12-23 19:02 ` Stan Bubrouski
2003-12-23 19:06 ` Andries Brouwer
2003-12-23 20:18 ` Stan Bubrouski
2003-12-23 20:21 ` Mitchell Blank Jr
2003-12-23 20:27 ` Linus Torvalds
2003-12-23 23:56 ` [OT] " Thomas Zehetbauer
2003-12-24 0:15 ` Stan Bubrouski
2003-12-23 16:15 ` venom
2003-12-23 15:50 ` Mitchell Blank Jr
2003-12-23 17:07 ` Andries Brouwer
2003-12-22 23:52 ` Erik Andersen
2003-12-22 23:01 ` Jesper Juhl
2003-12-23 11:18 ` Luiz Fernando Capitulino
2003-12-23 4:50 ` David Schwartz
2003-12-23 15:43 Xose Vazquez Perez
2003-12-23 15:46 jpo234
2003-12-23 18:49 jpo234
2003-12-24 12:19 Norman Diamond
2003-12-24 13:11 ` Jussi Laako
[not found] <no.id>
2003-12-28 7:04 ` Rick Bressler
2003-12-30 14:17 Bruno Haible
2003-12-30 17:27 ` Stan Bubrouski
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=20031223124024.A30934@discworld.dyndns.org \
--to=linux@discworld.dyndns.org \
--cc=cate@pixelized.ch \
--cc=esr@thyrsus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitch@sfgoth.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).