The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Warner Losh <imp@bsdimp.com>
Cc: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>,
	TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: forgotten versions
Date: Sat, 18 Jun 2022 13:57:14 -0400	[thread overview]
Message-ID: <CAC20D2Np447RK3ggS8fFtwXQw-Wp3=A9J9WKGnHMA3GAVCPANg@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfqffZZpeF6AhaVwogc_fz152i7dxEN+Q0gOM7PpzxvPMA@mail.gmail.com>

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

On Sat, Jun 18, 2022 at 1:19 PM Warner Losh <imp@bsdimp.com> wrote:

> Are these systems bootable?
>
It has been so reported - in this same space IIRC


> I see all the source, but recall previous discussions
> about how bootstrapping them was tricky, or at least involved a large
> number of
> steps, each of which wasn't bad, but the whole path wasn't well mapped out.
>
I believe that is also correct.  Been a ToDo item of mine to try to get
them running.  Supposedly people used V8 to get V9 running.



> For V[67] we at least have boot tapes from back in the day, and V5 has a
> bootable disk image...
>
Yep and it helps, some of us did it back in the day.

The problem has been expressed, that V{8,9,10} like Plan9, were locked away
for whatever reasons.   They were all created post-Judge Green when the
behavior of AT&T formally WRT to the rest of the world changed.   I don't
think the people in 1127's attitude changed (certainly not of my friends
that I interacted with) but what they could do was more constrained.

Before the 1956 consent decree, AT&T corporate was not allowed to be in the
computer business, post-Judge Green they were actively trying to be and
their SW was formally System III and the later System V versions.   BTW:
AT&T was unique in this behavior.   IBM and DEC did it too.  One of my
favorite stories (that I personally lived) is that of Motorola, which
became the 68000.  When I first got it (at Teklabs) it did not have a
number - which much, much later beget the 4404, it was explicitly told to
us that it was a toy and it was not committed.  We managed to get approx
$100 of them to make the first Magnolia machine
<https://streaklinks.com/BF0w99hsbHL5eGZttg1NqgOi/https%3A%2F%2Farchive.org%2Fdownload%2Fbitsavers_tektronixmliaplan_4739361%2F1980-9-16-magnolia-plan.pdf>
 But the original developers had given a couple of them to the research
teams of a few of their friends - the 6809 was the official product.
 Famously, when IBM asked Moto to bid on a processor for what was to later
become the PC, they had been playing with the future 68000 in NY and Conn,
already.  When the folks came to Austin, IBM was pressured to use the 6809
by Motorola marketing, and officially told that the other chip had no
future and was an experiment.

I always looked at V{8,9,10} and Plan9 in the same way.  BTW: I also think
that's part of why BSD got such a lead.   AT&T Marketing kept the 'consider
it standard' stuff in people's faces with System III and later Sys V.  Many
users  (like me) and our firms wanted no part of it.   If AT&T had been
offered V{8,9,10} or Plan9 under the same basic terms that V7 had
been, I suspect
that the story might have had a different ending.

Clem




> ᐧ

[-- Attachment #2: Type: text/html, Size: 6830 bytes --]

  reply	other threads:[~2022-06-18 17:58 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18  0:35 Douglas McIlroy
2022-06-18  5:00 ` Kevin Bowling
2022-06-18  5:13   ` Adam Thornton
2022-06-18 16:58     ` Clem Cole
2022-06-18 17:18       ` Warner Losh
2022-06-18 17:57         ` Clem Cole [this message]
2022-06-19 20:46   ` [TUHS] RFS (was Re: Re: forgotten versions) Derek Fawcus
2022-06-19 23:07     ` [TUHS] " Larry McVoy
2022-06-19 23:19       ` Brad Spencer
2022-06-20  5:03         ` Arno Griffioen via TUHS
2022-06-20  6:53           ` Theodore Ts'o
  -- strict thread matches above, loose matches on Subject: below --
2022-06-24  6:47 [TUHS] Re: forgotten versions Paul Ruizendaal
2022-06-25 19:16 ` Anthony Martin
2022-06-25 20:45   ` Paul Ruizendaal
2022-06-27  0:57     ` Kevin Bowling
2022-06-23  2:18 Noel Chiappa
2022-06-22 12:06 Noel Chiappa
2022-06-23  0:02 ` Dan Cross
2022-06-18 19:55 Paul Ruizendaal
2022-06-17 14:50 Paul Ruizendaal
2022-06-16 23:06 [TUHS] " Rob Pike
2022-06-16 23:17 ` [TUHS] " Earl Baugh
2022-06-16 23:18 ` George Michaelson
2022-06-16 23:44   ` George Michaelson
2022-06-17  0:10     ` Larry McVoy
2022-06-17  7:20 ` Diomidis Spinellis
2022-06-17  7:33   ` Rob Pike
2022-06-17  8:34   ` arnold
2022-06-17 10:52 ` arnold
2022-06-18  7:05 ` Angelo Papenhoff
2022-06-19  7:50   ` Rob Pike
2022-06-19  8:17     ` Angelo Papenhoff
2022-06-19  8:53       ` Rob Pike
2022-06-19  9:02         ` Angelo Papenhoff
2022-06-19  9:14           ` arnold
2022-06-19  9:19             ` Angelo Papenhoff
2022-06-19  9:23               ` arnold
2022-06-19 11:37                 ` Matthias Bruestle
2022-06-19 14:47         ` Kenneth Goodwin
2022-06-19 16:27           ` Al Kossow
2022-06-19 18:32           ` Theodore Ts'o
2022-06-19 18:38             ` Dan Cross
2022-06-21 23:56               ` Jacob Moody
2022-06-22  0:13                 ` Larry McVoy
2022-06-22  0:48                   ` Rob Pike
2022-06-22  1:55                     ` George Michaelson
2022-06-22  2:10                       ` Bakul Shah
2022-06-22  2:14                       ` Jon Steinhart
2022-06-22  2:19                         ` Andrew Hume
2022-06-22  2:58                           ` Rob Pike
2022-06-22  3:09                             ` George Michaelson
2022-06-22  2:16                   ` Andrew Hume
2022-06-22  2:55                   ` Brad Spencer

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='CAC20D2Np447RK3ggS8fFtwXQw-Wp3=A9J9WKGnHMA3GAVCPANg@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=douglas.mcilroy@dartmouth.edu \
    --cc=imp@bsdimp.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).