More 3.X removals.

This concludes the easy and obvious 3.X removals.  What's left
requires something resembling conscious thought, and perhaps even
actual decision-making.
This commit is contained in:
Michael Lucas 2005-05-12 01:46:37 +00:00
parent 3fdd461ddc
commit b1c0d85564
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=24528

View file

@ -4412,8 +4412,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</listitem>
<listitem>
<para>Static and dynamic ELF libraries (for use with
FreeBSD 3.0 and above).</para>
<para>Static and dynamic ELF libraries.</para>
</listitem>
<listitem>
@ -5126,8 +5125,8 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<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 if you
running a FreeBSD 3.0 or later system, there will be little
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>
@ -5150,7 +5149,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
</listitem>
</itemizedlist>
<para>Both of the above situations will cause your kernel to
<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
@ -6522,9 +6521,9 @@ perm /dev/acd0 0660</programlisting>
<answer>
<para>Yes, FreeBSD supports System V-style IPC, including
shared memory, messages and semaphores. Versions of
FreeBSD later than 3.2 support System V IPC in the GENERIC
kernel. In earlier versions of FreeBSD, enable this
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>
@ -6575,8 +6574,8 @@ options SYSVMSG # enable for messaging</programlisting>
</question><answer>
<para>Do not panic! Restart the system, type
<userinput>boot -s</userinput> at the Boot: prompt (just
<userinput>-s</userinput> for FreeBSD releases before 3.2) to
<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
@ -6817,10 +6816,10 @@ options SYSVMSG # enable for messaging</programlisting>
<para>Long answer: FreeBSD derives its releases from one of
two places. Major, dot-zero, releases, such as
3.0-RELEASE and 4.0-RELEASE, are branched from the head of
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 3.1-RELEASE or 4.2-RELEASE, have been snapshots of the active
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
@ -7453,14 +7452,14 @@ EndSection</programlisting>
session, do <keycombo
action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>.</para>
<para>The default FreeBSD installation has three virtual
consoles enabled (8 starting with 3.3-RELEASE), and
<para>The default FreeBSD installation has eight virtual
consoles enabled.
<keycombo
action="simul"><keycap>Alt</keycap><keycap>F1</keycap></keycombo>,
<keycombo
action="simul"><keycap>Alt</keycap><keycap>F2</keycap></keycombo>,
and <keycombo
action="simul"><keycap>Alt</keycap><keycap>F3</keycap></keycombo>
<keycombo
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
@ -8872,8 +8871,8 @@ Key F15 A A Menu Workplace Nop</programlisting>
</question>
<answer>
<para>FreeBSD 3.0 and later use a version of BIND
that uses a random high-numbered port for outgoing queries. If
<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