freebsd-skq

History

Enji Cooper fa8093473b Integrate pjdfstest test suite execution into kyua pjdfstest execution is opt-in and must be done as root due to some of the assumptions made by the test suite and lack of error checking in the non-root case A description of how to execute pjdfstest with kyua is provided in share/pjdfstest/README Phabric: D824 (an earlier prototype patch) MFC after: 1 month Relnotes: yes Sponsored by: EMC / Isilon Storage Division		2014-11-03 07:18:42 +00:00
..
bsdbox	Replace all uses of libncurses and libtermcap with their wide character	2014-07-17 18:24:34 +00:00
build	Integrate pjdfstest test suite execution into kyua	2014-11-03 07:18:42 +00:00
bus_space	Add a C libary and a Python module that implements an API similar	2014-04-28 18:06:11 +00:00
debugscripts	A number of places in the source tree still reference cuad.* after	2012-12-08 22:16:36 +00:00
diag	NO_MAN= has been deprecated in favor of MAN= for some time, go ahead	2014-04-13 05:21:56 +00:00
ifnet	* Handle ++x as well as x++ while converting.	2014-06-25 15:22:14 +00:00
kerneldoc	Clean up more lindev(4) vestiges.	2014-05-02 11:09:01 +00:00
KSE	NO_MAN= has been deprecated in favor of MAN= for some time, go ahead	2014-04-13 05:21:56 +00:00
LibraryReport
regression	Remove incorrect semicolon.	2014-10-26 17:56:58 +00:00
sched	Add schedgraph traces for callout handlers. Specifically, a callwheel logs	2014-10-08 16:22:59 +00:00
test	Ignore a test program which doesn't compile at the moment. It will be	2014-09-21 21:31:16 +00:00
tools	cxgbetool: Catch up with r185979. One of MAP_ANON, MAP_PRIVATE,	2014-10-21 01:34:18 +00:00
install.sh	Use = not == in test arguments.	2013-01-24 20:47:37 +00:00
make_libdeps.sh	Avoid rs(1) hitting LINE_MAX with custom trees that have large dependencies.	2014-09-08 17:01:30 +00:00
README
tinder.sh	Add a comment that shows how to limit the build to the specific list of arches.	2011-11-28 14:03:36 +00:00

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.