From: Steve Nickolas <usotsuki@buric.co>
To: tuhs@tuhs.org
Subject: [TUHS] Re: AIX moved into maintainance mode (fwd)
Date: Thu, 19 Jan 2023 15:08:52 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.2301191508180.2622@sd-119843.dedibox.fr> (raw)
Accidentally sent this only to the person I was replying to.
> I am getting some grief on Twitter too for "omitting" FreeBSD. I
> didn't, but the BSDs don't fit either definition of "Unix". The
> pre-1993 one being "based on AT&T code" -- after all, BSD (4.4 Lite r2
> was it? Before my time!) -- went to a lot of effort to eliminate AT&T
> code.
From what I've seen it's very much a gradual transition; 4.3-Tahoe starts to
have the new code and UCB copyright notices with the predecessor of what we call
the "BSD License" appearing in some of the source files. Then with Reno, a
majority of the userland is open-sourced, and Net/2 is fairly complete. (Net/2
and 4.4BSD-Lite / Lite/2 were lacking a few things.) But even right up until
the end things were in a state of flux.
A few things weren't finished until much later by the FreeBSD, OpenBSD and
NetBSD people.
-uso.
next reply other threads:[~2023-01-19 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 20:08 Steve Nickolas [this message]
2023-01-19 20:21 ` segaloco via TUHS
2023-01-19 20:54 ` G. Branden Robinson
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=alpine.DEB.2.21.2301191508180.2622@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--cc=tuhs@tuhs.org \
/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).