1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
5 | %general-entities;
|
---|
6 | ]>
|
---|
7 |
|
---|
8 | <sect1 id="space-creatingpartition">
|
---|
9 | <?dbhtml filename="creatingpartition.html"?>
|
---|
10 |
|
---|
11 | <title>Creating a New Partition</title>
|
---|
12 |
|
---|
13 | <para>Like most other operating systems, LFS is usually installed on a
|
---|
14 | dedicated partition. The recommended approach to building an LFS system
|
---|
15 | is to use an available empty partition or, if you have enough unpartitioned
|
---|
16 | space, to create one.</para>
|
---|
17 |
|
---|
18 | <!--
|
---|
19 |
|
---|
20 | <para>It is possible to install an LFS system (in fact even multiple LFS
|
---|
21 | systems) on a partition already occupied by another
|
---|
22 | operating system and the different systems will co-exist peacefully. The
|
---|
23 | document <ulink url="&hints-root;lfs_next_to_existing_systems.txt"/>
|
---|
24 | contains notes on how to implement this. This document was last updated
|
---|
25 | in 2004. It has not been updated since and it has not been tested with
|
---|
26 | recent versions of this LFS book. The document is more than likely not
|
---|
27 | usable as-is and you will need to account for changes made to the LFS
|
---|
28 | procedures since it was written. This is only recommended for expert LFS
|
---|
29 | users.</para>
|
---|
30 |
|
---|
31 | -->
|
---|
32 |
|
---|
33 | <para>A minimal system requires a partition of around 2.8 gigabytes (GB).
|
---|
34 | This is enough to store all the source tarballs and compile the packages.
|
---|
35 | However, if the LFS system is intended to be the primary Linux system,
|
---|
36 | additional software will probably be installed which will require additional
|
---|
37 | space. A 10GB partition is a reasonable size to provide for growth. The LFS
|
---|
38 | system itself will not take up this much room. A large portion of this
|
---|
39 | requirement is to provide sufficient free temporary storage. Compiling
|
---|
40 | packages can require a lot of disk space which will be reclaimed after the
|
---|
41 | package is installed.</para>
|
---|
42 |
|
---|
43 | <para>Because there is not always enough Random Access Memory (RAM) available
|
---|
44 | for compilation processes, it is a good idea to use a small disk partition as
|
---|
45 | <systemitem class="filesystem">swap</systemitem> space. This is used by the
|
---|
46 | kernel to store seldom-used data and leave more memory available for active
|
---|
47 | processes. The <systemitem class="filesystem">swap</systemitem> partition for
|
---|
48 | an LFS system can be the same as the one used by the host system, in which
|
---|
49 | case it is not necessary to create another one.</para>
|
---|
50 |
|
---|
51 | <para>Start a disk partitioning program such as <command>cfdisk</command>
|
---|
52 | or <command>fdisk</command> with a command line option naming the hard
|
---|
53 | disk on which the new partition will be created—for example
|
---|
54 | <filename class="devicefile">/dev/hda</filename> for the primary Integrated
|
---|
55 | Drive Electronics (IDE) disk. Create a Linux native partition and a
|
---|
56 | <systemitem class="filesystem">swap</systemitem> partition, if needed. Please
|
---|
57 | refer to <filename>cfdisk(8)</filename> or <filename>fdisk(8)</filename> if
|
---|
58 | you do not yet know how to use the programs.</para>
|
---|
59 |
|
---|
60 | <note><para>For experienced users, other partitioning schemes are possible.
|
---|
61 | The new LFS system can be on a software <ulink
|
---|
62 | url="&blfs-root;/view/svn/postlfs/raid.html">RAID</ulink> array or an <ulink
|
---|
63 | url="&blfs-root;/view/svn/postlfs/aboutlvm.html">LVM</ulink> logical volume.
|
---|
64 | However, some of these options require an <ulink
|
---|
65 | url="&blfs-root;/view/svn/postlfs/initramfs.html">initramfs</ulink>, which is
|
---|
66 | an advanced topic. These partitioning methodologies are not recommended for
|
---|
67 | first time LFS users.</para></note>
|
---|
68 |
|
---|
69 | <para>Remember the designation of the new partition (e.g., <filename
|
---|
70 | class="devicefile">hda5</filename>). This book will refer to this as
|
---|
71 | the LFS partition. Also remember the designation of the <systemitem
|
---|
72 | class="filesystem">swap</systemitem> partition. These names will be
|
---|
73 | needed later for the <filename>/etc/fstab</filename> file.</para>
|
---|
74 |
|
---|
75 | <sect2>
|
---|
76 | <title>Other Partition Issues</title>
|
---|
77 |
|
---|
78 | <para>Requests for advice on system partitioning are often posted on the LFS mailing
|
---|
79 | lists. This is a highly subjective topic. The default for most distributions
|
---|
80 | is to use the entire drive with the exception of one small swap partition. This
|
---|
81 | is not optimal for LFS for several reasons. It reduces flexibility, makes
|
---|
82 | sharing of data across multiple distributions or LFS builds more difficult, makes
|
---|
83 | backups more time consuming, and can waste disk space through inefficient
|
---|
84 | allocation of file system structures.</para>
|
---|
85 |
|
---|
86 | <sect3>
|
---|
87 | <title>The Root Partition</title>
|
---|
88 |
|
---|
89 | <para>A root LFS partition (not to be confused with the
|
---|
90 | <filename class="directory">/root</filename> directory) of
|
---|
91 | ten gigabytes is a good compromise for most systems. It provides enough
|
---|
92 | space to build LFS and most of BLFS, but is small enough so that multiple
|
---|
93 | partitions can be easily created for experimentation.</para> </sect3>
|
---|
94 |
|
---|
95 | <sect3>
|
---|
96 | <title>The Swap Partition</title>
|
---|
97 |
|
---|
98 | <para>Most distributions automatically create a swap partition. Generally
|
---|
99 | the recommended size of the swap partition is about twice the amount of
|
---|
100 | physical RAM, however this is rarely needed. If disk space is limited,
|
---|
101 | hold the swap partition to two gigabytes and monitor the amount of disk
|
---|
102 | swapping.</para>
|
---|
103 |
|
---|
104 | <para>Swapping is never good. Generally you can tell if a system is
|
---|
105 | swapping by just listening to disk activity and observing how the system
|
---|
106 | reacts to commands. The first reaction to swapping should be to check for
|
---|
107 | an unreasonable command such as trying to edit a five gigabyte file. If
|
---|
108 | swapping becomes a normal occurance, the best solution is to purchase more
|
---|
109 | RAM for your system.</para> </sect3>
|
---|
110 |
|
---|
111 | <sect3>
|
---|
112 | <title>Convenience Partitions</title>
|
---|
113 |
|
---|
114 | <para>There are several other partitions that are not required, but should
|
---|
115 | be considered when designing a disk layout. The following list
|
---|
116 | is not comprehensive, but is meant as a guide.</para>
|
---|
117 |
|
---|
118 | <itemizedlist>
|
---|
119 |
|
---|
120 | <listitem><para>/boot – Highly recommended. Use this partition to
|
---|
121 | store kernels and other booting information. To minimize potential boot
|
---|
122 | problems with larger disks, make this the first physical partition on
|
---|
123 | your first disk drive. A partition size of 100 megabytes is quite
|
---|
124 | adequate.</para></listitem>
|
---|
125 |
|
---|
126 | <listitem><para>/home – Highly recommended. Share your home
|
---|
127 | directory and user customization across multiple distributions or LFS
|
---|
128 | builds. The size is generally fairly large and depends on available disk
|
---|
129 | space.</para></listitem>
|
---|
130 |
|
---|
131 | <listitem><para>/usr – A separate /usr partition is generally used
|
---|
132 | if providing a server for a thin client or diskless workstation. It is
|
---|
133 | normally not needed for LFS. A size of five gigabytes will handle most
|
---|
134 | installations.</para></listitem>
|
---|
135 |
|
---|
136 | <listitem><para>/opt – This directory is most useful for
|
---|
137 | BLFS where multiple installations of large packages like Gnome or KDE can
|
---|
138 | be installed without embedding the files in the /usr hierarchy. If
|
---|
139 | used, five to ten gigabytes is generally adequate.</para>
|
---|
140 | </listitem>
|
---|
141 |
|
---|
142 | <listitem><para>/tmp – A separate /tmp directory is rare, but
|
---|
143 | useful if configuring a thin client. This partition, if used, will
|
---|
144 | usually not need to exceed a couple of gigabytes.</para></listitem>
|
---|
145 |
|
---|
146 | <listitem><para>/usr/src – This partition is very
|
---|
147 | useful for providing a location to store BLFS source files and
|
---|
148 | share them across LFS builds. It can also be used as a location
|
---|
149 | for building BLFS packages. A reasonably large partition of 30-50
|
---|
150 | gigabytes allows plenty of room.</para></listitem>
|
---|
151 |
|
---|
152 | </itemizedlist>
|
---|
153 |
|
---|
154 | <para>Any separate partition that you want automatically mounted upon boot
|
---|
155 | needs to be specified in the <filename>/etc/fstab</filename>. Details
|
---|
156 | about how to specify partitions will be discussed in <xref
|
---|
157 | linkend="ch-bootable-fstab"/>. </para>
|
---|
158 |
|
---|
159 | </sect3>
|
---|
160 | </sect2>
|
---|
161 | </sect1>
|
---|