From: Warner Losh <imp@bsdimp.com>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] dmr streams & networking [was: Re: If not Linux, then what?]
Date: Wed, 28 Aug 2019 12:34:10 -0600 [thread overview]
Message-ID: <CANCZdfqVt=Q+1DLmZuED4m1EgT5BC+8RudKtYZ8LKFxEAbooyg@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfpLtYgqj43aiTAoJPg_Obz=E+QhbMMHUvBcSU-yC-U0qQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
On Wed, Aug 28, 2019, 12:27 PM Warner Losh <imp@bsdimp.com> wrote:
>
>
> On Wed, Aug 28, 2019, 11:57 AM 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.
>>
>
>
> Is there a paper on this work?
>
Found the 32V paper, but this was still a swapping implementation if I'm
reading correctly. I thought that the virtual memory was added by BSD /
Bill Joy. That would explain why V8 was BSD 4.1 based, since it was the
first usable Vax port with VM.
Warner
>
[-- Attachment #2: Type: text/html, Size: 1809 bytes --]
next prev parent reply other threads:[~2019-08-28 18:34 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- 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 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
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
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='CANCZdfqVt=Q+1DLmZuED4m1EgT5BC+8RudKtYZ8LKFxEAbooyg@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=doug@cs.dartmouth.edu \
--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).