
		  	  	XZET	1.0

		    Graphical System Activity Monitor

			       INSTALLATION		

    		         	Zman 02/94



Xzet is normally distributed as a tar'd archive (or perhaps a GZIPPED tar'd
archive).  This archive includes the top level directory for xzet, which is
'xzet1.0'.  To begin the installation of xzet, simply enter the directory
that you wish to place this top level directory in and use the appropriate
tar command to un-archive the source code.  For example:

		cd /my-new-code-dir
		tar -xvzf ~/xzet1.0.tgz

This should result in the restoration of the following files:

		COPYING
		IAFA-PACKAGE
		INSTALL.xzet
		Imakefile
		README.xzet
		XZet.ad
		Xzet.h
		Ztach/Imakefile
		Ztach/Ztach.README
		Ztach/Ztach.c
		Ztach/Ztach.h
		Ztach/Ztach.man
		Ztach/ZtachP.h
		Ztach/ZtachT.c
		Ztach/ZtachT.man
		Ztach/ZtachTest
		Ztach/ZtachTest-how
		activity.c			
		bit-o-snap.c
		patchlevel.h
		process.c
		ps.h
		psdata.h
		sysinfo.h
		whattime.h
 		xzet.c
		xzet.man
		xzetactivity.bit
		xzetmain.bit
		xzetplist.bit
		xzetprocess.bit



This rest of this document is merely a copy of section seven of the README
file for xzet:


VII.  How do I build xzet from the source?
-----------------------------------------

If you are running Linux, then it should be extremely easy to build xzet, 
with no changes on your part needed at all.  Other OS's that support the
proc file system should only require minor changes (probably to the names of
some of the system level include files).  If your system doesn't support the
proc file system, then the easiest thing to do will probably be to duplicate 
the services provided within the file 'bit-o-snap.c'. That will permit you
to leave all of the rest of the source code untouched (except, as noted above,
for changes to the names of include files).  Of course, if you have System V
Rel 3.2, you may just wish to get a copy of xetat from the comp.sources
directory, volume 17.  
 
================ Starting point for patience impaired users =================
			
Changes to the code aside, once you have untared (or whatever...) the source 
code, the first thing to do is enter the sub-directory 'Ztach'.  This contains 
the source code for the tachometer widget which is used by xzet. This is a
complete distribution for the widget, including a README file, man pages,
and most importantly, an Imakefile to build the widget and a small test
client. Build the make file using either 'xmkmf' or using 'imake' with a
command line similar to the following:  

imake -DUseInstalled -I/usr/X386/lib/X11/config

Then run the 'make' command to generate the widget object and the test
client.  The test client is called 'ZtachT' and may be run at this time to
verify correct compilation.  (See the man pages and readme for further
information.) 

Once the tach widget is built, return to the main xzet directory, and create 
the make file for xzet using the same procedure specified above for the Ztach.

At this point, a 'make depend' may proove useful in finding include files
whose names may need to be changed.  I suspect that some of the  following 
files may need to be changed:  <linux/kernel.h>, <linux/sys.h>, <linux/tasks.h>,
<unistd.h>,  <sys/vfs.h>, <sys/dir.h>, <sys/user.h>  and <regex.h>.  
VFS.H is most notable here because it contains the struct for the 'statfs' 
call used to monitor the freespace in the user specified file systems.
TASKS.H only contains the 'NR_TASKS' define which sets the maximum number of
tasks which Linux can run.  Create your own file, or move the define to the
source code if your system doesn't have this file. SYS.H defines some of the
system calls (statfs), and may not be necessary to compile on your system. 
( The same may also be true of kernel, unistd, dir, user and regex ). In
fact, other than for VFS and TASKS, I would first try commenting out all
failed include files and then running a 'make', to see just how much further
work really needed to be done.  It may be less than you think!  For Linux
users, 'depends'' complaints about not finding 'stddef' and 'float' can be
ignored.

Once the include file situation is handled, a 'make' should be run to
generate the actual xzet application.  This takes less than five minutes 
on my meager 386/33.  

Before running xzet, be sure to set the application resources by either
running a 'make install' or using your own favorite technique to point to a
resource file not in the app-defaults directory.  Xzet is not well behaved
at all without its resource file!  (Install will also copy xzet to your X11
bin directory.)

Finally, use 'make install.man' to install the man pages.
