A boot file is essentially a "virtual execution environment": it consists of a memory image containing a number of BCDs that have been loaded but not started. The simple view of MakeBoot is that it takes a collection of specified BCDs, constructs a memory image, and writes it out as a boot file. In practice, however, MakeBoot requires more information than just the names of the BCDs to be included in the memory image; this information is contained in a text file (or files) called the command input. The command input includes a number of parameters that affect the way the boot file is constructed.

The memory image built by MakeBoot is loaded into memory by a simple loader called the germ, which then transfers control to the main body of a module named in the command input. Naturally, there is a certain amount of delicate initialization required to transform the loaded memory image into a running Pilot environment. The details of this initialization include configuration of memory, which, of course, includes dealing with the contents of the initial memory image (boot file) that the germ has loaded. For example, certain portions of the code in the boot file need to be initially resident in main memory, since they will be needed before Pilot's machinery for swapping from disk has been set up. The germ and the Pilot initialization code have to cooperate with MakeBoot to insure that memory residency, and other properties, are preserved during the delicate initialization phase. To do this, they share information contained in the boot file, information which is constructed from the BCDs that make up the memory image and the command input. MakeBoot relies almost entirely on its input for this information; very little is implicitly assumed.

The descriptions below assume certain knowledge of the structure of BCDs, which we summarize here. A .bcd file, which is the output of the compiler, binder, or packager, consists of three related parts: a descriptive portion called the "binary configuration description" (BCD), a (possibly empty) collection of code segments, and a (possibly empty) collection of symbol segments. The descriptive portion includes tables that describe a hierarchy of configurations and the modules they contain, the interfaces imported and exported by the root configuration of the hierarchy, and the packaging of the code and global frames that comprise the modules in the hierarchy. The BCD also describes the location of the code segments and their associated symbols, each of which may be either in the same file with the descriptive portion or in a different one. (There are other, subsidiary tables in the BCD that are not used by MakeBoot.)

This section describes the syntax and semantics of the command input. Many of the possible specifications should be used only upon the advice and counsel of a wizard, since they may cause extremely strange behavior in the initialization or subsequent execution of the boot file. Items of command input that fall in this category have their semantic descriptions preceded by (*).

MakeBoot treats its command input as a linear text stream, which may include white space and comments in the same form and places as Mesa source code. In the syntax equations that follow, white space is not significant and a "|" character denotes metalinguistic alternatives. Words in italics are metalinguistic variables (non-terminals), all other characters appear literally in the command input. (No definitions appear for identifier or non-terminals beginning with decimalNumber; these are presumed to be implicitly understood. Note that, as with all Mesa-related descriptions, the case of alphabetic characters within identifiers is significant.)

gftItem ::= GFT : decimalNumberIn[1..1024] ;

mdsBaseItem ::= MDSBASE : pageNumber ;

codeBaseItem ::= CODEBASE : pageNumber ;

pdaBaseItem ::= PDABASE : pageNumber ;

pdaPagesItem ::= PDAPAGES : decimalNumberIn[1..256] ;

framePagesItem ::= FRAMEPAGES : decimalNumberIn[0..256) ;

frameWeightItem ::= frameSpec : fsi , decimalNumber fsiChain ;

nProcessesItem ::= PROCESSES : decimalNumberIn[1..1024] ;

svItem ::= STATEVECTORCOUNT : priority, decimalNumber ;

svSizeItem ::= STATEVECTORSIZE : decimalNumber ;

wartItem ::= WART : wartModule ;

residentItem ::= RESIDENT : generalList ;
resDescItem ::= RESIDENTDESCRIPTOR : generalList ;
initiallyInItem ::= IN : generalList ;

noTrapItem ::= NOTRAP : moduleList ;

MakeBoot is invoked from the executive by loading MakeBoot.bcd and supplying a command line. The syntax of the command line resembles that of the compiler and binder:

[bootFile: f1, loadMap: f2] ← input[key1: value1, ..., keyn: valuen]/switches

The only mandatory part of the command line is input, which names a BCD (default extension .bcd). The bootFile specification supplies the file name for the boot file (default extension .boot or .germ, as appropriate); the loadMap specification supplies the file name for the load map file (default extension, .loadmap). Defaulting occurs in the usual way if either or both of these specifications are omitted: f1 is used as the root of names if it is present, otherwise input is used. As is customary, the order of the keyword parameters is irrelevant. The following keywords are recognized within the brackets following input:

MakeBoot recognizes several switches, all of which are intended for wizards only: