Remove 2.1 and 2.2 cruft from mouse questions, and rewrite answers to
be more readable now that the cruft is gone.
This commit is contained in:
parent
9574d9fae8
commit
d2f5cf5b1f
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=16496
1 changed files with 28 additions and 47 deletions
|
@ -2620,60 +2620,41 @@ usbd_flags=""</programlisting>
|
|||
|
||||
<qandaentry>
|
||||
<question id="moused">
|
||||
<para>Is it possible to make use of a mouse in any way outside
|
||||
<para>Is it possible to use a mouse in any way outside
|
||||
the X Window system?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>If you are using the default console driver, syscons, you
|
||||
<para>If you are using the default console driver, &man.syscons.4;, you
|
||||
can use a mouse pointer in text consoles to cut & paste
|
||||
text. Run the mouse daemon, moused, and turn on the mouse
|
||||
text. Run the mouse daemon, &man.moused.8;, and turn on the mouse
|
||||
pointer in the virtual console:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>moused -p /dev/<replaceable>xxxx</replaceable> -t <replaceable>yyyy</replaceable></userinput>
|
||||
&prompt.root; <userinput>vidcontrol -m on</userinput></screen>
|
||||
|
||||
<para>Where <replaceable>xxxx</replaceable> is the mouse device
|
||||
name and <replaceable>yyyy</replaceable> is a protocol type for
|
||||
the mouse. See the &man.moused.8; manual page for supported
|
||||
<para>Where <replaceable>xxxx</replaceable> is the mouse
|
||||
device name and <replaceable>yyyy</replaceable> is a
|
||||
protocol type for the mouse. The mouse daemon can
|
||||
automatically determine the protocol type of most
|
||||
mice, except old serial mice. Specify the
|
||||
<literal>auto</literal> protocol to invoke automatic
|
||||
detection. If automatic detection does not work, see the
|
||||
&man.moused.8; manual page for a list of supported
|
||||
protocol types.</para>
|
||||
|
||||
<para>You may wish to run the mouse daemon automatically when the
|
||||
system starts. In version 2.2.1, set the following variables in
|
||||
<filename>/etc/sysconfig</filename>.</para>
|
||||
|
||||
<programlisting>mousedtype="yyyy"
|
||||
mousedport="xxxx"
|
||||
mousedflags=""</programlisting>
|
||||
|
||||
<para>In versions 2.2.2 to 3.0, set the following variables in
|
||||
<para>If you have a PS/2 mouse, just
|
||||
add <literal>moused_enable="YES"</literal> to
|
||||
<filename>/etc/rc.conf</filename> to start the mouse daemon at boot-time.
|
||||
Additionally, if you would like to use the mouse
|
||||
daemon on all virtual terminals instead of just the console,
|
||||
add <literal>allscreens_flags="-m on"</literal> to
|
||||
<filename>/etc/rc.conf</filename>.</para>
|
||||
|
||||
<programlisting>moused_type="yyyy"
|
||||
moused_port="xxxx"
|
||||
moused_flags=""</programlisting>
|
||||
|
||||
<para>In 3.1 and later, assuming you have a PS/2 mouse, all you
|
||||
need to is add <literal>moused_enable="YES"</literal> to
|
||||
<filename>/etc/rc.conf</filename>.</para>
|
||||
|
||||
<para>In addition, if you would like to be able to use the mouse
|
||||
daemon on all virtual terminals instead of just console at
|
||||
boot-time, add the following to
|
||||
<filename>/etc/rc.conf</filename>.</para>
|
||||
|
||||
<programlisting>allscreens_flags="-m on"</programlisting>
|
||||
|
||||
<para>Starting from FreeBSD 2.2.6, the mouse daemon is capable of
|
||||
determining the correct protocol type automatically unless the
|
||||
mouse is a relatively old serial mouse model. Specify
|
||||
<literal>auto</literal> the protocol to invoke automatic
|
||||
detection.</para>
|
||||
|
||||
<para>When the mouse daemon is running, access to the mouse
|
||||
needs to be coordinated between the mouse daemon and other
|
||||
programs such as the X Window. Refer to <link
|
||||
linkend="x-and-moused">another section</link> on this
|
||||
must be coordinated between the mouse daemon and other
|
||||
programs such as X Windows. Refer to the FAQ <link
|
||||
linkend="x-and-moused">Why does my mouse not work with X?</link> for more details on this
|
||||
issue.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
@ -2685,17 +2666,17 @@ moused_flags=""</programlisting>
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Once you get the mouse daemon running (see
|
||||
<para>Once you get the mouse daemon running (see the
|
||||
<link linkend="moused">previous section</link>), hold down the
|
||||
button 1 (left button) and move the mouse to select a region of
|
||||
text. Then, press the button 2 (middle button) or the button 3
|
||||
(right button) to paste it at the text cursor.</para>
|
||||
text. Then, press the button 2 (middle button)
|
||||
to paste it at the text cursor.
|
||||
Pressing button 3 (right button) will
|
||||
<quote>extend</quote> the selected region of text.</para>
|
||||
|
||||
<para>In versions 2.2.6 and later, pressing the button 2 will
|
||||
paste the text. Pressing the button 3 will
|
||||
<quote>extend</quote> the selected region of text. If your
|
||||
mouse does not have the middle button, you may wish to emulate
|
||||
it or remap buttons using moused options. See the
|
||||
<para>If your
|
||||
mouse does not have a middle button, you may wish to emulate
|
||||
one or remap buttons using mouse daemon options. See the
|
||||
&man.moused.8; manual page for details.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
|
Loading…
Reference in a new issue