Subject: VAX/System V Migration
To: port-vax <port-vax@netbsd.org>
From: Don Hurwitz <dhurwitz@ec.rockwell.com>
List: port-vax
Date: 09/27/1999 21:09:00
This is a multi-part message in MIME format.

------=_NextPart_000_014B_01BF092C.85270080
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

At Rockwell International Electronic Commerce,
we are looking for an upgrade path from a

     VAX 11/785 running UNIX System V (Release 3.1b)
     ['uname -a' reports "3.1b 0528 vax7xx"]

to a more modern platform (hardware and OS) which is
binary compatible with the above VAX/SVR3 combo.

We are limited to a "binary-compatible platform" solution, which
will enable us to migrate (retain) the executables for our custom
development tools (cross-compiler/assembler/linker) from this platform
to a more modern VAX or VAX compatible machine, since we no longer have
the tool sources (there, I said it) and can't re-compile on some/any
other platform.


1) I've been told that NetBSD/VAX can be coerced to run
   System V/R3 binaries.  Is that true?  Are there for-hire
   firms that have expertise in this area (or, are there
   any NetBSD fans out there for-hire)?  Is this a major
   or a minor alteration?

2) Alternatively, if #1 is not doable/practical, does
   anybody know of an update path for the VAX/SVR3 combo.


Any help or pointers would be greatly appreciated.

Thanks in advance,

Don Hurwitz
Rockwell Electronic Commerce
Darien, IL
630/985-4181
dhurwitz@ec.rockwell.com


------=_NextPart_000_014B_01BF092C.85270080
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>At Rockwell International Electronic=20
Commerce,<BR>we are looking for an upgrade path from a</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; VAX 11/785 =
running UNIX=20
System V (Release 3.1b)<BR>&nbsp;&nbsp;&nbsp;&nbsp; ['uname -a' reports =
"3.1b=20
0528 vax7xx"]</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>to a more modern platform (hardware and =
OS) which=20
is<BR>binary compatible with the above VAX/SVR3 combo.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>We are limited to a "binary-compatible =
platform"=20
solution, which<BR>will enable us to migrate (retain) the executables =
for our=20
custom<BR>development tools (cross-compiler/assembler/linker) from this=20
platform<BR>to a more modern VAX or VAX compatible machine, since we no =
longer=20
have<BR>the tool sources (there, I said it) and can't re-compile on=20
some/any<BR>other platform.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><BR>1) I've been told that NetBSD/VAX =
can be=20
coerced to run<BR>&nbsp;&nbsp; System V/R3 binaries.&nbsp; Is that =
true?&nbsp;=20
Are there for-hire<BR>&nbsp;&nbsp; firms that have expertise in this =
area (or,=20
are there<BR>&nbsp;&nbsp; any NetBSD fans out there for-hire)?&nbsp; Is =
this a=20
major<BR>&nbsp;&nbsp; or a minor alteration?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>2) Alternatively, if #1 is not =
doable/practical,=20
does<BR>&nbsp;&nbsp; anybody know of an update path for the VAX/SVR3=20
combo.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><BR>Any help or pointers would be =
greatly=20
appreciated.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks in advance,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Don Hurwitz<BR>Rockwell Electronic=20
Commerce<BR>Darien, IL<BR>630/985-4181<BR><A=20
href=3D"mailto:dhurwitz@ec.rockwell.com">dhurwitz@ec.rockwell.com</A><BR>=
</FONT></DIV></BODY></HTML>

------=_NextPart_000_014B_01BF092C.85270080--