| … | |
… | |
| 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/2.5 --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 6 | |
6 | |
| 7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-disk.xml,v 1.30 2009/02/15 06:48:11 rane Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-disk.xml,v 1.32 2011/10/17 19:51:45 swift Exp $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | |
10 | |
| 11 | <version>9.1</version> |
11 | <version>11</version> |
| 12 | <date>2009-02-15</date> |
12 | <date>2011-10-17</date> |
| 13 | |
13 | |
| 14 | <section> |
14 | <section> |
| 15 | <title>Introduction to Block Devices</title> |
15 | <title>Introduction to Block Devices</title> |
| 16 | |
16 | |
| 17 | <subsection> |
17 | <subsection> |
| … | |
… | |
| 113 | nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
113 | nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
| 114 | </li> |
114 | </li> |
| 115 | </ul> |
115 | </ul> |
| 116 | |
116 | |
| 117 | <p> |
117 | <p> |
| 118 | However, multiple partitions have one big disadvantage: if not configured |
118 | However, multiple partitions have disadvantages as well. If not configured |
| 119 | properly, you might result in having a system with lots |
119 | properly, you will have a system with lots of free space on one partition and |
| 120 | of free space on one partition and none on another. |
120 | none on another. Another nuisance is that separate partitions - especially |
|
|
121 | for important mountpoints like <path>/usr</path> or <path>/var</path> - often |
|
|
122 | require the administrator to boot with an initramfs to mount the partition |
|
|
123 | before other boot scripts start. This isn't always the case though, so YMMV. |
| 121 | </p> |
124 | </p> |
| 122 | |
125 | |
| 123 | </body> |
126 | </body> |
| 124 | </subsection> |
127 | </subsection> |
| 125 | </section> |
128 | </section> |
| … | |
… | |
| 632 | <th>Filesystem</th> |
635 | <th>Filesystem</th> |
| 633 | <th>Creation Command</th> |
636 | <th>Creation Command</th> |
| 634 | </tr> |
637 | </tr> |
| 635 | <tr> |
638 | <tr> |
| 636 | <ti>ext2</ti> |
639 | <ti>ext2</ti> |
| 637 | <ti><c>mke2fs</c></ti> |
640 | <ti><c>mkfs.ext2</c></ti> |
| 638 | </tr> |
641 | </tr> |
| 639 | <tr> |
642 | <tr> |
| 640 | <ti>ext3</ti> |
643 | <ti>ext3</ti> |
| 641 | <ti><c>mke2fs -j</c></ti> |
644 | <ti><c>mkfs.ext3</c></ti> |
|
|
645 | </tr> |
|
|
646 | <tr> |
|
|
647 | <ti>ext4</ti> |
|
|
648 | <ti><c>mkfs.ext4</c></ti> |
| 642 | </tr> |
649 | </tr> |
| 643 | <tr> |
650 | <tr> |
| 644 | <ti>reiserfs</ti> |
651 | <ti>reiserfs</ti> |
| 645 | <ti><c>mkreiserfs</c></ti> |
652 | <ti><c>mkfs.reiserfs</c></ti> |
| 646 | </tr> |
653 | </tr> |
| 647 | <tr> |
654 | <tr> |
| 648 | <ti>xfs</ti> |
655 | <ti>xfs</ti> |
| 649 | <ti><c>mkfs.xfs</c></ti> |
656 | <ti><c>mkfs.xfs</c></ti> |
| 650 | </tr> |
657 | </tr> |
| … | |
… | |
| 658 | For instance, to have the root partition (<path>/dev/sda2</path> in our example) |
665 | For instance, to have the root partition (<path>/dev/sda2</path> in our example) |
| 659 | in ext3, you would use: |
666 | in ext3, you would use: |
| 660 | </p> |
667 | </p> |
| 661 | |
668 | |
| 662 | <pre caption="Applying a filesystem on a partition"> |
669 | <pre caption="Applying a filesystem on a partition"> |
| 663 | # <i>mke2fs -j /dev/sda2</i> |
670 | # <i>mkfs.ext3 /dev/sda2</i> |
| 664 | </pre> |
671 | </pre> |
| 665 | |
672 | |
| 666 | <p> |
673 | <p> |
| 667 | Now create the filesystems on your newly created partitions (or logical |
674 | Now create the filesystems on your newly created partitions (or logical |
| 668 | volumes). |
675 | volumes). |