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

Whitespace fixes from last commit.

Browse source 
No content changes.
This commit is contained in:
Michael Lucas 2005-05-12 01:51:30 +00:00
parent b1c0d85564
commit aba0df54e0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=24529
1 changed files with 36 additions and 38 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

74
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -5124,12 +5124,11 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<answer>
<para>Chances are, you compiled your kernel in
<emphasis>debug mode</emphasis>. Kernels built in debug
mode contain many symbols that are used for debugging, thus
greatly increasing the size of the kernel. Note that
there will be little
or no performance decrease from running a debug kernel,
and it is useful to keep one around in case of a system
panic.</para>
mode contain many symbols that are used for debugging,
thus greatly increasing the size of the kernel. Note that
there will be little or no performance decrease from
running a debug kernel, and it is useful to keep one
around in case of a system panic.</para>
<para>However, if you are running low on disk space, or
you simply do not want to run a debug kernel, make sure
@ -5150,10 +5149,11 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</itemizedlist>
<para>Either of the above settings will cause your kernel to
be built in debug mode. As long as you make sure you follow
the steps above, you can build your kernel normally, and you
should notice a fairly large size decrease; most kernels
tend to be around 1.5MB to 2MB.</para>
be built in debug mode. As long as you make sure you
follow the steps above, you can build your kernel
normally, and you should notice a fairly large size
decrease; most kernels tend to be around 1.5MB to
2MB.</para>
</answer>
</qandaentry>
@ -6521,11 +6521,9 @@ perm /dev/acd0 0660</programlisting>
<answer>
<para>Yes, FreeBSD supports System V-style IPC, including
shared memory, messages and semaphores,
in the GENERIC
kernel. In a custom kernel, enable this
support by adding the following lines to your kernel
config.</para>
shared memory, messages and semaphores, in the GENERIC
kernel. In a custom kernel, enable this support by adding
the following lines to your kernel config.</para>
<programlisting>options SYSVSHM # enable shared memory
options SYSVSEM # enable for semaphores
@ -6574,15 +6572,15 @@ options SYSVMSG # enable for messaging</programlisting>
</question><answer>
<para>Do not panic! Restart the system, type
<userinput>boot -s</userinput> at the Boot: prompt
to
enter Single User mode. At the question about the shell to use,
hit ENTER. You will be dropped to a &prompt.root; prompt. Enter
<command>mount -u /</command> to remount your root filesystem
read/write, then run <command>mount -a</command> to remount all
the filesystems. Run <command>passwd root</command> to change
the <username>root</username> password then run &man.exit.1; to
continue booting.</para>
<userinput>boot -s</userinput> at the Boot: prompt to
enter Single User mode. At the question about the shell to
use, hit ENTER. You will be dropped to a &prompt.root;
prompt. Enter <command>mount -u /</command> to remount
your root filesystem read/write, then run <command>mount
-a</command> to remount all the filesystems. Run
<command>passwd root</command> to change the
<username>root</username> password then run &man.exit.1;
to continue booting.</para>
</answer>
</qandaentry>
@ -6819,11 +6817,12 @@ options SYSVMSG # enable for messaging</programlisting>
4.0-RELEASE and 5.0-RELEASE, are branched from the head of
the development stream, commonly referred to as <link
linkend="current">-CURRENT</link>. Minor releases, such
as 4.1-RELEASE or 5.2-RELEASE, have been snapshots of the active
<link linkend="stable">-STABLE</link> branch. Starting with
4.3-RELEASE, each release also now has its own branch which can be
tracked by people requiring an extremely conservative rate
of development (typically only security advisories).</para>
as 4.1-RELEASE or 5.2-RELEASE, have been snapshots of the
active <link linkend="stable">-STABLE</link> branch.
Starting with 4.3-RELEASE, each release also now has its
own branch which can be tracked by people requiring an
extremely conservative rate of development (typically only
security advisories).</para>
<para>When a release is about to be made, the branch from
which it will be derived from has to undergo a certain
@ -7453,14 +7452,14 @@ EndSection</programlisting>
action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>.</para>
<para>The default FreeBSD installation has eight virtual
consoles enabled.
<keycombo
consoles enabled. <keycombo
action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>,
<keycombo
action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo>,
<keycombo
action="simul"><keycap>Alt</keycap><keycap>F3</keycap></keycombo>, and so on
will switch between these virtual consoles.</para>
action="simul"><keycap>Alt</keycap><keycap>F3</keycap></keycombo>,
and so on will switch between these virtual
consoles.</para>
<para>To enable more of them, edit
<filename>/etc/ttys</filename> (see &man.ttys.5;)
@ -8871,11 +8870,10 @@ Key F15 A A Menu Workplace Nop</programlisting>
</question>
<answer>
<para>BIND
uses a random high-numbered port for outgoing queries. If
you want to use port 53 for outgoing queries, either to get
past a firewall or to make yourself feel better, you can try
the following in
<para>BIND uses a random high-numbered port for outgoing
queries. If you want to use port 53 for outgoing queries,
either to get past a firewall or to make yourself feel
better, you can try the following in
<filename>/etc/namedb/named.conf</filename>:</para>
<programlisting>options {