krohn@u1100a.UUCP (04/07/87)
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)?
Thanks for your help.
--
--
Eric J. Krohn {ihnp4,allegra,pyuxww,bellcore}!u1100a!krohn
Bell Communications Research, 444 Hoes Ln, Piscataway, NJ 08854Karl.Kleinpaste@cbstr1.UUCP (04/08/87)
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