os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

More rewording around "you".

Browse source 
Sponsored by:	iXsystems
This commit is contained in:
Dru Lavigne 2014-05-14 15:52:23 +00:00
parent dd63eee42f
commit 3a80919159
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=44831
1 changed files with 89 additions and 148 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

237
en_US.ISO8859-1/books/faq/book.xml
View file

@ -3262,7 +3262,7 @@ kern.sched.name: ULE</screen>
</question>
<answer>
<para>Install LILO at the start of your &linux; boot
<para>Install LILO at the start of the &linux; boot
partition instead of in the Master Boot Record. You can
then boot LILO from
<application>BootEasy</application>.</para>
@ -3889,7 +3889,7 @@ kern.sched.name: ULE</screen>
-a -t ufs</command> to mount the file system where your
favorite editor is defined. If that editor is on
a network file system, either configure
the network manually before you mounting the network file
the network manually before mounting the network file
systems, or use an editor which resides on a local file
system, such as &man.ed.1;.</para>
@ -4343,7 +4343,7 @@ options SYSVMSG # enable for messaging</programlisting>
<para><literal>vnlru</literal> flushes and frees vnodes when
the system hits the <varname>kern.maxvnodes</varname>
limit. This kernel thread sits mostly idle, and only
activates if you have a huge amount of RAM and are
activates when there is a huge amount of RAM and users are
accessing tens of thousands of tiny files.</para>
</answer>
</qandaentry>
@ -4443,8 +4443,7 @@ options SYSVMSG # enable for messaging</programlisting>
<qandaentry>
<question xml:id="var-empty">
<para>What is <filename>/var/empty</filename>? I can not
delete it!</para>
<para>What is <filename>/var/empty</filename>?</para>
</question>
<answer>
@ -4453,14 +4452,8 @@ options SYSVMSG # enable for messaging</programlisting>
separation. The <filename>/var/empty</filename>
directory is empty, owned by <systemitem
class="username">root</systemitem> and has the
<literal>schg</literal> flag set.</para>
<para>Although it is not recommended to delete this
directory, to do so you will need to unset the
<literal>schg</literal> flag first. See the
&man.chflags.1; manual page for more information (and bear
in mind the answer to <link linkend="unsetting-schg">the
question on unsetting the schg flag</link>).</para>
<literal>schg</literal> flag set. This directory should
not be deleted.</para>
</answer>
</qandaentry>
@ -4472,7 +4465,7 @@ options SYSVMSG # enable for messaging</programlisting>
</question>
<answer>
<para>To see what &man.newsyslog.8; will do use the
<para>To see what &man.newsyslog.8; will do, use the
following:</para>
<screen>&prompt.user; <userinput>newsyslog -nrvv</userinput></screen>
@ -4509,8 +4502,8 @@ options SYSVMSG # enable for messaging</programlisting>
Foundation</link> administers the <link
xlink:href="http://en.wikipedia.org/wiki/X_Window_System_core_protocol">X
protocol standards</link>, with the current reference
implementation, version 11 release &xorg.version;, so you
will often see references shortened to
implementation, version 11 release &xorg.version;, so
references are often shortened to
<literal>X11</literal>.</para>
<para>Many implementations are available for different
@ -4560,7 +4553,7 @@ options SYSVMSG # enable for messaging</programlisting>
</question>
<answer>
<para>Your system is probably running at a raised
<para>The system is probably running at a raised
<literal>securelevel</literal>. It is not possible to
start X at a raised <literal>securelevel</literal> because
X requires write access to &man.io.4;. For more
@ -4582,20 +4575,20 @@ options SYSVMSG # enable for messaging</programlisting>
</question>
<answer>
<para>If you are using &man.syscons.4; (the default console
driver), you can configure &os; to support a mouse pointer
<para>When using &man.syscons.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
<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 your
&man.sysmouse.4; device via &man.moused.8;. To use the
mouse on one or more virtual consoles,
<emphasis>and</emphasis> use X, see <xref
linkend="moused" remap="another section"/> and set up
&man.moused.8;.</para>
<para>Then edit <filename>/etc/X11/xorg.conf</filename> and
make sure you have the following lines:</para>
make sure the following lines exist:</para>
<programlisting>Section "InputDevice"
Option "Protocol" "SysMouse"
@ -4635,19 +4628,12 @@ options SYSVMSG # enable for messaging</programlisting>
</question>
<answer>
<para>Yes.</para>
<para>You need to tell X that you have a 5 button mouse. To
<para>Yes, if you configure X for a 5 button mouse. To
do this, add the lines <literal>Buttons 5</literal>
and <literal>ZAxisMapping 4 5</literal> to the
<quote>InputDevice</quote> section of
<filename>/etc/X11/xorg.conf</filename>. For example, you
might have the following <quote>InputDevice</quote>
section in <filename>/etc/X11/xorg.conf</filename>.</para>
<example>
<title><quote>InputDevice</quote> Section for Wheeled
Mouse in &xorg; Configuration File</title>
<filename>/etc/X11/xorg.conf</filename>, as seen in this
example:</para>
<programlisting>Section "InputDevice"
Identifier "Mouse1"
@ -4657,16 +4643,14 @@ options SYSVMSG # enable for messaging</programlisting>
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
EndSection</programlisting>
</example>
<example>
<title><quote>.emacs</quote> Example for Naive Page
Scrolling with Wheeled Mouse (optional)</title>
<para>To use the mouse in
<application>Emacs</application>, also add the following
lines to<filename>~/.emacs</filename>:</para>
<programlisting>;; wheel mouse
(global-set-key [mouse-4] 'scroll-down)
(global-set-key [mouse-5] 'scroll-up)</programlisting>
</example>
</answer>
</qandaentry>
@ -4677,23 +4661,20 @@ EndSection</programlisting>
</question>
<answer>
<para>Yes, you will have to configure a few things to make
<para>Yes, after configuring a few things to make
it work.</para>
<para>If you plan to use the Xorg synaptics driver you
<emphasis>must</emphasis> remove moused_enable from
<filename>rc.conf</filename>. Xorg can not use the
synaptics mouse if the moused already sits on
<filename>/dev/psm0</filename>.</para>
<para>In order to use the Xorg synaptics driver,
first remove <literal>moused_enable</literal> from
<filename>rc.conf</filename>.</para>
<para>To enable synaptics in the &man.psm.4; driver you need
to add the following into
<para>To enable synaptics, add the following line to
<filename>/boot/loader.conf</filename>:</para>
<programlisting>hw.psm.synaptics_support="1"</programlisting>
<para>You also need the following into
<filename>xorg.conf</filename>:</para>
<para>Add the following to
<filename>/etc/X11/xorg.conf</filename>:</para>
<programlisting>Section "InputDevice"
Identifier "Touchpad0"
@ -4733,27 +4714,26 @@ EndSection</programlisting>
</question>
<answer>
<para>Virtual consoles enable you to have
<para>Virtual consoles provide
several simultaneous sessions on the same machine without
doing anything complicated like setting up a network or
running X.</para>
<para>When the system starts, it will display a login prompt
on the monitor after displaying all the boot messages.
You can then type in your login name and password and
start working (or playing!) on the first virtual
Type in your login name and password to
start working on the first virtual
console.</para>
<para>At some point, you will probably wish to start another
<para>To start another
session, perhaps to look at documentation for a program
you are running or to read your mail while waiting for an
FTP transfer to finish. Just do <keycombo
action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo>
(hold down <keycap>Alt</keycap> and press
<keycap>F2</keycap>), and you will find a login prompt
waiting for you on the second <quote>virtual
console</quote>! When you want to go back to the
original session, do <keycombo
or to read mail while waiting for an
FTP transfer to finish,
hold down <keycap>Alt</keycap> and press
<keycap>F2</keycap>. This will display the login prompt
for the second virtual
console. To go back to the
original session, press <keycombo
action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>.</para>
<para>The default &os; installation has eight virtual
@ -4766,10 +4746,10 @@ EndSection</programlisting>
and so on will switch between these virtual
consoles.</para>
<para>To enable more of them, edit
<para>To enable more of virtual consoles, edit
<filename>/etc/ttys</filename> (see &man.ttys.5;) and add
entries for <filename>ttyv8</filename> to
<filename>ttyvc</filename> after the comment on
<filename>ttyvc</filename>, after the comment on
<quote>Virtual terminals</quote>:</para>
<programlisting># Edit the existing entry for ttyv8 in /etc/ttys and change
@ -4779,63 +4759,34 @@ ttyv9 "/usr/libexec/getty Pc" xterm on secure
ttyva "/usr/libexec/getty Pc" xterm on secure
ttyvb "/usr/libexec/getty Pc" xterm on secure</programlisting>
<para>Use as many or as few as you want. The more virtual
terminals you have, the more resources that are used; this
can be important if you have 8&nbsp;MB RAM or less. You
may also want to change the <literal>secure</literal> to
<para>The more virtual
terminals, the more resources that are used. This can be
problematic on systems with 8&nbsp;MB RAM or less. Consider
changing <literal>secure</literal> to
<literal>insecure</literal>.</para>
<note>
<para>Versions of &os; prior to 9.0 used the <quote>
cons25</quote> terminal type, and not <quote>
xterm</quote>. Existing entries in
<filename>/etc/ttys</filename> can be used on which to
base new additions.</para>
xterm</quote>. Use the format of existing entries in
when adding entries to <filename>/etc/ttys</filename>.</para>
</note>
<important>
<para>If you want to run an X server you
<emphasis>must</emphasis> leave at least one virtual
terminal unused (or turned off) for it to use. That is
to say that if you want to have a login prompt pop up
for all twelve of your Alt-function keys, you are out of
luck &mdash; you can only do this for eleven of them if
you also want to run an X server on the same
machine.</para>
<para>In order to run an X server, at least one virtual
terminal must be left to <literal>off</literal> for it to use. This
means that only eleven of the Alt-function keys can be
used as virtual consoles so that one is left for the
X server.</para>
</important>
<para>The easiest way to disable a console is by turning it
off. For example, if you had the full 12 terminal
allocation mentioned above and you wanted to run X, you
would change settings for virtual terminal 12 from:</para>
<programlisting>ttyvb "/usr/libexec/getty Pc" xterm on secure</programlisting>
<para>to:</para>
<para>For example, to run X and eleven virtual consoles, the
setting for virtual terminal 12 should be:</para>
<programlisting>ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<para>If your keyboard has only ten function keys, you would
end up with:</para>
<programlisting>ttyv9 "/usr/libexec/getty Pc" xterm off secure
ttyva "/usr/libexec/getty Pc" xterm off secure
ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<para>(You could also just delete these lines.)</para>
<para>Next, the easiest (and cleanest) way to activate the
virtual consoles is to reboot. However, if you really do
not want to reboot, you can just shut down the X Window
system and execute (as <systemitem
class="username">root</systemitem>):</para>
<screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
<para>It is imperative that you completely shut down X
Window if it is running, before running this command. If
you do not, your system will probably appear to hang or
lock up after executing <command>kill</command>.</para>
<para>The easiest way to activate the
virtual consoles is to reboot.</para>
</answer>
</qandaentry>
@ -4851,20 +4802,19 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F1</keycap></keycombo>
would return you to the first virtual console.</para>
<para>Once you are back to a text console, you can then use
<para>Once at a text console, use
<keycombo
action="simul"><keycap>Alt</keycap><keycap>F<replaceable>n</replaceable></keycap></keycombo>
as normal to move between them.</para>
to move between them.</para>
<para>To return to the X session, you must switch to the
virtual console running X. If you invoked X from the
command line, (e.g., using <command>startx</command>) then
<para>To return to the X session, switch to the
virtual console running X. If X was started from the
command line using <command>startx</command>,
the X session will attach to the next unused virtual
console, not the text console from which it was invoked.
If you have eight active virtual terminals then X will be
running on the ninth, and you would use <keycombo
action="simul"><keycap>Alt</keycap><keycap>F9</keycap></keycombo>
to return.</para>
For eight active virtual terminals, X will
run on the ninth, so use <keycombo
action="simul"><keycap>Alt</keycap><keycap>F9</keycap></keycombo>.</para>
</answer>
</qandaentry>
@ -4903,12 +4853,12 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
this is to have the script sleep 10 seconds or so then
launch <command>xdm</command>.</para>
<para>If you are to start <command>xdm</command> from
<para>When starting <command>xdm</command> from
<filename>/etc/ttys</filename>, there still is a chance of
conflict between <command>xdm</command> and &man.getty.8;.
One way to avoid this is to add the <literal>vt</literal>
number in
<filename>/usr/local/lib/X11/xdm/Xservers</filename></para>
<filename>/usr/local/lib/X11/xdm/Xservers</filename>:</para>
<programlisting>:0 local /usr/local/bin/X vt4</programlisting>
@ -4927,7 +4877,7 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
</question>
<answer>
<para>If you start <application>X</application> with
<para>When <application>X</application> is started with
<command>startx</command>, the permissions on
<filename>/dev/console</filename> will
<emphasis>not</emphasis> get changed, resulting in things
@ -4959,18 +4909,12 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
</question>
<answer>
<para>Your mouse and the mouse driver may have somewhat
become out of synchronization.</para>
<para> In rare cases the driver may erroneously report
synchronization problem and you may see the kernel
message:</para>
<para>The mouse and the mouse driver may have
become out of synchronization. In rare cases, the driver may also erroneously report
synchronization errors:</para>
<programlisting>psmintr: out of sync (xxxx != yyyy)</programlisting>
<para>and notice that your mouse does not work
properly.</para>
<para>If this happens, disable the synchronization check
code by setting the driver flags for the PS/2 mouse driver
to <literal>0x100</literal>. This can be easiest achieved
@ -4986,11 +4930,10 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
</question>
<answer>
<para>Run the command
<command>xmodmap -e "pointer = 3 2 1"</command>.</para>
<para>You add the above command to
<filename>.xinitrc</filename> or
<filename>.xsession</filename> to make it happen
<para>Type
<command>xmodmap -e "pointer = 3 2 1"</command>. Add this command to
<filename>~/.xinitrc</filename> or
<filename>~/.xsession</filename> to make it happen
automatically.</para>
</answer>
</qandaentry>
@ -5017,11 +4960,11 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
</question>
<answer>
<para>Yes. All you need to do is use &man.xmodmap.1; to
define what function you wish them to perform.</para>
<para>Yes. Use &man.xmodmap.1; to
define which functions the keys should perform.</para>
<para>Assuming all <quote>Windows</quote> keyboards are
standard then the keycodes for these three keys are the
<para>Assuming all Windows keyboards are
standard, the keycodes for these three keys are the
following:</para>
<itemizedlist>
@ -5051,7 +4994,7 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<screen>&prompt.root; <userinput>xmodmap -e "keycode 115 = comma"</userinput></screen>
<para>To have the <keycap>Windows</keycap> key-mappings
enabled automatically every time you start X either put
enabled automatically every time X is started, either put
the <command>xmodmap</command> commands in
<filename>~/.xinitrc</filename> or, preferably, create
a <filename>~/.xmodmaprc</filename> and include the
@ -5061,31 +5004,29 @@ ttyvb "/usr/libexec/getty Pc" xterm off secure</programlisting>
<programlisting>xmodmap $HOME/.xmodmaprc</programlisting>
<para>For example, you could map the 3 keys to be
<para>For example, to map the 3 keys to be
<keycap>F13</keycap>, <keycap>F14</keycap>, and
<keycap>F15</keycap>, respectively. This would make it
easy to map them to useful functions within applications
or your window manager, as demonstrated further
down.</para>
or the window manager.</para>
<para>To do this put the following in
<para>To do this, put the following in
<filename>~/.xmodmaprc</filename>.</para>
<programlisting>keycode 115 = F13
keycode 116 = F14
keycode 117 = F15</programlisting>
<para>If you use the <package>x11-wm/fvwm2</package> port,
for example, you could map the keys so that
<keycap>F13</keycap> iconifies (or de-iconifies) the
<para>For the <package>x11-wm/fvwm2</package> desktop manager,
one could map the keys so that
<keycap>F13</keycap> iconifies or de-iconifies the
window the cursor is in, <keycap>F14</keycap> brings the
window the cursor is in to the front or, if it is already
at the front, pushes it to the back, and
<keycap>F15</keycap> pops up the main Workplace
(application) menu even if the cursor is not on the
desktop, which is useful if you do not have any part of
the desktop visible (and the logo on the key matches its
functionality).</para>
menu even if the cursor is not on the
desktop, which is useful when no part of
the desktop is visible.</para>
<para>The following entries in
<filename>~/.fvwmrc</filename> implement the
@ -5105,8 +5046,8 @@ Key F15 A A Menu Workplace Nop</programlisting>
<answer>
<para>The availability of 3D acceleration depends on the
version of &xorg; that you are using and the type of video
chip you have. If you have an nVidia chip, you can use
version of &xorg; and the type of video
chip. For an nVidia chip, use
the binary drivers provided for &os; by installing one of
the following ports:</para>