161 lines
12 KiB
Plaintext
161 lines
12 KiB
Plaintext
|
||
Hello 11.0
|
||
|
||
program: [eris]<lisp>Harmony>mesa>HelloDlion.boot
|
||
documentation: [eris]<lisp>Harmony>Doc>Hello.tedit
|
||
|
||
Hello 11.0 is a modified version of the Othello 11.0 utility, which is used for managing Pilot disk volumes. It offers most of the Othello commands (documented in the Mesa Users Guide), and adds a few commands which are useful when using Interlisp-D on a Dlion.
|
||
|
||
Hello is a .boot file, which can be loaded onto a Dlion disk using the Fetch Boot File command of Othello. It can also be booted off of a floppy disk.
|
||
|
||
|
||
Loading Interlisp From a File Server to a Logical Volume:
|
||
|
||
When Hello starts up, it prints out some information about the machine it is running on, including the Dlion's host number and memory size, and then prints the prompt ">", to indicate it is ready to recieve a command. The "Online" command, which is automatically printed, tells Hello to bring the physical disk on-line. (Note: all user input is underlined, including confirming carriage-returns)
|
||
|
||
Hello 11.0 of 6-Sep-84 10:14:03
|
||
Processor = ...
|
||
Memory Size=1536 bytes
|
||
>Online
|
||
Drive Name: RD0
|
||
|
||
Before fetching a lisp sysout from a file server, it is necessary to open a connection to a file server, and login. Note: Hello currently cannot communicate with NS file servers (ones with colons in their names, such as "Phylex:").
|
||
|
||
>Open
|
||
Open Connection to ERIS
|
||
>Login
|
||
User: Sannella
|
||
Password: *****
|
||
|
||
In order for a lisp sysout to run, it needs to have a special "initial microcode" file installed. This microcode only needs to be installed once for each Dlion.
|
||
|
||
>Initial Microcode Fetch
|
||
Drive Name: RD0
|
||
File Name: [eris]<lisp>Harmony>Basics>Lisp11SAx000Initial.db
|
||
Formatting...Fetching...Installing...done
|
||
|
||
Now, fetch the Interlisp sysout file [eris]<lispcore>next>Full.sysout and store it on the logical volume named "Lisp". Depending on the size of the sysout file, and the load on the ethernet, this can take 5-10 minutes.
|
||
|
||
>Lisp Sysout Fetch
|
||
Logical volume name: Lisp
|
||
Lisp sysout file name: [eris]<lisp>Harmony>Basics>Full.sysout
|
||
Fetching....
|
||
|
||
Before running a lisp sysout, it is necessary to "expand" the file containing the sysout to the full size of the logical volume. This will allow Interlisp virtual memory to grow as Interlisp needs more space. If this is NOT done, there can be problems with Interlisp on large-memory Dlions. Eventually, the low-level Interlisp virtual memory management system will be improved, so this will not be necessary.
|
||
|
||
>Expand Vmem file
|
||
volume to expand: Lisp
|
||
|
||
Finally, the Interlisp image on volume "Lisp" can be started with the boot command.
|
||
|
||
>Boot
|
||
Logical volume name: Lisp
|
||
Boot Lisp from this volume? YES
|
||
|
||
|
||
Copying Interlisp From One Logical Volume to Another:
|
||
|
||
A very useful facility that Hello offers is the capability of copying an Interlisp sysout from one logical volume to another. This is much faster than retrieving a sysout over the ethernet. Many people like to keep a "virgin" sysout on their Dlion, and reload from that. Here is how it is done: Load a sysout onto a volume named "BootLisp", as specified above. This sysout will be the "virgin" sysout used to re-initialize other Interlisp volumes. This volume should not be expanded with the "Expand Vmem file" command, and should never be booted.
|
||
|
||
>Open
|
||
Open Connection to ERIS
|
||
>Login
|
||
User: Sannella
|
||
Password: *****
|
||
>Initial Microcode Fetch
|
||
Drive Name: RD0
|
||
File Name: [eris]<lisp>Harmony>Basics>Lisp11SAx000Initial.db
|
||
Formatting...Fetching...Installing...done
|
||
>Lisp Sysout Fetch
|
||
Logical volume name: BootLisp
|
||
Lisp sysout file name: [eris]<lisp>Harmony>Basics>Full.sysout
|
||
Fetching....
|
||
|
||
To re-initialize the Interlisp volume "Lisp", copy the sysout file from the volume "BootLisp". This takes about a minute.
|
||
|
||
>Copy Lisp from Another Volume
|
||
Volume to copy from: BootLisp
|
||
Volume to copy to: Lisp
|
||
|
||
Now, expand and boot the "Lisp" volume as if the sysout had been loaded from a file server.
|
||
|
||
>Expand Vmem file
|
||
volume to expand: Lisp
|
||
>Boot
|
||
Logical volume name: Lisp
|
||
Boot Lisp from this volume? YES
|
||
|
||
|
||
Determining What is on Your Disk:
|
||
|
||
It is easy to forget exactly what sysouts are on what volumes of the DLion disk, or which Interlisp sysouts have been "expanded", etc. The "Describe" command prints out useful information about every volume on the disk.
|
||
|
||
>Describe
|
||
.
|
||
.
|
||
Volume Lisp (type=normal) 700 of 16200 pages free
|
||
starting at physical address 4129
|
||
Lisp sysout: [eris]<lispcore>next>Full.sysout (3-Aug-84 10:35:17)
|
||
.
|
||
.
|
||
|
||
In this example, we can tell what lisp sysout, with which creation date, is stored on the volume "Lisp". The fact that 700 of 16200 pages are free strongly indicates that the sysout has been expanded (expansion doesn't use ALL of the space). |