The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Lars Brinkhoff <lars@nocrew.org>
To: John Floren <john@jfloren.net>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] head/sed/tail (was The Unix shell: a 50-year view)
Date: Fri, 16 Jul 2021 08:27:17 +0000	[thread overview]
Message-ID: <7w8s26pst6.fsf@junk.nocrew.org> (raw)
In-Reply-To: <hnYS2RW60oBvlvcvoqNGbwEJCtOEHmclm_z1B_Od-Kc_vHLWpHYtHvFR5cVoNWdJXxy0h_3P8lFT-gAb2pO8BhHxGUtQ_-QmuFCuc2g9G2k=@jfloren.net> (John Floren's message of "Fri, 16 Jul 2021 00:02:21 +0000")

John Floren wrote:
> Speaking of SAIL (and I suppose further derailing an already derailed
> discussion), I've occasionally looked for more information about the
> environment (typically whenever a book or article briefly mentions
> SAIL as a place with lots of custom hardware and software) but come up
> with little. Anyone know of good description of SAIL computer systems?

I'm risking the Wrath of the Moderator here, but I really want to supply
some information.  Sorry, this is very far from Unix.  But hey, SUDS was
used to design the Stanford SUN Unix workstation.

What do you mean with "SAIL computer systems"?  I think upthread SAIL
was referencing the Algol compiler written at the Stanford AI lab.  But
SAIL was also an acronym for the entire lab, AND also used as a name for
the main timesharing computer hardware.  The hardware was first a PDP-6,
then adding a PDP-10 (KA10), then a KL10.  The operating system was
eventually named WAITS, but was also sometimes called SAIL or just
SYSTEM.  WAITS was also run on two Foonlies at other sites, and those
could also be called SAIL computer systems in some sense.

I gather you probably mean the AI lab and its computers.  The best place
for information is saildart.org, and Bruce Baumgart is working on a tome
called "SAILDART_Prolegomenon".  This work in progress is 116 pages.
https://github.com/PDP-10/waits/blob/master/doc/SAILDART_Prolegomenon_2016.pdf

  parent reply	other threads:[~2021-07-16  9:02 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 22:26 Nelson H. F. Beebe
2021-07-15 23:18 ` Jim Davis
2021-07-16  0:02   ` John Floren
2021-07-16  1:02     ` Nelson H. F. Beebe
2021-07-16  8:27     ` Lars Brinkhoff [this message]
2021-07-16 15:28       ` John Floren
2021-07-16  0:02 ` Clem Cole
2021-07-16  0:25   ` Nelson H. F. Beebe
2021-07-16  8:50     ` Lars Brinkhoff
  -- strict thread matches above, loose matches on Subject: below --
2021-07-18 20:07 Douglas McIlroy
     [not found] <CAKH6PiW58PDPb5HRi12aKE+mT+O8AjETr9R51Db6U3KcEp_KkA@mail.gmail.com>
2021-07-16 14:17 ` Nelson H. F. Beebe
2021-07-16 16:13   ` Theodore Y. Ts'o
2021-07-16 12:09 Douglas McIlroy
2021-07-16 14:32 ` Bakul Shah
2021-07-15 22:00 Douglas McIlroy
2021-07-15 22:12 ` John Cowan
2021-07-15 21:26 Paul Ruizendaal
2021-07-15 19:01 Norman Wilson
2021-07-15 19:27 ` Clem Cole
2021-07-15 19:28   ` Clem Cole
2021-07-15 19:34   ` Warner Losh
2021-07-16  7:38     ` arnold
2021-07-16 16:09       ` Warner Losh
2021-07-16  8:05   ` Lars Brinkhoff
2021-07-16 14:19     ` Clem Cole
2021-07-17  0:34       ` Charles Anthony
2021-07-15 16:54 Nelson H. F. Beebe
2021-07-15 15:44 Norman Wilson
2021-07-15  2:38 Douglas McIlroy
2021-07-15  4:19 ` arnold
2021-07-15  4:25   ` Adam Thornton
2021-07-15  7:20   ` Thomas Paulsen
2021-07-15 14:28 ` Theodore Y. Ts'o
2021-07-15 22:29 ` Bakul Shah

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=7w8s26pst6.fsf@junk.nocrew.org \
    --to=lars@nocrew.org \
    --cc=john@jfloren.net \
    --cc=tuhs@minnie.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).