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

* Remove some "remap=tt" from <emphasis>. In some cases, replace <emphasis>

Browse source 
with something more appropriate, like <command>

 * Fix up <address>.  White space within <address> *is* significant,
   so the translation teams will have to duplicate this change.

 * Remove some <para> and </para> tags that erroneously broke up some
   paragraphs into two or more paragraphs.

 * Correct some <literallayout>s to <programlisting>

 * Remove some <para>...</para>s that were wrapping elements that don't
   need them (like <itemizedlist>).

 * Convert examples to use <screen> and <userinput>.  Whitespace is
   significant, translators should be able to cut-n-paste the changes.

Haven't done the whole file yet, since I ran out of time.  More to
follow.
This commit is contained in:
Nik Clayton 2000-05-24 20:11:24 +00:00
parent 7056d587a8
commit b25a76ebcc
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7247
2 changed files with 662 additions and 360 deletions
en_US.ISO8859-1/books/faq
book.sgml
en_US.ISO_8859-1/books/faq
book.sgml

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

@ -13,7 +13,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.54 2000/05/07 16:48:51 joe Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.55 2000/05/23 00:44:07 nik Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -139,7 +139,7 @@
is being used in two ways here, one meaning ``at no cost'',
the other meaning ``you can do whatever you like''. Apart
from one or two things you
<emphasis remap=tt>cannot</emphasis> do with the FreeBSD code,
<emphasis>cannot</emphasis> do with the FreeBSD code,
for example pretending you wrote it, you really can do
whatever you like with it.</para>
</answer>
@ -437,46 +437,42 @@
<para>FreeBSD is also available via CDROM, from the following
place(s):</para>
<address>
<otheraddr>Walnut Creek CDROM</otheraddr>
<street>4041 Pike Lane, Suite F</street>
<city>Concord</city>, <state>CA</state> <postcode>94520</postcode>
<country>USA</country>
<address>Walnut Creek CDROM
<street>4041 Pike Lane, Suite F</street>
<city>Concord</city>, <state>CA</state>
<postcode>94520</postcode>
<country>USA</country>
<phone>Orders: +1 800 786-9907</phone>
<phone>Questions: +1 925 674-0783</phone>
<fax>FAX: +1 925 674-0821</fax>
<otheraddr>email: <ulink URL="mailto:orders@cdrom.com">WC Orders address</ulink></otheraddr>
<otheraddr>WWW: <ulink URL="http://www.cdrom.com/">WC Home page</ulink></otheraddr>
</address>
<phone>Orders: +1 800 786-9907</phone>
<phone>Questions: +1 925 674-0783</phone>
<fax>FAX: +1 925 674-0821</fax>
<otheraddr>email: <ulink URL="mailto:orders@cdrom.com">WC Orders address</ulink></otheraddr>
<otheraddr>WWW: <ulink URL="http://www.cdrom.com/">WC Home page</ulink></otheraddr></address>
<para>In Australia, you may find it at:</para>
<address>
<otheraddr>Advanced Multimedia Distributors</otheraddr>
<street>Factory 1/1 Ovata Drive</street>
<city>Tullamarine, Melbourne</city>
<state>Victoria</state>
<country>Australia</country>
<phone>Voice: +61 3 9338 6777</phone>
<address>Advanced Multimedia Distributors
<street>Factory 1/1 Ovata Drive</street>
<city>Tullamarine, Melbourne</city>
<state>Victoria</state>
<country>Australia</country>
<phone>Voice: +61 3 9338 6777</phone>
<otheraddr>CDROM Support BBS</otheraddr>
<street>17 Irvine St</street>
<city>Peppermint Grove</city>, <state>WA</state> <postcode>6011</postcode>
<phone>Voice: +61 9 385-3793</phone>
<fax>Fax: +61 9 385-2360</fax>
</address>
<otheraddr>CDROM Support BBS</otheraddr>
<street>17 Irvine St</street>
<city>Peppermint Grove</city>, <state>WA</state>
<postcode>6011</postcode>
<phone>Voice: +61 9 385-3793</phone>
<fax>Fax: +61 9 385-2360</fax></address>
<para>And in the UK:</para>
<address>
<otheraddr>The Public Domain &amp; Shareware Library</otheraddr>
<street>Winscombe House, Beacon Rd</street>
<city>Crowborough</city>
<state>Sussex. TN6 1UL</state>
<phone>Voice: +44 1892 663-298</phone>
<fax>Fax: +44 1892 667-473</fax>
</address>
<address>The Public Domain &amp; Shareware Library
<street>Winscombe House, Beacon Rd</street>
<city>Crowborough</city>
<state>Sussex. TN6 1UL</state>
<phone>Voice: +44 1892 663-298</phone>
<fax>Fax: +44 1892 667-473</fax></address>
</answer>
</qandaentry>
@ -645,9 +641,9 @@
</listitem>
</itemizedlist>
<para>A description of these can be found via WWW as:</para>
<para>A description of these can be found via WWW as:
<para><ulink
<ulink
URL="http://gnn.com/gnn/bus/ora/category/bsd.html">4.4BSD
books description</ulink>. Due to poor sales, however, these
manuals may be hard to get a hold of.</para>
@ -1014,17 +1010,17 @@ File: +DESC (ignored)</screen>
<para>Certainly! There are multiple ways to mirror the Web
pages.</para>
<para>
<itemizedlist>
<listitem>
<para>Using CVSUP: You can retrieve the formatted files
using CVSUP from cvsup.FreeBSD.org. Add this line to
your cvsup file:
your cvsup file:</para>
<literallayout>
<programlisting>
www release=current hostname=/home base=/usr/local/etc/cvsup
prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</literallayout></para>
prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</programlisting>
</listitem>
<listitem>
@ -1040,7 +1036,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</literallay
publishing them. Simply start at
ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www.</para>
</listitem>
</itemizedlist></para>
</itemizedlist>
</answer>
</qandaentry>
@ -1066,7 +1062,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</literallay
<para>The following newsgroups contain pertinent discussion for
FreeBSD users:</para>
<para>
<itemizedlist>
<listitem>
@ -1084,11 +1080,11 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</literallay
<para><ulink
URL="news:comp.unix.bsd.misc">comp.unix.bsd.misc</ulink></para>
</listitem>
</itemizedlist></para>
</itemizedlist>
<para>Web resources:</para>
<para>
<itemizedlist>
<listitem>
@ -1116,7 +1112,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</literallay
URL="http://people.FreeBSD.org/~ahasty/Bt848.html">Bt848</ulink>
video capture chip, then follow that link.</para>
</listitem>
</itemizedlist></para>
</itemizedlist>
<para>The FreeBSD handbook also has a fairly complete <ulink
URL="../handbook/bibliography.html">bibliography</ulink>
@ -1149,7 +1145,7 @@ copied onto floppies by tools like <command>fdimage</command> or
filesystem install, for instance), below are some recommendations
for distributions to grab:</para>
<para>
<itemizedlist>
<listitem>
@ -1173,7 +1169,7 @@ for distributions to grab:</para>
</listitem>
</itemizedlist>
</para>
<para>Full instructions on this procedure and a little bit more about
installation issues in general can be found in the <ulink URL="../handbook/install.html">Handbook entry on installing FreeBSD.</ulink></para>
@ -1187,42 +1183,42 @@ installation issues in general can be found in the <ulink URL="../handbook/insta
<para>A 3.5 inch (1.44MB) floppy can accomodate 1474560 bytes of data.
The boot image is exactly 1474560 bytes in size.</para>
<para>Common mistakes when preparing the boot floppy are:
<para>Common mistakes when preparing the boot floppy are:</para>
<itemizedlist>
<listitem>
<para>Not downloading the floppy image in <emphasis remap=tt>binary</emphasis> mode when
using <acronym>FTP</acronym>.
</para>
<para>Not downloading the floppy image in <emphasis>binary</emphasis> mode when
using <acronym>FTP</acronym>.</para>
<para>Some FTP clients default their transfer mode to <emphasis remap=tt>ascii</emphasis>
<para>Some FTP clients default their transfer mode to <emphasis>ascii</emphasis>
and attempt to change any end-of-line characters received to match
the conventions used by the client's system.
This will almost invariably corrupt the boot image. Check the
size of the downloaded boot image: if it is not <emphasis>exactly</emphasis>
that on the server, then the download process is suspect.</para>
<para>To workaround: type <emphasis remap=tt>binary</emphasis> at the FTP command prompt
<para>To workaround: type <emphasis>binary</emphasis> at the FTP command prompt
after getting connected to the server and before starting the
download of the image.</para>
</listitem>
<listitem>
<para>Using the DOS <emphasis remap=tt>copy</emphasis> command (or equivalent GUI tool) to
<para>Using the DOS <command>copy</command> command (or equivalent GUI tool) to
transfer the boot image to floppy.
</para>
<para>Programs like <emphasis remap=tt>copy</emphasis> will not work as the boot
<para>Programs like <command>copy</command> will not work as the boot
image has been created to be booted into directly. The image has
the complete content of the floppy, track for track, and is not
meant to be placed on the floppy as a regular file.
You have to transfer it to the floppy ``raw'', using the
low-level tools (e.g. <emphasis remap=tt>fdimage</emphasis> or <emphasis remap=tt>rawrite</emphasis>)
low-level tools (e.g. <command>fdimage</command> or <command>rawrite</command>)
described in the <ulink URL="../handbook/install.html">installation guide to FreeBSD</ulink>.</para>
</listitem>
</itemizedlist>
</para>
</answer></qandaentry>
@ -1252,7 +1248,7 @@ graphics card but to run X11R6, a VGA or better video card is needed.</para>
on a 4MB system. Newer versions of FreeBSD, like 2.2, need at least 5MB
to install on a new system.</para>
<para>All versions of FreeBSD, including 3.0, will RUN in 4MB of ram, they
<para>All versions of FreeBSD, including 3.0, will <emphasis>run</emphasis> in 4MB of RAM, they
just can't run the installation program in 4MB. You can add
extra memory for the install process, if you like, and then
after the system is up and running, go back to 4MB. Or you could
@ -1285,10 +1281,10 @@ system was almost unusable though :-))</para>
<para> How can I make my own custom install floppy?
</para></question><answer>
<para>Currently there's no way to *just* make a custom install floppy.
<para>Currently there's 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. There's some code in <filename>/usr/src/release/floppies/Makefile</filename>
that's supposed to let you *just* make those floppies, but it's not
that's supposed to let you <emphasis>just</emphasis> make those floppies, but it's not
really gelled yet.</para>
<para>To make a custom release, follow the instructions <link linkend="custrel">here</link>.</para>
@ -1320,7 +1316,7 @@ the next section.</para>
<para>You can reinstall the boot manager FreeBSD comes with in one of
two ways:</para>
<para>
<itemizedlist>
<listitem>
@ -1329,7 +1325,7 @@ distribution and look for <filename>bootinst.exe</filename>. You run it like so
</para>
<para><emphasis remap=bf>bootinst.exe boot.bin</emphasis></para>
<screen><prompt>...\TOOLS&gt;</prompt> <userinput>bootinst.exe boot.bin</userinput></screen>
<para></para>
@ -1351,7 +1347,7 @@ installation menu and reboot off the hard disk as normal.</para>
</listitem>
</itemizedlist>
</para>
</answer></qandaentry>
@ -1376,7 +1372,7 @@ you'd do well to try it first before simply giving up.</para>
spontaneously rebooting when you try to boot the install floppy,
here are three questions to ask yourself:-</para>
<para>
<orderedlist>
<listitem>
@ -1404,7 +1400,7 @@ shell in the GUI can cause this problem.</para>
</listitem>
</orderedlist>
</para>
<para>There have also been reports of Netscape causing problems when
downloading the boot floppy, so it's probably best to use a different
@ -1431,13 +1427,10 @@ too big.</para>
<para>Get a laplink cable. Make sure both computer have a kernel
with lpt driver support.</para>
<para>
<literallayout> $ dmesg | grep lp
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
</literallayout>
</para>
<screen>&prompt.root; <userinput>dmesg | grep lp</userinput>
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven
lp0: TCP/IP capable interface</screen>
<para>Plug in the laplink cable into the parallel interface.</para>
@ -1451,54 +1444,44 @@ IP Address 10.0.0.1 10.0.0.2
</literallayout>
</para>
<para>on max start
<literallayout> # ifconfig lp0 10.0.0.1 10.0.0.2
</literallayout>
</para>
<para>on max start</para>
<screen>&prompt.root; <userinput>ifconfig lp0 10.0.0.1 10.0.0.2</userinput></screen>
<para>on moritz start</para>
<para>
<literallayout> # ifconfig lp0 10.0.0.2 10.0.0.1
</literallayout>
</para>
<para>Thats all! Please read also the manpages
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?lp(4)">lp(4)
</ulink> and
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?lpt(4)">lpt(4)
</ulink>.</para>
<screen>&prompt.root; <userinput>ifconfig lp0 10.0.0.2 10.0.0.1</userinput></screen>
<para>Thats all! Please read also the manpages
&man.lp.4;
and
&man.lpt.4;
.</para>
<para>You should also add the hosts to <filename>/etc/hosts</filename>.</para>
<para>
<literallayout> 127.0.0.1 localhost.my.domain localhost
10.0.0.1 max.my.domain max
10.0.0.2 moritz.my.domain moritz
</literallayout>
</para>
<programlisting>127.0.0.1 localhost.my.domain localhost
10.0.0.1 max.my.domain max
10.0.0.2 moritz.my.domain</programlisting>
<para>To check if it works do:</para>
<para>on max:</para>
<para>
<literallayout>$ ifconfig lp0
lp0: flags=8851&lt;UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
inet 10.0.0.1 --&gt; 10.0.0.2 netmask 0xff000000 </literallayout>
</para>
<para>
<literallayout>$ netstat -r
<screen>&prompt.root; <userinput>ifconfig lp</userinput>0
lp0: flags=8851&lt;UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
inet 10.0.0.1 --&gt; 10.0.0.2 netmask 0xff000000
&prompt.root; <userinput>netstat -r</userinput>
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
moritz max UH 4 127592 lp0</literallayout>
</para>
<para>
<literallayout>$ ping -c 4 moritz
Destination Gateway Flags Refs Use Netif Expire
moritz max UH 4 127592 lp0
&prompt.root; <userinput>ping -c 4 moritz</userinput>
PING moritz (10.0.0.2): 56 data bytes
64 bytes from 10.0.0.2: icmp_seq=0 ttl=255 time=2.774 ms
64 bytes from 10.0.0.2: icmp_seq=1 ttl=255 time=2.530 ms
@ -1507,8 +1490,8 @@ PING moritz (10.0.0.2): 56 data bytes
--- moritz ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</literallayout>
</para>
round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
</answer></qandaentry>
@ -1519,29 +1502,119 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</literallayout>
<para>Connect the two computers using a Laplink parallel cable to use
this feature:</para>
<para>
<literallayout> +----------------------------------------+
|A-name A-End B-End Descr. Port/Bit |
+----------------------------------------+
|DATA0 2 15 Data 0/0x01 |
|-ERROR 15 2 1/0x08 |
+----------------------------------------+
|DATA1 3 13 Data 0/0x02 |
|+SLCT 13 3 1/0x10 |
+----------------------------------------+
|DATA2 4 12 Data 0/0x04 |
|+PE 12 4 1/0x20 |
+----------------------------------------+
|DATA3 5 10 Strobe 0/0x08 |
|-ACK 10 5 1/0x40 |
+----------------------------------------+
|DATA4 6 11 Data 0/0x10 |
|BUSY 11 6 1/0x80 |
+----------------------------------------+
|GND 18-25 18-25 GND - |
+----------------------------------------+
</literallayout>
</para>
<table>
<title>Wiring a parallel cable for networking</title>
<tgroup cols="5">
<thead>
<row>
<entry>A-name</entry>
<entry>A-End</entry>
<entry>B-End</entry>
<entry>Descr.</entry>
<entry>Post/Bit</entry>
</row>
</thead>
<tbody>
<row>
<entry><literallayout>DATA0
-ERROR</literallayout></entry>
<entry><literallayout>2
15</literallayout></entry>
<entry><literallayout>15
2</literallayout></entry>
<entry>Data</entry>
<entry><literallayout>0/0x01
1/0x08</literallayout></entry>
</row>
<row>
<entry><literallayout>DATA1
+SLCT</literallayout></entry>
<entry><literallayout>3
13</literallayout></entry>
<entry><literallayout>13
3</literallayout></entry>
<entry>Data</entry>
<entry><literallayout>0/0x02
1/0x10</literallayout></entry>
</row>
<row>
<entry><literallayout>DATA2
+PE</literallayout></entry>
<entry><literallayout>4
12</literallayout></entry>
<entry><literallayout>12
4</literallayout></entry>
<entry>Data</entry>
<entry><literallayout>0/0x04
1/0x20</literallayout></entry>
</row>
<row>
<entry><literallayout>DATA3
-ACK</literallayout></entry>
<entry><literallayout>5
10</literallayout></entry>
<entry><literallayout>10
5</literallayout></entry>
<entry>Strobe</entry>
<entry><literallayout>0/0x08
1/0x40</literallayout></entry>
</row>
<row>
<entry><literallayout>DATA4
BUSY</literallayout></entry>
<entry><literallayout>6
11</literallayout></entry>
<entry><literallayout>11
6</literallayout></entry>
<entry>Data</entry>
<entry><literallayout>0/0x10
1/0x80</literallayout></entry>
</row>
<row>
<entry>GND</entry>
<entry>18-25</entry>
<entry>18-25</entry>
<entry>GND</entry>
<entry>-</entry>
</row>
</tbody>
</tgroup>
</table>
<para>See also <link linkend="pao">this note</link> on the Mobile Computing page.</para>
@ -1558,7 +1631,7 @@ C/H/S for convenience. This is how the PC's BIOS works out
which area on a disk to read/write from).</para>
<para>This seems to cause a lot of confusion for some reason. First
of all, the <emphasis remap=tt>physical</emphasis> geometry of a SCSI drive is totally
of all, the <emphasis>physical</emphasis> geometry of a SCSI drive is totally
irrelevant, as FreeBSD works in term of disk blocks. In fact, there
is no such thing as "the" physical geometry, as the sector density
varies across the disk - what manufacturers claim is the "true"
@ -1567,7 +1640,7 @@ results in the least wasted space. For IDE disks, FreeBSD does
work in terms of C/H/S, but all modern drives will convert this
into block references internally as well.</para>
<para>All that matters is the <emphasis remap=tt>logical</emphasis> geometry - the answer that the
<para>All that matters is the <emphasis>logical</emphasis> geometry - the answer that the
BIOS gets when it asks "what is your geometry?" and then uses to access
the disk. As FreeBSD uses the BIOS when booting, it's very important
to get this right. In particular, if you have more than one operating
@ -1582,7 +1655,7 @@ and 32 sectors/track, where 'N' is the capacity of the disk in
MB. For example, a 2GB disk should pretend to have 2048 cylinders,
64 heads and 32 sectors/track.</para>
<para>If it <emphasis remap=tt>is</emphasis> turned on (it's often supplied this way to get around
<para>If it <emphasis>is</emphasis> turned on (it's often supplied this way to get around
certain limitations in MSDOS) and the disk capacity is more than 1GB,
use M cylinders, 63 sectors per track (*not* 64), and 255 heads, where
'M' is the disk capacity in MB divided by 7.844238 (!). So our
@ -1597,7 +1670,7 @@ the DOS partition in the partition editor if you don't want to keep
it, or leave it around for programming network cards and the like).</para>
<para>Alternatively, there is a freely available utility distributed with
FreeBSD called ``<filename>pfdisk.exe</filename>'' (located in the <emphasis remap=tt>tools</emphasis>
FreeBSD called ``<filename>pfdisk.exe</filename>'' (located in the <filename>tools</filename>
subdirectory on the FreeBSD CDROM or on the various FreeBSD
ftp sites) which can be used to work out what geometry the other
operating systems on the disk are using. You can then enter this
@ -1691,8 +1764,7 @@ includes several of the files mentioned here, and the
kernel. There is nothing in the system which requires the
presence of the sources to operate, however, except for the
kernel-configuration program
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?config(8)">config
</ulink>. With the exception
&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. (Because of the kernel-source
@ -1736,16 +1808,16 @@ systems.</para>
<para>If it is not absolutely imperative that you use DES style
encryption, you can use FreeBSD's default encryption for even
<emphasis remap=bf>better</emphasis> security, and with no export restrictions. FreeBSD
2.0's password default scrambler is now <emphasis remap=bf>MD5</emphasis>-based, and is
<emphasis>better</emphasis> security, and with no export restrictions. FreeBSD
2.0's password default scrambler is now <emphasis>MD5</emphasis>-based, and is
more CPU-intensive to crack with an automated password cracker
than DES, and allows longer passwords as well. The only reason
for not using the <emphasis remap=bf>MD5</emphasis>-based crypt today would be to use the
for not using the <emphasis>MD5</emphasis>-based crypt today would be to use the
the same password entries on FreeBSD and non-FreeBSD systems.</para>
<para>Since the DES encryption algorithm cannot legally be exported
from the US, non-US users should not download this software (as
part of the <emphasis remap=tt>secrdist</emphasis> from US FTP sites.</para>
part of the <literal>secrdist</literal> from US FTP sites.</para>
<para>There is however a replacement libcrypt available, based on
sources written in Australia by David Burren. This code is now
@ -1753,40 +1825,40 @@ available on some non-US FreeBSD mirror sites. Sources for the
unencumbered libcrypt, and binaries of the programs which use it,
can be obtained from the following FTP sites:</para>
<para>
<variablelist>
<varlistentry><term>South Africa</term>
<listitem>
<para><filename>ftp://ftp.internat.FreeBSD.org/pub/FreeBSD</filename><!-- <br> -->
<filename>ftp://storm.sea.uct.ac.za/pub/FreeBSD</filename></para>
<para></para>
<segmentedlist>
<seglistitem><seg>South Africa</seg>
<seg>
<ulink url="ftp://ftp.internat.FreeBSD.org/pub/FreeBSD/">ftp://ftp.internat.FreeBSD.org/pub/FreeBSD/</ulink>,
<ulink url="ftp://storm.sea.uct.ac.za/pub/FreeBSD/">ftp://storm.sea.uct.ac.za/pub/FreeBSD/</ulink>
</listitem>
</varlistentry>
<varlistentry><term>Brazil</term>
<listitem>
<para><filename>ftp://ftp.iqm.unicamp.br/pub/FreeBSD</filename></para>
</seg>
</seglistitem>
<para></para>
<seglistitem><seg>Brazil</seg>
</listitem>
</varlistentry>
<varlistentry><term>Finland</term>
<seg><ulink url="ftp://ftp.iqm.unicamp.br/pub/FreeBSD/">ftp://ftp.iqm.unicamp.br/pub/FreeBSD/</ulink></seg>
<listitem>
<para><filename>ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt</filename></para>
</listitem>
</varlistentry>
</variablelist>
</para>
<para>The non-US <emphasis remap=tt>securedist</emphasis> can be used as a direct replacement
for the encumbered US <emphasis remap=tt>securedist</emphasis>. This <emphasis remap=tt>securedist</emphasis>
</seglistitem>
<seglistitem><seg>Finland</seg>
<seg>
<ulink url="ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt/">ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt/</ulink>
</seg>
</seglistitem>
</segmentedlist>
<para>The non-US <emphasis>securedist</emphasis> can be used as a direct replacement
for the encumbered US <emphasis>securedist</emphasis>. This <emphasis>securedist</emphasis>
package is installed the same way as the US package (see
installation notes for details). If you are going to install DES
encryption, you should do so as soon as possible, before
@ -1798,14 +1870,12 @@ which the software is downloaded into severe legal difficulties.</para>
<para>A non-US distribution of Kerberos is also being developed, and
current versions can generally be obtained by anonymous FTP from
<filename>braae.ru.ac.za</filename>.</para>
<hostid role="fqdn">braae.ru.ac.za</hostid>.</para>
<para>There is also a <link linkend="mailing">mailing list</link> for the
discussion of non-US encryption software. For more information, send
an email message with a single line saying ``<emphasis remap=tt>help</emphasis>'' in the body
of your message to</para>
<para><email>majordomo@braae.ru.ac.za</email>.</para>
an email message with a single line saying ``<literal>help</literal>'' in the body
of your message to <email>majordomo@braae.ru.ac.za</email>.</para>
</answer></qandaentry>
@ -1843,11 +1913,11 @@ think is the boot disk, wd1, while it is really wd2, and fails.</para>
&quot;Enter&quot; at the &quot;Booting kernel in 10 seconds; hit
[Enter] to interrupt&quot; prompt. This will drop you into the boot
loader.</para>
<para>Then type set
root_disk_unit="&lt;disk_number&gt;". <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
<para>Then type <literal>set
root_disk_unit="<replaceable>disk_number</replaceable>"</literal>. <replaceable>disk_number</replaceable>
will be <literal>0</literal> if FreeBSD is installed on the master drive
on the first IDE controller, <literal>1</literal> if it is installed
on the slave on the first IDE controller, <literal>2</literal> 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>
@ -1855,15 +1925,15 @@ IDE controller.</para>
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
&quot;root_disk_unit="&lt;disk_number&gt;" in
<literal>root_disk_unit="<replaceable>disk_number</replaceable>"</literal> 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
<literal>1:wd(2,a)kernel</literal> and press Enter. If the system starts, then
run the command
<literallayout>echo "1:wd(2,a)kernel" &gt; /boot.config</literallayout>
<literal>echo "1:wd(2,a)kernel" &gt; /boot.config</literal>
to make it the default boot string.</para>
</listitem>
@ -1875,18 +1945,18 @@ hard disks are consecutive.</para>
<listitem>
<para><ulink URL="../handbook/kernelconfig.html">Rebuild your kernel,</ulink>
modify the wd configuration lines to read:
modify the wd configuration lines to read:</para>
<literallayout>controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr
<programlisting>controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wdc0 drive 0
# disk wd1 at wdc0 drive 1 # comment out this line
controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr
disk wd1 at wdc1 drive 0 # change from wd2 to wd1
disk wd2 at wdc1 drive 1 # change from wd3 to wd2</literallayout>
disk wd2 at wdc1 drive 1 # change from wd3 to wd2</programlisting>
Install the new kernel.
<para>Install the new kernel.
If you moved your disks and wish to restore the previous
configuration, replace the disks in the desired configuration and reboot.
Your system should boot successfully.
@ -1922,6 +1992,87 @@ filesystems with 4 terabytes are possible (and exist).</para>
<para>The maximum size of a single ffs file is approximately 1G blocks
(4TB) if the block size is 4K.</para>
<table>
<title>Maximum file sizes</title>
<tgroup cols="5">
<thead>
<row>
<entry>fs block size</entry>
<entry>2.2.7-stable</entry>
<entry>3.0-current</entry>
<entry>works</entry>
<entry>should work</entry>
</row>
</thead>
<tbody>
<row>
<entry>4K</entry>
<entry>4T-1</entry>
<entry>4T-1</entry>
<entry>4T-1</entry>
<entry>4+t</entry>
</row>
<row>
<entry>8K</entry>
<entry>32+G</entry>
<entry>8T-1</entry>
<entry>32+G</entry>
<entry>32T-1</entry>
</row>
<row>
<entry>16K</entry>
<entry>128+G</entry>
<entry>16T-1</entry>
<entry>128+G</entry>
<entry>32T-1</entry>
</row>
<row>
<entry>32K</entry>
<entry>512+G</entry>
<entry>32T-1</entry>
<entry>512+G</entry>
<entry>64T-1</entry>
</row>
<row>
<entry>64K</entry>
<entry>2048+G</entry>
<entry>64T-1</entry>
<entry>2048+G</entry>
<entry>128T-1</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
<literallayout> maxfilesize
----------------------------------

511
en_US.ISO_8859-1/books/faq/book.sgml
View file

@ -13,7 +13,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.54 2000/05/07 16:48:51 joe Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.55 2000/05/23 00:44:07 nik Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -139,7 +139,7 @@
is being used in two ways here, one meaning ``at no cost'',
the other meaning ``you can do whatever you like''. Apart
from one or two things you
<emphasis remap=tt>cannot</emphasis> do with the FreeBSD code,
<emphasis>cannot</emphasis> do with the FreeBSD code,
for example pretending you wrote it, you really can do
whatever you like with it.</para>
</answer>
@ -437,46 +437,42 @@
<para>FreeBSD is also available via CDROM, from the following
place(s):</para>
<address>
<otheraddr>Walnut Creek CDROM</otheraddr>
<street>4041 Pike Lane, Suite F</street>
<city>Concord</city>, <state>CA</state> <postcode>94520</postcode>
<country>USA</country>
<address>Walnut Creek CDROM
<street>4041 Pike Lane, Suite F</street>
<city>Concord</city>, <state>CA</state>
<postcode>94520</postcode>
<country>USA</country>
<phone>Orders: +1 800 786-9907</phone>
<phone>Questions: +1 925 674-0783</phone>
<fax>FAX: +1 925 674-0821</fax>
<otheraddr>email: <ulink URL="mailto:orders@cdrom.com">WC Orders address</ulink></otheraddr>
<otheraddr>WWW: <ulink URL="http://www.cdrom.com/">WC Home page</ulink></otheraddr>
</address>
<phone>Orders: +1 800 786-9907</phone>
<phone>Questions: +1 925 674-0783</phone>
<fax>FAX: +1 925 674-0821</fax>
<otheraddr>email: <ulink URL="mailto:orders@cdrom.com">WC Orders address</ulink></otheraddr>
<otheraddr>WWW: <ulink URL="http://www.cdrom.com/">WC Home page</ulink></otheraddr></address>
<para>In Australia, you may find it at:</para>
<address>
<otheraddr>Advanced Multimedia Distributors</otheraddr>
<street>Factory 1/1 Ovata Drive</street>
<city>Tullamarine, Melbourne</city>
<state>Victoria</state>
<country>Australia</country>
<phone>Voice: +61 3 9338 6777</phone>
<address>Advanced Multimedia Distributors
<street>Factory 1/1 Ovata Drive</street>
<city>Tullamarine, Melbourne</city>
<state>Victoria</state>
<country>Australia</country>
<phone>Voice: +61 3 9338 6777</phone>
<otheraddr>CDROM Support BBS</otheraddr>
<street>17 Irvine St</street>
<city>Peppermint Grove</city>, <state>WA</state> <postcode>6011</postcode>
<phone>Voice: +61 9 385-3793</phone>
<fax>Fax: +61 9 385-2360</fax>
</address>
<otheraddr>CDROM Support BBS</otheraddr>
<street>17 Irvine St</street>
<city>Peppermint Grove</city>, <state>WA</state>
<postcode>6011</postcode>
<phone>Voice: +61 9 385-3793</phone>
<fax>Fax: +61 9 385-2360</fax></address>
<para>And in the UK:</para>
<address>
<otheraddr>The Public Domain &amp; Shareware Library</otheraddr>
<street>Winscombe House, Beacon Rd</street>
<city>Crowborough</city>
<state>Sussex. TN6 1UL</state>
<phone>Voice: +44 1892 663-298</phone>
<fax>Fax: +44 1892 667-473</fax>
</address>
<address>The Public Domain &amp; Shareware Library
<street>Winscombe House, Beacon Rd</street>
<city>Crowborough</city>
<state>Sussex. TN6 1UL</state>
<phone>Voice: +44 1892 663-298</phone>
<fax>Fax: +44 1892 667-473</fax></address>
</answer>
</qandaentry>
@ -645,9 +641,9 @@
</listitem>
</itemizedlist>
<para>A description of these can be found via WWW as:</para>
<para>A description of these can be found via WWW as:
<para><ulink
<ulink
URL="http://gnn.com/gnn/bus/ora/category/bsd.html">4.4BSD
books description</ulink>. Due to poor sales, however, these
manuals may be hard to get a hold of.</para>
@ -1014,17 +1010,17 @@ File: +DESC (ignored)</screen>
<para>Certainly! There are multiple ways to mirror the Web
pages.</para>
<para>
<itemizedlist>
<listitem>
<para>Using CVSUP: You can retrieve the formatted files
using CVSUP from cvsup.FreeBSD.org. Add this line to
your cvsup file:
your cvsup file:</para>
<literallayout>
<programlisting>
www release=current hostname=/home base=/usr/local/etc/cvsup
prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</literallayout></para>
prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</programlisting>
</listitem>
<listitem>
@ -1040,7 +1036,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</literallay
publishing them. Simply start at
ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/www.</para>
</listitem>
</itemizedlist></para>
</itemizedlist>
</answer>
</qandaentry>
@ -1066,7 +1062,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</literallay
<para>The following newsgroups contain pertinent discussion for
FreeBSD users:</para>
<para>
<itemizedlist>
<listitem>
@ -1084,11 +1080,11 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</literallay
<para><ulink
URL="news:comp.unix.bsd.misc">comp.unix.bsd.misc</ulink></para>
</listitem>
</itemizedlist></para>
</itemizedlist>
<para>Web resources:</para>
<para>
<itemizedlist>
<listitem>
@ -1116,7 +1112,7 @@ prefix=/usr/local/www/data/www.FreeBSD.org delete old use-rel-suffix</literallay
URL="http://people.FreeBSD.org/~ahasty/Bt848.html">Bt848</ulink>
video capture chip, then follow that link.</para>
</listitem>
</itemizedlist></para>
</itemizedlist>
<para>The FreeBSD handbook also has a fairly complete <ulink
URL="../handbook/bibliography.html">bibliography</ulink>
@ -1149,7 +1145,7 @@ copied onto floppies by tools like <command>fdimage</command> or
filesystem install, for instance), below are some recommendations
for distributions to grab:</para>
<para>
<itemizedlist>
<listitem>
@ -1173,7 +1169,7 @@ for distributions to grab:</para>
</listitem>
</itemizedlist>
</para>
<para>Full instructions on this procedure and a little bit more about
installation issues in general can be found in the <ulink URL="../handbook/install.html">Handbook entry on installing FreeBSD.</ulink></para>
@ -1187,42 +1183,42 @@ installation issues in general can be found in the <ulink URL="../handbook/insta
<para>A 3.5 inch (1.44MB) floppy can accomodate 1474560 bytes of data.
The boot image is exactly 1474560 bytes in size.</para>
<para>Common mistakes when preparing the boot floppy are:
<para>Common mistakes when preparing the boot floppy are:</para>
<itemizedlist>
<listitem>
<para>Not downloading the floppy image in <emphasis remap=tt>binary</emphasis> mode when
using <acronym>FTP</acronym>.
</para>
<para>Not downloading the floppy image in <emphasis>binary</emphasis> mode when
using <acronym>FTP</acronym>.</para>
<para>Some FTP clients default their transfer mode to <emphasis remap=tt>ascii</emphasis>
<para>Some FTP clients default their transfer mode to <emphasis>ascii</emphasis>
and attempt to change any end-of-line characters received to match
the conventions used by the client's system.
This will almost invariably corrupt the boot image. Check the
size of the downloaded boot image: if it is not <emphasis>exactly</emphasis>
that on the server, then the download process is suspect.</para>
<para>To workaround: type <emphasis remap=tt>binary</emphasis> at the FTP command prompt
<para>To workaround: type <emphasis>binary</emphasis> at the FTP command prompt
after getting connected to the server and before starting the
download of the image.</para>
</listitem>
<listitem>
<para>Using the DOS <emphasis remap=tt>copy</emphasis> command (or equivalent GUI tool) to
<para>Using the DOS <command>copy</command> command (or equivalent GUI tool) to
transfer the boot image to floppy.
</para>
<para>Programs like <emphasis remap=tt>copy</emphasis> will not work as the boot
<para>Programs like <command>copy</command> will not work as the boot
image has been created to be booted into directly. The image has
the complete content of the floppy, track for track, and is not
meant to be placed on the floppy as a regular file.
You have to transfer it to the floppy ``raw'', using the
low-level tools (e.g. <emphasis remap=tt>fdimage</emphasis> or <emphasis remap=tt>rawrite</emphasis>)
low-level tools (e.g. <command>fdimage</command> or <command>rawrite</command>)
described in the <ulink URL="../handbook/install.html">installation guide to FreeBSD</ulink>.</para>
</listitem>
</itemizedlist>
</para>
</answer></qandaentry>
@ -1252,7 +1248,7 @@ graphics card but to run X11R6, a VGA or better video card is needed.</para>
on a 4MB system. Newer versions of FreeBSD, like 2.2, need at least 5MB
to install on a new system.</para>
<para>All versions of FreeBSD, including 3.0, will RUN in 4MB of ram, they
<para>All versions of FreeBSD, including 3.0, will <emphasis>run</emphasis> in 4MB of RAM, they
just can't run the installation program in 4MB. You can add
extra memory for the install process, if you like, and then
after the system is up and running, go back to 4MB. Or you could
@ -1285,10 +1281,10 @@ system was almost unusable though :-))</para>
<para> How can I make my own custom install floppy?
</para></question><answer>
<para>Currently there's no way to *just* make a custom install floppy.
<para>Currently there's 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. There's some code in <filename>/usr/src/release/floppies/Makefile</filename>
that's supposed to let you *just* make those floppies, but it's not
that's supposed to let you <emphasis>just</emphasis> make those floppies, but it's not
really gelled yet.</para>
<para>To make a custom release, follow the instructions <link linkend="custrel">here</link>.</para>
@ -1320,7 +1316,7 @@ the next section.</para>
<para>You can reinstall the boot manager FreeBSD comes with in one of
two ways:</para>
<para>
<itemizedlist>
<listitem>
@ -1329,7 +1325,7 @@ distribution and look for <filename>bootinst.exe</filename>. You run it like so
</para>
<para><emphasis remap=bf>bootinst.exe boot.bin</emphasis></para>
<screen><prompt>...\TOOLS&gt;</prompt> <userinput>bootinst.exe boot.bin</userinput></screen>
<para></para>
@ -1351,7 +1347,7 @@ installation menu and reboot off the hard disk as normal.</para>
</listitem>
</itemizedlist>
</para>
</answer></qandaentry>
@ -1376,7 +1372,7 @@ you'd do well to try it first before simply giving up.</para>
spontaneously rebooting when you try to boot the install floppy,
here are three questions to ask yourself:-</para>
<para>
<orderedlist>
<listitem>
@ -1404,7 +1400,7 @@ shell in the GUI can cause this problem.</para>
</listitem>
</orderedlist>
</para>
<para>There have also been reports of Netscape causing problems when
downloading the boot floppy, so it's probably best to use a different
@ -1431,13 +1427,10 @@ too big.</para>
<para>Get a laplink cable. Make sure both computer have a kernel
with lpt driver support.</para>
<para>
<literallayout> $ dmesg | grep lp
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
</literallayout>
</para>
<screen>&prompt.root; <userinput>dmesg | grep lp</userinput>
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven
lp0: TCP/IP capable interface</screen>
<para>Plug in the laplink cable into the parallel interface.</para>
@ -1451,54 +1444,44 @@ IP Address 10.0.0.1 10.0.0.2
</literallayout>
</para>
<para>on max start
<literallayout> # ifconfig lp0 10.0.0.1 10.0.0.2
</literallayout>
</para>
<para>on max start</para>
<screen>&prompt.root; <userinput>ifconfig lp0 10.0.0.1 10.0.0.2</userinput></screen>
<para>on moritz start</para>
<para>
<literallayout> # ifconfig lp0 10.0.0.2 10.0.0.1
</literallayout>
</para>
<para>Thats all! Please read also the manpages
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?lp(4)">lp(4)
</ulink> and
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?lpt(4)">lpt(4)
</ulink>.</para>
<screen>&prompt.root; <userinput>ifconfig lp0 10.0.0.2 10.0.0.1</userinput></screen>
<para>Thats all! Please read also the manpages
&man.lp.4;
and
&man.lpt.4;
.</para>
<para>You should also add the hosts to <filename>/etc/hosts</filename>.</para>
<para>
<literallayout> 127.0.0.1 localhost.my.domain localhost
10.0.0.1 max.my.domain max
10.0.0.2 moritz.my.domain moritz
</literallayout>
</para>
<programlisting>127.0.0.1 localhost.my.domain localhost
10.0.0.1 max.my.domain max
10.0.0.2 moritz.my.domain</programlisting>
<para>To check if it works do:</para>
<para>on max:</para>
<para>
<literallayout>$ ifconfig lp0
lp0: flags=8851&lt;UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
inet 10.0.0.1 --&gt; 10.0.0.2 netmask 0xff000000 </literallayout>
</para>
<para>
<literallayout>$ netstat -r
<screen>&prompt.root; <userinput>ifconfig lp</userinput>0
lp0: flags=8851&lt;UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
inet 10.0.0.1 --&gt; 10.0.0.2 netmask 0xff000000
&prompt.root; <userinput>netstat -r</userinput>
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
moritz max UH 4 127592 lp0</literallayout>
</para>
<para>
<literallayout>$ ping -c 4 moritz
Destination Gateway Flags Refs Use Netif Expire
moritz max UH 4 127592 lp0
&prompt.root; <userinput>ping -c 4 moritz</userinput>
PING moritz (10.0.0.2): 56 data bytes
64 bytes from 10.0.0.2: icmp_seq=0 ttl=255 time=2.774 ms
64 bytes from 10.0.0.2: icmp_seq=1 ttl=255 time=2.530 ms
@ -1507,8 +1490,8 @@ PING moritz (10.0.0.2): 56 data bytes
--- moritz ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</literallayout>
</para>
round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
</answer></qandaentry>
@ -1519,29 +1502,119 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</literallayout>
<para>Connect the two computers using a Laplink parallel cable to use
this feature:</para>
<para>
<literallayout> +----------------------------------------+
|A-name A-End B-End Descr. Port/Bit |
+----------------------------------------+
|DATA0 2 15 Data 0/0x01 |
|-ERROR 15 2 1/0x08 |
+----------------------------------------+
|DATA1 3 13 Data 0/0x02 |
|+SLCT 13 3 1/0x10 |
+----------------------------------------+
|DATA2 4 12 Data 0/0x04 |
|+PE 12 4 1/0x20 |
+----------------------------------------+
|DATA3 5 10 Strobe 0/0x08 |
|-ACK 10 5 1/0x40 |
+----------------------------------------+
|DATA4 6 11 Data 0/0x10 |
|BUSY 11 6 1/0x80 |
+----------------------------------------+
|GND 18-25 18-25 GND - |
+----------------------------------------+
</literallayout>
</para>
<table>
<title>Wiring a parallel cable for networking</title>
<tgroup cols="5">
<thead>
<row>
<entry>A-name</entry>
<entry>A-End</entry>
<entry>B-End</entry>
<entry>Descr.</entry>
<entry>Post/Bit</entry>
</row>
</thead>
<tbody>
<row>
<entry><literallayout>DATA0
-ERROR</literallayout></entry>
<entry><literallayout>2
15</literallayout></entry>
<entry><literallayout>15
2</literallayout></entry>
<entry>Data</entry>
<entry><literallayout>0/0x01
1/0x08</literallayout></entry>
</row>
<row>
<entry><literallayout>DATA1
+SLCT</literallayout></entry>
<entry><literallayout>3
13</literallayout></entry>
<entry><literallayout>13
3</literallayout></entry>
<entry>Data</entry>
<entry><literallayout>0/0x02
1/0x10</literallayout></entry>
</row>
<row>
<entry><literallayout>DATA2
+PE</literallayout></entry>
<entry><literallayout>4
12</literallayout></entry>
<entry><literallayout>12
4</literallayout></entry>
<entry>Data</entry>
<entry><literallayout>0/0x04
1/0x20</literallayout></entry>
</row>
<row>
<entry><literallayout>DATA3
-ACK</literallayout></entry>
<entry><literallayout>5
10</literallayout></entry>
<entry><literallayout>10
5</literallayout></entry>
<entry>Strobe</entry>
<entry><literallayout>0/0x08
1/0x40</literallayout></entry>
</row>
<row>
<entry><literallayout>DATA4
BUSY</literallayout></entry>
<entry><literallayout>6
11</literallayout></entry>
<entry><literallayout>11
6</literallayout></entry>
<entry>Data</entry>
<entry><literallayout>0/0x10
1/0x80</literallayout></entry>
</row>
<row>
<entry>GND</entry>
<entry>18-25</entry>
<entry>18-25</entry>
<entry>GND</entry>
<entry>-</entry>
</row>
</tbody>
</tgroup>
</table>
<para>See also <link linkend="pao">this note</link> on the Mobile Computing page.</para>
@ -1558,7 +1631,7 @@ C/H/S for convenience. This is how the PC's BIOS works out
which area on a disk to read/write from).</para>
<para>This seems to cause a lot of confusion for some reason. First
of all, the <emphasis remap=tt>physical</emphasis> geometry of a SCSI drive is totally
of all, the <emphasis>physical</emphasis> geometry of a SCSI drive is totally
irrelevant, as FreeBSD works in term of disk blocks. In fact, there
is no such thing as "the" physical geometry, as the sector density
varies across the disk - what manufacturers claim is the "true"
@ -1567,7 +1640,7 @@ results in the least wasted space. For IDE disks, FreeBSD does
work in terms of C/H/S, but all modern drives will convert this
into block references internally as well.</para>
<para>All that matters is the <emphasis remap=tt>logical</emphasis> geometry - the answer that the
<para>All that matters is the <emphasis>logical</emphasis> geometry - the answer that the
BIOS gets when it asks "what is your geometry?" and then uses to access
the disk. As FreeBSD uses the BIOS when booting, it's very important
to get this right. In particular, if you have more than one operating
@ -1582,7 +1655,7 @@ and 32 sectors/track, where 'N' is the capacity of the disk in
MB. For example, a 2GB disk should pretend to have 2048 cylinders,
64 heads and 32 sectors/track.</para>
<para>If it <emphasis remap=tt>is</emphasis> turned on (it's often supplied this way to get around
<para>If it <emphasis>is</emphasis> turned on (it's often supplied this way to get around
certain limitations in MSDOS) and the disk capacity is more than 1GB,
use M cylinders, 63 sectors per track (*not* 64), and 255 heads, where
'M' is the disk capacity in MB divided by 7.844238 (!). So our
@ -1597,7 +1670,7 @@ the DOS partition in the partition editor if you don't want to keep
it, or leave it around for programming network cards and the like).</para>
<para>Alternatively, there is a freely available utility distributed with
FreeBSD called ``<filename>pfdisk.exe</filename>'' (located in the <emphasis remap=tt>tools</emphasis>
FreeBSD called ``<filename>pfdisk.exe</filename>'' (located in the <filename>tools</filename>
subdirectory on the FreeBSD CDROM or on the various FreeBSD
ftp sites) which can be used to work out what geometry the other
operating systems on the disk are using. You can then enter this
@ -1691,8 +1764,7 @@ includes several of the files mentioned here, and the
kernel. There is nothing in the system which requires the
presence of the sources to operate, however, except for the
kernel-configuration program
<ulink URL="http://www.FreeBSD.org/cgi/man.cgi?config(8)">config
</ulink>. With the exception
&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. (Because of the kernel-source
@ -1736,16 +1808,16 @@ systems.</para>
<para>If it is not absolutely imperative that you use DES style
encryption, you can use FreeBSD's default encryption for even
<emphasis remap=bf>better</emphasis> security, and with no export restrictions. FreeBSD
2.0's password default scrambler is now <emphasis remap=bf>MD5</emphasis>-based, and is
<emphasis>better</emphasis> security, and with no export restrictions. FreeBSD
2.0's password default scrambler is now <emphasis>MD5</emphasis>-based, and is
more CPU-intensive to crack with an automated password cracker
than DES, and allows longer passwords as well. The only reason
for not using the <emphasis remap=bf>MD5</emphasis>-based crypt today would be to use the
for not using the <emphasis>MD5</emphasis>-based crypt today would be to use the
the same password entries on FreeBSD and non-FreeBSD systems.</para>
<para>Since the DES encryption algorithm cannot legally be exported
from the US, non-US users should not download this software (as
part of the <emphasis remap=tt>secrdist</emphasis> from US FTP sites.</para>
part of the <literal>secrdist</literal> from US FTP sites.</para>
<para>There is however a replacement libcrypt available, based on
sources written in Australia by David Burren. This code is now
@ -1753,40 +1825,40 @@ available on some non-US FreeBSD mirror sites. Sources for the
unencumbered libcrypt, and binaries of the programs which use it,
can be obtained from the following FTP sites:</para>
<para>
<variablelist>
<varlistentry><term>South Africa</term>
<listitem>
<para><filename>ftp://ftp.internat.FreeBSD.org/pub/FreeBSD</filename><!-- <br> -->
<filename>ftp://storm.sea.uct.ac.za/pub/FreeBSD</filename></para>
<para></para>
<segmentedlist>
<seglistitem><seg>South Africa</seg>
<seg>
<ulink url="ftp://ftp.internat.FreeBSD.org/pub/FreeBSD/">ftp://ftp.internat.FreeBSD.org/pub/FreeBSD/</ulink>,
<ulink url="ftp://storm.sea.uct.ac.za/pub/FreeBSD/">ftp://storm.sea.uct.ac.za/pub/FreeBSD/</ulink>
</listitem>
</varlistentry>
<varlistentry><term>Brazil</term>
<listitem>
<para><filename>ftp://ftp.iqm.unicamp.br/pub/FreeBSD</filename></para>
</seg>
</seglistitem>
<para></para>
<seglistitem><seg>Brazil</seg>
</listitem>
</varlistentry>
<varlistentry><term>Finland</term>
<seg><ulink url="ftp://ftp.iqm.unicamp.br/pub/FreeBSD/">ftp://ftp.iqm.unicamp.br/pub/FreeBSD/</ulink></seg>
<listitem>
<para><filename>ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt</filename></para>
</listitem>
</varlistentry>
</variablelist>
</para>
<para>The non-US <emphasis remap=tt>securedist</emphasis> can be used as a direct replacement
for the encumbered US <emphasis remap=tt>securedist</emphasis>. This <emphasis remap=tt>securedist</emphasis>
</seglistitem>
<seglistitem><seg>Finland</seg>
<seg>
<ulink url="ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt/">ftp://nic.funet.fi/pub/unix/FreeBSD/eurocrypt/</ulink>
</seg>
</seglistitem>
</segmentedlist>
<para>The non-US <emphasis>securedist</emphasis> can be used as a direct replacement
for the encumbered US <emphasis>securedist</emphasis>. This <emphasis>securedist</emphasis>
package is installed the same way as the US package (see
installation notes for details). If you are going to install DES
encryption, you should do so as soon as possible, before
@ -1798,14 +1870,12 @@ which the software is downloaded into severe legal difficulties.</para>
<para>A non-US distribution of Kerberos is also being developed, and
current versions can generally be obtained by anonymous FTP from
<filename>braae.ru.ac.za</filename>.</para>
<hostid role="fqdn">braae.ru.ac.za</hostid>.</para>
<para>There is also a <link linkend="mailing">mailing list</link> for the
discussion of non-US encryption software. For more information, send
an email message with a single line saying ``<emphasis remap=tt>help</emphasis>'' in the body
of your message to</para>
<para><email>majordomo@braae.ru.ac.za</email>.</para>
an email message with a single line saying ``<literal>help</literal>'' in the body
of your message to <email>majordomo@braae.ru.ac.za</email>.</para>
</answer></qandaentry>
@ -1843,11 +1913,11 @@ think is the boot disk, wd1, while it is really wd2, and fails.</para>
&quot;Enter&quot; at the &quot;Booting kernel in 10 seconds; hit
[Enter] to interrupt&quot; prompt. This will drop you into the boot
loader.</para>
<para>Then type set
root_disk_unit="&lt;disk_number&gt;". <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
<para>Then type <literal>set
root_disk_unit="<replaceable>disk_number</replaceable>"</literal>. <replaceable>disk_number</replaceable>
will be <literal>0</literal> if FreeBSD is installed on the master drive
on the first IDE controller, <literal>1</literal> if it is installed
on the slave on the first IDE controller, <literal>2</literal> 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>
@ -1855,15 +1925,15 @@ IDE controller.</para>
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
&quot;root_disk_unit="&lt;disk_number&gt;" in
<literal>root_disk_unit="<replaceable>disk_number</replaceable>"</literal> 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
<literal>1:wd(2,a)kernel</literal> and press Enter. If the system starts, then
run the command
<literallayout>echo "1:wd(2,a)kernel" &gt; /boot.config</literallayout>
<literal>echo "1:wd(2,a)kernel" &gt; /boot.config</literal>
to make it the default boot string.</para>
</listitem>
@ -1875,18 +1945,18 @@ hard disks are consecutive.</para>
<listitem>
<para><ulink URL="../handbook/kernelconfig.html">Rebuild your kernel,</ulink>
modify the wd configuration lines to read:
modify the wd configuration lines to read:</para>
<literallayout>controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr
<programlisting>controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr
disk wd0 at wdc0 drive 0
# disk wd1 at wdc0 drive 1 # comment out this line
controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr
disk wd1 at wdc1 drive 0 # change from wd2 to wd1
disk wd2 at wdc1 drive 1 # change from wd3 to wd2</literallayout>
disk wd2 at wdc1 drive 1 # change from wd3 to wd2</programlisting>
Install the new kernel.
<para>Install the new kernel.
If you moved your disks and wish to restore the previous
configuration, replace the disks in the desired configuration and reboot.
Your system should boot successfully.
@ -1922,6 +1992,87 @@ filesystems with 4 terabytes are possible (and exist).</para>
<para>The maximum size of a single ffs file is approximately 1G blocks
(4TB) if the block size is 4K.</para>
<table>
<title>Maximum file sizes</title>
<tgroup cols="5">
<thead>
<row>
<entry>fs block size</entry>
<entry>2.2.7-stable</entry>
<entry>3.0-current</entry>
<entry>works</entry>
<entry>should work</entry>
</row>
</thead>
<tbody>
<row>
<entry>4K</entry>
<entry>4T-1</entry>
<entry>4T-1</entry>
<entry>4T-1</entry>
<entry>4+t</entry>
</row>
<row>
<entry>8K</entry>
<entry>32+G</entry>
<entry>8T-1</entry>
<entry>32+G</entry>
<entry>32T-1</entry>
</row>
<row>
<entry>16K</entry>
<entry>128+G</entry>
<entry>16T-1</entry>
<entry>128+G</entry>
<entry>32T-1</entry>
</row>
<row>
<entry>32K</entry>
<entry>512+G</entry>
<entry>32T-1</entry>
<entry>512+G</entry>
<entry>64T-1</entry>
</row>
<row>
<entry>64K</entry>
<entry>2048+G</entry>
<entry>64T-1</entry>
<entry>2048+G</entry>
<entry>128T-1</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
<literallayout> maxfilesize
----------------------------------