| … | |
… | |
| 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/1.0 --> |
| 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.25 2004/12/12 11:10:46 sejo Exp $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | |
10 | |
| 11 | <version>1.19</version> |
11 | <version>1.21</version> |
| 12 | <date>2004-11-02</date> |
12 | <date>2004-12-12</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> |
| … | |
… | |
| 337 | <subsection> |
337 | <subsection> |
| 338 | <title>Filesystems?</title> |
338 | <title>Filesystems?</title> |
| 339 | <body> |
339 | <body> |
| 340 | |
340 | |
| 341 | <p> |
341 | <p> |
| 342 | Several filesystems are available. ext2, ext3, ReiserFS and XFS are found stable |
342 | Several filesystems are available. ext2, ext3 and XFS are found stable |
| 343 | on the PPC architecture. jfs is unsupported. |
343 | on the PPC architecture. jfs is unsupported, ReiserFS still has some problems on ppc and is not supported. |
| 344 | </p> |
344 | </p> |
| 345 | |
345 | |
| 346 | <p> |
346 | <p> |
| 347 | <b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
347 | <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 |
348 | journaling, which means that routine ext2 filesystem checks at startup time can |
| … | |
… | |
| 367 | performance and greatly outperforms both ext2 and ext3 when dealing with small |
367 | performance and greatly outperforms both ext2 and ext3 when dealing with small |
| 368 | files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
368 | files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
| 369 | extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
369 | extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is |
| 370 | solid and usable as both general-purpose filesystem and for extreme cases such |
370 | solid and usable as both general-purpose filesystem and for extreme cases such |
| 371 | as the creation of large filesystems, the use of many small files, very large |
371 | as the creation of large filesystems, the use of many small files, very large |
| 372 | files and directories containing tens of thousands of files. |
372 | files and directories containing tens of thousands of files. Unfortunately we still have some |
|
|
373 | issues with ReiserFS on ppc. We do not encourage people to use this filesystem. |
| 373 | </p> |
374 | </p> |
| 374 | |
375 | |
| 375 | <p> |
376 | <p> |
| 376 | <b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
377 | <b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
| 377 | feature-set and is optimized for scalability. We only recommend using this |
378 | feature-set and is optimized for scalability. We only recommend using this |
| … | |
… | |
| 485 | If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
486 | 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 |
487 | change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
| 487 | also holds for <path>/var/tmp</path>. |
488 | also holds for <path>/var/tmp</path>. |
| 488 | </note> |
489 | </note> |
| 489 | |
490 | |
| 490 | <p> |
491 | |
| 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> |
492 | <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 |
493 | 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 |
494 | kernel) on <path>/proc</path>. But first we will need to place our files on the |
| 504 | partitions. |
495 | partitions. |
| 505 | </p> |
496 | </p> |
| 506 | |
497 | |
| 507 | <p> |
498 | <p> |
Parent Directory
| 
Revision Log
| 
Patch