From: spedraja@gmail.com (Sergio Pedraja)
Subject: [Unix-jun72] Semi-OT: Other systems to reconstruct?
Date: Thu, 22 May 2008 18:52:36 +0200 [thread overview]
Message-ID: <f7f1e0d30805220952s765c2082h5d8380c459f97d3c@mail.gmail.com> (raw)
In-Reply-To: <483598D0.8070009@bitsavers.org>
Stretch ? Where ? :-)
But Seriously, this would be particularly a goal similar to CTSS. About the
SDS... Where can be obtained the sources ? Is it the SIMH a good way to do
this job ?
Greetings
Sergio
2008/5/22 Al Kossow <aek at bitsavers.org>:
> Andrew Warkentin wrote:
> > With the successful restoration of Unix V1, I was thinking of other
> > operating systems that could be restored in a similar way.
>
> There is no shortage of systems that could be worked on.
> The Berkeley GENIE SDS 940 system, for example. Machine readable
> sources exist, but no drum image, so it would have to be reassembled
> from the existing binaries, and cross-assembled to get the rest.
>
> I'm hoping to recover a bunch of system tapes for the B5700 soon.
>
> Someone else I know has been trying to get the Stretch system software
> running again from listings.
>
>
> _______________________________________________
> Unix-jun72 mailing list
> Unix-jun72 at tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/unix-jun72
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20080522/c9bae3e3/attachment.html>
next prev parent reply other threads:[~2008-05-22 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 3:05 Andrew Warkentin
2008-05-22 16:01 ` Al Kossow
2008-05-22 16:52 ` Sergio Pedraja [this message]
2008-06-06 12:37 ` Jose R. Valverde
2008-06-07 1:49 ` Doug Merritt
2008-06-08 4:06 ` [Unix-jun72] DEC 10 for sale on ebay Doug Merritt
2008-06-09 18:52 ` Milo Velimirovic
2008-06-09 20:36 ` Brad Parker
2008-06-09 19:51 ` Al Kossow
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=f7f1e0d30805220952s765c2082h5d8380c459f97d3c@mail.gmail.com \
--to=spedraja@gmail.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).