aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/faq
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/books/faq')
-rw-r--r--en_US.ISO8859-1/books/faq/book.sgml399
1 files changed, 30 insertions, 369 deletions
diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml
index d07b375c2a..9eff975fb9 100644
--- a/en_US.ISO8859-1/books/faq/book.sgml
+++ b/en_US.ISO8859-1/books/faq/book.sgml
@@ -1288,28 +1288,21 @@
<answer>
<para>For &os; you will need a 486 or better PC, with
- 24&nbsp;MB or more of RAM and at least 150&nbsp;MB of hard
+ 64&nbsp;MB or more of RAM and at least 1&nbsp;GB of hard
disk space.</para>
- <para>All versions of &os; can run with a low end MDA graphics
- card but to run &xorg;, a VGA or better video card is
- needed.</para>
-
<para>See also <xref linkend="hardware"/>.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="custom-boot-floppy">
- <para>How can I make my own custom install floppy?</para>
+ <para>How can I make my own custom install disk?</para>
</question>
<answer>
- <para>Currently there is no way to <emphasis>just</emphasis>
- make a custom install floppy. You have to cut a whole new
- release, which will include your install floppy.</para>
-
- <para>To make a custom release, follow the instructions in the
+ <para>Customized &os; installation media can be created by
+ building a custom release. Follow the instructions in the
<ulink
url="&url.articles.releng;/article.html">Release Engineering</ulink>
article.</para>
@@ -1822,35 +1815,17 @@
<qandaentry>
<question id="need-complete-sources">
- <para>Do I need to install the complete sources?</para>
+ <para>Do I need to install the source?</para>
</question>
<answer>
- <para>In general, no. However, we would strongly recommend
- that you install, at a minimum, the <literal>base</literal>
- source kit, which includes several of the files mentioned
- here, and the <literal>sys</literal> (kernel) source kit,
- which includes sources for the kernel. There is nothing in
- the system which requires the presence of the sources to
- operate, however, except for the kernel-configuration
- program &man.config.8;. With the exception of the kernel
- sources, our build structure is set up so that you can
- read-only mount the sources from elsewhere via NFS and still
- be able to make new binaries (due to the kernel-source
- restriction, we recommend that you not mount this on
- <filename class="directory">/usr/src</filename> directly, but
- rather in some other location with appropriate symbolic
- links to duplicate the top-level structure of the source
- tree).</para>
-
- <para>Having the sources on-line and knowing how to build a
- system with them will make it much easier for you to upgrade
- to future releases of &os;.</para>
-
- <para>To actually select a subset of the sources, use the
- <guimenuitem>Custom</guimenuitem> menu item when you are in
- the <guimenuitem>Distributions</guimenuitem> menu of the
- system installation tool.</para>
+ <para>In general, no. There is nothing in the base
+ system which requires the presence of the source to
+ operate. Some ports, like <filename
+ role="package">sysutils/lsof</filename>, will not build
+ unless the source is installed. In particular, if the
+ port builds a kernel module or directly operates on kernel
+ structures, the source must be installed.</para>
</answer>
</qandaentry>
@@ -1860,18 +1835,15 @@
</question>
<answer>
- <para>Building a new kernel was originally pretty much a
- required step in a &os; installation, but more recent releases
- have benefited from the introduction of much friendlier
- kernel configuration methods. It is very easy to configure
- the kernel's configuration by much more flexible
- <quote>hints</quote> which can be set at the loader
- prompt.</para>
-
- <para>It may still be worthwhile building a new kernel
- containing just the drivers that you need, just to save a
- bit of RAM, but it is no longer necessary for most
- systems.</para>
+ <para>Usually not. The supplied <literal>GENERIC</literal>
+ kernel contains the drivers an ordinary computer will
+ need. &man.freebsd-update.8;, the &os; binary upgrade
+ tool, cannot upgrade custom kernels, another reason
+ to stick with the GENERIC kernel when possible.
+ For computers with very limited RAM, such as
+ embedded systems, it may be worthwhile to build a
+ smaller custom kernel containing just the required
+ drivers.</para>
</answer>
</qandaentry>
@@ -1882,8 +1854,10 @@
</question>
<answer>
- <para>The default password format on &os; is to use
- <emphasis>MD5</emphasis>-based passwords. These are
+ <para>&os;&nbsp;7 and 8 use MD5 password hashing by
+ default. Recent versions
+ of &os; use <emphasis>SHA512</emphasis> by default.
+ These are
believed to be more secure than the traditional &unix;
password format, which used a scheme based on the
<emphasis>DES</emphasis> algorithm. DES passwords are still
@@ -2293,19 +2267,9 @@
support on Intel CPUs that support this feature. A kernel
with the <literal>options SMP</literal> feature enabled
will automatically detect the additional logical
- processors. The default &os; scheduler treats the logical
- processors the same as additional physical processors; in
- other words, no attempt is made to optimize scheduling
- decisions given the shared resources between logical
- processors within the same CPU. Because this naive
- scheduling can result in suboptimal performance, under
- certain circumstances it may be useful to disable the
- logical processors with the
- <varname>machdep.hlt_logical_cpus</varname> sysctl
- variable. It is also possible to halt any CPU in the idle
- loop with the <varname>machdep.hlt_cpus</varname> sysctl
- variable. The &man.smp.4; manual page has more
- details.</para>
+ processors.</para>
+
+ <para>&man.smp.4; has more details.</para>
</answer>
</qandaentry>
</qandaset>
@@ -4090,7 +4054,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<answer>
<para>The Open Group has released the source code to
- <application>&motif;&nbsp;2.2.2</application>. You can
+ <application>&motif;</application>. You can
install the <filename
role="package">x11-toolkits/open-motif</filename> package,
or compile it from ports. Refer to <ulink
@@ -5242,7 +5206,7 @@ use "disklabel -r" to install initial label</screen>
<term>ZFS</term>
<listitem>
- <para>As of this writing, &os; includes a port of
+ <para>&os; includes a port of
&sun;'s ZFS driver. The current recommendation is to
use it only on &arch.amd64; platforms with sufficient
memory. For more information, see &man.zfs.8;.</para>
@@ -7687,133 +7651,6 @@ Key F15 A A Menu Workplace Nop</programlisting>
</qandaentry>
<qandaentry>
- <question id="dec-pci-chipset">
- <para>Which network cards are based on the DEC PCI
- chipset?</para>
- </question>
-
- <answer>
- <para>Here is a list compiled by Glen Foster
- <email>gfoster@driver.nsta.org</email>, with some more
- modern additions:</para>
-
- <table>
- <title>Network Cards Based on the DEC PCI Chipset</title>
-
- <tgroup cols="2">
- <thead>
- <row>
- <entry>Vendor</entry>
-
- <entry>Model</entry>
- </row>
- </thead>
-
- <tbody>
- <row>
- <entry>ASUS</entry>
-
- <entry>PCI-L101-TB</entry>
- </row>
-
- <row>
- <entry>Accton</entry>
-
- <entry>ENI1203</entry>
- </row>
-
- <row>
- <entry>Cogent</entry>
-
- <entry>EM960PCI</entry>
- </row>
-
- <row>
- <entry>Compex</entry>
-
- <entry>ENET32-PCI</entry>
- </row>
-
- <row>
- <entry>D-Link</entry>
-
- <entry>DE-530</entry>
- </row>
-
- <row>
- <entry>Dayna</entry>
-
- <entry>DP1203, DP2100</entry>
- </row>
-
- <row>
- <entry>DEC</entry>
-
- <entry>DE435, DE450</entry>
- </row>
-
- <row>
- <entry>Danpex</entry>
-
- <entry>EN-9400P3</entry>
- </row>
-
- <row>
- <entry>JCIS</entry>
-
- <entry>Condor JC1260</entry>
- </row>
-
- <row>
- <entry>Linksys</entry>
-
- <entry>EtherPCI</entry>
- </row>
-
- <row>
- <entry>Mylex</entry>
-
- <entry>LNP101</entry>
- </row>
-
- <row>
- <entry>SMC</entry>
-
- <entry>EtherPower 10/100 (Model 9332)</entry>
- </row>
-
- <row>
- <entry>SMC</entry>
-
- <entry>EtherPower (Model 8432)</entry>
- </row>
-
- <row>
- <entry>TopWare</entry>
-
- <entry>TE-3500P</entry>
- </row>
-
- <row>
- <entry>Znyx (2.2.x)</entry>
-
- <entry>ZX312, ZX314, ZX342, ZX345, ZX346,
- ZX348</entry>
- </row>
-
- <row>
- <entry>Znyx (3.x)</entry>
-
- <entry>ZX345Q, ZX346Q, ZX348Q, ZX412Q, ZX414, ZX442,
- ZX444, ZX474, ZX478, ZX212, ZX214 (10mbps/hd)</entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="fqdn-hosts">
<para>Why do I have to use the FQDN for hosts on my
site?</para>
@@ -9243,92 +9080,6 @@ ATDT1234567</programlisting>
</qandaentry>
<qandaentry>
- <question id="useful-port-numbers">
- <para>Has anybody made a list of useful port numbers?</para>
- </question>
-
- <answer>
- <para>Not yet, but this is intended to grow into such a list
- (if any interest is shown). In each example,
- <replaceable>internal</replaceable> should be replaced with
- the IP number of the machine playing the game.</para>
-
- <itemizedlist>
- <listitem>
- <para><application>Asheron's Call</application></para>
-
- <para><literal>nat port udp
- <replaceable>internal</replaceable> :65000
- 65000</literal></para>
-
- <para>Manually change the port number within the game to
- <literal>65000</literal>. If you have got a number of
- machines that you wish to play on assign a unique port
- number for each (i.e. <literal>65001</literal>,
- <literal>65002</literal>, etc) and add a <literal>nat
- port</literal> line for each one.</para>
- </listitem>
-
- <listitem>
- <para><application>Half Life</application></para>
-
- <para><literal>nat port udp
- <replaceable>internal</replaceable>:27005
- 27015</literal></para>
- </listitem>
-
- <listitem>
- <para><application>PCAnywhere 8.0</application></para>
-
- <para><literal>nat port udp
- <replaceable>internal</replaceable>:5632
- 5632</literal></para>
-
- <para><literal>nat port tcp
- <replaceable>internal</replaceable>:5631
- 5631</literal></para>
- </listitem>
-
- <listitem>
- <para><application>Quake</application></para>
-
- <para><literal>nat port udp
- <replaceable>internal</replaceable>:6112
- 6112</literal></para>
- </listitem>
-
- <listitem>
- <para><application>Quake 2</application></para>
-
- <para><literal>nat port udp
- <replaceable>internal</replaceable>:27901
- 27910</literal></para>
-
- <para><literal>nat port udp
- <replaceable>internal</replaceable>:60021
- 60021</literal></para>
-
- <para><literal>nat port udp
- <replaceable>internal</replaceable>:60040
- 60040</literal></para>
- </listitem>
-
- <listitem>
- <para><application>Red Alert</application></para>
-
- <para><literal>nat port udp
- <replaceable>internal</replaceable>:8675
- 8675</literal></para>
-
- <para><literal>nat port udp
- <replaceable>internal</replaceable>:5009
- 5009</literal></para>
- </listitem>
- </itemizedlist>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="fcs-errors">
<para>What are FCS errors?</para>
</question>
@@ -9378,78 +9129,6 @@ ATDT1234567</programlisting>
</answer>
</qandaentry>
- <qandaentry id="PPPoEwithNAT">
- <question id="macos-win98-pppoe-freeze">
- <para>Why do &macos; and &windows;&nbsp;98 connections freeze
- when running PPPoE on the gateway?</para>
- </question>
-
- <answer>
- <para>Thanks to Michael Wozniak
- <email>mwozniak@netcom.ca</email> for figuring this out and
- Dan Flemming <email>danflemming@mac.com</email> for the Mac
- solution:</para>
-
- <para>This is due to what is called a <quote>Black
- Hole</quote> router. &macos; and &windows;&nbsp;98 (and maybe
- other &microsoft; OSs) send TCP packets with a requested
- segment size too big to fit into a PPPoE frame (MTU is
- <literal>1500</literal> by default for Ethernet)
- <emphasis>and</emphasis> have the <quote>do not
- fragment</quote> bit set (default of TCP) and the Telco
- router is not sending ICMP <quote>must fragment</quote> back
- to the WWW site you are trying to load. (Alternatively, the
- router is sending the ICMP packet correctly, but the
- firewall at the WWW site is dropping it.) When the www
- server is sending you frames that do not fit into the PPPoE
- pipe the Telco router drops them on the floor and your page
- does not load (some pages/graphics do as they are smaller
- than a MSS). This seems to be the default of most Telco
- PPPoE configurations.</para>
-
- <para>One fix is to use <application>regedit</application> on
- your 95/98 system to add the following registry entry:</para>
-
- <programlisting>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0000\MaxMTU</programlisting>
-
- <para>It should be a string with a value
- <literal>1436</literal>, as some ADSL routers are reported
- to be unable to deal with packets larger than this. This
- registry key has been changed to
- <literal>Tcpip\Parameters\Interfaces\<replaceable>ID for
- adapter</replaceable>\MTU</literal> in &windows;&nbsp;2000
- and becomes a <literal>DWORD</literal>.</para>
-
- <para>Refer to the Microsoft Knowledge Base documents <ulink
- url="http://support.microsoft.com/support/kb/articles/Q158/4/74.asp">Q158474 - Windows TCPIP Registry Entries</ulink>
- and <ulink
- url="http://support.microsoft.com/support/kb/articles/Q120/6/42.asp">Q120642 - TCPIP &amp; NBT Configuration Parameters for &windowsnt;</ulink>
- for more information on changing &windows; MTU to work with
- a NAT router.</para>
-
- <para>Another regedit possibility under &windows;&nbsp;2000 to
- set the <literal>Tcpip\Parameters\Interfaces\<replaceable>ID
- for adapter</replaceable>\EnablePMTUBHDetect</literal>
- <literal>DWORD</literal> to <literal>1</literal> as
- mentioned in the Microsoft document 120642 mentioned
- above.</para>
-
- <para>Unfortunately, &macos; does not provide an interface for
- changing TCP/IP settings. However, there are several commercial
- programs available that will allow users to customize TCP/IP
- settings. &macos; NAT users should search for their MTU
- settings and enter <literal>1450</literal> instead of
- <literal>1500</literal>.</para>
-
- <para>The &man.ppp.8; has an <command>enable
- tcpmssfixup</command> command that will automatically adjust
- the MSS to an appropriate value. This facility is enabled
- by default. If you are stuck with an older version of
- &man.ppp.8;, you may want to look at the <filename
- role="package">net/tcpmssd</filename> port.</para>
- </answer>
- </qandaentry>
-
<qandaentry>
<question id="desperation">
<para>None of this helps &mdash; I am desperate! What can I
@@ -10647,24 +10326,6 @@ hint.sio.7.irq="12"</programlisting>
</qandaentry>
<qandaentry>
- <question id="split-1392k">
- <para>How did you split the distribution into 1392&nbsp;KB
- files?</para>
- </question>
-
- <answer>
- <para>Newer BSD based systems have a <option>-b</option>
- option to &man.split.1; that allows them to split files on
- arbitrary byte boundaries.</para>
-
- <para>Here is an example from
- <filename>/usr/src/release/Makefile</filename>.</para>
-
- <programlisting>ZIPNSPLIT= gzip --no-name -9 -c | split -b 1392k -</programlisting>
- </answer>
- </qandaentry>
-
- <qandaentry>
<question id="submitting-kernel-extensions">
<para>I have written a kernel extension, who do I send it
to?</para>