(itstool) path: sect1/para

The next menu is used to determine the method for allocating disk space.
Context English Spanish State
Next, <application>bsdinstall</application> will prompt to select optional components to install.
_ external ref='bsdinstall/bsdinstall-config-components' md5='__failed__'
Deciding which components to install will depend largely on the intended use of the system and the amount of disk space available. The FreeBSD kernel and userland, collectively known as the <firstterm>base system</firstterm>, are always installed. Depending on the architecture, some of these components may not appear:
<literal>base-dbg</literal> - Base tools like <application>cat</application>, <application>ls</application> among many others with debug symbols activated.
<literal>kernel-dbg</literal> - Kernel and modules with debug symbols activated.
<literal>lib32-dbg</literal> - Compatibility libraries for running 32-bit applications on a 64-bit version of FreeBSD with debug symbols activated.
<literal>lib32</literal> - Compatibility libraries for running 32-bit applications on a 64-bit version of FreeBSD.
<literal>ports</literal> - The FreeBSD Ports Collection is a collection of files which automates the downloading, compiling and installation of third-party software packages. <xref linkend="ports"/> discusses how to use the Ports Collection.
The installation program does not check for adequate disk space. Select this option only if sufficient hard disk space is available. The FreeBSD Ports Collection takes up about 500 MB of disk space.
<literal>src</literal> - The complete FreeBSD source code for both the kernel and the userland. Although not required for the majority of applications, it may be required to build device drivers, kernel modules, or some applications from the Ports Collection. It is also used for developing FreeBSD itself. The full source tree requires 1 GB of disk space and recompiling the entire FreeBSD system requires an additional 5 GB of space.
<literal>tests</literal> - FreeBSD Test Suite.
Installing from the Network
The menu shown in <xref linkend="bsdinstall-netinstall-notify"/> only appears when installing from a <filename>-bootonly.iso</filename> or <filename>-mini-memstick.img</filename> as this installation media does not hold copies of the installation files. Since the installation files must be retrieved over a network connection, this menu indicates that the network interface must be configured first. If this menu is shown in any step of the process remember to follow the instructions in <xref linkend="bsdinstall-config-network-dev"/>.
_ external ref='bsdinstall/bsdinstall-netinstall-files' md5='__failed__'
Allocating Disk Space
The next menu is used to determine the method for allocating disk space.
Partitioning Choices
_ external ref='bsdinstall/bsdinstall-zfs-partmenu' md5='__failed__'
<application>bsdinstall</application> gives the user four methods for allocating disk space:
<literal>Auto (UFS)</literal> partitioning automatically sets up the disk partitions using the <literal>UFS</literal> file system.
<literal>Manual</literal> partitioning allows advanced users to create customized partitions from menu options.
<literal>Shell</literal> opens a shell prompt where advanced users can create customized partitions using command-line utilities like <citerefentry><refentrytitle>gpart</refentrytitle><manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>fdisk</refentrytitle><manvolnum>8</manvolnum></citerefentry>, and <citerefentry><refentrytitle>bsdlabel</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
<literal>Auto (ZFS)</literal> partitioning creates a root-on-ZFS system with optional GELI encryption support for <firstterm>boot environments</firstterm>.
This section describes what to consider when laying out the disk partitions. It then demonstrates how to use the different partitioning methods.
Designing the Partition Layout
<primary>partition layout</primary>
When laying out file systems, remember that hard drives transfer data faster from the outer tracks to the inner. Thus, smaller and heavier-accessed file systems should be closer to the outside of the drive, while larger partitions like <filename>/usr</filename> should be placed toward the inner parts of the disk. It is a good idea to create partitions in an order similar to: <filename>/</filename>, swap, <filename>/var</filename>, and <filename>/usr</filename>.
The size of the <filename>/var</filename> partition reflects the intended machine's usage. This partition is used to hold mailboxes, log files, and printer spools. Mailboxes and log files can grow to unexpected sizes depending on the number of users and how long log files are kept. On average, most users rarely need more than about a gigabyte of free disk space in <filename>/var</filename>.


User avatar None

New source string

FreeBSD Doc / books_handbookSpanish

New source string a year ago
Browse all component changes


English Spanish
No related strings found in the glossary.

Source information

Source string comment

(itstool) path: sect1/para

Source string location
String age
a year ago
Source string age
a year ago
Translation file
books/es_ES/handbook.po, string 507