The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Some resources for V6/PDP/SIMH newbs like me
Date: Mon, 20 Nov 2017 18:08:06 -0500 (EST)	[thread overview]
Message-ID: <20171120230806.985CA18C0A1@mercury.lcs.mit.edu> (raw)

    > From: Will Senn

    > (e) UNIX assembler uses the characters $ and "*" where the DEC 
    > assemblers use "#" and "@" respectively.

Amusing: the "UNIX Assembler Reference Manual" says:

  The syntax of the address forms is identical to that in DEC assemblers,
  except that "*" has been substituted for "@" and "$" for "#"; the
  UNIX typing conventions make "@" and "#" rather inconvenient.

What's amusing is that in almost 40 years, it had never dawned on me that
_that_ was why they'd made the @->*, etc change! "Duhhhh" indeed!

Interesting side note: the UNIX erase/kill characters are described as being
the same as Multics', but since Bell pulled out of the Multics project fairly
early, I wonder if they'd used it long enough to get '@' and '#' hardwired
into their fingers. So I recently has the thought 'Multics was a follow-on to
CTSS, maybe CTSS used the same characters, and that's how they got burned in'.
So I looked in the "CTSS Programmer's Guide" (2nd edition), and no, according
to it (pg. AC.2.02), the erase and kill characters on CTSS were '"' and
'?'. So, so much for that theory!


    > (l) The names "_edata" and "_end" are loader pseudo variables which 
    > define the size of the data segment, and the data segment plus the bss 
    > segment respectively.

That one threw me, too, when I first started looking at the kernel!

I don't recall if I found documentation about it, or just worked it out: it is
in the UPM, although not in ld(1) like one might expect (at least, not in the
V6 UPM; although in V7: 

  http://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/man/man1/ld.1

it is there), but in end(3):

  http://minnie.tuhs.org/cgi-bin/utree.pl?file=V6/usr/man/man3/end.3

	Noel


             reply	other threads:[~2017-11-20 23:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 23:08 Noel Chiappa [this message]
2017-11-21  0:00 ` Ron Natalie
  -- strict thread matches above, loose matches on Subject: below --
2017-11-20 20:01 Noel Chiappa
2017-11-20 19:31 Noel Chiappa
2017-11-20 19:45 ` Will Senn
2017-11-20 19:20 Will Senn
2018-01-09 18:05 ` Wolfgang Helbig
2018-01-14 19:56   ` Will Senn

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=20171120230806.985CA18C0A1@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).