CYBIS (R2) Operation and Usage (Virtual Book)
This Virtual Book contains chapters organized in a suggested order but you are free to select whatever topics address your needs best.
Installation instructions for the CYBIS Release 1, and underlying NOS 2.8.7 system may be found on Kevin Jordan's GitHub Repository.
Abstract
For CYBIS Release 2, there have been significant changes to the PLATO (CYBIS) application and a large number of procedures, lessons, and configuration files. Therefore we have decided to make this release available in a “ready to run” (pre-built) configuration.
The project provides all tools required to deploy CYBIS Release 2 with the exception of the dtCYBER application itself. Due to the complexity of building DtCyber on multiple platforms, the project will provide the following files:
cyber.iniThere are some tools which may also be made available.
Building the DtCyber executable is an exercise left to the hobbyist as a working DtCyber executable is required prior to taking any other steps. This approach should be sufficient for most hobbyists but when upgrading from a previous system, the operator will need to have considerable knowledge of the underlying systems (NOS and CYBIS).
The hobbyist is expected to have build a working CYBIS Release 1 system before taking the steps necessary to upgrade to CYBIS Release 2.
Scope Limitation
This Virtual Book not provide the level of detail required to pursue a full system upgrade from CYBIS Release 1.
Those details are left to developers who have demonstrated the proficiencies or interest in learning at that level.
Prebuilt Binaries
Although the build of DtCyber for a users specific platform is highly encouraged, it is sometimes impractical. As time permits, updated installers will be prepared and made available.
Retro1.Org cdc.io.While there are no simple answers to these considerations, you may have made it easier or harder on yourself depending on what you did with the original installation.
In the original installation of CYBIS/R1, there were some errors in configuration of group s that inhibited anyone's ability to submit batch jobs. To remedy that - the CYBIS/R2 version of the group s file was corrected. This presents a conundrum if you want to keep the user information in your current group file.
It turns out that fixing the original problem is a (somewhat) trivial matter to resolve using built-in system lessons.
Also - when CYBIS/R1 was built, there were no “GENERAL” packs created so all new or updated files were left, comingled, with the other unmodified files.
These, and many other considerations led to the creation of the tool: CDC.IO.
This tool (written in Python3) is designed to perform many system-to-system and pack-to-pack activities including the transfer of individual files between systems. At this time - the utility is only capable of reading and writing PLATO files between various systems.