Upgrading Your Multics System

From Multics Wiki
Jump to: navigation, search

Upgrading an Existing MR12.6 System to MR12.6f

There are two ways to upgrade an existing MR12.6 (a, b, c, d, e, or f beta) system to MR12.6f. The first is by far the simplest way -- by using the MR12.6e_to_MR12.6f_upgrade.ini simulator script. The second, which more closely mimics the historical way site administrators would upgrade a real hardware-based Multics system, uses a trivial simulator boot script that simply boots the Multics system tape and lets the operator enter all the commands manually. These two procedures are described below.

Upgrading Using the MR12.6e_to_MR12.6f_upgrade.ini Simulator Script

This process assumes you have a directory populated with an existing, runnable Multics system of an earlier release. The system should be shut down before you start.

  • Make a backup of your whole Multics host directory (or at least your *.dsk files)
  • In the directory with your existing system, add the following files from the MR12.6f distribution:
    • All 12 MR12.6f tapes (see Release Artifacts)
    • The MR12.6e_to_MR12.6f_upgrade.ini simulator script
    • The MR12.6f_boot.ini simulator script
  • Make sure your directory contains:
    • The Devices.txt file
    • All *.dsk files required to boot your system
  • If you have other logical volumes besides the root logical volume (RLV) in your existing system, update the MR12.6e_to_MR12.6f_upgrade.ini script to add each of these logical volumes. The script, as provided, only attaches the root.dsk (RLV) disk as disk0. If you have other disks, add additional lines of the form "attach diskN xxx.dsk" where N is an integer from 1 to 16 and where xxx is the name of the disk file containing your logical volume image.
  • Make sure you have a recent copy of the dps8 simulator on your path or in your Multics host directory.
  • Change directories to your Multics directory.
  • Run "dps8 MR12.6e_to_MR12.6f_upgrade.ini” (if dps8 isn't on your path, but in your Multics directory, you can use "./dps8 MR12.6e_to_MR12.6f_upgrade.ini" (Linux or macOS) or ".\dsp8 MR12.6e_to_MR12.6f_upgrade.ini" (Windows). Otherwise, reference the simulator executable by relative or absolute path.
  • Wait about 20 minutes (more if your system is slow).
  • Note that loading the tape 12.6fLDD_STANDARD_2 takes a very long time (due to its containing all the small include segments). Be patient.

When the script exits, you should have a bootable MR12.6f system in your current directory.

Boot your system by running the simulator with MR12.6f_boot.ini as the script parameter (e.g. "dps8 MR12.6f_boot.ini"). If you have more logical volumes than the root logical volume (RLV) be sure to update the MR12.6f_boot.ini script to include disk attachments for those other logical volumes.

Upgrading By Hand Using a Minimal Simulator Script

If you want to follow the instructions in the System Installation Bulletin (SIB) and perform an upgrade of a existing earlier release system the way site administrators would have done so in years past, you can following the instructions here.

This process assumes you have a directory populated with an existing, runnable Multics system. The system should be shut down before you start.

  • Make a backup of your whole Multics host directory (or at least your *.dsk files)
  • In the directory with your existing system, add the following files from the MR12.6f distribution:
    • All 12 MR12.6f tapes (see Release Artifacts)
    • The following (minimal) simulator script saved as "boot.ini":
attach -r tape0 12.6fMULTICS.tap
attach disk0 root.dsk
boot iom0 
  • Make sure your directory contains:
    • The Devices.txt file
    • All *.dsk files required to boot your system
  • If you have other logical volumes besides the root logical volume (RLV) in your existing system, update the boo.ini script to add each of these logical volumes. The above script only attaches the root.dsk (RLV) disk as disk0. If you have other disks, add additional lines of the form "attach diskN xxx.dsk" where N is an integer from 1 to 16 and where xxx is the name of the disk file containing your logical volume image.
  • Make sure you have a recent copy of the dps8 simulator on your path or in your Multics directory.
  • Change directories to your Multics directory.
  • Follow the instructions in Section 4 of the MR12.6f System Installation Bulletin (SIB), however, you can skip Step 1 (which has you deleting the unbundled directories while booted using your existing system). This is not necessary. Start with Step 2.
  • When you are asked to boot your system, run "dps8 boot.ini” (if dps8 isn't on your path, but in your Multics directory, you can use "./dps8 boot.ini" (Linux or macOS) or ".\dsp8 boot.ini" (Windows). Otherwise, reference the simulator executable by relative or absolute path.
  • Follow all the steps in Section 4.
  • Note that loading the tape 12.6fLDD_STANDARD_2 takes a very long time (due to its containing all the small include segments). Be patient.
  • At the end of the instructions in Section 4, you will be left with a running MR12.6f system.

When you shut your system down, you can boot it again using the same minimal boot.ini (but be prepared to manually enter all the pre-bce and bce commands required to bring your system up). Alternatively, boot your system by running the simulator with MR12.6f_boot.ini as the script parameter (e.g. "dps8 MR12.6f_boot.ini"). If you have more logical volumes than the root logical volume (RLV) be sure to update the MR12.6f_boot.ini script to include disk attachments for those other logical volumes.

Upgrading Your Terminal Type Table

When you upgrade Multics from a previous version, any changes to the Terminal Type Table (TTT) are no incorporated. This is because you may have updated your TTT locally, and it isn't obvious, in all cases, whether merging in the new TTF definitions is safe. If you wish to merge in any new terminal types, you can follow these instructions:

  • Locate any new terminal types you wish to integrate into your TTT from the system source for the TTT. This is located in >tools>TTF.ttf. (TTF stands for Terminal Type File).
  • Using an editor (emacs), select the new TTF entries and copy them to "clipboard" (called "kill ring" in emacs)
  • Then read in your copy of the TTF. This is located in >udd>sa>a>TTF.ttf.
  • Find a suitable place to place the new entries in this file and yank them from the kill ring.
  • Save the updated TTF.ttf.
  • Exit the editor
  • In the >udd>sa>a directory, compile the TTF into a ttt. Use the command "cv_ttf TTF.ttf". This will produce the compiled TTT in the file >udd>sa>a>TTF.ttt.
  • Install the updated TTT using the command "install TTF.ttt"

Note: the above should be done from a *.SysAdmin account.