Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!cblpf!cbstr1!Karl.Kleinpaste
From: Karl.Kleinpaste@cbstr1.UUCP
Newsgroups: comp.sys.att
Subject: Re: Help needed on 3b{2,5,15,20} object code compatibility
Message-ID: <208@cbstr1.att.com>
Date: Wed, 8-Apr-87 09:24:58 EST
Article-I.D.: cbstr1.208
Posted: Wed Apr  8 09:24:58 1987
Date-Received: Sat, 11-Apr-87 06:28:51 EST
References: <1267@u1100a.UUCP>
Sender: karl@cbstr1.att.com
Distribution: na
Lines: 20
In-reply-to: krohn@u1100a.UUCP's message of 7 Apr 87 15:25:20 GMT
Posting-Front-End: GNU Emacs 18.41.1 of Mon Mar 30 1987 on cbstr1 (usg-unix-v)

krohn@u1100a.UUCP writes:
   I need to know about object code inter-exchangability between members
   of the 3B series.  Will my 3b2 (running Sys V R 2) object code
   run without change on a 3b5, 3b20, etc (again running SVR2)?
   What about variations on the OS version (SVR3 or SVR0)?

The 3B{2,5,15} can be considered equivalent.  I transport compiled
binaries of GNU Emacs between 2's and 15's with some regularity, and
that's got to be just about the worst acid test readily available.
Even the unexec code works fine when transported.

OS differences shouldn't be tough to manage.  SysV.2/SysV.3 should not
affect you, as long as you're moving up, of course.  I'm not even sure
it's possible to *have* SysV.0 on a 3B - they came out after the
initial introduction of SysV.2.

The 3B20, however, is a different beast altogether.  It is not binary
compatible with the {2,5,15}s.

Karl