freebsd-nq

History

Marcel Moolenaar 6763e7c1ed Add the beginnings of a testsuite for testing GPT control requests. The testsuite is based on a simple driver program that builds a request from the arguments passed to it and issues the request to Geom. The driver emits FAIL with the error string or PASS depending on whether the request completed with an error or not. A -v option has been added to the driver and causes the request to be dumped. The -v option to prove(1) controls the -v option to the driver. The testsuite itself contains a hash of which the key constitutes the arguments and the value is the expected result.		2005-09-19 02:59:09 +00:00
..
build	Make <runefile.h> internal to libc.	2005-05-16 09:32:41 +00:00
debugscripts	I forgot to commit this fix that is now kgdb aware...	2005-03-20 02:08:21 +00:00
diag	Start the dreaded NOFOO -> NO_FOO conversion.	2004-12-21 08:47:35 +00:00
kerneldoc	Experimental support for using doxygen to generate kernel documentation.	2004-07-11 16:13:57 +00:00
KSE	Start the dreaded NOFOO -> NO_FOO conversion.	2004-12-21 08:47:35 +00:00
lib32	Remove the build32.sh hack, it is now slightly broken (missing some	2004-11-25 04:25:21 +00:00
LibraryReport
regression	Add the beginnings of a testsuite for testing GPT control requests.	2005-09-19 02:59:09 +00:00
sched	- ktrace(1) has nothing to do with schedgraph. Remove that from the	2005-03-14 11:52:24 +00:00
test	Start the dreaded NOFOO -> NO_FOO conversion.	2004-12-21 08:47:35 +00:00
tools	Remove reference to bpfstat, this no longer exists.	2005-09-17 23:45:22 +00:00
install.sh	Arguments to options aren't necessarily separated with whitespace.	2004-07-07 09:38:14 +00:00
make_libdeps.sh	Teach the script where libssl actually lives.	2004-04-13 11:06:20 +00:00
README

README

$FreeBSD$

This directory tree contains tools used for the maintenance and
testing of FreeBSD.  There is no toplevel Makefile structure since
these tools are not meant to be built as part of the standard system,
though there may be individual Makefiles in some of the subdirs.

Please read the README files in the subdirs for further information.