|
|
1.1 root 1: This is a simple extensible shell (scsish) for poking at scsi
2: devices, particularly the simpler kinds commonly called toasters.
3: it is supposed to be self-documenting in use; try the help command.
4: my use of the moran-dronek /dev/scsi library is still imperfect;
5: there is still some some debugging showing.
6:
7: To compile, you first need mk. you then have to pick a system type
8: to set some flags; currently we support research and sgi.
9: yours may differ, particularly as no one else has our ansi C compiler for the sgi.
10: the only problem i would expect is the normal header file crap you get
11: mixing ansi and non-ansi files. i recommend setting NPROC=1 while debugging hdr files.
12: if you change (header) files, try putting them in the directory inc
13: (then others may benefit). To support a new system (say sgi-gcc), just create
14: a new file sgi-gcc.mk and so on. you may be missing some devices in
15: your /dev/scsi; the script scsi/gendev may help (but check the major/minor
16: numbers and permissions).
17:
18: As for modifying/extending scsish, it has been designed to be not too hard.
19: Adding a new device means adding a new set of rules (like the other rules)
20: to mkfile and creating a new directory (say exabyte) and at least two files in it
21: (dev.c and fns.h). The wren directory is a small example you can clone.
22: Adding new functions to any device means updating a file list in mkfile,
23: updating dev.c and fns.h in the device directory. The argument syntax
24: scheme is arguably pokey, but liveable. at some future point we should probably
25: switch over to osterhout's tcl.
26:
27: as always, i invite you send extensions/fixes etc back to
28: [email protected]
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.