Running CHARON-VAX for Linux
Table of Contents
CHARON-VAX symbolic links
Use the following symbolic link to run different models of CHARON-VAX:
Link name | Emulator to run |
mv3k6 | MicroVAX 3600 |
mv3k9 | MicroVAX 3900 |
mv3k196 | MicroVAX 3100 Model 96 |
mv3k198 | MicroVAX 3100 Model 98 |
mvii | MicroVAX II |
vs4k90 | VAXStation 4000 Model 90 |
vx3k6 | VAXserver 3600 |
vx3k6_128 | VAXserver 3600 (128Mb of RAM is available) |
vx3k6_512 | VAXserver 3600 (512Mb of RAM is available) |
vx3k9 | VAXserver 3900 |
vx3k9_128 | VAXserver 3900 (128Mb of RAM is available) |
vx3k9_512 | VAXserver 3900 (512Mb of RAM is available) |
vx4k106 | VAX 4000 Model 106 |
vx4k108 | VAX 4000 Model 108 |
vx4k700 | VAX 4000 Model 700 |
vx4k705 | VAX 4000 Model 705 |
vx6k310 | VAX 6310 |
vx6k610 | VAX 6610 |
vx6k620 | VAX 6620 |
vx6k630 | VAX 6630 |
vx6k640 | VAX 6640 |
vx6k650 | VAX 6650 |
vx6k660 | VAX 6660 |
Running CHARON-VAX emulators
It is possible to run one or several instances of CHARON-VAX at the same time if your license allows it.
In case of multiple instances please note to use only absolute paths and unique names to all the files referenced in configuration file of each CHARON-VAX instance (log, toy clock, nvram files and all the other data such as disk images - all these objects will be discussed later; at this stage just pay attention to the files specified in the configuration file) and to specify only unique for each instance hardware devices to avoid clashing. .
For example:
|
Please refer to the next chapters for more details concerning CHARON-VAX configuration details.
Running from console
Copy required configuration template from "/opt/charon/cfg/" directory to some local file and set correct privileges to that file to be able to edit it:
|