| 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/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-mips-disk.xml,v 1.31 2011/10/17 19:51:45 swift Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml,v 1.32 2012/10/06 19:54:14 swift Exp $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | |
10 | |
| 11 | <abstract> |
11 | <abstract> |
| 12 | To be able to install Gentoo, you must create the necessary partitions. |
12 | To be able to install Gentoo, you must create the necessary partitions. |
| 13 | This chapter describes how to partition a disk for future usage. |
13 | This chapter describes how to partition a disk for future usage. |
| 14 | </abstract> |
14 | </abstract> |
| 15 | |
15 | |
| 16 | <version>7</version> |
16 | <version>6</version> |
| 17 | <date>2011-10-17</date> |
17 | <date>2012-10-06</date> |
| 18 | |
18 | |
| 19 | <section> |
19 | <section> |
| 20 | <title>Introduction to Block Devices</title> |
20 | <title>Introduction to Block Devices</title> |
| 21 | |
21 | |
| 22 | <subsection> |
22 | <subsection> |
| 23 | <include href="hb-install-blockdevices.xml"/> |
23 | <include href="hb-install-blockdevices.xml"/> |
| 24 | </subsection> |
24 | </subsection> |
| 25 | |
25 | |
| 26 | <subsection> |
26 | <subsection> |
| 27 | <title>Partitions</title> |
27 | <title>Partitions</title> |
| 28 | <body> |
28 | <body> |
| 29 | |
29 | |
| 30 | <p> |
30 | <p> |
| 31 | Although it is theoretically possible to use a full disk to house your Linux |
31 | Although it is theoretically possible to use a full disk to house your Linux |
| 32 | system, this is almost never done in practice. Instead, full disk block devices |
32 | system, this is almost never done in practice. Instead, full disk block devices |
| … | |
… | |
| 75 | be done in parallel (although this advantage is more with multiple disks than |
75 | be done in parallel (although this advantage is more with multiple disks than |
| 76 | it is with multiple partitions) |
76 | it is with multiple partitions) |
| 77 | </li> |
77 | </li> |
| 78 | <li> |
78 | <li> |
| 79 | Security can be enhanced by mounting some partitions or volumes read-only, |
79 | Security can be enhanced by mounting some partitions or volumes read-only, |
| 80 | nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
80 | nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
| 81 | </li> |
81 | </li> |
| 82 | </ul> |
82 | </ul> |
| 83 | |
83 | |
| 84 | <p> |
84 | <p> |
| 85 | However, multiple partitions have disadvantages as well. If not configured |
85 | However, multiple partitions have disadvantages as well. If not configured |
| 86 | properly, you will have a system with lots of free space on one partition and |
86 | properly, you will have a system with lots of free space on one partition and |
| 87 | none on another. Another nuisance is that separate partitions - especially |
87 | none on another. Another nuisance is that separate partitions - especially |
| 88 | for important mountpoints like <path>/usr</path> or <path>/var</path> - often |
88 | for important mountpoints like <path>/usr</path> or <path>/var</path> - often |
| 89 | require the administrator to boot with an initramfs to mount the partition |
89 | require the administrator to boot with an initramfs to mount the partition |
| 90 | before other boot scripts start. This isn't always the case though, so YMMV. |
90 | before other boot scripts start. This isn't always the case though, so your |
|
|
91 | results may vary. |
| 91 | </p> |
92 | </p> |
| 92 | |
93 | |
| 93 | <p> |
94 | <p> |
| 94 | There is also a 15-partition limit for SCSI and SATA. |
95 | There is also a 15-partition limit for SCSI and SATA. |
| 95 | </p> |
96 | </p> |
| 96 | |
97 | |
| 97 | </body> |
98 | </body> |
| 98 | </subsection> |
99 | </subsection> |
| 99 | </section> |
100 | </section> |
| 100 | <section> |
101 | <section> |
| 101 | <title>Using fdisk on MIPS to Partition your Disk</title> |
102 | <title>Using fdisk on MIPS to Partition your Disk</title> |
| 102 | <subsection> |
103 | <subsection> |
| 103 | <title>SGI Machines: Creating an SGI Disk Label</title> |
104 | <title>SGI Machines: Creating an SGI Disk Label</title> |
| 104 | <body> |
105 | <body> |
| 105 | |
106 | |