/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.20 Revision 1.34
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml,v 1.20 2004/11/09 13:01:52 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ppc-disk.xml,v 1.34 2006/02/27 00:55:34 fox2mike Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.19</version> 11<version>2.5</version>
12<date>November 2, 2004</date> 12<date>2006-02-27</date>
13 13
14<section> 14<section>
15<title>Introduction to Block Devices</title> 15<title>Introduction to Block Devices</title>
16<subsection> 16<subsection>
17<title>Block Devices</title> 17<title>Block Devices</title>
24you'll be guided through the process of setting up partitions and filesystems 24you'll be guided through the process of setting up partitions and filesystems
25for your Gentoo Linux installation. 25for your Gentoo Linux installation.
26</p> 26</p>
27 27
28<p> 28<p>
29To begin, we'll introduce <e>block devices</e>. The most famous block device is 29To begin, we'll introduce <e>block devices</e>. The most common block device is
30probably the one that represents the first IDE drive in a Linux system, namely 30the one that represents the first IDE drive in a Linux system, namely
31<path>/dev/hda</path>. If your system uses SCSI drives, then your first hard 31<path>/dev/hda</path>. If you are installing onto SCSI, FireWire, USB or SATA
32drive would be <path>/dev/sda</path>. 32drives, then your first hard drive would be <path>/dev/sda</path>.
33</p> 33</p>
34 34
35<p> 35<p>
36The block devices above represent an abstract interface to the disk. User 36The block devices above represent an abstract interface to the disk. User
37programs can use these block devices to interact with your disk without worrying 37programs can use these block devices to interact with your disk without worrying
41</p> 41</p>
42 42
43</body> 43</body>
44</subsection> 44</subsection>
45<subsection> 45<subsection>
46<title>Partitions and Slices</title> 46<title>Partitions</title>
47<body> 47<body>
48 48
49<p> 49<p>
50Although it is theoretically possible to use a full disk to house your Linux 50Although it is theoretically possible to use a full disk to house your Linux
51system, this is almost never done in practice. Instead, full disk block devices 51system, this is almost never done in practice. Instead, full disk block devices
52are split up in smaller, more manageable block devices. On most systems, 52are split up in smaller, more manageable block devices. On most systems,
53these are called <e>partitions</e>. Other architectures use a similar technique, 53these are called <e>partitions</e>.
54called <e>slices</e>.
55</p> 54</p>
56 55
57</body> 56</body>
58</subsection> 57</subsection>
59</section> 58</section>
71<table> 70<table>
72<tr> 71<tr>
73 <th>Partition NewWorld</th> 72 <th>Partition NewWorld</th>
74 <th>Partition OldWorld</th> 73 <th>Partition OldWorld</th>
75 <th>Partition Pegasos</th> 74 <th>Partition Pegasos</th>
75 <th>Partition RS/6000</th>
76 <th>Filesystem</th> 76 <th>Filesystem</th>
77 <th>Size</th> 77 <th>Size</th>
78 <th>Description</th> 78 <th>Description</th>
79</tr> 79</tr>
80<tr> 80<tr>
81 <ti><path>/dev/hda1</path></ti> 81 <ti><path>/dev/hda1</path></ti>
82 <ti>/dev/hda1</ti> 82 <ti><path>/dev/hda1</path></ti>
83 <ti>(Not applicable)</ti>
83 <ti>(Not applicable)</ti> 84 <ti>(Not applicable)</ti>
84 <ti>(Partition Map)</ti> 85 <ti>(Partition Map)</ti>
85 <ti>32k</ti> 86 <ti>32k</ti>
86 <ti>Apple_partition_map</ti> 87 <ti>Apple_partition_map</ti>
87</tr> 88</tr>
88<tr> 89<tr>
89 <ti><path>/dev/hda2</path></ti> 90 <ti><path>/dev/hda2</path></ti>
90 <ti>(Not needed)</ti> 91 <ti>(Not applicable)</ti>
92 <ti>(Not applicable)</ti>
91 <ti>(Not applicable)</ti> 93 <ti>(Not applicable)</ti>
92 <ti>(bootstrap)</ti> 94 <ti>(bootstrap)</ti>
93 <ti>800k</ti> 95 <ti>800k</ti>
94 <ti>Apple_Bootstrap</ti> 96 <ti>Apple_Bootstrap</ti>
95</tr> 97</tr>
96<tr> 98<tr>
99 <ti>(Not applicable)</ti>
100 <ti>(Not applicable)</ti>
101 <ti>(Not applicable)</ti>
102 <ti><path>/dev/sda1</path></ti>
103 <ti>(PReP Boot)</ti>
104 <ti>800k</ti>
105 <ti>Type 0x41</ti>
106</tr>
107<tr>
108 <ti>(Not applicable)</ti>
109 <ti><path>/dev/hda2</path> (If using quik)</ti>
110 <ti><path>/dev/hda1</path></ti>
111 <ti>(Not applicable)</ti>
112 <ti>ext2</ti>
113 <ti>32MB</ti>
114 <ti>Boot partition</ti>
115</tr>
116<tr>
97 <ti><path>/dev/hda3</path></ti> 117 <ti><path>/dev/hda3</path></ti>
118 <ti><path>/dev/hda2</path>(<path>/dev/hda3</path> if using quik)</ti>
98 <ti><path>/dev/hda2</path></ti> 119 <ti><path>/dev/hda2</path></ti>
99 <ti><path>/dev/hda1</path></ti> 120 <ti><path>/dev/sda2</path></ti>
100 <ti>(swap)</ti> 121 <ti>(swap)</ti>
101 <ti>512M</ti> 122 <ti>512M</ti>
102 <ti>Swap partition</ti> 123 <ti>Swap partition, Type 0x82</ti>
103</tr> 124</tr>
104<tr> 125<tr>
105 <ti><path>/dev/hda4</path></ti> 126 <ti><path>/dev/hda4</path></ti>
127 <ti><path>/dev/hda3</path> (<path>/dev/hda4</path> if using quik)</ti>
106 <ti><path>/dev/hda3</path></ti> 128 <ti><path>/dev/hda3</path></ti>
107 <ti><path>/dev/hda2</path></ti> 129 <ti><path>/dev/sda3</path></ti>
108 <ti>ext3</ti> 130 <ti>ext3, xfs</ti>
109 <ti>Rest of the disk</ti> 131 <ti>Rest of the disk</ti>
110 <ti>Root partition</ti> 132 <ti>Root partition, Type 0x83</ti>
111</tr> 133</tr>
112</table> 134</table>
135
113<note> 136<note>
114There are some partitions named like this: <path>Apple_Driver43, 137There are some partitions named: <path>Apple_Driver43, Apple_Driver_ATA,
115Apple_Driver_ATA, Apple_FWDriver, Apple_Driver_IOKit, 138Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If you are not
116Apple_Patches</path>. If you are not planning to use MacOS 9 you can 139planning to use MacOS 9 you can delete them, because MacOS X and Linux don't
117delete them, because MacOS X and Linux don't need them. 140need them. To delete them, either use parted or erase the whole disk by
118You might have to use parted in order to delete them, as mac-fdisk can't delete them yet. 141initializing the partition map.
119</note> 142</note>
143
144<warn>
145<c>parted</c> is able to resize partitions including HFS+. Unfortunately it is
146not possible to resize HFS+ journaled filesystems, so switch off journaling in
147Mac OS X before resizing. Remeber that any resizing operation is dangerous,
148so attempt at your own risk! Be sure to always have a backup of your data
149before resizing!
150</warn>
151
120<p> 152<p>
121If you are interested in knowing how big a partition should be, or even how 153If you are interested in knowing how big a partition should be, or even how many
122many partitions you need, read on. Otherwise continue now with 154partitions you need, read on. Otherwise continue now with
123<uri link="#fdisk">Default: Using mac-fdisk (Apple/IBM) to Partition your 155<uri link="#mac-fdisk"> Default: Using mac-fdisk (Apple) to Partition your Disk
124Disk</uri> or <uri link="#parted">Alternative: Using parted (especially Pegasos) to 156</uri> or <uri link="#parted">Alternative: Using parted (IBM/Pegasos) to
125Partition your Disk</uri>. 157Partition your Disk</uri>.
126</p> 158</p>
127 159
128</body> 160</body>
129</subsection> 161</subsection>
133 165
134<p> 166<p>
135The number of partitions is highly dependent on your environment. For instance, 167The number of partitions is highly dependent on your environment. For instance,
136if you have lots of users, you will most likely want to have your 168if you have lots of users, you will most likely want to have your
137<path>/home</path> separate as it increases security and makes backups easier. 169<path>/home</path> separate as it increases security and makes backups easier.
138If you are installing Gentoo to perform as a mailserver, your 170If you are installing Gentoo to perform as a mailserver, your <path>/var</path>
139<path>/var</path> should be separate as all mails are stored inside 171should be separate as all mails are stored inside <path>/var</path>. A good
140<path>/var</path>. A good choice of filesystem will then maximise your 172choice of filesystem will then maximize your performance. Gameservers will have
141performance. Gameservers will have a separate <path>/opt</path> as most gaming 173a separate <path>/opt</path> as most gaming servers are installed there. The
142servers are installed there. The reason is similar for <path>/home</path>: 174reason is similar for <path>/home</path>: security and backups. You will
143security and backups. 175definitely want to keep <path>/usr</path> big: not only will it contain the
176majority of applications, the Portage tree alone takes around 500 MB
177excluding the various sources that are stored in it.
144</p> 178</p>
145 179
146<p> 180<p>
147As you can see, it very much depends on what you want to achieve. Separate 181As you can see, it very much depends on what you want to achieve. Separate
148partitions or volumes have the following advantages: 182partitions or volumes have the following advantages:
160 If necessary, file system checks are reduced in time, as multiple checks can 194 If necessary, file system checks are reduced in time, as multiple checks can
161 be done in parallel (although this advantage is more with multiple disks than 195 be done in parallel (although this advantage is more with multiple disks than
162 it is with multiple partitions) 196 it is with multiple partitions)
163</li> 197</li>
164<li> 198<li>
165 Security can be enhanced by mounting some partitions or volumes read-only, 199 Security can be enhanced by mounting some partitions or volumes read-only,
166 nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. 200 nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc.
167</li> 201</li>
168</ul> 202</ul>
169 203
170<p> 204<p>
171However, multiple partitions have one big disadvantage: if not configured 205However, multiple partitions have one big disadvantage: if not configured
172properly, you might result in having a system with lots 206properly, you might result in having a system with lots of free space on one
173of free space on one partition and none on another. There is also a 15-partition 207partition and none on another. There is also a 15-partition limit for SCSI and
174limit for SCSI and SATA. 208SATA.
175</p> 209</p>
176 210
177</body> 211</body>
178</subsection> 212</subsection>
179</section> 213</section>
180<section id="fdisk"> 214<section id="mac-fdisk">
181<title>Default: Using mac-fdisk (Apple/IBM) Partition your Disk</title> 215<title>Default: Using mac-fdisk (Apple) Partition your Disk</title>
182<body> 216<body>
183 217
184<p> 218<p>
185At this point, create your partitions using <c>mac-fdisk</c>: 219At this point, create your partitions using <c>mac-fdisk</c>:
186</p> 220</p>
190</pre> 224</pre>
191 225
192<p> 226<p>
193First delete the partitions you have cleared previously to make room for your 227First delete the partitions you have cleared previously to make room for your
194Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s). 228Linux partitions. Use <c>d</c> in <c>mac-fdisk</c> to delete those partition(s).
195It will ask for the partition number to delete. 229It will ask for the partition number to delete. The first partition on Apple
196</p> 230machines (Apple_partition_map) can not be deleted.
197
198<p> 231</p>
232
233<p>
199Second, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>. It will 234On NewWorld Macs, create an <e>Apple_Bootstrap</e> partition by using <c>b</c>.
200ask for what block you want to start. Enter the number of your first free 235It will ask for what block you want to start. Enter the number of your first
201partition, followed by a <c>p</c>. For instance this is <c>1p</c>. 236free partition, followed by a <c>p</c>. For instance this is <c>2p</c>.
202</p> 237</p>
203 238
204<note> 239<note>
205This partition is <e>not</e> a "boot" partition. It is not used by Linux at all; 240This partition is <e>not</e> a <path>/boot</path> partition. It is not used by
206you don't have to place any filesystem on it and you should never mount it. PPC 241Linux at all; you don't have to place any filesystem on it and you should never
207users don't need a an extra partition for <path>/boot</path>. 242mount it. Apple users don't need an extra partition for <path>/boot</path>.
208</note> 243</note>
209 244
210<p> 245<p>
211Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will 246Now create a swap partition by pressing <c>c</c>. Again <c>mac-fdisk</c> will
212ask for what block you want to start this partition from. As we used <c>1</c> 247ask for what block you want to start this partition from. As we used <c>2</c>
213before to create the Apple_Bootstrap partition, you now have to enter 248before to create the Apple_Bootstrap partition, you now have to enter
214<c>2p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size 249<c>3p</c>. When you're asked for the size, enter <c>512M</c> (or whatever size
215you want -- 512MB is recommended though). When asked for a name, enter <c>swap</c> 250you want -- 512MB is recommended though). When asked for a name, enter
216(mandatory). 251<c>swap</c> (mandatory).
217</p>
218
219<p> 252</p>
253
254<p>
220To create the root partition, enter <c>c</c>, followed by <c>3p</c> to select 255To create the root partition, enter <c>c</c>, followed by <c>4p</c> to select
221from what block the root partition should start. When asked for the size, enter 256from what block the root partition should start. When asked for the size, enter
222<c>3p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available 257<c>4p</c> again. <c>mac-fdisk</c> will interpret this as "Use all available
223space". When asked for the name, enter <c>root</c> (mandatory). 258space". When asked for the name, enter <c>root</c> (mandatory).
224</p> 259</p>
225 260
226<p> 261<p>
227To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to 262To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to
228quit <c>mac-fdisk</c>. 263quit <c>mac-fdisk</c>.
229</p> 264</p>
230 265
231<note> 266<note>
232To make sure everything is ok, you should run mac-fdisk once more and check whether all the partitions are there. 267To make sure everything is ok, you should run mac-fdisk once more and check
233If you don't see any of the partitions you created, or the changes you made, you should reinitialize your partitions by pressing "i" in mac-fdisk. 268whether all the partitions are there. If you don't see any of the partitions
234Note that this will recreate the partition map and thus remove all your partitions. 269you created, or the changes you made, you should reinitialize your partitions
270by pressing "i" in mac-fdisk. Note that this will recreate the partition map
271and thus remove all your partitions.
235</note> 272</note>
236 273
237<p> 274<p>
238Now that your partitions are created, you can now continue with <uri 275Now that your partitions are created, you can continue with <uri
239link="#filesystems">Creating Filesystems</uri>. 276link="#filesystems">Creating Filesystems</uri>.
240</p> 277</p>
241 278
242</body> 279</body>
243</section> 280</section>
244<section id="parted"> 281<section id="parted">
245<title>Using parted (especially Pegasos) to Partition your Disk</title> 282<title>Using parted (Mostly Pegasos) to Partition your Disk</title>
246<body> 283<body>
247 284
248<p> 285<p>
249<c>parted</c>, the Partition Editor, can now handle HFS+ partitions used by 286<c>parted</c>, the Partition Editor, can now handle HFS+ partitions used by
250Mac OS and Mac OS X. With this tool you can shrink your Mac-partitions and 287Mac OS and Mac OS X. With this tool you can resize your Mac-partitions and
251create space for your Linux partitions. Nevertheless, the example below 288create space for your Linux partitions. Nevertheless, the example below
252describes partitioning for Pegasos machines only. 289describes partitioning for Pegasos machines only.
253</p> 290</p>
254 291
255<p> 292<p>
259<pre caption="Starting parted"> 296<pre caption="Starting parted">
260# <i>parted /dev/hda</i> 297# <i>parted /dev/hda</i>
261</pre> 298</pre>
262 299
263<p> 300<p>
264If the drive is unpartitioned, run <c>mklabel amiga</c> to create a new 301If the drive isn't partitioned, run <c>mklabel amiga</c> to create a new
265disklabel for the drive. 302disklabel for the drive.
266</p> 303</p>
267 304
268<p> 305<p>
269You can type <c>print</c> at any time in parted to display the current partition 306You can type <c>print</c> at any time in parted to display the current partition
270table. Your changes aren't saved until you quit the application; if at any time 307table. If at any time you change your mind or made a mistake you can press
271you change your mind or made a mistake you can press <c>Ctrl-c</c> to abort 308<c>Ctrl-c</c> to abort parted.
272parted.
273</p> 309</p>
274 310
275<p> 311<p>
276If you intend to also install MorphOS on your Pegasos create an affs1 filesystem 312If you intend to also install MorphOS on your Pegasos create an affs1 filesystem
277named "BI0" (BI zero) at the start of the drive. 50MB should be more than enough 313named "BI0" (BI zero) at the start of the drive. 32MB should be more than enough
278to store the MorphOS kernel. If you have a Pegasos I or intend to use reiserfs or 314to store the MorphOS kernel. If you have a Pegasos I or intend to use reiserfs
279xfs, you will also have to store your Linux kernel on this partition (the 315or xfs, you will also have to store your Linux kernel on this partition (the
280Pegasos II can boot from ext2/ext3 drives). To create the partition run 316Pegasos II can only boot from ext2/ext3 or affs1 partitions). To create the partition run
281<c>mkpart primary affs1 START END</c> where <c>START</c> and <c>END</c> should 317<c>mkpart primary affs1 START END</c> where <c>START</c> and <c>END</c> should
282be replaced with the megabyte range (f.i. <c>5 55</c> creates a 50 MB partition 318be replaced with the megabyte range (e.g. <c>0 32</c> creates a 32 MB partition
283starting at 5MB and ending at 55MB. 319starting at 0MB and ending at 32MB.
284</p> 320</p>
285 321
286<p> 322<p>
287You need to create two partitions for Linux, one root filesystem for all your 323You need to create two partitions for Linux, one root filesystem for all your
288program files etc, and one swap partition. To create the root filesystem you 324program files etc, and one swap partition. To create the root filesystem you
301partition, run <c>mkpart primary linux-swap START END</c>. 337partition, run <c>mkpart primary linux-swap START END</c>.
302</p> 338</p>
303 339
304<p> 340<p>
305Write down the partition minor numbers as they are required during the 341Write down the partition minor numbers as they are required during the
306installation process. To dislay the minor numbers run <c>print</c>. Your drives 342installation process. To display the minor numbers run <c>print</c>. Your drives
307are accessed as <path>/dev/hdaX</path> where X is replaced with the minor number 343are accessed as <path>/dev/hdaX</path> where X is replaced with the minor number
308of the partition. 344of the partition.
309</p> 345</p>
310 346
311<p> 347<p>
319<subsection> 355<subsection>
320<title>Introduction</title> 356<title>Introduction</title>
321<body> 357<body>
322 358
323<p> 359<p>
324Now that your partitions are created, it is time to place a filesystem on them. 360Now that your partitions are created, it is time to place a filesystem on them.
325If you don't care about what filesystem to choose and are happy with what we use 361If you don't care about what filesystem to choose and are happy with what we use
326as default in this handbook, continue with <uri 362as default in this handbook, continue with <uri
327link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. 363 link="#filesystems-apply">Applying a Filesystem to a Partition</uri>.
328Otherwise read on to learn about the available filesystems... 364Otherwise read on to learn about the available filesystems...
329</p> 365</p>
330 366
331</body> 367</body>
332</subsection> 368</subsection>
333<subsection> 369<subsection>
334<title>Filesystems?</title> 370<title>Filesystems?</title>
335<body> 371<body>
336 372
337<p> 373<p>
338Several filesystems are available. ext2, ext3, reiserfs and xfs are found stable 374Several filesystems are available. ext2, ext3, ReiserFS and XFS have been found
339on the PPC architecture. jfs is unsupported. 375stable on the PPC architecture.
340</p> 376</p>
341 377
342<p> 378<p>
343<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata 379<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
344journaling, which means that routine ext2 filesystem checks at startup time can 380journaling, which means that routine ext2 filesystem checks at startup time can
352<p> 388<p>
353<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata 389<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
354journaling for fast recovery in addition to other enhanced journaling modes like 390journaling for fast recovery in addition to other enhanced journaling modes like
355full data and ordered data journaling. ext3 is a very good and reliable 391full data and ordered data journaling. ext3 is a very good and reliable
356filesystem. It has an additional hashed b-tree indexing option that enables 392filesystem. It has an additional hashed b-tree indexing option that enables
357high performance in almost all situations. In short, ext3 is an excellent 393high performance in almost all situations. You can enable this indexing by
358filesystem. 394adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an
395excellent filesystem.
359</p> 396</p>
360 397
361<p> 398<p>
362<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall 399<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall
363performance and greatly outperforms both ext2 and ext3 when dealing with small 400performance and greatly outperforms both ext2 and ext3 when dealing with small
394 <th>Filesystem</th> 431 <th>Filesystem</th>
395 <th>Creation Command</th> 432 <th>Creation Command</th>
396</tr> 433</tr>
397<tr> 434<tr>
398 <ti>ext2</ti> 435 <ti>ext2</ti>
399 <ti><c>mke2fs</c></ti> 436 <ti><c>mkfs.ext2</c></ti>
400</tr> 437</tr>
401<tr> 438<tr>
402 <ti>ext3</ti> 439 <ti>ext3</ti>
403 <ti><c>mke2fs -j</c></ti> 440 <ti><c>mkfs.ext3</c></ti>
404</tr> 441</tr>
405<tr> 442<tr>
406 <ti>reiserfs</ti> 443 <ti>reiserfs</ti>
407 <ti><c>mkreiserfs</c></ti> 444 <ti><c>mkfs.reiserfs</c></ti>
408</tr> 445</tr>
409<tr> 446<tr>
410 <ti>xfs</ti> 447 <ti>xfs</ti>
411 <ti><c>mkfs.xfs</c></ti> 448 <ti><c>mkfs.xfs</c></ti>
412</tr> 449</tr>
413</table> 450</table>
414 451
415<p> 452<p>
416For instance, to have the root partition (<path>/dev/hda3</path> in our example) 453For instance, to have the root partition (<path>/dev/hda4</path> in our example)
417in ext3 (as in our example), you would use: 454in ext3 (as in our example), you would use:
418</p> 455</p>
419 456
420<pre caption="Applying a filesystem on a partition"> 457<pre caption="Applying a filesystem on a partition">
421# <i>mke2fs -j /dev/hda3</i> 458# <i>mkfs.ext3 /dev/hda4</i>
422</pre> 459</pre>
423 460
424<p> 461<p>
425Now create the filesystems on your newly created partitions (or logical 462Now create the filesystems on your newly created partitions (or logical
426volumes). 463volumes).
427</p> 464</p>
428 465
429<note> 466<note>
430Be sure that the partition which will host your kernel (the 467On the PegasosII your partition which holds the kernel must be ext2 or ext3.
431<path>/boot</path>-path) must be ext2 or ext3. The bootloader can only handle 468NewWorld machines can boot from any of ext2, ext3, XFS, ReiserFS or even
432this filesystem. 469HFS/HFS+ filesystems. On OldWorld machines booting with BootX, the kernel must
470be placed on an HFS partition, but this will be completed when you configure
471your bootloader.
433</note> 472</note>
434 473
435</body> 474</body>
436</subsection> 475</subsection>
437<subsection> 476<subsection>
441<p> 480<p>
442<c>mkswap</c> is the command that is used to initialize swap partitions: 481<c>mkswap</c> is the command that is used to initialize swap partitions:
443</p> 482</p>
444 483
445<pre caption="Creating a Swap signature"> 484<pre caption="Creating a Swap signature">
446# <i>mkswap /dev/hda2</i> 485# <i>mkswap /dev/hda3</i>
447</pre> 486</pre>
448 487
449<p> 488<p>
450To activate the swap partition, use <c>swapon</c>: 489To activate the swap partition, use <c>swapon</c>:
451</p> 490</p>
452 491
453<pre caption="Activating the swap partition"> 492<pre caption="Activating the swap partition">
454# <i>swapon /dev/hda2</i> 493# <i>swapon /dev/hda3</i>
455</pre> 494</pre>
456 495
457<p> 496<p>
458Create and activate the swap now. 497Create and activate the swap now.
459</p> 498</p>
467 506
468<p> 507<p>
469Now that your partitions are initialized and are housing a filesystem, it is 508Now that your partitions are initialized and are housing a filesystem, it is
470time to mount those partitions. Use the <c>mount</c> command. Don't forget to 509time to mount those partitions. Use the <c>mount</c> command. Don't forget to
471create the necessary mount directories for every partition you created. As an 510create the necessary mount directories for every partition you created. As an
472example we create a mount-point and mount the root and boot partition: 511example we create a mount-point and mount the root partition:
473</p> 512</p>
474 513
475<pre caption="Mounting partitions"> 514<pre caption="Mounting partitions">
476# <i>mkdir /mnt/gentoo</i> 515# <i>mkdir /mnt/gentoo</i>
477# <i>mount /dev/hda3 /mnt/gentoo</i> 516# <i>mount /dev/hda4 /mnt/gentoo</i>
478</pre> 517</pre>
479 518
480<note> 519<note>
481If you want your <path>/tmp</path> to reside on a separate partition, be sure to 520If you want your <path>/tmp</path> to reside on a separate partition, be sure to
482change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This 521change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This
483also holds for <path>/var/tmp</path>. 522also holds for <path>/var/tmp</path>.
484</note> 523</note>
485 524
486<p> 525<p>
487Finally we have to create the <path>/dev</path> files in our new home, which is
488needed during the bootloader installation. This could be done by "bind"-mapping
489the <path>/dev</path>-filesystem from the LiveCD:
490</p>
491
492<pre caption="Bind-mounting the /dev-filesystem">
493# <i>mkdir /mnt/gentoo/dev</i>
494# <i>mount -o bind /dev /mnt/gentoo/dev</i>
495</pre>
496
497<p>
498We will also have to mount the proc filesystem (a virtual interface with the 526We will have to mount the proc filesystem (a virtual interface with the
499kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. 527kernel) on <path>/proc</path>. But first we will need to place our files on the
528partitions.
500</p> 529</p>
501 530
502<p> 531<p>
503Continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo 532Continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo
504Installation Files</uri>. 533Installation Files</uri>.

Legend:
Removed from v.1.20  
changed lines
  Added in v.1.34

  ViewVC Help
Powered by ViewVC 1.1.20