This is a tutorial of how to install xiafs-0.7.2

SETUP
	(Frank):
	AMD386-40, 4MB, MX7120A 120MB and MX7213A 210MB IDE disks. 
	GCC 2.3.3./libc 4.3
	/dev/hdb1 /      xiafs
	/dev/hdb2        swap
	/dev/hdb3 /usr   xiafs

	(Fred):
	iNTEL 386DX25, 8Mb, 2xMFM 41Mb (GCC 2.2.2d7, JT 4.1)
	iNTEL 486DX50, 16Mb, Seagate 105Mb and Conner 170Mb IDE, 
	GCC 2.3.3/JT 4.2

CONTENTS
	A copy of virgin Linux-0.99.6.tar.Z (dirty copy is ok if you know
	how to make patch against it), 
	A copy of xiafs-0.7.2.tar.Z.

INSTALL
	Login as root.
	Unpack linux-0.99.6.tar.Z as you did before under /usr/src.
	Unpack xiafs-0.7.2.tar.Z under /usr/src.

		# zcat xiafs-0.7.2.tar | tar xvf -
		
	Apply patch.

		# patch -p0 < xiafs-0.7.2/l99.6xfs7.2.diff 2>&1 | tee p.log

	Check p.log to make sure patch are successfully applied.
	Change to linux directory and make the kernel.

		# cd linux
		# make clean
		# make config
		# make dep
		# make

	Install the kernel in your favorite way.

MKFS
	Use efdisk to make a partition for xiafs with ID number 88.  This
	doesn't actually matter much, since LINUX does not check on the
	partition type values.  However, it looks cleaner if you use some
	unique partition type for each kind of file system...

	Create a XIA-FS file system.  If your disk(s) is not IDE or SCSI,
	make sure you use switch "-c".  The "-c" switch checks the bad
	blocks on your hard disk and marks them as used blocks so other 
	files will not use them.  (Fred: You can call the file system 
	creating program either by calling the new "mkxfs" program
	directly, as in:

		# mkxfs -c /dev/hda3 131072

	or you can install this program in the /etc directory with the
	name "mkfs.xiafs", and then use the newly posted "mkfs" frontend
	as follows:

		# mkfs -t xiafs -c /dev/hda3 131072

	to create a file system.  I personally prefer the latter method.)

	The above command line (either form) makes a 128MB xiafs filesystem
	on /dev/hda3. If switch "-c" is on, mkxfs will write the bad block
	numbers in the file "badblocks.log", one number per line. It is
	harmless to use "-c" for an IDE or SCSI disk, but it takes a while to
	check a large partition.

FSCK
	Then, run xfsck to show the super block information and make a first
	check.

		# xfsck -s /dev/hda3
		# xfsck /dev/hda3

	(Fred: Alternatively, you can again install this program as 
	"fsck.xiafs", and call the "fsck" frontend as:

		# fsck -t xiafs -s /dev/hda3
		# fsck -t xiafs /dev/hda3

	) Write down the super block information as shown by xfsck. In case
	things get funny, it will help me figure out what is wrong.

MOUNT
	Mount the xiafs.

		# mount -t xiafs /dev/hda3 /usr/test

	Now you can play with it. Use xfsck check xiafs regularly.  

BUGS
	In case things get funny, or, worse, you get into serious trouble,
	please contact me by email to:

		Frank Xia <qx@math.columbia.edu>

	Please include following information:

		kernel version (should be 0.99.6 or up)
		xiafs version (should be 0.7.2 or up)
		disk type (MFM/RLL disks may give trouble)
		gcc version (GCC 2.2.2d7 hasn't been tested, really)

AUTHOR
	Frank Xia <qx@math.columbia.edu>
	Fred N. van Kempen, <waltje@uwalt.nl.mugnet.org> (cleanups)
