If we haven't already created suitable descriptors, we need to do this now:
% 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 %
In this example we need an HTTP server (port 80) and a DNS server (port 53). Such access to privileged ports is not granted to just anyone. We need the following:
# jnode 104 -webres 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
-------------------------------------------------------
GMS: address is victoria:1455
-------------------------------------------------------
no mapping for sas-in: SAS Warrant
writing hos01-admin.xml for hosting-out: Admin Warrant
deleting /var/tmp/jtrix/disk-104/dsk-6875745-0
deleting /var/tmp/jtrix/disk-104/dsk-6875745-3
deleting /var/tmp/jtrix/disk-104/dsk-6875745-5
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
writing hos01-real-admin.xml for hosting-out: real hosting warrant
Bootstrap complete
All that's different is the extra argument -webres which requests
the relevant resources. This really does nothing more than request
two port blocks with the -netblock option of jnode.jar.
See Appendix
for the appropriate help file.
Nik Silver 2002-03-09