[Info-vax] Tertiary VMB?

[JF Mezei]

gerry77 at no.spam.mail.com wrote:

> I think it was a bit later, around the 4.7/5.0 timeframe. Actually, the
> Internals and Data Structures manual for V4.4 doesn't have any mention of
> LAVc, while the one for V5.2 does.


Something I don't understand:

MOP requests are in the firmware. They don't specify which file to feed.
It just says "feed me !" "feed me" until someone feeds that node.

Either NCP or LANCP have a database of nodes' ethernet addresses, and
which file to send. For LAVC, it is NICS_LOAD.EXE .

What is not obvious is that the MOP server (LANACP for instance) will
append stuff to that file, notably the applicable VAXVMSSYS.PAR file.

Also, it will send the cluster_authorize.dat (or at least, that file is
mentioned in the executable)


If you look at LANACP.EXE, you will see a reference to
[SYSEXE]VAXVMSSYS.PAR, SYS$COMMON:[SYSEXE]CLUSTER_AUTHORIZE.DAT, and
there is a string "Tertiary loader", but no TERTIARY_VMB.EXE

Note that so far, none of the files mentioned above have any mention of
the tertiary_vmb.exe file.


Does the MOP protocole have the ability to have the loading node request
specific files (such as drivers), or is it assumed that once the initial
package has been sent, the booting node will have enough brains to start
accessing its disk via MSCP and load its own drivers and files ?