All of lore.kernel.org
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Seth McDonald <sethmcmail@pm.me>,
	 Alejandro Colomar <alx@kernel.org>,
	linux-man@vger.kernel.org
Subject: Re: [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix
Date: Mon, 29 Dec 2025 23:40:11 -0800	[thread overview]
Message-ID: <87ldikxvs4.fsf@gmail.com> (raw)
In-Reply-To: <20251230072756.c25thnpent43mjma@illithid>

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

"G. Branden Robinson" <g.branden.robinson@gmail.com> writes:

> At 2025-12-30T07:18:50+0000, Seth McDonald wrote:
>> > [1] https://www.tuhs.org/cgi-bin/utree.pl?file=2.11BSD/src/man/man3/sysctl.3
>> 
>> That would be good to include, though we may need to first modify
>> standards(7) since 2.11BSD currently isn't listed there (the earliest
>> mentioned is 3BSD).
>
> The date on that file, 1993, strongly suggests a backport from the
> then-getting-finalized 4.4BSD (which settled out over the course of 1994
> and into 1995 depending on whether one considers the "Encumbered" or
> "Lite" versions mandated by the settlement of the USL v. BSDI lawsuit).
>
> 4.3BSD, by contrast, dates to 1986.  See my previous mail.
>
> So in that sense, a sysctl()-bearing 2.11BSD is more recent than
> 4.3BSD.

It does say 1993, but it also has the following:

    .\"	@(#)sysctl.3	8.1.1 (2.11BSD GTE) 1/13/95
    .\"
    .TH SYSCTL 3 "January 13, 1995"

The first line being used by SCCS? That is an assumption since I have
never used it.

> I suggest the Linux man-pages project not attempt to track the
> provenance or timeline of 2.11BSD features.  It's too much work.

And there is probably not much practical benefit, i.e., just some (very
few, probably) people interested in the history.

Collin

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

  reply	other threads:[~2025-12-30  7:40 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 [this message]
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       ` 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=87ldikxvs4.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=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.