From: cubexyz@gmail.com (Mark Longridge)
Subject: [TUHS] recreating bj.s for Unix v5
Date: Fri, 12 Jun 2015 15:01:51 -0400 [thread overview]
Message-ID: <CADxT5N4M_=DWC86R=JpKuKa+wt5HRb22Y9XVM3SkfvGff6UnAw@mail.gmail.com> (raw)
In-Reply-To: <20150612183937.00ECF18C0BE@mercury.lcs.mit.edu>
Here it is:
http://www.maxhost.org/other/unix-v5-bj-pdp-11-executable
Judging by it's small size I figure the original code was assembly language.
On 6/12/15, Noel Chiappa <jnc at mercury.lcs.mit.edu> wrote:
> > From: Mark Longridge <cubexyz at gmail.com>
>
> > My first idea was to grab bj.s from 2.11BSD and assemble it the Unix
> v5
> > as command. That seems to generate a bunch of errors. Also other
> > assembly source files don't seem to have .even in them.
>
> My first question was going to be 'Maybe try an earlier version of the
> source?', but I see there is no earlier version online. Odd. ISTR that some
> of the fun things in V6 came without source, maybe blackjack was the same
> way?
>
> > Another idea would be generate the source code from the executable
> > itself, but there doesn't seem to be a disassembler for early Unix.
>
> Where's the binary? I'd like to take a look at it, and see if the source
> was
> assembler, or C (there's a C version in the source tree, too). Then I can
> look and see how close it is to that 2.11 source - that may be a
> re-implementation, and totally different.
>
> Noel
>
next prev parent reply other threads:[~2015-06-12 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 18:39 Noel Chiappa
2015-06-12 19:01 ` Mark Longridge [this message]
2015-06-12 22:46 ` Greg 'groggy' Lehey
-- strict thread matches above, loose matches on Subject: below --
2015-06-12 20:00 Noel Chiappa
2015-06-12 20:16 ` Mark Longridge
2015-06-12 19:31 Noel Chiappa
2015-06-12 18:23 Mark Longridge
2015-06-15 5:14 ` Lars Brinkhoff
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='CADxT5N4M_=DWC86R=JpKuKa+wt5HRb22Y9XVM3SkfvGff6UnAw@mail.gmail.com' \
--to=cubexyz@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).