The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jsteve@superglobalmegacorp.com (jsteve@superglobalmegacorp.com)
Subject: [TUHS] Reorganising the Unix Archive? (GNU?)
Date: Mon, 20 Feb 2017 17:59:32 +0800	[thread overview]
Message-ID: <c749e965-732e-49a7-8c29-3cf3e5f47990@SG2APC01FT012.eop-APC01.prod.protection.outlook.com> (raw)
In-Reply-To: <201702200908.v1K983DP011135@freefriends.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2037 bytes --]

I recently found out that vim.org of all places had a copy of GCC 0.9, which was the first public version, to support the VAX & 68020 SUN platforms of the time.

http://ftp.vim.org/languages/gcc/old-releases/gcc-1/

I built it on SIMH + 4.2BSD VAX along with the ‘gnu1988’ along with other gems like bison 1.00, flex 1.0 .. and it was a lot more unstable than I was expecting, the next oldest version is 1.21 which adds more platforms, and some much needed stability.  I know it’s old, but it’s funny how pro SUN they were at the time.

Sent from Mail for Windows 10

From: arnold@skeeve.com
Sent: Tuesday, 21 February 2017 5:23 PM
To: wkt at tuhs.org; jsteve at superglobalmegacorp.com
Cc: tuhs at tuhs.org
Subject: Re: [TUHS] Reorganising the Unix Archive? (GNU?)

There's a fair amount of stuff on ftp.gnu.org itself.  The FSF
used to make tapes and CDs; perhaps they still have some laying around?

I'm not sure who to ask there, though, although I could try to find
someone.

Arnold

Jason Stevens <jsteve at superglobalmegacorp.com> wrote:

> I've been on again and off again collecting stuff...  What I've found I've put on source forge since it's easier to upload binaries there.  Same for Linux, while there is an ancient Linux site, all it's mirrors are vanishing
>
> On February 20, 2017 2:50:13 PM GMT+08:00, Warren Toomey <wkt at tuhs.org> wrote:
> >On Mon, Feb 20, 2017 at 02:14:19PM +0800, Jason Stevens wrote:
> >>    I dont know if it's worth even trying to find and mirror pre 1993
> >( IE
> >>    when cheap CD-ROM mastering was possible) GNU software?
> >
> >I'm happy to accept CD images of GNU stuff, but "GNU's not Unix" so it
> >may not be put into the Unix Archive.
> >
> >We do need a GNU historian and curator. Ditto for Linux.
> >
> >Cheers, Warren
>
> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170220/9c9debe8/attachment-0001.html>


  reply	other threads:[~2017-02-20  9:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20  6:14 Jason Stevens
2017-02-20  6:50 ` Warren Toomey
2017-02-20  7:00   ` Nick Downing
2017-02-20  7:23   ` Jason Stevens
2017-02-20  9:08     ` arnold
2017-02-20  9:59       ` jsteve [this message]
2017-02-20 11:12         ` arnold
2017-02-20 16:46           ` Deborah Scherrer
2017-02-20 18:27             ` arnold
2017-02-20 18:37               ` Deborah Scherrer
2017-02-20 18:56                 ` arnold
2017-02-20 19:46             ` Brantley Coile
2017-02-20  7:10 ` Lars Brinkhoff
2017-02-20  7:19   ` Jason Stevens

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=c749e965-732e-49a7-8c29-3cf3e5f47990@SG2APC01FT012.eop-APC01.prod.protection.outlook.com \
    --to=jsteve@superglobalmegacorp.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).