text and, as a result, 'FreeBSD' is not visible in apropos output
when security(7) is displayed. Fix this buglet by using a
literal 'FreeBSD' string in .Nd
PR: docs/85986
Submitted by: Matthias Schmidt <schmidtm@mathematik.uni-marburg.de>
MFC after: 1 week
list of Atheros-based cards from ath(4). The online list is
always more up to date, anyway.
This invalidates:
PR: docs/95360
Submitted by: Erik Nordstr:om Andersen <erik@erik-n-andersen.dk>
seperately. Also use pfil hook/unhook instead of keeping the check
functions in pfil just to return there based on the sysctl. While here fix
some whitespace on a nearby SYSCTL_ macro.
When porting FreeBSD to a new platform, one of the more useful things to do is
get mi_startup() to let you know which SYSINIT it's up to. Most people tend to
whack a printf in the SYSINIT loop to print the address of the function it's
about to call. Going one better, jhb made a version that uses DDB to look up
the name of the function and print that instead. This version is essentially
his with the addition of some ifdeffery to make it optional and to allow it to
work (although using only the function address, not the symbol) if you forgot
to enable DDB.
All the cool bits by: jhb
Approved by: scottl, rink, cognet, imp
in HEAD's release notes, even though the issues involved were applied
(and fixed). Copy their descriptions from one of the RELENG_*
branches (RELENG_5 in this case).
SA-06:08 and SA-06:09 were not applicable to code on HEAD and thus not
mentioned.
Remove an unnecessary check of the table's bus clock. CPUs that
support this feature export only the high/low settings via the MSR,
packed into 32 bits.
Hardware from: Centaur Technologies
MFC after: 1 week
to device hints was committed. The GENERIC kernel configuration lost
its 'device fd' line at revision 1.260, committed by peter@ on
2000/06/13 22:28:46 UTC.
Delete the reference to 'device fd', to avoid kernel build breakage like
the one described in the PR audit trail.
PR: docs/91448
Submitted by: Eugene Grosbein <eugen@grosbein.pp.ru>
MFC after: 1 week
issue where some global jail_* variables were overriden in the script. [1]
- Change "jid" to "jname" in rc.conf(5), since it's more a jail name than a
jail id. [1]
- Update examples and comments in defaults/rc.conf to advertise new
variables and the fact that some of the jail-specific variables may be made
jail-global. [2]
Reported by: pjd [1], clsung [2]
Approved by: cperciva
X-MFC after: i got sufficient testing from people using rc.d/jail
to a host behind a firewall where only specific services are allowed.
For example, to trace the hops to an HTTP server behind a firewall,
$ traceroute -e -P tcp -p 80 www-firewalled.example.com
MFC after: 1 week
Updates to historic rules only for: part of Alaska, Algeria, Bulgaria,
Colombia, Easter Island, Italy, Malta, Mexico, Mongolia, Montserrat,
Puerto Rico, Poland, Russia, South Korea, Spain, part of North Dakota,
United Kingdom, Uruguay, Uzbekistan
Updates to current and future rules for: Guatemala, Haiti, Honduras,
part of Indiana, Iran, Nicaragua, Palestinian Territories, Sri Lanka,
Tunisia,
Updates to future rules only for: Canada, Thule AFB in Greenland
"sweeping" ping(8), sh(1) built-in times.
I uncovered these in a sweep of items that need to be merged to
the 5.4 release notes. It's possible that all of these items
should have been in the 6.1 release notes (not confirmed).
particular importance to those living in the Western Hemisphere as
many non-U.S. zones will be changing DST rules next year to match the
U.S.
Obtained from: Arthur David Olson, ftp://elsie.nci.nih.gov/
