The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jonathan Gray <jsg@jsg.id.au>
To: Warner Losh <imp@bsdimp.com>
Cc: segaloco <segaloco@protonmail.com>, tuhs@tuhs.org
Subject: [TUHS] Re: UNIX/TS 4.x Findings
Date: Fri, 10 Feb 2023 14:22:01 +1100	[thread overview]
Message-ID: <Y+W4Wc95CfZbyEw3@largo.jsg.id.au> (raw)
In-Reply-To: <CANCZdfpX5GQEimSaohfztKOUX6OPUzAY8gNHU23vD0kBPoyf8Q@mail.gmail.com>

On Thu, Feb 09, 2023 at 08:07:45PM -0700, Warner Losh wrote:
> On Thu, Feb 9, 2023 at 6:30 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
> 
> > The more I look at things, the more 5.0 appears to actually be a minor
> > release compared to what all was going on in the 4.x era.  From 4.1 to 5.0
> >
> 
> So let's look at release dates:
> 
> 4.2BSD released August 1983
> 4.3BSD released May 1986
> 
> System V released sometime in 1983 (so TS 5.0 was 1982 by convention?)
> 
> 5.0 felt like a minor release... (even after TS 4.2) Sure sounds like it
> was rebranded to 5.0 to avoid confusion with 4.2BSD which was released
> around... as well as to have a '.0' zero feel to it but neatly avoiding
> that by calling it V...
> 
> Anybody here know for sure? I have a vague memory of Dr McKusick mentioning
> this off hand in one of his informal talks or maybe it was over dinner at a
> conference...

It was the other way around.

"The original intent had been to call it the 5BSD release; however,
there were objections from AT&T that there would be customer confusion
between their commercial Unix release, System V, and a Berkeley release
named 5BSD. So, to resolve the issue, Berkeley agreed to change the
naming scheme for future releases to stay at 4BSD and just increment the
minor number."
https://www.oreilly.com/openbook/opensources/book/kirkmck.html

  parent reply	other threads:[~2023-02-10  3:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  1:32 [TUHS] " segaloco via TUHS
2023-02-10  2:54 ` [TUHS] " Jonathan Gray
2023-02-10  4:38   ` segaloco via TUHS
2023-02-10  4:48     ` George Michaelson
2023-02-10  4:58       ` segaloco via TUHS
2023-02-10 17:47         ` [TUHS] Re: UNIX Release 4 Findings segaloco via TUHS
2023-02-10  3:07 ` [TUHS] Re: UNIX/TS 4.x Findings Warner Losh
2023-02-10  3:15   ` Larry McVoy
2023-02-10  3:22     ` Warner Losh
2023-02-10  3:22   ` Jonathan Gray [this message]
2023-02-10  3:47     ` Jonathan Gray

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=Y+W4Wc95CfZbyEw3@largo.jsg.id.au \
    --to=jsg@jsg.id.au \
    --cc=imp@bsdimp.com \
    --cc=segaloco@protonmail.com \
    --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).