Added question about boot.flp hanging on an ASUS K7V motherboard, and the
workaround (disable BIOS boot sector virus check). Submitted by: Discussion on -stable Add 4.0 to a few places. Update the "Panic: can't mount root!" now we have a new boot loader. Add an "Error: can't find libc.so.4" and a "How do I upgrade from 3.x to 4.x" question. Fix a few typos in the PR. PR: docs/17861 Submitted by: Eric Ogren <eogren@earthlink.net> Add a little bit of extra information about chmod(1) on symlinks, so that the questions are a little bit clearer. Suggested by: Suresh Bhushan <sbhushan@smartshop.com> Reword the "snd0" answer, to make it clearer. Submitted by: gouders@et.bocholt.fh-gelsenkirchen.de
This commit is contained in:
Nik Clayton
parent
5a9e4f3502
commit
ceaadd8963
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=7118
2 changed files with 282 additions and 102 deletions
|
|
@ -5,7 +5,7 @@
|
|||
|
||||
<book>
|
||||
<bookinfo>
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X and 3.X</title>
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X, 3.X and 4.X</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
|
|
@ -13,10 +13,10 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.49 2000/04/03 12:01:33 phantom Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.50 2000/04/10 13:32:27 brian Exp $</pubdate>
|
||||
|
||||
<abstract>
|
||||
<para>This is the FAQ for FreeBSD versions 2.X and 3.X. All entries
|
||||
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.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,
|
||||
|
|
@ -37,7 +37,7 @@
|
|||
<preface id="preface">
|
||||
<title>Preface</title>
|
||||
|
||||
<para>Welcome to the FreeBSD 2.X-3.X FAQ!</para>
|
||||
<para>Welcome to the FreeBSD 2.X-4.X FAQ!</para>
|
||||
|
||||
<para>As is usual with Usenet FAQs, this document aims to cover the
|
||||
most frequently asked questions concerning the FreeBSD operating
|
||||
|
|
@ -58,7 +58,7 @@
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Briefly, FreeBSD 2.X is a UN*X-like operating system based
|
||||
<para>Briefly, FreeBSD is a UN*X-like operating system based
|
||||
on U.C. Berkeley's 4.4BSD-lite release for the i386 platform.
|
||||
It is also based indirectly on William Jolitz's port of U.C.
|
||||
Berkeley's Net/2 to the i386, known as 386BSD, though very
|
||||
|
|
@ -152,16 +152,16 @@
|
|||
|
||||
<answer>
|
||||
<para>Version <ulink
|
||||
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/3.4-RELEASE/">3.4</ulink>
|
||||
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.0-RELEASE/">4.0</ulink>
|
||||
is the latest <emphasis>stable</emphasis> version; it was
|
||||
released in December, 1999. This is also the latest
|
||||
released in March, 2000. This is also the latest
|
||||
<emphasis>release</emphasis> version.</para>
|
||||
|
||||
<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. Releases can come
|
||||
from either "branch," but you should only use
|
||||
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>
|
||||
|
|
@ -244,9 +244,16 @@
|
|||
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 the
|
||||
5.0-CURRENT, 4.X-STABLE and 3.X-STABLE branches.</para>
|
||||
URL="ftp://current.FreeBSD.org/pub/FreeBSD/">
|
||||
ftp://current.FreeBSD.org/pub/FreeBSD/</ulink>
|
||||
for 5.0-CURRENT and
|
||||
<ulink url="ftp://releng4.FreeBSD.org/pub/FreeBSD">
|
||||
releng4.FreeBSD.org</ulink> for 4-STABLE snapshots.
|
||||
3-STABLE snapshots can be found at
|
||||
<ulink url="releng3.FreeBSD.org/pub/FreeBSD">
|
||||
releng3.FreeBSD.org.</ulink>
|
||||
Snapshots are generated, on the average, once a day for
|
||||
all actively developed branches.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
@ -339,7 +346,7 @@
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>FreeBSD 3.x currently runs on the <ulink
|
||||
<para>Since 3.x, FreeBSD has run on the <ulink
|
||||
URL="../alpha/alpha.html">DEC Alpha</ulink> as well as the
|
||||
x86 architecture. Some interest has also been expressed in a
|
||||
SPARC port, but details on this project are not yet
|
||||
|
|
@ -397,26 +404,26 @@
|
|||
URL="ftp://current.FreeBSD.org/pub/FreeBSD/releases/i386/3.4-RELEASE/">3.4-RELEASE</ulink>
|
||||
directory.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
URL="ftp://releng22.FreeBSD.org/pub/FreeBSD/">2.2 Snapshot</ulink>
|
||||
releases are made once a day along the RELENG_2_2 branch (post
|
||||
2.2.8) as it slowly winds down in maintenance mode. The
|
||||
RELENG_2_2 branch is currently being carefully maintained by
|
||||
the legacy support folks and no changes other than those
|
||||
strictly necessary for security or reliability enhancements
|
||||
are now made.</para>
|
||||
</listitem>
|
||||
|
||||
<para>The current 4.X-STABLE release, 4.0-RELEASE can be
|
||||
found in <ulink
|
||||
url="ftp://current.FreeBSD.org/pub/FreeBSD/releases/i386/4.0-RELEASE"> the 4.0-RELEASE</ulink> directory.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
URL="ftp://releng3.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>
|
||||
3.5-RELEASE.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="ftp://releng4.FreeBSD.org/pub/FreeBSD/">4.X
|
||||
snapshots</ulink> are made once a day as well.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
URL="ftp://current.FreeBSD.org/pub/FreeBSD/">5.0 Snapshot</ulink>
|
||||
|
|
@ -1630,7 +1637,28 @@ think is the boot disk, wd1, while it is really wd2, and fails.</para>
|
|||
<orderedlist>
|
||||
|
||||
<listitem>
|
||||
<para>At the Boot: prompt, enter
|
||||
<para>For FreeBSD 3.3 and later, reboot the system and hit
|
||||
"Enter" at the "Booting kernel in 10 seconds; hit
|
||||
[Enter] to interrupt" prompt. This will drop you into the boot
|
||||
loader.</para>
|
||||
<para>Then type set
|
||||
root_disk_unit="<disk_number>". <literal>disk_number</literal>
|
||||
will be <emphasis>0</emphasis> if FreeBSD is installed on the master drive
|
||||
on the first IDE controller, <emphasis>1</emphasis> if it is installed
|
||||
on the slave on the first IDE controller, <emphasis>2</emphasis> if it
|
||||
is installed on the master of the second IDE controller, and
|
||||
<emphasis>3</emphasis> if it is installed on the slave of the second
|
||||
IDE controller.</para>
|
||||
<para>Then type "boot", and your system should boot
|
||||
correctly.</para>
|
||||
<para>To make this change permanent (ie so you don't have to do this
|
||||
everytime you reboot or turn on your FreeBSD machine), put the line
|
||||
"root_disk_unit="<disk_number>" in
|
||||
<filename>/boot/loader.conf.local</filename>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>If using FreeBSD 3.2 or earlier, at the Boot: prompt, enter
|
||||
<emphasis remap=tt>1:wd(2,a)kernel</emphasis> and press Enter. If the system starts, then
|
||||
run the command
|
||||
<literallayout>echo "1:wd(2,a)kernel" > /boot.config</literallayout>
|
||||
|
|
@ -1771,7 +1799,24 @@ started. More specifically, you have upgraded the source for your
|
|||
kernel, and installed a new kernel builtin from them <emphasis>without making
|
||||
world</emphasis>. This is not supported. Make world.</para>
|
||||
|
||||
</answer></qandaentry></qandaset>
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question><para>How do I upgrade from 3.X -> 4.X?</para></question>
|
||||
|
||||
<answer><para>We <emphasis>strongly</emphasis> recommend that you use
|
||||
binary snapshots to do this. 4.X-STABLE snapshots are available at
|
||||
<ulink
|
||||
url="ftp://releng4.FreeBSD.org">releng4.FreeBSD.org</ulink>.</para>
|
||||
<para>If you wish to upgrade using source, please see the <ulink
|
||||
url="http://www.FreeBSD.org/handbook/cutting-edge.html">FreeBSD
|
||||
Handbook</ulink> for more information.</para>
|
||||
<para><emphasis>Upgrading via source is never recommended for new
|
||||
users, and upgading from 3.X -> 4.X is even less so; make sure you
|
||||
have read the instructions carefully before attempting to upgrade via
|
||||
source this!</emphasis></para>
|
||||
</answer></qandaentry>
|
||||
</qandaset>
|
||||
</chapter>
|
||||
|
||||
<chapter
|
||||
|
|
@ -2494,7 +2539,20 @@ System" flag in the BIOS. </para>
|
|||
|
||||
<para>SMP is supported in 3.0-STABLE and later releases only.</para>
|
||||
|
||||
</answer></qandaentry></qandaset>
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>The boot floppy hangs on a system with an ASUS K7V
|
||||
motherboard. How do I fix this?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Go in to the BIOS setup and disable the boot virus
|
||||
protection.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</chapter>
|
||||
|
||||
<chapter
|
||||
|
|
@ -3430,13 +3488,22 @@ of FreeBSD at the following locations:</para>
|
|||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry><term>for 4.0-CURRENT</term>
|
||||
<varlistentry><term>for 4.0-RELEASE/4.X-STABLE</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>
|
||||
<para><ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/</ulink></para>
|
||||
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>for 5.X-CURRENT</term>
|
||||
|
||||
<listitem>
|
||||
<para><ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current</ulink></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
|
||||
|
|
@ -3484,11 +3551,21 @@ at the <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp.FreeBSD.org</ulink> m
|
|||
<qandaentry><question>
|
||||
<para>Where do I find libc.so.3.0?</para></question><answer>
|
||||
|
||||
<para>You are trying to run a package for 2.2/3.x/4.0 on a 2.1.x
|
||||
<para>You are trying to run a package built on 2.2 and later on a 2.1.x
|
||||
system. Please take a look at the previous section and get
|
||||
the correct port/package for your system.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
<qandaentry><question>
|
||||
<para>I get a message "Error: can't find
|
||||
libc.so.4.0"</para></question>
|
||||
<answer>
|
||||
|
||||
<para>You accidently downloaded packages meant for 4.X and 5.X
|
||||
systems and attempted to install them on your 2.X or 3.X FreeBSD system.
|
||||
Please download the correct version of the
|
||||
packages.</para></answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry><question
|
||||
id="emul">
|
||||
|
|
@ -4860,16 +4937,16 @@ using a regular expression. </para>
|
|||
<qandaentry><question>
|
||||
<para>I can't create the snd0 device!</para></question><answer>
|
||||
|
||||
<para>The command to create the devices for the sound card is:
|
||||
<literallayout> # cd /dev
|
||||
# sh MAKEDEV snd0</literallayout>
|
||||
</para>
|
||||
|
||||
<para>However, this does not make a device named <filename>/dev/snd0</filename>.
|
||||
Instead, it creates devices named <emphasis remap=tt>mixer0</emphasis>, <emphasis remap=tt>audio0</emphasis>,
|
||||
<emphasis remap=tt>dsp0</emphasis>, and others. Running the command is still necessary
|
||||
to add sound devices, however.</para>
|
||||
|
||||
<para>There is no <devicename>snd</devicename> device. The name is
|
||||
used as a shorthand for the various devices that make up the
|
||||
FreeBSD sound driver, such as <devicename>mixer</devicename>,
|
||||
<devicename>sequencer</devicename>, and
|
||||
<devicename>dsp</devicename>.</para>
|
||||
|
||||
<para>To create these devices you should</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /dev</userinput>
|
||||
&prompt.root; <userinput>sh MAKDEV snd0</userinput></screen>
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry><question>
|
||||
|
|
@ -8096,6 +8173,18 @@ eventually removed from the kernel once the need to run legacy
|
|||
<qandaentry><question>
|
||||
<para>Why won't chmod change the permissions on symlinks?</para></question><answer>
|
||||
|
||||
<para>Symlinks do not have permissions, and by default,
|
||||
&man.chmod.1; will not follow symlinks to change the permissions
|
||||
on the target file. So if you have a file,
|
||||
<filename>foo</filename>, and a symlink to that file,
|
||||
<filename>bar</filename>, then this command will always
|
||||
succeed.</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>chmod g-w bar</userinput></screen>
|
||||
|
||||
<para>However, the permissions on <filename>foo</filename> will not
|
||||
have changed.</para>
|
||||
|
||||
<para>You have to use either ``<option>-H</option>'' or ``<option>-L</option>'' together with
|
||||
the ``<option>-R</option>'' option to make this work. See the <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?chmod">chmod</ulink> and
|
||||
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?symlink">symlink</ulink>
|
||||
|
|
@ -8382,15 +8471,19 @@ 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></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></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><acronym>HEAD</acronym> AKA <option>-CURRENT</option> AKA <emphasis remap=bf>4.0-CURRENT</emphasis></para>
|
||||
<para><symbol>RELENG_4</symbol> AKA <emphasis>4.X-STABLE</emphasis></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><acronym>HEAD</acronym> AKA <option>-CURRENT</option> AKA <emphasis remap=bf>5.0-CURRENT</emphasis></para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
|
@ -8401,15 +8494,12 @@ simply a symbolic constant for
|
|||
<emphasis>"the current, non-branched development stream"</emphasis> which we simply
|
||||
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 5.0 development stream and the
|
||||
<emphasis remap=bf>4-STABLE</emphasis> branch, <symbol>RELENG_4</symbol>, forked off from
|
||||
<option>-CURRENT</option> in Mar 2000.</para>
|
||||
|
||||
<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
|
||||
September of 1994. This branch has been fully retired.</para>
|
||||
November 1996, and has pretty much been retired.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@
|
|||
|
||||
<book>
|
||||
<bookinfo>
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X and 3.X</title>
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X, 3.X and 4.X</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
|
|
@ -13,10 +13,10 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.49 2000/04/03 12:01:33 phantom Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.50 2000/04/10 13:32:27 brian Exp $</pubdate>
|
||||
|
||||
<abstract>
|
||||
<para>This is the FAQ for FreeBSD versions 2.X and 3.X. All entries
|
||||
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.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,
|
||||
|
|
@ -37,7 +37,7 @@
|
|||
<preface id="preface">
|
||||
<title>Preface</title>
|
||||
|
||||
<para>Welcome to the FreeBSD 2.X-3.X FAQ!</para>
|
||||
<para>Welcome to the FreeBSD 2.X-4.X FAQ!</para>
|
||||
|
||||
<para>As is usual with Usenet FAQs, this document aims to cover the
|
||||
most frequently asked questions concerning the FreeBSD operating
|
||||
|
|
@ -58,7 +58,7 @@
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Briefly, FreeBSD 2.X is a UN*X-like operating system based
|
||||
<para>Briefly, FreeBSD is a UN*X-like operating system based
|
||||
on U.C. Berkeley's 4.4BSD-lite release for the i386 platform.
|
||||
It is also based indirectly on William Jolitz's port of U.C.
|
||||
Berkeley's Net/2 to the i386, known as 386BSD, though very
|
||||
|
|
@ -152,16 +152,16 @@
|
|||
|
||||
<answer>
|
||||
<para>Version <ulink
|
||||
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/3.4-RELEASE/">3.4</ulink>
|
||||
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.0-RELEASE/">4.0</ulink>
|
||||
is the latest <emphasis>stable</emphasis> version; it was
|
||||
released in December, 1999. This is also the latest
|
||||
released in March, 2000. This is also the latest
|
||||
<emphasis>release</emphasis> version.</para>
|
||||
|
||||
<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. Releases can come
|
||||
from either "branch," but you should only use
|
||||
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>
|
||||
|
|
@ -244,9 +244,16 @@
|
|||
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 the
|
||||
5.0-CURRENT, 4.X-STABLE and 3.X-STABLE branches.</para>
|
||||
URL="ftp://current.FreeBSD.org/pub/FreeBSD/">
|
||||
ftp://current.FreeBSD.org/pub/FreeBSD/</ulink>
|
||||
for 5.0-CURRENT and
|
||||
<ulink url="ftp://releng4.FreeBSD.org/pub/FreeBSD">
|
||||
releng4.FreeBSD.org</ulink> for 4-STABLE snapshots.
|
||||
3-STABLE snapshots can be found at
|
||||
<ulink url="releng3.FreeBSD.org/pub/FreeBSD">
|
||||
releng3.FreeBSD.org.</ulink>
|
||||
Snapshots are generated, on the average, once a day for
|
||||
all actively developed branches.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
@ -339,7 +346,7 @@
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>FreeBSD 3.x currently runs on the <ulink
|
||||
<para>Since 3.x, FreeBSD has run on the <ulink
|
||||
URL="../alpha/alpha.html">DEC Alpha</ulink> as well as the
|
||||
x86 architecture. Some interest has also been expressed in a
|
||||
SPARC port, but details on this project are not yet
|
||||
|
|
@ -397,26 +404,26 @@
|
|||
URL="ftp://current.FreeBSD.org/pub/FreeBSD/releases/i386/3.4-RELEASE/">3.4-RELEASE</ulink>
|
||||
directory.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
URL="ftp://releng22.FreeBSD.org/pub/FreeBSD/">2.2 Snapshot</ulink>
|
||||
releases are made once a day along the RELENG_2_2 branch (post
|
||||
2.2.8) as it slowly winds down in maintenance mode. The
|
||||
RELENG_2_2 branch is currently being carefully maintained by
|
||||
the legacy support folks and no changes other than those
|
||||
strictly necessary for security or reliability enhancements
|
||||
are now made.</para>
|
||||
</listitem>
|
||||
|
||||
<para>The current 4.X-STABLE release, 4.0-RELEASE can be
|
||||
found in <ulink
|
||||
url="ftp://current.FreeBSD.org/pub/FreeBSD/releases/i386/4.0-RELEASE"> the 4.0-RELEASE</ulink> directory.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
URL="ftp://releng3.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>
|
||||
3.5-RELEASE.</para>
|
||||
</listitem>
|
||||
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="ftp://releng4.FreeBSD.org/pub/FreeBSD/">4.X
|
||||
snapshots</ulink> are made once a day as well.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
URL="ftp://current.FreeBSD.org/pub/FreeBSD/">5.0 Snapshot</ulink>
|
||||
|
|
@ -1630,7 +1637,28 @@ think is the boot disk, wd1, while it is really wd2, and fails.</para>
|
|||
<orderedlist>
|
||||
|
||||
<listitem>
|
||||
<para>At the Boot: prompt, enter
|
||||
<para>For FreeBSD 3.3 and later, reboot the system and hit
|
||||
"Enter" at the "Booting kernel in 10 seconds; hit
|
||||
[Enter] to interrupt" prompt. This will drop you into the boot
|
||||
loader.</para>
|
||||
<para>Then type set
|
||||
root_disk_unit="<disk_number>". <literal>disk_number</literal>
|
||||
will be <emphasis>0</emphasis> if FreeBSD is installed on the master drive
|
||||
on the first IDE controller, <emphasis>1</emphasis> if it is installed
|
||||
on the slave on the first IDE controller, <emphasis>2</emphasis> if it
|
||||
is installed on the master of the second IDE controller, and
|
||||
<emphasis>3</emphasis> if it is installed on the slave of the second
|
||||
IDE controller.</para>
|
||||
<para>Then type "boot", and your system should boot
|
||||
correctly.</para>
|
||||
<para>To make this change permanent (ie so you don't have to do this
|
||||
everytime you reboot or turn on your FreeBSD machine), put the line
|
||||
"root_disk_unit="<disk_number>" in
|
||||
<filename>/boot/loader.conf.local</filename>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>If using FreeBSD 3.2 or earlier, at the Boot: prompt, enter
|
||||
<emphasis remap=tt>1:wd(2,a)kernel</emphasis> and press Enter. If the system starts, then
|
||||
run the command
|
||||
<literallayout>echo "1:wd(2,a)kernel" > /boot.config</literallayout>
|
||||
|
|
@ -1771,7 +1799,24 @@ started. More specifically, you have upgraded the source for your
|
|||
kernel, and installed a new kernel builtin from them <emphasis>without making
|
||||
world</emphasis>. This is not supported. Make world.</para>
|
||||
|
||||
</answer></qandaentry></qandaset>
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question><para>How do I upgrade from 3.X -> 4.X?</para></question>
|
||||
|
||||
<answer><para>We <emphasis>strongly</emphasis> recommend that you use
|
||||
binary snapshots to do this. 4.X-STABLE snapshots are available at
|
||||
<ulink
|
||||
url="ftp://releng4.FreeBSD.org">releng4.FreeBSD.org</ulink>.</para>
|
||||
<para>If you wish to upgrade using source, please see the <ulink
|
||||
url="http://www.FreeBSD.org/handbook/cutting-edge.html">FreeBSD
|
||||
Handbook</ulink> for more information.</para>
|
||||
<para><emphasis>Upgrading via source is never recommended for new
|
||||
users, and upgading from 3.X -> 4.X is even less so; make sure you
|
||||
have read the instructions carefully before attempting to upgrade via
|
||||
source this!</emphasis></para>
|
||||
</answer></qandaentry>
|
||||
</qandaset>
|
||||
</chapter>
|
||||
|
||||
<chapter
|
||||
|
|
@ -2494,7 +2539,20 @@ System" flag in the BIOS. </para>
|
|||
|
||||
<para>SMP is supported in 3.0-STABLE and later releases only.</para>
|
||||
|
||||
</answer></qandaentry></qandaset>
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>The boot floppy hangs on a system with an ASUS K7V
|
||||
motherboard. How do I fix this?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Go in to the BIOS setup and disable the boot virus
|
||||
protection.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</chapter>
|
||||
|
||||
<chapter
|
||||
|
|
@ -3430,13 +3488,22 @@ of FreeBSD at the following locations:</para>
|
|||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry><term>for 4.0-CURRENT</term>
|
||||
<varlistentry><term>for 4.0-RELEASE/4.X-STABLE</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>
|
||||
<para><ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/</ulink></para>
|
||||
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>for 5.X-CURRENT</term>
|
||||
|
||||
<listitem>
|
||||
<para><ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current</ulink></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
|
||||
|
|
@ -3484,11 +3551,21 @@ at the <ulink URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp.FreeBSD.org</ulink> m
|
|||
<qandaentry><question>
|
||||
<para>Where do I find libc.so.3.0?</para></question><answer>
|
||||
|
||||
<para>You are trying to run a package for 2.2/3.x/4.0 on a 2.1.x
|
||||
<para>You are trying to run a package built on 2.2 and later on a 2.1.x
|
||||
system. Please take a look at the previous section and get
|
||||
the correct port/package for your system.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
<qandaentry><question>
|
||||
<para>I get a message "Error: can't find
|
||||
libc.so.4.0"</para></question>
|
||||
<answer>
|
||||
|
||||
<para>You accidently downloaded packages meant for 4.X and 5.X
|
||||
systems and attempted to install them on your 2.X or 3.X FreeBSD system.
|
||||
Please download the correct version of the
|
||||
packages.</para></answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry><question
|
||||
id="emul">
|
||||
|
|
@ -4860,16 +4937,16 @@ using a regular expression. </para>
|
|||
<qandaentry><question>
|
||||
<para>I can't create the snd0 device!</para></question><answer>
|
||||
|
||||
<para>The command to create the devices for the sound card is:
|
||||
<literallayout> # cd /dev
|
||||
# sh MAKEDEV snd0</literallayout>
|
||||
</para>
|
||||
|
||||
<para>However, this does not make a device named <filename>/dev/snd0</filename>.
|
||||
Instead, it creates devices named <emphasis remap=tt>mixer0</emphasis>, <emphasis remap=tt>audio0</emphasis>,
|
||||
<emphasis remap=tt>dsp0</emphasis>, and others. Running the command is still necessary
|
||||
to add sound devices, however.</para>
|
||||
|
||||
<para>There is no <devicename>snd</devicename> device. The name is
|
||||
used as a shorthand for the various devices that make up the
|
||||
FreeBSD sound driver, such as <devicename>mixer</devicename>,
|
||||
<devicename>sequencer</devicename>, and
|
||||
<devicename>dsp</devicename>.</para>
|
||||
|
||||
<para>To create these devices you should</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /dev</userinput>
|
||||
&prompt.root; <userinput>sh MAKDEV snd0</userinput></screen>
|
||||
</answer></qandaentry>
|
||||
|
||||
<qandaentry><question>
|
||||
|
|
@ -8096,6 +8173,18 @@ eventually removed from the kernel once the need to run legacy
|
|||
<qandaentry><question>
|
||||
<para>Why won't chmod change the permissions on symlinks?</para></question><answer>
|
||||
|
||||
<para>Symlinks do not have permissions, and by default,
|
||||
&man.chmod.1; will not follow symlinks to change the permissions
|
||||
on the target file. So if you have a file,
|
||||
<filename>foo</filename>, and a symlink to that file,
|
||||
<filename>bar</filename>, then this command will always
|
||||
succeed.</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>chmod g-w bar</userinput></screen>
|
||||
|
||||
<para>However, the permissions on <filename>foo</filename> will not
|
||||
have changed.</para>
|
||||
|
||||
<para>You have to use either ``<option>-H</option>'' or ``<option>-L</option>'' together with
|
||||
the ``<option>-R</option>'' option to make this work. See the <ulink URL="http://www.FreeBSD.org/cgi/man.cgi?chmod">chmod</ulink> and
|
||||
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?symlink">symlink</ulink>
|
||||
|
|
@ -8382,15 +8471,19 @@ 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></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></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><acronym>HEAD</acronym> AKA <option>-CURRENT</option> AKA <emphasis remap=bf>4.0-CURRENT</emphasis></para>
|
||||
<para><symbol>RELENG_4</symbol> AKA <emphasis>4.X-STABLE</emphasis></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><acronym>HEAD</acronym> AKA <option>-CURRENT</option> AKA <emphasis remap=bf>5.0-CURRENT</emphasis></para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
|
@ -8401,15 +8494,12 @@ simply a symbolic constant for
|
|||
<emphasis>"the current, non-branched development stream"</emphasis> which we simply
|
||||
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 5.0 development stream and the
|
||||
<emphasis remap=bf>4-STABLE</emphasis> branch, <symbol>RELENG_4</symbol>, forked off from
|
||||
<option>-CURRENT</option> in Mar 2000.</para>
|
||||
|
||||
<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
|
||||
September of 1994. This branch has been fully retired.</para>
|
||||
November 1996, and has pretty much been retired.</para>
|
||||
|
||||
</answer></qandaentry>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue