* Add reference to 3.X in <title> and <abstract>
* -stable -> -STABLE * -current -> -CURRENT * Update 3.0/3.2 entries to 3.3 or 3.X as appropriate * .x -> .X (i.e., 3.x -> 3.X) * Update entries to correspond to new directory structure on ftp site * Removed reference to RELENG_2_ snapshots, which no longer exist * Add reference to allscreens_flags="-m on" for moused * Note that 3.3-RELEASE has 8 virtual terminals by default Submitter sent the original PR, Jim Mock added to it, I cleaned up a couple of bits and pieces. PR: docs/13949 Submitted by: Chris D. Faulhaber <jedgar@fxp.org>, jim
This commit is contained in:
Nik Clayton
parent
d71066fb87
commit
b90ea8b776
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=6066
2 changed files with 156 additions and 138 deletions
|
|
@ -2,7 +2,7 @@
|
|||
<book>
|
||||
|
||||
<bookinfo>
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X</title>
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X and 3.X</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
|
|
@ -10,9 +10,9 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.22 1999/11/12 04:36:42 chris Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.23 1999/11/13 00:25:00 jim Exp $</pubdate>
|
||||
|
||||
<abstract><para> This is the FAQ for FreeBSD systems version 2.X All entries are
|
||||
<abstract><para> This is the FAQ for FreeBSD versions 2.X and 3.X. All entries are
|
||||
assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted.
|
||||
Any entries with a <XXX> are under construction.
|
||||
If you are interested in helping with this project, send
|
||||
|
|
@ -25,7 +25,7 @@
|
|||
<preface id="preface">
|
||||
<title>Preface</title>
|
||||
|
||||
<para>Welcome to the FreeBSD 2.X FAQ!</para>
|
||||
<para>Welcome to the FreeBSD 2.X-3.X FAQ!</para>
|
||||
|
||||
<para>As is usual with Usenet FAQs, this document aims to cover the most
|
||||
frequently asked questions concerning the FreeBSD operating system
|
||||
|
|
@ -122,45 +122,45 @@ really can do whatever you like with it.</para>
|
|||
<qandaentry><question>
|
||||
<para>What is the latest version of FreeBSD?</para></question><answer>
|
||||
|
||||
<para>Version <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/3.2-RELEASE/">3.2</ulink> is the latest <emphasis>stable</emphasis> version; it was released
|
||||
in May, 1999. This is also the latest <emphasis>release</emphasis> version.</para>
|
||||
<para>Version <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/3.3-RELEASE/">3.3</ulink> is the latest <emphasis>stable</emphasis> version; it was released
|
||||
in September, 1999. This is also the latest <emphasis>release</emphasis> version.</para>
|
||||
|
||||
<para>Briefly explained, <emphasis>-stable</emphasis> is aimed at the ISP or other
|
||||
<para>Briefly explained, <emphasis>-STABLE</emphasis> is aimed at the ISP or other
|
||||
corporate user who wants stability and a low change count over
|
||||
the wizzy new features of the latest <emphasis>-current</emphasis> snapshot.
|
||||
the wizzy new features of the latest <emphasis>-CURRENT</emphasis> snapshot.
|
||||
Releases can come from either "branch," but you should only use
|
||||
<emphasis>-current</emphasis> if you're sure that you're prepared for its
|
||||
increased volatility (relative to <emphasis>-stable</emphasis>, that is).</para>
|
||||
<emphasis>-CURRENT</emphasis> if you're sure that you're prepared for its
|
||||
increased volatility (relative to <emphasis>-STABLE</emphasis>, that is).</para>
|
||||
|
||||
<para>Releases are only made <link linkend="release-freq">every few months</link>. While many people stay more up-to-date with the
|
||||
FreeBSD sources (see the questions on <link linkend="current">FreeBSD-current</link> and <link linkend="stable">FreeBSD-stable</link>) than that, doing so is more of a
|
||||
FreeBSD sources (see the questions on <link linkend="current">FreeBSD-CURRENT</link> and <link linkend="stable">FreeBSD-STABLE</link>) than that, doing so is more of a
|
||||
commitment, as the sources are a moving target.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry><question
|
||||
id="current">
|
||||
<para>What is FreeBSD-current?</para></question><answer>
|
||||
<para>What is FreeBSD-CURRENT?</para></question><answer>
|
||||
|
||||
<para><ulink URL="../handbook/cutting-edge.html#CURRENT">FreeBSD-current</ulink> is the
|
||||
<para><ulink URL="../handbook/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink> is the
|
||||
development version of the operating system, which will in due
|
||||
course become 4.0-RELEASE. As such, it is really only of interest
|
||||
to developers working on the system and die-hard hobbyists.
|
||||
See the <ulink URL="../handbook/cutting-edge.html#CURRENT">relevant section</ulink>
|
||||
in the <ulink URL="../handbook/index.html">handbook</ulink> for
|
||||
details on running -current.</para>
|
||||
details on running -CURRENT.</para>
|
||||
|
||||
<para>If you are not familiar with the operating system or are not
|
||||
capable of identifying the difference between a real problem and
|
||||
a temporary problem, you should not use FreeBSD-current. This
|
||||
a temporary problem, you should not use FreeBSD-CURRENT. This
|
||||
branch sometimes evolves quite quickly and can be un-buildable
|
||||
for a number of days at a time. People that use FreeBSD-current
|
||||
for a number of days at a time. People that use FreeBSD-CURRENT
|
||||
are expected to be able to analyze any problems and only report them
|
||||
if they are deemed to be mistakes rather than ``glitches''. Questions
|
||||
such as ``make world produces some error about groups'' on the
|
||||
-current mailing list are sometimes treated with contempt.</para>
|
||||
-CURRENT mailing list are sometimes treated with contempt.</para>
|
||||
|
||||
<para>Every now and again, a <ulink URL="../releases/snapshots.html">snapshot</ulink> release is also made of this -current development
|
||||
<para>Every now and again, a <ulink URL="../releases/snapshots.html">snapshot</ulink> release is also made of this -CURRENT development
|
||||
code, CDROM distributions of the occasional snapshot even now being
|
||||
made available. The goals behind each snapshot release are:</para>
|
||||
|
||||
|
|
@ -173,7 +173,7 @@ made available. The goals behind each snapshot release are:</para>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>To give people who would like to run -current but who don't
|
||||
<para>To give people who would like to run -CURRENT but who don't
|
||||
have the time and/or bandwidth to follow it on a day-to-day
|
||||
basis an easy way of bootstrapping it onto their systems.
|
||||
</para>
|
||||
|
|
@ -199,22 +199,22 @@ greatest possible number of potential testers.</para>
|
|||
and tested mettle, you will have to stick to full releases.</para>
|
||||
|
||||
<para>Snapshot releases are directly available from <ulink URL="ftp://current.FreeBSD.org/pub/FreeBSD/">ftp://current.FreeBSD.org/pub/FreeBSD/</ulink> and are generated,
|
||||
on the average, once a day for both the 4.0-current and 3.0-stable
|
||||
on the average, once a day for both the 4.0-CURRENT and 3.0-STABLE
|
||||
branches.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry><question
|
||||
id="stable">
|
||||
<para>What is the FreeBSD-stable concept?</para></question><answer>
|
||||
<para>What is the FreeBSD-STABLE concept?</para></question><answer>
|
||||
|
||||
<para>Back when FreeBSD 2.0.5 was released, we decided to branch FreeBSD
|
||||
development into two parts. One branch was named <ulink URL="../handbook/stable.html">-stable</ulink>, with the
|
||||
development into two parts. One branch was named <ulink URL="../handbook/stable.html">-STABLE</ulink>, with the
|
||||
intention that only well-tested bug fixes and small incremental
|
||||
enhancements would be made to it (for Internet Service Providers
|
||||
and other commercial enterprises for whom sudden shifts or
|
||||
experimental features are quite undesirable). The other branch was
|
||||
<ulink URL="../handbook/cutting-edge.html#CURRENT">-current</ulink>, which
|
||||
<ulink URL="../handbook/cutting-edge.html#CURRENT">-CURRENT</ulink>, which
|
||||
essentially has been one unbroken line leading towards 4.0-RELEASE
|
||||
(and beyond) since 2.0 was released. If a little ASCII art would
|
||||
help, this is how it looks:</para>
|
||||
|
|
@ -223,12 +223,12 @@ help, this is how it looks:</para>
|
|||
<literallayout> 2.0
|
||||
|
|
||||
|
|
||||
| [2.1-stable]
|
||||
*BRANCH* 2.0.5 -> 2.1 -> 2.1.5 -> 2.1.6 -> 2.1.7.1 [2.1-stable ends]
|
||||
| [2.1-STABLE]
|
||||
*BRANCH* 2.0.5 -> 2.1 -> 2.1.5 -> 2.1.6 -> 2.1.7.1 [2.1-STABLE ends]
|
||||
| (Mar 1997)
|
||||
|
|
||||
|
|
||||
| [2.2-stable]
|
||||
| [2.2-STABLE]
|
||||
*BRANCH* 2.2.1 -> 2.2.2-RELEASE -> 2.2.5 -> 2.2.6 -> 2.2.7 -> 2.2.8 [end]
|
||||
| (Mar 1997) (Oct 97) (Apr 98) (Jul 98) (Dec 98)
|
||||
|
|
||||
|
|
@ -238,19 +238,19 @@ help, this is how it looks:</para>
|
|||
|
|
||||
3.0.0-RELEASE (Oct 1998)
|
||||
|
|
||||
| [3.0-stable]
|
||||
| [3.0-STABLE]
|
||||
*BRANCH* 3.1 (Feb 1999) -> 3.2 -> ... future 3.x releases ...
|
||||
| (May 1999)
|
||||
|
|
||||
\|/
|
||||
+
|
||||
[4.0-current continues]</literallayout>
|
||||
[4.0-CURRENT continues]</literallayout>
|
||||
</para>
|
||||
|
||||
<para>The -current branch is slowly progressing towards 4.0 and beyond,
|
||||
the previous 2.2-stable branch having just retired with the release
|
||||
of 2.2.8. 3.0-stable has now replaced it, the next release coming
|
||||
up with 3.3 in Q3 1999. 4.0-current is now the "current branch",
|
||||
<para>The -CURRENT branch is slowly progressing towards 4.0 and beyond,
|
||||
the previous 2.2-STABLE branch having been retired with the release
|
||||
of 2.2.8. 3.3-STABLE has now replaced it, with 3.3-RELEASE being released
|
||||
in mid-September 1999. 4.0-CURRENT is now the "current branch",
|
||||
with the first 4.0 releases appearing in Q1 2000.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
|
@ -315,14 +315,14 @@ from the <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD FTP site</ulink
|
|||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para>For the current 2.2-stable release, 2.2.8R, see the
|
||||
<ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/2.2.8-RELEASE/">2.2.8-RELEASE</ulink> directory.
|
||||
<para>For the current 2.2-STABLE release, 2.2.8R, see the
|
||||
<ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/2.2.8-RELEASE/">2.2.8-RELEASE</ulink> directory.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>For the current 3.0-stable release, 3.0-RELEASE, see the
|
||||
<ulink URL="ftp://current.FreeBSD.org/pub/FreeBSD/releases/3.0-RELEASE/">3.0-RELEASE</ulink> directory.
|
||||
<para>For the current 3.X-STABLE release, 3.3-RELEASE, see the
|
||||
<ulink URL="ftp://current.FreeBSD.org/pub/FreeBSD/releases/i386/3.3-RELEASE/">3.3-RELEASE</ulink> directory.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -337,15 +337,15 @@ are now made.
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink URL="ftp://releng30.FreeBSD.org/pub/FreeBSD/">3.0 Snapshot</ulink> releases are also made once a day along the
|
||||
RELENG_3 branch (post 3.0-release) as it continues on its way
|
||||
towards 3.2-RELEASE.
|
||||
<para><ulink URL="ftp://releng30.FreeBSD.org/pub/FreeBSD/">3.X Snapshot</ulink> releases are also made once a day along the
|
||||
RELENG_3 branch (post 3.0-RELEASE) as it continues on its way
|
||||
towards 3.4-RELEASE.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink URL="ftp://current.FreeBSD.org/pub/FreeBSD/">4.0 Snapshot</ulink> releases are made once a day for the
|
||||
<link linkend="current">-current</link> branch, these being of service
|
||||
<link linkend="current">-CURRENT</link> branch, these being of service
|
||||
purely to bleeding-edge testers and developers.</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -704,7 +704,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix
|
|||
<listitem>
|
||||
<para>Using ftp mirror: You can download the FTP server's copy of
|
||||
the web site using your favorite ftp mirror tool. Simply start at
|
||||
ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www.</para>
|
||||
ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-CURRENT/www.</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
|
@ -1557,7 +1557,7 @@ filesystems with 4 terabytes are possible (and exist).</para>
|
|||
<literallayout> maxfilesize
|
||||
----------------------------------
|
||||
2.2.7 3.0
|
||||
fs block size -stable -current works should-work
|
||||
fs block size -STABLE -CURRENT works should-work
|
||||
------------- ------- -------- ----- -----------
|
||||
4K 4T-1 4T-1 4T-1 4+T
|
||||
8K 32+G 8T-1 32+G 16T-1
|
||||
|
|
@ -1577,10 +1577,10 @@ unreachable when the fs block size is 4K.</para>
|
|||
|
||||
<para>For block sizes of 8K and larger, everything should be limited
|
||||
by the 2G-1 limit on fs block numbers, but is actually limited by the
|
||||
1G-1 limit on fs block numbers, except under -stable triple indirect
|
||||
1G-1 limit on fs block numbers, except under -STABLE triple indirect
|
||||
blocks are unreachable, so the limit is the maxiumum fs block number
|
||||
that can be represented using double indirect blocks
|
||||
(approx. (blocksize/4)^2 + (blocksize/4)), and under -current
|
||||
(approx. (blocksize/4)^2 + (blocksize/4)), and under -CURRENT
|
||||
exceeding this limit may cause problems. Using the correct limit of
|
||||
2G-1 blocks does cause problems.</para>
|
||||
|
||||
|
|
@ -1859,6 +1859,15 @@ system starts. In version 2.2.1, set the following variables in
|
|||
</literallayout>
|
||||
</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>
|
||||
|
||||
<para>
|
||||
<literallayout> allscreens_flags="-m on"
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
<para>Staring 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 ``<emphasis remap=tt>auto</emphasis>'' as
|
||||
|
|
@ -3014,7 +3023,7 @@ of FreeBSD at the following locations:</para>
|
|||
|
||||
<para>
|
||||
<variablelist>
|
||||
<varlistentry><term>for 2.2.8-release/2.2.8-stable</term>
|
||||
<varlistentry><term>for 2.2.8-RELEASE/2.2.8-STABLE</term>
|
||||
<listitem>
|
||||
<para><ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-2.2.8/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-2.2.8/</ulink></para>
|
||||
|
||||
|
|
@ -3023,7 +3032,7 @@ of FreeBSD at the following locations:</para>
|
|||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry><term>for 3.2-release/3.2-stable</term>
|
||||
<varlistentry><term>for 3.X-RELEASE/3.X-STABLE</term>
|
||||
|
||||
<listitem>
|
||||
<para><ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/</ulink></para>
|
||||
|
|
@ -3033,7 +3042,7 @@ of FreeBSD at the following locations:</para>
|
|||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry><term>for 4.0-current</term>
|
||||
<varlistentry><term>for 4.0-CURRENT</term>
|
||||
|
||||
<listitem>
|
||||
<para><ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-current/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-current/</ulink></para>
|
||||
|
|
@ -3110,7 +3119,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
|
|||
</para>
|
||||
|
||||
<para>You just need socksys to go to <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?null(4)">/dev/null</ulink>
|
||||
to fake the open & close. The code in -current will handle the
|
||||
to fake the open & close. The code in -CURRENT will handle the
|
||||
rest. This is much cleaner than the way it was done before. If you
|
||||
want the <emphasis remap=tt>spx</emphasis> driver for a local socket X connection, define
|
||||
<symbol>SPX_HACK</symbol> when you compile the system.</para>
|
||||
|
|
@ -3142,15 +3151,15 @@ in the ports tree.</para>
|
|||
</answer></qandaentry>
|
||||
|
||||
<qandaentry><question>
|
||||
<para>Why can't I build this port on my 3.x-stable machine?</para></question><answer>
|
||||
<para>Why can't I build this port on my 3.X-STABLE machine?</para></question><answer>
|
||||
|
||||
<para>If you're running a FreeBSD version that lags significantly behind
|
||||
-current or -stable, you may need a ports upgrade kit from
|
||||
-CURRENT or -STABLE, you may need a ports upgrade kit from
|
||||
<ulink URL="http://www.FreeBSD.org/ports/">http://www.FreeBSD.org/ports/</ulink>. If you are up to date, then
|
||||
someone might have committed a change to the port which works for
|
||||
-current but which broke the port for -stable. Please submit a bug
|
||||
-CURRENT but which broke the port for -STABLE. Please submit a bug
|
||||
report on this with the <command>send-pr(1)</command> command, since the ports
|
||||
collection is supposed to work for both the -current and -stable
|
||||
collection is supposed to work for both the -CURRENT and -STABLE
|
||||
branches.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
|
@ -3260,11 +3269,11 @@ write to through a special program to manage it called
|
|||
``<emphasis remap=tt>ft</emphasis>'' - see the man page on <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?ft">ft</ulink>
|
||||
for further details.</para>
|
||||
|
||||
<para>Versions previous to <option>-current</option> also had some trouble dealing
|
||||
<para>Versions previous to <option>-CURRENT</option> also had some trouble dealing
|
||||
with bad tape media; if you have trouble where <emphasis remap=tt>ft</emphasis> seems to
|
||||
go back and forth over the same spot, try grabbing the latest
|
||||
version of <emphasis remap=tt>ft</emphasis> from <filename>/usr/src/sbin/ft</filename> in
|
||||
<option>-current</option> and try that.</para>
|
||||
<option>-CURRENT</option> and try that.</para>
|
||||
|
||||
</answer></qandaentry></qandaset>
|
||||
</chapter>
|
||||
|
|
@ -4711,8 +4720,8 @@ waiting for you on the second ``virtual console''! When you
|
|||
want to go back to the original session, do Alt-F1.</para>
|
||||
|
||||
<para>The default FreeBSD installation has three virtual consoles
|
||||
enabled, and Alt-F1, Alt-F2, and Alt-F3 will switch between
|
||||
these virtual consoles.</para>
|
||||
enabled (8 starting with 3.3-RELEASE), and Alt-F1, Alt-F2, and
|
||||
Alt-F3 will switch between these virtual consoles.</para>
|
||||
|
||||
<para>To enable more of them, edit <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?ttys">/etc/ttys</ulink>
|
||||
and add entries for ``<emphasis remap=tt>ttyv4</emphasis>'' to ``<emphasis remap=tt>ttyvc</emphasis>'' after the
|
||||
|
|
@ -7510,7 +7519,7 @@ back when.</para>
|
|||
|
||||
<para>One thousand, one hundred and seventy-two:</para>
|
||||
|
||||
<para>Twenty-three to complain to -current about the lights being
|
||||
<para>Twenty-three to complain to -CURRENT about the lights being
|
||||
out;</para>
|
||||
|
||||
<para>Four to claim that it is a configuration problem, and that
|
||||
|
|
@ -7533,7 +7542,7 @@ have cvsupped at a bad time;</para>
|
|||
<para>One to post a patch for a new lightbulb to -hackers;</para>
|
||||
|
||||
<para>One to complain that he had patches for this three years ago,
|
||||
but when he sent them to -current they were just ignored, and he
|
||||
but when he sent them to -CURRENT they were just ignored, and he
|
||||
has had bad experiences with the PR system; besides, the
|
||||
proposed new lightbulb is non-reflexive;</para>
|
||||
|
||||
|
|
@ -7622,15 +7631,15 @@ id="hackers">
|
|||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para><symbol>RELENG_2_2</symbol> AKA <emphasis remap=bf>2.2-stable</emphasis> AKA <emphasis remap=bf>"2.2 branch"</emphasis></para>
|
||||
<para><symbol>RELENG_2_2</symbol> AKA <emphasis remap=bf>2.2-STABLE</emphasis> AKA <emphasis remap=bf>"2.2 branch"</emphasis></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><symbol>RELENG_3</symbol> AKA <emphasis remap=bf>3.x-stable</emphasis> AKA <emphasis remap=bf>"3.0 branch"</emphasis></para>
|
||||
<para><symbol>RELENG_3</symbol> AKA <emphasis remap=bf>3.X-STABLE</emphasis> AKA <emphasis remap=bf>"3.0 branch"</emphasis></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><acronym>HEAD</acronym> AKA <option>-current</option> AKA <emphasis remap=bf>4.0-current</emphasis></para>
|
||||
<para><acronym>HEAD</acronym> AKA <option>-CURRENT</option> AKA <emphasis remap=bf>4.0-CURRENT</emphasis></para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
|
@ -7639,16 +7648,16 @@ id="hackers">
|
|||
<para><acronym>HEAD</acronym> is not an actual branch tag, like the other two, it's
|
||||
simply a symbolic constant for
|
||||
<emphasis>"the current, non-branched development stream"</emphasis> which we simply
|
||||
refer to as <option>-current</option>.</para>
|
||||
refer to as <option>-CURRENT</option>.</para>
|
||||
|
||||
<para>Right now, <option>-current</option> is the 4.0 development stream and the
|
||||
<emphasis remap=bf>3.0-stable</emphasis> branch, <symbol>RELENG_3</symbol>, forked off from
|
||||
<option>-current</option> in Jan 1999.</para>
|
||||
<para>Right now, <option>-CURRENT</option> is the 4.0 development stream and the
|
||||
<emphasis remap=bf>3.0-STABLE</emphasis> branch, <symbol>RELENG_3</symbol>, forked off from
|
||||
<option>-CURRENT</option> in Jan 1999.</para>
|
||||
|
||||
<para>The <emphasis remap=bf>2.2-stable</emphasis> branch, <symbol>RELENG_2_2</symbol>, departed -current in
|
||||
<para>The <emphasis remap=bf>2.2-STABLE</emphasis> branch, <symbol>RELENG_2_2</symbol>, departed -CURRENT in
|
||||
November 1996.</para>
|
||||
|
||||
<para>The <emphasis remap=bf>2.1-stable</emphasis> branch, <symbol>RELENG_2_1_0</symbol>, departed -current in
|
||||
<para>The <emphasis remap=bf>2.1-STABLE</emphasis> branch, <symbol>RELENG_2_1_0</symbol>, departed -CURRENT in
|
||||
September of 1994. This branch has been fully retired.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
|
@ -7709,7 +7718,7 @@ above you've got the CVS repository in <filename>/home/ncvs</filename>:</para>
|
|||
<filename>/some/big/filesystem/release</filename> and you will have a full FTP-type
|
||||
installation in <filename>/some/big/filesystem/release/R/ftp</filename> when you're
|
||||
done. If you want to build your SNAP along some other branch than
|
||||
-current, you can also add <literal>RELEASETAG=SOMETAG</literal> to
|
||||
-CURRENT, you can also add <literal>RELEASETAG=SOMETAG</literal> to
|
||||
the make release command line above, e.g. <literal>RELEASETAG=RELENG_2_2</literal>
|
||||
would build an up-to-the- minute 2.2-STABLE snapshot.</para>
|
||||
|
||||
|
|
@ -8032,7 +8041,7 @@ instruction pointer with a function in the kernel symbol table.</para>
|
|||
<para> The best way to track down the cause of a panic is by
|
||||
capturing a crash dump, then using <command>gdb(1)</command> to to a stack
|
||||
trace on the crash dump. Of course, this depends on <command>gdb(1)</command>
|
||||
in -current working correctly, which I can't guarantee (I recall
|
||||
in -CURRENT working correctly, which I can't guarantee (I recall
|
||||
somebody saying that the new ELF-ized <command>gdb(1)</command> didn't handle
|
||||
kernel crash dumps correctly: somebody should check this before
|
||||
3.0 goes out of beta or there'll be a lot of red faces after the
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
<book>
|
||||
|
||||
<bookinfo>
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X</title>
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X and 3.X</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
|
|
@ -10,9 +10,9 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.22 1999/11/12 04:36:42 chris Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.23 1999/11/13 00:25:00 jim Exp $</pubdate>
|
||||
|
||||
<abstract><para> This is the FAQ for FreeBSD systems version 2.X All entries are
|
||||
<abstract><para> This is the FAQ for FreeBSD versions 2.X and 3.X. All entries are
|
||||
assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted.
|
||||
Any entries with a <XXX> are under construction.
|
||||
If you are interested in helping with this project, send
|
||||
|
|
@ -25,7 +25,7 @@
|
|||
<preface id="preface">
|
||||
<title>Preface</title>
|
||||
|
||||
<para>Welcome to the FreeBSD 2.X FAQ!</para>
|
||||
<para>Welcome to the FreeBSD 2.X-3.X FAQ!</para>
|
||||
|
||||
<para>As is usual with Usenet FAQs, this document aims to cover the most
|
||||
frequently asked questions concerning the FreeBSD operating system
|
||||
|
|
@ -122,45 +122,45 @@ really can do whatever you like with it.</para>
|
|||
<qandaentry><question>
|
||||
<para>What is the latest version of FreeBSD?</para></question><answer>
|
||||
|
||||
<para>Version <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/3.2-RELEASE/">3.2</ulink> is the latest <emphasis>stable</emphasis> version; it was released
|
||||
in May, 1999. This is also the latest <emphasis>release</emphasis> version.</para>
|
||||
<para>Version <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/3.3-RELEASE/">3.3</ulink> is the latest <emphasis>stable</emphasis> version; it was released
|
||||
in September, 1999. This is also the latest <emphasis>release</emphasis> version.</para>
|
||||
|
||||
<para>Briefly explained, <emphasis>-stable</emphasis> is aimed at the ISP or other
|
||||
<para>Briefly explained, <emphasis>-STABLE</emphasis> is aimed at the ISP or other
|
||||
corporate user who wants stability and a low change count over
|
||||
the wizzy new features of the latest <emphasis>-current</emphasis> snapshot.
|
||||
the wizzy new features of the latest <emphasis>-CURRENT</emphasis> snapshot.
|
||||
Releases can come from either "branch," but you should only use
|
||||
<emphasis>-current</emphasis> if you're sure that you're prepared for its
|
||||
increased volatility (relative to <emphasis>-stable</emphasis>, that is).</para>
|
||||
<emphasis>-CURRENT</emphasis> if you're sure that you're prepared for its
|
||||
increased volatility (relative to <emphasis>-STABLE</emphasis>, that is).</para>
|
||||
|
||||
<para>Releases are only made <link linkend="release-freq">every few months</link>. While many people stay more up-to-date with the
|
||||
FreeBSD sources (see the questions on <link linkend="current">FreeBSD-current</link> and <link linkend="stable">FreeBSD-stable</link>) than that, doing so is more of a
|
||||
FreeBSD sources (see the questions on <link linkend="current">FreeBSD-CURRENT</link> and <link linkend="stable">FreeBSD-STABLE</link>) than that, doing so is more of a
|
||||
commitment, as the sources are a moving target.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry><question
|
||||
id="current">
|
||||
<para>What is FreeBSD-current?</para></question><answer>
|
||||
<para>What is FreeBSD-CURRENT?</para></question><answer>
|
||||
|
||||
<para><ulink URL="../handbook/cutting-edge.html#CURRENT">FreeBSD-current</ulink> is the
|
||||
<para><ulink URL="../handbook/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink> is the
|
||||
development version of the operating system, which will in due
|
||||
course become 4.0-RELEASE. As such, it is really only of interest
|
||||
to developers working on the system and die-hard hobbyists.
|
||||
See the <ulink URL="../handbook/cutting-edge.html#CURRENT">relevant section</ulink>
|
||||
in the <ulink URL="../handbook/index.html">handbook</ulink> for
|
||||
details on running -current.</para>
|
||||
details on running -CURRENT.</para>
|
||||
|
||||
<para>If you are not familiar with the operating system or are not
|
||||
capable of identifying the difference between a real problem and
|
||||
a temporary problem, you should not use FreeBSD-current. This
|
||||
a temporary problem, you should not use FreeBSD-CURRENT. This
|
||||
branch sometimes evolves quite quickly and can be un-buildable
|
||||
for a number of days at a time. People that use FreeBSD-current
|
||||
for a number of days at a time. People that use FreeBSD-CURRENT
|
||||
are expected to be able to analyze any problems and only report them
|
||||
if they are deemed to be mistakes rather than ``glitches''. Questions
|
||||
such as ``make world produces some error about groups'' on the
|
||||
-current mailing list are sometimes treated with contempt.</para>
|
||||
-CURRENT mailing list are sometimes treated with contempt.</para>
|
||||
|
||||
<para>Every now and again, a <ulink URL="../releases/snapshots.html">snapshot</ulink> release is also made of this -current development
|
||||
<para>Every now and again, a <ulink URL="../releases/snapshots.html">snapshot</ulink> release is also made of this -CURRENT development
|
||||
code, CDROM distributions of the occasional snapshot even now being
|
||||
made available. The goals behind each snapshot release are:</para>
|
||||
|
||||
|
|
@ -173,7 +173,7 @@ made available. The goals behind each snapshot release are:</para>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>To give people who would like to run -current but who don't
|
||||
<para>To give people who would like to run -CURRENT but who don't
|
||||
have the time and/or bandwidth to follow it on a day-to-day
|
||||
basis an easy way of bootstrapping it onto their systems.
|
||||
</para>
|
||||
|
|
@ -199,22 +199,22 @@ greatest possible number of potential testers.</para>
|
|||
and tested mettle, you will have to stick to full releases.</para>
|
||||
|
||||
<para>Snapshot releases are directly available from <ulink URL="ftp://current.FreeBSD.org/pub/FreeBSD/">ftp://current.FreeBSD.org/pub/FreeBSD/</ulink> and are generated,
|
||||
on the average, once a day for both the 4.0-current and 3.0-stable
|
||||
on the average, once a day for both the 4.0-CURRENT and 3.0-STABLE
|
||||
branches.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry><question
|
||||
id="stable">
|
||||
<para>What is the FreeBSD-stable concept?</para></question><answer>
|
||||
<para>What is the FreeBSD-STABLE concept?</para></question><answer>
|
||||
|
||||
<para>Back when FreeBSD 2.0.5 was released, we decided to branch FreeBSD
|
||||
development into two parts. One branch was named <ulink URL="../handbook/stable.html">-stable</ulink>, with the
|
||||
development into two parts. One branch was named <ulink URL="../handbook/stable.html">-STABLE</ulink>, with the
|
||||
intention that only well-tested bug fixes and small incremental
|
||||
enhancements would be made to it (for Internet Service Providers
|
||||
and other commercial enterprises for whom sudden shifts or
|
||||
experimental features are quite undesirable). The other branch was
|
||||
<ulink URL="../handbook/cutting-edge.html#CURRENT">-current</ulink>, which
|
||||
<ulink URL="../handbook/cutting-edge.html#CURRENT">-CURRENT</ulink>, which
|
||||
essentially has been one unbroken line leading towards 4.0-RELEASE
|
||||
(and beyond) since 2.0 was released. If a little ASCII art would
|
||||
help, this is how it looks:</para>
|
||||
|
|
@ -223,12 +223,12 @@ help, this is how it looks:</para>
|
|||
<literallayout> 2.0
|
||||
|
|
||||
|
|
||||
| [2.1-stable]
|
||||
*BRANCH* 2.0.5 -> 2.1 -> 2.1.5 -> 2.1.6 -> 2.1.7.1 [2.1-stable ends]
|
||||
| [2.1-STABLE]
|
||||
*BRANCH* 2.0.5 -> 2.1 -> 2.1.5 -> 2.1.6 -> 2.1.7.1 [2.1-STABLE ends]
|
||||
| (Mar 1997)
|
||||
|
|
||||
|
|
||||
| [2.2-stable]
|
||||
| [2.2-STABLE]
|
||||
*BRANCH* 2.2.1 -> 2.2.2-RELEASE -> 2.2.5 -> 2.2.6 -> 2.2.7 -> 2.2.8 [end]
|
||||
| (Mar 1997) (Oct 97) (Apr 98) (Jul 98) (Dec 98)
|
||||
|
|
||||
|
|
@ -238,19 +238,19 @@ help, this is how it looks:</para>
|
|||
|
|
||||
3.0.0-RELEASE (Oct 1998)
|
||||
|
|
||||
| [3.0-stable]
|
||||
| [3.0-STABLE]
|
||||
*BRANCH* 3.1 (Feb 1999) -> 3.2 -> ... future 3.x releases ...
|
||||
| (May 1999)
|
||||
|
|
||||
\|/
|
||||
+
|
||||
[4.0-current continues]</literallayout>
|
||||
[4.0-CURRENT continues]</literallayout>
|
||||
</para>
|
||||
|
||||
<para>The -current branch is slowly progressing towards 4.0 and beyond,
|
||||
the previous 2.2-stable branch having just retired with the release
|
||||
of 2.2.8. 3.0-stable has now replaced it, the next release coming
|
||||
up with 3.3 in Q3 1999. 4.0-current is now the "current branch",
|
||||
<para>The -CURRENT branch is slowly progressing towards 4.0 and beyond,
|
||||
the previous 2.2-STABLE branch having been retired with the release
|
||||
of 2.2.8. 3.3-STABLE has now replaced it, with 3.3-RELEASE being released
|
||||
in mid-September 1999. 4.0-CURRENT is now the "current branch",
|
||||
with the first 4.0 releases appearing in Q1 2000.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
|
@ -315,14 +315,14 @@ from the <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/">FreeBSD FTP site</ulink
|
|||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para>For the current 2.2-stable release, 2.2.8R, see the
|
||||
<ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/2.2.8-RELEASE/">2.2.8-RELEASE</ulink> directory.
|
||||
<para>For the current 2.2-STABLE release, 2.2.8R, see the
|
||||
<ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/2.2.8-RELEASE/">2.2.8-RELEASE</ulink> directory.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>For the current 3.0-stable release, 3.0-RELEASE, see the
|
||||
<ulink URL="ftp://current.FreeBSD.org/pub/FreeBSD/releases/3.0-RELEASE/">3.0-RELEASE</ulink> directory.
|
||||
<para>For the current 3.X-STABLE release, 3.3-RELEASE, see the
|
||||
<ulink URL="ftp://current.FreeBSD.org/pub/FreeBSD/releases/i386/3.3-RELEASE/">3.3-RELEASE</ulink> directory.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -337,15 +337,15 @@ are now made.
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink URL="ftp://releng30.FreeBSD.org/pub/FreeBSD/">3.0 Snapshot</ulink> releases are also made once a day along the
|
||||
RELENG_3 branch (post 3.0-release) as it continues on its way
|
||||
towards 3.2-RELEASE.
|
||||
<para><ulink URL="ftp://releng30.FreeBSD.org/pub/FreeBSD/">3.X Snapshot</ulink> releases are also made once a day along the
|
||||
RELENG_3 branch (post 3.0-RELEASE) as it continues on its way
|
||||
towards 3.4-RELEASE.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink URL="ftp://current.FreeBSD.org/pub/FreeBSD/">4.0 Snapshot</ulink> releases are made once a day for the
|
||||
<link linkend="current">-current</link> branch, these being of service
|
||||
<link linkend="current">-CURRENT</link> branch, these being of service
|
||||
purely to bleeding-edge testers and developers.</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -704,7 +704,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix
|
|||
<listitem>
|
||||
<para>Using ftp mirror: You can download the FTP server's copy of
|
||||
the web site using your favorite ftp mirror tool. Simply start at
|
||||
ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www.</para>
|
||||
ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-CURRENT/www.</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
|
@ -1557,7 +1557,7 @@ filesystems with 4 terabytes are possible (and exist).</para>
|
|||
<literallayout> maxfilesize
|
||||
----------------------------------
|
||||
2.2.7 3.0
|
||||
fs block size -stable -current works should-work
|
||||
fs block size -STABLE -CURRENT works should-work
|
||||
------------- ------- -------- ----- -----------
|
||||
4K 4T-1 4T-1 4T-1 4+T
|
||||
8K 32+G 8T-1 32+G 16T-1
|
||||
|
|
@ -1577,10 +1577,10 @@ unreachable when the fs block size is 4K.</para>
|
|||
|
||||
<para>For block sizes of 8K and larger, everything should be limited
|
||||
by the 2G-1 limit on fs block numbers, but is actually limited by the
|
||||
1G-1 limit on fs block numbers, except under -stable triple indirect
|
||||
1G-1 limit on fs block numbers, except under -STABLE triple indirect
|
||||
blocks are unreachable, so the limit is the maxiumum fs block number
|
||||
that can be represented using double indirect blocks
|
||||
(approx. (blocksize/4)^2 + (blocksize/4)), and under -current
|
||||
(approx. (blocksize/4)^2 + (blocksize/4)), and under -CURRENT
|
||||
exceeding this limit may cause problems. Using the correct limit of
|
||||
2G-1 blocks does cause problems.</para>
|
||||
|
||||
|
|
@ -1859,6 +1859,15 @@ system starts. In version 2.2.1, set the following variables in
|
|||
</literallayout>
|
||||
</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>
|
||||
|
||||
<para>
|
||||
<literallayout> allscreens_flags="-m on"
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
<para>Staring 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 ``<emphasis remap=tt>auto</emphasis>'' as
|
||||
|
|
@ -3014,7 +3023,7 @@ of FreeBSD at the following locations:</para>
|
|||
|
||||
<para>
|
||||
<variablelist>
|
||||
<varlistentry><term>for 2.2.8-release/2.2.8-stable</term>
|
||||
<varlistentry><term>for 2.2.8-RELEASE/2.2.8-STABLE</term>
|
||||
<listitem>
|
||||
<para><ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-2.2.8/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-2.2.8/</ulink></para>
|
||||
|
||||
|
|
@ -3023,7 +3032,7 @@ of FreeBSD at the following locations:</para>
|
|||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry><term>for 3.2-release/3.2-stable</term>
|
||||
<varlistentry><term>for 3.X-RELEASE/3.X-STABLE</term>
|
||||
|
||||
<listitem>
|
||||
<para><ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/</ulink></para>
|
||||
|
|
@ -3033,7 +3042,7 @@ of FreeBSD at the following locations:</para>
|
|||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry><term>for 4.0-current</term>
|
||||
<varlistentry><term>for 4.0-CURRENT</term>
|
||||
|
||||
<listitem>
|
||||
<para><ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-current/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-current/</ulink></para>
|
||||
|
|
@ -3110,7 +3119,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
|
|||
</para>
|
||||
|
||||
<para>You just need socksys to go to <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?null(4)">/dev/null</ulink>
|
||||
to fake the open & close. The code in -current will handle the
|
||||
to fake the open & close. The code in -CURRENT will handle the
|
||||
rest. This is much cleaner than the way it was done before. If you
|
||||
want the <emphasis remap=tt>spx</emphasis> driver for a local socket X connection, define
|
||||
<symbol>SPX_HACK</symbol> when you compile the system.</para>
|
||||
|
|
@ -3142,15 +3151,15 @@ in the ports tree.</para>
|
|||
</answer></qandaentry>
|
||||
|
||||
<qandaentry><question>
|
||||
<para>Why can't I build this port on my 3.x-stable machine?</para></question><answer>
|
||||
<para>Why can't I build this port on my 3.X-STABLE machine?</para></question><answer>
|
||||
|
||||
<para>If you're running a FreeBSD version that lags significantly behind
|
||||
-current or -stable, you may need a ports upgrade kit from
|
||||
-CURRENT or -STABLE, you may need a ports upgrade kit from
|
||||
<ulink URL="http://www.FreeBSD.org/ports/">http://www.FreeBSD.org/ports/</ulink>. If you are up to date, then
|
||||
someone might have committed a change to the port which works for
|
||||
-current but which broke the port for -stable. Please submit a bug
|
||||
-CURRENT but which broke the port for -STABLE. Please submit a bug
|
||||
report on this with the <command>send-pr(1)</command> command, since the ports
|
||||
collection is supposed to work for both the -current and -stable
|
||||
collection is supposed to work for both the -CURRENT and -STABLE
|
||||
branches.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
|
@ -3260,11 +3269,11 @@ write to through a special program to manage it called
|
|||
``<emphasis remap=tt>ft</emphasis>'' - see the man page on <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?ft">ft</ulink>
|
||||
for further details.</para>
|
||||
|
||||
<para>Versions previous to <option>-current</option> also had some trouble dealing
|
||||
<para>Versions previous to <option>-CURRENT</option> also had some trouble dealing
|
||||
with bad tape media; if you have trouble where <emphasis remap=tt>ft</emphasis> seems to
|
||||
go back and forth over the same spot, try grabbing the latest
|
||||
version of <emphasis remap=tt>ft</emphasis> from <filename>/usr/src/sbin/ft</filename> in
|
||||
<option>-current</option> and try that.</para>
|
||||
<option>-CURRENT</option> and try that.</para>
|
||||
|
||||
</answer></qandaentry></qandaset>
|
||||
</chapter>
|
||||
|
|
@ -4711,8 +4720,8 @@ waiting for you on the second ``virtual console''! When you
|
|||
want to go back to the original session, do Alt-F1.</para>
|
||||
|
||||
<para>The default FreeBSD installation has three virtual consoles
|
||||
enabled, and Alt-F1, Alt-F2, and Alt-F3 will switch between
|
||||
these virtual consoles.</para>
|
||||
enabled (8 starting with 3.3-RELEASE), and Alt-F1, Alt-F2, and
|
||||
Alt-F3 will switch between these virtual consoles.</para>
|
||||
|
||||
<para>To enable more of them, edit <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?ttys">/etc/ttys</ulink>
|
||||
and add entries for ``<emphasis remap=tt>ttyv4</emphasis>'' to ``<emphasis remap=tt>ttyvc</emphasis>'' after the
|
||||
|
|
@ -7510,7 +7519,7 @@ back when.</para>
|
|||
|
||||
<para>One thousand, one hundred and seventy-two:</para>
|
||||
|
||||
<para>Twenty-three to complain to -current about the lights being
|
||||
<para>Twenty-three to complain to -CURRENT about the lights being
|
||||
out;</para>
|
||||
|
||||
<para>Four to claim that it is a configuration problem, and that
|
||||
|
|
@ -7533,7 +7542,7 @@ have cvsupped at a bad time;</para>
|
|||
<para>One to post a patch for a new lightbulb to -hackers;</para>
|
||||
|
||||
<para>One to complain that he had patches for this three years ago,
|
||||
but when he sent them to -current they were just ignored, and he
|
||||
but when he sent them to -CURRENT they were just ignored, and he
|
||||
has had bad experiences with the PR system; besides, the
|
||||
proposed new lightbulb is non-reflexive;</para>
|
||||
|
||||
|
|
@ -7622,15 +7631,15 @@ id="hackers">
|
|||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para><symbol>RELENG_2_2</symbol> AKA <emphasis remap=bf>2.2-stable</emphasis> AKA <emphasis remap=bf>"2.2 branch"</emphasis></para>
|
||||
<para><symbol>RELENG_2_2</symbol> AKA <emphasis remap=bf>2.2-STABLE</emphasis> AKA <emphasis remap=bf>"2.2 branch"</emphasis></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><symbol>RELENG_3</symbol> AKA <emphasis remap=bf>3.x-stable</emphasis> AKA <emphasis remap=bf>"3.0 branch"</emphasis></para>
|
||||
<para><symbol>RELENG_3</symbol> AKA <emphasis remap=bf>3.X-STABLE</emphasis> AKA <emphasis remap=bf>"3.0 branch"</emphasis></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><acronym>HEAD</acronym> AKA <option>-current</option> AKA <emphasis remap=bf>4.0-current</emphasis></para>
|
||||
<para><acronym>HEAD</acronym> AKA <option>-CURRENT</option> AKA <emphasis remap=bf>4.0-CURRENT</emphasis></para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
|
@ -7639,16 +7648,16 @@ id="hackers">
|
|||
<para><acronym>HEAD</acronym> is not an actual branch tag, like the other two, it's
|
||||
simply a symbolic constant for
|
||||
<emphasis>"the current, non-branched development stream"</emphasis> which we simply
|
||||
refer to as <option>-current</option>.</para>
|
||||
refer to as <option>-CURRENT</option>.</para>
|
||||
|
||||
<para>Right now, <option>-current</option> is the 4.0 development stream and the
|
||||
<emphasis remap=bf>3.0-stable</emphasis> branch, <symbol>RELENG_3</symbol>, forked off from
|
||||
<option>-current</option> in Jan 1999.</para>
|
||||
<para>Right now, <option>-CURRENT</option> is the 4.0 development stream and the
|
||||
<emphasis remap=bf>3.0-STABLE</emphasis> branch, <symbol>RELENG_3</symbol>, forked off from
|
||||
<option>-CURRENT</option> in Jan 1999.</para>
|
||||
|
||||
<para>The <emphasis remap=bf>2.2-stable</emphasis> branch, <symbol>RELENG_2_2</symbol>, departed -current in
|
||||
<para>The <emphasis remap=bf>2.2-STABLE</emphasis> branch, <symbol>RELENG_2_2</symbol>, departed -CURRENT in
|
||||
November 1996.</para>
|
||||
|
||||
<para>The <emphasis remap=bf>2.1-stable</emphasis> branch, <symbol>RELENG_2_1_0</symbol>, departed -current in
|
||||
<para>The <emphasis remap=bf>2.1-STABLE</emphasis> branch, <symbol>RELENG_2_1_0</symbol>, departed -CURRENT in
|
||||
September of 1994. This branch has been fully retired.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
|
@ -7709,7 +7718,7 @@ above you've got the CVS repository in <filename>/home/ncvs</filename>:</para>
|
|||
<filename>/some/big/filesystem/release</filename> and you will have a full FTP-type
|
||||
installation in <filename>/some/big/filesystem/release/R/ftp</filename> when you're
|
||||
done. If you want to build your SNAP along some other branch than
|
||||
-current, you can also add <literal>RELEASETAG=SOMETAG</literal> to
|
||||
-CURRENT, you can also add <literal>RELEASETAG=SOMETAG</literal> to
|
||||
the make release command line above, e.g. <literal>RELEASETAG=RELENG_2_2</literal>
|
||||
would build an up-to-the- minute 2.2-STABLE snapshot.</para>
|
||||
|
||||
|
|
@ -8032,7 +8041,7 @@ instruction pointer with a function in the kernel symbol table.</para>
|
|||
<para> The best way to track down the cause of a panic is by
|
||||
capturing a crash dump, then using <command>gdb(1)</command> to to a stack
|
||||
trace on the crash dump. Of course, this depends on <command>gdb(1)</command>
|
||||
in -current working correctly, which I can't guarantee (I recall
|
||||
in -CURRENT working correctly, which I can't guarantee (I recall
|
||||
somebody saying that the new ELF-ized <command>gdb(1)</command> didn't handle
|
||||
kernel crash dumps correctly: somebody should check this before
|
||||
3.0 goes out of beta or there'll be a lot of red faces after the
|
||||
|
|
|
|||
Loading…
Reference in a new issue