1 |
swift 13/12/18 10:13:54 |
2 |
|
3 |
Modified: handbook-amd64.xml handbook-x86.xml |
4 |
hb-install-config.xml |
5 |
hb-install-x86+amd64-bootloader.xml |
6 |
hb-install-x86+amd64-disk.xml |
7 |
Log: |
8 |
Fix bugs #485042 #488844 #437338 |
9 |
|
10 |
Revision Changes Path |
11 |
1.159 xml/htdocs/doc/en/handbook/handbook-amd64.xml |
12 |
|
13 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml?rev=1.159&view=markup |
14 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml?rev=1.159&content-type=text/plain |
15 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml?r1=1.158&r2=1.159 |
16 |
|
17 |
Index: handbook-amd64.xml |
18 |
=================================================================== |
19 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v |
20 |
retrieving revision 1.158 |
21 |
retrieving revision 1.159 |
22 |
diff -u -r1.158 -r1.159 |
23 |
--- handbook-amd64.xml 11 Feb 2013 20:38:20 -0000 1.158 |
24 |
+++ handbook-amd64.xml 18 Dec 2013 10:13:54 -0000 1.159 |
25 |
@@ -1,7 +1,7 @@ |
26 |
<?xml version='1.0' encoding='UTF-8'?> |
27 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
28 |
|
29 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v 1.158 2013/02/11 20:38:20 swift Exp $ --> |
30 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-amd64.xml,v 1.159 2013/12/18 10:13:54 swift Exp $ --> |
31 |
|
32 |
<book> |
33 |
<title>Gentoo Linux AMD64 Handbook</title> |
34 |
@@ -9,7 +9,7 @@ |
35 |
<values> |
36 |
<key id="arch">AMD64</key> |
37 |
<key id="arch-sub">x86_64</key> |
38 |
- <key id="/boot">/dev/sda1</key> |
39 |
+ <key id="/boot">/dev/sda2</key> |
40 |
<key id="kernel-version">3.4.9</key> |
41 |
<key id="kernel-name">kernel-3.4.9-gentoo</key> |
42 |
<key id="genkernel-name">kernel-genkernel-amd64-3.4.9-gentoo</key> |
43 |
@@ -141,8 +141,8 @@ |
44 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
45 |
<license/> |
46 |
|
47 |
-<version>15</version> |
48 |
-<date>2013-02-11</date> |
49 |
+<version>16</version> |
50 |
+<date>2013-12-18</date> |
51 |
|
52 |
<part> |
53 |
<title>Installing Gentoo</title> |
54 |
|
55 |
|
56 |
|
57 |
1.180 xml/htdocs/doc/en/handbook/handbook-x86.xml |
58 |
|
59 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml?rev=1.180&view=markup |
60 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml?rev=1.180&content-type=text/plain |
61 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml?r1=1.179&r2=1.180 |
62 |
|
63 |
Index: handbook-x86.xml |
64 |
=================================================================== |
65 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v |
66 |
retrieving revision 1.179 |
67 |
retrieving revision 1.180 |
68 |
diff -u -r1.179 -r1.180 |
69 |
--- handbook-x86.xml 9 Feb 2013 08:46:08 -0000 1.179 |
70 |
+++ handbook-x86.xml 18 Dec 2013 10:13:54 -0000 1.180 |
71 |
@@ -1,7 +1,7 @@ |
72 |
<?xml version='1.0' encoding='UTF-8'?> |
73 |
<!DOCTYPE book SYSTEM "/dtd/book.dtd"> |
74 |
|
75 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v 1.179 2013/02/09 08:46:08 swift Exp $ --> |
76 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/handbook-x86.xml,v 1.180 2013/12/18 10:13:54 swift Exp $ --> |
77 |
|
78 |
<book> |
79 |
<title>Gentoo Linux x86 Handbook</title> |
80 |
@@ -9,7 +9,7 @@ |
81 |
<values> |
82 |
<key id="arch">x86</key> |
83 |
<key id="arch-sub">x86</key> |
84 |
- <key id="/boot">/dev/sda1</key> |
85 |
+ <key id="/boot">/dev/sda2</key> |
86 |
<key id="kernel-version">3.3.8</key> |
87 |
<key id="kernel-name">kernel-3.3.8-gentoo</key> |
88 |
<key id="genkernel-name">kernel-genkernel-x86-3.3.8-gentoo</key> |
89 |
@@ -141,8 +141,8 @@ |
90 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
91 |
<license/> |
92 |
|
93 |
-<version>15</version> |
94 |
-<date>2013-02-09</date> |
95 |
+<version>16</version> |
96 |
+<date>2013-12-18</date> |
97 |
|
98 |
<part> |
99 |
<title>Installing Gentoo</title> |
100 |
|
101 |
|
102 |
|
103 |
1.128 xml/htdocs/doc/en/handbook/hb-install-config.xml |
104 |
|
105 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml?rev=1.128&view=markup |
106 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml?rev=1.128&content-type=text/plain |
107 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml?r1=1.127&r2=1.128 |
108 |
|
109 |
Index: hb-install-config.xml |
110 |
=================================================================== |
111 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v |
112 |
retrieving revision 1.127 |
113 |
retrieving revision 1.128 |
114 |
diff -u -r1.127 -r1.128 |
115 |
--- hb-install-config.xml 17 Dec 2013 11:52:05 -0000 1.127 |
116 |
+++ hb-install-config.xml 18 Dec 2013 10:13:54 -0000 1.128 |
117 |
@@ -4,7 +4,7 @@ |
118 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
119 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
120 |
|
121 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.127 2013/12/17 11:52:05 swift Exp $ --> |
122 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-config.xml,v 1.128 2013/12/18 10:13:54 swift Exp $ --> |
123 |
|
124 |
<sections> |
125 |
|
126 |
@@ -14,8 +14,8 @@ |
127 |
proceed. |
128 |
</abstract> |
129 |
|
130 |
-<version>33</version> |
131 |
-<date>2013-12-17</date> |
132 |
+<version>34</version> |
133 |
+<date>2013-12-18</date> |
134 |
|
135 |
<section> |
136 |
<title>Filesystem Information</title> |
137 |
@@ -131,7 +131,7 @@ |
138 |
Now use the <e>example</e> below to create your <path>/etc/fstab</path>: |
139 |
</p> |
140 |
|
141 |
-<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA'"> |
142 |
+<pre caption="A full /etc/fstab example" test="func:keyval('arch')='HPPA' or func:keyval('arch')='x86' or func:keyval('arch')='AMD64'"> |
143 |
<keyval id="/boot"/> /boot ext2 defaults,noatime 0 2 |
144 |
/dev/sda3 none swap sw 0 0 |
145 |
/dev/sda4 / ext4 noatime 0 1 |
146 |
@@ -139,7 +139,7 @@ |
147 |
/dev/cdrom /mnt/cdrom auto noauto,user 0 0 |
148 |
</pre> |
149 |
|
150 |
-<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS' or func:keyval('arch')='x86' or func:keyval('arch')='AMD64'"> |
151 |
+<pre caption="A full /etc/fstab example" test="func:keyval('arch')='Alpha' or func:keyval('arch')='MIPS'"> |
152 |
<keyval id="/boot"/> /boot ext2 defaults,noatime 0 2 |
153 |
/dev/sda2 none swap sw 0 0 |
154 |
/dev/sda3 / ext4 noatime 0 1 |
155 |
|
156 |
|
157 |
|
158 |
1.38 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml |
159 |
|
160 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.38&view=markup |
161 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.38&content-type=text/plain |
162 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.37&r2=1.38 |
163 |
|
164 |
Index: hb-install-x86+amd64-bootloader.xml |
165 |
=================================================================== |
166 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v |
167 |
retrieving revision 1.37 |
168 |
retrieving revision 1.38 |
169 |
diff -u -r1.37 -r1.38 |
170 |
--- hb-install-x86+amd64-bootloader.xml 18 Dec 2013 07:38:48 -0000 1.37 |
171 |
+++ hb-install-x86+amd64-bootloader.xml 18 Dec 2013 10:13:54 -0000 1.38 |
172 |
@@ -4,11 +4,11 @@ |
173 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
174 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
175 |
|
176 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.37 2013/12/18 07:38:48 swift Exp $ --> |
177 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.38 2013/12/18 10:13:54 swift Exp $ --> |
178 |
|
179 |
<sections> |
180 |
|
181 |
-<version>21</version> |
182 |
+<version>22</version> |
183 |
<date>2013-12-18</date> |
184 |
|
185 |
<section> |
186 |
@@ -251,16 +251,16 @@ |
187 |
image=/boot/<keyval id="kernel-name"/> |
188 |
label=gentoo <comment># Name we give to this section</comment> |
189 |
read-only <comment># Start with a read-only root. Do not alter!</comment> |
190 |
- root=/dev/sda3 <comment># Location of the root filesystem</comment> |
191 |
+ root=/dev/sda4 <comment># Location of the root filesystem</comment> |
192 |
|
193 |
image=/boot/<keyval id="kernel-name"/> |
194 |
label=gentoo.rescue <comment># Name we give to this section</comment> |
195 |
read-only <comment># Start with a read-only root. Do not alter!</comment> |
196 |
- root=/dev/sda3 <comment># Location of the root filesystem</comment> |
197 |
+ root=/dev/sda4 <comment># Location of the root filesystem</comment> |
198 |
append="init=/bin/bb" <comment># Launch the Gentoo static rescue shell</comment> |
199 |
|
200 |
<comment># The next two lines are only if you dualboot with a Windows system.</comment> |
201 |
-<comment># In this case, Windows is hosted on /dev/sda6.</comment> |
202 |
+<comment># In this example, Windows is hosted on /dev/sda6.</comment> |
203 |
other=/dev/sda6 |
204 |
label=windows |
205 |
</pre> |
206 |
@@ -280,7 +280,7 @@ |
207 |
image=/boot/<keyval id="kernel-name"/> |
208 |
label=gentoo |
209 |
read-only |
210 |
- <i>append="real_root=/dev/sda3"</i> |
211 |
+ <i>append="real_root=/dev/sda4"</i> |
212 |
<i>initrd=/boot/<keyval id="genkernel-initrd" /></i> |
213 |
</pre> |
214 |
|
215 |
@@ -294,7 +294,7 @@ |
216 |
image=/boot/<keyval id="kernel-name"/> |
217 |
label=gentoo |
218 |
read-only |
219 |
- root=/dev/sda3 |
220 |
+ root=/dev/sda4 |
221 |
<i>append="video=uvesafb:mtrr,ywrap,1024x768-32@85"</i> |
222 |
</pre> |
223 |
|
224 |
@@ -355,8 +355,8 @@ |
225 |
<p> |
226 |
The most critical part of understanding GRUB is getting comfortable with how |
227 |
GRUB refers to hard drives and partitions. Your Linux partition |
228 |
-<path>/dev/sda1</path> will most likely be called <path>(hd0,0)</path> under |
229 |
-GRUB. Notice the parentheses around the <path>hd0,0</path> - they are |
230 |
+<path>/dev/sda2</path> will most likely be called <path>(hd0,1)</path> under |
231 |
+GRUB. Notice the parentheses around the <path>hd0,1</path> - they are |
232 |
required. |
233 |
</p> |
234 |
|
235 |
@@ -440,16 +440,16 @@ |
236 |
timeout 30 |
237 |
<comment># Nice, fat splash-image to spice things up :) |
238 |
# Comment out if you don't have a graphics card installed</comment> |
239 |
-splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
240 |
+splashimage=(hd0,1)/boot/grub/splash.xpm.gz |
241 |
|
242 |
title Gentoo Linux <keyval id="kernel-version"/> |
243 |
<comment># Partition where the kernel image (or operating system) is located</comment> |
244 |
-root (hd0,0) |
245 |
+root (hd0,1) |
246 |
kernel /boot/<keyval id="kernel-name"/> root=/dev/sda3 |
247 |
|
248 |
title Gentoo Linux <keyval id="kernel-version"/> (rescue) |
249 |
<comment># Partition where the kernel image (or operating system) is located</comment> |
250 |
-root (hd0,0) |
251 |
+root (hd0,1) |
252 |
kernel /boot/<keyval id="kernel-name"/> root=/dev/sda3 init=/bin/bb |
253 |
|
254 |
<comment># The next four lines are only if you dualboot with a Windows system.</comment> |
255 |
@@ -468,7 +468,7 @@ |
256 |
|
257 |
<pre caption="GRUB snippet for initramfs-enabled kernel builds"> |
258 |
title Gentoo Linux <keyval id="kernel-version"/> |
259 |
-root (hd0,0) |
260 |
+root (hd0,1) |
261 |
kernel /boot/<keyval id="kernel-version"/> <i>real_</i>root=/dev/sda3 |
262 |
<i>initrd /boot/<keyval id="genkernel-initrd"/></i> |
263 |
</pre> |
264 |
@@ -476,9 +476,9 @@ |
265 |
<p> |
266 |
If you used a different partitioning scheme and/or kernel image, adjust |
267 |
accordingly. However, make sure that anything that follows a GRUB-device (such |
268 |
-as <path>(hd0,0)</path>) is relative to the mountpoint, not the root. In other |
269 |
-words, <path>(hd0,0)/grub/splash.xpm.gz</path> is in reality |
270 |
-<path>/boot/grub/splash.xpm.gz</path> since <path>(hd0,0)</path> is |
271 |
+as <path>(hd0,1)</path>) is relative to the mountpoint, not the root. In other |
272 |
+words, <path>(hd0,1)/grub/splash.xpm.gz</path> is in reality |
273 |
+<path>/boot/grub/splash.xpm.gz</path> since <path>(hd0,1)</path> is |
274 |
<path>/boot</path>. |
275 |
</p> |
276 |
|
277 |
@@ -619,7 +619,7 @@ |
278 |
For instance, if you type in "<c>root (</c>" followed by a TAB, you will |
279 |
be presented with a list of devices (such as <path>hd0</path>). If you |
280 |
type in "<c>root (hd0,</c>" followed by a TAB, you will receive a list |
281 |
-of available partitions to choose from (such as <path>hd0,0</path>). |
282 |
+of available partitions to choose from (such as <path>hd0,1</path>). |
283 |
</p> |
284 |
|
285 |
<p> |
286 |
@@ -628,7 +628,7 @@ |
287 |
</p> |
288 |
|
289 |
<pre caption="Installing GRUB in the MBR"> |
290 |
-grub> <i>root (hd0,0)</i> <comment>(Specify where your /boot partition resides)</comment> |
291 |
+grub> <i>root (hd0,1)</i> <comment>(Specify where your /boot partition resides)</comment> |
292 |
grub> <i>setup (hd0)</i> <comment>(Install GRUB in the MBR)</comment> |
293 |
grub> <i>quit</i> <comment>(Exit the GRUB shell)</comment> |
294 |
</pre> |
295 |
@@ -637,7 +637,7 @@ |
296 |
If you want to install GRUB in a certain partition instead of the MBR, |
297 |
you have to alter the <c>setup</c> command so it points to the right |
298 |
partition. For instance, if you want GRUB installed in |
299 |
-<path>/dev/sda3</path>, then the command becomes <c>setup (hd0,2)</c>. |
300 |
+<path>/dev/sda4</path>, then the command becomes <c>setup (hd0,4)</c>. |
301 |
Few users however want to do this. |
302 |
</note> |
303 |
|
304 |
|
305 |
|
306 |
|
307 |
1.29 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml |
308 |
|
309 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml?rev=1.29&view=markup |
310 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml?rev=1.29&content-type=text/plain |
311 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml?r1=1.28&r2=1.29 |
312 |
|
313 |
Index: hb-install-x86+amd64-disk.xml |
314 |
=================================================================== |
315 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml,v |
316 |
retrieving revision 1.28 |
317 |
retrieving revision 1.29 |
318 |
diff -u -r1.28 -r1.29 |
319 |
--- hb-install-x86+amd64-disk.xml 17 Dec 2013 10:09:49 -0000 1.28 |
320 |
+++ hb-install-x86+amd64-disk.xml 18 Dec 2013 10:13:54 -0000 1.29 |
321 |
@@ -4,7 +4,7 @@ |
322 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
323 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
324 |
|
325 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml,v 1.28 2013/12/17 10:09:49 swift Exp $ --> |
326 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-disk.xml,v 1.29 2013/12/18 10:13:54 swift Exp $ --> |
327 |
|
328 |
<sections> |
329 |
|
330 |
@@ -13,8 +13,8 @@ |
331 |
This chapter describes how to partition a disk for future usage. |
332 |
</abstract> |
333 |
|
334 |
-<version>20</version> |
335 |
-<date>2013-12-17</date> |
336 |
+<version>21</version> |
337 |
+<date>2013-12-18</date> |
338 |
|
339 |
<section> |
340 |
<title>Introduction to Block Devices</title> |
341 |
@@ -31,35 +31,89 @@ |
342 |
Although it is theoretically possible to use a full disk to house your Linux |
343 |
system, this is almost never done in practice. Instead, full disk block devices |
344 |
are split up in smaller, more manageable block devices. On <keyval id="arch"/> |
345 |
-systems, these are called <e>partitions</e>. |
346 |
+systems, these are called <e>partitions</e>. There are currently two standard |
347 |
+partitioning technologies in use: MBR and GPT. |
348 |
</p> |
349 |
|
350 |
<p> |
351 |
-Partitions are divided in three types: |
352 |
-<e>primary</e>, <e>extended</e> and <e>logical</e>. |
353 |
+The <e>MBR (Master Boot Record)</e> setup uses 32-bit identifiers for |
354 |
+partitions, and supports three partition types: <e>primary</e>, |
355 |
+<e>extended</e> and <e>logical</e>. Primary partitions have their information |
356 |
+stored in the master boot record itself - a very small (usually 512 bytes) |
357 |
+location at the very beginning of a disk. Due to this small space, only four |
358 |
+primary partitions are supported (for instance, <path>/dev/sda1</path> to |
359 |
+<path>/dev/sda4</path>). |
360 |
</p> |
361 |
|
362 |
<p> |
363 |
-A <e>primary</e> partition is a partition which has its information stored in |
364 |
-the MBR (master boot record). As an MBR is very small (512 bytes) only four |
365 |
-primary partitions can be defined (for instance, <path>/dev/sda1</path> to |
366 |
-<path>/dev/sda4</path>). |
367 |
+To support more partitions, one of the primary partitions can be marked as an |
368 |
+extended partition. This partition can then contain logical partitions |
369 |
+(partitions within a partition). |
370 |
+</p> |
371 |
+ |
372 |
+<p> |
373 |
+Each partition is limited to 2 TB in size (due to the 32-bit identifiers). |
374 |
+Also, the MBR setup does not provide any backup-MBR, so if an application |
375 |
+or user overwrites the MBR, all partition information is lost. |
376 |
+</p> |
377 |
+ |
378 |
+ |
379 |
+<p> |
380 |
+The <e>GPT (GUID Partition table)</e> setup uses 64-bit identifiers for |
381 |
+the partitions. The location in which it stores the partition information |
382 |
+is also much bigger than the 512 bytes of an MBR, and there is no limit on |
383 |
+the amount of partitions. Also the size of a partition is bounded by a much |
384 |
+greater limit (more than a few ZB - yes, zetabytes). |
385 |
+</p> |
386 |
+ |
387 |
+<p> |
388 |
+When a system's software interface between the operating system and firmware |
389 |
+is UEFI (instead of BIOS), GPT is almost mandatory as compatibility issues will |
390 |
+arise with MBR here. |
391 |
</p> |
392 |
|
393 |
<p> |
394 |
-An <e>extended</e> partition is a special primary partition (meaning the |
395 |
-extended partition must be one of the four possible primary partitions) which |
396 |
-contains more partitions. Such a partition didn't exist originally, but as |
397 |
-four partitions were too few, it was brought to life to extend the formatting |
398 |
-scheme without losing backward compatibility. |
399 |
+GPT also has the advantage that it has a backup GPT at the end of the disk, |
400 |
+which can be used to recover damage of the primary GPT at the beginning. GPT |
401 |
+also carries CRC32 checksums to detect errors in the header and partition |
402 |
+tables. |
403 |
+</p> |
404 |
+ |
405 |
+</body> |
406 |
+</subsection> |
407 |
+<subsection id="gpt_or_mbr"> |
408 |
+<title>So, GPT or MBR?</title> |
409 |
+<body> |
410 |
+ |
411 |
+<p> |
412 |
+From the description above, one might think that using GPT should always be the |
413 |
+recommended approach. But there are a few caveats with this. |
414 |
+</p> |
415 |
+ |
416 |
+<p> |
417 |
+Using GPT on a BIOS-based computer works, but you cannot dual-boot then with a |
418 |
+Microsoft Windows operating system. The reason is that Microsoft Windows will |
419 |
+boot in EFI mode if it detects a GPT partition label. |
420 |
</p> |
421 |
|
422 |
<p> |
423 |
-A <e>logical</e> partition is a partition inside the extended partition. Their |
424 |
-definitions aren't placed inside the MBR, but are declared inside the extended |
425 |
-partition. |
426 |
+Some buggy BIOSes or EFIs configured to boot in BIOS/CSM/legacy mode might also |
427 |
+have problems with booting from GPT labeled disks. If that is the case, you |
428 |
+might be able to work around the problem by adding the boot/active flag on the |
429 |
+protective MBR partition: |
430 |
</p> |
431 |
|
432 |
+<pre caption="Enabling boot flag on protective MBR"> |
433 |
+# <i>fdisk /dev/sda</i> |
434 |
+WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk |
435 |
+doesn't support GPT. Use GNU Parted. |
436 |
+ |
437 |
+Command (m for help): <i>a</i> |
438 |
+Partition number (1-4): <i>1</i> |
439 |
+ |
440 |
+Command (m for help): <i>w</i> |
441 |
+</pre> |
442 |
+ |
443 |
</body> |
444 |
</subsection> |
445 |
<subsection> |
446 |
@@ -84,7 +138,7 @@ |
447 |
|
448 |
<p> |
449 |
If you are not interested in drawing up a partitioning scheme for your system, |
450 |
-you can use the partitioning scheme we use throughout this book: |
451 |
+you can use the partitioning scheme we use throughout this book. |
452 |
</p> |
453 |
|
454 |
<table> |
455 |
@@ -96,18 +150,24 @@ |
456 |
</tr> |
457 |
<tr> |
458 |
<ti><path>/dev/sda1</path></ti> |
459 |
+ <ti>(bootloader)</ti> |
460 |
+ <ti>2M</ti> |
461 |
+ <ti>BIOS boot partition</ti> |
462 |
+</tr> |
463 |
+<tr> |
464 |
+ <ti><path>/dev/sda2</path></ti> |
465 |
<ti>ext2</ti> |
466 |
- <ti>32M</ti> |
467 |
+ <ti>128M</ti> |
468 |
<ti>Boot partition</ti> |
469 |
</tr> |
470 |
<tr> |
471 |
- <ti><path>/dev/sda2</path></ti> |
472 |
+ <ti><path>/dev/sda3</path></ti> |
473 |
<ti>(swap)</ti> |
474 |
<ti>512M or higher</ti> |
475 |
<ti>Swap partition</ti> |
476 |
</tr> |
477 |
<tr> |
478 |
- <ti><path>/dev/sda3</path></ti> |
479 |
+ <ti><path>/dev/sda4</path></ti> |
480 |
<ti>ext4</ti> |
481 |
<ti>Rest of the disk</ti> |
482 |
<ti>Root partition</ti> |
483 |
@@ -117,9 +177,9 @@ |
484 |
<p> |
485 |
If you are interested in knowing how big a partition should be, or even how |
486 |
many partitions you need, read on. Otherwise continue now with partitioning |
487 |
-your disk by reading <uri link="#fdisk">Using fdisk to Partition your |
488 |
-Disk</uri> or <uri link="#parted">Using parted to Partition your Disk</uri> |
489 |
-(both are partitioning tools, <c>fdisk</c> is well known and stable, |
490 |
+your disk by reading <uri link="#parted">Default: Using parted to Partition |
491 |
+your Disk</uri> (or <uri link="#fdisk">Alternative: Using fdisk to Partition |
492 |
+your Disk</uri>). Both are partitioning tools, <c>fdisk</c> is well known and stable, |
493 |
<c>parted</c> is a bit more recent but supports partitions larger than |
494 |
2TB). |
495 |
</p> |
496 |
@@ -238,17 +298,264 @@ |
497 |
|
498 |
</body> |
499 |
</subsection> |
500 |
+<subsection> |
501 |
+<title>What is the BIOS boot partition?</title> |
502 |
+<body> |
503 |
+ |
504 |
+<p> |
505 |
+A BIOS boot partition is a very small (1 to 2 MB) partition in which |
506 |
+bootloaders like GRUB can put additional data that doesn't fit in the |
507 |
+allocated storage (a few hundred bytes in case of MBR) and cannot place |
508 |
+elsewhere. |
509 |
+</p> |
510 |
+ |
511 |
+<p> |
512 |
+Such partitions are not always necessary, but considering the low space |
513 |
+consumption and the difficulties we would have with documenting the plethora |
514 |
+of partitioning differences otherwise, it is recommended to create it in |
515 |
+either case. |
516 |
+</p> |
517 |
+ |
518 |
+<p> |
519 |
+For completeness, we can say that the BIOS boot partition is needed when |
520 |
+GPT partition layout is used with GRUB, or when the MBR partition layout |
521 |
+is used with GRUB when the first partition starts earlier than the 1 MB |
522 |
+location on the disk. |
523 |
+</p> |
524 |
+ |
525 |
+</body> |
526 |
+</subsection> |
527 |
+</section> |
528 |
+<section id="parted"> |
529 |
+<title>Default: Using parted to Partition your Disk</title> |
530 |
+<subsection> |
531 |
+<body> |
532 |
+ |
533 |
+<p> |
534 |
+In this chapter, we guide you through the creation of the example partition |
535 |
+layout mentioned earlier in the instructions, but repeat here again for |
536 |
+your convenience: |
537 |
+</p> |
538 |
+ |
539 |
+<table> |
540 |
+<tr> |
541 |
+ <th>Partition</th> |
542 |
+ <th>Description</th> |
543 |
+</tr> |
544 |
+<tr> |
545 |
+ <ti><path>/dev/sda1</path></ti> |
546 |
+ <ti>BIOS boot partition</ti> |
547 |
+</tr> |
548 |
+<tr> |
549 |
+ <ti><path>/dev/sda2</path></ti> |
550 |
+ <ti>Boot partition</ti> |
551 |
+</tr> |
552 |
+<tr> |
553 |
+ <ti><path>/dev/sda3</path></ti> |
554 |
+ <ti>Swap partition</ti> |
555 |
+</tr> |
556 |
+<tr> |
557 |
+ <ti><path>/dev/sda4</path></ti> |
558 |
+ <ti>Root partition</ti> |
559 |
+</tr> |
560 |
+</table> |
561 |
+ |
562 |
+<p> |
563 |
+Change your partition layout according to your own preference. |
564 |
+</p> |
565 |
+ |
566 |
+</body> |
567 |
+</subsection> |
568 |
+<subsection> |
569 |
+<title>Viewing the Current Partition Layout</title> |
570 |
+<body> |
571 |
+ |
572 |
+<p> |
573 |
+The <c>parted</c> application offers a simple interface for partitioning your |
574 |
+disks and supports very large partitions (more than 2 TB). Fire up |
575 |
+<c>parted</c> on your disk (in our example, we use <path>/dev/sda</path>). |
576 |
+We will ask <c>parted</c> to use optimum alignment: |
577 |
+</p> |
578 |
+ |
579 |
+<pre caption="Starting parted"> |
580 |
+# <i>parted -a optimal /dev/sda</i> |
581 |
+GNU Parted 2.3 |
582 |
+Using /dev/vda |
583 |
+Welcome to GNU Parted! Type 'help' to view a list of commands. |
584 |
+</pre> |
585 |
+ |
586 |
+<p> |
587 |
+Alignment means that partitions are started on well-known boundaries within |
588 |
+the disk, ensuring that operations on the disk from the operating system level |
589 |
+(retrieve pages from the disk) use the least amount of internal disk |
590 |
+operations. Misaligned partitions might require the disk to fetch two pages |
591 |
+instead of one even if the operating system asked for a single page. |
592 |
+</p> |
593 |
+ |
594 |
+<p> |
595 |
+To find out about all options supported by <c>parted</c>, type <c>help</c> and |
596 |
+press return. |
597 |
+</p> |
598 |
+ |
599 |
+</body> |
600 |
+</subsection> |
601 |
+<subsection> |
602 |
+<title>Setting the GPT Label</title> |
603 |
+<body> |
604 |
+ |
605 |
+<p> |
606 |
+Most disks on x86/amd64 are prepared using an <e>msdos</e> label. Using |
607 |
+<c>parted</c>, we can put a GPT label on the disk using <c>mklabel gpt</c>: |
608 |
+</p> |
609 |
+ |
610 |
+<warn> |
611 |
+Changing the partition type will remove all partitions from your disk. All data |
612 |
+on the disk will be lost. |
613 |
+</warn> |
614 |
+ |
615 |
+<pre caption="Setting the GPT label"> |
616 |
+(parted) <i>mklabel gpt</i> |
617 |
+</pre> |
618 |
+ |
619 |
+<p> |
620 |
+If you want the disk to have MBR layout, use <c>mklabel msdos</c>. |
621 |
+</p> |
622 |
+ |
623 |
+</body> |
624 |
+</subsection> |
625 |
+<subsection> |
626 |
+<title>Removing all Partitions</title> |
627 |
+<body> |
628 |
+ |
629 |
+<p> |
630 |
+If this isn't done yet (for instance through the <c>mklabel</c> operation |
631 |
+earlier, or because the disk is a freshly formatted one), we will first |
632 |
+remove all existing partitions from the disk. Type <c>print</c> to view the |
633 |
+current partitions, and <c>rm <number></c> where <number> is the |
634 |
+partition you want to remove. |
635 |
+</p> |
636 |
+ |
637 |
+<pre caption="Removing a partition from the disk"> |
638 |
+(parted) <i>rm 2</i> |
639 |
+</pre> |
640 |
+ |
641 |
+<p> |
642 |
+Do the same for all other partitions that you don't need. However, make sure you |
643 |
+do not make any mistakes here - <c>parted</c> executes the changes immediately |
644 |
+(unlike <c>fdisk</c> which stages them, allowing a user to "undo" his changes |
645 |
+before saving or exiting <c>fdisk</c>). |
646 |
+</p> |
647 |
+ |
648 |
+</body> |
649 |
+</subsection> |
650 |
+<subsection> |
651 |
+<title>Creating the Partitions</title> |
652 |
+<body> |
653 |
+ |
654 |
+<p> |
655 |
+Now let's create the partitions we mentioned earlier. Creating partitions with |
656 |
+<c>parted</c> isn't very difficult - all we need to do is inform <c>parted</c> |
657 |
+about the following settings: |
658 |
+</p> |
659 |
+ |
660 |
+<ul> |
661 |
+ <li> |
662 |
+ The <e>partition type</e> to use. This usually is <e>primary</e>. |
663 |
+ If you use the <e>msdos</e> partition label, keep in mind that you can have |
664 |
+ no more than 4 primary partitions. If you need more than 4 partitions, make |
665 |
+ a partition <e>extended</e> and create <e>logical</e> partitions inside it. |
666 |
+ </li> |
667 |
+ <li> |
668 |
+ The start location of a partition (which can be expressed in MB or GB) |
669 |
+ </li> |
670 |
+ <li> |
671 |
+ The end location of the partition (which can be expressed in MB or GB) |
672 |
+ </li> |
673 |
+</ul> |
674 |
+ |
675 |
+<p> |
676 |
+First, we tell <c>parted</c> that the size unit we work with is megabytes |
677 |
+(actually mebibytes, abbreviated as MiB which is the "standard" notation): |
678 |
+</p> |
679 |
+ |
680 |
+<pre caption="Using MiB units"> |
681 |
+(parted) <i>unit mib</i> |
682 |
+</pre> |
683 |
+ |
684 |
+<p> |
685 |
+Now create a 2 MB partition that will be used by the GRUB bootloader later. |
686 |
+We use the <c>mkpart</c> command for this, and inform <c>parted</c> to start |
687 |
+from 1 MB and end at 3 MB (creating a partition of 2 MB in size). |
688 |
+</p> |
689 |
+ |
690 |
+<pre caption="Creating a 128 MB partition"> |
691 |
+(parted) <i>mkpart primary 1 3</i> |
692 |
+(parted) <i>name 1 grub</i> |
693 |
+(parted) <i>set 1 bios_grub on</i> |
694 |
+(parted) <i>print</i> |
695 |
+Model: Virtio Block Device (virtblk) |
696 |
+Disk /dev/sda: 20480MiB |
697 |
+Sector size (logical/physical): 512B/512B |
698 |
+Partition Table: gpt |
699 |
+ |
700 |
+Number Start End Size File system Name Flags |
701 |
+ 1 1.00MiB 3.00MiB 2.00MiB grub bios_grub |
702 |
+</pre> |
703 |
+ |
704 |
+<p> |
705 |
+Do the same for the boot partition (128 MB), swap partition (in the example, |
706 |
+512 MB) and the root partition that spans the remaining disk (for which the |
707 |
+end size is marked as <c>-1</c>, meaning the end of the disk minus one MB, |
708 |
+which is the farthest a partition can go). |
709 |
+</p> |
710 |
+ |
711 |
+<pre caption="Creating other partitions"> |
712 |
+(parted) <i>mkpart primary 3 131</i> |
713 |
+(parted) <i>name 2 boot</i> |
714 |
+(parted) <i>mkpart primary 131 643</i> |
715 |
+(parted) <i>name 3 swap</i> |
716 |
+(parted) <i>mkpart primary 643 -1</i> |
717 |
+(parted) <i>name 4 rootfs</i> |
718 |
+</pre> |
719 |
+ |
720 |
+<p> |
721 |
+The end result looks like so: |
722 |
+</p> |
723 |
+ |
724 |
+<pre caption="Viewing the current partition layout"> |
725 |
+(parted) <i>print</i> |
726 |
+Model: Virtio Block Device (virtblk) |
727 |
+Disk /dev/sda: 20480MiB |
728 |
+Sector size (logical/physical): 512B/512B |
729 |
+Partition Table: gpt |
730 |
+ |
731 |
+Number Start End Size File system Name Flags |
732 |
+ 1 1.00MiB 3.00MiB 2.00MiB grub bios_grub |
733 |
+ 2 3.00MiB 131MiB 128MiB boot |
734 |
+ 3 131MiB 643MiB 512MiB swap |
735 |
+ 4 643MiB 20479MiB 19836MiB rootfs |
736 |
+</pre> |
737 |
+ |
738 |
+<p> |
739 |
+When you are satisfied, use the <c>quit</c> command to exit <c>parted</c>. |
740 |
+</p> |
741 |
+ |
742 |
+</body> |
743 |
+</subsection> |
744 |
</section> |
745 |
<section id="fdisk"> |
746 |
-<title>Using fdisk to Partition your Disk</title> |
747 |
+<title>Alternative: Using fdisk to Partition your Disk</title> |
748 |
<subsection> |
749 |
<body> |
750 |
|
751 |
<impo> |
752 |
If your environment will deal with partitions larger than 2 TB, please |
753 |
-use the <uri link="#parted">Using parted to Partition your Disk</uri> |
754 |
+use the <uri link="#parted">Default: Using parted to Partition your Disk</uri> |
755 |
instructions instead. <c>fdisk</c> is not able to deal with larger |
756 |
-partitions. |
757 |
+partitions. Fdisk will also use the MBR partition layout. Alternative fdisk |
758 |
+applications, like gdisk (which Gentoo provides through the gptfdisk package) |
759 |
+exist that do support GPT, but might not be included on the Gentoo installation |
760 |
+media. |
761 |
</impo> |
762 |
|
763 |
<p> |
764 |
@@ -263,14 +570,18 @@ |
765 |
</tr> |
766 |
<tr> |
767 |
<ti><path>/dev/sda1</path></ti> |
768 |
- <ti>Boot partition</ti> |
769 |
+ <ti>BIOS boot partition</ti> |
770 |
</tr> |
771 |
<tr> |
772 |
<ti><path>/dev/sda2</path></ti> |
773 |
- <ti>Swap partition</ti> |
774 |
+ <ti>Boot partition</ti> |
775 |
</tr> |
776 |
<tr> |
777 |
<ti><path>/dev/sda3</path></ti> |
778 |
+ <ti>Swap partition</ti> |
779 |
+</tr> |
780 |
+<tr> |
781 |
+ <ti><path>/dev/sda4</path></ti> |
782 |
<ti>Root partition</ti> |
783 |
</tr> |
784 |
</table> |
785 |
@@ -383,18 +694,23 @@ |
786 |
</body> |
787 |
</subsection> |
788 |
<subsection> |
789 |
-<title>Creating the Boot Partition</title> |
790 |
+<title>Creating the BIOS Boot Partition</title> |
791 |
<body> |
792 |
|
793 |
<p> |
794 |
-We first create a small boot partition. Type <c>n</c> to create a new partition, |
795 |
-then <c>p</c> to select a primary partition, followed by <c>1</c> to select the |
796 |
-first primary partition. When prompted for the first sector, make sure it starts |
797 |
-from <c>2048</c> (which is needed for the boot loader) and hit enter. When |
798 |
+We first create a very small BIOS boot partition. Type <c>n</c> to create a new |
799 |
+partition, then <c>p</c> to select a primary partition, followed by <c>1</c> to |
800 |
+select the first primary partition. When prompted for the first sector, make sure |
801 |
+it starts from <c>2048</c> (which is needed for the boot loader) and hit enter. When |
802 |
prompted for the last sector, type <c>+32M</c> to create a partition 32 Mbyte |
803 |
in size: |
804 |
</p> |
805 |
|
806 |
+<note> |
807 |
+The start from sector 2048 is a fail-safe in case the boot loader does not |
808 |
+detect this partition as being available for its use. |
809 |
+</note> |
810 |
+ |
811 |
<pre caption="Creating the boot partition"> |
812 |
Command (m for help): <i>n</i> |
813 |
Command action |
814 |
@@ -403,7 +719,43 @@ |
815 |
<i>p</i> |
816 |
Partition number (1-4): <i>1</i> |
817 |
First sector (64-10486533532, default 64): <i>2048</i> |
818 |
-Last sector, +sectors +size{M,K,G} (4096-10486533532, default 10486533532): <i>+32M</i> |
819 |
+Last sector, +sectors +size{M,K,G} (4096-10486533532, default 10486533532): <i>+2M</i> |
820 |
+</pre> |
821 |
+ |
822 |
+<p> |
823 |
+Mark the partition for EFI purposes: |
824 |
+</p> |
825 |
+ |
826 |
+<pre caption="Marking the partition for EFI purposes"> |
827 |
+Command (m for help): <i>t</i> |
828 |
+Selected partition 1 |
829 |
+Hex code (type L to list codes): <i>ef</i> |
830 |
+Changed system type of partition 1 to ef (EFI (FAT-12/16/32)) |
831 |
+</pre> |
832 |
+ |
833 |
+</body> |
834 |
+</subsection> |
835 |
+<subsection> |
836 |
+<title>Creating the Boot Partition</title> |
837 |
+<body> |
838 |
+ |
839 |
+<p> |
840 |
+We now create a small boot partition. Type <c>n</c> to create a new partition, |
841 |
+then <c>p</c> to select a primary partition, followed by <c>2</c> to select the |
842 |
+second primary partition. When prompted for the first sector, accept the default |
843 |
+by hitting enter. When prompted for the last sector, type <c>+128M</c> to create a |
844 |
+partition 128 Mbyte in size: |
845 |
+</p> |
846 |
+ |
847 |
+<pre caption="Creating the boot partition"> |
848 |
+Command (m for help): <i>n</i> |
849 |
+Command action |
850 |
+ e extended |
851 |
+ p primary partition (1-4) |
852 |
+<i>p</i> |
853 |
+Partition number (1-4): <i>2</i> |
854 |
+First sector (5198-10486533532, default 5198): <comment>(Hit enter)</comment> |
855 |
+Last sector, +sectors +size{M,K,G} (4096-10486533532, default 10486533532): <i>+128M</i> |
856 |
</pre> |
857 |
|
858 |
<p> |
859 |
@@ -418,7 +770,8 @@ |
860 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
861 |
|
862 |
Device Boot Start End Blocks Id System |
863 |
-/dev/sda1 1 14 105808+ 83 Linux |
864 |
+/dev/sda1 1 3 5198+ ef EFI (FAT-12/16/32) |
865 |
+/dev/sda2 3 14 105808+ 83 Linux |
866 |
</pre> |
867 |
|
868 |
<p> |
869 |
@@ -436,31 +789,18 @@ |
870 |
<p> |
871 |
Let's now create the swap partition. To do this, type <c>n</c> to create a new |
872 |
partition, then <c>p</c> to tell fdisk that you want a primary partition. Then |
873 |
-type <c>2</c> to create the second primary partition, <path>/dev/sda2</path> in |
874 |
+type <c>3</c> to create the third primary partition, <path>/dev/sda3</path> in |
875 |
our case. When prompted for the first sector, hit enter. When prompted for |
876 |
the last sector, type <c>+512M</c> (or any other size you need for the swap |
877 |
space) to create a partition 512MB in size. |
878 |
</p> |
879 |
|
880 |
<p> |
881 |
-After you've done this, type <c>t</c> to set the partition type, <c>2</c> to select |
882 |
+After you've done this, type <c>t</c> to set the partition type, <c>3</c> to select |
883 |
the partition you just created and then type in <c>82</c> to set the partition |
884 |
-type to "Linux Swap". After completing these steps, typing <c>p</c> should |
885 |
-display a partition table that looks similar to this: |
886 |
+type to "Linux Swap". |
887 |
</p> |
888 |
|
889 |
-<pre caption="Partition listing after creating a swap partition"> |
890 |
-Command (m for help): <i>p</i> |
891 |
- |
892 |
-Disk /dev/sda: 30.0 GB, 30005821440 bytes |
893 |
-240 heads, 63 sectors/track, 3876 cylinders |
894 |
-Units = cylinders of 15120 * 512 = 7741440 bytes |
895 |
- |
896 |
- Device Boot Start End Blocks Id System |
897 |
-/dev/sda1 * 1 14 105808+ 83 Linux |
898 |
-/dev/sda2 15 81 506520 82 Linux swap |
899 |
-</pre> |
900 |
- |
901 |
</body> |
902 |
</subsection> |
903 |
<subsection> |
904 |
@@ -470,7 +810,7 @@ |
905 |
<p> |
906 |
Finally, let's create the root partition. To do this, type <c>n</c> to create a |
907 |
new partition, then <c>p</c> to tell fdisk that you want a primary partition. |
908 |
-Then type <c>3</c> to create the third primary partition, <path>/dev/sda3</path> |
909 |
+Then type <c>4</c> to create the fourth primary partition, <path>/dev/sda4</path> |
910 |
in our case. When prompted for the first sector, hit enter. When prompted for |
911 |
the last sector, hit enter to create a partition that takes up the rest of the |
912 |
remaining space on your disk. After completing these steps, typing <c>p</c> |
913 |
@@ -485,9 +825,10 @@ |
914 |
Units = cylinders of 15120 * 512 = 7741440 bytes |
915 |
|
916 |
Device Boot Start End Blocks Id System |
917 |
-/dev/sda1 * 1 14 105808+ 83 Linux |
918 |
-/dev/sda2 15 81 506520 82 Linux swap |
919 |
-/dev/sda3 82 3876 28690200 83 Linux |
920 |
+/dev/sda1 1 3 5198+ ef EFI (FAT-12/16/32) |
921 |
+/dev/sda2 * 3 14 105808+ 83 Linux |
922 |
+/dev/sda3 15 81 506520 82 Linux swap |
923 |
+/dev/sda4 82 3876 28690200 83 Linux |
924 |
</pre> |
925 |
|
926 |
</body> |
927 |
@@ -512,204 +853,6 @@ |
928 |
</body> |
929 |
</subsection> |
930 |
</section> |
931 |
-<section id="parted"> |
932 |
-<title>Using parted to Partition your Disk</title> |
933 |
-<subsection> |
934 |
-<body> |
935 |
- |
936 |
-<p> |
937 |
-In this chapter, we guide you through the creation of the example partition |
938 |
-layout mentioned earlier in the instructions. Unlike the previous chapter, we |
939 |
-describe the method using the <c>parted</c> application instead. Both |
940 |
-<c>parted</c> and <c>fdisk</c> offer the same functions, so if you partitioned |
941 |
-your system using <c>fdisk</c> already, you can skip this section and continue |
942 |
-with <uri link="#filesystems">Creating Filesystems</uri>. |
943 |
-</p> |
944 |
- |
945 |
-<p> |
946 |
-The example partition layout we use is shown in the next table: |
947 |
-</p> |
948 |
- |
949 |
-<table> |
950 |
-<tr> |
951 |
- <th>Partition</th> |
952 |
- <th>Description</th> |
953 |
-</tr> |
954 |
-<tr> |
955 |
- <ti><path>/dev/sda1</path></ti> |
956 |
- <ti>Boot partition</ti> |
957 |
-</tr> |
958 |
-<tr> |
959 |
- <ti><path>/dev/sda2</path></ti> |
960 |
- <ti>Swap partition</ti> |
961 |
-</tr> |
962 |
-<tr> |
963 |
- <ti><path>/dev/sda3</path></ti> |
964 |
- <ti>Root partition</ti> |
965 |
-</tr> |
966 |
-</table> |
967 |
- |
968 |
-<p> |
969 |
-Change your partition layout according to your own preference. |
970 |
-</p> |
971 |
- |
972 |
-</body> |
973 |
-</subsection> |
974 |
-<subsection> |
975 |
-<title>Viewing the Current Partition Layout</title> |
976 |
-<body> |
977 |
- |
978 |
-<p> |
979 |
-The <c>parted</c> application is a somewhat more modern variant of |
980 |
-<c>fdisk</c>. It offers a simpler interface for partitioning your disks and |
981 |
-supports very large partitions (more than 2 TB). Fire up <c>parted</c> on your |
982 |
-disk (in our example, we use <path>/dev/sda</path>): |
983 |
-</p> |
984 |
- |
985 |
-<pre caption="Starting parted"> |
986 |
-# <i>parted /dev/sda</i> |
987 |
-GNU Parted 2.3 |
988 |
-Using /dev/vda |
989 |
-Welcome to GNU Parted! Type 'help' to view a list of commands. |
990 |
-</pre> |
991 |
- |
992 |
-<p> |
993 |
-To find out about all options supported by <c>parted</c>, type <c>help</c> and |
994 |
-press return. For now, we just continue by asking <c>parted</c> to show the |
995 |
-partitions currently in use on the selected disk. The <c>print</c> command can |
996 |
-be used for that. |
997 |
-</p> |
998 |
- |
999 |
-<pre caption="An example partition configuration shown by parted"> |
1000 |
-(parted) <i>print</i> |
1001 |
-Model: SCSI Block Device |
1002 |
-Disk /dev/sda: 21.5GB |
1003 |
-Sector size (logical/physical): 512B/512B |
1004 |
-Partition Table: msdos |
1005 |
- |
1006 |
-Number Start End Size Type File system Flags |
1007 |
- 1 512B 2148MB 2148MB primary ext4 |
1008 |
- 2 2148MB 3222MB 1074MB primary linux-swap(v1) |
1009 |
- 3 3222MB 21.5GB 18.3GB primary lvm |
1010 |
-</pre> |
1011 |
- |
1012 |
-</body> |
1013 |
-</subsection> |
1014 |
-<subsection> |
1015 |
-<title>Optional: Setting the GPT Label</title> |
1016 |
-<body> |
1017 |
- |
1018 |
-<p> |
1019 |
-Most disks on x86/amd64 are prepared using an <e>msdos</e> label. However, if |
1020 |
-you plan on creating huge partitions (2 TB and more), you must use a <e>gpt</e> |
1021 |
-label (the <e>GUID Partition Type</e>) for your disk. Using <c>parted</c>, this |
1022 |
-can be accomplished with <c>mklabel gpt</c>: |
1023 |
-</p> |
1024 |
- |
1025 |
-<warn> |
1026 |
-Changing the partition type will remove all partitions from your disk. All data |
1027 |
-on the disk will be lost. |
1028 |
-</warn> |
1029 |
- |
1030 |
-<pre caption="Setting the GPT label"> |
1031 |
-(parted) <i>mklabel gpt</i> |
1032 |
-</pre> |
1033 |
- |
1034 |
-</body> |
1035 |
-</subsection> |
1036 |
-<subsection> |
1037 |
-<title>Removing all Partitions</title> |
1038 |
-<body> |
1039 |
- |
1040 |
-<p> |
1041 |
-If this isn't done yet (for instance through the <c>mklabel</c> operation |
1042 |
-earlier, or because the disk is a freshly formatted one), we will first |
1043 |
-remove all existing partitions from the disk. Type <c>rm <number></c> |
1044 |
-where <number> is the partition you want to remove. |
1045 |
-</p> |
1046 |
- |
1047 |
-<pre caption="Removing a partition from the disk"> |
1048 |
-(parted) <i>rm 2</i> |
1049 |
-</pre> |
1050 |
- |
1051 |
-<p> |
1052 |
-Do the same for all other partitions that you don't need. However, make sure you |
1053 |
-do not make any mistakes here - <c>parted</c> executes the changes immediately |
1054 |
-(unlike <c>fdisk</c> which stages them, allowing a user to "undo" his changes |
1055 |
-before saving or exiting <c>fdisk</c>). |
1056 |
-</p> |
1057 |
- |
1058 |
-</body> |
1059 |
-</subsection> |
1060 |
-<subsection> |
1061 |
-<title>Creating the Partitions</title> |
1062 |
-<body> |
1063 |
- |
1064 |
-<p> |
1065 |
-Now let's create the partitions we mentioned earlier. Creating partitions with |
1066 |
-<c>parted</c> isn't very difficult - all we need to do is inform <c>parted</c> |
1067 |
-about the following settings: |
1068 |
-</p> |
1069 |
- |
1070 |
-<ul> |
1071 |
- <li> |
1072 |
- The <e>partition type</e> to use. This usually is <e>primary</e> in case you |
1073 |
- are not going to have more than 4 partitions (with the <e>msdos</e> |
1074 |
- partition label). Otherwise, you will need to make your fourth partition an |
1075 |
- <e>extended</e> one which hosts the rest of the disk, and create |
1076 |
- <e>logical</e> partitions inside it. If you use a <e>gpt</e>-labeled |
1077 |
- partition, then there is no limit on the number of primary partitions. |
1078 |
- </li> |
1079 |
- <li> |
1080 |
- The <e>file system type</e> to use. The <c>parted</c> application supports |
1081 |
- most common file systems and knows which kind of partition ID it needs to |
1082 |
- use for these partitions. This does <e>not</e> mean that <c>parted</c> will |
1083 |
- create a file system on the partition (you can with the <c>mkpartfs</c> |
1084 |
- command, but we'll use the regular <c>mkfs.*</c> commands later for this |
1085 |
- purpose). The partition ID is often used by auto-detection tools to know |
1086 |
- what to do with a particular partition. |
1087 |
- </li> |
1088 |
- <li> |
1089 |
- The start location of a partition (which can be expressed in MB or GB) |
1090 |
- </li> |
1091 |
- <li> |
1092 |
- The end location of the partition (which can be expressed in MB or GB) |
1093 |
- </li> |
1094 |
-</ul> |
1095 |
- |
1096 |
-<p> |
1097 |
-One advantage of <c>parted</c> is that you can easily just use the partition |
1098 |
-sizes to automatically find the correct start and end location as you will see |
1099 |
-in the next example. |
1100 |
-</p> |
1101 |
- |
1102 |
-<pre caption="Creating the partitions"> |
1103 |
-<comment># Create a 32 mbyte /boot partition</comment> |
1104 |
-(parted) <i>mkpart primary ext2 0 32mb</i> |
1105 |
-Warning: The resulting partition is not properly aligned for best performance. |
1106 |
-Ignore/Cancel? <i>i</i> |
1107 |
- |
1108 |
-<comment># Create a 512 mbyte swap partition</comment> |
1109 |
-(parted) <i>mkpart primary linux-swap 32mb 544mb</i> |
1110 |
- |
1111 |
-<comment># Create a partition that spans the remaining disk. |
1112 |
-# -1s (minus one s) means the end of the disk</comment> |
1113 |
-(parted) <i>mkpart primary ext4 544mb -1s</i> |
1114 |
-Warning: You requested a partition from 544MB to 21.5GB. |
1115 |
-The closest location we can manage is 544MB to 21.5GB. |
1116 |
-Is this still acceptable to you? |
1117 |
-Yes/No? <i>y</i> |
1118 |
-</pre> |
1119 |
- |
1120 |
-<p> |
1121 |
-You can now <c>print</c> the partition layout again to validate if everything is |
1122 |
-as expected. When you are satisfied, use the <c>quit</c> command to exit |
1123 |
-<c>parted</c>. |
1124 |
-</p> |
1125 |
- |
1126 |
-</body> |
1127 |
-</subsection> |
1128 |
-</section> |
1129 |
<section id="filesystems"> |
1130 |
<title>Creating Filesystems</title> |
1131 |
<subsection> |
1132 |
@@ -772,14 +915,14 @@ |
1133 |
</table> |
1134 |
|
1135 |
<p> |
1136 |
-For instance, to have the boot partition (<path>/dev/sda1</path> in our |
1137 |
-example) in ext2 and the root partition (<path>/dev/sda3</path> in our example) |
1138 |
+For instance, to have the boot partition (<path>/dev/sda2</path> in our |
1139 |
+example) in ext2 and the root partition (<path>/dev/sda4</path> in our example) |
1140 |
in ext4 (as in our example), you would use: |
1141 |
</p> |
1142 |
|
1143 |
<pre caption="Applying a filesystem on a partition"> |
1144 |
-# <i>mkfs.ext2 /dev/sda1</i> |
1145 |
-# <i>mkfs.ext4 /dev/sda3</i> |
1146 |
+# <i>mkfs.ext2 /dev/sda2</i> |
1147 |
+# <i>mkfs.ext4 /dev/sda4</i> |
1148 |
</pre> |
1149 |
|
1150 |
<p> |
1151 |
@@ -798,7 +941,7 @@ |
1152 |
</p> |
1153 |
|
1154 |
<pre caption="Creating a Swap signature"> |
1155 |
-# <i>mkswap /dev/sda2</i> |
1156 |
+# <i>mkswap /dev/sda3</i> |
1157 |
</pre> |
1158 |
|
1159 |
<p> |
1160 |
@@ -806,7 +949,7 @@ |
1161 |
</p> |
1162 |
|
1163 |
<pre caption="Activating the swap partition"> |
1164 |
-# <i>swapon /dev/sda2</i> |
1165 |
+# <i>swapon /dev/sda3</i> |
1166 |
</pre> |
1167 |
|
1168 |
<p> |
1169 |
@@ -828,9 +971,9 @@ |
1170 |
</p> |
1171 |
|
1172 |
<pre caption="Mounting partitions"> |
1173 |
-# <i>mount /dev/sda3 /mnt/gentoo</i> |
1174 |
+# <i>mount /dev/sda4 /mnt/gentoo</i> |
1175 |
# <i>mkdir /mnt/gentoo/boot</i> |
1176 |
-# <i>mount /dev/sda1 /mnt/gentoo/boot</i> |
1177 |
+# <i>mount /dev/sda2 /mnt/gentoo/boot</i> |
1178 |
</pre> |
1179 |
|
1180 |
<note> |