The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arno.griffioen@ieee.org (Arno Griffioen)
Subject: [TUHS] SVR4 x86 -- Sources
Date: Wed, 13 Jul 2011 15:25:04 +0200	[thread overview]
Message-ID: <20110713132504.GY13454@attic.nerdnet.nl> (raw)
In-Reply-To: <CA+rfG9a--Uj4t1sSSXZwDwjq5Jc_6OXhdjoO0YiSc1hV2v6ZcQ@mail.gmail.com>

On Tue, Jul 12, 2011 at 08:23:41PM -0400, Jason Stevens wrote:
> And then there was that whole SYSV to the Commodore Amiga that SUN tried to
> piggy back on.... There had to be a lot more to that then meets the eye.

The SVR4 Amiga UNIX implementation was an interesting oddball in itself as 
CBM was of course 'cheap' and trying to save money on the project, so
they licensed the code-base for the 3B2 instead of the original M68k codebase
from AT&T..

The M68k codebase was much more expensive to license as I recall from my days 
working at CBM

The result was that the 'port' was a real SVR4 and worked as such, but 
it lacked the SVR4 M68K ABI support in the kernel, which meant that
nearly all available off-the-shelf applications for M68K SVR4 
did NOT work on these.

Which 'slightly' hampered the rollout and acceptance of these UNIX machine
(understatement!).

Pity they disbanded the CBM UNIX devel group before it really got started and
an 68040 version was never officially released so the whole product fizzled
out.

I remember that the decision to axe the whole UNIX team inside CBM was 
really made without anyone knowing about it. Some of the guys were off 
on visits to CBM offices in other countries when they were told 
they were fired :(

The previous (mostly un-released/internal) SVR3.2 port to the A2500UX'es
for 68020+MMU or 68030 (of which I still have one, just no SVR3.2 media..) 
was AFAIK based on the real M68k codebase.

> Not to mention Commodore not letting SUN OEM the Amiga 3000/UX was their
> biggest mistake.

CBM in their late days were very good at making bad decisions ;)

								Bye, Arno



  reply	other threads:[~2011-07-13 13:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 15:11 Michele Ghisolfo
2011-07-12 23:26 ` Larry McVoy
2011-07-13  0:23   ` Jason Stevens
2011-07-13 13:25     ` Arno Griffioen [this message]
2011-07-13  2:48   ` John Cowan
2011-07-13  3:07     ` Larry McVoy
2011-07-14 17:37   ` Al Kossow
2011-07-15  4:30 ` Warren Toomey
  -- strict thread matches above, loose matches on Subject: below --
2011-07-12 13:24 Norman Wilson
     [not found] <1310385759.2145.18.camel@localhost.localdomain>
2011-07-11 14:09 ` Sergio Aguayo
2011-07-11 10:29 Michele Ghisolfo
2011-07-11 12:42 ` Michael Kerpan
2011-07-11 12:53   ` Jim Capp
2011-07-14 17:42     ` Al Kossow
2011-07-14 17:46       ` Jason Stevens
2011-07-15  4:10         ` Random832
2011-07-15  4:22           ` John Cowan
2011-07-12  7:54   ` Wesley Parish
2011-07-12  9:53     ` Nick Downing
2011-07-19 23:17       ` Doug McIntyre
2011-07-20  0:42         ` Larry McVoy
2011-07-20  3:16         ` John Cowan
2011-07-20  4:04           ` Warner Losh
2011-07-12  9:57     ` Nick Downing
2011-07-12 11:22       ` Tim Bradshaw
2011-07-12 11:54         ` Nick Downing
2011-07-11 12:50 ` Sergio Aguayo
     [not found] ` <4E1B6A45.40607@laposte.net>
2011-07-11 19:50   ` Michele Ghisolfo
2011-07-11 21:56     ` Jason Stevens
2011-07-11 20:08       ` Michele Ghisolfo
2011-07-11 22:56         ` Warren Toomey
2011-07-12 13:04       ` Milo Velimirović
2011-07-12 13:07         ` Jason Stevens

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=20110713132504.GY13454@attic.nerdnet.nl \
    --to=arno.griffioen@ieee.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).