H1: Grid Tool Kit

H2: Make ready --- Grid Library
H3: $home/lib/grid
directory $home/lib/grid/NAME
NAME is a handle name of the grid system
this directory contains two files, named
"factotum" and "names"

H3: Example
H4: $home/lib/grid/bell-labs/factotum

key dom=grid.bell-labs.com proto=p9sk1 user=arisawa !password=XXXXXXXX


H4: $home/lib/grid/bell-labs/names

b.grid.bell-labs.com
#c.grid.bell-labs.com
#d.grid.bell-labs.com
#e.grid.bell-labs.com
f.grid.bell-labs.com
g.grid.bell-labs.com
#h.grid.bell-labs.com
#i.grid.bell-labs.com



H2: Installation of taskfs
H3: Files for Grid Tool Kit
bin/386/taskfs
bin/386/alarm
bin/rc
check
run
src/exportfs.c
src/exportfs.h
src/exportsrv.c
src/mkfile
src/task.c
pattern
readme
S/*
Q/*

where alarm is very general tool and the source program
is located in http://plan9.aichi-u.ac.jp/netlib/cmd/

H3: Compilation
	cd src
	mk install

H3: Execution
	check S
for slave testing of ability
and
	run Q
for N queens problem
I believe Q is a good prototype for more generic problems.

H2: Slave Testing
H3: items of testing
- /tmp (clean?)
- /tmp (writable?)
- ramfs (permitted?)
- Python (available?)
- rx (supported?)

the results are placed in S/host

H3: files for slave testing
S/host/
S/mrun
S/prun
S/srun

where prun is purpose specific file for Python test.
the result is written in S/host

H3: Execution
execute at this directory
	check S

H2: Installation of queen
queen is a resolver for N queens problem.

H3: Files for queen
Q/bin/386/queen
Q/bin/rc/
Q/data/*
Q/finish
Q/mktask
Q/mrun
Q/readme
Q/src/*
Q/srun
Q/task
Q/tasks/task.*

and the following files or directory are generated
(and some of them are removed) in progress

Q/done
Q/task.*.*/
Q/task.*.*/done
Q/task.*.*/hostname
Q/task.*.*/result
Q/task.*.*/dup

where Q/task.*.*/result are our main result for each task.

H3: Compilation
	cd Q/src
	mk install

H3: Execution
execute at this directory
	run Q

H3: More Info
look Q/readme
