Replace all contractions with their expanded form.
Approved by: nik
This commit is contained in:
parent
b15029d064
commit
49731ee7b9
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10957
1 changed files with 8 additions and 8 deletions
|
@ -60,11 +60,11 @@
|
|||
<para>If you want maximum performance and easy setup, the SCSI
|
||||
interface is the best choice. This will probably require adding a
|
||||
SCSI host adapter, since most PC's (except for high-performance
|
||||
servers) don't have built-in SCSI support. Each SCSI host adapter
|
||||
servers) do not have built-in SCSI support. Each SCSI host adapter
|
||||
can support either 7 or 15 SCSI devices, depending on the
|
||||
model.</para>
|
||||
|
||||
<para>Each SCSI device has it's own controller, and these
|
||||
<para>Each SCSI device has its own controller, and these
|
||||
controllers are fairly intelligent and well standardized, (the
|
||||
second `S' in SCSI is for Standard) so from the operating system's
|
||||
point of view, all SCSI disk drives look about the same, as do all
|
||||
|
@ -73,7 +73,7 @@
|
|||
a generic driver for each type of device, i.e. a SCSI disk driver,
|
||||
SCSI tape driver, and so on. There are some SCSI devices that can
|
||||
be better utilized with specialized drivers (e.g. DAT tape drives),
|
||||
but they tend to work OK with the generic driver, too. It's just
|
||||
but they tend to work OK with the generic driver, too. It is just
|
||||
that the generic drivers may not support some of the special
|
||||
features.</para>
|
||||
|
||||
|
@ -81,7 +81,7 @@
|
|||
device file in the <filename>/dev</filename> directory represents
|
||||
the ZIP drive. This can be determined by looking at the boot
|
||||
messages while FreeBSD is booting (or in
|
||||
<filename>/var/log/messages</filename> after booting), where you'll
|
||||
<filename>/var/log/messages</filename> after booting), where you will
|
||||
see a line something like this:</para>
|
||||
|
||||
<programlisting>da1: <IOMEGA ZIP 100 D.13> Removable Direct Access SCSI-2 Device</programlisting>
|
||||
|
@ -167,7 +167,7 @@
|
|||
uses IRQ 5 and address 378. Only the IRQ is required in the config
|
||||
file.</para>
|
||||
|
||||
<para>If you're root hard disk is a SCSI disk, you might run into a
|
||||
<para>If your root hard disk is a SCSI disk, you might run into a
|
||||
problem with probing order, which will cause the system to attempt
|
||||
to use the ZIP drive as the root device. This will cause a boot
|
||||
failure, unless you happen to have a FreeBSD root file-system on
|
||||
|
@ -195,7 +195,7 @@
|
|||
|
||||
<programlisting>controller scbus0 at aha0</programlisting></para>
|
||||
|
||||
<para>Lastly, as long as you're editing the kernel config, you
|
||||
<para>Lastly, as long as you are editing the kernel config, you
|
||||
can take the opportunity to remove all the unnecessary drivers. This
|
||||
should be done with a great deal of caution, and only if you feel
|
||||
confident about making kernel modifications. Removing unnecessary
|
||||
|
@ -209,7 +209,7 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Now it's time to compile the kernel:</para>
|
||||
<para>Now it is time to compile the kernel:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>/usr/sbin/config MYKERNEL</userinput>
|
||||
&prompt.root; <userinput>cd ../../compile/MYKERNEL</userinput>
|
||||
|
@ -217,7 +217,7 @@
|
|||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<para>After the kernel is rebuilt, you'll need to reboot. Make sure the
|
||||
<para>After the kernel is rebuilt, you will need to reboot. Make sure the
|
||||
ZIP drive is connected to the parallel port before the boot begins. You
|
||||
should see the ZIP drive show up in the boot messages as device vpo0 or
|
||||
vpo1, depending on which parallel port the drive is attached to. It
|
||||
|
|
Loading…
Reference in a new issue