|
Lines 140-176
Link Here
|
| 140 |
<sect1 xml:id="bsdinstall-hardware"> |
140 |
<sect1 xml:id="bsdinstall-hardware"> |
| 141 |
<title>Minimum Hardware Requirements</title> |
141 |
<title>Minimum Hardware Requirements</title> |
| 142 |
|
142 |
|
| 143 |
<para>The hardware requirements to install &os; vary by the |
143 |
<para>The hardware requirements to install &os; vary by |
| 144 |
hardware architecture. Hardware architectures |
144 |
architecture. Hardware architectures |
| 145 |
and devices supported by a &os; release are listed on the |
145 |
and devices supported by a &os; release are listed on the |
| 146 |
Release Information page of the &os; web site (<link |
146 |
Release Information page of the &os; web site (<link |
| 147 |
xlink:href="&url.base;/releases/index.html">http://www.FreeBSD.org/releases/index.html</link>).</para> |
147 |
xlink:href="&url.base;/releases/index.html">http://www.FreeBSD.org/releases/index.html</link>). |
|
|
148 |
The &os; download page also has recommendations for choosing the |
| 149 |
correct image for different architectures (<link |
| 150 |
xlink:href="&url.base;/where.html">https://www.FreeBSD.org/where.html</link>).</para> |
| 148 |
|
151 |
|
| 149 |
<para>A &os; installation will require a minimum 64 MB of |
152 |
<para>A &os; installation requires a minimum of 64 MB of |
| 150 |
<acronym>RAM</acronym> and 1.5 GB of free hard drive space |
153 |
<acronym>RAM</acronym> and 1.5 GB of free hard drive space. |
| 151 |
for the most minimal installation. However, that is a |
154 |
However, such small amounts of memory and disk space are really |
| 152 |
<emphasis>minimal</emphasis> install, leaving almost no |
155 |
only suitable for custom applications like embedded appliances. |
| 153 |
free space. RAM requirements depend on usage. Specialized |
156 |
General-purpose desktop |
| 154 |
FreeBSD systems can run in as little as 128MB RAM while desktop |
157 |
systems need more resources. 2-4 GB RAM and |
| 155 |
systems should have at least 4 GB |
158 |
at least 8 GB hard drive space is a good starting point.</para> |
| 156 |
of <acronym>RAM</acronym>.</para> |
|
|
| 157 |
|
159 |
|
| 158 |
<para>The processor requirements for each architecture can be |
160 |
<para>These are the processor requirements for each architecture:</para> |
| 159 |
summarized as follows:</para> |
|
|
| 160 |
|
161 |
|
| 161 |
<variablelist> |
162 |
<variablelist> |
| 162 |
<varlistentry> |
163 |
<varlistentry> |
| 163 |
<term>&arch.amd64;</term> |
164 |
<term>&arch.amd64;</term> |
| 164 |
<listitem> |
165 |
<listitem> |
| 165 |
<para>This is the most common type of processor desktop and |
166 |
<para>This is the most common desktop and laptop processor type, |
| 166 |
laptop computers will have. Other vendors may call this |
167 |
used in most modern systems. &intel; calls it <acronym>Intel64</acronym>. |
| 167 |
architecture <acronym>x86-64</acronym>.</para> |
168 |
Other manufacturers sometimes call it <acronym>x86-64</acronym>.</para> |
| 168 |
|
169 |
|
| 169 |
<para>There are two primary vendors of &arch.amd64; |
|
|
| 170 |
processors: &intel; (which produces |
| 171 |
<acronym>Intel64</acronym> class processors) and AMD |
| 172 |
(which produces <acronym>AMD64</acronym>).</para> |
| 173 |
|
| 174 |
<para>Examples of &arch.amd64; compatible processsors |
170 |
<para>Examples of &arch.amd64; compatible processsors |
| 175 |
include: &amd.athlon;64, &amd.opteron;, |
171 |
include: &amd.athlon;64, &amd.opteron;, |
| 176 |
multi-core &intel; &xeon;, and |
172 |
multi-core &intel; &xeon;, and |
|
Lines 181-187
Link Here
|
| 181 |
<varlistentry> |
177 |
<varlistentry> |
| 182 |
<term>&arch.i386;</term> |
178 |
<term>&arch.i386;</term> |
| 183 |
<listitem> |
179 |
<listitem> |
| 184 |
<para>This architecture is the 32-bit x86 |
180 |
<para>Older desktops and laptops often use this 32-bit, x86 |
| 185 |
architecture.</para> |
181 |
architecture.</para> |
| 186 |
|
182 |
|
| 187 |
<para>Almost all i386-compatible processors with a floating |
183 |
<para>Almost all i386-compatible processors with a floating |
|
Lines 190-201
Link Here
|
| 190 |
|
186 |
|
| 191 |
<para>&os; will take advantage of Physical Address |
187 |
<para>&os; will take advantage of Physical Address |
| 192 |
Extensions (<acronym>PAE</acronym>) support on |
188 |
Extensions (<acronym>PAE</acronym>) support on |
| 193 |
<acronym>CPU</acronym>s that support this feature. A |
189 |
<acronym>CPU</acronym>s with this feature. A |
| 194 |
kernel with the <acronym>PAE</acronym> feature enabled |
190 |
kernel with the <acronym>PAE</acronym> feature enabled |
| 195 |
will detect memory above 4 GB and allow it to be used |
191 |
will detect memory above 4 GB and allow it to be used |
| 196 |
by the system. This feature places constraints on the |
192 |
by the system. However, using <acronym>PAE</acronym> places constraints on |
| 197 |
device drivers and other features of &os; which may be |
193 |
device drivers and other features of |
| 198 |
used; refer to &man.pae.4; for details.</para> |
194 |
&os;. Refer to &man.pae.4; for details.</para> |
| 199 |
</listitem> |
195 |
</listitem> |
| 200 |
</varlistentry> |
196 |
</varlistentry> |
| 201 |
|
197 |
|
|
Lines 1673-1680
Link Here
|
| 1673 |
<para>If one or more disks are missing from the list, or if |
1669 |
<para>If one or more disks are missing from the list, or if |
| 1674 |
disks were attached after the installer was started, select |
1670 |
disks were attached after the installer was started, select |
| 1675 |
<guibutton>- Rescan Devices</guibutton> to repopulate the list |
1671 |
<guibutton>- Rescan Devices</guibutton> to repopulate the list |
| 1676 |
of available disks. To ensure that the correct disks are |
1672 |
of available disks. |
| 1677 |
selected, so as not to accidently destroy the wrong disks, the |
1673 |
To avoid accidentally erasing the wrong disk, the |
| 1678 |
<guibutton>- Disk Info</guibutton> menu can be used to inspect |
1674 |
<guibutton>- Disk Info</guibutton> menu can be used to inspect |
| 1679 |
each disk, including its partition table and various other |
1675 |
each disk, including its partition table and various other |
| 1680 |
information such as the device model number and serial number, |
1676 |
information such as the device model number and serial number, |
|
Lines 1737-1743
Link Here
|
| 1737 |
<title>Shell Mode Partitioning</title> |
1733 |
<title>Shell Mode Partitioning</title> |
| 1738 |
|
1734 |
|
| 1739 |
<para>When creating advanced installations, the |
1735 |
<para>When creating advanced installations, the |
| 1740 |
<application>bsdinstall</application> paritioning menus may |
1736 |
<application>bsdinstall</application> partitioning menus may |
| 1741 |
not provide the level of flexibility required. Advanced users |
1737 |
not provide the level of flexibility required. Advanced users |
| 1742 |
can select the <guibutton>Shell</guibutton> option from the |
1738 |
can select the <guibutton>Shell</guibutton> option from the |
| 1743 |
partitioning menu in order to manually partition the drives, |
1739 |
partitioning menu in order to manually partition the drives, |