The Loony Bin
(
loonies@bloodaxe.demon.co.uk
)
Wed, 27 Aug 1997 01:59:56 +0100
Hiya All...
Here's a new UNIX man page...from the Oracle...
Wishes & Dreams...
- ANDREA
xx
***<andrea@bloodaxe.demon.co.uk>****<ajc6@ukc.ac.uk>***
***<bloodaxe@geocities.com>***<bloodaxe@bigfoot.com>***
*** ***
*** THE LOONY BIN ***
*** loonies@bloodaxe.demon.co.uk ***
*** Archive: http://eleceng.ukc.ac.uk/~pjw/loonies/ ***
*** ***
*******************Internet Goddess********************
**********************ANDROMEDA************************
------- Forwarded foolishness follows -------
The Internet Oracle has pondered your question deeply.
Your question was:
> gzip -d woodchuck.tar.gz
> tar -xf woodchuck.tar
> cd woodchuck
> xmkmf
> make all
> make install
> man 1 woodchuck
> /usr/bin/woodchuck
And in response, thus spake the Oracle:
}% man 1 woodchuck
}
} WOODCHUCK(1)
}
} NAME
} woodchuck - chuck wood
}
} SYNOPSIS
} woodchuck [options] source [destination]
} Options:
} [-rlb]
}
} DESCRIPTION
} This manual page documents the GNU version of woodchuck. GNU
} woodchuck will chuck wood from the source directory to the
} destination directory. If no destination is specified, the
} wood is chucked into the user's current working directory.
}
} It is necessary to remove wood from an inode in order to
} make full use of it (exceptions: hike, sparrow, lemur, etc),
} however the presence of too much chucked wood in a directory
} can render it equally unusable. Hence it is recommended that
} woodchuck be used in tandem with sawmill(1), a GNU project
} replacement for the standard UNIX(tm) burn(1).
}
} OPTIONS
} -r, --resilient
} Ignore standard requests to terminate. Will only
} terminate on the use of ZOT -9.
} -l, --lemur
} Lemur compatibility mode. Will not attempt to chuck
} wood already in use by the lemur program.
} -b, --background
} Continue running, after the invoking user logs out.
} The same result can be achieved with the nohup
} program.
} -a, --all
} Chuck wood from all directories available to the
} user. Use in conjunction with -br with caution.
} -R n
} Specifies the rate at which wood will be chucked.
} High values of n can increase system load markedly.
} -h, --help
} Prints usage information.
} -v, --version
} Prints version information.
}
} SEE ALSO
} lemur(6), ZOT(1), sawmill(1), burn(1)
}
} AUTHOR
} Joel Furr did most of the work in porting woodchuck from
} the original Microsoft(tm) version. The Microsoft(tm) copy
} is no longer distributed, however many of the key ideas
} are incorporated in Microsoft Windows(tm).
}
} 17 August, 1997
}
} > /usr/bin/woodchuck
}
} Syntax: woodchuck [options] source [destination]
}
} > /usr/bin/woodchuck /tmp
}
} Felling wood in /tmp . . . Done.
} Chucking wood into /home/oracle . . . Done.
}
} > cd /tmp
} > ls -al
}
} drwxrwxrwt 4 root root 1024 Aug 18 01:03 ./
} drwxr-xr-x 18 root root 1024 Aug 18 00:59 ../
}
} > cd
} > ls -al
}
} drwxrwxr-x 3 jrl jrl 1024 Aug 18 01:03 ./
} drwxr-xr-x 5 root root 1024 Aug 18 00:59 ../
} -rw-r--r-- 1 jrl jrl 124 Jun 29 00:14 .bashrc
} -rw-r--r-- 1 jrl jrl 307 Jun 27 03:03 .profile
} -rw-r--r-- 1 jrl jrl 4096 Aug 17 02:01 wood0001
} -rw-r--r-- 1 jrl jrl 4096 Aug 17 02:01 wood0002
} -rw-r--r-- 1 jrl jrl 4096 Aug 17 02:02 wood0003
} -rw-r--r-- 1 jrl jrl 4096 Aug 17 02:03 wood0004
} -rw-r--r-- 1 jrl jrl 4096 Aug 17 02:01 wood0005
} -rw-r--r-- 1 jrl jrl 4096 Aug 17 02:04 wood0006
} -rw-r--r-- 1 jrl jrl 4096 Aug 17 02:01 wood0007
} -rw-r--r-- 1 jrl jrl 4096 Aug 17 02:05 wood0008
} [truncated for sanity]
}
} There you go, supplicant. All your data neatly stacked in blocks of
} 4kb.
}
} You owe the oracle woodchuck -arb run on your system as root.