The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Andreas Grapentin <andreas.grapentin@hpi.uni-potsdam.de>
To: <tuhs@minnie.tuhs.org>, Jason Stevens <jsteve@superglobalmegacorp.com>
Subject: Re: [TUHS] CMU Mach sources?
Date: Tue, 25 Jun 2019 09:59:40 +0200	[thread overview]
Message-ID: <20190625075940.GA2646@parabola-pocket.localdomain> (raw)
In-Reply-To: <f0a73e06-b6e3-44bd-9862-256b205f6786@PU1APC01FT022.eop-APC01.prod.protection.outlook.com>

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


Amazing, thanks for sharing!

Best,
Andreas

On Tue, Jun 25, 2019 at 03:49:57PM +0800, Jason Stevens wrote:
> Well hot on the heels of the SUN-3 version of Mach25 I managed to figure out enough of the wedge issues for the 386 directory on the CSRG CD set and got it to compile!
> 
> I put up a non HTTPS server on port 8080 for people with http only access to this stuff..
> 
> http://vpsland.superglobalmegacorp.com:8080/install/Mach/mach25-i386.tar.gz
> 
> I apologize for the 404 & password craziness but the whole story is in the 404 page.  It’s so annoying, but here we are in the world of anonymous virus scans and skittish data centres.
> 
> I’m using the aforementioned MtXinu (http://vpsland.superglobalmegacorp.com:8080/install/Mach/MtXinu/) Mach386 to build this stuff.  I haven’t looked at cross compiling from anything yet at the moment.
> 
> Gzip -dc & tar -xvf this somewhere with space (/usr/src?)
> 
> The Makefile bombs while running config on the source, I don’t immediately see where it fails, but it’s easy enough to just CD into the directory run config , cd out & re-run make…
> 
>        cd mach25-i386
>        bash# sh build.sh
> 
> and it'll do the build dance....
> 
> cc -c -O -MD  -DCMU -DINET -DMACH -DAT386 -DCMUCS -DKERNEL -fno-function-cse ../../i386at/pic_isa.c;  ;  ;
> cc -c -O -MD  -DCMU -DINET -DMACH -DAT386 -DCMUCS -DKERNEL -fno-function-cse ../../i386at/rtc.c;  ;  ;
> cc -c -O -MD  -DCMU -DINET -DMACH -DAT386 -DCMUCS -DKERNEL -fno-function-cse ../../i386at/wt.c;  ;  ;
> grep -v '^#' ../../machine/symbols.raw  | sed 's/^      //' | sort -u > symbols.tmp
> mv -f symbols.tmp symbols.sort
> cc -c -O -MD  -DCMU -DINET -DMACH -DAT386 -DCMUCS -DKERNEL -fno-function-cse ../../machine/swapgeneric.c
> (null command)
> (null command)
> (null command)
> vers.config: No such file or directory
> loading vmunix.sys
> rearranging symbols
> text    data    bss     dec     hex
> 442336  46776   115216  604328  938a8
> ln vmunix.sys vmunix; ln vmunix vmunix.I386x.
> md -f -d `ls *.d`
> 
> 
> 
> So yeah, turns out both trees are buildable!  who knew?!  It's certainly not easy to figure out or anything close to self explanatory.
> 
> I had to copy some files from the 'other' SUN-3 complete Mach.
> 
> --
>        cp /usr/src/mach25/sys/Makeconf .
>        cp /usr/src/mach25/sys/Makefile .
>        cp /usr/src/mach25/sys/conf/newvers.sh conf
> 
> 
> To get anywhere with this.  So weird that they were missing.
> 
> I'm working on the boot sector stuff, looks like the stuff I build is too big, and I’m trying to work with the pre-built stuff.
> 
> 
>        mkfs /dev/rfloppy 2880 18 2 4096 512 32 1
>        dd if=boot.hd of=/dev/rfd0c
>        fsck /dev/rfd0a
>        mount /dev/floppy /mnt
> 
> I'd like to think I'm getting close. close to something. ... lol
> 
> I’m not sure if this is so off topic, or noise?  Anyways I’ll keep updating unless told otherwise.
> 
> From: Chris Hanson
> 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
> 

-- 

------------------------------------------------------------------------------
Andreas Grapentin, M.Sc.          Research Assistant @ Hasso-Plattner-Institut
Operating Systems and Middleware Group              www.dcl.hpi.uni-potsdam.de
Phone: +49 (0) 331 55 09-238                        Fax: +49 (0) 331 55 09-229
my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
------------------------------------------------------------------------------

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-06-25  8:09 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
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 [this message]
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=20190625075940.GA2646@parabola-pocket.localdomain \
    --to=andreas.grapentin@hpi.uni-potsdam.de \
    --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).