Attack of the spelling police. The grammar police were also occasionally
called onto the scene.
This commit is contained in:
Jim Mock
parent
c60eb2fceb
commit
aca13e8771
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=7356
15 changed files with 340 additions and 344 deletions
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.224 2000/06/12 12:48:31 asmodai Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.225 2000/06/12 23:38:59 will Exp $
|
||||
-->
|
||||
|
||||
<chapter id="contrib">
|
||||
|
|
@ -284,7 +284,7 @@
|
|||
<orderedlist>
|
||||
<listitem>
|
||||
<para>NetWare Server (protected mode ODI driver) loader and
|
||||
subservices to allow the use of ODI card drivers supplied with
|
||||
sub-services to allow the use of ODI card drivers supplied with
|
||||
network cards. The same thing for NDIS drivers and NetWare SCSI
|
||||
drivers.</para>
|
||||
</listitem>
|
||||
|
|
@ -303,7 +303,7 @@
|
|||
<para>A concerted effort at support for portable computers. This is
|
||||
somewhat handled by changing PCMCIA bridging rules and power
|
||||
management event handling. But there are things like detecting
|
||||
internal vs. external display and picking a different screen
|
||||
internal v.s.. external display and picking a different screen
|
||||
resolution based on that fact, not spinning down the disk if the
|
||||
machine is in dock, and allowing dock-based cards to disappear
|
||||
without affecting the machines ability to boot (same issue for
|
||||
|
|
@ -363,7 +363,7 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>If you know of any bugfixes which have been successfully
|
||||
<para>If you know of any bug fixes which have been successfully
|
||||
applied to -current but have not been merged into -stable after a
|
||||
decent interval (normally a couple of weeks), send the committer a
|
||||
polite reminder.</para>
|
||||
|
|
@ -546,7 +546,7 @@
|
|||
|
||||
<para>In the rare case of a significant contribution of a large body
|
||||
work, or the addition of an important new feature to FreeBSD, it
|
||||
becomes almost always necessary to either send changes as uuencode'd
|
||||
becomes almost always necessary to either send changes as uuencoded
|
||||
tar files or upload them to our ftp site <ulink
|
||||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/">ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/</ulink>.</para>
|
||||
|
||||
|
|
@ -731,7 +731,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
<title>Donors Gallery</title>
|
||||
|
||||
<para>The FreeBSD Project is indebted to the following donors and would
|
||||
like to publically thank them here!</para>
|
||||
like to publicly thank them here!</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
@ -846,7 +846,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
<listitem>
|
||||
<para><ulink url="http://www.cdrom.co.jp/">Laser5</ulink> of Japan
|
||||
(a portion of the profits from sales of their various FreeBSD
|
||||
CD-ROMs).</para>
|
||||
CDROMs).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -983,10 +983,10 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
<listitem>
|
||||
<para>The <ulink url="http://www.interface-business.de/">interface
|
||||
business GmbH, Dresden</ulink> has been patiently supporting
|
||||
&a.joerg; who has often preferred FreeBSD work over paywork, and
|
||||
&a.joerg; who has often preferred FreeBSD work over paid work, and
|
||||
used to fall back to their (quite expensive) EUnet Internet
|
||||
connection whenever his private connection became too slow or
|
||||
flakey to work with it...</para>
|
||||
flaky to work with it...</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -1126,7 +1126,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Adrian Chadd <email>adrian@freebsd.org</email></para>
|
||||
<para>Adrian Chadd <email>adrian@FreeBSD.org</email></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.24 2000/05/02 22:40:41 unfurl Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.25 2000/06/08 01:55:49 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="advanced-networking">
|
||||
|
|
@ -399,7 +399,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
|
||||
<para>Luckily for us, on a FreeBSD system this setup is a snap. The
|
||||
processes that need to be running can all be run at boot time with
|
||||
a few modificationss to your <filename>/etc/rc.conf</filename>
|
||||
a few modifications to your <filename>/etc/rc.conf</filename>
|
||||
file.</para>
|
||||
|
||||
<para>On the NFS server make sure you have:</para>
|
||||
|
|
@ -758,7 +758,7 @@ diskless:\
|
|||
<row>
|
||||
<entry>swapsize
|
||||
<option><replaceable>size</replaceable></option></entry>
|
||||
<entry>set diskless swapsize in Kbytes</entry>
|
||||
<entry>set diskless swapsize in KBytes</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
|
|
@ -827,7 +827,7 @@ hostname myclient.mydomain</programlisting>
|
|||
as in the example above, the swapfile for myclient will be called
|
||||
<filename>/swapfs/swap.<replaceable>X.X.X.X</replaceable></filename>
|
||||
where <replaceable>X.X.X.X</replaceable> is the client's IP addr,
|
||||
eg:</para>
|
||||
e.g.:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>dd if=/dev/zero of=/swapfs/swap.192.1.2.4 bs=1k count=20000</userinput></screen>
|
||||
|
||||
|
|
@ -900,7 +900,7 @@ hostname myclient.mydomain</programlisting>
|
|||
<ulink url="http://alumni.caltech.edu/~dank/isdn/">Dan Kegel's ISDN
|
||||
Page</ulink>.</para>
|
||||
|
||||
<para>A quick simple roadmap to ISDN follows:</para>
|
||||
<para>A quick simple road map to ISDN follows:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
@ -910,14 +910,14 @@ hostname myclient.mydomain</programlisting>
|
|||
|
||||
<listitem>
|
||||
<para>If you are planning to use ISDN primarily to connect to the
|
||||
Internet with an Internet Provider on a dialup non-dedicated basis,
|
||||
Internet with an Internet Provider on a dial-up non-dedicated basis,
|
||||
I suggest you look into Terminal Adapters. This will give you the
|
||||
most flexibility, with the fewest problems, if you change
|
||||
providers.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>If you are connecting two lans together, or connecting to the
|
||||
<para>If you are connecting two LANs together, or connecting to the
|
||||
Internet with a dedicated ISDN connection, I suggest you consider
|
||||
the stand alone router/bridge option.</para>
|
||||
</listitem>
|
||||
|
|
@ -991,7 +991,7 @@ subscribe freebsd-isdn</programlisting>
|
|||
<para>The main advantage of using a TA to connect to an Internet
|
||||
Provider is that you can do Dynamic PPP. As IP address space becomes
|
||||
more and more scarce, most providers are not willing to provide you
|
||||
with a static IP anymore. Most standalone routers are not able to
|
||||
with a static IP anymore. Most stand-alone routers are not able to
|
||||
accommodate dynamic IP allocation.</para>
|
||||
|
||||
<para>TA's completely rely on the PPP daemon that you are running for
|
||||
|
|
@ -1039,11 +1039,11 @@ subscribe freebsd-isdn</programlisting>
|
|||
save you having to buy another serial cable, and find another empty
|
||||
electrical socket.</para>
|
||||
|
||||
<para>A synchronous card with a TA is at least as fast as a standalone
|
||||
<para>A synchronous card with a TA is at least as fast as a stand-alone
|
||||
router, and with a simple 386 FreeBSD box driving it, probably more
|
||||
flexible.</para>
|
||||
|
||||
<para>The choice of sync/TA vs standalone router is largely a religious
|
||||
<para>The choice of sync/TA v.s. stand-alone router is largely a religious
|
||||
issue. There has been some discussion of this in the mailing lists.
|
||||
I suggest you search the <ulink
|
||||
url="http://www.FreeBSD.org/search.html">archives</ulink> for the
|
||||
|
|
@ -1051,7 +1051,7 @@ subscribe freebsd-isdn</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Standalone ISDN Bridges/Routers</title>
|
||||
<title>Stand-alone ISDN Bridges/Routers</title>
|
||||
|
||||
<para>ISDN bridges or routers are not at all specific to FreeBSD or any
|
||||
other operating system. For a more complete description of routing
|
||||
|
|
@ -1097,12 +1097,12 @@ subscribe freebsd-isdn</programlisting>
|
|||
|
|
||||
---Windows 95 (Do not admit to owning it)
|
||||
|
|
||||
Standalone router
|
||||
Stand-alone router
|
||||
|
|
||||
ISDN BRI line</programlisting>
|
||||
|
||||
<para>If your home/branch office is only one computer you can use a
|
||||
twisted pair crossover cable to connect to the standalone router
|
||||
twisted pair crossover cable to connect to the stand-alone router
|
||||
directly.</para>
|
||||
</example>
|
||||
|
||||
|
|
@ -1121,7 +1121,7 @@ ISDN BRI line</programlisting>
|
|||
| |
|
||||
| ---Windows 95
|
||||
| B |
|
||||
|___---Standalone router
|
||||
|___---Stand-alone router
|
||||
|
|
||||
ISDN BRI line</programlisting>
|
||||
</example>
|
||||
|
|
@ -1134,12 +1134,12 @@ ISDN BRI line</programlisting>
|
|||
etc.</para>
|
||||
|
||||
<para>This can be very useful feature, for example if you have an
|
||||
dedicated internet ISDN connection at your office and would like to
|
||||
dedicated ISDN connection at your office and would like to
|
||||
tap into it, but don't want to get another ISDN line at work. A router
|
||||
at the office location can manage a dedicated B channel connection
|
||||
(64Kbs) to the internet, as well as a use the other B channel for a
|
||||
separate data connection. The second B channel can be used for
|
||||
dialin, dialout or dynamically bond(MPP etc.) with the first B channel
|
||||
dial-in, dial-out or dynamically bond(MPP etc.) with the first B channel
|
||||
for more bandwidth.</para>
|
||||
|
||||
<para>An Ethernet bridge will also allow you to transmit more than just
|
||||
|
|
@ -1167,10 +1167,10 @@ ISDN BRI line</programlisting>
|
|||
<sect2>
|
||||
<title>How does it work?</title>
|
||||
|
||||
<para>There are 3 types of hosts in an NIS enviornment; master
|
||||
<para>There are 3 types of hosts in an NIS environment; master
|
||||
servers, slave servers, and clients. Servers act as a central
|
||||
repository for host configuration information. Master servers
|
||||
hold the authoritatve copy of this information, while slave
|
||||
hold the authoritative copy of this information, while slave
|
||||
servers mirror this information for redundancy. Clients rely on
|
||||
the servers to provide this information to them.</para>
|
||||
|
||||
|
|
@ -1217,7 +1217,7 @@ ISDN BRI line</programlisting>
|
|||
<sect4>
|
||||
<title>Physical Server Requirements</title>
|
||||
|
||||
<para>There are several things to keep in mind when chosing a
|
||||
<para>There are several things to keep in mind when choosing a
|
||||
machine to use as a NIS server. One of the unfortunate things
|
||||
about NIS is the level of dependency the clients have on the
|
||||
server. If a client cannot contact the server for its NIS
|
||||
|
|
@ -1259,7 +1259,7 @@ ISDN BRI line</programlisting>
|
|||
<sect4>
|
||||
<title>Setting up a NIS master server</title>
|
||||
|
||||
<para>Setting up a master NIS server can be relativly straight
|
||||
<para>Setting up a master NIS server can be relatively straight
|
||||
forward, depending on your needs. FreeBSD comes with a handy
|
||||
script called <command>ypinit</command> that makes the initial
|
||||
setup procedure very easy. A few steps are needed ahead of
|
||||
|
|
@ -1392,46 +1392,46 @@ Ok, please remember to go back and redo manually whatever fails.
|
|||
If you don't, something might not work.
|
||||
There will be no further questions. The remainder of the procedure
|
||||
should take a few minutes, to copy the databases from master.example.com.
|
||||
Transfering netgroup...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering netgroup.byuser...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering netgroup.byhost...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering master.passwd.byuid...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering passwd.byuid...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering passwd.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering group.bygid...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering group.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering services.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering rpc.bynumber...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering rpc.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering protocols.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering master.passwd.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering networks.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering networks.byaddr...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering netid.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering hosts.byaddr...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering protocols.bynumber...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering ypservers...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering hosts.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transferring netgroup...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring netgroup.byuser...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring netgroup.byhost...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring master.passwd.byuid...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring passwd.byuid...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring passwd.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring group.bygid...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring group.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring services.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring rpc.bynumber...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring rpc.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring protocols.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring master.passwd.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring networks.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring networks.byaddr...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring netid.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring hosts.byaddr...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring protocols.bynumber...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring ypservers...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring hosts.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
|
||||
slave.example.com has been setup as an YP slave server without any errors.
|
||||
Don't forget to update map ypservers on master.example.com.</screen>
|
||||
|
|
@ -1622,7 +1622,7 @@ Don't forget to update map ypservers on master.example.com.</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>libscrypt vs. libdescrypt</title>
|
||||
<title>libscrypt v.s. libdescrypt</title>
|
||||
|
||||
<para>One of the most common issues that people run into when trying
|
||||
to implement NIS is crypt library compatibility. If your NIS
|
||||
|
|
@ -1644,7 +1644,7 @@ lrwxr-xr-x 1 root wheel 16 Nov 8 14:27 /usr/lib/libdescrypt.so@ -> libdes
|
|||
-r--r--r-- 1 root wheel 14750 Nov 8 14:27 /usr/lib/libdescrypt_p.a</screen>
|
||||
|
||||
<para>If the machine is configured to use the standard FreeBSD MD5
|
||||
crypt libraries they will look somethine like this:</para>
|
||||
crypt libraries they will look something like this:</para>
|
||||
|
||||
<screen>
|
||||
&prompt.user; <userinput>ls -l /usr/lib/*crypt*</userinput>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.22 2000/05/15 00:10:38 joe Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.23 2000/06/08 01:55:59 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="backups">
|
||||
|
|
@ -33,7 +33,7 @@
|
|||
x 12 mm) than 8mm cartridges. 4mm, like 8mm, has comparatively short
|
||||
head life for the same reason, both use helical scan.</para>
|
||||
|
||||
<para>Data thruput on these drives starts ~150kB/s, peaking at ~500kB/s.
|
||||
<para>Data throughput on these drives starts ~150kB/s, peaking at ~500kB/s.
|
||||
Data capacity starts at 1.3 GB and ends at 2.0 GB. Hardware
|
||||
compression, available with most of these drives, approximately
|
||||
doubles the capacity. Multi-drive tape library units can have 6
|
||||
|
|
@ -60,7 +60,7 @@
|
|||
One downside of 8mm tape is relatively short head and tape life due to
|
||||
the high rate of relative motion of the tape across the heads.</para>
|
||||
|
||||
<para>Data thruput ranges from ~250kB/s to ~500kB/s. Data sizes start
|
||||
<para>Data throughput ranges from ~250kB/s to ~500kB/s. Data sizes start
|
||||
at 300 MB and go up to 7 GB. Hardware compression, available with
|
||||
most of these drives, approximately doubles the capacity. These
|
||||
drives are available as single units or multi-drive tape libraries
|
||||
|
|
@ -99,7 +99,7 @@
|
|||
also use 1/4" wide tape are discussed separately. Tape libraries and
|
||||
changers are not available.</para>
|
||||
|
||||
<para>Data thruput ranges from ~150kB/s to ~500kB/s. Data capacity
|
||||
<para>Data throughput ranges from ~150kB/s to ~500kB/s. Data capacity
|
||||
ranges from 40 MB to 15 GB. Hardware compression is available on many
|
||||
of the newer QIC drives. QIC drives are less frequently installed;
|
||||
they are being supplanted by DAT drives.</para>
|
||||
|
|
@ -139,7 +139,7 @@
|
|||
both the supply and take-up spools located inside the tape cartridge
|
||||
itself.</para>
|
||||
|
||||
<para>Data thruput is approximately 1.5MB/s, three times the thruput of
|
||||
<para>Data throughput is approximately 1.5MB/s, three times the throughput of
|
||||
4mm, 8mm, or QIC tape drives. Data capacities range from 10GB to 20GB
|
||||
for a single drive. Drives are available in both multi-tape changers
|
||||
and multi-tape, multi-drive tape libraries containing from 5 to 900
|
||||
|
|
@ -381,7 +381,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
two copies of
|
||||
each.</para>
|
||||
|
||||
<para>Second, determine that the boot and fixit floppies
|
||||
<para>Second, determine that the boot and fix-it floppies
|
||||
(<filename>boot.flp</filename> and <filename>fixit.flp</filename>)
|
||||
have all your devices. The easiest way to check is to reboot your
|
||||
machine with the boot floppy in the floppy drive and check the boot
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.224 2000/06/12 12:48:31 asmodai Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.225 2000/06/12 23:38:59 will Exp $
|
||||
-->
|
||||
|
||||
<chapter id="contrib">
|
||||
|
|
@ -284,7 +284,7 @@
|
|||
<orderedlist>
|
||||
<listitem>
|
||||
<para>NetWare Server (protected mode ODI driver) loader and
|
||||
subservices to allow the use of ODI card drivers supplied with
|
||||
sub-services to allow the use of ODI card drivers supplied with
|
||||
network cards. The same thing for NDIS drivers and NetWare SCSI
|
||||
drivers.</para>
|
||||
</listitem>
|
||||
|
|
@ -303,7 +303,7 @@
|
|||
<para>A concerted effort at support for portable computers. This is
|
||||
somewhat handled by changing PCMCIA bridging rules and power
|
||||
management event handling. But there are things like detecting
|
||||
internal vs. external display and picking a different screen
|
||||
internal v.s.. external display and picking a different screen
|
||||
resolution based on that fact, not spinning down the disk if the
|
||||
machine is in dock, and allowing dock-based cards to disappear
|
||||
without affecting the machines ability to boot (same issue for
|
||||
|
|
@ -363,7 +363,7 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>If you know of any bugfixes which have been successfully
|
||||
<para>If you know of any bug fixes which have been successfully
|
||||
applied to -current but have not been merged into -stable after a
|
||||
decent interval (normally a couple of weeks), send the committer a
|
||||
polite reminder.</para>
|
||||
|
|
@ -546,7 +546,7 @@
|
|||
|
||||
<para>In the rare case of a significant contribution of a large body
|
||||
work, or the addition of an important new feature to FreeBSD, it
|
||||
becomes almost always necessary to either send changes as uuencode'd
|
||||
becomes almost always necessary to either send changes as uuencoded
|
||||
tar files or upload them to our ftp site <ulink
|
||||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/">ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/</ulink>.</para>
|
||||
|
||||
|
|
@ -731,7 +731,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
<title>Donors Gallery</title>
|
||||
|
||||
<para>The FreeBSD Project is indebted to the following donors and would
|
||||
like to publically thank them here!</para>
|
||||
like to publicly thank them here!</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
@ -846,7 +846,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
<listitem>
|
||||
<para><ulink url="http://www.cdrom.co.jp/">Laser5</ulink> of Japan
|
||||
(a portion of the profits from sales of their various FreeBSD
|
||||
CD-ROMs).</para>
|
||||
CDROMs).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -983,10 +983,10 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
<listitem>
|
||||
<para>The <ulink url="http://www.interface-business.de/">interface
|
||||
business GmbH, Dresden</ulink> has been patiently supporting
|
||||
&a.joerg; who has often preferred FreeBSD work over paywork, and
|
||||
&a.joerg; who has often preferred FreeBSD work over paid work, and
|
||||
used to fall back to their (quite expensive) EUnet Internet
|
||||
connection whenever his private connection became too slow or
|
||||
flakey to work with it...</para>
|
||||
flaky to work with it...</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -1126,7 +1126,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Adrian Chadd <email>adrian@freebsd.org</email></para>
|
||||
<para>Adrian Chadd <email>adrian@FreeBSD.org</email></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.47 2000/06/08 01:56:06 jim Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.48 2000/06/09 22:54:37 nik Exp $
|
||||
-->
|
||||
|
||||
<chapter id="cutting-edge">
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
</sect1>
|
||||
|
||||
<sect1 id="current-stable">
|
||||
<title>-CURRENT vs. -STABLE</title>
|
||||
<title>-CURRENT v.s.. -STABLE</title>
|
||||
|
||||
<para>There are two development branches to FreeBSD; -CURRENT and
|
||||
-STABLE. This section will explain a bit about each and describe
|
||||
|
|
@ -183,7 +183,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
<ulink
|
||||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/</ulink>.
|
||||
We also use <command>wu-ftpd</command> which allows
|
||||
compressed/tar'd grabbing of whole trees. e.g. you
|
||||
compressed/tarred grabbing of whole trees. e.g. you
|
||||
see:</para>
|
||||
|
||||
<screen>usr.bin/lex</screen>
|
||||
|
|
@ -354,7 +354,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-stable/">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-stable/</ulink></para>
|
||||
|
||||
<para>We also use <command>wu-ftpd</command> which allows
|
||||
compressed/tar'd grabbing of whole trees. e.g. you
|
||||
compressed/tarred grabbing of whole trees. e.g. you
|
||||
see:</para>
|
||||
|
||||
<screen>usr.bin/lex</screen>
|
||||
|
|
@ -707,7 +707,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
</example>
|
||||
|
||||
<example>
|
||||
<title>Creating a list of changes (as unidiffs) to &man.ls.1;</title>
|
||||
<title>Creating a list of changes (as unified diffs) to &man.ls.1;</title>
|
||||
|
||||
<screen>
|
||||
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
|
||||
|
|
@ -764,7 +764,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
<sect1 id="makeworld">
|
||||
<title>Using <command>make world</command></title>
|
||||
|
||||
<para>Once you have synchronised your local source tree against a
|
||||
<para>Once you have synchronized your local source tree against a
|
||||
particular version of FreeBSD (<literal>stable</literal>,
|
||||
<literal>current</literal> and so on) you must then use the source
|
||||
tree to rebuild the system.</para>
|
||||
|
|
@ -779,7 +779,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
when you make mistakes, or when mistakes made by others in the
|
||||
source tree render your system unbootable.</para>
|
||||
|
||||
<para>Make sure you have taken a backup. And have a fixit floppy to
|
||||
<para>Make sure you have taken a backup. And have a fix-it floppy to
|
||||
hand. I have never needed to use them, and, touch wood, I never
|
||||
will, but it is always better to be safe than sorry.</para>
|
||||
</warning>
|
||||
|
|
@ -1006,7 +1006,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
|
||||
<screen>&prompt.root; <userinput>make -DNOPROFILE=true <replaceable>target</replaceable></userinput></screen>
|
||||
|
||||
<para>is another way of specifying that profiled libaries should
|
||||
<para>is another way of specifying that profiled libraries should
|
||||
not be built, and corresponds with the</para>
|
||||
|
||||
<programlisting>NOPROFILE= true
|
||||
|
|
@ -1261,7 +1261,7 @@ Script done, …</screen>
|
|||
|
||||
<tip>
|
||||
<title>Name the new root directory
|
||||
(<filename>/var/tmp/root</filename>)with a timestamp, so you can
|
||||
(<filename>/var/tmp/root</filename>)with a time stamp, so you can
|
||||
easily compare differences between versions</title>
|
||||
|
||||
<para>Frequently remaking the world means that you have to update
|
||||
|
|
@ -1348,7 +1348,7 @@ Script done, …</screen>
|
|||
<para>If you are using DEVFS then this is probably unnecessary.</para>
|
||||
</note>
|
||||
|
||||
<para>For safety's sake, this is a multistep process.</para>
|
||||
<para>For safety's sake, this is a multi-step process.</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
|
|
@ -1362,7 +1362,7 @@ Script done, …</screen>
|
|||
<para>Now, take a snapshot of your current
|
||||
<filename>/dev</filename>. This snapshot needs to contain the
|
||||
permissions, ownerships, major and minor numbers of each filename,
|
||||
but it should not contain the timestamps. The easiest way to do
|
||||
but it should not contain the time stamps. The easiest way to do
|
||||
this is to use &man.awk.1; to strip out some of the
|
||||
information.</para>
|
||||
|
||||
|
|
@ -1399,11 +1399,11 @@ Script done, …</screen>
|
|||
<title>Update <filename>/stand</filename></title>
|
||||
|
||||
<note>
|
||||
<para>This step is included only for completeness, it can safely be
|
||||
<para>This step is included only for completeness. It can safely be
|
||||
omitted.</para>
|
||||
</note>
|
||||
|
||||
<para>For completenesses sake you may want to update the files in
|
||||
<para>For the sake of completeness, you may want to update the files in
|
||||
<filename>/stand</filename> as well. These files consist of hard
|
||||
links to the <filename>/stand/sysinstall</filename> binary. This
|
||||
binary should be statically linked, so that it can work when no other
|
||||
|
|
@ -1769,8 +1769,8 @@ Antonio</screen>
|
|||
<listitem>
|
||||
<para>Also in <filename>/etc/make.conf</filename>, set
|
||||
<quote>CFLAGS</quote> to something like <quote>-O
|
||||
-pipe</quote>. The optimisation <quote>-O2</quote> is much
|
||||
slower, and the optimisation difference between
|
||||
-pipe</quote>. The optimization <quote>-O2</quote> is much
|
||||
slower, and the optimization difference between
|
||||
<quote>-O</quote> and <quote>-O2</quote> is normally
|
||||
negligible. <quote>-pipe</quote> lets the compiler use
|
||||
pipes rather than temporary files for communication, which
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml,v 1.18 2000/04/30 22:10:06 nik Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml,v 1.19 2000/06/08 01:56:07 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="disks">
|
||||
|
|
@ -54,7 +54,7 @@
|
|||
<title>An illustration from the files of Bill and Fred's Exceptional
|
||||
Adventures:</title>
|
||||
|
||||
<para>Bill breaks-down an older WIntel box to make another FreeBSD box
|
||||
<para>Bill breaks-down an older Wintel box to make another FreeBSD box
|
||||
for Fred. Bill installs a single SCSI drive as SCSI unit zero, and
|
||||
installs FreeBSD on it.</para>
|
||||
|
||||
|
|
@ -75,7 +75,7 @@
|
|||
<para>Fred continues his work for several days, and soon Bill and Fred
|
||||
decide that it's time for a new adventure -- time to upgrade to a
|
||||
newer version of FreeBSD. Bill removes SCSI unit zero because it was
|
||||
a bit flakey, and replaces it with another identical disk drive from
|
||||
a bit flaky, and replaces it with another identical disk drive from
|
||||
the "archive." Bill then installs the new version of FreeBSD onto the
|
||||
new SCSI unit zero using Fred's magic internet FTP floppies. The
|
||||
installation goes well.</para>
|
||||
|
|
@ -104,7 +104,7 @@
|
|||
|
||||
<para>We are delighted to mention that no data bytes were killed or
|
||||
harmed in any way by our discovery of this phenomenon. The older SCSI
|
||||
unit zero was retrieved from the bonepile, and all of Fred's work was
|
||||
unit zero was retrieved from the bone pile, and all of Fred's work was
|
||||
returned to him, (and now Bill knows that he can count as high as
|
||||
zero).</para>
|
||||
|
||||
|
|
@ -116,7 +116,7 @@
|
|||
<sect1 id="disks-naming">
|
||||
<title>Disk Naming</title>
|
||||
|
||||
<para>Physical drives come in two main flavours,
|
||||
<para>Physical drives come in two main flavors,
|
||||
<acronym>IDE</acronym>, or <acronym>SCSI</acronym>; but there
|
||||
are also drives backed by RAID controllers, flash memory, and so
|
||||
forth. Since these behave quite differently, they have their
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.43 2000/04/17 16:10:31 phantom Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.44 2000/06/08 01:56:07 jim Exp $
|
||||
-->
|
||||
|
||||
<appendix id="eresources">
|
||||
|
|
@ -434,7 +434,7 @@ help
|
|||
subscriber overlap and except for the most esoteric mixes (say
|
||||
"-stable & -scsi"), there really is no reason to post to more
|
||||
than one list at a time. If a message is sent to you in such a
|
||||
way that multiple mailing lists appear on the Cc line then the cc
|
||||
way that multiple mailing lists appear on the Cc line then the Cc
|
||||
line should also be trimmed before sending it out again.
|
||||
<emphasis>You are <emphasis>still</emphasis> responsible for your
|
||||
own cross-postings, no matter who the originator might have
|
||||
|
|
@ -1235,7 +1235,7 @@ help
|
|||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.nz.FreeBSD.org/">http://www.nz.FreeBSD.org/</ulink> — New Zeland.</para>
|
||||
url="http://www.nz.FreeBSD.org/">http://www.nz.FreeBSD.org/</ulink> — New Zealand.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -1423,15 +1423,15 @@ help
|
|||
<tbody>
|
||||
<row>
|
||||
<entry>storm.uk.FreeBSD.org</entry>
|
||||
<entry>ssh only</entry>
|
||||
<entry>Read-only cvs, personal webspace, email</entry>
|
||||
<entry>SSH only</entry>
|
||||
<entry>Read-only cvs, personal web space, email</entry>
|
||||
<entry>&a.brian</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>dogma.freebsd-uk.eu.org</entry>
|
||||
<entry>Telnet/FTP/SSH</entry>
|
||||
<entry>E-Mail, Webspace, Anonymous FTP</entry>
|
||||
<entry>E-Mail, Web space, Anonymous FTP</entry>
|
||||
<entry>Lee Johnston
|
||||
<email>lee@uk.FreeBSD.org</email></entry>
|
||||
</row>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml,v 1.31 2000/04/02 19:38:11 chris Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml,v 1.32 2000/06/08 01:56:07 jim Exp $
|
||||
-->
|
||||
|
||||
<appendix id="hw">
|
||||
|
|
@ -74,7 +74,7 @@
|
|||
<para>For Pentium Pro (P6) systems, I'm quite fond of the <ulink
|
||||
url="http://www.tyan.com/html/products.html">Tyan</ulink> S1668
|
||||
dual-processor motherboard as well as the Intel PR440FX motherboard
|
||||
with on-board SCSI WIDE and 100/10MB Intel Etherexpress NIC. You
|
||||
with on-board SCSI WIDE and 100/10MB Intel EtherExpress NIC. You
|
||||
can build a dandy little single or dual processor system (which is
|
||||
supported in FreeBSD 3.0) for very little cost now that the Pentium
|
||||
Pro 180/256K chips have fallen so greatly in price, but no telling
|
||||
|
|
@ -153,7 +153,7 @@
|
|||
|
||||
<para>My SCSI preferences extend to SCSI CDROM drives as well, and
|
||||
while the <ulink url="http://www.toshiba.com/">Toshiba</ulink> drives
|
||||
have always been favourites of mine (in whatever speed is hot that
|
||||
have always been favorites of mine (in whatever speed is hot that
|
||||
week), I'm still fond of my good old <ulink
|
||||
url="http://www.plextor.com/">Plextor</ulink> PX-12CS drive. It's
|
||||
only a 12 speed, but it's offered excellent performance and
|
||||
|
|
@ -263,13 +263,13 @@
|
|||
then <ulink url="http://www.dgii.com/">Digi International</ulink>
|
||||
makes the <ulink
|
||||
url="http://www.dgii.com/prodprofiles/profiles-prices/digiprofiles/digispecs/sync570.html">SYNC/570</ulink>
|
||||
series, with drivers now in FreeBSD-current. <ulink
|
||||
series, with drivers now in FreeBSD-CURRENT. <ulink
|
||||
url="http://www.etinc.com/">Emerging Technologies</ulink> also
|
||||
manufactures a board with T1/E1 capabilities, using software they
|
||||
provide. I have no direct experience using either product,
|
||||
however.</para>
|
||||
|
||||
<para>Multiport card options are somewhat more numerous, though it has
|
||||
<para>multiport card options are somewhat more numerous, though it has
|
||||
to be said that FreeBSD's support for <ulink
|
||||
url="http://www.cyclades.com/">Cyclades</ulink>'s products is
|
||||
probably the tightest, primarily as a result of that company's
|
||||
|
|
@ -291,7 +291,7 @@
|
|||
Labs</ulink> AWE32 though just about anything from Creative Labs
|
||||
will generally work these days. This is not to say that other types
|
||||
of sound cards don't also work, simply that I have little experience
|
||||
with them (I was a former GUS fan, but Gravis's soundcard situation
|
||||
with them (I was a former GUS fan, but Gravis's sound card situation
|
||||
has been dire for some time).</para>
|
||||
</sect3>
|
||||
|
||||
|
|
@ -379,10 +379,11 @@
|
|||
|
||||
<listitem>
|
||||
<para>Works fine, but many MB manufactures leave out the
|
||||
external dirty bit SRAM needed for write back operation. Work
|
||||
arounds are either run it in write through mode, or get the
|
||||
dirty bit SRAM installed. (I have these for the ASUS
|
||||
PCI/I-486SP3G rev 1.6 and later boards).</para>
|
||||
external dirty bit SRAM needed for write back operation.
|
||||
You can work around this either by running it in write
|
||||
through mode, or get the dirty bit SRAM installed (I
|
||||
have these for the ASUS PCI/I-486SP3G rev 1.6 and later
|
||||
boards).</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -460,7 +461,7 @@
|
|||
<title>P6 class (Pentium Pro/Pentium II)</title>
|
||||
|
||||
<para>Both the Pentium Pro and Pentium II work fine with FreeBSD. In
|
||||
fact, our main ftp site <ulink
|
||||
fact, our main FTP site <ulink
|
||||
url="ftp://ftp.FreeBSD.org/">ftp.FreeBSD.org</ulink> (also known
|
||||
as "<filename>ftp.cdrom.com</filename>", world's largest ftp site)
|
||||
runs FreeBSD on a Pentium Pro. <ulink
|
||||
|
|
@ -474,7 +475,7 @@
|
|||
<para>The Intel Pentium (P54C), Pentium MMX (P55C), AMD K6 and
|
||||
Cyrix/IBM 6x86MX processors are all reported to work with FreeBSD.
|
||||
I will not go into details of which processor is faster than what,
|
||||
there are zillions of web sites on the Internet that tells you one
|
||||
there are millions of web sites on the Internet that tells you one
|
||||
way or another. <!-- smiley --><emphasis>:)</emphasis></para>
|
||||
|
||||
<note>
|
||||
|
|
@ -656,7 +657,7 @@
|
|||
<title>286 class</title>
|
||||
|
||||
<para>Sorry, FreeBSD does not run on 80286 machines. It is nearly
|
||||
impossible to run today's large full-featured UNIXes on such
|
||||
impossible to run today's large full-featured unices on such
|
||||
hardware.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
|
@ -840,7 +841,7 @@
|
|||
when the device connected to the UART is a modem, the modem may
|
||||
report the presence of a carrier on the phone line while the
|
||||
computer may be able to instruct the modem to reset itself or to
|
||||
not take calls by asserting or deasserting one more more of these
|
||||
not take calls by asserting or disasserting one more more of these
|
||||
extra signals. The function of each of these additional signals is
|
||||
defined in the EIA RS232-C standard.</para>
|
||||
</sect4>
|
||||
|
|
@ -1622,7 +1623,7 @@ INS8250 -> INS8250B
|
|||
combinations of events occur that were not well tested or
|
||||
considered in the Windows driver. This is because most modem
|
||||
vendors and 16550-clone makers use the Microsoft drivers from
|
||||
Windows for Workgroups 3.11 and the Microsoft MSD utility as the
|
||||
Windows for Workgroups 3.11 and the Microsoft MS-DOS utility as the
|
||||
primary tests for compatibility with the NS16550A. This
|
||||
over-simplistic criteria means that if a different operating
|
||||
system is used, problems could appear due to subtle differences
|
||||
|
|
@ -2549,7 +2550,7 @@ INS8250 -> INS8250B
|
|||
<listitem>
|
||||
<para>By default this part is similar to the NS16550A, but an
|
||||
extended 32-byte send and receive buffer can be optionally
|
||||
enabled. Made by Startech.</para>
|
||||
enabled. Made by StarTech.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -2769,7 +2770,7 @@ sio16: type 16550A (multiport master)</screen>
|
|||
&prompt.root; <userinput>./MAKEDEV ttyg</userinput>
|
||||
&prompt.root; <userinput>./MAKEDEV cuag</userinput></screen>
|
||||
|
||||
<para>If you do not want or need callout devices for some
|
||||
<para>If you do not want or need call-out devices for some
|
||||
reason, you can dispense with making the
|
||||
<filename>cua*</filename> devices.</para>
|
||||
</step>
|
||||
|
|
@ -2806,7 +2807,7 @@ sio16: type 16550A (multiport master)</screen>
|
|||
need to configure them as <devicename>COM2</devicename> (aka
|
||||
<devicename>sio1</devicename>–I/O address 0x2F8 and IRQ 3),
|
||||
and the third port (aka <devicename>sio2</devicename>) as I/O
|
||||
0x3E8 and IRQ 5. Obviously this is a waste of IRQ ressources, as
|
||||
0x3E8 and IRQ 5. Obviously this is a waste of IRQ resources, as
|
||||
it should be basically possible to run both extension board ports
|
||||
using a single IRQ with the <literal>COM_MULTIPORT</literal>
|
||||
configuration described in the previous sections.</para>
|
||||
|
|
@ -2838,7 +2839,7 @@ IRQ 2 3 4 5</programlisting>
|
|||
<para>You need to decouple the IRQ drivers for the two UARTs, so
|
||||
that the IRQ line of the board only goes up if (and only if) one
|
||||
of the UARTs asserts a IRQ, and stays low otherwise. The solution
|
||||
was proposed by Jrg Wunsch
|
||||
was proposed by Joerg Wunsch
|
||||
<email>j@ida.interface-business.de</email>: To solder up a
|
||||
wired-or consisting of two diodes (Germanium or Schottky-types
|
||||
strongly preferred) and a 1 kOhm resistor. Here is the schematic,
|
||||
|
|
@ -2873,7 +2874,7 @@ device sio2 at isa? port "IO_COM3" tty flags 0x205 irq 3</programlis
|
|||
|
||||
<para>Note that the <literal>flags</literal> setting for
|
||||
<devicename>sio1</devicename> and <devicename>sio2</devicename> is
|
||||
truely essential; refer to
|
||||
truly essential; refer to
|
||||
&man.sio.4; for details. (Generally, the <literal>2</literal> in
|
||||
the "flags" attribute refers to <devicename>sio</devicename>2
|
||||
which holds the IRQ, and you surely want a <literal>5</literal>
|
||||
|
|
@ -2895,7 +2896,7 @@ sio2: type 16550A (multiport master)</screen>
|
|||
the basic idea is that you observe <literal>0x1</literal> in the
|
||||
first, third, and fourth place. This means that the corresponding
|
||||
IRQ was set upon output and cleared after, which is just what we
|
||||
would expect. If your kernel does not display this behaviour, most
|
||||
would expect. If your kernel does not display this behavior, most
|
||||
likely there is something wrong with your wiring.</para>
|
||||
</sect4>
|
||||
</sect3>
|
||||
|
|
@ -2980,7 +2981,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure</programlisting>
|
|||
use I/O locations, but instead require a 32K chunk of memory. The
|
||||
factory configuration for ISA cards places this at
|
||||
<literal>0xd0000-0xd7fff</literal>.
|
||||
They also require an IRQ. PCI cards will, of course, autoconfigure
|
||||
They also require an IRQ. PCI cards will, of course, auto-configure
|
||||
themselves.</para>
|
||||
|
||||
<para>You can attach up to 4 external modules to each host card. The
|
||||
|
|
@ -3127,7 +3128,7 @@ moused_port="/dev/psm0"</programlisting>
|
|||
mouse daemon you will need to include the following text in
|
||||
<filename>/etc/rc.conf</filename>. This example assumes that the
|
||||
mouse is connected to <devicename>COM1:</devicename> and can be
|
||||
automatically recognised by the mouse daemon.</para>
|
||||
automatically recognized by the mouse daemon.</para>
|
||||
|
||||
<programlisting>moused_enable="YES"
|
||||
moused_type="auto"
|
||||
|
|
@ -3165,7 +3166,7 @@ moused_port="/dev/cuaa0"</programlisting>
|
|||
|
||||
<para>The USB device drivers are a relatively new addition to
|
||||
FreeBSD and have not yet been included in the GENERIC kernel. The
|
||||
following prodecure is an example of how to setup the relevant
|
||||
following procedure is an example of how to setup the relevant
|
||||
drivers on a typical system.</para>
|
||||
|
||||
<procedure>
|
||||
|
|
@ -3350,7 +3351,7 @@ moused_port="/dev/ums0"</programlisting>
|
|||
<para>Mainstream ESDI drives use 34 to 36 sectors per track. Most
|
||||
(older) controllers cannot handle more than this number of
|
||||
sectors. Newer, higher capacity, drives use higher numbers of
|
||||
sectors per track. For instance, I own a 670 Mb drive that has 54
|
||||
sectors per track. For instance, I own a 670 MB drive that has 54
|
||||
sectors per track.</para>
|
||||
|
||||
<para>In my case, the controller could not handle this number of
|
||||
|
|
@ -3582,7 +3583,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
BIOS to allow the BIOS to boot it.</para>
|
||||
|
||||
<para>Before using <command>NEFMT.EXE</command> I tried to format
|
||||
the disk using the ACB-2320 BIOS builtin formatter. This proved
|
||||
the disk using the ACB-2320 BIOS built-in formatter. This proved
|
||||
to be a show stopper, because it did not give me an option to
|
||||
disable spare sectoring. With spare sectoring enabled the FreeBSD
|
||||
installation process broke down on the <command>bad144</command>
|
||||
|
|
@ -3675,7 +3676,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
<para>After some time an industry effort was started to come to a more
|
||||
strict standard allowing devices from different vendors to work
|
||||
together. This effort was recognized in the ANSI SCSI-1 standard.
|
||||
The SCSI-1 standard (approx 1985) is rapidly becoming obsolete. The
|
||||
The SCSI-1 standard (approximately 1985) is rapidly becoming obsolete. The
|
||||
current standard is SCSI-2 (see <link
|
||||
linkend="scsi-further-reading">Further reading</link>), with SCSI-3
|
||||
on the drawing boards.</para>
|
||||
|
|
@ -3711,7 +3712,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
<para>In SCSI-3 even faster bus types are introduced, along with a
|
||||
serial SCSI busses that reduces the cabling overhead and allows a
|
||||
higher maximum bus length. You might see names like SSA and
|
||||
Fiberchannel in this context. None of the serial buses are currently
|
||||
fibre channel in this context. None of the serial buses are currently
|
||||
in widespread use (especially not in the typical FreeBSD environment).
|
||||
For this reason the serial bus types are not discussed any
|
||||
further.</para>
|
||||
|
|
@ -3981,7 +3982,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
|
||||
<para>On modern devices, sometimes integrated terminators are used.
|
||||
These things are special purpose integrated circuits that can be
|
||||
dis/en-abled with a control pin. It is not necessary to
|
||||
enabled or disabled with a control pin. It is not necessary to
|
||||
physically remove them from a device. You may find them on newer
|
||||
host adapters, sometimes they are software configurable, using
|
||||
some sort of setup tool. Some will even auto-detect the cables
|
||||
|
|
@ -4052,7 +4053,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
<para>A narrow SCSI device can not communicate with a SCSI device
|
||||
with a target ID larger than 7. This means it is generally not
|
||||
a good idea to move your SCSI host adapter's target ID to
|
||||
something higher than 7 (or your CD-ROM will stop
|
||||
something higher than 7 (or your CDROM will stop
|
||||
working).</para>
|
||||
</note>
|
||||
|
||||
|
|
@ -4210,7 +4211,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)</screen>
|
|||
|
||||
<para>On top of the card drivers there are a number of more generic
|
||||
drivers for a class of devices. More specific: a driver for tape
|
||||
devices (abbreviation: st), magnetic disks (sd), CD-ROMs (cd) etc.
|
||||
devices (abbreviation: st), magnetic disks (sd), CDROMs (cd) etc.
|
||||
In case you are wondering where you can find this stuff, it all
|
||||
lives in <filename>/sys/scsi</filename>. See the man pages in
|
||||
section 4 for more details.</para>
|
||||
|
|
@ -4288,7 +4289,7 @@ disk sd1 at scbus0 target 1 [implicit LUN 0 if omitted]
|
|||
disk sd2 at scbus1 target 3 [SCSI disk on the uha0]
|
||||
disk sd3 at scbus2 target 4 [SCSI disk on the ncr0]
|
||||
tape st1 at scbus0 target 6 [SCSI tape at target 6]
|
||||
device cd0 at scbus? [the first ever CD-ROM found, no wiring]</programlisting>
|
||||
device cd0 at scbus? [the first ever CDROM found, no wiring]</programlisting>
|
||||
|
||||
<para>The example above tells the kernel to look for a ahc (Adaptec
|
||||
274x) controller, then for an NCR/Symbios board, and so on. The
|
||||
|
|
@ -4349,7 +4350,7 @@ controller scbus0
|
|||
device sd0 [support for 4 SCSI harddisks, sd0 up sd3]
|
||||
device st0 [support for 2 SCSI tapes]
|
||||
|
||||
[for the CD-ROM]
|
||||
[for the CDROM]
|
||||
device cd0 #Only need one of these, the code dynamically grows</programlisting>
|
||||
|
||||
<para>Both examples support SCSI disks. If during boot more devices
|
||||
|
|
@ -4361,7 +4362,7 @@ device cd0 #Only need one of these, the code dynamically grows</pro
|
|||
|
||||
<para>Use <command>man 4 scsi</command> to check for the latest info
|
||||
on the SCSI subsystem. For more detailed info on host adapter
|
||||
drivers use eg <command>man 4 ahc</command> for info on the
|
||||
drivers use e.g., <command>man 4 ahc</command> for info on the
|
||||
Adaptec 294x driver.</para>
|
||||
</sect4>
|
||||
|
||||
|
|
@ -4371,7 +4372,7 @@ device cd0 #Only need one of these, the code dynamically grows</pro
|
|||
<para>Experience has shown that some devices are slow to respond to
|
||||
INQUIRY commands after a SCSI bus reset (which happens at boot
|
||||
time). An INQUIRY command is sent by the kernel on boot to see
|
||||
what kind of device (disk, tape, CD-ROM etc) is connected to a
|
||||
what kind of device (disk, tape, CDROM etc.) is connected to a
|
||||
specific target ID. This process is called device probing by the
|
||||
way.</para>
|
||||
|
||||
|
|
@ -4384,7 +4385,7 @@ device cd0 #Only need one of these, the code dynamically grows</pro
|
|||
options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device</programlisting>
|
||||
|
||||
<para>This line sets the delay time to 15 seconds. On my own system
|
||||
I had to use 3 seconds minimum to get my trusty old CD-ROM drive
|
||||
I had to use 3 seconds minimum to get my trusty old CDROM drive
|
||||
to be recognized. Start with a high value (say 30 seconds or so)
|
||||
when you have problems with device recognition. If this helps,
|
||||
tune it back until it just stays working.</para>
|
||||
|
|
@ -4426,7 +4427,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
|
|||
|
||||
<para>This scheme works fine, but keep in mind that it of course
|
||||
only works for devices that are known to be weird. If you are the
|
||||
first to connect your bogus Mumbletech SCSI CD-ROM you might be
|
||||
first to connect your bogus Mumbletech SCSI CDROM you might be
|
||||
the one that has to define which workaround is needed.</para>
|
||||
|
||||
<para>After you got your Mumbletech working, please send the
|
||||
|
|
@ -4473,14 +4474,14 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
|
|||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>Tagged command queueing</title>
|
||||
<title>Tagged command queuing</title>
|
||||
|
||||
<para>Modern SCSI devices, particularly magnetic disks,
|
||||
support what is called tagged command queuing (TCQ).</para>
|
||||
|
||||
<para>In a nutshell, TCQ allows the device to have multiple I/O
|
||||
requests outstanding at the same time. Because the device is
|
||||
intelligent, it can optimise its operations (like head
|
||||
intelligent, it can optimize its operations (like head
|
||||
positioning) based on its own request queue. On SCSI devices
|
||||
like RAID (Redundant Array of Independent Disks) arrays the TCQ
|
||||
function is indispensable to take advantage of the device's
|
||||
|
|
@ -4513,7 +4514,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
|
|||
different transfer speeds on the host bus (ISA or AT in this
|
||||
case). The controller is settable to different rates because not
|
||||
all motherboards can handle the higher speeds. Problems like
|
||||
hangups, bad data etc might be the result of using a higher data
|
||||
hang-ups, bad data etc might be the result of using a higher data
|
||||
transfer rate then your motherboard can stomach.</para>
|
||||
|
||||
<para>The solution is of course obvious: switch to a lower data
|
||||
|
|
@ -4575,7 +4576,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
|
||||
<listitem>
|
||||
<para>Disable tagged command queuing to make things as simple as
|
||||
possible (for a NCR hostadapter based system see man
|
||||
possible (for a NCR host adapter based system see man
|
||||
ncrcontrol)</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -4782,7 +4783,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
megabytes/sec you can get out of the drive.</para>
|
||||
|
||||
<para>(If you are a speed maniac and want a 10,000RPM drive for your
|
||||
cute little peecee, be my guest; however, those drives become
|
||||
cute little PC, be my guest; however, those drives become
|
||||
extremely hot. Don't even think about it if you don't have a fan
|
||||
blowing air <emphasis>directly at</emphasis> the drive or a
|
||||
properly ventilated disk enclosure.)</para>
|
||||
|
|
@ -4827,7 +4828,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<para>Most SCSI drives sold today are of 3.5" form factor. They
|
||||
come in two different heights; 1.6" (<quote>half-height</quote>) or
|
||||
1" (<quote>low-profile</quote>). The half-height drive is the same
|
||||
height as a CD-ROM drive. However, don't forget the spacing rule
|
||||
height as a CDROM drive. However, don't forget the spacing rule
|
||||
mentioned in the previous section. If you have three standard
|
||||
3.5" drive bays, you will not be able to put three half-height
|
||||
drives in there (without frying them, that is).</para>
|
||||
|
|
@ -4908,7 +4909,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
|
||||
<para>The &man.st.4; driver provides support for 8mm (Exabyte), 4mm
|
||||
(DAT: Digital Audio Tape), QIC (Quarter-Inch Cartridge), DLT
|
||||
(Digital Linear Tape), QIC Minicartridge and 9-track (remember the
|
||||
(Digital Linear Tape), QIC Mini cartridge and 9-track (remember the
|
||||
big reels that you see spinning in Hollywood computer rooms) tape
|
||||
drives. See the &man.st.4; manual page for a detailed
|
||||
description.</para>
|
||||
|
|
@ -4955,7 +4956,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<sect4>
|
||||
<title>QIC (Quarter-Inch Cartridge)</title>
|
||||
|
||||
<para><link linkend="hw-storage-anaconda">Archive Ananconda
|
||||
<para><link linkend="hw-storage-anaconda">Archive Anaconda
|
||||
2750</link></para>
|
||||
|
||||
<para><link linkend="hw-storage-viper60">Archive Viper
|
||||
|
|
@ -5176,7 +5177,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<para>This drives quirks are known and pre-compiled into the scsi
|
||||
tape device driver (&man.st.4;).</para>
|
||||
|
||||
<para>Under FreeBSD 2.2-current, use <command>mt blocksize
|
||||
<para>Under FreeBSD 2.2-CURRENT, use <command>mt blocksize
|
||||
512</command> to set the blocksize. (The particular drive had
|
||||
firmware revision 21247 -005. Other firmware revisions may behave
|
||||
differently) Previous versions of FreeBSD did not have this
|
||||
|
|
@ -5187,8 +5188,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<para>Reported by: Pedro A M Vazquez
|
||||
<email>vazquez@IQM.Unicamp.BR</email></para>
|
||||
|
||||
<para>Mike Smith
|
||||
<email>msmith@atrad.adelaide.edu.au</email></para>
|
||||
<para>&a.msmith;</para>
|
||||
</sect4>
|
||||
|
||||
<sect4 id="hw-storage-viper2525">
|
||||
|
|
@ -5219,7 +5219,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<para>The boot message identifier for this drive is <literal>Conner
|
||||
tape</literal>.</para>
|
||||
|
||||
<para>This is a floppy controller, minicartridge tape drive.</para>
|
||||
<para>This is a floppy controller, mini cartridge tape drive.</para>
|
||||
|
||||
<para>Native capacity is XXXX</para>
|
||||
|
||||
|
|
@ -5238,7 +5238,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
CTMS 3200 7.00</literal> <literal>type 1 removable SCSI
|
||||
2</literal>.</para>
|
||||
|
||||
<para>This is a minicartridge tape drive.</para>
|
||||
<para>This is a mini cartridge tape drive.</para>
|
||||
|
||||
<para>Native capacity is XXXX</para>
|
||||
|
||||
|
|
@ -5283,12 +5283,12 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<para>This is a mini-cartridge tape drive.</para>
|
||||
|
||||
<para>Native capacity is 1GB when using MC3000XL
|
||||
minicartridges.</para>
|
||||
mini cartridges.</para>
|
||||
|
||||
<para>Data transfer rate is XXX</para>
|
||||
|
||||
<para>This drive can read and write DC2300 (550MB), DC2750 (750MB),
|
||||
MC3000 (750MB), and MC3000XL (1GB) minicartridges.</para>
|
||||
MC3000 (750MB), and MC3000XL (1GB) mini cartridges.</para>
|
||||
|
||||
<para>WARNING: This drive does not meet the SCSI-2 specifications.
|
||||
The drive locks up completely in response to a SCSI MODE_SELECT
|
||||
|
|
@ -5297,8 +5297,8 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
|
||||
<screen>&prompt.root; <userinput>mt -f /dev/st0ctl.0 blocksize 1024</userinput></screen>
|
||||
|
||||
<para>Before using a minicartridge for the first time, the
|
||||
minicartridge must be formated. FreeBSD 2.1.0-RELEASE and
|
||||
<para>Before using a mini cartridge for the first time, the
|
||||
mini cartridge must be formated. FreeBSD 2.1.0-RELEASE and
|
||||
earlier:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>/sbin/scsi -f /dev/rst0.ctl -s 600 -c "4 0 0 0 0 0"</userinput></screen>
|
||||
|
|
@ -5340,8 +5340,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
|
||||
<para>Production of this drive has been discontinued.</para>
|
||||
|
||||
<para>Reported by: Mike Smith
|
||||
<email>msmith@atrad.adelaide.edu.au</email></para>
|
||||
<para>Reported by: &a.msmith;</para>
|
||||
</sect4>
|
||||
|
||||
<sect4 id="hw-storage-exb8500">
|
||||
|
|
@ -5580,7 +5579,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
|
|||
|
||||
<para>Data transfer rate is 160kB/s.</para>
|
||||
|
||||
<para>Reported by: mark thompson
|
||||
<para>Reported by: Mark Thompson
|
||||
<email>mark.a.thompson@pobox.com</email></para>
|
||||
</sect4>
|
||||
|
||||
|
|
@ -5674,10 +5673,10 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
|
|||
|
||||
<para>In order to get this drive to stream, set the blocksize to 512
|
||||
bytes (<command>mt blocksize 512</command>) reported by Kenneth
|
||||
Merry ken@ulc199.residence.gatech.edu</para>
|
||||
Merry <email>ken@ulc199.residence.gatech.edu</email>.</para>
|
||||
|
||||
<para><literal>SONY SDT-5000 327M</literal> information reported by
|
||||
Charles Henrich henrich@msu.edu</para>
|
||||
Charles Henrich <email>henrich@msu.edu</email>.</para>
|
||||
|
||||
<para>Reported by: &a.jmz;</para>
|
||||
</sect4>
|
||||
|
|
@ -5703,8 +5702,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
|
|||
<para>IBM and Emerald units will not work. Replacing the firmware
|
||||
EPROM of these units will solve the problem.</para>
|
||||
|
||||
<para>Reported by: Michael Smith
|
||||
<email>msmith@atrad.adelaide.edu.au</email></para>
|
||||
<para>Reported by: &a.msmith;</para>
|
||||
</sect4>
|
||||
|
||||
<sect4 id="hw-storage-tandberg3620">
|
||||
|
|
@ -5747,7 +5745,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
|
|||
|
||||
<para>This drives quirks are known and pre-compiled into the scsi
|
||||
tape device driver (&man.st.4;) beginning with FreeBSD
|
||||
2.2-current. For previous versions of FreeBSD, use
|
||||
2.2-CURRENT. For previous versions of FreeBSD, use
|
||||
<command>mt</command> to read one block from the tape, rewind the
|
||||
tape, and then execute the backup program (<command>mt fsr 1; mt
|
||||
rewind; dump ...</command>)</para>
|
||||
|
|
@ -5820,7 +5818,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>CD-ROM drives</title>
|
||||
<title>CDROM drives</title>
|
||||
|
||||
<para><emphasis>Contributed by &a.obrien;. 23 November
|
||||
1997.</emphasis></para>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.24 2000/05/02 22:40:41 unfurl Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.25 2000/06/08 01:55:49 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="advanced-networking">
|
||||
|
|
@ -399,7 +399,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
|
||||
<para>Luckily for us, on a FreeBSD system this setup is a snap. The
|
||||
processes that need to be running can all be run at boot time with
|
||||
a few modificationss to your <filename>/etc/rc.conf</filename>
|
||||
a few modifications to your <filename>/etc/rc.conf</filename>
|
||||
file.</para>
|
||||
|
||||
<para>On the NFS server make sure you have:</para>
|
||||
|
|
@ -758,7 +758,7 @@ diskless:\
|
|||
<row>
|
||||
<entry>swapsize
|
||||
<option><replaceable>size</replaceable></option></entry>
|
||||
<entry>set diskless swapsize in Kbytes</entry>
|
||||
<entry>set diskless swapsize in KBytes</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
|
|
@ -827,7 +827,7 @@ hostname myclient.mydomain</programlisting>
|
|||
as in the example above, the swapfile for myclient will be called
|
||||
<filename>/swapfs/swap.<replaceable>X.X.X.X</replaceable></filename>
|
||||
where <replaceable>X.X.X.X</replaceable> is the client's IP addr,
|
||||
eg:</para>
|
||||
e.g.:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>dd if=/dev/zero of=/swapfs/swap.192.1.2.4 bs=1k count=20000</userinput></screen>
|
||||
|
||||
|
|
@ -900,7 +900,7 @@ hostname myclient.mydomain</programlisting>
|
|||
<ulink url="http://alumni.caltech.edu/~dank/isdn/">Dan Kegel's ISDN
|
||||
Page</ulink>.</para>
|
||||
|
||||
<para>A quick simple roadmap to ISDN follows:</para>
|
||||
<para>A quick simple road map to ISDN follows:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
@ -910,14 +910,14 @@ hostname myclient.mydomain</programlisting>
|
|||
|
||||
<listitem>
|
||||
<para>If you are planning to use ISDN primarily to connect to the
|
||||
Internet with an Internet Provider on a dialup non-dedicated basis,
|
||||
Internet with an Internet Provider on a dial-up non-dedicated basis,
|
||||
I suggest you look into Terminal Adapters. This will give you the
|
||||
most flexibility, with the fewest problems, if you change
|
||||
providers.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>If you are connecting two lans together, or connecting to the
|
||||
<para>If you are connecting two LANs together, or connecting to the
|
||||
Internet with a dedicated ISDN connection, I suggest you consider
|
||||
the stand alone router/bridge option.</para>
|
||||
</listitem>
|
||||
|
|
@ -991,7 +991,7 @@ subscribe freebsd-isdn</programlisting>
|
|||
<para>The main advantage of using a TA to connect to an Internet
|
||||
Provider is that you can do Dynamic PPP. As IP address space becomes
|
||||
more and more scarce, most providers are not willing to provide you
|
||||
with a static IP anymore. Most standalone routers are not able to
|
||||
with a static IP anymore. Most stand-alone routers are not able to
|
||||
accommodate dynamic IP allocation.</para>
|
||||
|
||||
<para>TA's completely rely on the PPP daemon that you are running for
|
||||
|
|
@ -1039,11 +1039,11 @@ subscribe freebsd-isdn</programlisting>
|
|||
save you having to buy another serial cable, and find another empty
|
||||
electrical socket.</para>
|
||||
|
||||
<para>A synchronous card with a TA is at least as fast as a standalone
|
||||
<para>A synchronous card with a TA is at least as fast as a stand-alone
|
||||
router, and with a simple 386 FreeBSD box driving it, probably more
|
||||
flexible.</para>
|
||||
|
||||
<para>The choice of sync/TA vs standalone router is largely a religious
|
||||
<para>The choice of sync/TA v.s. stand-alone router is largely a religious
|
||||
issue. There has been some discussion of this in the mailing lists.
|
||||
I suggest you search the <ulink
|
||||
url="http://www.FreeBSD.org/search.html">archives</ulink> for the
|
||||
|
|
@ -1051,7 +1051,7 @@ subscribe freebsd-isdn</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Standalone ISDN Bridges/Routers</title>
|
||||
<title>Stand-alone ISDN Bridges/Routers</title>
|
||||
|
||||
<para>ISDN bridges or routers are not at all specific to FreeBSD or any
|
||||
other operating system. For a more complete description of routing
|
||||
|
|
@ -1097,12 +1097,12 @@ subscribe freebsd-isdn</programlisting>
|
|||
|
|
||||
---Windows 95 (Do not admit to owning it)
|
||||
|
|
||||
Standalone router
|
||||
Stand-alone router
|
||||
|
|
||||
ISDN BRI line</programlisting>
|
||||
|
||||
<para>If your home/branch office is only one computer you can use a
|
||||
twisted pair crossover cable to connect to the standalone router
|
||||
twisted pair crossover cable to connect to the stand-alone router
|
||||
directly.</para>
|
||||
</example>
|
||||
|
||||
|
|
@ -1121,7 +1121,7 @@ ISDN BRI line</programlisting>
|
|||
| |
|
||||
| ---Windows 95
|
||||
| B |
|
||||
|___---Standalone router
|
||||
|___---Stand-alone router
|
||||
|
|
||||
ISDN BRI line</programlisting>
|
||||
</example>
|
||||
|
|
@ -1134,12 +1134,12 @@ ISDN BRI line</programlisting>
|
|||
etc.</para>
|
||||
|
||||
<para>This can be very useful feature, for example if you have an
|
||||
dedicated internet ISDN connection at your office and would like to
|
||||
dedicated ISDN connection at your office and would like to
|
||||
tap into it, but don't want to get another ISDN line at work. A router
|
||||
at the office location can manage a dedicated B channel connection
|
||||
(64Kbs) to the internet, as well as a use the other B channel for a
|
||||
separate data connection. The second B channel can be used for
|
||||
dialin, dialout or dynamically bond(MPP etc.) with the first B channel
|
||||
dial-in, dial-out or dynamically bond(MPP etc.) with the first B channel
|
||||
for more bandwidth.</para>
|
||||
|
||||
<para>An Ethernet bridge will also allow you to transmit more than just
|
||||
|
|
@ -1167,10 +1167,10 @@ ISDN BRI line</programlisting>
|
|||
<sect2>
|
||||
<title>How does it work?</title>
|
||||
|
||||
<para>There are 3 types of hosts in an NIS enviornment; master
|
||||
<para>There are 3 types of hosts in an NIS environment; master
|
||||
servers, slave servers, and clients. Servers act as a central
|
||||
repository for host configuration information. Master servers
|
||||
hold the authoritatve copy of this information, while slave
|
||||
hold the authoritative copy of this information, while slave
|
||||
servers mirror this information for redundancy. Clients rely on
|
||||
the servers to provide this information to them.</para>
|
||||
|
||||
|
|
@ -1217,7 +1217,7 @@ ISDN BRI line</programlisting>
|
|||
<sect4>
|
||||
<title>Physical Server Requirements</title>
|
||||
|
||||
<para>There are several things to keep in mind when chosing a
|
||||
<para>There are several things to keep in mind when choosing a
|
||||
machine to use as a NIS server. One of the unfortunate things
|
||||
about NIS is the level of dependency the clients have on the
|
||||
server. If a client cannot contact the server for its NIS
|
||||
|
|
@ -1259,7 +1259,7 @@ ISDN BRI line</programlisting>
|
|||
<sect4>
|
||||
<title>Setting up a NIS master server</title>
|
||||
|
||||
<para>Setting up a master NIS server can be relativly straight
|
||||
<para>Setting up a master NIS server can be relatively straight
|
||||
forward, depending on your needs. FreeBSD comes with a handy
|
||||
script called <command>ypinit</command> that makes the initial
|
||||
setup procedure very easy. A few steps are needed ahead of
|
||||
|
|
@ -1392,46 +1392,46 @@ Ok, please remember to go back and redo manually whatever fails.
|
|||
If you don't, something might not work.
|
||||
There will be no further questions. The remainder of the procedure
|
||||
should take a few minutes, to copy the databases from master.example.com.
|
||||
Transfering netgroup...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering netgroup.byuser...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering netgroup.byhost...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering master.passwd.byuid...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering passwd.byuid...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering passwd.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering group.bygid...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering group.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering services.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering rpc.bynumber...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering rpc.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering protocols.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering master.passwd.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering networks.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering networks.byaddr...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering netid.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering hosts.byaddr...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering protocols.bynumber...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering ypservers...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transfering hosts.byname...
|
||||
ypxfr: Exiting: Map successfully transfered
|
||||
Transferring netgroup...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring netgroup.byuser...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring netgroup.byhost...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring master.passwd.byuid...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring passwd.byuid...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring passwd.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring group.bygid...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring group.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring services.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring rpc.bynumber...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring rpc.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring protocols.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring master.passwd.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring networks.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring networks.byaddr...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring netid.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring hosts.byaddr...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring protocols.bynumber...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring ypservers...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
Transferring hosts.byname...
|
||||
ypxfr: Exiting: Map successfully transferred
|
||||
|
||||
slave.example.com has been setup as an YP slave server without any errors.
|
||||
Don't forget to update map ypservers on master.example.com.</screen>
|
||||
|
|
@ -1622,7 +1622,7 @@ Don't forget to update map ypservers on master.example.com.</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>libscrypt vs. libdescrypt</title>
|
||||
<title>libscrypt v.s. libdescrypt</title>
|
||||
|
||||
<para>One of the most common issues that people run into when trying
|
||||
to implement NIS is crypt library compatibility. If your NIS
|
||||
|
|
@ -1644,7 +1644,7 @@ lrwxr-xr-x 1 root wheel 16 Nov 8 14:27 /usr/lib/libdescrypt.so@ -> libdes
|
|||
-r--r--r-- 1 root wheel 14750 Nov 8 14:27 /usr/lib/libdescrypt_p.a</screen>
|
||||
|
||||
<para>If the machine is configured to use the standard FreeBSD MD5
|
||||
crypt libraries they will look somethine like this:</para>
|
||||
crypt libraries they will look something like this:</para>
|
||||
|
||||
<screen>
|
||||
&prompt.user; <userinput>ls -l /usr/lib/*crypt*</userinput>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.22 2000/05/15 00:10:38 joe Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.23 2000/06/08 01:55:59 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="backups">
|
||||
|
|
@ -33,7 +33,7 @@
|
|||
x 12 mm) than 8mm cartridges. 4mm, like 8mm, has comparatively short
|
||||
head life for the same reason, both use helical scan.</para>
|
||||
|
||||
<para>Data thruput on these drives starts ~150kB/s, peaking at ~500kB/s.
|
||||
<para>Data throughput on these drives starts ~150kB/s, peaking at ~500kB/s.
|
||||
Data capacity starts at 1.3 GB and ends at 2.0 GB. Hardware
|
||||
compression, available with most of these drives, approximately
|
||||
doubles the capacity. Multi-drive tape library units can have 6
|
||||
|
|
@ -60,7 +60,7 @@
|
|||
One downside of 8mm tape is relatively short head and tape life due to
|
||||
the high rate of relative motion of the tape across the heads.</para>
|
||||
|
||||
<para>Data thruput ranges from ~250kB/s to ~500kB/s. Data sizes start
|
||||
<para>Data throughput ranges from ~250kB/s to ~500kB/s. Data sizes start
|
||||
at 300 MB and go up to 7 GB. Hardware compression, available with
|
||||
most of these drives, approximately doubles the capacity. These
|
||||
drives are available as single units or multi-drive tape libraries
|
||||
|
|
@ -99,7 +99,7 @@
|
|||
also use 1/4" wide tape are discussed separately. Tape libraries and
|
||||
changers are not available.</para>
|
||||
|
||||
<para>Data thruput ranges from ~150kB/s to ~500kB/s. Data capacity
|
||||
<para>Data throughput ranges from ~150kB/s to ~500kB/s. Data capacity
|
||||
ranges from 40 MB to 15 GB. Hardware compression is available on many
|
||||
of the newer QIC drives. QIC drives are less frequently installed;
|
||||
they are being supplanted by DAT drives.</para>
|
||||
|
|
@ -139,7 +139,7 @@
|
|||
both the supply and take-up spools located inside the tape cartridge
|
||||
itself.</para>
|
||||
|
||||
<para>Data thruput is approximately 1.5MB/s, three times the thruput of
|
||||
<para>Data throughput is approximately 1.5MB/s, three times the throughput of
|
||||
4mm, 8mm, or QIC tape drives. Data capacities range from 10GB to 20GB
|
||||
for a single drive. Drives are available in both multi-tape changers
|
||||
and multi-tape, multi-drive tape libraries containing from 5 to 900
|
||||
|
|
@ -381,7 +381,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
two copies of
|
||||
each.</para>
|
||||
|
||||
<para>Second, determine that the boot and fixit floppies
|
||||
<para>Second, determine that the boot and fix-it floppies
|
||||
(<filename>boot.flp</filename> and <filename>fixit.flp</filename>)
|
||||
have all your devices. The easiest way to check is to reboot your
|
||||
machine with the boot floppy in the floppy drive and check the boot
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.224 2000/06/12 12:48:31 asmodai Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.225 2000/06/12 23:38:59 will Exp $
|
||||
-->
|
||||
|
||||
<chapter id="contrib">
|
||||
|
|
@ -284,7 +284,7 @@
|
|||
<orderedlist>
|
||||
<listitem>
|
||||
<para>NetWare Server (protected mode ODI driver) loader and
|
||||
subservices to allow the use of ODI card drivers supplied with
|
||||
sub-services to allow the use of ODI card drivers supplied with
|
||||
network cards. The same thing for NDIS drivers and NetWare SCSI
|
||||
drivers.</para>
|
||||
</listitem>
|
||||
|
|
@ -303,7 +303,7 @@
|
|||
<para>A concerted effort at support for portable computers. This is
|
||||
somewhat handled by changing PCMCIA bridging rules and power
|
||||
management event handling. But there are things like detecting
|
||||
internal vs. external display and picking a different screen
|
||||
internal v.s.. external display and picking a different screen
|
||||
resolution based on that fact, not spinning down the disk if the
|
||||
machine is in dock, and allowing dock-based cards to disappear
|
||||
without affecting the machines ability to boot (same issue for
|
||||
|
|
@ -363,7 +363,7 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>If you know of any bugfixes which have been successfully
|
||||
<para>If you know of any bug fixes which have been successfully
|
||||
applied to -current but have not been merged into -stable after a
|
||||
decent interval (normally a couple of weeks), send the committer a
|
||||
polite reminder.</para>
|
||||
|
|
@ -546,7 +546,7 @@
|
|||
|
||||
<para>In the rare case of a significant contribution of a large body
|
||||
work, or the addition of an important new feature to FreeBSD, it
|
||||
becomes almost always necessary to either send changes as uuencode'd
|
||||
becomes almost always necessary to either send changes as uuencoded
|
||||
tar files or upload them to our ftp site <ulink
|
||||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/">ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/</ulink>.</para>
|
||||
|
||||
|
|
@ -731,7 +731,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
<title>Donors Gallery</title>
|
||||
|
||||
<para>The FreeBSD Project is indebted to the following donors and would
|
||||
like to publically thank them here!</para>
|
||||
like to publicly thank them here!</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
@ -846,7 +846,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
<listitem>
|
||||
<para><ulink url="http://www.cdrom.co.jp/">Laser5</ulink> of Japan
|
||||
(a portion of the profits from sales of their various FreeBSD
|
||||
CD-ROMs).</para>
|
||||
CDROMs).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -983,10 +983,10 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
<listitem>
|
||||
<para>The <ulink url="http://www.interface-business.de/">interface
|
||||
business GmbH, Dresden</ulink> has been patiently supporting
|
||||
&a.joerg; who has often preferred FreeBSD work over paywork, and
|
||||
&a.joerg; who has often preferred FreeBSD work over paid work, and
|
||||
used to fall back to their (quite expensive) EUnet Internet
|
||||
connection whenever his private connection became too slow or
|
||||
flakey to work with it...</para>
|
||||
flaky to work with it...</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -1126,7 +1126,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Adrian Chadd <email>adrian@freebsd.org</email></para>
|
||||
<para>Adrian Chadd <email>adrian@FreeBSD.org</email></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.47 2000/06/08 01:56:06 jim Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.48 2000/06/09 22:54:37 nik Exp $
|
||||
-->
|
||||
|
||||
<chapter id="cutting-edge">
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
</sect1>
|
||||
|
||||
<sect1 id="current-stable">
|
||||
<title>-CURRENT vs. -STABLE</title>
|
||||
<title>-CURRENT v.s.. -STABLE</title>
|
||||
|
||||
<para>There are two development branches to FreeBSD; -CURRENT and
|
||||
-STABLE. This section will explain a bit about each and describe
|
||||
|
|
@ -183,7 +183,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
<ulink
|
||||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/</ulink>.
|
||||
We also use <command>wu-ftpd</command> which allows
|
||||
compressed/tar'd grabbing of whole trees. e.g. you
|
||||
compressed/tarred grabbing of whole trees. e.g. you
|
||||
see:</para>
|
||||
|
||||
<screen>usr.bin/lex</screen>
|
||||
|
|
@ -354,7 +354,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-stable/">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-stable/</ulink></para>
|
||||
|
||||
<para>We also use <command>wu-ftpd</command> which allows
|
||||
compressed/tar'd grabbing of whole trees. e.g. you
|
||||
compressed/tarred grabbing of whole trees. e.g. you
|
||||
see:</para>
|
||||
|
||||
<screen>usr.bin/lex</screen>
|
||||
|
|
@ -707,7 +707,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
</example>
|
||||
|
||||
<example>
|
||||
<title>Creating a list of changes (as unidiffs) to &man.ls.1;</title>
|
||||
<title>Creating a list of changes (as unified diffs) to &man.ls.1;</title>
|
||||
|
||||
<screen>
|
||||
&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
|
||||
|
|
@ -764,7 +764,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
<sect1 id="makeworld">
|
||||
<title>Using <command>make world</command></title>
|
||||
|
||||
<para>Once you have synchronised your local source tree against a
|
||||
<para>Once you have synchronized your local source tree against a
|
||||
particular version of FreeBSD (<literal>stable</literal>,
|
||||
<literal>current</literal> and so on) you must then use the source
|
||||
tree to rebuild the system.</para>
|
||||
|
|
@ -779,7 +779,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
when you make mistakes, or when mistakes made by others in the
|
||||
source tree render your system unbootable.</para>
|
||||
|
||||
<para>Make sure you have taken a backup. And have a fixit floppy to
|
||||
<para>Make sure you have taken a backup. And have a fix-it floppy to
|
||||
hand. I have never needed to use them, and, touch wood, I never
|
||||
will, but it is always better to be safe than sorry.</para>
|
||||
</warning>
|
||||
|
|
@ -1006,7 +1006,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
|
|||
|
||||
<screen>&prompt.root; <userinput>make -DNOPROFILE=true <replaceable>target</replaceable></userinput></screen>
|
||||
|
||||
<para>is another way of specifying that profiled libaries should
|
||||
<para>is another way of specifying that profiled libraries should
|
||||
not be built, and corresponds with the</para>
|
||||
|
||||
<programlisting>NOPROFILE= true
|
||||
|
|
@ -1261,7 +1261,7 @@ Script done, …</screen>
|
|||
|
||||
<tip>
|
||||
<title>Name the new root directory
|
||||
(<filename>/var/tmp/root</filename>)with a timestamp, so you can
|
||||
(<filename>/var/tmp/root</filename>)with a time stamp, so you can
|
||||
easily compare differences between versions</title>
|
||||
|
||||
<para>Frequently remaking the world means that you have to update
|
||||
|
|
@ -1348,7 +1348,7 @@ Script done, …</screen>
|
|||
<para>If you are using DEVFS then this is probably unnecessary.</para>
|
||||
</note>
|
||||
|
||||
<para>For safety's sake, this is a multistep process.</para>
|
||||
<para>For safety's sake, this is a multi-step process.</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
|
|
@ -1362,7 +1362,7 @@ Script done, …</screen>
|
|||
<para>Now, take a snapshot of your current
|
||||
<filename>/dev</filename>. This snapshot needs to contain the
|
||||
permissions, ownerships, major and minor numbers of each filename,
|
||||
but it should not contain the timestamps. The easiest way to do
|
||||
but it should not contain the time stamps. The easiest way to do
|
||||
this is to use &man.awk.1; to strip out some of the
|
||||
information.</para>
|
||||
|
||||
|
|
@ -1399,11 +1399,11 @@ Script done, …</screen>
|
|||
<title>Update <filename>/stand</filename></title>
|
||||
|
||||
<note>
|
||||
<para>This step is included only for completeness, it can safely be
|
||||
<para>This step is included only for completeness. It can safely be
|
||||
omitted.</para>
|
||||
</note>
|
||||
|
||||
<para>For completenesses sake you may want to update the files in
|
||||
<para>For the sake of completeness, you may want to update the files in
|
||||
<filename>/stand</filename> as well. These files consist of hard
|
||||
links to the <filename>/stand/sysinstall</filename> binary. This
|
||||
binary should be statically linked, so that it can work when no other
|
||||
|
|
@ -1769,8 +1769,8 @@ Antonio</screen>
|
|||
<listitem>
|
||||
<para>Also in <filename>/etc/make.conf</filename>, set
|
||||
<quote>CFLAGS</quote> to something like <quote>-O
|
||||
-pipe</quote>. The optimisation <quote>-O2</quote> is much
|
||||
slower, and the optimisation difference between
|
||||
-pipe</quote>. The optimization <quote>-O2</quote> is much
|
||||
slower, and the optimization difference between
|
||||
<quote>-O</quote> and <quote>-O2</quote> is normally
|
||||
negligible. <quote>-pipe</quote> lets the compiler use
|
||||
pipes rather than temporary files for communication, which
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml,v 1.18 2000/04/30 22:10:06 nik Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/disks/chapter.sgml,v 1.19 2000/06/08 01:56:07 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="disks">
|
||||
|
|
@ -54,7 +54,7 @@
|
|||
<title>An illustration from the files of Bill and Fred's Exceptional
|
||||
Adventures:</title>
|
||||
|
||||
<para>Bill breaks-down an older WIntel box to make another FreeBSD box
|
||||
<para>Bill breaks-down an older Wintel box to make another FreeBSD box
|
||||
for Fred. Bill installs a single SCSI drive as SCSI unit zero, and
|
||||
installs FreeBSD on it.</para>
|
||||
|
||||
|
|
@ -75,7 +75,7 @@
|
|||
<para>Fred continues his work for several days, and soon Bill and Fred
|
||||
decide that it's time for a new adventure -- time to upgrade to a
|
||||
newer version of FreeBSD. Bill removes SCSI unit zero because it was
|
||||
a bit flakey, and replaces it with another identical disk drive from
|
||||
a bit flaky, and replaces it with another identical disk drive from
|
||||
the "archive." Bill then installs the new version of FreeBSD onto the
|
||||
new SCSI unit zero using Fred's magic internet FTP floppies. The
|
||||
installation goes well.</para>
|
||||
|
|
@ -104,7 +104,7 @@
|
|||
|
||||
<para>We are delighted to mention that no data bytes were killed or
|
||||
harmed in any way by our discovery of this phenomenon. The older SCSI
|
||||
unit zero was retrieved from the bonepile, and all of Fred's work was
|
||||
unit zero was retrieved from the bone pile, and all of Fred's work was
|
||||
returned to him, (and now Bill knows that he can count as high as
|
||||
zero).</para>
|
||||
|
||||
|
|
@ -116,7 +116,7 @@
|
|||
<sect1 id="disks-naming">
|
||||
<title>Disk Naming</title>
|
||||
|
||||
<para>Physical drives come in two main flavours,
|
||||
<para>Physical drives come in two main flavors,
|
||||
<acronym>IDE</acronym>, or <acronym>SCSI</acronym>; but there
|
||||
are also drives backed by RAID controllers, flash memory, and so
|
||||
forth. Since these behave quite differently, they have their
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.43 2000/04/17 16:10:31 phantom Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.44 2000/06/08 01:56:07 jim Exp $
|
||||
-->
|
||||
|
||||
<appendix id="eresources">
|
||||
|
|
@ -434,7 +434,7 @@ help
|
|||
subscriber overlap and except for the most esoteric mixes (say
|
||||
"-stable & -scsi"), there really is no reason to post to more
|
||||
than one list at a time. If a message is sent to you in such a
|
||||
way that multiple mailing lists appear on the Cc line then the cc
|
||||
way that multiple mailing lists appear on the Cc line then the Cc
|
||||
line should also be trimmed before sending it out again.
|
||||
<emphasis>You are <emphasis>still</emphasis> responsible for your
|
||||
own cross-postings, no matter who the originator might have
|
||||
|
|
@ -1235,7 +1235,7 @@ help
|
|||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="http://www.nz.FreeBSD.org/">http://www.nz.FreeBSD.org/</ulink> — New Zeland.</para>
|
||||
url="http://www.nz.FreeBSD.org/">http://www.nz.FreeBSD.org/</ulink> — New Zealand.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -1423,15 +1423,15 @@ help
|
|||
<tbody>
|
||||
<row>
|
||||
<entry>storm.uk.FreeBSD.org</entry>
|
||||
<entry>ssh only</entry>
|
||||
<entry>Read-only cvs, personal webspace, email</entry>
|
||||
<entry>SSH only</entry>
|
||||
<entry>Read-only cvs, personal web space, email</entry>
|
||||
<entry>&a.brian</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>dogma.freebsd-uk.eu.org</entry>
|
||||
<entry>Telnet/FTP/SSH</entry>
|
||||
<entry>E-Mail, Webspace, Anonymous FTP</entry>
|
||||
<entry>E-Mail, Web space, Anonymous FTP</entry>
|
||||
<entry>Lee Johnston
|
||||
<email>lee@uk.FreeBSD.org</email></entry>
|
||||
</row>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml,v 1.31 2000/04/02 19:38:11 chris Exp $
|
||||
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/hw/chapter.sgml,v 1.32 2000/06/08 01:56:07 jim Exp $
|
||||
-->
|
||||
|
||||
<appendix id="hw">
|
||||
|
|
@ -74,7 +74,7 @@
|
|||
<para>For Pentium Pro (P6) systems, I'm quite fond of the <ulink
|
||||
url="http://www.tyan.com/html/products.html">Tyan</ulink> S1668
|
||||
dual-processor motherboard as well as the Intel PR440FX motherboard
|
||||
with on-board SCSI WIDE and 100/10MB Intel Etherexpress NIC. You
|
||||
with on-board SCSI WIDE and 100/10MB Intel EtherExpress NIC. You
|
||||
can build a dandy little single or dual processor system (which is
|
||||
supported in FreeBSD 3.0) for very little cost now that the Pentium
|
||||
Pro 180/256K chips have fallen so greatly in price, but no telling
|
||||
|
|
@ -153,7 +153,7 @@
|
|||
|
||||
<para>My SCSI preferences extend to SCSI CDROM drives as well, and
|
||||
while the <ulink url="http://www.toshiba.com/">Toshiba</ulink> drives
|
||||
have always been favourites of mine (in whatever speed is hot that
|
||||
have always been favorites of mine (in whatever speed is hot that
|
||||
week), I'm still fond of my good old <ulink
|
||||
url="http://www.plextor.com/">Plextor</ulink> PX-12CS drive. It's
|
||||
only a 12 speed, but it's offered excellent performance and
|
||||
|
|
@ -263,13 +263,13 @@
|
|||
then <ulink url="http://www.dgii.com/">Digi International</ulink>
|
||||
makes the <ulink
|
||||
url="http://www.dgii.com/prodprofiles/profiles-prices/digiprofiles/digispecs/sync570.html">SYNC/570</ulink>
|
||||
series, with drivers now in FreeBSD-current. <ulink
|
||||
series, with drivers now in FreeBSD-CURRENT. <ulink
|
||||
url="http://www.etinc.com/">Emerging Technologies</ulink> also
|
||||
manufactures a board with T1/E1 capabilities, using software they
|
||||
provide. I have no direct experience using either product,
|
||||
however.</para>
|
||||
|
||||
<para>Multiport card options are somewhat more numerous, though it has
|
||||
<para>multiport card options are somewhat more numerous, though it has
|
||||
to be said that FreeBSD's support for <ulink
|
||||
url="http://www.cyclades.com/">Cyclades</ulink>'s products is
|
||||
probably the tightest, primarily as a result of that company's
|
||||
|
|
@ -291,7 +291,7 @@
|
|||
Labs</ulink> AWE32 though just about anything from Creative Labs
|
||||
will generally work these days. This is not to say that other types
|
||||
of sound cards don't also work, simply that I have little experience
|
||||
with them (I was a former GUS fan, but Gravis's soundcard situation
|
||||
with them (I was a former GUS fan, but Gravis's sound card situation
|
||||
has been dire for some time).</para>
|
||||
</sect3>
|
||||
|
||||
|
|
@ -379,10 +379,11 @@
|
|||
|
||||
<listitem>
|
||||
<para>Works fine, but many MB manufactures leave out the
|
||||
external dirty bit SRAM needed for write back operation. Work
|
||||
arounds are either run it in write through mode, or get the
|
||||
dirty bit SRAM installed. (I have these for the ASUS
|
||||
PCI/I-486SP3G rev 1.6 and later boards).</para>
|
||||
external dirty bit SRAM needed for write back operation.
|
||||
You can work around this either by running it in write
|
||||
through mode, or get the dirty bit SRAM installed (I
|
||||
have these for the ASUS PCI/I-486SP3G rev 1.6 and later
|
||||
boards).</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -460,7 +461,7 @@
|
|||
<title>P6 class (Pentium Pro/Pentium II)</title>
|
||||
|
||||
<para>Both the Pentium Pro and Pentium II work fine with FreeBSD. In
|
||||
fact, our main ftp site <ulink
|
||||
fact, our main FTP site <ulink
|
||||
url="ftp://ftp.FreeBSD.org/">ftp.FreeBSD.org</ulink> (also known
|
||||
as "<filename>ftp.cdrom.com</filename>", world's largest ftp site)
|
||||
runs FreeBSD on a Pentium Pro. <ulink
|
||||
|
|
@ -474,7 +475,7 @@
|
|||
<para>The Intel Pentium (P54C), Pentium MMX (P55C), AMD K6 and
|
||||
Cyrix/IBM 6x86MX processors are all reported to work with FreeBSD.
|
||||
I will not go into details of which processor is faster than what,
|
||||
there are zillions of web sites on the Internet that tells you one
|
||||
there are millions of web sites on the Internet that tells you one
|
||||
way or another. <!-- smiley --><emphasis>:)</emphasis></para>
|
||||
|
||||
<note>
|
||||
|
|
@ -656,7 +657,7 @@
|
|||
<title>286 class</title>
|
||||
|
||||
<para>Sorry, FreeBSD does not run on 80286 machines. It is nearly
|
||||
impossible to run today's large full-featured UNIXes on such
|
||||
impossible to run today's large full-featured unices on such
|
||||
hardware.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
|
@ -840,7 +841,7 @@
|
|||
when the device connected to the UART is a modem, the modem may
|
||||
report the presence of a carrier on the phone line while the
|
||||
computer may be able to instruct the modem to reset itself or to
|
||||
not take calls by asserting or deasserting one more more of these
|
||||
not take calls by asserting or disasserting one more more of these
|
||||
extra signals. The function of each of these additional signals is
|
||||
defined in the EIA RS232-C standard.</para>
|
||||
</sect4>
|
||||
|
|
@ -1622,7 +1623,7 @@ INS8250 -> INS8250B
|
|||
combinations of events occur that were not well tested or
|
||||
considered in the Windows driver. This is because most modem
|
||||
vendors and 16550-clone makers use the Microsoft drivers from
|
||||
Windows for Workgroups 3.11 and the Microsoft MSD utility as the
|
||||
Windows for Workgroups 3.11 and the Microsoft MS-DOS utility as the
|
||||
primary tests for compatibility with the NS16550A. This
|
||||
over-simplistic criteria means that if a different operating
|
||||
system is used, problems could appear due to subtle differences
|
||||
|
|
@ -2549,7 +2550,7 @@ INS8250 -> INS8250B
|
|||
<listitem>
|
||||
<para>By default this part is similar to the NS16550A, but an
|
||||
extended 32-byte send and receive buffer can be optionally
|
||||
enabled. Made by Startech.</para>
|
||||
enabled. Made by StarTech.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -2769,7 +2770,7 @@ sio16: type 16550A (multiport master)</screen>
|
|||
&prompt.root; <userinput>./MAKEDEV ttyg</userinput>
|
||||
&prompt.root; <userinput>./MAKEDEV cuag</userinput></screen>
|
||||
|
||||
<para>If you do not want or need callout devices for some
|
||||
<para>If you do not want or need call-out devices for some
|
||||
reason, you can dispense with making the
|
||||
<filename>cua*</filename> devices.</para>
|
||||
</step>
|
||||
|
|
@ -2806,7 +2807,7 @@ sio16: type 16550A (multiport master)</screen>
|
|||
need to configure them as <devicename>COM2</devicename> (aka
|
||||
<devicename>sio1</devicename>–I/O address 0x2F8 and IRQ 3),
|
||||
and the third port (aka <devicename>sio2</devicename>) as I/O
|
||||
0x3E8 and IRQ 5. Obviously this is a waste of IRQ ressources, as
|
||||
0x3E8 and IRQ 5. Obviously this is a waste of IRQ resources, as
|
||||
it should be basically possible to run both extension board ports
|
||||
using a single IRQ with the <literal>COM_MULTIPORT</literal>
|
||||
configuration described in the previous sections.</para>
|
||||
|
|
@ -2838,7 +2839,7 @@ IRQ 2 3 4 5</programlisting>
|
|||
<para>You need to decouple the IRQ drivers for the two UARTs, so
|
||||
that the IRQ line of the board only goes up if (and only if) one
|
||||
of the UARTs asserts a IRQ, and stays low otherwise. The solution
|
||||
was proposed by Jrg Wunsch
|
||||
was proposed by Joerg Wunsch
|
||||
<email>j@ida.interface-business.de</email>: To solder up a
|
||||
wired-or consisting of two diodes (Germanium or Schottky-types
|
||||
strongly preferred) and a 1 kOhm resistor. Here is the schematic,
|
||||
|
|
@ -2873,7 +2874,7 @@ device sio2 at isa? port "IO_COM3" tty flags 0x205 irq 3</programlis
|
|||
|
||||
<para>Note that the <literal>flags</literal> setting for
|
||||
<devicename>sio1</devicename> and <devicename>sio2</devicename> is
|
||||
truely essential; refer to
|
||||
truly essential; refer to
|
||||
&man.sio.4; for details. (Generally, the <literal>2</literal> in
|
||||
the "flags" attribute refers to <devicename>sio</devicename>2
|
||||
which holds the IRQ, and you surely want a <literal>5</literal>
|
||||
|
|
@ -2895,7 +2896,7 @@ sio2: type 16550A (multiport master)</screen>
|
|||
the basic idea is that you observe <literal>0x1</literal> in the
|
||||
first, third, and fourth place. This means that the corresponding
|
||||
IRQ was set upon output and cleared after, which is just what we
|
||||
would expect. If your kernel does not display this behaviour, most
|
||||
would expect. If your kernel does not display this behavior, most
|
||||
likely there is something wrong with your wiring.</para>
|
||||
</sect4>
|
||||
</sect3>
|
||||
|
|
@ -2980,7 +2981,7 @@ ttyc7 "/usr/libexec/getty std.38400" unknown on insecure</programlisting>
|
|||
use I/O locations, but instead require a 32K chunk of memory. The
|
||||
factory configuration for ISA cards places this at
|
||||
<literal>0xd0000-0xd7fff</literal>.
|
||||
They also require an IRQ. PCI cards will, of course, autoconfigure
|
||||
They also require an IRQ. PCI cards will, of course, auto-configure
|
||||
themselves.</para>
|
||||
|
||||
<para>You can attach up to 4 external modules to each host card. The
|
||||
|
|
@ -3127,7 +3128,7 @@ moused_port="/dev/psm0"</programlisting>
|
|||
mouse daemon you will need to include the following text in
|
||||
<filename>/etc/rc.conf</filename>. This example assumes that the
|
||||
mouse is connected to <devicename>COM1:</devicename> and can be
|
||||
automatically recognised by the mouse daemon.</para>
|
||||
automatically recognized by the mouse daemon.</para>
|
||||
|
||||
<programlisting>moused_enable="YES"
|
||||
moused_type="auto"
|
||||
|
|
@ -3165,7 +3166,7 @@ moused_port="/dev/cuaa0"</programlisting>
|
|||
|
||||
<para>The USB device drivers are a relatively new addition to
|
||||
FreeBSD and have not yet been included in the GENERIC kernel. The
|
||||
following prodecure is an example of how to setup the relevant
|
||||
following procedure is an example of how to setup the relevant
|
||||
drivers on a typical system.</para>
|
||||
|
||||
<procedure>
|
||||
|
|
@ -3350,7 +3351,7 @@ moused_port="/dev/ums0"</programlisting>
|
|||
<para>Mainstream ESDI drives use 34 to 36 sectors per track. Most
|
||||
(older) controllers cannot handle more than this number of
|
||||
sectors. Newer, higher capacity, drives use higher numbers of
|
||||
sectors per track. For instance, I own a 670 Mb drive that has 54
|
||||
sectors per track. For instance, I own a 670 MB drive that has 54
|
||||
sectors per track.</para>
|
||||
|
||||
<para>In my case, the controller could not handle this number of
|
||||
|
|
@ -3582,7 +3583,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
BIOS to allow the BIOS to boot it.</para>
|
||||
|
||||
<para>Before using <command>NEFMT.EXE</command> I tried to format
|
||||
the disk using the ACB-2320 BIOS builtin formatter. This proved
|
||||
the disk using the ACB-2320 BIOS built-in formatter. This proved
|
||||
to be a show stopper, because it did not give me an option to
|
||||
disable spare sectoring. With spare sectoring enabled the FreeBSD
|
||||
installation process broke down on the <command>bad144</command>
|
||||
|
|
@ -3675,7 +3676,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
<para>After some time an industry effort was started to come to a more
|
||||
strict standard allowing devices from different vendors to work
|
||||
together. This effort was recognized in the ANSI SCSI-1 standard.
|
||||
The SCSI-1 standard (approx 1985) is rapidly becoming obsolete. The
|
||||
The SCSI-1 standard (approximately 1985) is rapidly becoming obsolete. The
|
||||
current standard is SCSI-2 (see <link
|
||||
linkend="scsi-further-reading">Further reading</link>), with SCSI-3
|
||||
on the drawing boards.</para>
|
||||
|
|
@ -3711,7 +3712,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
<para>In SCSI-3 even faster bus types are introduced, along with a
|
||||
serial SCSI busses that reduces the cabling overhead and allows a
|
||||
higher maximum bus length. You might see names like SSA and
|
||||
Fiberchannel in this context. None of the serial buses are currently
|
||||
fibre channel in this context. None of the serial buses are currently
|
||||
in widespread use (especially not in the typical FreeBSD environment).
|
||||
For this reason the serial bus types are not discussed any
|
||||
further.</para>
|
||||
|
|
@ -3981,7 +3982,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
|
||||
<para>On modern devices, sometimes integrated terminators are used.
|
||||
These things are special purpose integrated circuits that can be
|
||||
dis/en-abled with a control pin. It is not necessary to
|
||||
enabled or disabled with a control pin. It is not necessary to
|
||||
physically remove them from a device. You may find them on newer
|
||||
host adapters, sometimes they are software configurable, using
|
||||
some sort of setup tool. Some will even auto-detect the cables
|
||||
|
|
@ -4052,7 +4053,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
<para>A narrow SCSI device can not communicate with a SCSI device
|
||||
with a target ID larger than 7. This means it is generally not
|
||||
a good idea to move your SCSI host adapter's target ID to
|
||||
something higher than 7 (or your CD-ROM will stop
|
||||
something higher than 7 (or your CDROM will stop
|
||||
working).</para>
|
||||
</note>
|
||||
|
||||
|
|
@ -4210,7 +4211,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)</screen>
|
|||
|
||||
<para>On top of the card drivers there are a number of more generic
|
||||
drivers for a class of devices. More specific: a driver for tape
|
||||
devices (abbreviation: st), magnetic disks (sd), CD-ROMs (cd) etc.
|
||||
devices (abbreviation: st), magnetic disks (sd), CDROMs (cd) etc.
|
||||
In case you are wondering where you can find this stuff, it all
|
||||
lives in <filename>/sys/scsi</filename>. See the man pages in
|
||||
section 4 for more details.</para>
|
||||
|
|
@ -4288,7 +4289,7 @@ disk sd1 at scbus0 target 1 [implicit LUN 0 if omitted]
|
|||
disk sd2 at scbus1 target 3 [SCSI disk on the uha0]
|
||||
disk sd3 at scbus2 target 4 [SCSI disk on the ncr0]
|
||||
tape st1 at scbus0 target 6 [SCSI tape at target 6]
|
||||
device cd0 at scbus? [the first ever CD-ROM found, no wiring]</programlisting>
|
||||
device cd0 at scbus? [the first ever CDROM found, no wiring]</programlisting>
|
||||
|
||||
<para>The example above tells the kernel to look for a ahc (Adaptec
|
||||
274x) controller, then for an NCR/Symbios board, and so on. The
|
||||
|
|
@ -4349,7 +4350,7 @@ controller scbus0
|
|||
device sd0 [support for 4 SCSI harddisks, sd0 up sd3]
|
||||
device st0 [support for 2 SCSI tapes]
|
||||
|
||||
[for the CD-ROM]
|
||||
[for the CDROM]
|
||||
device cd0 #Only need one of these, the code dynamically grows</programlisting>
|
||||
|
||||
<para>Both examples support SCSI disks. If during boot more devices
|
||||
|
|
@ -4361,7 +4362,7 @@ device cd0 #Only need one of these, the code dynamically grows</pro
|
|||
|
||||
<para>Use <command>man 4 scsi</command> to check for the latest info
|
||||
on the SCSI subsystem. For more detailed info on host adapter
|
||||
drivers use eg <command>man 4 ahc</command> for info on the
|
||||
drivers use e.g., <command>man 4 ahc</command> for info on the
|
||||
Adaptec 294x driver.</para>
|
||||
</sect4>
|
||||
|
||||
|
|
@ -4371,7 +4372,7 @@ device cd0 #Only need one of these, the code dynamically grows</pro
|
|||
<para>Experience has shown that some devices are slow to respond to
|
||||
INQUIRY commands after a SCSI bus reset (which happens at boot
|
||||
time). An INQUIRY command is sent by the kernel on boot to see
|
||||
what kind of device (disk, tape, CD-ROM etc) is connected to a
|
||||
what kind of device (disk, tape, CDROM etc.) is connected to a
|
||||
specific target ID. This process is called device probing by the
|
||||
way.</para>
|
||||
|
||||
|
|
@ -4384,7 +4385,7 @@ device cd0 #Only need one of these, the code dynamically grows</pro
|
|||
options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device</programlisting>
|
||||
|
||||
<para>This line sets the delay time to 15 seconds. On my own system
|
||||
I had to use 3 seconds minimum to get my trusty old CD-ROM drive
|
||||
I had to use 3 seconds minimum to get my trusty old CDROM drive
|
||||
to be recognized. Start with a high value (say 30 seconds or so)
|
||||
when you have problems with device recognition. If this helps,
|
||||
tune it back until it just stays working.</para>
|
||||
|
|
@ -4426,7 +4427,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
|
|||
|
||||
<para>This scheme works fine, but keep in mind that it of course
|
||||
only works for devices that are known to be weird. If you are the
|
||||
first to connect your bogus Mumbletech SCSI CD-ROM you might be
|
||||
first to connect your bogus Mumbletech SCSI CDROM you might be
|
||||
the one that has to define which workaround is needed.</para>
|
||||
|
||||
<para>After you got your Mumbletech working, please send the
|
||||
|
|
@ -4473,14 +4474,14 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
|
|||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>Tagged command queueing</title>
|
||||
<title>Tagged command queuing</title>
|
||||
|
||||
<para>Modern SCSI devices, particularly magnetic disks,
|
||||
support what is called tagged command queuing (TCQ).</para>
|
||||
|
||||
<para>In a nutshell, TCQ allows the device to have multiple I/O
|
||||
requests outstanding at the same time. Because the device is
|
||||
intelligent, it can optimise its operations (like head
|
||||
intelligent, it can optimize its operations (like head
|
||||
positioning) based on its own request queue. On SCSI devices
|
||||
like RAID (Redundant Array of Independent Disks) arrays the TCQ
|
||||
function is indispensable to take advantage of the device's
|
||||
|
|
@ -4513,7 +4514,7 @@ Mar 29 21:16:37 yedi /kernel: st1: Archive Viper 150 is a known rogue </screen>
|
|||
different transfer speeds on the host bus (ISA or AT in this
|
||||
case). The controller is settable to different rates because not
|
||||
all motherboards can handle the higher speeds. Problems like
|
||||
hangups, bad data etc might be the result of using a higher data
|
||||
hang-ups, bad data etc might be the result of using a higher data
|
||||
transfer rate then your motherboard can stomach.</para>
|
||||
|
||||
<para>The solution is of course obvious: switch to a lower data
|
||||
|
|
@ -4575,7 +4576,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
|
||||
<listitem>
|
||||
<para>Disable tagged command queuing to make things as simple as
|
||||
possible (for a NCR hostadapter based system see man
|
||||
possible (for a NCR host adapter based system see man
|
||||
ncrcontrol)</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -4782,7 +4783,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
megabytes/sec you can get out of the drive.</para>
|
||||
|
||||
<para>(If you are a speed maniac and want a 10,000RPM drive for your
|
||||
cute little peecee, be my guest; however, those drives become
|
||||
cute little PC, be my guest; however, those drives become
|
||||
extremely hot. Don't even think about it if you don't have a fan
|
||||
blowing air <emphasis>directly at</emphasis> the drive or a
|
||||
properly ventilated disk enclosure.)</para>
|
||||
|
|
@ -4827,7 +4828,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<para>Most SCSI drives sold today are of 3.5" form factor. They
|
||||
come in two different heights; 1.6" (<quote>half-height</quote>) or
|
||||
1" (<quote>low-profile</quote>). The half-height drive is the same
|
||||
height as a CD-ROM drive. However, don't forget the spacing rule
|
||||
height as a CDROM drive. However, don't forget the spacing rule
|
||||
mentioned in the previous section. If you have three standard
|
||||
3.5" drive bays, you will not be able to put three half-height
|
||||
drives in there (without frying them, that is).</para>
|
||||
|
|
@ -4908,7 +4909,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
|
||||
<para>The &man.st.4; driver provides support for 8mm (Exabyte), 4mm
|
||||
(DAT: Digital Audio Tape), QIC (Quarter-Inch Cartridge), DLT
|
||||
(Digital Linear Tape), QIC Minicartridge and 9-track (remember the
|
||||
(Digital Linear Tape), QIC Mini cartridge and 9-track (remember the
|
||||
big reels that you see spinning in Hollywood computer rooms) tape
|
||||
drives. See the &man.st.4; manual page for a detailed
|
||||
description.</para>
|
||||
|
|
@ -4955,7 +4956,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<sect4>
|
||||
<title>QIC (Quarter-Inch Cartridge)</title>
|
||||
|
||||
<para><link linkend="hw-storage-anaconda">Archive Ananconda
|
||||
<para><link linkend="hw-storage-anaconda">Archive Anaconda
|
||||
2750</link></para>
|
||||
|
||||
<para><link linkend="hw-storage-viper60">Archive Viper
|
||||
|
|
@ -5176,7 +5177,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<para>This drives quirks are known and pre-compiled into the scsi
|
||||
tape device driver (&man.st.4;).</para>
|
||||
|
||||
<para>Under FreeBSD 2.2-current, use <command>mt blocksize
|
||||
<para>Under FreeBSD 2.2-CURRENT, use <command>mt blocksize
|
||||
512</command> to set the blocksize. (The particular drive had
|
||||
firmware revision 21247 -005. Other firmware revisions may behave
|
||||
differently) Previous versions of FreeBSD did not have this
|
||||
|
|
@ -5187,8 +5188,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<para>Reported by: Pedro A M Vazquez
|
||||
<email>vazquez@IQM.Unicamp.BR</email></para>
|
||||
|
||||
<para>Mike Smith
|
||||
<email>msmith@atrad.adelaide.edu.au</email></para>
|
||||
<para>&a.msmith;</para>
|
||||
</sect4>
|
||||
|
||||
<sect4 id="hw-storage-viper2525">
|
||||
|
|
@ -5219,7 +5219,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<para>The boot message identifier for this drive is <literal>Conner
|
||||
tape</literal>.</para>
|
||||
|
||||
<para>This is a floppy controller, minicartridge tape drive.</para>
|
||||
<para>This is a floppy controller, mini cartridge tape drive.</para>
|
||||
|
||||
<para>Native capacity is XXXX</para>
|
||||
|
||||
|
|
@ -5238,7 +5238,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
CTMS 3200 7.00</literal> <literal>type 1 removable SCSI
|
||||
2</literal>.</para>
|
||||
|
||||
<para>This is a minicartridge tape drive.</para>
|
||||
<para>This is a mini cartridge tape drive.</para>
|
||||
|
||||
<para>Native capacity is XXXX</para>
|
||||
|
||||
|
|
@ -5283,12 +5283,12 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
<para>This is a mini-cartridge tape drive.</para>
|
||||
|
||||
<para>Native capacity is 1GB when using MC3000XL
|
||||
minicartridges.</para>
|
||||
mini cartridges.</para>
|
||||
|
||||
<para>Data transfer rate is XXX</para>
|
||||
|
||||
<para>This drive can read and write DC2300 (550MB), DC2750 (750MB),
|
||||
MC3000 (750MB), and MC3000XL (1GB) minicartridges.</para>
|
||||
MC3000 (750MB), and MC3000XL (1GB) mini cartridges.</para>
|
||||
|
||||
<para>WARNING: This drive does not meet the SCSI-2 specifications.
|
||||
The drive locks up completely in response to a SCSI MODE_SELECT
|
||||
|
|
@ -5297,8 +5297,8 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
|
||||
<screen>&prompt.root; <userinput>mt -f /dev/st0ctl.0 blocksize 1024</userinput></screen>
|
||||
|
||||
<para>Before using a minicartridge for the first time, the
|
||||
minicartridge must be formated. FreeBSD 2.1.0-RELEASE and
|
||||
<para>Before using a mini cartridge for the first time, the
|
||||
mini cartridge must be formated. FreeBSD 2.1.0-RELEASE and
|
||||
earlier:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>/sbin/scsi -f /dev/rst0.ctl -s 600 -c "4 0 0 0 0 0"</userinput></screen>
|
||||
|
|
@ -5340,8 +5340,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed</programli
|
|||
|
||||
<para>Production of this drive has been discontinued.</para>
|
||||
|
||||
<para>Reported by: Mike Smith
|
||||
<email>msmith@atrad.adelaide.edu.au</email></para>
|
||||
<para>Reported by: &a.msmith;</para>
|
||||
</sect4>
|
||||
|
||||
<sect4 id="hw-storage-exb8500">
|
||||
|
|
@ -5580,7 +5579,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
|
|||
|
||||
<para>Data transfer rate is 160kB/s.</para>
|
||||
|
||||
<para>Reported by: mark thompson
|
||||
<para>Reported by: Mark Thompson
|
||||
<email>mark.a.thompson@pobox.com</email></para>
|
||||
</sect4>
|
||||
|
||||
|
|
@ -5674,10 +5673,10 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
|
|||
|
||||
<para>In order to get this drive to stream, set the blocksize to 512
|
||||
bytes (<command>mt blocksize 512</command>) reported by Kenneth
|
||||
Merry ken@ulc199.residence.gatech.edu</para>
|
||||
Merry <email>ken@ulc199.residence.gatech.edu</email>.</para>
|
||||
|
||||
<para><literal>SONY SDT-5000 327M</literal> information reported by
|
||||
Charles Henrich henrich@msu.edu</para>
|
||||
Charles Henrich <email>henrich@msu.edu</email>.</para>
|
||||
|
||||
<para>Reported by: &a.jmz;</para>
|
||||
</sect4>
|
||||
|
|
@ -5703,8 +5702,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
|
|||
<para>IBM and Emerald units will not work. Replacing the firmware
|
||||
EPROM of these units will solve the problem.</para>
|
||||
|
||||
<para>Reported by: Michael Smith
|
||||
<email>msmith@atrad.adelaide.edu.au</email></para>
|
||||
<para>Reported by: &a.msmith;</para>
|
||||
</sect4>
|
||||
|
||||
<sect4 id="hw-storage-tandberg3620">
|
||||
|
|
@ -5747,7 +5745,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
|
|||
|
||||
<para>This drives quirks are known and pre-compiled into the scsi
|
||||
tape device driver (&man.st.4;) beginning with FreeBSD
|
||||
2.2-current. For previous versions of FreeBSD, use
|
||||
2.2-CURRENT. For previous versions of FreeBSD, use
|
||||
<command>mt</command> to read one block from the tape, rewind the
|
||||
tape, and then execute the backup program (<command>mt fsr 1; mt
|
||||
rewind; dump ...</command>)</para>
|
||||
|
|
@ -5820,7 +5818,7 @@ scsi -f $2 -s 100 -c "1b 0 0 $cdb3 $cdb4 $cdb5"</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>CD-ROM drives</title>
|
||||
<title>CDROM drives</title>
|
||||
|
||||
<para><emphasis>Contributed by &a.obrien;. 23 November
|
||||
1997.</emphasis></para>
|
||||
|
|
|
|||
Loading…
Reference in a new issue