The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Henry Bent <henry.r.bent@gmail.com>
To: Jason Stevens <jsteve@superglobalmegacorp.com>
Cc: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] CMU Mach sources?
Date: Sun, 23 Jun 2019 10:54:44 -0400	[thread overview]
Message-ID: <CAEdTPBeaDesz42GAfbQ-0B12O1VQW44ySgr6ezJpxRZv90BOCA@mail.gmail.com> (raw)
In-Reply-To: <5df8c6f6-2768-4bfb-9c47-3345098078a7@PU1APC01FT048.eop-APC01.prod.protection.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2442 bytes --]

 I know that it's not exactly what was asked for, but DEC's OSF/1 V1.0
source is floating around out there in the ether, which is a fusion of Mach
2.5 and Ultrix 4.2.  It's the original release, for MIPS-based DECstations,
of what eventually became Digital UNIX / Tru64.

-Henry

On Sun, 23 Jun 2019 at 04:05, Jason Stevens <jsteve@superglobalmegacorp.com>
wrote:

> The fractions I've found of the 2.5 is on the CSRG #4 cd
>
> https://vpsland.superglobalmegacorp.com/install/Mach/MACH_CSRG_CD.7z
> <https://vpsland.superglobalmegacorp.com/old/install/Mach/MACH_CSRG_CD.7z>
>
> You have to read the 404 to get the password. It changes frequently.
>
> I've been slowly trying to get 2.5 to build under Mt Xinu BSD/Mach.
>
> I've managed only the tools and bootloader so far.  I've just been busy
> moving offices the last week.
>
> Anyway in that directory is a bunch of other Mach stuff I've found.
>
> I also started trying to map the Mach 3.0 stuff
>
>
> https://unix.superglobalmegacorp.com/cgi-bin/cvsweb.cgi/?sortby=file&only_with_tag=MAIN&hideattic=1&hidenonreadable=1&f=u&logsort=date&cvsroot=Mach3&path=
>
> Including BSDSS a unknown to me port of BSD to Mach 3.
>
> It seems plenty of the Mach 1/2 stuff is hidden on CMU's servers in wait
> of the ATT v CSRG lawsuit.  And that everyone who worked on it left so it's
> locked away hidden.
>
> There is a vmdk of the mt Xinu installed that will run on qemu and most
> likely others as well.  So you can take it out for a test drive
>
>
>
>
>
> *From: *Chris Hanson <cmhanson@eschatologist.net>
> *Sent: *Sunday, June 23, 2019 12:46 PM
> *To: *tuhs@minnie.tuhs.org
> *Subject: *[TUHS] CMU Mach sources?
>
>
>
> Does anyone know whether CMU’s local Mach sources have been preserved?
>
>
>
> I’m not just talking about MK84.default.tar.Z  and so on, I’m talking
> about all the bits of Mach that were used on cluster systems on campus,
> prior to the switch to vendor UNIX.
>
>
>
> I know at least one person who had complete MacMach sources for the last
> version, but threw out the backup discs with the sources in the process of
> moving. So I know they exist.
>
>
>
> If nothing else, CMU did provide other sites their UX source package (eg
> UX42), which was the BSD single server environment. So I know that has to
> be out there, somewhere.
>
>
>
>   — Chris
>
>
>
> Sent from my iPhone
>
>
>

[-- Attachment #2: Type: text/html, Size: 5320 bytes --]

  reply	other threads:[~2019-06-23 14:55 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23  4:38 Chris Hanson
2019-06-23  5:15 ` Larry McVoy
2019-06-23  8:52   ` Andrew Warkentin
2019-06-23 13:39   ` Jon Forrest
2019-06-23 13:59     ` arnold
2019-06-23 14:03     ` Jason Stevens
2019-06-23  8:04 ` Jason Stevens
2019-06-23 14:54   ` Henry Bent [this message]
2019-06-23 21:52     ` Clem Cole
2019-06-25  0:06       ` Larry McVoy
2019-06-25  0:31         ` Theodore Ts'o
2019-06-25  0:45           ` Larry McVoy
2019-06-25  0:55             ` Kurt H Maier
2019-06-25  4:18               ` Larry McVoy
2019-06-26 23:19                 ` [TUHS] Craft vs Research (Re: " Bakul Shah
2019-06-27  0:16                   ` tuhs
2019-06-27 17:06                     ` Clem Cole
2019-06-25  1:00             ` [TUHS] " Richard Salz
2019-06-25  8:00               ` Kevin Bowling
2019-06-25 12:11                 ` Arthur Krewat
2019-06-25 12:17                   ` Arthur Krewat
2019-06-26  2:45               ` Kurt H Maier
2019-06-26  2:56                 ` Larry McVoy
2019-06-26 15:11                   ` Theodore Ts'o
2019-06-26 17:44                     ` Larry McVoy
2019-06-26 18:01                       ` arnold
2019-06-26 18:18                         ` Warner Losh
2019-06-26 19:22                       ` Chris Hanson
2019-06-26 19:32                         ` Ben Greenfield via TUHS
2019-06-26 20:21                           ` Larry McVoy
2019-06-27  0:22                             ` Chris Hanson
2019-06-27  1:02                               ` Larry McVoy
2019-06-27  1:26                                 ` Chris Hanson
2019-06-27  4:01                             ` Lyndon Nerenberg
2019-06-27 10:34                               ` Ben Greenfield via TUHS
2019-06-27 10:59                                 ` arnold
2019-06-27 11:13                                   ` Ben Greenfield via TUHS
2019-06-27 11:39                                     ` arnold
2019-06-27 14:58                                     ` Warner Losh
2019-06-27 17:25                                       ` Larry McVoy
2019-06-26 19:30                       ` Dennis Boone
2019-06-26 19:25                     ` Adam Thornton
2019-06-23  8:27 ` Kevin Bowling
2019-06-25  3:07 ` Gregg Levine
2019-06-25  8:15   ` Kevin Bowling
2019-06-25 18:18   ` Chris Hanson
2019-06-25 20:23     ` Gregg Levine
2019-06-26  1:04       ` Jason Stevens
2019-06-26  0:53     ` Jason Stevens
2019-06-25  7:49 ` Jason Stevens
2019-06-25  7:59   ` Andreas Grapentin
2019-06-23 22:08 Noel Chiappa
2019-06-23 23:54 ` Theodore Ts'o
2019-06-24 17:04   ` Jason Stevens
2019-07-01 13:20 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=CAEdTPBeaDesz42GAfbQ-0B12O1VQW44ySgr6ezJpxRZv90BOCA@mail.gmail.com \
    --to=henry.r.bent@gmail.com \
    --cc=jsteve@superglobalmegacorp.com \
    --cc=tuhs@minnie.tuhs.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).