**** IMPORTANT ****

PI is intended to be a "Public ITS" system; access is unrestricted,
and anyone can do anything.  If you don't know what you're doing,
please be very careful.  There are no protections, and nothing
prevents you from crashing or killing the system altogether.

The future of the system will depend greatly on how the network
community treats it.  If it consumes too much of our time to repair
damage, whether caused by intent or accident, we won't be able to
continue this experiment.

All available documentation is online, although finding it may take
time.  Try these commands to begin with:
	:HELP
	:?
	:INFO
More will be added later, hopefully on an external web site for easier
perusal.  This will include the SUPDUP client program, a much better
way to access ITS than via TELNET.

Various items:

- Don't use INQUIR, despite any instructions to do so.  It will
require some modification to work away from MIT.  In general, the file
system is still fairly rudimentary and some software may not run
because supporting files are missing.

- PI is running on a KLH10 -- an emulated KS10 written in C and being
executed by a P3-450 running FreeBSD.  It is much faster than a real
KS10 unless other FreeBSD processes take cycles away from the emulator.

- One program that is usually interesting is PEEK.  Not only does it
show the system status in various ways, it is significant because it
works by mapping system pages into its own address space and cannot
live anywhere but on a real ITS.

- For now, e-mail any questions or problems to either klh@netcom.com
or its-lovers@mc.lcs.mit.edu.  Another mailing list specific to
PI issues will probably be set up depending on interest.

--Ken