Add a wpa_supplicant rc script and bring in code to handle "WPA" in an
ifconfig_blah0="..." line in rc.conf. It should now be possible to bring
up a wireless interface with a line similar to:
ifconfig_iwi0="up WPA DHCP"
This commit also removes the restriction that when "DHCP" was specified,
the rest of the arguments were ignored. So the following should work now:
ifconfig_rl0="DHCP media 10baseT/UTP"
The commit also adds rc settings for interface renaming, e.g.:
ifconfig_iwi0_name="net0"
ifconfig_net0="up WPA DHCP"
Obtained-from: FreeBSD

Now that we support foo_enable="YES|NO" as well as foo="YES|NO" some
variables collide because they use foo="" for something else.
Rename those variables to non-conflicting names.
Noticed-by: Sascha Wildner
The securelevel stuff is based on Kevin L. Kane work.

Mega mdoc(7) update:
* Introduce a .Dx macro, for meaning `DragonFly'.
* Use the .Dx macro where we mean `DragonFly' and
revert to using .Fx where we mean `FreeBSD'.
* Update various sentences, paragraphs to be in
context with DragonFly, and mention FreeBSD as
required in HISTORY sections.
* Fix mdoc(7) markup wherever possible.
* Use .Fx wherever possible, and minimize the use
of FreeBSD in favour of .Fx. Do the same for
`OpenBSD' and `NetBSD' by using `.Ox' and `.Nx'
respectively.
* Correct a confusion of `FreeBSD' is `DragonFly'
left by a previous commit to some of the manual
pages, by using the appropriate .Dx/.Fx entities.
NOTE: contrib/ and other manual pages such as sysintall(8)
manual pages are left untouched, because the former should
not be modified directly and the latter has reached
'End of Life' stage.
Submitted by:
Aaron Malone <aaron@munge.net>, Hiten Pandya <hmp@backplane.com>

Add the -f option to the rpc.umntall call to reduce boot-time stalls when
remote servers are unreachable. Add a new rc.conf variable,
rpc_umntall_enable, which defaults to "YES", which may be used to disable
boot-time rpc.umntall operation entirely.
rpc.umntall has caused me headaches ever since it was introduced in FreeBSD
because it could stall a system boot by 60+ seconds per unreachable remote
server in /var/db/mounttab. This should solve the problem both by reducing
the per-entry stall to around 4-6 seconds, and providing a method by which
the boot-time execution fo the program can be disabled.