Installing ofiles

1.  Pick a destination installation directory and enter it as the BIN string
    in Makefile.

2.  Establish what group -- kmem, operator, etc. -- has read access to
    /dev/kmem and enter it as the KMEM string in Makefile.

3.  Set the OSVERS string in the Makefile for the NeXTStep version for which
    you are building ofiles.  Note that there is a special version of user.h
    for NeXTStep 1.0a, NS_1.0a_user.h., because the <sys/user.h> in my version
    of NeXTStep 1.0a does not match the utask structure of the kernel.

3.  If you are compiling ofiles for use on a diskless NFS client of a NeXTStep
    server, you may need to change the KNAMELIST string.  On my NeXTStep 1.0a
    test machine, /mach is a symlink to $BOOTFILE, but $BOOTFILE is not
    defined.  (Usually $BOOTFILE resolves to /sdmach or /odmach.)  This is
    the way to set KNAMELIST for /sdmach.

	KNAMELIST=-DVMUNIX=\"/sdmach\"

    (The escaped quotes are necessary, because VMUNIX defaults to "/mach" in
    ofiles.c.)

4.  Compile ofiles:

	% make ofiles

5.  Become root and install it:

	# make install

    If you are installing ofiles for use from a diskless NSF client of a
    NeXTStep server, you may need to take other steps to enable ofiles to
    read /dev/kmem, depending on your particular NFS environment.

WARNING:

	Ofiles has only been tested under NeXTStep 1.0a and 2.0.

Vic Abell <abe@mace.cc.purdue.edu>
Purdue University Computing Center
May 3, 1991