The mention of UNOS a realtime "clone" of Unix in a recent thread raises a question for me. How many
Unix clones are there?
(My interest in Unix was the result of a local computer magazine, Bits'n'Bytes in the late 80s and early 90s
discussing two clones, Minix and Coherent in its Unix column. Then came Linux ...)
We've got a timeline (in several forms, in the 4.3BSD and 4.4BSD books and The Magic Garden, on Groklaw,
and elsewhere) for Unix and its developments; has anyone done one for the clones?
Thanks
Wesley Parish
"I have supposed that he who buys a Method means to learn it." - Ferdinand Sor,
Method for Guitar
"A verbal contract isn't worth the paper it's written on." -- Samuel Goldwyn
I suppose that it would make sense that all of AT&T's leading edge projects would use research Unix. I've always heard of the original C++ to C translator but this is the first time I've actually seen it.
It doesn't look like it had the wide scale following that C or Fortan had at this point.
Sadly my experience with C++ was mostly tied to Borland on the micro in early 90's, which makes it look mature compared to these early versions.
It's great finding stuff like this in the tree hiding in plain sight, if only you know what to look for. (http://unix.superglobalmegacorp.com/cgi-bin/cvsweb.cgi/researchv9/cmd/cfron…)
Or that emacs was in the v9 tree, in the religious wars I always imagined NJ being more vi.
Thanks again for making this release happen!
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
On Thu, 30 Mar 2017, Warren Toomey via Uucp wrote:
> On 03/29/2017 11:09 PM, Dave Horsfall via Uucp wrote:
> > Let the cancel/rmgroup/flame wars begin :-)
>
> :-P
And I still bear the scars from the aus.bizarre war... And I'll bet that
not many people remember that little episode :-)
> > (Been too busy to set up "utzoo" yet, so if anyone is desperate for it
> > then they can have it instead; my long-term goal is to run SimH on a
> > RasbPi but first I have to afford one...)
>
> What's your address? I've got an unused Raspberry Pi that I'll send you
> (or anyone else). ;-) First come, first serve.
To be sent privately...
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
wow thats perfect, thanks!
> ----------
> From: Paul McJones
> Sent: Thursday, April 6, 2017 10:42 AM
> To: tuhs(a)minnie.tuhs.org
> Cc: Jason Stevens
> Subject: Re: [TUHS] I just noticed all the cfont aka C++ in research
>
> I suppose that it would make sense that all of AT&T's leading edge
> projects would use research Unix. I've always heard of the original C++
> to C translator but this is the first time I've actually seen it.
>
>
>
> In case you're interested, Bjarne Stroustrup has been helping me collect
> early versions of cfront here:
>
>
> http://www.softwarepreservation.org/projects/c_plus_plus/#cfront
>
>
> Previously we had located a listing of Release E (which we scanned),
> source for Release 1.0 of 10/10/85, and source for Release 3.0.3. From
> these 9th and 10th edition snapshots, cfront 1.2.2 6/10/87, AT&T C++
> Translator 2.00 06/30/89, AT&T C++ Translator 2.1.0+ 04/01/90, and AT&T
> C++ Translator 2.1++ 08/24/90 join the list.
>
> I suppose that it would make sense that all of AT&T's leading edge projects would use research Unix. I've always heard of the original C++ to C translator but this is the first time I've actually seen it.
In case you’re interested, Bjarne Stroustrup has been helping me collect early versions of cfront here:
http://www.softwarepreservation.org/projects/c_plus_plus/#cfront
Previously we had located a listing of Release E (which we scanned), source for Release 1.0 of 10/10/85, and source for Release 3.0.3. From these 9th and 10th edition snapshots, cfront 1.2.2 6/10/87, AT&T C++ Translator 2.00 06/30/89, AT&T C++ Translator 2.1.0+ 04/01/90, and AT&T C++ Translator 2.1++ 08/24/90 join the list.
Joerg Schilling:
BTW: UNOS has been sold to real customers from it's beginning. Was UNIX V8
available outside AT&T?
=====
I'm not sure what that has to do with anything. Which
of your body parts is so small as to make you insecure,
and which UNIX distributions are your body parts drawn
from?
To answer the question seriously, though: as I think I've
already explained here, Eighth Edition UNIX was available
under special per-site licensing (a letter agreement) to
educational institutions. I'm not sure what the official
criterion was: I helped make the tape, but wasn't involved
in the paperwork. I believe the total was about a dozen
places. A few of them did interesting work with the
system that was published e.g. at USENIX conferences
(Princeton comes to mind), but most I think never even
booted the system up. By then there were other members
of the UNIX family that were more comfortable for general
use, and people were more interested in the ideas than
in the code.
And of course we were a research group. We weren't making
things for customers. We were sharing our work, to the
extent the laywers and our own limited resources allowed.
That was the last time the Computing Science Research
Center attempted anything like a formal distribution.
Any `distributions' after that are just snapshots of
a constantly-evolving system.
Norman Wilson
Toronto ON
(Body parts not available on github. Sorry.)
> > Can you characterize what the 3rd-party material might be?
>
> Me personally, no. But there are others on the list who can help do this.
> Hopefully they will chime in!
Here's a list, gathered from the manuals, of stuff that Bell Labs
may not have the right to redistribute, with some (uncertain)
attributions of origin. I did not check to see which of them appear in
the TUHS archives; I doubt that /usr/src fully covered /bin and /usr/bin.
This list is at best a first draft. Please weigh in with corrections.
Doug
Kernel internet code. BSD
Imported commands
esterel INRIA
lisp, liszt, lxref MIT
icont, iconc Arizona
macsyma MIT
maple Maplesoft
Mail BSD
matlab Mathworks
more BSD (From the manpage: "More, a paginator that lives up to its name, has
too many features to describe." Its prodigality has been eclipsed by "less".)
netnews Duke
ops5 CMU
pascal, pc BSD
pxp BSD
readnews, checknews, postnews Duke
sdb BSD
smp Wolfram
spitbol IIT
telnet BSD
tex Stanford
tset BSD
vi, ex, edit BSD
Commands I'm not sure about, could be from Bell Labs
cyntax
news
ropy
strings
Library functions
termcap BSD
Imported games
adventure, zork, aarvark, rogue
atc
doctor MIT
mars
trek, ogre, sol, warp, sail
Games I'm not sure about
back
boggle, hangman
cribbage, fish
ching
gebam
imp
mille
pacman
pengo
swar
tso
Joerg Schilling:
Interesting that they created a name clash:
"p" was the name of a pager on UNOS, the first realtime
UNIX lookalike from former AT&T employees.
=====
p was something Rob Pike brought when he arrived in
1980. I believe he wrote its first version several
years earlier, when he was at the University of Toronto.
Since UNOS dates from 1981 (says Wikipedia), I think
Rob's p gets precedence.
Not that it matters. There never was, nor should there
ever have been, some global register of UNIX command
names during its formative years. UNIX was a research
platform and a living work-in-progress until it became
productized in the latter part of the 1980s.
And, of course, UNOS was a lookalike written from scratch.
It wasn't UNIX. If it wanted to be, it should have
adopted Rob's p!
Norman Wilson
Toronto ON
(Not in a particularly serious mood)