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: Is 2.11BSD < 4BSD? It depends. (was: [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix)
Date: Tue, 30 Dec 2025 01:22:31 -0600 [thread overview]
Message-ID: <20251230072231.cbsmcowvonavhd4c@illithid> (raw)
In-Reply-To: <87zf70xxog.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2162 bytes --]
At 2025-12-29T22:59:11-0800, Collin Funk wrote:
> It actually existed before 4.4BSD. It existed in 2.11BSD at least [1].
Hang on a second. BSD version numbers are a little funny.
It is true that 1BSD < 2BSD < 3BSD < 4BSD.
After that, things get a little weird.
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]
4BSD was a relatively minor update to 3BSD, also exclusively for the
VAX. 4.1BSD was a much bigger deal and would have been 5BSD, except
AT&T blew a gasket over the version numbered, seeking a proprietary
claim over the number five. This has been discussed just this week on
the TUHS list.[1]
2BSD however was not abandoned as soon as 3BSD or even 4BSD showed up.
Some people still had PDP-11s around. And thanks to (Open)SIMH, we can
all still run one if we choose.
Features from 3,4BSD got backported to 2BSD, which eventually stabilized
its minor version number at "11", I suspect because that was
irresibility useful to characterize the system's only supported target
architecture.
2.11BSD continues to be maintained today, as a set of literally hundreds
of patches, as Berekeley-flavored Unix aficionadios explore just what
they can do with what is now basically an "embedded system".
The most recent patch I know of is #498, dated 2 September.[2]
I wish we had a modern package manager for the thing. I've never been
crazy about BSD's "patch && make world" approach. :-P
Regards,
Branden
[0] The demand-paged kernel was such a big deal that it's why the
"virtual memory" version of the Unix kernel appeared on disk as
"vmunix". The Linux kernel aped this as "vmlinux"--"vmlinuz" for
its compressed form--even though there has never existed a
traditionally swapping version. The more arbitrary and esoteric a
naming convention is, the more tightly Unix people cling to it.
[1] https://www.tuhs.org/pipermail/tuhs/2025-December/032903.html
[2] https://www.tuhs.org/Archive/Distributions/UCB/2.11BSD/Patches/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-30 7:22 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 ` G. Branden Robinson [this message]
2025-12-30 7:35 ` Is 2.11BSD < 4BSD? It depends Collin Funk
2026-01-03 10:31 ` Is 2.11BSD < 4BSD? It depends. (was: [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix) G. Branden Robinson
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=20251230072231.cbsmcowvonavhd4c@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