freebsd-skq

History

Jilles Tjoelker e9dec7758d popen(): Add 'e' mode character to set close-on-exec on the new fd. If 'e' is used, the kernel must support the recently added pipe2() system call. The use of pipe2() with O_CLOEXEC also fixes race conditions between concurrent popen() calls from different threads, even if the close-on-exec flag on the fd of the returned FILE is later cleared (because popen() closes all file descriptors from earlier popen() calls in the child process). Therefore, this approach should be used in all cases when pipe2() can be assumed present. The old version of popen() rejects "re" and "we" but treats "r+e" like "r+".		2013-05-20 17:31:18 +00:00
..
bsdbox	Do a bunch of fixing and refactoring.	2012-08-29 22:55:50 +00:00
build	Add support for an external cross compiler. The cross compiler is	2013-05-15 14:30:03 +00:00
debugscripts	A number of places in the source tree still reference cuad.* after	2012-12-08 22:16:36 +00:00
diag	Remove scripts and tools which only functioned when src was using CVS	2012-09-13 17:49:11 +00:00
kerneldoc	Correct double "the the"	2012-09-14 21:28:56 +00:00
KSE	Spelling fixes for tools/	2011-12-30 00:04:11 +00:00
LibraryReport
regression	popen(): Add 'e' mode character to set close-on-exec on the new fd.	2013-05-20 17:31:18 +00:00
sched
test	As python3 does not have raw_input(), convert it to input() when we	2013-05-13 19:53:19 +00:00
tools	Minor mdoc improvements.	2013-05-16 20:55:20 +00:00
install.sh	Use = not == in test arguments.	2013-01-24 20:47:37 +00:00
make_libdeps.sh	Import libyaml as libbsdyml (private brand name)	2013-03-04 11:27:41 +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.