| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
compiling with NO_NIS.
PR: bin/87221
Reviewed by: simon
MFC after: 4 weeks
|
|
|
|
|
| |
PR: kern/79998
MFC after: 1 month
|
|
|
|
| |
Submitted by: Anders Hanssen <anders@rethink.no>
|
|
|
|
|
| |
- Remove a few items from the HARDWARE list. This support is
already described in the snd_mss(4) manual page.
|
|
|
|
| |
Reviewed by: brueffer
|
|
|
|
| |
Discussed with: glebius
|
|
|
|
| |
- Explain when ALTQ should be used on ng_iface(4) and when not.
|
|
|
|
|
|
|
|
|
| |
where applicable. The main reason for this change is that
the location of make.conf is not constant and can be
modified via __MAKE_CONF. This change also improves
hyper-text linkage in our manpages.
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
Reviewed by: mlaier
|
|
|
|
|
| |
Reviewed by: simokawa, ru (mdoc markup)
MFC after: 1 week
|
|
|
|
|
| |
Spotted by: marius
Discussed with: ru
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove references to cpu_critical_*() as they no longer exist.
- Explain that any preemptions that occur during a critical section are
deferred until the current thread exits the section.
- Remove a bogus example usage of a critical section.
- Note that one can interlock critical sections with spin mutexes in
certain situations.
MFC after: 3 days
|
| |
|
|
|
|
|
|
| |
glue.
Submitted by: David Boggs
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
system boot, and hook it up in the system.
The separate script is needed because in the presence of various
interface lists in rc.conf ($network_interfaces, $cloned_interfaces,
$sppp_interfaces, $gif_interfaces, more to come) it is hard to start
them orderly, so that pfsync is brought up after its syncdev, which
is required for the proper startup of pfsync.
Discussed with: mlaier on -pf
MFC after: 5 days
|
|
|
|
| |
Submitted by: ru
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Remove description of poll in trap feature.
- Tell that polling should be turned on and off with ifconfig.
- Move description of kern.polling.enable to the end and say
that this a deprecated way of turning polling on.
- Remove note that idle poll has some problems in CURRENT. I failed
to find them, while Sam and Luigi failed to remember what the
problem actually were there.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Consistently use 'x86' when referring to behaviour common to the
i386 and amd64.
Submitted by: Niklas Sorensson <nik@cs.chalmers.se> [1]
|
|
|
|
| |
around ${network_interfaces}.
|
|
|
|
| |
if MACHINE_ARCH is defined is no longer needed.
|
| |
|
| |
|
| |
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
replacement and has additional features which make it superior.
Discussed on: -arch
Reviewed by: thompsa
X-MFC-after: never (RELENG_6 as transition period)
|
|
|
|
|
|
|
|
|
| |
- Add arm and ppc to the list of archs not supporting operations on 64-bit
integers.
- Update the sample code for acquiring a mutex to be more recent and to
take into account the recent atomic_foo_ptr() changes.
MFC after: 1 week
|
|
|
|
| |
Sponsored by: TCP/IP Optimization Fundraise 2005
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
so. If the full list of fe(4) options is documented we can revive the
entire section.
PR: docs/86228
Submitted by: n-kogane@syd.odn.ne.jp
Helped by: Masahiro Sekiguchi <seki@jp.fujitsu.com>
MFC after: 1 week
|
|
|
|
|
|
|
| |
Add a VFS_LOCK_GIANT(9)/VFS_UNLOCK_GIANT(9) man page.
Discussed with: jeff
MFC after: 3 days
|
|
|
|
|
|
|
| |
administrator to specify additional start-up flags to the Kerberos
5 Authentication Server.
MFC after: 3 days
|
| |
|
|
|
|
| |
MFC after: 5 days
|
|
|
|
|
|
| |
Make sure that this is clearly stated.
Prodded by: simon, Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
|
|
|
|
|
|
| |
recent changes in a manpage.
Reviewed by: cognet
|
|
|
|
|
|
| |
the supported hardware.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
different from the use of `*' in /etc/passwd.
PR: docs/86234
Submitted by: Paul Hoffman <phoffman@above.proper.com>
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
Reminded by: simon
|
|
|
|
| |
Reviewed by: brueffer
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
shutdown procedures (which have a duration of more than 120 seconds).
We have two user-space affecting shutdown timeouts: a "soft" one in
/etc/rc.shutdown and a "hard" one in init(8). The first one can be
configured via /etc/rc.conf variable "rcshutdown_timeout" and defaults
to 30 seconds. The second one was originally (in 1998) intended to be
configured via sysctl(8) variable "kern.shutdown_timeout" and defaults
to 120 seconds.
Unfortunately, the "kern.shutdown_timeout" was declared "unused" in 1999
(as it obviously is actually not used within the kernel itself) and
hence was intentionally but misleadingly removed in revision 1.107 from
init_main.c. Kernel sysctl(8) variables are certainly a wrong way to
control user-space processes in general, but in this particular case the
sysctl(8) variable should have remained as it supports init(8), which
isn't passed command line flags (which in turn could have been set via
/etc/rc.conf), etc.
As there is already a similar "kern.init_path" sysctl(8) variable which
directly affects init(8), resurrect the init(8) shutdown timeout under
sysctl(8) variable "kern.init_shutdown_timeout". But this time document
it as being intentionally unused within the kernel and used by init(8).
Also document it in the manpages init(8) and rc.conf(5).
Reviewed by: phk
MFC after: 2 weeks
|
|
|
|
| |
Approved by: brueffer (mentor)
|
| |
|
|
|
|
|
|
| |
moment, but better than nothing.
MFC after: 3 days
|