The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] dmr streams & networking [was: Re: If not Linux, then what?]
Date: Thu, 29 Aug 2019 08:29:03 +1000	[thread overview]
Message-ID: <CAKr6gn1ZHLerb4sODqYzMo8zi82gRAt6RnB3Wjtany8TdD15qg@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgw_OJO6ehq4g=t_cqUw-Pqz_T6gn48uMDuyfpiQqNvOKw@mail.gmail.com>

This is an object lesson in not making assumptions about things. I had
always assumed the V in UNIX 32V stood for something which went to
demand paging, from 'Virtual Addressing'. Turns out: I was wrong.

One other note about sockets: The original 4.2 port had to be used by
a lot of people without the ethernet, because we didn't have the DEC
ethernet card it was written to. This made unix domain sockets very
interesting because you could test in them. Except: the very first
test program somebody wrote at Leeds university to create and write to
a unix domain socket in /tmp crashed the vax. ... (this was around
1982/3) -We were warned off using sockets until the first patch tape
came in the post.

The Berkeley lawyers were amazing. I like to think 'shakespear
witches' or 'evil gnomes' -We had changed staff in some functional
role, and when we came to do licence renewal for the upgrade from 4.1
They insisted we find the mouldering body of the ex appointee and get
them to countersign (press the dead flesh in a pot of ink and put on
the paper?) before they'd re-issue. I'd never seen documents (a)
printed on this bizarre page size called 'legal and (b) actually
*embossed* by the university seal.. This was some serious magic going
down. In my nightmares, somebody in mid-western nondescript university
of somewhereville is screaming "I CANT GET THE ORIGINAL SIGNATURE" and
the Berkeley lawyers just shrug and walk away from the deal.

This was also the release which brought T/Roff drivers for xerographic
process printers. They emitted wet, shiny, even slimy pages in some
process I don't want to understand, all of which bore cut marks on the
side (roll feed, before A4 printers existed) marking this US legal
thing. Cut at the mark? Won't fit a ring-binder we own in the entire
University...  Mike Lesk told me the code had 'witticisms' such as an
extra emitted char on \r to ensure the specific printer it was written
for didn't stuff up TBL output.

-G

On Thu, Aug 29, 2019 at 7:55 AM Rob Pike <robpike@gmail.com> wrote:
>
> Reiser added paging and it was working well by early 1981.
>
> -rob
>
>
> On Thu, Aug 29, 2019 at 4:41 AM Doug McIlroy <doug@cs.dartmouth.edu> wrote:
>>
>> > Doug McIlroy <doug@cs.dartmouth.edu> wrote:
>> >
>> >>
>> >>> How long was research running on a PDP-11 and when did they move to a VAX?
>> >>
>> >> London and Reiser had ported Unix to the VAX, replete with virtual memory, in 1978. By the time v7 was released (1979), Vaxen had become the workhorse machines in Research.
>> >>
>> >> Doug
>> >
>> > So, what's the story on why the London/Reiser port didn't get adapted
>> > back by Research, and they ended up starting from 4.1 BSD?
>> >
>> > Thanks,
>> >
>> > Arnold
>>
>>
>> Sorry, what I said about London/Reiser is true, but not the whole story. L/R didn't have demand paging; BSD did.
>>
>> Doug
>>

  reply	other threads:[~2019-08-28 22:30 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 18:41 Doug McIlroy
2019-08-28 18:49 ` arnold
2019-08-28 19:03   ` Chet Ramey
2019-08-28 19:05     ` Larry McVoy
2019-08-29 14:58       ` Jason Stevens
2019-08-29 16:25         ` arnold
2019-08-29 16:38           ` Ralph Corderoy
2019-08-29 17:35             ` arnold
2019-08-28 21:55 ` Rob Pike
2019-08-28 22:29   ` George Michaelson [this message]
2019-08-28 22:36     ` William Pechter
2019-08-28 23:02       ` Arthur Krewat
2019-08-29  0:11       ` Clem cole
2019-08-29  0:18         ` George Michaelson
2019-08-29  6:27         ` Lars Brinkhoff
  -- strict thread matches above, loose matches on Subject: below --
2019-09-01  2:36 [TUHS] dmr streams & networking [was: Re: If not Linux, then what? Rudi Blom
2019-09-01  2:16 [TUHS] dmr streams & networking [was: Re: If not Linux, then what?] Rudi Blom
2019-08-31  9:43 Rudi Blom
2019-08-31 15:41 ` Clem Cole
2019-08-30 20:21 Norman Wilson
2019-08-30 20:28 ` Larry McVoy
2019-08-30 20:39 ` Clem Cole
2019-08-30 21:52   ` Larry McVoy
2019-08-31  0:58     ` Clem Cole
2019-08-31  1:13       ` Bakul Shah
2019-08-31  2:46         ` Clem cole
2019-08-31  2:57           ` Clem cole
2019-08-31  3:14             ` Gregg Levine
2019-08-31  3:47               ` Clem cole
2019-08-31  3:38             ` Bakul Shah
2019-08-31  5:37             ` Dave Horsfall
2019-08-31 19:03               ` Clem Cole
2019-09-05  5:11                 ` Al Kossow
2019-09-02  8:28               ` Peter Jeremy
2019-09-02 23:26                 ` Dave Horsfall
2019-08-31  3:19           ` Bakul Shah
2019-08-28 17:57 Doug McIlroy
2019-08-28 18:05 ` Adam Thornton
2019-08-28 18:08 ` arnold
2019-08-28 18:27 ` Warner Losh
2019-08-28 18:34   ` Warner Losh
2019-08-28 21:54 ` Rob Pike
2019-08-29  6:43   ` arnold
2019-08-29  7:39     ` Rob Pike
2019-08-29 16:26       ` arnold
2019-08-29  3:29 ` Lawrence Stewart
2019-08-29  4:10   ` Larry McVoy
2019-08-28  9:17 Paul Ruizendaal
2019-08-28 10:44 ` Angelo Papenhoff

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=CAKr6gn1ZHLerb4sODqYzMo8zi82gRAt6RnB3Wjtany8TdD15qg@mail.gmail.com \
    --to=ggm@algebras.org \
    --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).