The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com
To: "Jacob Ritorto" <jacob.ritorto@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] as(1) on Ultrix-11 vs 2.11BSD
Date: Tue, 28 Apr 2020 20:54:24 -0400	[thread overview]
Message-ID: <f8918b56d0077b179ec08e893bdde5b1.squirrel@squirrelmail.tuffmail.net> (raw)
In-Reply-To: <CAHYQbfBPgLKLGeGL=wLBQLOhXqLd0AfpRZOpfJi_7hjo2aYc3w@mail.gmail.com>

Yes, the calling sequence changes were in the back of my mind, but
fortunately the TUHS source archives allowed me to easily look at the
kernel source to see how the arguments were passed.     Somewhere between
2.8 and 2.11 they changed it.   Again, 2.11 was one fo the first attempts
to formalize a true "multi platform" kernel rather than just copying over
the kernel and reworking it for a new machine from a seperate source
"tree."

Yes, your code takes the return of the write system call and uses it as
the exit code.   Not that it makes too much difference.   My 2.11 version
of your code passes a zero explicitly.

Amusingly, speaking of college courses.    I had early on joined the UNIX
systems programming team at JHU and had also done some custom work for
various PDP-11 sites on campus (DOS/BATCH, RT-11, etc...).    PDP-11
assembler was something I knew well.    The head of the EE department told
me he'd be very disappointed if I actually signed up for his PDP-11
assembler programming course my senior year.    Oddly, this caused some
consternation with the faculty committee approving my graduation as I
hadn't taken it and it was required.

Our department UNIX machine as a PDP-11/45 running a high modified V6
kernel.   I also got one of the early 11/23's and we brought up the same
software on that.    A year after I graduated, I was attending a DEC
announcement on the T-11 (I think the first single chip PDP-11).    The
speaker says it had all the instructions with the exception of MARK.   Me
and one other guy are going, "What?   No MARK instruction?"    MARK was
the most useless instruction concocted and it wouldn't even work on an
executable that was set up split I/D.



  reply	other threads:[~2020-04-29  0:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28  1:56 Jacob Ritorto
2020-04-28 13:03 ` Ronald Natalie
2020-04-29  0:17   ` Jacob Ritorto
2020-04-29  0:54     ` ron [this message]
2020-04-29  2:26 Noel Chiappa
2020-04-29  4:08 ` Jacob Ritorto
2020-04-29 12:20   ` Ronald Natalie
2020-04-29 13:55 Paul Ruizendaal
2020-04-29 14:18 ` ron
2020-04-30 21:49   ` Alexander Voropay
2020-04-30 22:06     ` Clem Cole
2020-04-30 22:09       ` Clem Cole
2020-05-01  0:12     ` Ronald Natalie

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=f8918b56d0077b179ec08e893bdde5b1.squirrel@squirrelmail.tuffmail.net \
    --to=ron@ronnatalie.com \
    --cc=jacob.ritorto@gmail.com \
    --cc=tuhs@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).