Our second node can now be started anywhere on the same LAN. This time it's much simpler, but the steps are slightly different to what we've seen before, including giving this jnode a different node ID:
% telnet_init 2001
configuring telnet on 2001...
% ls telnet-*
telnet-2000.xml telnet-2001.xml
% jnode 101 -netlet-stdio hos01-boot.xml hosting-out=hos01-admin.xml \
telnet-2001.xml hosting-in=hos01-admin.xml
Jnode starting...
Initialising Nodality...
Bootstrap starting
starting hos01-boot
netlet:101.0.1: This node: 0a77088b0704000001000000
-------------------------------------------------------
GMS: address is victoria:1292
-------------------------------------------------------
netlet:101.0.1: master changed;true:false
netlet:101.0.1: connecting to master: 0a77088b0204000001000000
no mapping for sas-in: SAS Warrant
writing hos01-admin.xml for hosting-out: Admin Warrant
starting telnet-2001
reading hos01-admin.xml for hosting-in: Telnet Hosting Warrant
Bootstrap complete
There's only one setup script, but we must reuse the previous descriptor
of Hospitality boot netlet. This is discussed in Section
.
The hosting service spreads out to this second node and SAS follows
it. Also we can telnet to this second node on port 2001.
Nik Silver 2002-03-09