What we're going to do here is prepare three Jtrix applications and then run them on our own node. The preparation is creating netlet descriptors which are digitally signed with our own unique key pairs.
Here are the commands to start this from scratch, with the system's
responses. First we set things up. See Section
for an explanation of this:
% hospitality_init hos01 generating hospitality for hos01... generating key pair for hos01... % ls hos01* hos01-boot.xml hos01.prv hos01.pub % telnet_init 2000 configuring telnet on 2000... % ls telnet-* telnet-2000.xml % sas2_init sas01 generating key pair for sas01... creating sas01 launch descriptor... configuring sas01... % ls sas01* sas01-boot.xml sas01.prv sas01.pub sas01.xml %
Note that Hospitality is the name of Jtrix.org's implementation of a hosting service. So hospitality_init initialises the hosting service.
Now we can run the first node with a hosting service. Section
has an explanation of this:
% jnode 100 -netlet-stdio hos01-boot.xml hosting-out=hos01-admin.xml \
telnet-2000.xml hosting-in=hos01-admin.xml \
sas01-boot.xml hosting-in=hos01-admin.xml \
hosting-out=hos01-real-admin.xml sas-out=sas01-warrant.xml \
sas-desc=sas01-real-desc.xml
Jnode starting...
Initialising Nodality...
Bootstrap starting
starting hos01-boot
netlet:100.0.1: This node: 0a77088b0204000001000000
-------------------------------------------------------
GMS: address is victoria:1342
-------------------------------------------------------
netlet:100.0.1: master changed;false:false
netlet:100.0.1: master changed;true:true
netlet:100.0.1: connecting to master: 0a77088b0204000001000000
no mapping for sas-in: SAS Warrant
writing hos01-admin.xml for hosting-out: Admin Warrant
deleting /var/tmp/jtrix/disk-100/dsk-6613601-0
starting telnet-2000
reading hos01-admin.xml for hosting-in: Telnet Hosting Warrant
starting sas01-boot
reading hos01-admin.xml for hosting-in: hosting admin warrant
writing sas01-real-desc.xml for sas-desc: sas descriptor
writing sas01-warrant.xml for sas-out: real SAS warrant
netlet:100.0.1: connecting to SAS
writing hos01-real-admin.xml for hosting-out: real hosting warrant
Bootstrap complete
At the end the prompt does not return, since the node is running. Notice the lines that begin netlet:XXX.0.1. That XXX is the node ID we chose on the command line. We should make a note of it for later.
Also, make sure you leave the node running in its own window; don't ``background'' it. It will continue to produce all kinds of output, and you don't want that to interfere with any other things we're going to.
Starting the node with these applications also produced some more files. Here is everything we have so far:
% ls hos01* telnet-* sas01* hos01-admin.xml hos01.prv sas01-real-desc.xml sas01.pub hos01-boot.xml hos01.pub sas01-warrant.xml sas01.xml hos01-real-admin.xml sas01-boot.xml sas01.prv telnet-2000.xml %
Nik Silver 2002-03-09