From: Warner Losh <imp@bsdimp.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Paul Ruizendaal <pnr@planet.nl>
Subject: Re: [TUHS] 32V memory management: not quite V7 style swapping -- source code update
Date: Sun, 6 Jun 2021 12:40:38 -0600 [thread overview]
Message-ID: <CANCZdfpUb6CUbDfOn+uYk6wn7951J9d9X53WMG-djgZCKx6SHA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NUuygSmpTSpBTrALVd+yqJtAd0KVLaePuAWVgM1tbpBg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2176 bytes --]
On Sun, Jun 6, 2021, 12:36 PM Clem Cole <clemc@ccc.com> wrote:
> 4.2 had networking, 4.1 did not. 32V did not either. I'm asking 32V vs
> 4.1
> ᐧ
>
My info is from the 4.2 time frame...
Warner
On Sun, Jun 6, 2021 at 2:30 PM Larry McVoy <lm@mcvoy.com> wrote:
>
>> BSD had networking. Once you had that, you don't look back. Sys V (and
>> prior) so far as I know, didn't get networking until Coherent did their
>> STREAMS stack that somehow ended up at Lachman - I ported it to a crazy
>> super computer and to SCO Unix. SCO was pretty stock AT&T code and let
>> me tell you, it felt pretty crappy after having used BSD and then SunOS.
>> It was a giant step backwards.
>>
>> I just think the BSD folks were moving forward faster. Rob with start
>> talking about cat waving its tail, I get it, not everything was better
>> but a lot was. Solid networking that performed was very pleasant.
>>
>> On Sun, Jun 06, 2021 at 02:23:49PM -0400, Clem Cole wrote:
>> > Paul,
>> >
>> > You got me thinking and I'm curious if anyone really knows historically
>> how
>> > many sites ran a 32V system? In those days (late 70s/early 80s) the
>> > universities that knew and and even many sites inside the Bell System,
>> the
>> > Vaxen I ran 4.1BSD (say the Marx's brothers at Whippany along with the
>> Vax
>> > in the underseas research lab were we put the AP I did for my thesis).
>> > There were a couple in Summit I know, and probably Homdel and I'm
>> guessing
>> > in some of the operating companies, but I never got the feeling 32V was
>> > popular. The folks with Vaxen that I knew, if you were able to run BSD
>> > (4.1 and eventually 4.2), did. Later on the only non-'pure-joy'
>> systems I
>> > knew were a couple of Ultrix systems because they wanted the support
>> from
>> > DEC and IIRC were using FORTRAN and wanted the DEC compiler which only
>> ran
>> > on Ultrix or VMS. Inside of AT&T, I personally think I knew more folks
>> > with VMS (Fortran being the key anchor) than those that ran 32V.
>> > ???
>>
>> --
>> ---
>> Larry McVoy lm at mcvoy.com
>> http://www.mcvoy.com/lm
>>
>
[-- Attachment #2: Type: text/html, Size: 3676 bytes --]
next prev parent reply other threads:[~2021-06-06 18:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 18:03 Paul Ruizendaal via TUHS
2021-06-06 18:23 ` Clem Cole
2021-06-06 18:30 ` Larry McVoy
2021-06-06 18:35 ` Clem Cole
2021-06-06 18:40 ` Warner Losh [this message]
2021-06-06 18:52 ` Richard Salz
2021-06-06 19:02 ` Clem Cole
2021-06-06 19:18 ` arnold
2021-06-06 19:35 ` Clem Cole
2021-06-06 19:45 ` arnold
2021-06-06 20:46 ` Clem Cole
2021-06-06 18:53 ` Clem Cole
2021-06-06 18:39 ` Warner Losh
2021-06-06 19:23 ` Clem Cole
2021-06-06 19:08 ` Paul Ruizendaal via TUHS
2021-06-07 19:24 ` Greg A. Woods
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=CANCZdfpUb6CUbDfOn+uYk6wn7951J9d9X53WMG-djgZCKx6SHA@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=clemc@ccc.com \
--cc=pnr@planet.nl \
--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).