From: Collin Funk <collin.funk1@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@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.
Date: Mon, 29 Dec 2025 23:35:55 -0800 [thread overview]
Message-ID: <87pl7wxvz8.fsf@gmail.com> (raw)
In-Reply-To: <20251230072231.cbsmcowvonavhd4c@illithid>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
"G. Branden Robinson" <g.branden.robinson@gmail.com> writes:
> At 2025-12-29T22:59:11-0800, Collin Funk wrote:
>> It actually existed before 4.4BSD. It existed in 2.11BSD at least [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.
Oh, right. The source I linked has a 1995 date on it that I missed. I
would have realized the mistake if I had, since 4.4BSD is from 1992 or
1993.
Collin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2025-12-30 7:35 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 ` Collin Funk [this message]
2026-01-03 10:31 ` 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=87pl7wxvz8.fsf@gmail.com \
--to=collin.funk1@gmail.com \
--cc=alx@kernel.org \
--cc=g.branden.robinson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.