OpenVMS 9.2 for x86, Getting Began half 2, auto boot, licenses, PAKs, networking and SSH
OpenVMS on x86 is now out there for hobbyists! Virtually a 12 months after the official release. This can be a half 2 of my getting began information. Half 1 ended with an put in system, this half continues with automated startup, activating the license recordsdata (PAKs) and establishing networking together with SSH entry.
You can read all my OpenVMS articles here.
Lately I eliminated all Google Advertisements from this web site on account of their invasive monitoring, in addition to Google Analytics. Please, should you discovered this content material helpful, contemplate a small donation utilizing any of the choices beneath:
This information is a summarized / shorter model of the official installation
guide. It’s tailor-made for hobbyist utilization utilizing VirtualBox and lets you
get arrange shortly. Please check with the official documentation for any
questions. The official documentation is focused at VMWare ESXi, this information is
for VirtualBox.
This information is a comply with up on part 1 of my guide. It is best to have an
put in system in VirtualBox. Be sure to even have the license recordsdata
(x86community-20240401.zip) from https://sp.vmssoftware.com.
Make a snapshot
Open up VirtualBox, choose the shut-down OpenVMS machine and press
CTRL+SHIFT+T, or within the menu bar choose Snapshots -> Take Snapshot. Give
it a reputation like After preliminary set up and proceed.
Do that after each step within the information or after each customization that you simply make,
should you do make a mistake, you’ll be able to fall again to the snapshot and never need to
begin over again.
Computerized begin / bootup
Throughout the set up you needed to sort VMS_BOOTMGR within the UEFI Shell to get
into the OpenVMS Boot Supervisor, then you definately wanted to sort BOOT DKA0 to start out
from the disk. That is cumbersome and on an actual server you’ll need it to
boot mechanically. Begin the VM and within the EFI Shell> immediate, sort EDIT to open a primary editor. Enter the next:
fs0:efibootstartup.nsh
VMS_BOOTMGR DKA0 -fl 0,0
Then press CTRL+S to avoid wasting the file and CTRL+Q to exit the editor.
Reset / restart the VM, then after the UEFI shell has mechanically
opened the Boot Supervisor, enter the next instructions:
AUTOBOOT DKA0
SAVE
BOOT DKA0
The primary line will allow auto boot, the following line tells OpenVMS which
gadget to (auto) boot from. Full the boot sequence, login with the
SYSTEM account after which execute the SHUTDOWN command.
The subsequent boot will present the next auto boot:
BOOT MANAGER DEVICE: DKA0
DEFAULT BOOT COMMAND: BOOT DKA0 0 00000000
[...]
Press <ESC> to cease automated motion or another key to skip countdown and proceed.
5...4...3...2...1...
Booting...
If it fails, you may need to vary the VirtualBox Boot Order.
Reset the VM, press ESC a couple of instances shortly to get into a distinct UEFI menu,
type of like a BIOS menu.
Choose Boot Supervisor Choices, then Boot Order,
then Change Boot Order. Use the + and - keys to maneuver the VirtualBox above the
Arduous DisksUEFI Shell possibility, then Save and Proceed booting.
As soon as auto boot is working appropriately, make one other VirtualBox snapshot.
Telnet settings
OpenVMS requires particular telnet settings. I am utilizing WSL and the Ubuntu telnet
shopper, however PuTTY is a good possibility as effectively. For a Linux terminal, press and
maintain CTRL, then press ]. The immediate adjustments to telnet>. It’s good to enter
the command:
unset crlf
Press CTRL+] once more and enter one other command:
mode char
For PuTTY: Proper-click on the window body of your PuTTY session and choose
Change Settings. In Terminal settings, verify the next bins:
- TURN OFF Implicit CR in each LF
- TURN OFF Implicit LF in each CR
- TURN OFF Native Echo
- TURN OFF Native line enhancing
License set up / PAKs
Boot up your OpenVMS digital machine and log in utilizing the SYSTEM account.
It is best to see the next:
%LICENSE-I-NOLICENSE, no license is lively for this software program product
%LOGIN-S-LOGOPRCON, login allowed from OPA0:
VMS Software program, Inc. OpenVMS (TM) x86_64 Working System, E9.2-1
Final interactive login on Monday, 10-APR-2023 22:08:44.88
The Neighborhood License file (x86community-20240401.zip) from
https://sp.vmssoftware.com is a ZIP file containing an extended textual content file. If
you attempt to copy and paste it into the shell you’ll get an error:
$ $
%RMS-F-RER, file learn error
-SYSTEM-W-DATAOVERUN, information overrun
Four years ago I made an ISO file for the licenses. This time, we’ll simply
manually activate the OPENVMS-X86-BOE license, which is what we have to setup
networking. Then we’ll use OpenSSH to repeat over the license file and execute
that script. A lot simpler and fewer bother.
Examine the txt file and search for the road OPENVMS-X86-BOE. Copy the
instructions, line by line (not your complete command, that can fail):
LICENSE REGISTER OPENVMS-X86-BOE -
Press ENTER. Then paste:
/ISSUER=VSI -
Press ENTER. Then paste:
/AUTHORIZATION=...
Repeat this for each line within the license (PRODUCT, UNTIS, TERMINATION_DATE,).
OPTIONS, CHECKSUM
When you attempt to verify the licenses, you may observe that none are lively but:
SHOW LICENSE
Output:
Lively licenses on node REMY1:
%SHOW-I-NOLICENSE, no licenses exist
Load this particular license:
LICENSE LOAD OPENVMS-X86-BOE
Output:
%LICENSE-I-LOADED, VSI OPENVMS-X86-BOE was efficiently loaded with 6 models
Now the SHOW LICENSE command will present that’s is lively:
Lively licenses on node REMY1:
------- Product ID -------- ---- Score ----- -- Model --
Product Producer Items PCL Activ Model Launch Termination
OPENVMS-X86-BOE VSI 6 1 0 0.0 (none) 1-APR-2024
With this license loaded you’ll be able to setup networking and OpenSSH. Proceed on,
after community has been setup, we’ll activate the complete license file.
Community setup
The VM must be shut all the way down to edit the VirtualBox settings. Execute the
SHUTDOWN command to do this. Then, in VirtualBox, open the settings and
navigate to community and alter the adapter from NAT to bridged. Choose your
foremost community adapter. Beneath Superior, choose Intel PRO 1000 T Server because the
Adapter Sort.
Bridging makes the VM develop into an actual a part of your community, different machines
with the ability to entry it. NAT would require port forwarding in VirtualBox which
is a bit cumbersome.
After altering the community settings in VirtualBox, boot up the OpenVMS
set up.
Login to the system account and execute the next command:
@tcpip$config
Output:
VSI TCP/IP Companies for OpenVMS Configuration Menu
Configuration choices:
1 - Core atmosphere
2 - Consumer parts
3 - Server parts
4 - Elective parts
5 - Shutdown VSI TCP/IP Companies for OpenVMS
6 - Startup VSI TCP/IP Companies for OpenVMS
7 - Run checks
A - Configure choices 1 - 4
[E] - Exit configuration process
Enter configuration possibility:
Enter A and press ENTER. Output:
VSI TCP/IP Companies for OpenVMS Core Setting Configuration Menu
Configuration choices:
1 - Area
2 - Interfaces
3 - Routing
4 - BIND Resolver
5 - Time Zone
A - Configure choices 1 - 5
[E] - Exit menu
Enter configuration possibility:
Enter 1 and press ENTER. Output:
DOMAIN Configuration
Enter Web area: spnw.nl
Enter a site title, I used spnw.nl and press ENTER. You will be again within the
CORE menu. Choose possibility 2 - Interfaces. Output:
VSI TCP/IP Companies for OpenVMS Interface & Deal with Configuration Menu
Hostname Particulars: Configured=Not Configured, Lively=Not Configured
Configuration choices:
0 - Set The Goal Node (Present Node: REMY1)
1 - IE0 Menu (EIA0: TwistedPair 1000mbps)
[E] - Exit menu
Enter configuration possibility:
If you don’t see possibility 1, ensure that the VirtualBox community interface is ready to
the Adapter Sort Intel PRO 1000 T Server. Enter 1 and press ENTER. Output:
VSI TCP/IP Companies for OpenVMS Interface IE0 Configuration Menu (Node: REMY1)
Configuration choices:
1 - Add a major handle on IE0
2 - Add an alias handle on IE0
3 - Allow DHCP shopper to handle handle on IE0
[E] - Exit menu
Enter configuration possibility:
Press 3, then ENTER. I will use DHCP as a result of that’s simpler. I can
setup a static IP in my router (by way of DHCP). Output:
No interface is configured because the DHCP PRIMARY.
Both configure a DHCP PRIMARY or manually configure
the system-wide parameters.
DHCP Consumer configures system-wide parameters and
interface-specific parameters. Just one interface, the
DHCP "major" interface, can obtain system-wide
parameters.
Configure IE0 because the DHCP PRIMARY? (Y,N,HELP) [Y]:
Press ENTER to simply accept the default of Y. Then press E to exit the
Interfaces menu. You are again in the principle menu. Press 3 to enter the
Routing menu. Output:
DYNAMIC ROUTING Configuration
Dynamic routing has not been configured.
You could configure dynamic ROUTED or GATED routing.
You can not allow each on the identical time. If you would like
to vary from one to the opposite, you will need to disable the
present routing first, then allow the specified routing.
When you allow dynamic ROUTED routing, this host will use the
Routing Info Protocol (RIP) - Model 1 to hear
for all dynamic routing info coming from different
hosts to replace its inner routing tables.
It's going to additionally provide its personal Web addresses to
routing requests comprised of distant hosts.
When you allow dynamic GATED routing, it is possible for you to to
configure this host to make use of any mixture of the next
routing protocols to trade dynamic routing info
with different hosts on the community:
Routing Info Protocol (RIP) - Model 1 & 2
Router Discovery Protocol (RDISC)
Open Shortest Path First (OSPF)
Exterior Gateway Protocol (EGP)
Border Gateway Protocol (BGP-4)
Static routes
* Do you need to configure dynamic ROUTED or GATED routing [NO]:
Press ENTER to simply accept the default of NO. Output:
A default route has not been configured.
* Do you need to configure a default route [YES]:
Press ENTER to simply accept the default of YES. Output:
Enter your Default Gateway host title or handle:
Enter the IP of your router. Mine is 192.168.1.1. Press ENTER, output:
192.168.1.1 just isn't within the native host database.
If you wish to enter the default gateway within the native host
database, enter its host title. In any other case, enter <CR>.
Enter the Default Gateway host title []: router
I entered router. Press ENTER. You are now again within the core menu. Enter 4
to enter the BIND DNS Resolver menu. Output:
BIND RESOLVER Configuration
A BIND resolver has not been configured.
VSI TCP/IP Companies for OpenVMS helps the Berkeley Web Identify
Area (BIND) resolver. BIND is a community service that permits shoppers
to call sources or objects and share info with different objects
on the community.
Earlier than configuring your system as a BIND resolver, it's best to
first ensure that there's no less than one system on the community
configured as both a BIND major or secondary server for
this area.
You possibly can specify a BIND server by its handle or title;
nevertheless, if specified by title, an entry for it should
exist within the TCPIP$HOST database.
You may be requested one query for every server.
Press Return on the immediate to terminate the listing.
Enter your BIND server title:
I entered my router’s IP handle right here, 192.168.1.1. On the subsequent server
immediate, I left that vacant and pressed ENTER. You are now again within the Core
menu.
Press E to return to the principle TCP/IP menu, then press 6 to start out the
TCP/IP companies. Bunch of output, but it surely ought to finish with:
%TCPIP-I-FSIPADDRUP, IE0 192.168.1.23 major lively on node REMY1, interface IE0
Press <ENTER> key to proceed ...
192.168.1.23 is the DHCP handle. Press ENTER, then press E to exit this
menu.
The final step is to allow auto begin of the TCP/IP companies, in any other case, after a
reboot, you may don’t have any networking. Edit the next file: SYS$COMMON: and take away the exclamation level (
[SYSMGR]SYSTARTUP_VMS.COM!) from the
starting of the next line:
$!$ @SYS$STARTUP:TCPIP$STARTUP.COM
You possibly can edit this file with the next command:
EDIT /EDT SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM
You will enter a line editor. To change to visible mode, sort change adopted by
ENTER. You need to use the arrow keys to scroll down.
Exit visible mode with CTRL+Z, then sort exit to avoid wasting the file:
*exit
SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM;2 418 strains
It is best to now be capable to ping exterior sources from inside OpenVMS:
$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 information bytes2 418 strains
64 bytes from 8.8.8.8: icmp_seq=0 ttl=60 time=20 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=60 time=20 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=60 time=10 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=60 time=10 ms
----8.8.8.8 PING Statistics----
4 packets transmitted, 4 packets acquired, 0% packet loss
round-trip (ms) min/avg/max = 10/15/20 ms
Vice-versa, you must also be capable to ping the OpenVMS VM, from a Linux
machine for instance:
$ ping -c 4 192.168.1.23
PING 192.168.1.23 (192.168.1.23) 56(84) bytes of information.
64 bytes from 192.168.1.23: icmp_seq=1 ttl=64 time=0.464 ms
64 bytes from 192.168.1.23: icmp_seq=2 ttl=64 time=0.572 ms
64 bytes from 192.168.1.23: icmp_seq=3 ttl=64 time=0.589 ms
64 bytes from 192.168.1.23: icmp_seq=4 ttl=64 time=0.688 ms
--- 192.168.1.23 ping statistics ---
4 packets transmitted, 4 acquired, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 0.464/0.578/0.688/0.081 ms
That is all for the networking setup. Take a look at a reboot to be sure to’ve set
up autostart appropriately and do not forget to make a snapshot.
After a reboot it’s best to see the next within the operator console:
%TCPIP-S-STARTDONE, TCPIP$DHCP_CLIENT startup accomplished
%TCPIP-S-STARTDONE, TCP/IP Companies startup accomplished at 15-APR-2023 21:35:51.99
%EIA0, Hyperlink up: 1000 mbit, fdx, movement management (rcv solely), 08-00-27-66-2F-C3
SSH Setup
OpenSSH has been built-in into OpenVMS x86-64 V9.2 as a required layered
product and is put in unconditionally. Nevertheless, earlier than OpenSSH can be utilized,
a couple of guide steps are wanted after set up. Be sure to’ve arrange
TCP/IP as proven within the earlier paragraph.
Execute the next OpenSSH command procedures within the precise order listed:
@sys$frequent:[openssh.bin]ssh$create_account.com
Output:
Person Accounts and Person Identification Codes (UICs)
--------------------------------------------------
The OpenVMS OpenSSH set up creates two OpenVMS accounts:
SSH$SSH, SSH$SSHD. The default UIC group quantity for these new
accounts is determined by the next:
o If you're putting in the server for the primary time, the
default is the primary unused UIC group quantity, beginning
with 3655.
o If any of those accounts already exists, then the default
UIC group quantity won't be used to vary the UIC of
any present accounts.
o If previous account TCPIP$SSH already exists, then the default
UIC group quantity shall be used from TCPIP$SSH account.
For extra details about UIC group numbers, see the
OpenVMS System Supervisor's Handbook.
Enter default UIC group quantity for OpenSSH account
Group: [3656]
Settle for the default 3656, press ENTER. Plenty of output from OPCOM.
@sys$frequent:[openssh.bin]ssh$create_startup_file.com
Output:
SSH$ROOT is outlined as "SYS$SYSDEVICE:[SYS0.SYSCOMMON.OPENSSH.]"
Setting file protections...
File protections are set
Creating OpenSSH for OpenVMS root definition file SYS$COMMON:[SYS$STARTUP]SSH$DE
FINE_ROOT.COM...
File created
Save startup recordsdata
Setup OpenSSH logical atmosphere
@sys$frequent:[openssh.bin]ssh$generate_keys.com
Output, seems rather a lot like common OpenSSH:
Producing public/personal keys:
Producing public/personal dsa key pair.
Created listing '/sys$login/ssh'.
Your identification has been saved in /SSH$ROOT/ETC/ssh_host_dsa_key
Your public key has been saved in /SSH$ROOT/ETC/ssh_host_dsa_key.pub
The important thing fingerprint is:
SHA256:OQediEAOnpg6yL69HiqS7RQxBbsyz6DgeIIpRljgyhE system@REMY1.spnw.nl
The important thing's randomart picture is:
+---[DSA 1024]----+
|.Eoo+ |
|.=.* . . o . |
|ooB . . o o |
|B..+ o |
|@+o S . |
|OO . o |
|B*=. |
|*+= . |
|o+o+. |
+----[SHA256]-----+
Producing public/personal ecdsa key pair.
Your identification has been saved in /SSH$ROOT/ETC/ssh_host_ecdsa_key
Your public key has been saved in /SSH$ROOT/ETC/ssh_host_ecdsa_key.pub
The important thing fingerprint is:
SHA256:bFJnWSWvMfibCBdjlMH3z3ixBzYKEw5+ZRTqUYxYemM system@REMY1.spnw.nl
The important thing's randomart picture is:
+---[ECDSA 256]---+
| ++**o. |
| oo=*=o |
| .ooE=o.. |
| o.B=* +=. |
| . S.oooo *o|
| o o ..o..=|
| . o ..|
| |
| |
+----[SHA256]-----+
Producing public/personal rsa key pair.
Your identification has been saved in /SSH$ROOT/ETC/ssh_host_rsa_key
Your public key has been saved in /SSH$ROOT/ETC/ssh_host_rsa_key.pub
The important thing fingerprint is:
SHA256:3QudzNhe0tHxyYueML70Kwd1r1mKyFZ35esoI2x4094 system@REMY1.spnw.nl
The important thing's randomart picture is:
+---[RSA 3072]----+
| . |
| ..+|
| .oo|
| . B +.oo|
| S +oX.+oo|
| .+=+o =|
| o..=+= *.|
| . *===.=. |
| o.+o=Eo. |
+----[SHA256]-----+
Producing public/personal ed25519 key pair.
Your identification has been saved in /SSH$ROOT/ETC/ssh_host_ed25519_key
Your public key has been saved in /SSH$ROOT/ETC/ssh_host_ed25519_key.pub
The important thing fingerprint is:
SHA256:PAtsDDSTNMtm0BIASlOY2g3OW5+30MKxPGFuc6hGlvY system@REMY1.spnw.nl
The important thing's randomart picture is:
+--[ED25519 256]--+
|++*=*. |
|oo++o= |
|o+ +* |
|. +oo++. |
| o B=BS |
| . =.#.+o |
| + + B.. |
| o E . |
| . |
+----[SHA256]-----+
@sys$frequent:[openssh.bin]ssh$install_info.com
Output:
Purging put in recordsdata...
Efficiently completed
To mechanically begin OpenVMS OpenSSH throughout system startup
add the next line to the file SYS$MANAGER:SYSTARTUP_VMS.COM
after the TCPIP startup command process:
$ @SYS$STARTUP:SSH$STARTUP.COM
Outline symbols for all OpenSSH utilities:
$ @SSH$ROOT:[BIN]SSH$DEFINE_COMMANDS.COM
Begin SSH manually to check it with the next command:
@SYS$STARTUP:SSH$STARTUP.COM
Output:
Enabling service...
Efficiently enabled SSHD22 service
Additionally execute the next command to get a couple of good shell aliases:
@SSH$ROOT:[BIN]SSH$DEFINE_COMMANDS.COM ALL
To check OpenSSH, open one other Linux terminal or PuTTY session and attempt to login:
[21:49:50] [remy@gateway] [ ~ ]
$ ssh system@192.168.1.23
system@192.168.1.23's password:
Final interactive login on Saturday, 15-APR-2023 21:49:44.82
Final non-interactive login on Wednesday, 17-NOV-1858 00:00:00.00
1 failure since final profitable login
$ present system
OpenVMS E9.2-1 on node REMY1 15-APR-2023 21:49:57.38 Uptime 0 00:08:39
Pid Course of Identify State Pri I/O CPU Web page flts Pages
00000401 SWAPPER HIB 16 0 0 00:00:00.03 0 17
00000404 LANACP HIB 14 62 0 00:00:00.02 217 268
Within the telnet terminal, edit the startup file and ensure OpenSSH
is began at boot. The process is rather a lot like enabling TCP/IP.
Edit the next file: SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM and add the
OpenSSH begin instructions after the TCP/IP startup instructions, so beneath the
following line:
@SYS$STARTUP:TCPIP$STARTUP.COM
You possibly can edit this file with the next command:
EDIT /EDT SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM
You will enter a line editor. To change to visible mode, sort change adopted by
ENTER. You need to use the arrow keys to scroll down.
Add the next strains beneath the TCP/IP startup command:
@SYS$STARTUP:SSH$STARTUP.COM
@SSH$ROOT:[BIN]SSH$DEFINE_COMMANDS.COM ALL
Exit visible mode with CTRL+Z, then sort exit to avoid wasting the file:
*exit
SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM;4 422 strains
Strive a reboot and should you did all the pieces appropriately, SSH login must be potential
proper after a reboot.
If you wish to setup a different user for SSH entry or login with a
public key, please click on these hyperlinks. The directions from 2018 ought to
nonetheless work.
Activating the remainder of the licenses (PAKs)
Now that we’ve networking and OpenSSH arrange, it is a lot simpler to repeat the
hobbyist license file over to our OpenVMS set up and execute it.
Be sure to’ve received networking and OpenSSH setup, as described above. From
one other terminal or SCP shopper, copy over the X86COMMUNITY20240401.TXT
license file:
scp X86Community-20240401.txt system@192.168.1.23:
system@192.168.1.23's password:
X86Community-20240401.txt
Within the OpenVMS immediate, execute the file we simply copied over:
@X86Community-20240401.txt
Output:
%SHOW-I-NOLICMATCH, no licenses match search standards
%LICENSE-I-DISABLED, ABS-CLIENT-X86 EVAL-X86COMMUNITY-E202304019999 has been dis
abled
%LICENSE-W-NOENT, no license was loaded for this product - VSI ABS-CLIENT-X86
%LICENSE-I-ENABLED, ABS-CLIENT-X86 EVAL-X86COMMUNITY-E202304019999 has been enab
[...]
That output continues on for some time. A number of errors may seem, however afterwards
it’s best to be capable to see all of the licenses activated:
$ present license
Output:
Lively licenses on node REMY1:
------- Product ID -------- ---- Score ----- -- Model --
Product Producer Items PCL Activ Model Launch Termination
ABS-CLIENT-X86 VSI 6 1 0 0.0 (none) 1-APR-2024
ABS-SERVER-X86 VSI 6 1 0 0.0 (none) 1-APR-2024
ACMS VSI 6 1 0 0.0 (none) 1-APR-2024
ACMS-REM VSI 6 1 0 0.0 (none) 1-APR-2024
ACMS-RT VSI 6 1 0 0.0 (none) 1-APR-2024
AVAIL-MAN VSI 6 1 0 0.0 (none) 1-APR-2024
BASIC VSI 6 0 1 0.0 (none) 1-APR-2024
C VSI 6 0 1 0.0 (none) 1-APR-2024
CARTRIDGE-SERVER-V VSI 6 1 0 0.0 (none) 1-APR-2024
CMS VSI 6 1 0 0.0 (none) 1-APR-2024
COBOL VSI 6 0 1 0.0 (none) 1-APR-2024
CXX-V VSI 6 0 1 0.0 (none) 1-APR-2024
DFG VSI 6 1 0 0.0 (none) 1-APR-2024
DFS VSI 6 1 0 0.0 (none) 1-APR-2024
DQS VSI 6 1 0 0.0 (none) 1-APR-2024
DTM VSI 6 1 0 0.0 (none) 1-APR-2024
DTR VSI 6 1 0 0.0 (none) 1-APR-2024
DVNETEXT VSI 6 1 0 0.0 (none) 1-APR-2024
FMS VSI 6 1 0 0.0 (none) 1-APR-2024
FMS-RT VSI 6 1 0 0.0 (none) 1-APR-2024
FORMS VSI 6 1 0 0.0 (none) 1-APR-2024
FORMS-RT VSI 6 1 0 0.0 (none) 1-APR-2024
FORTRAN VSI 6 0 1 0.0 (none) 1-APR-2024
GKS VSI 6 1 0 0.0 (none) 1-APR-2024
GKS-RT VSI 6 1 0 0.0 (none) 1-APR-2024
LSE VSI 6 1 0 0.0 (none) 1-APR-2024
MMS VSI 6 1 0 0.0 (none) 1-APR-2024
OMNI VSI 6 1 0 0.0 (none) 1-APR-2024
OPENVMS-X86-BOE VSI 6 1 0 0.0 (none) 1-APR-2024
OPENVMS-X86-HAOE VSI 6 1 0 0.0 (none) 1-APR-2024
OSAP VSI 6 1 0 0.0 (none) 1-APR-2024
PASCAL VSI 6 0 1 0.0 (none) 1-APR-2024
PCA VSI 6 1 0 0.0 (none) 1-APR-2024
RMSJNL VSI 6 1 0 0.0 (none) 1-APR-2024
RTR-CL VSI 6 1 0 0.0 (none) 1-APR-2024
RTR-SVR VSI 6 1 0 0.0 (none) 1-APR-2024
SAVE-SET-MANAGER VSI 6 1 0 0.0 (none) 1-APR-2024
SW-RAID5 VSI 6 1 0 0.0 (none) 1-APR-2024
TDMS VSI 6 1 0 0.0 (none) 1-APR-2024
TDMS-RT VSI 6 1 0 0.0 (none) 1-APR-2024
VAXSET VSI 6 1 0 0.0 (none) 1-APR-2024
VMSCLUSTER VSI 6 1 0 0.0 (none) 1-APR-2024
VMSCLUSTER-CLIENT VSI 6 1 0 0.0 (none) 1-APR-2024
VOLSHAD VSI 6 1 0 0.0 (none) 1-APR-2024
X25 VSI 6 1 0 0.0 (none) 1-APR-2024
Congratulations! You have arrange OpenVMS TCP/IP and OpenSSH and activated the
hobbyist licenses. Properly finished! The subsequent a part of this information will cowl software program
set up, like a C++ compiler. When it is completed, I am going to submit the hyperlink right here!
This is a screenshot of DECWindows, operating by way of X11 forwarding. I am figuring
out the right way to begin CDE, however that fails for some cause. Once I get it working
anticipate an article on it:
Tags: alpha
, blog
, dec
, itanium
, openvms
, pdp
, vax
, vms
, vsi
, x86