MULTICS INSTALLATION INSTRUCTIONS RELEASE 12.8 PREPARED BY: DPS8M Development Team August 8, 2023 Copyright, (C) DPS8M Development Team, 2023 CONTENTS Page Section 1 Introduction . . . . . . . . . . . . . . 1-1 Section 2 Description of Package . . . . . . . . . 2-1 Library Naming Conventions . . . . . . 2-1 Contents of MR12.8 Package . . . . . . 2-2 Section 3 FCO and Firmware Status . . . . . . . . . 3-1 Section 4 Instructions for Sites Updating to MR12.8 from an Earlier Release . . . . . . . . 4-1 Step 1: Pre-Installation Preparation 4-2 Step 2: Installation to BCE (early) Level . . . . . . . . . . . . . . . . 4-2 Step 3: Changes to Config Deck . . . 4-3 Step 4: Installation to BCE (boot) Level . . . . . . . . . . . . . . . . 4-3 Step 5: Fix PDT cutoff values . . . . 4-5 Step 6: ACLs and Ring Brackets . . . 4-6 Step 7: Check quota on >dumps . . . . 4-7 Step 8: System Cleanup . . . . . . . 4-7 Section 5 Instructions for Sites Installing for First Time . . . . . . . . . . . . . . . 5-1 Step 1: Logical Volume Assignments . 5-1 Step 2: RPV Initialization . . . . . 5-4 Step 3: Configuration . . . . . . . . 5-6 Step 4: Initializing Root Volumes . . 5-7 Step 5: Additional Configuration Parameters . . . . . . . . . . . . . 5-8 Step 6: Reload of Executable Libraries . . . . . . . . . . . . . . 5-9 Step 7: Setting and Checking Access . 5-11 Step 8: Setting Volume Quota . . . . 5-12 Step 9: Reload of Remaining Release Tapes . . . . . . . . . . . . . . . . 5-13 Step 10: Fix Permissions on Libraries 5-14 Step 11: Running acct_start_up.ec . . 5-14 Step 12: Multics Communications System . . . . . . . . . . . . . . . 5-14 Step 13: Complete Accounting Startup 5-17 Step 14: Check Gate ACLs . . . . . . 5-18 iii SIB12.8 CONTENTS (cont) Page Step 15: Set Quota on >dumps . . . . 5-20 Step 16: Save Checkpoint . . . . . . 5-20 Step 17: Tailor System and Register Projects . . . . . . . . . . . . . . 5-20 Step 18: Setup Volume Backup/Reloader 5-20 Step 19: Setup Directory Quota . . . 5-21 Step 20: System Cleanup . . . . . . . 5-22 Appendix A Module Changes since MR12.7 . . . . . . . A-1 New Info Segments since MR12.7 . . . . A-2 Modified Info Segments since MR12.7 . A-3 Deleted Info Segments since MR12.7 . . A-4 New Segments since MR12.7 . . . . . . A-5 Modified Segments since MR12.7 . . . . A-7 Deleted Segments since MR12.7 . . . . A-11 New Include Files since MR12.7 . . . . A-12 Modified Include Files since MR12.7 . A-13 iv SIB12.8 SECTION 1 INTRODUCTION This document describes the MR12.8 package. Detailed instructions for installation of a system for the first time and upgrading to MR12.8 from an earlier release constitute the major portion of this document. No attempt is made to document features of MR12.8 other than those directly required for its installation. Software Releases prior to MR12.8 are no longer supported. All sites running pre-MR12.8 software are strongly encouraged to upgrade to MR12.8 as soon as possible. Note to simulator users: It is recommended that only versions R3.0.1 or later of the dps8m simulator be used with MR12.8. Older versions of the simulator will work, but may lead to unexpected results. Booting MR12.8 with a version of the dps8m simulator older than R3.0.1 will result in a warning message emitted to the operator console and to the syserr log that looks similar to the following: Warning: You are running an old version of the simulator. Please update to R3.0.1 or later. See https://dps8m.gitlab.io/ for details. Introduction 1-1 SIB12.8 SECTION 2 DESCRIPTION OF PACKAGE LIBRARY NAMING CONVENTIONS The primary pathnames on most of the system directories are somewhat lengthy. For this document, abbreviated (added) names are used in lieu of the primary name. The following list gives the primary and abbreviated names used in this document. >daemon_dir_dir >system_library_1 >ddd >sl1 >documentation >system_library_obsolete >doc >obs >system_library_tandd >system_library_standard >firmware >sss >library_dir_dir >system_library_tools >ldd >tools >process_dir_dir >system_library_unbundled >pdd >unb >system_control_1 >user_dir_dir >sc1 >udd The system directories firmware and obs are not included in the standard system search rules. Segments in these directories must either be accessed by absolute pathnames or by changing the system search rules via the set_system_search_rules command added to the system_start_up.ec. Package Description 2-1 SIB12.8 CONTENTS OF MR12.8 PACKAGE MR12.8 includes this document, a set of magnetic tape images, and accompanying documentation. Sites not installing Multics for the first time will be able to proceed to the MR12.8 release from MR12.3, MR12.4, MR12.5, MR12.6a, MR12.6b, MR12.6c, MR12.6d, MR12.6e, MR12.6f, or MR12.7. Sites upgrading to MR12.8 from an earlier release of Multics, refer to Section 4. Sites installing Multics for the first time should refer to Section 5. The instructions in each section will provide a procedure to guide a site through the installation. Documentation for some of the new features and tickets resolved in this release is contained in the directory >doc>MR12.8, which is part of this release. This is a total software release. It contains a complete set of all modules contained in the Multics standard system as well as all currently available unbundled products. Appendix A lists modules added, modified or deleted since MR12.7. A set of master tapes was generated for this release. Package Description 2-2 SIB12.8 Tape Names Description 12.8EXEC Complete dump of Multics executable libraries >sss, >tools, >obs> and >firmware. 12.8LDD_STANDARD Complete dump of all standard library source, object, include files and info segs. 12.8UNBUNDLED Complete dump of Multics unbundled libraries. Includes all of >unbundled, >ldd>unbundled, >ldd>mcs and >system_library_3rd_party. 12.8MULTICS Complete Multics System Tape (MST). 12.8AML Complete dump of the Author Maintained Library on GHM. Includes all of >aml and >ldd>aml. >doc>aml_info is included on the 12.8LDD_STANDARD tape. 12.8MISC The compout segment for this document and other supporting documentation, if any, are contained on this tape in >doc>MR12.8. Last minute changes, if any, made to software modules after generation of the above tapes are also contained on this tape. This is the last tape to be loaded. Package Description 2-3 SIB12.8 Tape File Name Describes _system_book_ MR12.8 hardcore modules srb MR12.8 Software Release Bulletin sib MR12.8 Software Installation Bulletin error_msgs.compout Listing of hardcore error messages error_msgs.toc.compout A TOC of hardcore error messages Tickets_fixed_in_MR12.8 A list of the tickets fixed in this release Package Description 2-4 SIB12.8 SECTION 3 FCO AND FIRMWARE STATUS There are no differences in FCOs and firmware from MR12.6. Firmware Status 3-1 SIB12.8 SECTION 4 INSTRUCTIONS FOR SITES UPDATING TO MR12.8 FROM AN EARLIER RELEASE MR12.8 supports upgrading from any of the following releases: MR12.3 MR12.4 MR12.5 MR12.6a MR12.6b MR12.6c MR12.6d MR12.6e MR12.6f MR12.7 If problems are encountered in any of the steps listed below, return to the last step known to be successful and retry the steps. Pay particular attention to procedure. This entire procedure was verified by the DPS8M Development Team, but some hardware/software differences may exist at a particular site. In this section, two formats of text are used to indicate the typing of input into the system. This input usually is a command line, but could be data typed in response to a query from the operator console. Strings of input, and output messages of importance are indicated on separate lines. In addition, all input to the system is to be typed in lowercase, except when indicated by the occurrence of both uppercase and lowercase in the input line. User input is preceeded by an exclamation mark (!). System display output is shown as is, except when the displayed line exceeds the page margins for this document. When this occurs, the displayed line is split into two lines, with the second line indented from the first. Instructions - Updating 4-1 SIB12.8 STEP 1: PRE-INSTALLATION PREPARATION It is recommended that sites back up their systems before upgrading to MR12.8. For those sites running under the DPS8M emulator, it is recommended that you shut down your system, and make backup copies of all disk volumes (.dsk files). Due to the method by which unbundled software is dumped, normal trimming during reloading of new software does not occur. To ensure that unbundled directories are clean, execute the following before shutting down your existing system for the last time. Enter admin mode and type: cwd >system_library_unbundled answer yes -bf hpdl ([files **]) cwd >library_dir_dir>unbundled>source answer yes -bf hpdl ([files **]) cwd >library_dir_dir>unbundled>object answer yes -bf hpdl ([files **]) To shut the system down and continue to the next step type: ame shutdown Once you have deleted the unbundled directories, you will not be able to boot your existing system for normal service until you complete the next few steps to upgrade your system (and reinstall the unbundled executables). STEP 2: INSTALLATION TO BCE (EARLY) LEVEL For sites running under the DPS8 emulator, prepare a minimal INI file that looks like this: attach -r tape0 12.8MULTICS.tap attach disk0 root.dsk clrautoinput autoinput \z boot iom0 Do not include other commands to boot the system. If your RLV disk is not called "root.dsk", change the "attach disk0" command to reference your RLV disk file. If your RLV disk is not mounted on disk0, change this disk designation to the correct one. If you have more than one disk, use the appropriate "attach diskN " commands from your current Multics installation INI file. Instructions - Updating 4-2 SIB12.8 At this time you will be asked to input the RPV location in channel, controller, device and unit number format: bootload_0: Booting system MR12.8 generated 07/19/23 1756.0 pdt Wed. 0058.9 announce_chwm: 431. pages used of 512. in wired environment. 0058.9 announce_chwm: 708. words used of 1024. in int_unpaged_page_tables. find_rpv_subsystem: Enter RPV data: M-> [auto-input] rpv a11 ipc 3381 0a 0058.9 load_mst: 954. out of 1048. pages used in disk mst area. bce (early) 0059.0: M-> STEP 3: CHANGES TO CONFIG DECK There are no config deck changes for MR12.8. To examine, display, and possibly change the current contents of the config deck, as saved in the "conf" partition, enter the following commands: config 1,$p After having made any necessary changes, exit the editor by typing "w" and "q". The "w" request will verify card syntax. The "q" request will leave the qedx editor and place the user at the bce (early) level. STEP 4: INSTALLATION TO BCE (BOOT) LEVEL Continue installation of BCE by typing: bce (early) 0059.0: M-> bce System was last shutdown at: Wednesday, July 19, 2023 17:58:08 pdt Current system time is: Wednesday, July 19, 2023 17:59:01 pdt. Is this correct? M-> ! yes You may see the following message: Warning: You are running an old version of the simulator. Please update to R3.0.1 or later. See https://dps8m.gitlab.io/ for details. If you do, you should consider updating your version of the simulator to the version specified in the warning message. You may also see messages like these: The current time is more than the supplied boot_delta hours beyond the unmounted time recorded in the RPV label. Is this correct? M-> ! yes Instructions - Updating 4-3 SIB12.8 The current time I'm using is more than 12 hours after the last shutdown time recorded in the RPV label. Are you sure this is correct? M-> ! yes Now boot the system to Initializer ring-1 command level. Type: bce (boot) 1325.5: ! boot Multics MR12.8 - 07/19/23 1756.0 pdt Wed. Command: At Initializer ring-1 command level, type: alv -all You will now load the system libraries from tape. The release tapes should be reloaded in this specific order: 12.8EXEC 12.8LDD_STANDARD 12.8UNBUNDLED 12.8AML 12.8MISC To reload the libraries type: reload_system_release -nosetlvid When the system asks "Input tape label:" type: where is the reel identification specified for the next tape to be reloaded. Enter for each library tape, as specified above, and in the order shown above. When all tapes are loaded, shut down the system and, if you wish to run service Multics at this time, reboot it to "standard" (not "startup") mode: type: Command: M-> ! shut 1232.9 shutdown complete bce (boot) 1232.9: M-> ! boot stan 1233.1 CPU A: Model #: DPS 8/SIM M; Serial #: 0; Ship date: 230709; PROM Layout Version: 2; Simulator Release: X3.0.1.1 (2023-07-09); Build Number: ; Build Arch: arm64; Build OS: Darwin; Target Arch: Unknown Target Arch.; Target OS: Unknown Target OpSys. Multics MR12.8 - 08/08/23 1233.1 pdt Tue Ready M-> ! admin r 12:33 0.913 4486 Instructions - Updating 4-4 SIB12.8 M-> shut boot stan admin (if any) Note: the reason why you should shut down Multics and restart it is because there appears to be an issue with running service Multics ("startup" or "star") directly after reloading all the release tapes when their are absentee jobs in the queue that run concurrently with the remaining steps. STEP 5: FIX PDT CUTOFF VALUES If you are upgrading from MR12.3 or MR12.5, the existing PDTs will most likely be past their project cutoff dates. This is because neither MR12.3 nor MR12.5 supported dates past 1999, and most likely (especially since MR12.8 was released in the year 2021), the current date is well past 1999. Without adjusting these cutoff dates, no one, including system daemons and SysAdmin personnel, would be able to login. If you are upgrading from an MR12.6 or MR12.7 release, and you already fixed the PDT cutoff values when, or before, you upgraded to your currently running release, you can skip this section. In this step, you run cv_pmf on any undelegated projects. You should update the PDTs for the SysDaemon, SysAdmin, and Daemon projects. You can update any other PDTs at this time, although you can also update those from an interactive login session after the system is brought up in a normal session. Follow the steps below, and add any other PDTs you wish to the list. Note: PMFs for these projects may either be in >udd>sa>a or in >udd>sa>a>pmf.archive. It is a good idea to check to see if the PMFs are in >udd>sa>a before extracting them from the pmf.archive, in case the ones in >udd>sa>a are newer than the ones in the archive. cwd >udd>sa>a ls *.pmf ac t pmf Based on whether the PMFs you want to convert are in >udd>sa>a or >udd>sa>a>pmf.archive, either extract them from pmf.archive or skip that step. Then, run cv_pmf on each of these PMFs. ac x pmf (SysAdmin SysDaemon Daemon).pmf cv_pmf (SysAdmin SysDaemon Daemon) cp (SysAdmin SysDaemon Daemon).pdt >sc1>pdt>== -force Instructions - Updating 4-5 SIB12.8 Note: do not use the "install" command to install the PDTs. Otherwise, when the system is brought up in normal mode, the daemons may try to login before the delayed installation of system tables is performed, causing those logins to fail due to product cutoffs. STEP 6: ACLS AND RING BRACKETS Check the ACLs for the following gates: >sss>dm_admin_gate_ >sss>dm_daemon_gate_ >tools>installation_tools_ >tools>pnt_admin_gate_ >tools>pnt_login_gate_ >tools>pnt_network_gate_ >tools>pnt_priv_gate_ >sss>metering_gate_ >sss>queue_admin_. The ACLs on these gates are as they appear on Gold Hill Multics (GHM), the Multics development and integration system, and should be restricted. The ACL for these gates are site dependent and should be changed to meet each site's needs. The dm_admin_gate_ and dm_daemon_gate_ should be restricted to data management administrators or daemons. The installation_tools_ gate should be restricted to system library maintainers. All persons on the ACL for metering_gate_ have access to the Multics metering data. All persons on the ACL for queue_admin_ are permitted to move absentee and daemon requests for themselves and other users to different queues. Users not on this ACL are only able to move their own requests. The Initializer must have access to queue_admin_. This capability is also dependent on extended access to the .ms segments. The various pnt__gate_ acls should be restricted to the following minimums for correct system operation: >t>pnt_admin_gate_ re *.SysDaemon.* re *.SysAdmin.* >t>pnt_fs_gate_ re *.*.* Instructions - Updating 4-6 SIB12.8 >t>pnt_login_gate_ re Initializer.SysDaemon.* re *.SysAdmin.* >t>pnt_network_gate_ re Initializer.SysDaemon.* re IMFT.Daemon.* re Card_Input.Daemon.* re *.SysDaemon.* >t>pnt_priv_gate_ re Initializer.SysDaemon.* r *.SysDaemon.* re *.SysAdmin.* STEP 7: CHECK QUOTA ON >DUMPS Systems prior to MR12.8 may not have quota specified on the >dumps directory. If this is the case, you would see an error message from Utility.SysDaemon of the form: monitor_quota: The requested action was not performed. The quota of >dumps is 0, a record limit needs to be specified. To fix this, simply move some quota to >dumps. It is recommended that at least 5000 records or quota be provided to >dumps. mq >dumps +5000 STEP 8: SYSTEM CLEANUP The system is now ready for normal operation under MR12.8. Exit admin mode and start up normal service: M-> !ame Ready M-> ! startup 1234.8 Loading FNP d, >user_dir_dir>SysAdmin>a>mcs.7.6c>site_mcs 7.6c 1234.8 FNP d loaded successfully scavenge_vol: No volumes found Ready M-> Following a reasonable period of MR12.8 operation, it is suggested that sites delete any segments created as part of this procedure. It is also recommended that sites salvage their systems and fix quota by running Salvager.SysDaemon, executing the following command: Instructions - First Time 4-7 SIB12.8 x repair salvquota > -rebuild -dcf The reload_system_release command creates large map segments in the >reload_dir directory. These are not required for normal system operation. You may delete them in order to conserve disk space. Anyone on the SysAdmin project can delete the map files, which have names like !BBBKQBlDQKxQzh.reload.map. Alternatively, in admin mode on the operator console, you may delete these map files with a command such as "dl >reload_dir>**.reload.map". Instructions - First Time 4-8 SIB12.8 SECTION 5 INSTRUCTIONS FOR SITES INSTALLING FOR FIRST TIME The following basic procedure must be performed when installing Multics for the first time. STEP 1: LOGICAL VOLUME ASSIGNMENTS Choose logical volume assignments. Decide how many logical volumes are needed and how many physical volumes are to be in each. Most installations have the following: Logical Volume Contents root >system_control_1 >system_library_standard >system_library_tools >system_library_unbundled >system_library_auth_maint >system_library_1 >documentation >daemon_dir_dir >dumps >system_library_tandd >system_library_obsolete >system_library_3rd_party >site >lv partitions public >user_dir_dir >library_dir_dir>include ldd >library_dir_dir Other logical volumes may be set up for specific applications. Instructions - First Time 5-1 SIB12.8 The assignment decision requires the system administrator to balance the costs of seek interference and breakage against the advantages of being able to define and process logically different collections of data. Databases used for only a few hours a day or only a few days a month are natural candidates for allocation to a separate logical volume. Breaking up the system's storage into several logical volumes also allows the site to operate without all logical volumes mounted if hardware goes down. For example, an MPC or channel might go down, halving the system's disk drive capacity. Instructions - First Time 5-2 SIB12.8 Logical volume assignments might be as follows: Logical Volume Contents root >system_library_tandd >library_dir_dir >system_library_obsolete >system_library_standard >system_library_tools >system_library_unbundled >system_library_3rd_party >daemon_dir_dir >documentation >dumps >system_library_1 >system_library_auth_maint >user_dir_dir>Daemon >user_dir_dir>SysAdmin >user_dir_dir>SysDaemon >user_dir_dir>SysMaint >site >lv partitions Mcc >user_dir_dir>Mcc Multics_Pubs >user_dir_dir>Pubs >user_dir_dir>Multics Old_Dumps >dumps>Old_dumps Public >user_dir_dir >experimental >process_dir_dir >ldd>include list_1 >library_dir_dir>listings>hard >library_dir_dir>mcs >library_dir_dir>unbundled list_2 >library_dir_dir>listings These particular assignments give a wide range of flexibility and Multics can run with only the root logical volume mounted, or with one or two of the less critical logical volumes not mounted due to unavailability of disk drives. For example, logical volumes, list_1 and list_2, can easily be demounted. This frees two disk drives to be available for use with other more critical logical volumes. Installations that wish to use the Access Isolation Mechanism Instructions - First Time 5-3 SIB12.8 (AIM) by specifying more than one access category (sensitivity level) should specify the maximum and minimum categories for one or more volumes and thus ensure that sensitive data is confined to a few packs, or that packs are not "contaminated" with information requiring special precautions. The logical volumes that hold process directory segments must be chosen. Because of the heavy usage of process directory segments, these segments should be spread over as many physical volumes as possible. One or more logical volumes may be selected to hold process directory segments, using the set_pdir_volumes command in system_start_up.ec. In the supplied system_start_up.ec, a single logical volume, named public, is selected. However, since a site may not have a "public" logical volume, this assignment is commented out. This command line should be changed to select a set of publicly accessible and permanently mounted logical volumes containing as many physical volumes as possible, subject to some constraints. Site maintenance personnel are responsible for ensuring there is always enough space available on the selected logical volumes to hold the process directory segments. The process directory placement algorithm causes process directory creations to be made on each logical volume in proportion to the number of physical volumes in the logical volume. Ensure that enough storage will be available. About 5% of each volume is used for the VTOC and volume map. In addition, some breakage is unavoidable. Since the system handles running out of storage without crashing, and since it is possible to add physical volumes to a logical volume dynamically, logical volumes can be defined with fewer physical volumes than their maximum anticipated size. STEP 2: RPV INITIALIZATION Boot the Multics System Tape (MST). Multics will prompt with: bootload_0: Booting system MR12.8 generated 07/19/23 1756.0 pdt Wed. 0058.9 announce_chwm: 431. pages used of 512. in wired environment. 0058.9 announce_chwm: 708. words used of 1024. in int_unpaged_page_tables. find_rpv_subsystem: Enter RPV data: M-> Since you are cold booting Multics and initializing the RPV (destroying all content on the drive), answer with the following: cold a11 ipc 3381 0a Multics will respond with: find_rpv_subsystem: Booting cold will destroy all data on the RPV. Are you sure that you want to boot cold? M-> ! yes Instructions - First Time 5-4 SIB12.8 Default RPV layout: (Respond "end" to use it.) Average seg length = 2.00 VTOC size = 13495 pages, 26974 vtoces. 53950 paging records. Constrained by average seg length. part hc 13495. 2500. part conf 15995. 4. part dump 72660. 2000. part log 72404. 256. part file 72149. 255. part bce 69949. 2200. request: M-> These are the default partition assignments. Any changes to the default partitions or RPV parameters can be redefined by using the "startover" request in init_vol. The system installer should review the write-up of init_vol in the Multics Administration, Maintenance, and Operations Commands Manual, Order Number GB64-00, prior to the installation. Sizes for the various partitions and their locations can be modified based on the needs of the site. Enter the following: request: M-> ! startover request: M-> ! asl 2.0 request: M-> ! part hc low 2500 request: M-> ! part conf low 4 request: M-> ! part dump high 32000 request: M-> ! part log high 256 request: M-> ! part file high 255 request: M-> ! part bce high 2200 request: M-> ! list Average seg length = 2.00 VTOC size = 7495 pages, 14974 vtoces. 29950 paging records. Constrained by average seg length. part hc 7495. 2500. part conf 9995. 4. part dump 42660. 32000. part log 42404. 256. part file 42149. 255. part bce 39949. 2200. request: M-> ! end Next Multics responds with: init_empty_root: Begin rpv initialization. This will take some time. init_empty_root: rpv initialized; 29950 records. Instructions - First Time 5-5 SIB12.8 2352.8 find_file_partition: Initializing file partition. Data not in expected format. 2353.3 load_mst: 947. out of 1048. pages used in disk mst area. bce (early) 2353.6: M-> STEP 3: CONFIGURATION Build the configuration description as follows (user input preceeded by an exclamation mark (!): ! config ! 1,$d ! a ! [User types in configuration fields as defined in the System Maintenance Procedures, Order Number AM81-03] ! \f ! w ! q As an example, you can use the following config deck: clok -delta 7. -zone pst iom -tag a -port 0 -model iom -state on iom -tag b -port 1 -model iom -state on cpu -tag a -port 7 -state on -type dps8 -model 70. -cache 8. mem -port a -size 4096. -state on mem -port b -size 4096. -state on mem -port c -size 4096. -state on mem -port d -size 4096. -state on ipc -type fips -iom a -chn 13 -nchan 1 prph -subsys dska -iom a -chn 13 -nchan 1 -model 3381. -number 16 prph -device fnpd -iom a -chn 20 -model 6670. -state on mpc -ctlr mtpa -iom a -chn 12 -nchan 1 -model 501. prph -subsys tapa -iom a -chn 12 -nchan 1 -model 500. -number 16. prph -device opca -iom a -chn 36 -model 6001. -ll 256. -state on mpc -ctlr urpa -iom a -chn 15 -model 8004. -nchan 1 prph -device rdra -iom a -chn 15 -model 301. mpc -ctlr urpb -iom a -chn 16 -model 8004. -nchan 1 prph -device puna -iom a -chn 16 -model 301. mpc -ctlr urpc -iom a -chn 17 -model 8004. -nchan 1 prph -device prta -iom a -chn 17 -model 1600. -train 600. -ll 136. part -part hc -subsys dska -drive 00a part -part dump -subsys dska -drive 00a root -subsys dska -drive 00a sst -4k 2000. -16k 1000. -64k 500. -256k 250. dbmj 64. 700. 400. 150. 60. 25. tcd -apt 500. -itt 1000. intk warm 0. rpvs star Do not enter any part cards at this time, except for those partitions defined on the rpv. Also, make the root card specify only the rpv. Instructions - First Time 5-6 SIB12.8 Continue booting bce. bce (early) 0020.0: M-> ! bce System was last shudown/ESD at: Monday, December 31, 1900 16:00:00 pst Current system time is: Saturday, July 30, 2023 15:21:07 pst. Is this correct? M->! y bce (boot) 1325.5 : M-> ! boot -cold Do you really wish to boot cold and there by destroy the system hierarchy? M-> ! yes 1655.9 init_syserr_log: Syserr LOG partition reinitialized. 1657.0 volume_registration_mgr_$check_volume_registration: Reregistered public LV root LVID 371626522536 (Initializer.SysDaemon.z) 1657.0 volume_registration_mgr_$check_volume_registration: Reregistered PV rpv PVID 371626522524 in LV root (Initializer.SysDaemon.z) disk_table_: New disk_table created Multics MR12.8 - 07/19/23 1756.0 pdt Wed. Command: Ignore the messages prefaced by disk_table_ and volume_registration_mgr_. STEP 4: INITIALIZING ROOT VOLUMES Initialize each new root volume except the RPV with the init_vol command. For better performance, it is advisable to place a hardcore partition (hc) on each physical volume of the Root Logical Volume (RLV). The placement of the hardcore partition on each volume must be low. The recommended size of additional partitions is 2500 records divided by the number of physical volume used. The RPV size should remain 2500 records to allow the system to boot with only an RPV mounted. For most volumes the command looks like: init_vol PV_NAME DRIVE_NAME -rlv {-special} For example: Command: M-> ! init_vol root2 dska_00b -rlv volume root2 68111 records Command: M-> ! init_vol root3 dska_00c -rlv volume root3 68111 records Command: M-> Instructions - First Time 5-7 SIB12.8 For those volumes that are to have partitions, or an average segment length other than the default of five records, add the optional "-special" as a third argument. The command then asks for instructions about the partition location. Hardcore partitions, for additional root volumes, should be specified as they are initialized. You may type one or more of the following: part NAME low nrec part NAME high nrec avg fff.ff list complete initialization by typing: end An example of typing the init_vol for an MSS0451/400 with an alternate partition on a RLV drive is: init_vol root2 dska_02 -rlv -special part alt high 141 (Note: 451 disk only) part hc low 625 (Example: 2500/4 root volumes) end when done type: shut STEP 5: ADDITIONAL CONFIGURATION PARAMETERS At bce (boot) level enter the configuration deck editor by typing "config". The PART cards and ROOT card should be added to the deck. Subsequent boots divide the hardcore supervisor among all hardcore partitions. The following script is provided as an example where a root card exists in the configuration deck and a part card does not exist. Parameters of cards will vary according to the configuration of individual sites. User input is preceeded by an exclamation mark (!). bce (boot): M-> ! config M-> ! /root/ root -subsys dska -drive 00a M-> ! s/$/ -subsys dska -drive 00b -subsys dska -drive 00c/p root -subsys dska -drive 00a -subsys dska -drive 00b -subsys dska -drive 00c M-> ! w M-> ! q bce (boot) 1215.2: M-> reinit Instructions - First Time 5-8 SIB12.8 STEP 6: RELOAD OF EXECUTABLE LIBRARIES Do a normal boot "BOOT". bce (boot) 1641.1: M-> ! boot Multics MR12.8 - 07/19/23 1756.0 pdt Wed. Command: M-> While at ring-1 initializer command level load the executable libraries. This is done as follows: Command: M-> ! reload -nosetlvid Only the system libraries (12.8EXEC) should be reloaded at this time. The -nosetlvid control argument ignores the logical volume ID on the tape when a directory is being reloaded. Input tape label: M-> ! 12.8EXEC Mounting tape 12.8EXEC for reading 1521.9 RCP: Attached tapa_01 for Initializer.SysDaemon.z 1521.9 RCP: Note (tapa_01) - 12.8EXEC,sys CONSOLE: ALERT 1522.0 RCP: Mount Reel 12.8EXEC without ring on tapa_01 for Initializer.SysDaemon.z <12.8EXEC.tap> attachTape selected unit 1 Mounted Multics volume "12.8EXEC" (recorded at 800 BPI), on device tapa_01 Begin at 02/05/20 1522.0 pst Thu End of reel encountered. iload: Are there any more tapes to be reloaded? M-> ! no 1522.3 RCP: Detached tapa_01 from Initializer.SysDaemon.z Normal termination 02/06/20 1729.1 pst Thu. Command: M-> At this point, shut the system down and reboot to ring 4 command level: M-> ! shut 1230.1 shutdown complete. bce (boot) 1231.1: M-> ! boot standard (ignore the messages from sc_init_.) Multics MR12.8 - 07/19/23 1756.0 pdt Wed. Ready M-> ! admin admin: Entry not found. Could not retrieve admin password from the PNT to check admin password. Entering admin mode. [NOTE: This error message is repeated each time admin is entered until a password has been set.] Register and initialize all non-RLV volumes. For ease of typing, use of lower case names is recommended. Use the add_volume_registration (avr) command as in the following Instructions - First Time 5-9 SIB12.8 example: ! avr -pv pub01 -lv public -serial 233-81 -model 451 add_volume_registration: LV "public" does not exist. Do you wish to create it? M-> ! yes add_volume_registration: Registered PV "pub01" (pvid 100172223140) on new LV "public" lvid 100172223005). r 14:15 1.473 8 to create registration entries for each logical and physical volume. The registration file for the root logical volume is created automatically by the bootload. Since the default model number is 451, use the change_vol_registration command, if necessary, to set the correct value of model number on the rpv. The serial number can also be set as follows: lvr -pv rpv cvr -pv rpv -serial 233-79 -model ame Use the init_vol for the additional logical volumes as follows: init_vol pub01 dska_03 -special part alt high 141 (Note: 451 disk only) end init_vol pub02 dska_04 -special part alt high 141 (Note: 451 disk only) end After all physical volumes are registered and initialized, add them to the disk_table by typing the add_vol (av) command for all except the RPV: av pvname dskX_NN An example: av pub01 dska_03 At this point add all of the logical volumes by typing: alv -all Instructions - First Time 5-10 SIB12.8 STEP 7: SETTING AND CHECKING ACCESS The ACL for >lv should be set to "s" for all users. Setting initial ACLs for segments in the >lv directory is done from admin mode by typing: M-> ! admin M-> ! sis >lv rew *.SysAdmin rew *.SysDaemon M-> ! sa >lv s * sma *.SysAdmin sma *.SysMaint Create Access Control Segments (ACS) for each logical volume. For system public volumes, create them as follows: M-> ! create >lv>{lvname}.acs M-> ! cvr -lv {lvname} -acs >lv>{lvname}.acs M-> ! set_max_length >lv>*.acs 0 where {lvname} stands for name of each logical volume. For example: ! create >lv>root.acs ! cvr -lv root -acs >lv>root.acs ! set_max_length >lv>*.acs 0 The ACLs of these segments are interpreted to give permission to attach the logical volume (for private volumes) and permission to modify master directory control information in the MDCS (for specific logical volumes). Specific ACL entries for Initializer.SysDaemon should be deleted at this time by typing: delete_acl >lv>*.acs This is necessary because Initializer.SysDaemon always gets default access of "rw". This would prevent the Initializer from being a volume administrator by virtue of the missing "e" access. Deletion of specific access gives the Initializer the "rew" access allowed all SysDaemons. The ACL is now set so that all system administrators and all SysDaemons are volume administrators. The "e" bit controls executive access. For private volumes, the ACS is in a directory controlled by the volume owner. The ACS segment must reside in a directory on a logical volume different from the private logical volume. Instructions - First Time 5-11 SIB12.8 STEP 8: SETTING VOLUME QUOTA Use the set_volume_quota command to give the Initializer process enough quota on each logical volume to create the necessary master directories. set_volume_quota LV_NAME QUOTA Example: set_volume_quota public 36000 The number QUOTA should be at least the total of the quotas of the directories to be created in the next step. Use create_dir to create master directories. The format of the command is: create_dir pathname -lv logical_volume -quota QQ where QQ <262144 Example: cd >library_dir_dir -lv no_backup -quota 40000 cd >library_dir_dir>include -lv public -quota 3000 The acct_start_up.ec will, in step 10, create a number of project directories and assign terminal quota if the directories do not exist. They are the following with the quota that will be assigned: >udd>SysAdmin 5000 >udd>SysAdmin>admin 2000 >udd>SysDaemon 5000 >udd>Daemon 1000 >udd>Operator 100 >udd>Terminals 10 >udd>HFED 5000 Set ACLs and additional names, as desired, on all master directories at this time. Directory quota should be set for each master directory by those sites that wish to have disk charges for directory pages included in monthly bills. Those sites not interested in implementing this feature may type "ame" and "shutdown" then skip to the next step. Instructions - First Time 5-12 SIB12.8 A directory quota of 1000 pages should be sufficient for all master directories with the exception of >udd. If udd is a master directory it is recommended that it be given a directory quota of 100000 pages. This provides enough directory quota for 100 projects at 1000 pages each. If the site has more than 100 active projects the 100000 figure should be adjusted accordingly. To set directory quota on each master directory execute the following command: set_dir_quota PATHNAME QQ This command allows a system administrator to place an arbitrary secondary storage quota for directories on a specified directory. PATHNAME is the name of a directory on which the directory quota is to be placed. -wd can be used to specify the working directory. QQ is the directory quota in 1024 word pages. If additional directory quota is required for a master directory the quota can be reset following movement of directory quota to inferior directories. Instructions for moving directory quota down to the project level is included in Step 19. To shut down, do the following: ame shut STEP 9: RELOAD OF REMAINING RELEASE TAPES Reboot Multics to ring 1 and reload the remaining tapes with the following commands: boot alv -all reload -nosetlvid Load each of the following tapes, in this order: 12.8LDD_STANDARD 12.8UNBUNDLED 12.8AML 12.8MISC The tape labeled MR12.8MISC must be the final tape of the MR12.8 supplied set to be reloaded. Instructions - First Time 5-13 SIB12.8 STEP 10: FIX PERMISSIONS ON LIBRARIES After all the release tapes have been reloaded cross into ring 4 by executing the following commands: standard admin [Ignore messages from admin at this time.] STEP 11: RUNNING ACCT_START_UP.EC At this time you are ready to execute part 1 of the acct_start_up.ec. To do this type: ec >tools>acct_start_up cold F.ANSS where F.ANSS is the channel number of the hardwired Initializer terminal. F = FNP number (a-h) A = Adaptor type (h = hsla) N = Adaptor number (0-2 for hsla) SS = Decimal subchannel number of specified adaptor The string "F.ANSS" should be replaced by "otw_" if there is no hardwired terminal and the bootload console is to be used as the Initializer terminal. The error: new_iod_tables_compiler: Entry not found. Accessing cdt. Channel name checks will not be performed may be encountered during this stage. This error should be disregarded. At this point, tapes dumped from other Multics sites can be reloaded as desired using the "reload" command with the control arguments "-noquota -notrim -nosetlvid" to avoid deletion of existing segments and resetting of quotas. If any segments are to be loaded into ring 1 then it cannot be done without exiting admin mode and rebooting to ring 1. STEP 12: MULTICS COMMUNICATIONS SYSTEM A Multics Communications System (CS) core image is supplied in the >unbundled library, and is named site_mcs. The site_mcs version for this release is 7.6c. The site_mcs core image contains the basic support for DN6780 type FNPs with 64k of memory. Instructions - First Time 5-14 SIB12.8 The communication system core images are built using the bind_fnp command in conjunction with a bindfile describing the CS modules and configurations to be used. A copy of the site_mcs.bind_fnp can be found in >ldd>mcs>info. Sites should build their own CS core image tailored to their own FNP configuration, terminal type requirements, and use of additional separately priced FNP software modules. Sites using the default site_mcs core image should ensure the CMF image statement points to the correct default core image located in >unb. The initial CMF, which includes some sample channel entries in comments, as well as one FNP entry, should be checked. Edit this CMF to eliminate any inconsistencies with the actual configuration and add one or more entries for login channels. Sites modifying their own CS core image are required to use the GCOS Environment Simulator which is an unbundled software product. To build a new core image, the following procedure is suggested: Sites will need to extract the communications object segments from archives located in >ldd>mcs>object. Sites should create a virgin directory under >udd>sa>a for each new core image. The following example is for sites with the more common type Datanet and a larger memory configuration. Execute the following commands: create_dir >udd>sa>a>mcs.7.6c cwd >udd>sa>a>mcs.7.6c ted r >ldd>mcs>info>site_mcs.bind_fnp (or location of sites CS bind file) . . . make editing changes if any... . . . w site_mcs.bind_fnp q ac x ([segs >ldd>mcs>o>*.archive -absp]) bind_fnp site_mcs -list Be sure the image statement in the CMF points to this newly created CS core image. The following example assumes the default CMF to be in the >udd>sa>a directory. This procedure will insure that the new CS image is used: cwd >udd>sa>a ted Instructions - First Time 5-15 SIB12.8 r CMF.cmf . . Locate the image: statement by typing: /image/ Edit the image: statement to point to the CS image, site_mcs, by making the statement read: image: >udd>sa>a>mcs.7.6c>site_mcs; . . Make any other changes needed. . . w CMF.cmf q cv_cmf CMF.cmf copy CMF.cdt >sc1>cdt -force The above procedure builds a site dependent CS core image and ensures that this image is loaded in the FNP by the answering service. The following command provide examples of performing the above steps: create_dir >user_dir_dir>SysAdmin>a>mcs.7.6c cwd >user_dir_dir>SysAdmin>a>mcs.7.6c ted r >ldd>mcs>info>site_mcs.bind_fnp w site_mcs.bind_fnp q ac x ([segs >ldd>mcs>o>*.archive -absp]) bind_fnp site_mcs -list cwd >user_dir_dir>SysAdmin>a ted r CMF.cmf 1,$d a Service: login; Charge: none; Terminal_type: none; Line_type: none; Baud: 9600; FNP_required_up_time: 5; FNP: D; type: DN6670; memory: 64; lsla: 0; hsla: 1; Instructions - First Time 5-16 SIB12.8 image: >system_library_unbundled>site_mcs; service: active; name: d.h000; attributes: hardwired; name: d.h001-d.h031; end; \f 1,$p w ; ted: Do you want to w with the untrusted pathname >user_dir_dir>SysAdmin>a>CMF.cmf? y q cv_cmf CMF.cmf copy CMF.cdt >sc1>cdt -force STEP 13: COMPLETE ACCOUNTING STARTUP During this step, expect many messages, some with audible alarms, reporting that certain segments do not exist and are being created. These messages would be cause for concern during normal system operation but are to be expected during accounting start up and may be ignored. Execute the following example: ame stop_mpx d (sites with multiple FNPs execute this command for each FNP) multics load_mpx d -check (sites with multiple FNPs execute this command for each FNP) admin (any error messages displayed at this time, except hardware error messages can be ignored.) ec >tools>acct_start_up cold2 This procedure will finish accounting start up. The load_mpx command indicates on the FNP console any configuration errors if console_man is loaded and "console: yes;" is in the bind_file. If any errors are reported they should be corrected. During this stage you will encountered the error, "set_max_length: Validation level not in ring bracket. >system_control_1>mcaa.acs", which occurs if an IMU is configured. Ignore this error message. The cause of this error, validation level of >sc1>mcaa.acs, must be fixed manually after cold2 has completed successfully. A default start_up.ec is available for use by new Multics users when they first log in. This exec_com is executed by users who login to the system without their own start_up.ec. The segment >tools>start_up.ec was copied into >sc1 by the acct_start_up.ec. Individual sites can modify this exec_com to meet their own Instructions - First Time 5-17 SIB12.8 needs. The access for the segment should be "r *.*.*" and ring brackets of 4,5,5. To start the system up for normal service type: ame word login abs start go After typing "go" a number of messages will be returned. These messages are of the form: absentee_utility_: Entry not found. Creating new . scavenge_vol: No volumes. Found unexpected command_error in system start_up.ec. These messages may be ignored. STEP 14: CHECK GATE ACLS Type "admin" and enter the new admin password you selected. Check the ACLs for >sss>dm_admin_gate_, >sss>dm_daemon_gate_, >tools>installation_tools_, >tools>pnt_admin_gate_, >tools>pnt_login_gate_, >tools>pnt_network_gate_, >tools>pnt_priv_gate_, >sss>metering_gate_ and >sss>queue_admin_. The ACLs on these gates are as they appear on GHM and should be restricted. The ACL for these gates are site dependent and should be changed to meet each site's needs. The dm_admin_gate_ and dm_daemon_gate_ should be restricted to data management administrators or daemons. The installations_tools_ gate should be restricted to system library maintainers. All persons on the ACL for metering_gate_ have access to the Multics metering data. All persons on the ACL for queue_admin_ are permitted to move absentee and daemon requests for themselves and other users to different queues. Users not on this ACL are only able to move their own requests. The Initializer must have access to queue_admin_. This capability is also dependent on extended access to the .ms segments. The various pnt__gate_ acls should be restricted to the following minimums for correct system operation: >t>pnt_admin_gate_ re *.SysDaemon.* re *.SysAdmin.* >t>pnt_fs_gate_ re *.*.* >t>pnt_login_gate_ re Initializer.SysDaemon.* re *.SysAdmin.* Instructions - First Time 5-18 SIB12.8 >t>pnt_network_gate_ re Initializer.SysDaemon.* re IMFT.Daemon.* re Card_Input.Daemon.* re *.SysDaemon.* >t>pnt_priv_gate_ re Initializer.SysDaemon.* r *.SysDaemon.* re *.SysAdmin.* Set ACLs on the >sc1>rcp directory and on the access control segments in it (.acs), to allow users to attach tape drives and any other peripherals they are allowed to use. After all ACLs are set, type: ame x repair salvquota > 2 -dcf -rebuild Instructions - First Time 5-19 SIB12.8 STEP 15: SET QUOTA ON >DUMPS By default, the >dumps directory does not have any quota set, and thus derives its quota from the root directory. Utility.SysDaemon's start_up.ec, however, includes a monitor_quota command to monitor the quota in, among other directories, >dumps. Without any quota set on this directory, you will see warnings on the console similar to the following: monitor_quota: The requested action was not performed. The quota of >dumps is 0, a record limit needs to be specified. To fix this, move some quota to >dumps. It is recommended that at least 5000 records or quota be provided to >dumps. mq >dumps +5000 STEP 16: SAVE CHECKPOINT Type "logout * *" and "shutdown". STEP 17: TAILOR SYSTEM AND REGISTER PROJECTS Reboot the system for normal service by typing "boot star". The system is now ready for registration of projects and users from a SysAdmin process, such as Repair.SysAdmin, logged in from a standard terminal. The default password for Repair is "repair". You will be required to change it the first time you login, by specifying the "-cpw" control argument to the "login" command. The acct_start_up exec_com created default system_start_up.ec, admin.ec, iod_tables.iodt, RTMF.rtmf, and CMF.cmf segments. These segments should be tailored by the local Site SA to meet site operational and configuration requirements. STEP 18: SETUP VOLUME BACKUP/RELOADER The following instructions are necessary only for those sites that intend to use the Volume Backup/Reloader facility: The personids "Volume_Dumper", "Volume_Reloader", and "Volume_Retriever" are registered. These personids are registered on the Daemon project with the multip and daemon attributes and with a home_dir of >user_dir_dir>Daemon>Volume_Dumper. Sites using AIM must set the authorization for these personids at system_high and upgrade the Instructions - First Time 5-20 SIB12.8 home directory to system_high. Login Repair SysDaemon, or if running in special session using the Initializer, execute the following commands: admin ec >tools>setup_volume_reloader The error message that Volumes dm001 and dm002 are not registered should be ignored. This exec_com creates all directories, segments, and message segments necessary for running the volume dumper/reloader system. This exec_com also sets suggested access on the directories and segments created. Not all the access set is required. If a site wishes, the access created for *.SysMaint.* and *.SysAdmin.* may be removed. This exec_com resets the VTOCE fields for both incremental and consolidated dumps by making a first dump pass with output to discard_. This is necessary since the first dump pass is equivalent to a complete dump on both the incremental and consolidated pass. Follow the instructions for normal use of this facility at the completion of this exec_com. Sites need a sufficient number of tapes to accommodate the entire file system and any incremental and consolidated dumps until a subsequent complete dump is taken. This is known as a reload group. It is suggested that new sites start with 100 reels of tape or a sufficient quantity to contain two complete reload groups. A single reel of tape at 6250 bpi holds approximately 26000 Multics records. STEP 19: SETUP DIRECTORY QUOTA This step is necessary only for those sites that wish to charge their user projects for disk storage used by directory pages, or to obtain a more complete disk report containing additional disk usage statistics. If directory quota is not already set on >udd execute the following commands from a SysAdmin process if >udd is not a master directory: sac set_dir_quota > 120000 sac move_dir_quota >udd 100000 If >udd is a master directory, then execute: set_dir_quota >udd 100000 Then execute the commands: cwd >udd move_dir_quota ([dirs **]) 1000 Instructions - First Time 5-21 SIB12.8 These commands move or set sufficient directory quota on >udd for 100 projects with the suggested default project directory quota of 1000. If a site has more than 100 active projects a figure in excess of 100000 must be chosen for the initial directory quota of >udd. The master.ec gives each new project a default directory quota of 1000 pages by moving 1000 pages of directory quota from >udd. The system administrator should make sure there is always sufficient directory quota on >udd to accommodate new projects. It is also suggested that all directories directly off the root with the exception of pdd and sl1 be given nonzero segment and directory quotas large enough to accommodate their current page usage and allowing for some growth. The purpose of this is to cause the disk report to contain complete statistical information on these directories (directories with 0 quotas are omitted from the disk report). STEP 20: SYSTEM CLEANUP The reload_system_release command creates large map segments in the >reload_dir directory. These are not required for normal system operation. You may delete them in order to conserve disk space. Anyone on the SysAdmin project can delete the map files, which have names like !BBBKQBlDQKxQzh.reload.map. Alternatively, in admin mode on the operator console, you may delete these map files with a command such as "dl >reload_dir>**.reload.map". Module Changes since MR12.7 5-22 SIB12.8 APPENDIX A MODULE CHANGES SINCE MR12.7 This appendix provides information about changes to the Multics operating system on a segment basis. The following information applies to changes made to the system since MR12.7. This appendix is provided to help sites identify, to a segment level, changes they may have applied for emergency bug fixes or site dependent modifications to current system software. Information is catagorized as follows: new info segments modified info segments deleted info segments new segments modified segments deleted segments new include files modified include files Module Changes since MR12.7 A-1 SIB12.8 NEW INFO SEGMENTS SINCE MR12.7 >doc>info>an52.errata.info >doc>info>an61.errata.info >doc>info>ar97.errata.info >doc>info>cv_binary_.info >doc>info>cv_condition_.info >doc>info>cv_fixed_point_string_.info >doc>info>radix_indicator_string_.info >doc>info_segments>call.info >doc>privileged>decimal_no_round_.info >doc>privileged>fim_meters.info >doc>privileged>patch_ring_zero.info >doc>subsystem>analyze_multics>core_map_entry.info >doc>subsystem>analyze_multics>page_control_check.gi.info >doc>subsystem>analyze_multics>page_control_check.info >doc>subsystem>analyze_multics>slt_entry.info Module Changes since MR12.7 A-2 SIB12.8 MODIFIED INFO SEGMENTS SINCE MR12.7 >doc>info>al39.errata.info >doc>info>arithmetic_af.info >doc>info>binary.info >doc>info>calc.info >doc>info>eis_tester.info >doc>info>fs_util_.info >doc>info>gb64.errata.info >doc>info>hcs_.info >doc>info>help.info >doc>info>history_comment.info >doc>info>index_set.info >doc>info>info_seg.gi.info >doc>info>list_ref_names.info >doc>info>numeric_to_ascii_.info >doc>info>plus.info >doc>privileged>analyze_multics.info >doc>privileged>copy_deadproc.info >doc>privileged>deckfile_manager.info >doc>privileged>map355.info >doc>privileged>mbuild.info >doc>privileged>test_cpu.info >doc>subsystem>analyze_multics>aste.info >doc>subsystem>analyze_multics>display.info >doc>subsystem>analyze_multics>display_absolute.info >doc>subsystem>analyze_multics>list_processes.info >doc>subsystem>analyze_multics>sdw.info Module Changes since MR12.7 A-3 SIB12.8 DELETED INFO SEGMENTS SINCE MR12.7 >doc>info>ceil.info >doc>info>cv_dec_.info >doc>info>cv_dec_check_.info >doc>info>cv_hex_.info >doc>info>cv_hex_check_.info >doc>info>cv_integer_string_.info >doc>info>cv_integer_string_check_.info >doc>info>cv_oct_.info >doc>info>cv_oct_check_.info >doc>info>decimal.info >doc>info>divide.info >doc>info>floor.info >doc>info>hexadecimal.info >doc>info>max.info >doc>info>min.info >doc>info>minus.info >doc>info>mod.info >doc>info>numeric_to_ascii_base_.info >doc>info>octal.info >doc>info>quotient.info >doc>info>times.info >doc>info>trunc.info >doc>privileged>copy_liveproc.info >doc>privileged>meter_fim.info Module Changes since MR12.7 A-4 SIB12.8 NEW SEGMENTS SINCE MR12.7 >doc>info>an52.errata.info >doc>info>an61.errata.info >doc>info>ar97.errata.info >doc>info>cv_binary_.info >doc>info>cv_condition_.info >doc>info>cv_fixed_point_string_.info >doc>info>radix_indicator_string_.info >doc>info_segments>call.info >doc>privileged>decimal_no_round_.info >doc>privileged>fim_meters.info >doc>privileged>patch_ring_zero.info >doc>subsystem>analyze_multics>core_map_entry.info >doc>subsystem>analyze_multics>page_control_check.gi.info >doc>subsystem>analyze_multics>page_control_check.info >doc>subsystem>analyze_multics>slt_entry.info >ldd>incl>call_dtype_fcns.incl.pl1 >ldd>incl>call_entry_info_.incl.pl1 >ldd>incl>pl1_symbol_type_fcns.incl.pl1 >ldd>include>azm_sst_util_ptws.incl.pl1 >ldd>include>cv_fixed_point_string_.incl.pl1 >ldd>include>mbuild_script_info_attr.incl.pl1 >ldd>sss>object>bound_help_.archive >ldd>sss>source>bound_help_.s.archive >ldd>tools>object>daily_bk_log.ssl >ldd>tools>object>daily_vinc_log.ssl >sss>bound_full_cp_ >sss>bound_help_ >system_library_3rd_party>games>adventure>execution>ADVNTCAV.DAT >system_library_3rd_party>games>adventure>execution>adventure >system_library_3rd_party>games>adventure>object>adventure >system_library_3rd_party>games>adventure>source>ADVNTCAV.DAT >system_library_3rd_party>games>adventure>source>adventure.pl1 >system_library_3rd_party>games>backgammon>execution>backgammon >system_library_3rd_party>games>backgammon>object>backgammon.cob >system_library_3rd_party>games>backgammon>source>backgammon.c >system_library_3rd_party>games>backgammon>source>makefile >system_library_3rd_party>games>craps>execution>craps >system_library_3rd_party>games>craps>object>craps.cob >system_library_3rd_party>games>craps>source>craps.c >system_library_3rd_party>games>craps>source>makefile >system_library_3rd_party>games>dungeon>execution>DINDX.DAT >system_library_3rd_party>games>dungeon>execution>DTEXT.DAT >system_library_3rd_party>games>dungeon>execution>bound_dungeon >system_library_3rd_party>games>dungeon>object>bound_dungeon.1.archive >system_library_3rd_party>games>dungeon>object>bound_dungeon.2.archive >system_library_3rd_party>games>dungeon>source>bound_dungeon.1.s.archive >system_library_3rd_party>games>dungeon>source>bound_dungeon.2.s.archive >system_library_3rd_party>games>dungeon>source>dparam.incl.fortran >system_library_3rd_party>games>dungeon>source>makefile >system_library_3rd_party>games>dungeon>source>readme Module Changes since MR12.7 A-5 SIB12.8 >system_library_3rd_party>games>executable>>blkjak >system_library_3rd_party>games>executable>>wassay >system_library_3rd_party>games>maze>execution>maze >system_library_3rd_party>games>maze>object>maze.cob >system_library_3rd_party>games>maze>source>makefile >system_library_3rd_party>games>maze>source>maze.c >system_library_3rd_party>games>source>blkjak.basi >system_library_3rd_party>games>source>whassay.pl1 >system_library_3rd_party>games>wizard>execution>wizard >system_library_3rd_party>games>wizard>object>classes.cob >system_library_3rd_party>games>wizard>object>combat.cob >system_library_3rd_party>games>wizard>object>defines.cob >system_library_3rd_party>games>wizard>object>fancy.cob >system_library_3rd_party>games>wizard>object>functions.cob >system_library_3rd_party>games>wizard>object>getch.cob >system_library_3rd_party>games>wizard>object>intro.cob >system_library_3rd_party>games>wizard>object>main.cob >system_library_3rd_party>games>wizard>source>classes.c >system_library_3rd_party>games>wizard>source>combat.c >system_library_3rd_party>games>wizard>source>defines.c >system_library_3rd_party>games>wizard>source>fancy.c >system_library_3rd_party>games>wizard>source>functions.c >system_library_3rd_party>games>wizard>source>getch.c >system_library_3rd_party>games>wizard>source>intro.c >system_library_3rd_party>games>wizard>source>main.c >system_library_3rd_party>games>wizard>source>makefile >tools>daily_bk_log.ssl >tools>daily_vinc_log.ssl Module Changes since MR12.7 A-6 SIB12.8 MODIFIED SEGMENTS SINCE MR12.7 >doc>info>al39.errata.info >doc>info>arithmetic_af.info >doc>info>binary.info >doc>info>calc.info >doc>info>eis_tester.info >doc>info>fs_util_.info >doc>info>gb64.errata.info >doc>info>hcs_.info >doc>info>help.info >doc>info>history_comment.info >doc>info>index_set.info >doc>info>info_seg.gi.info >doc>info>list_ref_names.info >doc>info>numeric_to_ascii_.info >doc>info>plus.info >doc>privileged>analyze_multics.info >doc>privileged>copy_deadproc.info >doc>privileged>deckfile_manager.info >doc>privileged>map355.info >doc>privileged>mbuild.info >doc>privileged>test_cpu.info >doc>subsystem>analyze_multics>aste.info >doc>subsystem>analyze_multics>display.info >doc>subsystem>analyze_multics>display_absolute.info >doc>subsystem>analyze_multics>list_processes.info >doc>subsystem>analyze_multics>sdw.info >ldd>hard>execution>bootload_tape_label >ldd>hard>execution>bound_355_wired >ldd>hard>execution>bound_bce_wired >ldd>hard>execution>bound_bootload_0 >ldd>hard>execution>bound_error_handlers_ >ldd>hard>execution>bound_hc_reconfig >ldd>hard>execution>bound_init_1 >ldd>hard>execution>bound_interceptors >ldd>hard>execution>bound_library_1_ >ldd>hard>execution>bound_library_wired_ >ldd>hard>execution>bound_multics_bce_ >ldd>hard>execution>bound_temp_1 >ldd>hard>execution>bound_wired_1 >ldd>hard>info>hardcore.header >ldd>hard>object>bootload_tape_label >ldd>hard>object>bound_355_wired.archive >ldd>hard>object>bound_bce_wired.archive >ldd>hard>object>bound_bootload_0.archive >ldd>hard>object>bound_error_handlers_.archive >ldd>hard>object>bound_hc_reconfig.archive >ldd>hard>object>bound_init_1.archive >ldd>hard>object>bound_interceptors.archive >ldd>hard>object>bound_library_1_.archive >ldd>hard>object>bound_library_wired_.archive Module Changes since MR12.7 A-7 SIB12.8 >ldd>hard>object>bound_multics_bce_.archive >ldd>hard>object>bound_temp_1.archive >ldd>hard>object>bound_wired_1.archive >ldd>hard>source>bootload_tape_label.alm >ldd>hard>source>bound_355_wired.s.archive >ldd>hard>source>bound_bce_wired.s.archive >ldd>hard>source>bound_bootload_0.s.archive >ldd>hard>source>bound_error_handlers_.s.archive >ldd>hard>source>bound_hc_reconfig.s.archive >ldd>hard>source>bound_init_1.s.archive >ldd>hard>source>bound_interceptors.s.archive >ldd>hard>source>bound_library_1_.s.archive >ldd>hard>source>bound_library_wired_.s.archive >ldd>hard>source>bound_multics_bce_.s.archive >ldd>hard>source>bound_temp_1.s.archive >ldd>hard>source>bound_wired_1.s.archive >ldd>include>amu_hardcore_info.incl.pl1 >ldd>include>azm_info.incl.pl1 >ldd>include>io_page_tables.incl.pl1 >ldd>include>mbuild_data_.incl.pl1 >ldd>include>mbuild_request_parms_.incl.pl1 >ldd>include>oc_data.incl.pl1 >ldd>include>pnotice_language_info_.incl.pl1 >ldd>include>rcerr.incl.pl1 >ldd>include>slte.incl.pl1 >ldd>include>unpaged_page_tables.incl.pl1 >ldd>sss>o>pl1.dcl >ldd>sss>object>bound_access_commands_.archive >ldd>sss>object>bound_binder_.archive >ldd>sss>object>bound_full_cp_.archive >ldd>sss>object>bound_info_rtns_.archive >ldd>sss>object>bound_install_table_.archive >ldd>sss>object>bound_proj_admin_.archive >ldd>sss>source>bound_access_commands_.s.archive >ldd>sss>source>bound_binder_.s.archive >ldd>sss>source>bound_full_cp_.s.archive >ldd>sss>source>bound_info_rtns_.s.archive >ldd>sss>source>bound_install_table_.s.archive >ldd>sss>source>bound_proj_admin_.s.archive >ldd>tools>object>acct_start_up.ec >ldd>tools>object>admin.ec >ldd>tools>object>bound_admin_tools_.archive >ldd>tools>object>bound_amu_.archive >ldd>tools>object>bound_as_install_ctl_.archive >ldd>tools>object>bound_as_misc_.archive >ldd>tools>object>bound_azm_.archive >ldd>tools>object>bound_checker_.archive >ldd>tools>object>bound_gm_.archive >ldd>tools>object>bound_mbuild_.archive >ldd>tools>object>bound_meter_util_.archive >ldd>tools>object>bound_pnotice_.archive >ldd>tools>object>bound_structure_lib_.archive >ldd>tools>object>bound_system_test_.archive Module Changes since MR12.7 A-8 SIB12.8 >ldd>tools>object>bound_tolts_.archive >ldd>tools>object>et_scripts >ldd>tools>object>master.ec >ldd>tools>object>mca_priv_ >ldd>tools>object>multics_libraries_ >ldd>tools>object>system_start_up.ec >ldd>tools>source>bound_admin_tools_.s.archive >ldd>tools>source>bound_amu_.s.archive >ldd>tools>source>bound_as_install_ctl_.s.archive >ldd>tools>source>bound_as_misc_.s.archive >ldd>tools>source>bound_azm_.s.archive >ldd>tools>source>bound_checker_.s.archive >ldd>tools>source>bound_gm_.s.archive >ldd>tools>source>bound_mbuild_.s.archive >ldd>tools>source>bound_meter_util_.s.archive >ldd>tools>source>bound_pnotice_.s.archive >ldd>tools>source>bound_system_test_.s.archive >ldd>tools>source>bound_tolts_.s.archive >ldd>tools>source>mca_priv_.alm >ldd>tools>source>multics_libraries_.ld >ldd>unb>o>bound_emacs_full_.archive >ldd>unb>object>bound_gcos_.1.archive >ldd>unb>s>bound_emacs_full_.s.archive >ldd>unb>source>bound_gcos_.1.s.archive >sl3p>cc>incl>time.h >sss>bound_access_commands_ >sss>bound_binder_ >sss>bound_full_cp_ >sss>bound_info_rtns_ >sss>bound_install_table_ >sss>bound_proj_admin_ >sss>pl1.dcl >tools>acct_start_up.ec >tools>admin.ec >tools>bound_admin_tools_ >tools>bound_amu_ >tools>bound_as_install_ctl_ >tools>bound_as_misc_ >tools>bound_azm_ >tools>bound_checker_ >tools>bound_gm_ >tools>bound_mbuild_ >tools>bound_meter_util_ >tools>bound_pnotice_ >tools>bound_structure_lib_ >tools>bound_system_test_ >tools>bound_tolts_ >tools>et_scripts >tools>master.ec >tools>mca_priv_ >tools>multics_libraries_ >tools>system_start_up.ec >unb>bound_emacs_full_ Module Changes since MR12.7 A-9 SIB12.8 >unb>bound_gcos_ >unb>emacs.12.9.sv.lisp >unb>emacs_.12.9.sv.lisp Module Changes since MR12.7 A-10 SIB12.8 DELETED SEGMENTS SINCE MR12.7 >doc>info>ceil.info >doc>info>cv_dec_.info >doc>info>cv_dec_check_.info >doc>info>cv_hex_.info >doc>info>cv_hex_check_.info >doc>info>cv_integer_string_.info >doc>info>cv_integer_string_check_.info >doc>info>cv_oct_.info >doc>info>cv_oct_check_.info >doc>info>decimal.info >doc>info>divide.info >doc>info>floor.info >doc>info>hexadecimal.info >doc>info>max.info >doc>info>mbx_delete_acl.info >doc>info>mbx_list_acl.info >doc>info>mbx_set_acl.info >doc>info>min.info >doc>info>minus.info >doc>info>mod.info >doc>info>ms_delete_acl.info >doc>info>ms_list_acl.info >doc>info>ms_set_acl.info >doc>info>numeric_to_ascii_base_.info >doc>info>octal.info >doc>info>quotient.info >doc>info>times.info >doc>info>trunc.info >doc>privileged>copy_liveproc.info >doc>privileged>meter_fim.info >ldd>sss>object>bound_calc_.archive >ldd>sss>source>bound_calc_.s.archive >sss>bound_calc_ Module Changes since MR12.7 A-11 SIB12.8 NEW INCLUDE FILES SINCE MR12.7 >ldd>incl>call_dtype_fcns.incl.pl1 >ldd>incl>call_entry_info_.incl.pl1 >ldd>incl>pl1_symbol_type_fcns.incl.pl1 >ldd>include>azm_sst_util_ptws.incl.pl1 >ldd>include>cv_fixed_point_string_.incl.pl1 >ldd>include>mbuild_script_info_attr.incl.pl1 Module Changes since MR12.7 A-12 SIB12.8 MODIFIED INCLUDE FILES SINCE MR12.7 >ldd>include>amu_hardcore_info.incl.pl1 >ldd>include>azm_info.incl.pl1 >ldd>include>io_page_tables.incl.pl1 >ldd>include>mbuild_data_.incl.pl1 >ldd>include>mbuild_request_parms_.incl.pl1 >ldd>include>oc_data.incl.pl1 >ldd>include>pnotice_language_info_.incl.pl1 >ldd>include>rcerr.incl.pl1 >ldd>include>slte.incl.pl1 >ldd>include>unpaged_page_tables.incl.pl1 Module Changes since MR12.7 A-13 SIB12.8