Remove $FreeBSD$: one-line bare tag

Remove /^\s*\$FreeBSD\$$\n/

Remove ia64.

This includes:
o All directories named *ia64*
o All files named *ia64*
o All ia64-specific code guarded by __ia64__
o All ia64-specific makefile logic
o Mention of ia64 in comments and documentation

This excludes:
o Everything under contrib/
o Everything under crypto/
o sys/xen/interface
o sys/sys/elf_common.h

Discussed at: BSDcan

Remove AppleTalk support.

AppleTalk was a network transport protocol for Apple Macintosh devices
in 80s and then 90s. Starting with Mac OS X in 2000 the AppleTalk was
a legacy protocol and primary networking protocol is TCP/IP. The last
Mac OS X release to support AppleTalk happened in 2009. The same year
routing equipment vendors (namely Cisco) end their support.

Thus, AppleTalk won't be supported in FreeBSD 11.0-RELEASE.

Spelling fixes for tools/

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

A new jail(8) with a configuration file, to replace the work currently done
by /etc/rc.d/jail.

Create the altix project branch. The altix project will add support
for the SGI Altix 350 to FreeBSD/ia64. The hardware used for porting
is a two-module system, consisting of a base compute module and a
CPU expansion module. SGI's NUMAFlex architecture can be an excellent
platform to test CPU affinity and NUMA-aware features in FreeBSD.

Add the regression test for bin/date.

- Import the HEAD csup code which is the basis for the cvsmode work.

Document the .in .out file naming conventions adopted in commit_prep.pl's
exclusions list for header checking.

Document a procedure for testing individual binaries under development.

Replace a mention of the ia64_unaligned directory with one of the
ia64 subdirectory. All ia64 specific regression tests live under
the ia64 directory.

Switch over to a different, more flexible test output protocol that's
understood by Perl's Test::Harness module and prove(1) commands.

Update README to describe the new protocol. The work's broken down into
two main sets of changes.

First, update the existing test programs (shell scripts and C programs)
to produce output in the ok/not ok format, and to, where possible, also
produce a header describing the number of tests that are expected to be
run.

Second, provide the .t files that actually run the tests. In some cases
these are copies of, or very similar too, scripts that already existed.
I've kept the old scripts around so that it's possible to verify that
behaviour under this new system (in terms of whether or not a test fails)
is identical to the behaviour under the old system.

Add a TODO file.

Add my getaddrinfo(3) stress-tester as gaithrstress. The most obvious
regressions would be to see the program or your kernel crashing.

If you want to give it something to really test out, try a much more
reentrant version of the resolver.
<URL:http://green.homeunix.org/~green/reentrant_resolver.patch>
Any Mozilla-based browser would show you a clear difference.

Add a regression test for the big pipe bug.

Suggested by: silby

Add regression tests for sysvipc.

Submitted by: Hiten Pandya <hiten@uk.FreeBSD.org>
Obtained from: NetBSD

Describe ia64_unaligned and geom directories. I hope I got these right.

Prefix tests with PASS and FAIL, to make grepping easier, and note this in
the README.

This affects only the base-system regression tests, of course.

Start adding framework for userland regression tests, and tests for
uuencode and uudecode.

Add Apple's filesystem exercising tool.

Submitted by: Conrad Minshall <conrad@apple.com>
Obtained from: Apple Computer

These are regression tests for the P1003.1B scheduler.

Approved by: jkh

Add a couple of test cases for mmap over NFS.

Fix a couple of typos.

README reads:
This directory is for regression test programs.

A regression test program is one that will excercise a particular bit of the
system to check that we have not reintroduced an old bug.

Please make a subdir per program, and add a brief description to this file.