These files are a crude begining of testing the flash filesystem on
Brecis boards.

They are not very portable between environments at this point (original
checkin).  Specifically:

1. "telnet zaphod 2016":  

	My EVM console serial port is connected to a terminal server.
	This command connects to the EVM console to get output and
	send input.  For a locally attached port, you'd use cu,
	kermit, or perhaps minicom (Does minicom work well under
	expect???) 

2. "rst x":

	My EVM is connected to an x10 power control device, similar to
	remdev, with pwrup, pwrdwn, and rst scripts of the same name.
	I use "x" as the paramter (ignored in my system) so I don't
	accidentally run this on remdev and power down someone else's
	test.  Change accordingly.

3. "bootit":

	This command does the usual TFTP to download code to a board.
	I assume everyone's using a similar script, rather than typing
	the commands every time...

4. "mount -n 199.86.15.105:/home/steve/work/uClinux /mnt":

	In fstest_setup, ip address and path hardcoded.  You'll have
	to change to match your own setup.

Other necessary changes may be missing from this list.

With that out of the way, here's a description of the files:

fstest - test the filesystem to see if it is "intact" after a power
down.  It will, of course, loose the last few writes, but it should
not leave the filesystem in an inconsistent state.  Based on checkfs
shiped with the mtd/jffs2 source.

fstest2 - same as fstest, except only power cycles the board once, at
the very begining.  Thereafter, it shuts the board down "nicely",
causing a soft reset.  Supposedly, crc errors in the filesystem will
not show up except if the EVM is powered down or reset mid write.
This file is supposed to prove that.

fstest_setup - erases the flash and starts from a known good
filesystem.

