Mention the Linux compatibility layer instead of the Linux emulator in the BUGS section.

linux(4) explicitly states that it is not an emulator.

While here, pet mandoc and igor.

Reviewed by:	mat (mentor), rpokala
Approved by:	manpages (rpokala), mat (mentor)
Differential Revision:	https://reviews.freebsd.org/D16375
This commit is contained in:
Mateusz Piotrowski 2018-07-21 19:09:29 +00:00
parent b89ff96c7d
commit 56218bf79d
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=336584

View File

@ -24,7 +24,7 @@
.\"
.\" $FreeBSD$
.\"
.Dd December 30, 1999
.Dd July 21, 2018
.Dt SYSCTL.CONF 5
.Os
.Sh NAME
@ -37,9 +37,9 @@ file is read in when the system goes into multi-user mode to set default
settings for the kernel.
The
.Pa /etc/sysctl.conf
is in the format of the
file is in the format of the
.Xr sysctl 8
command, i.e.\&
command, i.e.,
.Bd -literal -offset indent
sysctl_mib=value
.Ed
@ -62,7 +62,7 @@ To turn off logging of programs that exit due to fatal signals you may use
a configuration like
.Bd -literal -offset indent
# Configure logging.
kern.logsigexit=0 # Do not log fatal signal exits (e.g. sig 11)
kern.logsigexit=0 # Do not log fatal signal exits (e.g., sig 11)
.Ed
.Sh SEE ALSO
.Xr rc.conf 5 ,
@ -78,7 +78,11 @@ If loadable kernel modules are used to introduce additional kernel
functionality and sysctls to manage that functionality,
.Nm
may be processed too early in the boot process to set those sysctls.
For example, sysctls to manage the linux emulator cannot be set in
For example, sysctls to manage the Linux compatibility layer
.Po
.Xr linux 4
.Pc
cannot be set in
.Nm
if the linux emulator is loaded as a module rather than
if the Linux compatibility layer is loaded as a module rather than
compiled into the kernel.