[Info-vax] Locally mount vms volumes in Linux

gregor.oelze gregor.oelze at gmail.com
Mon Feb 28 06:08:09 EST 2011


On 28 Feb., 11:51, pe... at langstoeger.at (Peter 'EPLAN' LANGSTOEGER)
wrote:
> In article <f2f9a73b-ae71-43d0-8f25-2f8a6fdc5... at t13g2000vbo.googlegroups.com>, "gregor.oelze" <gregor.oe... at gmail.com> writes:
>
> >I recently started a discussion how to get tcpware on our vms 5.x
> >version to work on simh, simulated on a spare ubuntu machine.
>
> Yup.
>
> >There seem to be many problems regarding the licenses and migration-
> >problems with the virtual hardware, so I asked myself if it could be
> >possible - to mount the available dd-image of the microvax harddrive
> >somehow in linux, so we can extract the compiled programs out of the
> >vms system and transfer them to the targetmachine via ftp on the same
> >host - where simh is running.
>
> Don't know.
>
> But we still don't know, what the purpose of this simulated machine is.

The purpose of the simulated machine is to develop programs for a
testing
appliance called genrad - which is running in the same-lab. Once
compiled
the programs were transfered to the genrad system via ftp.

The simulated vax in simh is the replacement for the dead hardware
since
program changes are made about 2-3 times a year.

> If you need to get a file out of the disk *once*, the way with an ODS2
> program on Linux *may* be sufficient.

I need to extract the files about 2-3 times a year.

> But if you need to get a replacement hardware for the died MicroVAX 3100
> (running the GENRAD software for the board test equipment hardware which
> is still in use), then I'd go with SIMH or CHARON-VAX or a real VAXstation
> In this case, you need to *legally* solve your (VMS & TCPware) license
> issues at all, and with this solve your technical license issues as well.
> Both should be no big deal, but will cost money.

The license issues seems to be gone - regarding the vms system. The
TCPWARE though, still outputs the same-error.

> If you ignore the legal license problems, the technical ones are solved
> by getting an emulated VAX hardware which behaves like the old/real one
> (for VMS and for TCPware) - like discussed/explained in previous thread.

Done.

best regards

Gregor Oelze



More information about the Info-vax mailing list