1
0
mirror of https://github.com/DoctorWkt/unix-jun72.git synced 2026-01-24 03:26:49 +00:00
2008-04-25 20:30:44 +00:00

141 lines
4.3 KiB
Plaintext

Original Source:
http://www.bitsavers.org/pdf/bellLabs/unix/PreliminaryUnixImplementationDocument_Jun72.pdf
------
I started with the pdf, using Preview in mac I selected regions and
copied and created new doc, saved it as jpeg and then used
the online OCR program: http://asv.aso.ecei.tohoku.ac.jp/tesseract/
I then manually edited each file.
The files are named according to the page index in the pdf and the
section and page given in the page footer. Page headers and footers
were not captured.
------------------
e00-01 to e00-10 (10) - u0 -
assigned: tim newsham, complete
reviewed:
e01-01 to e01-10 (10) - u1 -
assigned: Hellwig Geisse
reviewed:
e02-01 to e02-10 (10) - u2 -
assigned: Brantley Coile
reviewed:
e03-01 to e03-04 (4) - u3 -
assigned: Tim Bradshaw
reviewed:
e04-01 to e04-07 (7) - u4 -
assigned: Alex Garbutt
reviewed:
e05-01 to e05-06 (6) - u5 -
assigned: Ralph Logan, complete
reviewed:
e06-01 to e06-06 (6) - u6 -
assigned: johan beisser
reviewed:
e07-01 to e07-08 (8) - u7 -
assigned: Naoki Hamada
reviewed:
e08-01 to e08-09 (9) - u8 -
assigned: Christian David
reviewed:
e09-01 to e09-08 (8) - u9 -
assigned: tim newsham
reviewed:
e10-01 to e10-02 (2) - ux -
assigned: tim newsham, complete
reviewed:
e11-01 to e11-07 (7) - sh
we have a binary for the sh already I think. this may be optional
assigned:
reviewed:
e12-01 to e12-04 (4) - init
we have a binary for init already
assigned:
reviewed:
------------------
e00-01
- I used spaces to line up the comment columns, not tabs. I
picked the column distance arbitrarily.
- the bottom section looks like it could be tabbed but my tabstops
didnt line up with the values given so I used spaces
e00-02
- I used tabs for the start of each asm command but not for the
separation between mnemonic and arguments since these didnt line up.
with my tab stops.
e00-03
- left "dis addresses" typo in per original
e00-05
- cant tell if the "O" in quotes after 1: is a O or a 0.
- left mispelled "mormally" in comment
- left "file/etc/init" without space.
e00-06
- left mis-spacing on 5: move r5,r1.
e00-10
- left "/ect/init" typo
--------------------
I noticed that "inode" and "i-node" were used interchangably, which could possibly
indicate two different people commenting the code. I left each as the original.
e05-01
- line 9 has a crossed out term, so i used the correction "r2"
e05-01
- line 48 comment says "panic / found no tres storage" - left it as "tres"
no idea whether it is supposed to be "tree", "free", or "tres"
e05-04
- some of the latter parts of the code have comments "/ ?", left as is
e05-05
- looks like some of the comments contain a "does not equal symbol" manually
created by typing =<backspace>/. I symbolized it with "=/".
--------------------
e06:
- Used tabs between sections of code instead of spaces.
For example:
bpn rtty0 / comment
This may need some review later. I'll go over it again this afternoon.
--------------------
e09-01
- I'm using tabs between opcode and operands now
- left "bic $!77,r1" although written comment says "? !177"
e09-02
- left "movb tty+38r0),r1" as is. There's a write in
correction for "(" instead of "8". This concerns me as it
means there are probably some errors in this listing as
the paren is most likely the right character here.
e09-03
- hard to tell due to hand written correction, but I believe
the line before "rts r0" reads "mov (sp)+,r0"
- comment "ASC11" (one instead of I) left as is.
e09-04
- text comment says a label was lost! leaving it out for now.
- correction "if count >=0" obscures original text in comment.
no choice but to use new text.
- "ASC11" sic
e09-05
- 5th to last "byte" line 2nd column is uneadable. pattern suggests
the value "000"
--------------------
e10-01
e10-02
- I used tabs for the first tab stop and spaced out to the next step.
- Per discussions with Brantley Coile it appears that the origianl
source probably used tabs, and that the printout has a tab stop
after 8 characters and another after 7 characters. The spaces
between opcode and operands are probably due to a tab, as can be
seen in later assembly code we have in machine readable form.