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