Update FAQ use of "default console driver" to be vt(4), not syscons(4)

PR:		220015
Submitted by:	pauamma_gundo.com
Reported by:	salternate@gmx.com
Reviewed by:	bcr
Approved by:	bcr (mentor)
Differential Revision:	https://reviews.freebsd.org/D22699
This commit is contained in:
Mateusz Piotrowski 2020-02-06 16:52:49 +00:00
parent e60fd6aa0b
commit 718f982e37
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=53871

View file

@ -1592,7 +1592,7 @@
<answer>
<para>The default console driver,
&man.syscons.4;, provides the ability to use a mouse
&man.vt.4;, provides the ability to use a mouse
pointer in text consoles to cut &amp; paste text. Run
the mouse daemon, &man.moused.8;, and turn on the mouse
pointer in the virtual console:</para>
@ -3770,23 +3770,11 @@ options SYSVMSG # enable for messaging</programlisting>
</question>
<answer>
<para>When using &man.syscons.4;, the default console
driver, build and install a new kernel with this line in
the configuration file:</para>
<para>When using &man.vt.4;, the default console
driver, this can be done by setting the following
&man.sysctl.8;:</para>
<programlisting>options SC_DISABLE_REBOOT</programlisting>
<para>This can also be done by setting the following
&man.sysctl.8; which does not require a reboot or kernel
recompile:</para>
<screen>&prompt.root; <userinput>sysctl hw.syscons.kbd_reboot=0</userinput></screen>
<note>
<para>The above two methods are exclusive: The
&man.sysctl.8; does not exist if the kernel is compiled
with <literal>SC_DISABLE_REBOOT</literal>.</para>
</note>
<screen>&prompt.root; <userinput>sysctl kern.vt.kbd_reboot=0</userinput></screen>
</answer>
</qandaentry>
@ -4231,10 +4219,10 @@ options SYSVMSG # enable for messaging</programlisting>
</question>
<answer>
<para>When using &man.syscons.4;, the default console
<para>When using &man.vt.4;, the default console
driver, &os; can be configured to support a mouse pointer
on each virtual screen. To avoid conflicting with X,
&man.syscons.4; supports a virtual device called
&man.vt.4; supports a virtual device called
<filename>/dev/sysmouse</filename>. All mouse events
received from the real mouse device are written to the
&man.sysmouse.4; device via &man.moused.8;. To use the