| 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-alpha-disk.xml,v 1.32 2011/10/17 19:51:45 swift Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-disk.xml,v 1.33 2012/10/06 19:54:14 swift Exp $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | |
10 | |
| 11 | <version>11</version> |
11 | <version>12</version> |
| 12 | <date>2011-10-17</date> |
12 | <date>2012-10-06</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> |
| 18 | <include href="hb-install-blockdevices.xml"/> |
18 | <include href="hb-install-blockdevices.xml"/> |
| 19 | </subsection> |
19 | </subsection> |
| 20 | |
20 | |
| 21 | <subsection> |
21 | <subsection> |
| 22 | <title>Slices</title> |
22 | <title>Slices</title> |
| 23 | <body> |
23 | <body> |
| 24 | |
24 | |
| 25 | <p> |
25 | <p> |
| 26 | Although it is theoretically possible to use a full disk to house your Linux |
26 | Although it is theoretically possible to use a full disk to house your Linux |
| 27 | system, this is almost never done in practice. Instead, full disk block devices |
27 | system, this is almost never done in practice. Instead, full disk block devices |
| … | |
… | |
| 108 | be done in parallel (although this advantage is more with multiple disks than |
108 | be done in parallel (although this advantage is more with multiple disks than |
| 109 | it is with multiple partitions) |
109 | it is with multiple partitions) |
| 110 | </li> |
110 | </li> |
| 111 | <li> |
111 | <li> |
| 112 | Security can be enhanced by mounting some partitions or volumes read-only, |
112 | Security can be enhanced by mounting some partitions or volumes read-only, |
| 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 disadvantages as well. If not configured |
118 | However, multiple partitions have disadvantages as well. If not configured |
| 119 | properly, you will have a system with lots of free space on one partition and |
119 | properly, you will have a system with lots of free space on one partition and |
| 120 | none on another. Another nuisance is that separate partitions - especially |
120 | none on another. Another nuisance is that separate partitions - especially |
| 121 | for important mountpoints like <path>/usr</path> or <path>/var</path> - often |
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 |
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. |
123 | before other boot scripts start. This isn't always the case though, so your |
|
|
124 | results may vary. |
| 124 | </p> |
125 | </p> |
| 125 | |
126 | |
| 126 | </body> |
127 | </body> |
| 127 | </subsection> |
128 | </subsection> |
| 128 | </section> |
129 | </section> |
| 129 | <section id="fdisk_SRM"> |
130 | <section id="fdisk_SRM"> |
| 130 | <title>Using fdisk to Partition your Disk (SRM only)</title> |
131 | <title>Using fdisk to Partition your Disk (SRM only)</title> |
| 131 | <subsection> |
132 | <subsection> |
| 132 | <body> |
133 | <body> |
| 133 | |
134 | |
| 134 | <p> |
135 | <p> |
| 135 | The following parts explain how to create the example slice layout described |
136 | The following parts explain how to create the example slice layout described |
| 136 | previously, namely: |
137 | previously, namely: |
| 137 | </p> |
138 | </p> |
| 138 | |
139 | |
Parent Directory
| 
Revision Log
| 
Patch