Spelling fixes for tools/

Add some $FreeBSD$ tags so svn will allow the commit.

tools/KSE/ksetest/kse_threads_test.c

@@ -418,7 +418,7 @@ uts(struct kse_mailbox *km)
 
 	simplelock_lock(&data->runq->lock);
 	/*
-	 * Process any signals we've recieved (but only if we have
+	 * Process any signals we've received (but only if we have
 	 * somewhere to deliver them to).
 	 */
 	if ((data->runq->head != NULL) && SIGNOTEMPTY(km->km_sigscaught)) {

tools/debugscripts/gdbinit.i386

@@ -268,7 +268,7 @@ while (*(int *) $frame > 0xc0000000)
 end
 end
 document btr
-Show a backtrace from the ebp address specified.  This can be used to get a backtrace from any stack resident in memory.  It's the user's responsiblity to ensure that the address is meaningful.
+Show a backtrace from the ebp address specified.  This can be used to get a backtrace from any stack resident in memory.  It's the user's responsibility to ensure that the address is meaningful.
 end
 
 # btp <pid>

tools/debugscripts/kld_deb.py

@@ -68,9 +68,9 @@
 
 def searchfor(inp, re, j = 0, l = None):
 	"""searchfor(inp, re, j, l):  Searches for regex re in inp.  It will
-automaticly add more lines.  If j is set, the lines will be joined together.
+automatically add more lines.  If j is set, the lines will be joined together.
 l can provide a starting line to help search against.  Return value is a
-tupple of the last line, and the match if any."""
+tuple of the last line, and the match if any."""
 	ret = None
 	if not l:
 		l = inp.readline()
@@ -87,7 +87,7 @@ def searchfor(inp, re, j = 0, l = None):
 def get_addresses(inp, out):
 	"""get_addresses(inp, out):  It will search for addresses from gdb.
 inp and out, are the gdb input and output respectively.  Return value is
-a list of tupples.  The tupples contain the filename and the address the
+a list of tuples.  The tuples contain the filename and the address the
 filename was loaded."""
 	addr = []
 	nxad = 1

tools/regression/README

@@ -37,7 +37,7 @@ test name.  For example,
 A test may be flagged as 'todo'.  This indicates that you expect the test
 to fail (perhaps because the necessary functionality hasn't been written
 yet).  'todo' tests are expected to fail, so when they start working the
-test framework can alert you to this happy occurence.  Flag these tests 
+test framework can alert you to this happy occurrence.  Flag these tests 
 with a '# TODO' comment after the test name
 
     not ok 1 - infiniteloop # TODO write test for an infinite loop

tools/regression/bin/sh/builtins/cd1.0

@@ -7,7 +7,7 @@ T=$(mktemp -d sh-test.XXXXXX)
 
 chmod 0 $T
 if [ `id -u` -ne 0 ]; then
-	# Root can always cd, irregardless of directory permissions.
+	# Root can always cd, regardless of directory permissions.
 	cd -L $T 2>/dev/null && exit 1
 	[ "$PWD" = "$P" ]
 	[ "$(pwd)" = "$P" ]

tools/regression/fifo/fifo_io/fifo_io.c

@@ -395,7 +395,7 @@ timed_read(int fd, void *data, size_t len, ssize_t *read_lenp,
  *
  * We use a timeout of 5 seconds, concluding that in 5 seconds either all I/O
  * that can take place will, and that if we reach the end of the timeout,
- * then blocking has occured.
+ * then blocking has occurred.
  *
  * We assume that the buffer size on a fifo is <512K, and as such, that
  * writing that much data without an active reader will result in blocking.

tools/regression/file/dup/dup.c

@@ -104,7 +104,7 @@ main(int __unused argc, char __unused *argv[])
 	 * Normally dup and dup2 will clear the close-on-exec
 	 * flag on the new fd (which appears to be an implementation
 	 * mistake from start and not some planned behavior).
-	 * In todays implementations of dup and dup2 we have to make
+	 * In today's implementations of dup and dup2 we have to make
 	 * an effort to really clear that flag.  But all tested
 	 * implementations of dup2 have another tweak.  If we
 	 * dup2(old, new) when old == new, the syscall short-circuits

tools/regression/kthread/kld/kthrdlk.c

@@ -164,7 +164,7 @@ kthrdlk_done(void)
 	while (test_thrcnt != 0) {
 		ret = mtx_sleep(&global_condvar, &test_global_lock, 0, "waiting thrs end", 30 * hz);
 		if (ret == EWOULDBLOCK) {
-			panic("some threads not die! remaing: %d", test_thrcnt);
+			panic("some threads not die! remaining: %d", test_thrcnt);
 			break;
 		}
 	}

tools/regression/lib/libc/nss/README

@@ -5,7 +5,7 @@ A brief how-to
 
 Each nsswitch regression test does 2 kinds of actions:
 1. It runs a series of queries and tests the correctness of results.
-   There are 2 basic criterias which are used for that:
+   There are 2 basic criteria which are used for that:
       - numbers must be in the correct range
       - certain pointers should not be NULL
 

tools/regression/nfsmmap/Makefile

@@ -1,3 +1,5 @@
+# $FreeBSD$
+
 SUBDIR= test1 test2
 
 .include <bsd.subdir.mk>

tools/regression/nfsmmap/README

@@ -1,3 +1,4 @@
+$FreeBSD$
 These tests are intended to make sure that NFS's use of the
 b_{valid,dirty}{off,end} fields of struct buf is consistent with the
 VM system's use of the underlying VM pages.
@@ -17,4 +18,4 @@ Test2:
 	should first write out the dirty range and then read the rest
 	of the page.  This is currently broken since the vnode_pager
 	doesn't use the original buf for its i/o and therefore the
-	information in b_dirtyoff, b_dirtyend is not avalable.
+	information in b_dirtyoff, b_dirtyend is not available.

tools/regression/pjdfstest/tests/chown/00.t

@@ -296,7 +296,7 @@ for type in regular dir fifo block char socket symlink; do
 	fi
 done
 
-# successfull chown(2) call (except uid and gid equal to -1) updates ctime.
+# successful chown(2) call (except uid and gid equal to -1) updates ctime.
 for type in regular dir fifo block char socket symlink; do
 	if [ "${type}" != "symlink" ]; then
 		create_file ${type} ${n0}

tools/regression/priv/priv_cred.c

@@ -31,7 +31,7 @@
 
 /*
  * Confirm that various UID/GID/etc-related system calls require root
- * privilege in the absense of any saved/real/etc variations in the
+ * privilege in the absence of any saved/real/etc variations in the
  * credential.  It would be nice to also check cases where those bits of the
  * credential are more interesting.
  *

tools/regression/security/open_to_operation/open_to_operation.c

@@ -796,7 +796,7 @@ check_write(const char *testname, write_fn fn, const char *path,
 		} else {
 			if (!((mode & O_ACCMODE) == O_WRONLY ||
 			    (mode & O_ACCMODE) == O_RDWR))
-				notok_mode(testname, "write suceeded", mode);
+				notok_mode(testname, "write succeeded", mode);
 			else
 				ok_mode(testname, "write succeeded", mode);
 		}
@@ -880,7 +880,7 @@ check_read(const char *testname, read_fn fn, const char *path,
 		} else {
 			if (!((mode & O_ACCMODE) == O_RDONLY ||
 			    (mode & O_ACCMODE) == O_RDWR))
-				notok_mode(testname, "read suceeded", mode);
+				notok_mode(testname, "read succeeded", mode);
 			else
 				ok_mode(testname, "read succeeded", mode);
 		}

tools/regression/usr.bin/env/regress-sb.rb

@@ -341,7 +341,7 @@ class RGTestOptions
 	#   for test data.  Format of all recognized values should be:
 	#		[%-object.value-%]
 	#   which is hopefully distinctive-enough that they will never
-	#   conflict with any naturally-occuring string.  Also note that
+	#   conflict with any naturally-occurring string.  Also note that
 	#   we only match the specific values that we recognize, and not
 	#   "just anything" that matches the general pattern.  There are
 	#   no blanks in the recognized values, but I use an x-tended

tools/regression/usr.bin/make/README

@@ -8,7 +8,7 @@ output for '^not ok'.
 
 ----------------------------------------------------------------------------
 
-The rest of this file is intented for developers.
+The rest of this file is intended for developers.
 
 The tests are invoked via the test.sh script or prove(1) from p5-Test-Harness.
 Tests are normally executed in a special test directory that is built under

tools/regression/usr.bin/make/variables/modifier_M/Makefile

@@ -12,7 +12,7 @@ test1:
 	@echo "all files: ${FILES}"
 	@echo "cfiles: ${FILES:M*.c}"
 	@echo "hfiles: ${FILES:M*.h}"
-	@echo "grammer and lexer: ${FILES:M*.[ly]}"
+	@echo "grammar and lexer: ${FILES:M*.[ly]}"
 	@echo "man page: ${FILES:M*.[1-9]}"
 	@echo "utility files: ${FILES:Mutil.?}"
 	@echo "m files: ${FILES:Mm*}"

tools/regression/usr.bin/make/variables/modifier_M/expected.stdout.1

@@ -1,7 +1,7 @@
 all files: main.c globals.h  util.c util.h  map.c map.h  parser.y lexer.l  cmdman.1 format.5
 cfiles: main.c util.c map.c
 hfiles: globals.h util.h map.h
-grammer and lexer: parser.y lexer.l
+grammar and lexer: parser.y lexer.l
 man page: cmdman.1 format.5
 utility files: util.c util.h
 m files: main.c map.c map.h

tools/regression/usr.bin/sed/math.sed

@@ -57,7 +57,7 @@ x
 	s//\1(\2)/
 	b loop
 }
-# pull any burried exponents
+# pull any buried exponents
 /^\(.*[^0-9]\)\([0-9][0-9]*^[0-9][0-9]*\)$/{
 	s//\1(\2)/
 	b loop

tools/regression/usr.sbin/newsyslog/regress.sh

@@ -70,8 +70,8 @@ cknt()
 	fi
 }
 
-# Check if a file is there, depending of if it's suposed to or not -
-# basically how many log files we are suposed to keep vs. how many we
+# Check if a file is there, depending of if it's supposed to or not -
+# basically how many log files we are supposed to keep vs. how many we
 # actually keep.
 ckntfe()
 {

tools/test/posixshm/shm_test.c

@@ -1,6 +1,6 @@
 /*
  * Test the POSIX shared-memory API.
- * Dedicated to tyhe public domain by Garrett A. Wollman, 2000.
+ * Dedicated to the public domain by Garrett A. Wollman, 2000.
  * $FreeBSD$
  */
 

tools/test/testfloat/systemBugs.txt

@@ -27,7 +27,7 @@ For some reason, most of the bugs found involve conversions from floating-
 point to integer formats.
 
 The bugs are shown as actual TestFloat error lines, along with a brief
-explanation.  The error lines given are not necesarily exhaustive and were
+explanation.  The error lines given are not necessarily exhaustive and were
 not necessarily output in the order shown.
 
 This document does not pretend to be an authoritative bug listing for all

tools/test/testfloat/testfloat-source.txt

@@ -46,7 +46,7 @@ name has been obsolete for some time.
 Limitations
 
 TestFloat as written requires an ISO/ANSI-style C compiler.  No attempt has
-been made to accomodate compilers that are not ISO-conformant.  Older ``K&R-
+been made to accommodate compilers that are not ISO-conformant.  Older ``K&R-
 style'' compilers are not adequate for compiling TestFloat.  All testing I
 have done so far has been with the GNU C Compiler.  Compilation with other
 compilers should be possible but has not been tested.
@@ -168,7 +168,7 @@ intended to be identical to that included with the SoftFloat source.
 
 These are the defaults, but other organizations of the sources are possible.
 The TestFloat makefiles and `milieu.h' files (see below) are easily edited
-to accomodate other arrangements.
+to accommodate other arrangements.
 
 
 -------------------------------------------------------------------------------

tools/test/testfloat/testfloat.txt

@@ -289,7 +289,7 @@ raise the invalid exception if the source value cannot be rounded to a
 representable integer of the desired size (32 or 64 bits).  If such a
 conversion overflows, TestFloat expects the largest integer with the same
 sign as the operand to be returned.  If the floating-point operand is a NaN,
-TestFloat allows either the largest postive or largest negative integer to
+TestFloat allows either the largest positive or largest negative integer to
 be returned.
 
 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
@@ -629,7 +629,7 @@ TestFloat assumes that conversions to integer will raise the invalid
 exception if the source value cannot be rounded to a representable integer.
 When the conversion overflows, TestFloat expects the largest integer with
 the same sign as the operand to be returned.  If the floating-point operand
-is a NaN, TestFloat allows either the largest postive or largest negative
+is a NaN, TestFloat allows either the largest positive or largest negative
 integer to be returned.  The current version of TestFloat provides no means
 to alter these conventions.
 

tools/tools/bus_autoconf/bus_autoconf.c

@@ -27,7 +27,7 @@
 
 /*
  * Disclaimer: This utility and format is subject to change and not a
- * comitted interface.
+ * committed interface.
  */
 
 #include <stdio.h>

tools/tools/cd2dvd/cd2dvd.sh

@@ -229,7 +229,7 @@ then
 	echo "Error: less than two CD images specified."
 fi
 
-## Some usefull variables
+## Some useful variables
 pwd=`pwd`
 tmpdirin="${pwd}/tmp-$$-in"
 tmpdirout="${pwd}/tmp-$$-out"

tools/tools/net80211/wlaninject/README

@@ -46,7 +46,7 @@ Interesting 802.11 header options.
    will be calculated.  Symbolic names are:
 	preq, probereq	Probe Request
 	auth		Authenticate
-	areq, assocreq	Assocation Request
+	areq, assocreq	Association Request
 	data		Data
    Otherwise the numerical subtype must be supplied.
 -4 The 4th MAC addr used for WDS.  Make sure you specify this before

tools/tools/netmap/bridge.c

@@ -227,7 +227,7 @@ process_rings(struct netmap_ring *rxring, struct netmap_ring *txring,
 		ts->buf_idx = rs->buf_idx;
 		rs->buf_idx = pkt;
 
-		/* copy the packet lenght. */
+		/* copy the packet length. */
 		if (rs->len < 14 || rs->len > 2048)
 			D("wrong len %d rx[%d] -> tx[%d]", rs->len, j, k);
 		else if (verbose > 1)

tools/tools/netmap/pkt-gen.c

@@ -432,7 +432,7 @@ sender_body(void *data)
 
 	if (setaffinity(targ->thread, targ->affinity))
 		goto quit;
-	/* setup poll(2) machanism. */
+	/* setup poll(2) mechanism. */
 	memset(fds, 0, sizeof(fds));
 	fds[0].fd = targ->fd;
 	fds[0].events = (POLLOUT);
@@ -543,7 +543,7 @@ receiver_body(void *data)
 	if (setaffinity(targ->thread, targ->affinity))
 		goto quit;
 
-	/* setup poll(2) machanism. */
+	/* setup poll(2) mechanism. */
 	memset(fds, 0, sizeof(fds));
 	fds[0].fd = targ->fd;
 	fds[0].events = (POLLIN);
@@ -568,7 +568,7 @@ receiver_body(void *data)
 		   before quitting. */
 		if (poll(fds, 1, 1 * 1000) <= 0) {
 			gettimeofday(&targ->toc, NULL);
-			targ->toc.tv_sec -= 1; /* Substract timeout time. */
+			targ->toc.tv_sec -= 1; /* Subtract timeout time. */
 			break;
 		}
 
@@ -994,8 +994,8 @@ main(int arc, char **argv)
 			continue;
 
 		/*
-		 * Collect threads o1utput and extract information about
-		 * how log it took to send all the packets.
+		 * Collect threads output and extract information about
+		 * how long it took to send all the packets.
 		 */
 		count += targs[i].count;
 		if (!timerisset(&tic) || timercmp(&targs[i].tic, &tic, <))

tools/tools/sysbuild/README

@@ -22,7 +22,7 @@ If you know how nanobsd works, you will find a lot of similarity.
 HOWTO
 =====
 
-In all likelyhood, it is easier if we imagine you start with a blank
+In all likelihood, it is easier if we imagine you start with a blank
 computer.
 
 Grab a FreeBSD install ISO and boot it.

tools/tools/tinybsd/README

@@ -105,7 +105,7 @@ do that step-by-step.
 3) Edit the tinybsd.basefiles file and add/remove all binaries you'll need on
 your system.
 
-4) Copy all your /etc configuration wich you want to conf/YOURIMAGE/etc/.
+4) Copy all your /etc configuration which you want to conf/YOURIMAGE/etc/.
 
 5) Gather the right information on your destination media. To do that, plug in
 the device on the system and fetch the information using diskinfo(8):