The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jsteve@superglobalmegacorp.com (jsteve@superglobalmegacorp.com)
Subject: [TUHS] Un-released/internal/special UNIX versions/ports during theyears?
Date: Sat, 25 Feb 2017 22:44:45 +0800	[thread overview]
Message-ID: <37bb0648-3c13-4b00-897d-2e6afe3219c2@HK2APC01FT004.eop-APC01.prod.protection.outlook.com> (raw)
In-Reply-To: <20170225141738.f3uauxhasru7gsb3@ancienthardware.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3417 bytes --]

I’ve read from early Microsoft employee’s that you had to learn to use vi to get vacation time, as they ran Xenix on all their backend stuff.  Although their first Xenix ads did mention it was available on the PDP-11, and other than one old post where someone mentioned that anytime there was a serious bug it was always in the Xenix portion.

It’s kind of funny that despite at one time being the highest installation by site count, Xenix has all but disappeared.  Not that OpenSERVER was either open or much of a good server.  And the only people I ever saw all that excited about UnixWare was telecom companies.

Sent from Mail for Windows 10

From: Arno Griffioen
Sent: Saturday, 25 February 2017 10:18 PM
To: tuhs at minnie.tuhs.org
Subject: [TUHS] Un-released/internal/special UNIX versions/ports during theyears?

Hi!

Some of the stories on here reminded me of the fact that there's also likely 
a whole boat-load of UNIX ports/variants in the past that were never released 
to customers or outside certain companies.

Not talking about UNIX versions that have become obsolete or which have
vanished by now like IRIX or the original Apple A/UX (now *that* was an 
interesting oddball though..) and such, but the ones that either died or 
failed or got cancelled during the product development process or were never 
intended to be released to the outside ar all.

Personally I came across one during some UNIX consultancy work at Commodore 
during the time that they were working on bringing out an SVR4 release for the 
Amiga (which they actually sold for some time)

Side-note.. Interestingly enough according to my contacts at that time inside 
CBM it was based on the much cheaper to license 3B2 SVR4 codebase and not the 
M68k codebase which explained some of the oddities and lack of M68k ABI 
compliance of the Amiga SVR4 release.. 

However.. 

It turned out that they had been running an SVRIII port on much older Amiga 
2000's with 68020 cards for some of their internal corporate networking and 
email, UUCP, etc. and was called 'AMIX' internally. But as far as I know it 
was never released to the public or external customers.

It was a fairly 'plain jane' SVRIII port with little specific 'Amiga' hardware 
bits supported but otherwise quite complete and pretty stable.

Worked quite well in the 4MB DRAM available on these cards. The later SVR4
didn't fare so well.. Paged itself to death unless you had 8 or even (gasp!) 
16MB.

It was known 'outside' that something like this existed as the boot ROM's on 
the 68020 card had an 'AMIX' option but outside CBM few people really knew 
much about it.

It may have been used at the University of Lowell as they developed a TI34010 
based card that may already have had some support in this release.

Still..

This does make me wonder.. Does anyone else know of these kinds of special 
'snowflake' UNIX versions that never got out at various companies/insitutes?
(and can talk about it without violating a whole stack of NDA's ;) )

No special reason.. Just idle curiosity :)

Likely all these are gone forever anyway as prototypes and small run production 
devices and related software tends to get destroyed when companies go bust or 
get aquired.

							Bye, Arno.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170225/cae48007/attachment-0001.html>


  parent reply	other threads:[~2017-02-25 14:44 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25 14:17 [TUHS] Un-released/internal/special UNIX versions/ports during the years? Arno Griffioen
2017-02-25 14:32 ` Larry McVoy
2017-02-25 16:35   ` Steve Nickolas
2017-02-25 18:11     ` Joerg Schilling
2017-02-25 18:16       ` Brantley Coile
2017-02-25 17:31   ` Clem Cole
2017-02-25 17:34     ` Charles Anthony
2017-02-25 17:36     ` Brantley Coile
2017-02-25 18:28     ` Tim Bradshaw
2017-02-27  5:08       ` Dave Horsfall
2017-02-25 17:40   ` Nemo
2017-02-25 17:43     ` Brantley Coile
2017-02-25 23:23   ` Dave Horsfall
2017-02-26 12:39     ` Noel Chiappa
2017-02-26 12:46       ` [TUHS] The size of EMACS, and what hides in kLOCs Michael Kjörling
2017-02-26 16:05         ` Nemo
2017-02-26 17:05           ` Michael Kjörling
2017-02-26 18:23             ` Tim Bradshaw
2017-02-26 19:19               ` Jim Carpenter
2017-02-26 19:39                 ` [TUHS] EMACS movemail suid root bug Michael Kjörling
     [not found]           ` <CALMnNGg3dRV0yPV1GgeqaOFG0Mb5PSNuqgPs8pLKOHYzurYEOg@mail.gmail.com>
2017-02-27  1:00             ` [TUHS] The size of EMACS, and what hides in kLOCs Nemo
2017-02-27  1:48               ` Steve Nickolas
2017-02-27  8:26                 ` Michael Kjörling
2017-02-27  1:19           ` Jason Stevens
2017-02-27  2:13             ` Nick Downing
2017-02-26 13:32       ` [TUHS] Un-released/internal/special UNIX versions/ports during the years? Tim Bradshaw
2017-02-26 14:19         ` Michael Kerpan
2017-02-26 14:54           ` Joerg Schilling
2017-02-26 15:25             ` Angelo Papenhoff
2017-02-26 15:55               ` Joerg Schilling
2017-02-26 15:37             ` Tim Bradshaw
2017-02-26 15:52               ` Joerg Schilling
2017-02-26 16:06                 ` tfb
2017-02-26 16:27                   ` Ron Natalie
2017-02-26 18:32                     ` Lars Brinkhoff
2017-02-27 16:04                       ` Tony Finch
2017-02-27 23:51                         ` Nick Downing
2017-02-26 16:22                 ` Michael Kerpan
2017-02-26 16:36                   ` Ron Natalie
2017-02-26 18:01                     ` William Pechter
2017-02-26 18:40               ` Lars Brinkhoff
2017-02-26 16:06           ` Tim Bradshaw
2017-02-26 16:30             ` Ron Natalie
2017-02-26 17:15           ` Ron Natalie
2017-02-26 17:20             ` Michael Kjörling
2017-02-26 17:23               ` Ron Natalie
2017-02-26 17:33               ` Steve Nickolas
2017-02-26 17:39                 ` Michael Kjörling
2017-02-26 17:39                 ` Michael Kerpan
2017-02-26 19:33                   ` [TUHS] roff Larry McVoy
2017-02-26 19:34                     ` Ron Natalie
2017-02-26 19:36                       ` Ron Natalie
2017-02-26 19:46                         ` Dan Cross
2017-02-26 19:41                     ` Michael Kerpan
2017-02-26 21:27                       ` Joerg Schilling
2017-02-26 21:28                         ` Joerg Schilling
2017-02-27 13:59                         ` Steffen Nurpmeso
2017-02-28 20:15       ` [TUHS] Un-released/internal/special UNIX versions/ports during the years? Dave Horsfall
2017-02-28 20:22         ` Lars Brinkhoff
2017-03-01  1:31           ` Dave Horsfall
2017-02-28 20:40         ` Jaap Akkerhuis
2017-03-01 12:45           ` Michael Kjörling
2017-02-25 14:44 ` jsteve [this message]
2017-02-25 19:02 ` Al Kossow
2017-02-26  4:06   ` Jason Stevens
2017-03-01  4:15 ` Gregg Levine
2017-03-01  7:17   ` arnold
2017-03-01  7:45   ` Ronald Natalie
2017-03-01 11:14     ` [TUHS] Un-released/internal/special UNIX versions/ports duringthe years? jsteve
2017-03-01 14:54     ` [TUHS] Un-released/internal/special UNIX versions/ports during the years? Dan Cross
2017-03-01 15:41     ` Nemo
2017-03-01 18:17     ` Clem Cole
2017-03-02  2:13       ` Jason Stevens
2017-03-02  2:27       ` Gregg Levine

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=37bb0648-3c13-4b00-897d-2e6afe3219c2@HK2APC01FT004.eop-APC01.prod.protection.outlook.com \
    --to=jsteve@superglobalmegacorp.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).