Update sources to 1.2.1

Submitted by:	wxs@
Add, remove and move files for the 1.2.1 import of libpcap

Submitted by:	wxs
General mdoc(7) and typo fixes.

PR:		167713
Submitted by:	Nobuyuki Koganemaru (kogane!jp.freebsd.org)
Always define LD_32_PRELOAD so it works for 32 bits binaries on
64 bits platforms.  Let rtld(1) decide if it needs to honor it
or not.

While here, fix a small bug in error reporting when asprintf(3)
returns an error.

Submitted by:	kib
Reviewed by:	kib (mentor)
MFC after:	1 week
Plug a leak.

Submitted by:	Greg Bednarek <gbednarek averesystems com>
MFC after:	1 week
The DEVICE_POLLING dereference of sc->tsec_ifp needs to be checked for null
first or this will panic. Condense three blocks that check sc->tsec_ifp into
one while I am here.
- Rename sysctl "loose_rx_mtu" to "strict_rx_mtu" to match code usage.

Submitted by:	davidch
MFC after:	1 day
Do not reinitialise the interface if it is already running, this prevents the
bootp+nfs code from working as it calls init on each dhcp send and rx fails to
start in time.
The DDB_CTF has little or nothing to do with the debugger so move it
next KDTRACE_HOOKS.
Implement basic remote PHY support. Remote PHY allows the
controller to perform MDIO type accesses to a remote transceiver
using message pages defined through MRBE(multirate backplane
ethernet).  It's used in blade systems(e.g Dell Blade m610) which
are connected to pass-through blades rather than traditional
switches.
This change directly manipulates firmware's mailboxes to control
remote PHY such that it does not use mii(4).  Alternatively, as
David said, it could be implemented in brgphy(4) by creating a fake
PHY and let brgphy(4) do necessary mii accesses and bce(4) can
implement mailbox accesses based on the type of brgphy(4)'s mii
accesses. Personally, I think it would make brgphy(4) hard to
maintain since it would have to access many bce(4) registers in
brgphy(4). Given that there are users who are suffering from lack
of remote PHY support, it would be better to get working system
rather than waiting for complete/perfect implementation.

Tested by:	Jan Winter ( jan.winter <> kantarmedia dot de )
Reviewed by:	davidch (initial version)
MFC after:	2 weeks
Make is part of the bootstrap path, so we need to guard against this
not being defined.  Otherwise we don't make a new make when the old
make is incompatible.
sys/boot: add common CTASSERT definition
btxldr: future-proof argument passing from boot1/2-ish to loader

Place the arguments at a fixed offset of 0x800 withing the argument area
(of size 0x1000).  Allow variable size extended arguments first of which
should be a size of the extended arguments (including the size
parameter).

Consolidate all related definitions in a new i386/common/bootargs.h header.

Many thanks to jhb and bde for their guidance and reviews.

Reviewed by:	jhb, bde
Approved by:	jhb
MFC after:	1 month
i386 boot: consolidate MAXBDDEV definition

MFC after:	1 month
i386 zfsloader: rename LIBZFS to LIBZFSBOOT

... to avoid name clash with the other libzfs

MFC after:	1 month
r235154 followup: add stddef.h for offsetof

MFC after:	1 month
Mac OS X 10.8 added (belatedly).
Revert r235194: 10.8 appears to be a developer preview.

Reported by:	trasz
Clarify error that geli generates
when it finds corrupt data.

PR:		kern/165695
Submitted by:	Robert Simmons <rsimmons0@gmail.com>
Reviewed by:	pjd
Approved by:	cperciva
MFC after:	1 week
Remove reference to non-existent FreeBSD Security Architecture

Approved by:	cperciva
MFC after:	3 days