The default X server loading sequence (listed in Table 4-1) automatically loads the first X server found in the default TFTP directory (usually /tftpboot). The default directory is defined by your implementation of TFTP.
After the request for an X server is answered by a host and is downloaded, no further requests are made. You can disable any of the requests.
Although the sequence uses predefined pathnames, you can use it to boot an X server located in another directory by linking one of the default pathnames to the X server's true location. For information about linking, see "Linking X Server Files".
Table 4-1 Default Server Loading Sequence
To prevent the terminal from booting automatically, set the boot-automatically parameter to "false" (Setup -> Change Setup Parameters -> Booting -> Boot automatically at power up). If automatic booting is disabled, the terminal displays the Boot Monitor prompt instead of loading an X server. This parameter is saved in NVRAM.
Table 4-2 boot-automatically Parameter
Possible Values
Result
default
true
true
The Boot Monitor attempts to download an X server.
false
The Boot Monitor does not attempt to download an X server.
Disabling Broadcast Requests for an X Server
To prevent broadcasting for an X server, set the boot-tcpip-broadcast-boot-request parameter to "false" (Setup -> Change Setup Parameters -> Booting -> TCP/IP Broadcast Boot Request). This parameter is saved in NVRAM.
Table 4-3 boot-tcpip-broadcast-boot-request Parameter
Possible Values
Result
default
true
true
The Boot Monitor attempts to download an X server by broadcasting.
false
The Boot Monitor does not attempt to download an X server by broadcasting.
Disabling the MOP Request for an X Server
To prevent MOP download requests, set the boot-mop parameter to "false" (Setup -> Change Setup Parameters -> Booting [NCDnet Boot Options section] -> Try MOP). This parameter is saved in NVRAM.
Table 4-4 boot-mop Parameter
Possible Values
Result
default
true
true
The Boot Monitor tries to download an X server using the MOP protocol.
false
The Boot Monitor does not try to download an X server using the MOP protocol.
Disabling Selected TFTP or NFS Requests for an X Server
The parameters listed in Table 4-5 control the X server filenames that the Boot Monitor requests via TFTP or NFS during the default X server download sequence.
boot-tcpip-unit-address-with-path-file = false
Table 4-5 Download Sequence Parameters
Specifying a Non-Standard X Server Filename
To specify a non-standard X server filename (not one of the names listed in Table 4-5), use the boot-custom-file parameter (Setup -> Change Setup Parameters -> Booting -> Custom File). This parameter is saved in NVRAM.
Table 4-6 boot-custom-file Parameter
Possible Values
Result
default
nil
filename
A non-standard name for the X server file.
Specifying a Non-Standard X Server Directory
To specify a non-standard X server directory, set the boot-nfs-directory parameter or boot-tftp-directory parameter. For details, see "Using TFTP for X Server Downloading" or "Using NFS for X Server Downloading".
Keeping the Terminal from Entering the Boot Monitor at Boot Time
By default, the Boot Monitor prompt appears when attempts to load an X server are unsuccessful. To configure the terminal to continue attempting to boot until it succeeds, set the boot-persistent-loading parameter to "true" (Setup -> Change Setup Parameters -> Booting -> Persist in Loading). This parameter is saved in NVRAM.
Table 4-7 boot-persistent-loading Parameter
Configuring the Sequence of X Server Loading Methods
When booting over a Token-Ring network, the MOP boot attempt is disabled automatically.
To specify the first method to try, set the value of the boot-desired-source parameter to the desired method (see Table 4-8). (Setup -> Change Setup Parameters -> Booting -> Primary Boot Source or Setup -> Change Quick Setup -> Booting -> Boot From). This parameter is saved in NVRAM.
Table 4-8 boot-desired-source Parameter
The method specified in boot-second-source is used if the method specified in boot-desired-source does not succeed.
Table 4-9 boot-second-source Parameter
The method specified in boot-third-source is used if the method specified in boot-second-source does not succeed.
Table 4-10 boot-third-source Parameter