/[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.12 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.12 2004/08/02 15:54:00 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
11<version>2.5</version>
12<date>2006-02-27</date>
13
10<section> 14<section>
11<title>Introduction to Block Devices</title> 15<title>Introduction to Block Devices</title>
12<subsection> 16<subsection>
13<title>Block Devices</title> 17<title>Block Devices</title>
14<body> 18<body>
20you'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
21for your Gentoo Linux installation. 25for your Gentoo Linux installation.
22</p> 26</p>
23 27
24<p> 28<p>
25To 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
26probably 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
27<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
28drive would be <path>/dev/sda</path>. 32drives, then your first hard drive would be <path>/dev/sda</path>.
29</p> 33</p>
30 34
31<p> 35<p>
32The block devices above represent an abstract interface to the disk. User 36The block devices above represent an abstract interface to the disk. User
33programs 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
37</p> 41</p>
38 42
39</body> 43</body>
40</subsection> 44</subsection>
41<subsection> 45<subsection>
42<title>Partitions and Slices</title> 46<title>Partitions</title>
43<body> 47<body>
44 48
45<p> 49<p>
46Although 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
47system, 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
48are split up in smaller, more manageable block devices. On most systems, 52are split up in smaller, more manageable block devices. On most systems,
49these are called <e>partitions</e>. Other architectures use a similar technique, 53these are called <e>partitions</e>.
50called <e>slices</e>.
51</p> 54</p>
52 55
53</body> 56</body>
54</subsection> 57</subsection>
55</section> 58</section>
67<table> 70<table>
68<tr> 71<tr>
69 <th>Partition NewWorld</th> 72 <th>Partition NewWorld</th>
70 <th>Partition OldWorld</th> 73 <th>Partition OldWorld</th>
71 <th>Partition Pegasos</th> 74 <th>Partition Pegasos</th>
75 <th>Partition RS/6000</th>
72 <th>Filesystem</th> 76 <th>Filesystem</th>
73 <th>Size</th> 77 <th>Size</th>
74 <th>Description</th> 78 <th>Description</th>
75</tr> 79</tr>
76<tr> 80<tr>
77 <ti><path>/dev/hda1</path></ti> 81 <ti><path>/dev/hda1</path></ti>
78 <ti>(Not needed)</ti> 82 <ti><path>/dev/hda1</path></ti>
83 <ti>(Not applicable)</ti>
84 <ti>(Not applicable)</ti>
85 <ti>(Partition Map)</ti>
86 <ti>32k</ti>
87 <ti>Apple_partition_map</ti>
88</tr>
89<tr>
90 <ti><path>/dev/hda2</path></ti>
91 <ti>(Not applicable)</ti>
92 <ti>(Not applicable)</ti>
79 <ti>(Not applicable)</ti> 93 <ti>(Not applicable)</ti>
80 <ti>(bootstrap)</ti> 94 <ti>(bootstrap)</ti>
81 <ti>800k</ti> 95 <ti>800k</ti>
82 <ti>Apple_Bootstrap</ti> 96 <ti>Apple_Bootstrap</ti>
83</tr> 97</tr>
84<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>
117 <ti><path>/dev/hda3</path></ti>
118 <ti><path>/dev/hda2</path>(<path>/dev/hda3</path> if using quik)</ti>
85 <ti><path>/dev/hda2</path></ti> 119 <ti><path>/dev/hda2</path></ti>
86 <ti><path>/dev/hda1</path></ti> 120 <ti><path>/dev/sda2</path></ti>
87 <ti><path>/dev/hda1</path></ti>
88 <ti>(swap)</ti> 121 <ti>(swap)</ti>
89 <ti>512M</ti> 122 <ti>512M</ti>
90 <ti>Swap partition</ti> 123 <ti>Swap partition, Type 0x82</ti>
91</tr>
92<tr> 124</tr>
125<tr>
126 <ti><path>/dev/hda4</path></ti>
127 <ti><path>/dev/hda3</path> (<path>/dev/hda4</path> if using quik)</ti>
93 <ti><path>/dev/hda3</path></ti> 128 <ti><path>/dev/hda3</path></ti>
94 <ti><path>/dev/hda2</path></ti> 129 <ti><path>/dev/sda3</path></ti>
95 <ti><path>/dev/hda2</path></ti>
96 <ti>ext3</ti> 130 <ti>ext3, xfs</ti>
97 <ti>Rest of the disk</ti> 131 <ti>Rest of the disk</ti>
98 <ti>Root partition</ti> 132 <ti>Root partition, Type 0x83</ti>
99</tr> 133</tr>
100</table> 134</table>
101 135
136<note>
137There are some partitions named: <path>Apple_Driver43, Apple_Driver_ATA,
138Apple_FWDriver, Apple_Driver_IOKit, Apple_Patches</path>. If you are not
139planning to use MacOS 9 you can delete them, because MacOS X and Linux don't
140need them. To delete them, either use parted or erase the whole disk by
141initializing the partition map.
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
102<p> 152<p>
103If 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
104many partitions you need, read on. Otherwise continue now with 154partitions you need, read on. Otherwise continue now with
105<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
106Disk</uri> or <uri link="#parted">Alternative: Using parted (especially Pegasos) to 156</uri> or <uri link="#parted">Alternative: Using parted (IBM/Pegasos) to
107Partition your Disk</uri>. 157Partition your Disk</uri>.
108</p> 158</p>
109 159
110</body> 160</body>
111</subsection> 161</subsection>
115 165
116<p> 166<p>
117The number of partitions is highly dependent on your environment. For instance, 167The number of partitions is highly dependent on your environment. For instance,
118if 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
119<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.
120If you are installing Gentoo to perform as a mailserver, your 170If you are installing Gentoo to perform as a mailserver, your <path>/var</path>
121<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
122<path>/var</path>. A good choice of filesystem will then maximise your 172choice of filesystem will then maximize your performance. Gameservers will have
123performance. Gameservers will have a separate <path>/opt</path> as most gaming 173a separate <path>/opt</path> as most gaming servers are installed there. The
124servers are installed there. The reason is similar for <path>/home</path>: 174reason is similar for <path>/home</path>: security and backups. You will
125security 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.
126</p> 178</p>
127 179
128<p> 180<p>
129As 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
130partitions or volumes have the following advantages: 182partitions or volumes have the following advantages:
142 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
143 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
144 it is with multiple partitions) 196 it is with multiple partitions)
145</li> 197</li>
146<li> 198<li>
147 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,
148 nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. 200 nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc.
149</li> 201</li>
150</ul> 202</ul>
151 203
152<p> 204<p>
153However, multiple partitions have one big disadvantage: if not configured 205However, multiple partitions have one big disadvantage: if not configured
154properly, you might result in having a system with lots 206properly, you might result in having a system with lots of free space on one
155of free space on one partition and none on another. 207partition and none on another. There is also a 15-partition limit for SCSI and
208SATA.
156</p> 209</p>
157 210
158</body> 211</body>
159</subsection> 212</subsection>
160</section> 213</section>
161<section id="fdisk"> 214<section id="mac-fdisk">
162<title>Default: Using mac-fdisk (Apple/IBM) Partition your Disk</title> 215<title>Default: Using mac-fdisk (Apple) Partition your Disk</title>
163<body> 216<body>
164 217
165<p> 218<p>
166At this point, create your partitions using <c>mac-fdisk</c>: 219At this point, create your partitions using <c>mac-fdisk</c>:
167</p> 220</p>
171</pre> 224</pre>
172 225
173<p> 226<p>
174First 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
175Linux 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).
176It will ask for the partition number to delete. 229It will ask for the partition number to delete. The first partition on Apple
177</p> 230machines (Apple_partition_map) can not be deleted.
178
179<p> 231</p>
232
233<p>
180Second, 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>.
181ask 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
182partition, 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>.
183</p> 237</p>
184 238
185<note> 239<note>
186This 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
187you 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
188users 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>.
189</note> 243</note>
190 244
191<p> 245<p>
192Now 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
193ask 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>
194before to create the Apple_Bootstrap partition, you now have to enter 248before to create the Apple_Bootstrap partition, you now have to enter
195<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
196you 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
197(mandatory). 251<c>swap</c> (mandatory).
198</p>
199
200<p> 252</p>
253
254<p>
201To 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
202from 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
203<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
204space". When asked for the name, enter <c>root</c> (mandatory). 258space". When asked for the name, enter <c>root</c> (mandatory).
205</p> 259</p>
206 260
207<p> 261<p>
208To 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
209quit <c>mac-fdisk</c>. 263quit <c>mac-fdisk</c>.
210</p> 264</p>
211 265
266<note>
267To make sure everything is ok, you should run mac-fdisk once more and check
268whether all the partitions are there. If you don't see any of the 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.
272</note>
273
212<p> 274<p>
213Now that your partitions are created, you can now continue with <uri 275Now that your partitions are created, you can continue with <uri
214link="#filesystems">Creating Filesystems</uri>. 276link="#filesystems">Creating Filesystems</uri>.
215</p> 277</p>
216 278
217</body> 279</body>
218</section> 280</section>
219<section id="parted"> 281<section id="parted">
220<title>Using parted (especially Pegasos) to Partition your Disk</title> 282<title>Using parted (Mostly Pegasos) to Partition your Disk</title>
221<body> 283<body>
222 284
223<p> 285<p>
224<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
225Mac 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
226create space for your Linux partitions. Nevertheless, the example below 288create space for your Linux partitions. Nevertheless, the example below
227describes partitioning for Pegasos machines only. 289describes partitioning for Pegasos machines only.
228</p> 290</p>
229 291
230<p> 292<p>
234<pre caption="Starting parted"> 296<pre caption="Starting parted">
235# <i>parted /dev/hda</i> 297# <i>parted /dev/hda</i>
236</pre> 298</pre>
237 299
238<p> 300<p>
239If 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
240disklabel for the drive. 302disklabel for the drive.
241</p> 303</p>
242 304
243<p> 305<p>
244You 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
245table. 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
246you change your mind or made a mistake you can press <c>Ctrl-c</c> to abort 308<c>Ctrl-c</c> to abort parted.
247parted.
248</p> 309</p>
249 310
250<p> 311<p>
251If 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
252named "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
253to store the MorphOS kernel. If you have a Pegasos I or intend to use reiserfs, 314to store the MorphOS kernel. If you have a Pegasos I or intend to use reiserfs
254xfs or jfs 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
255Pegasos 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
256<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
257be 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
258starting at 5MB and ending at 55MB. 319starting at 0MB and ending at 32MB.
259</p> 320</p>
260 321
261<p> 322<p>
262You 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
263program 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
264must first decide which filesystem to use. Possible options are ext2, ext3, 325must first decide which filesystem to use. Possible options are ext2, ext3,
265reiserfs, jfs and xfs. Unless you know what you are doing, use ext3. Run 326reiserfs and xfs. Unless you know what you are doing, use ext3. Run
266<c>mkpart primary ext3 START END</c> to create an ext3 partition. Again, replace 327<c>mkpart primary ext3 START END</c> to create an ext3 partition. Again, replace
267<c>START</c> and <c>END</c> with the megabyte start and stop marks for the 328<c>START</c> and <c>END</c> with the megabyte start and stop marks for the
268partition. 329partition.
269</p> 330</p>
270 331
276partition, run <c>mkpart primary linux-swap START END</c>. 337partition, run <c>mkpart primary linux-swap START END</c>.
277</p> 338</p>
278 339
279<p> 340<p>
280Write down the partition minor numbers as they are required during the 341Write down the partition minor numbers as they are required during the
281installation 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
282are 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
283of the partition. 344of the partition.
284</p> 345</p>
285 346
286<p> 347<p>
294<subsection> 355<subsection>
295<title>Introduction</title> 356<title>Introduction</title>
296<body> 357<body>
297 358
298<p> 359<p>
299Now 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.
300If 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
301as default in this handbook, continue with <uri 362as default in this handbook, continue with <uri
302link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. 363 link="#filesystems-apply">Applying a Filesystem to a Partition</uri>.
303Otherwise read on to learn about the available filesystems... 364Otherwise read on to learn about the available filesystems...
304</p> 365</p>
305 366
306</body> 367</body>
307</subsection> 368</subsection>
308<subsection> 369<subsection>
309<title>Filesystems?</title> 370<title>Filesystems?</title>
310<body> 371<body>
311 372
312<p> 373<p>
313Several filesystems are available. ext2 and ext3 are found stable on the 374Several filesystems are available. ext2, ext3, ReiserFS and XFS have been found
314PPC architecture, reiserfs and xfs are in testing stage, though we did not 375stable on the PPC architecture.
315encountered any serious errors with the 2.6 Linux kernel. jfs is
316unsupported.
317</p> 376</p>
318 377
319<p> 378<p>
320<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
321journaling, which means that routine ext2 filesystem checks at startup time can 380journaling, which means that routine ext2 filesystem checks at startup time can
329<p> 388<p>
330<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
331journaling for fast recovery in addition to other enhanced journaling modes like 390journaling for fast recovery in addition to other enhanced journaling modes like
332full 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
333filesystem. It has an additional hashed b-tree indexing option that enables 392filesystem. It has an additional hashed b-tree indexing option that enables
334high performance in almost all situations. In short, ext3 is an excellent 393high performance in almost all situations. You can enable this indexing by
335filesystem. 394adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an
395excellent filesystem.
336</p> 396</p>
337 397
338<p> 398<p>
339<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
340performance and greatly outperforms both ext2 and ext3 when dealing with small 400performance and greatly outperforms both ext2 and ext3 when dealing with small
353in RAM, improperly designed programs (those that don't take proper precautions 413in RAM, improperly designed programs (those that don't take proper precautions
354when writing files to disk and there are quite a few of them) can lose a good 414when writing files to disk and there are quite a few of them) can lose a good
355deal of data if the system goes down unexpectedly. 415deal of data if the system goes down unexpectedly.
356</p> 416</p>
357 417
358<p>
359<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
360become production-ready and there hasn't been a sufficient track record to
361comment positively nor negatively on its general stability at this point.
362</p>
363
364</body> 418</body>
365</subsection> 419</subsection>
366<subsection id="filesystems-apply"> 420<subsection id="filesystems-apply">
367<title>Applying a Filesystem to a Partition</title> 421<title>Applying a Filesystem to a Partition</title>
368<body> 422<body>
377 <th>Filesystem</th> 431 <th>Filesystem</th>
378 <th>Creation Command</th> 432 <th>Creation Command</th>
379</tr> 433</tr>
380<tr> 434<tr>
381 <ti>ext2</ti> 435 <ti>ext2</ti>
382 <ti><c>mke2fs</c></ti> 436 <ti><c>mkfs.ext2</c></ti>
383</tr> 437</tr>
384<tr> 438<tr>
385 <ti>ext3</ti> 439 <ti>ext3</ti>
386 <ti><c>mke2fs -j</c></ti> 440 <ti><c>mkfs.ext3</c></ti>
387</tr> 441</tr>
388<tr> 442<tr>
389 <ti>reiserfs</ti> 443 <ti>reiserfs</ti>
390 <ti><c>mkreiserfs</c></ti> 444 <ti><c>mkfs.reiserfs</c></ti>
391</tr> 445</tr>
392<tr> 446<tr>
393 <ti>xfs</ti> 447 <ti>xfs</ti>
394 <ti><c>mkfs.xfs</c></ti> 448 <ti><c>mkfs.xfs</c></ti>
395</tr> 449</tr>
396<tr>
397 <ti>jfs</ti>
398 <ti><c>mkfs.jfs</c></ti>
399</tr>
400</table> 450</table>
401 451
402<p> 452<p>
403For 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)
404in ext3 (as in our example), you would use: 454in ext3 (as in our example), you would use:
405</p> 455</p>
406 456
407<pre caption="Applying a filesystem on a partition"> 457<pre caption="Applying a filesystem on a partition">
408# <i>mke2fs -j /dev/hda3</i> 458# <i>mkfs.ext3 /dev/hda4</i>
409</pre> 459</pre>
410 460
411<p> 461<p>
412Now create the filesystems on your newly created partitions (or logical 462Now create the filesystems on your newly created partitions (or logical
413volumes). 463volumes).
414</p> 464</p>
415 465
416<note> 466<note>
417Be sure that the partition which will host your kernel (the 467On the PegasosII your partition which holds the kernel must be ext2 or ext3.
418<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
419this 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.
420</note> 472</note>
421 473
422</body> 474</body>
423</subsection> 475</subsection>
424<subsection> 476<subsection>
428<p> 480<p>
429<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:
430</p> 482</p>
431 483
432<pre caption="Creating a Swap signature"> 484<pre caption="Creating a Swap signature">
433# <i>mkswap /dev/hda2</i> 485# <i>mkswap /dev/hda3</i>
434</pre> 486</pre>
435 487
436<p> 488<p>
437To activate the swap partition, use <c>swapon</c>: 489To activate the swap partition, use <c>swapon</c>:
438</p> 490</p>
439 491
440<pre caption="Activating the swap partition"> 492<pre caption="Activating the swap partition">
441# <i>swapon /dev/hda2</i> 493# <i>swapon /dev/hda3</i>
442</pre> 494</pre>
443 495
444<p> 496<p>
445Create and activate the swap now. 497Create and activate the swap now.
446</p> 498</p>
454 506
455<p> 507<p>
456Now 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
457time 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
458create the necessary mount directories for every partition you created. As an 510create the necessary mount directories for every partition you created. As an
459example we create a mount-point and mount the root and boot partition: 511example we create a mount-point and mount the root partition:
460</p> 512</p>
461 513
462<pre caption="Mounting partitions"> 514<pre caption="Mounting partitions">
463# <i>mkdir /mnt/gentoo</i> 515# <i>mkdir /mnt/gentoo</i>
464# <i>mount /dev/hda3 /mnt/gentoo</i> 516# <i>mount /dev/hda4 /mnt/gentoo</i>
465</pre> 517</pre>
466 518
467<note> 519<note>
468If 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
469change 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
470also holds for <path>/var/tmp</path>. 522also holds for <path>/var/tmp</path>.
471</note> 523</note>
472 524
473<p> 525<p>
474Finally we have to create the <path>/dev</path> files in our new home, which is
475needed during the bootloader installation. This could be done by "bind"-mapping
476the <path>/dev</path>-filesystem from the LiveCD:
477</p>
478
479<pre caption="Bind-mounting the /dev-filesystem">
480# <i>mkdir /mnt/gentoo/dev</i>
481# <i>mount -o bind /dev /mnt/gentoo/dev</i>
482</pre>
483
484<p>
485We 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
486kernel) 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.
487</p> 529</p>
488 530
489<p> 531<p>
490Continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo 532Continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo
491Installation Files</uri>. 533Installation Files</uri>.

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

  ViewVC Help
Powered by ViewVC 1.1.20