public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Collin Funk <collin.funk1@gmail.com>
Cc: seth.i.mcdonald@gmail.com, Alejandro Colomar <alx@kernel.org>,
	Seth McDonald <sethmcmail@pm.me>,
	linux-man@vger.kernel.org
Subject: Re: Is 2.11BSD < 4BSD?  It depends. (was: [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix)
Date: Sat, 3 Jan 2026 04:31:48 -0600	[thread overview]
Message-ID: <20260103103148.pbpvnxmauaaqdsew@illithid> (raw)
In-Reply-To: <20251230072231.cbsmcowvonavhd4c@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 1117 bytes --]

[self-correction]

At 2025-12-30T01:22:34-0600, G. Branden Robinson wrote:
> 2BSD targeted only the PDP-11, and swapped out entire processes just
> as Unix historically always had.
> 
> 3BSD targeted the VAX, and supported demand paging--just as UNIX 32/V,
> the most recent common ancestor of AT&T System III/V and [34]BSD,
> did.[0]

Nope, I mangled my history here.  UNIX 32/V (or just 32V) _did not
implement demand paging_.  It ported Unix to the 32-bit VAX-11
architecture, but continued to swap out entire process's memory images.
You can read more about 32/V in the attachment.

3BSD _did_ implement demand paging and was, rightly, viewed as a major
feather in the cap of the Berkeley CSRG that produced it.

> 4BSD was a relatively minor update to 3BSD,

I'll further qualify that this characterization may apply only if one
cares about operating system kernels.  4BSD also introduced the curses
library, which in its ncurses reimplementation, many *nix system users
still use today.  Even some Windows users do, via PDCurses{,Mod}.

Sorry for my inaccuracies.

Regards,
Branden

[-- Attachment #1.2: Unix_for_VAX-11-780_London Reiser_reconstructed-v5-groff-1.24.0pre.pdf --]
[-- Type: application/pdf, Size: 105508 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2026-01-03 10:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30  6:41 [PATCH v1 0/4] Miscellaneous fixes seth.i.mcdonald
2025-12-30  6:42 ` [PATCH v1 1/4] man/man2/syscall.2: Add HISTORY section seth.i.mcdonald
2025-12-31 13:46   ` Alejandro Colomar
2025-12-30  6:42 ` [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix seth.i.mcdonald
2025-12-30  6:59   ` Collin Funk
2025-12-30  7:18     ` Seth McDonald
2025-12-30  7:27       ` G. Branden Robinson
2025-12-30  7:40         ` Collin Funk
2025-12-30  7:53           ` G. Branden Robinson
2025-12-30 11:34             ` Alejandro Colomar
2025-12-30  7:22     ` Is 2.11BSD < 4BSD? It depends. (was: [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix) G. Branden Robinson
2025-12-30  7:35       ` Is 2.11BSD < 4BSD? It depends Collin Funk
2026-01-03 10:31       ` G. Branden Robinson [this message]
2025-12-31 13:46   ` [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix Alejandro Colomar
2025-12-30  6:42 ` [PATCH v1 3/4] man/man2/utime.2: SYNOPSIS: ffix seth.i.mcdonald
2025-12-31 13:45   ` Alejandro Colomar
2025-12-30  6:42 ` [PATCH v1 4/4] man/man2const/F_GETSIG.2const: HISTORY: tfix seth.i.mcdonald
2025-12-31 13:47   ` Alejandro Colomar
2025-12-31 13:48 ` [PATCH v1 0/4] Miscellaneous fixes Alejandro Colomar

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=20260103103148.pbpvnxmauaaqdsew@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx@kernel.org \
    --cc=collin.funk1@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=seth.i.mcdonald@gmail.com \
    --cc=sethmcmail@pm.me \
    /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