This makes a small change in how the expect script interacts with PEEK
when it's built. Instead of triggering on text written by PEEK, it
waits for the $G that comes from the purify valret. The reason is
that if ITS considers the 340 online and available, PEEK running on
the console will send its output to the 340 rather than the teletype,
so expect has nothing to trigger on.
KA10 specific programs: DECtape tools, programs related to the Rubin
10-11 interface (including the Knight TV), programs using the 340
display, and programs using the PDP-6.
KL10 specific programs: microcode, frontend programs, and LSPEED.
KS10 specific programs: microcode, frontend programs, MTBOOT, and TENTH.
This is the real source for DEVICE; OARCDV BIN, which uses the old
"ARC!!!" archive format. The previously reconstructed ARCDEV 66 can
be removed, and it was also the wrong version.
Since we're interacting with ITS through the system console, one cause
of build failures is the messages the system job prints to the console
at unpredictable times -- for example, periodic timestamps and
notifications of changes to files in system directories. If one of these
gets printed while we're expecting something else, it's hard for the
Expect script to recover.
Avoid this by patching STYO, the system job's character-printing
routine, to return without doing anything if this system is up.
Adjust the pdset routine so it's matching PDSET's output rather than the
system job's to tell when the time has been set.
