The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Early Unix Spider network
Date: Sat, 27 May 2017 09:52:59 -0400 (EDT)	[thread overview]
Message-ID: <20170527135259.2EB4418C0A1@mercury.lcs.mit.edu> (raw)

    > From: Paul Ruizendaal

    >>> The report I have is: "SPIDER-a data communication experiment"
    >>> ...
    >>> I think it can be public now, but doing some checks.

OK, that would be great to have online. I _think_ the hardcopy I have
(somewhere! :-) is that report, but my memory should not be trusted.

The people working on TCP/IP did know of the Spider work (like they knew of
the Cambridge ring work), but it didn't really have any impact; it was a
totally different direction than the one we were going in.


    >>> it turns out that the TIU driver was in Warren's repo all along:

V4?! Wow. I'd have never guessed it went that far back.


    >>> The code calls snstat()

    >> The object code for snstat() is in libc.a in the dmr's V5 image.
    >> Reconstructed, the source code is here:
    >> ...
    >> In short, snstat() is a modified stty call

Yes, I looked and found the original source, appended below.


    >>> Could that be the tiu sys call (#45) in the sysent.c table for V4-V6?

I wonder if we'll ever be able to find a copy of the kernel code for that
tiu() system call. And I wonder what it did?


    > [1] Oldest alarm() code I can find is in PWB1
    > ...
    > Either alarm existed in V5 and V6 .. or is was added after V6 was
    > released, perhaps soon after. In the latter case the 'nfs' code that we
    > have must be later than 1974

Remember, that source came from the MIT system, which is a modified PWB1.
So it's not surprising it's using PWB1 system calls.

	Noel


--------

/ C interface to spider status call

.globl  _snstat
.globl  cerror

_snstat:
        mov     r5,-(sp)
        mov     sp,r5
        mov     4(r5),r0
        mov     6(r5),0f
        mov     8(r5),0f+2
        sys     stty; 0f
        bec     1f
        jmp     cerror
1:
        clr     r0
        mov     (sp)+,r5
        rts     pc

.data
0:      .=.+6



             reply	other threads:[~2017-05-27 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-27 13:52 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-05-29  9:54 Paul Ruizendaal
2017-05-26 19:08 Paul Ruizendaal
     [not found] <mailman.880.1495676169.3779.tuhs@minnie.tuhs.org>
2017-05-25 19:31 ` Paul Ruizendaal

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=20170527135259.2EB4418C0A1@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).