From: Warner Losh <imp@bsdimp.com>
To: Will Senn <will.senn@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] BSD 2.11 documentation
Date: Thu, 30 Dec 2021 13:10:27 -0700 [thread overview]
Message-ID: <CANCZdfrUy65QJACPqtDRKbZJwtRF8eXrwiEbeFNb=Q+g8J7h8Q@mail.gmail.com> (raw)
In-Reply-To: <4407AB71-8024-4F83-ACA8-59898315E14B@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
On Thu, Dec 30, 2021 at 12:10 PM Will Senn <will.senn@gmail.com> wrote:
> Are there any extant 2.11 manuals other than the online manual and various
> install and configure PDFs, available for download?
>
> Also, am I understanding correctly that 2.11 is 2.10 plus some 4.3
> backports and a ton of patches? If there aren’t any 2.11 specific docs,
> what would be the closest of what is available?
>
BSD2.11 as released was BSD2.10 with even more 4.3 backports (though that
process started before 2.10 was released).
BSD2.11-pl473 has a lot that's not been summarized. Release notes /
installation guides have been updated as things like disk labels were
added. But I've not seen any comprehensive summary of the patches. I should
spend some time putting something together that summarizes things (rather
than the tick-tock of each patch, some of which fix very niche bugs, others
which add an ANSI-C compiler). There's also a few bugs that were fixed that
didn't get proper patches that you can detect with careful diffing, at
least in the early days...
https://www.tuhs.org/Archive/Distributions/UCB/2.11BSD/ has the latest,
nearly canonical version of 2.11BSD.
Warner
[-- Attachment #2: Type: text/html, Size: 1675 bytes --]
prev parent reply other threads:[~2021-12-30 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 19:10 Will Senn
2021-12-30 20:10 ` Warner Losh [this message]
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='CANCZdfrUy65QJACPqtDRKbZJwtRF8eXrwiEbeFNb=Q+g8J7h8Q@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=tuhs@tuhs.org \
--cc=will.senn@gmail.com \
/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).