|
Lines 4-15
Link Here
|
| 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.15 2005/08/02 08:03:53 swift Exp $ --> |
7 |
<!-- $Header: /var/cvsroot/gentoo-doc/en/handbook/hb-install-mips-disk.xml,v 1.24 2005/07/25 13:58:58 stuartl Exp $ --> |
| 8 |
|
8 |
|
| 9 |
<sections> |
9 |
<sections> |
| 10 |
|
10 |
|
| 11 |
<version>1.10</version> |
11 |
<version>1.10</version> |
| 12 |
<date>2005-08-02</date> |
12 |
<date>2005-07-25</date> |
| 13 |
|
13 |
|
| 14 |
<section> |
14 |
<section> |
| 15 |
<title>Introduction to Block Devices</title> |
15 |
<title>Introduction to Block Devices</title> |
|
Lines 124-136
Link Here
|
| 124 |
|
124 |
|
| 125 |
<ul> |
125 |
<ul> |
| 126 |
<li> |
126 |
<li> |
| 127 |
<!-- <e>SGI Volume Header</e> (9th partition): This partition is important. It |
|
|
| 128 |
is where the kernel images will go. To store kernel images, you will utilize |
| 129 |
the tool known as <c>dvhtool</c> to copy kernel images to this partition. |
| 130 |
You will then be able to boot kernels from this partition via the SGI PROM |
| 131 |
Monitor. --> |
| 132 |
<e>SGI Volume Header</e> (9th partition): This partition is important. It |
127 |
<e>SGI Volume Header</e> (9th partition): This partition is important. It |
| 133 |
is where the arcboot bootloader will go. |
128 |
is where the bootloader, and in some cases, will also contain the kernel |
|
|
129 |
images. |
| 134 |
</li> |
130 |
</li> |
| 135 |
<li> |
131 |
<li> |
| 136 |
<e>SGI Volume</e> (11th partition): This partition is similar in purpose to |
132 |
<e>SGI Volume</e> (11th partition): This partition is similar in purpose to |
|
Lines 203-224
Link Here
|
| 203 |
second is to overwrite the partition table with null data via the following |
199 |
second is to overwrite the partition table with null data via the following |
| 204 |
command: <c>dd if=/dev/zero of=/dev/sda bs=512 count=1</c>. |
200 |
command: <c>dd if=/dev/zero of=/dev/sda bs=512 count=1</c>. |
| 205 |
</note> |
201 |
</note> |
|
|
202 |
</body> |
| 203 |
</subsection> |
| 204 |
|
| 205 |
<subsection> |
| 206 |
<title>Getting the SGI Volume Header to just the right size</title> |
| 207 |
<body> |
| 206 |
|
208 |
|
| 207 |
<!-- This has been dropped in favour of using arcboot |
209 |
<impo> |
| 208 |
<p>Getting the SGI Volume Header to just the right size</p> |
210 |
This step is often needed, due to a bug in <c>fdisk</c>. For some reason, the |
|
|
211 |
volume header isn't created correctly, the end result being it starts and ends |
| 212 |
on cylinder 0. This prevents multiple partitions from being created. To get |
| 213 |
around this issue... read on. |
| 214 |
</impo> |
| 209 |
|
215 |
|
| 210 |
<p> |
216 |
<p> |
| 211 |
Now that an SGI Disklabel is created, partitions may now be defined. In the |
217 |
Now that an SGI Disklabel is created, partitions may now be defined. In the |
| 212 |
above example, there are already two partitions defined for you. These are the |
218 |
above example, there are already two partitions defined for you. These are the |
| 213 |
special partitions mentioned above and should not normally be altered. However, |
219 |
special partitions mentioned above and should not normally be altered. However, |
| 214 |
for installing Gentoo, we'll need to load multiple kernel images directly into |
220 |
for installing Gentoo, we'll need to load a bootloader, and possibly multiple |
| 215 |
the volume header, as there is no supported SGI Bootloader available in Portage |
221 |
kernel images (depending on system type) directly into the volume header. |
| 216 |
yet. The volume header itself can hold up to <e>eight</e> images of any size, |
222 |
The volume header itself can hold up to <e>eight</e> images of any size, |
| 217 |
with each image allowed eight-character names. |
223 |
with each image allowed eight-character names. |
| 218 |
</p> |
224 |
</p> |
| 219 |
|
225 |
|
| 220 |
<p> |
226 |
<p> |
| 221 |
The process of making the volume header larger isn't exactly straight-forward - - |
227 |
The process of making the volume header larger isn't exactly straight-forward; |
| 222 |
there's a bit of a trick to it. One cannot simply delete and re-add the volume |
228 |
there's a bit of a trick to it. One cannot simply delete and re-add the volume |
| 223 |
header due to odd fdisk behavior. In the example provided below, we'll create a |
229 |
header due to odd fdisk behavior. In the example provided below, we'll create a |
| 224 |
50MB Volume header in conjunction with a 50MB /boot partition. The actual layout |
230 |
50MB Volume header in conjunction with a 50MB /boot partition. The actual layout |
|
Lines 231-242
Link Here
|
| 231 |
First cylinder (5-8682, default 5): <i>51</i> |
237 |
First cylinder (5-8682, default 5): <i>51</i> |
| 232 |
Last cylinder (51-8682, default 8682): <i>101</i> |
238 |
Last cylinder (51-8682, default 8682): <i>101</i> |
| 233 |
|
239 |
|
| 234 |
<comment>(Notice how fdisk only allows Partition #1 to be re-created starting at a |
240 |
<comment>(Notice how fdisk only allows Partition #1 to be re-created starting at a ) |
| 235 |
minimum of cylinder 5? Had you attempted to delete & re-create the SGI |
241 |
(minimum of cylinder 5? Had you attempted to delete & re-create the SGI ) |
| 236 |
Volume Header this way, this is the same issue you would have encountered. |
242 |
(Volume Header this way, this is the same issue you would have encountered. ) |
| 237 |
In our example, we want /boot to be 50MB, so we start it at cylinder 51 (the |
243 |
(In our example, we want /boot to be 50MB, so we start it at cylinder 51 (the ) |
| 238 |
Volume Header needs to start at cylinder 0, remember?), and set its ending |
244 |
(Volume Header needs to start at cylinder 0, remember?), and set its ending ) |
| 239 |
cylinder to 101, which will roughly be 50MB (+/- 1-5MB).)</comment> |
245 |
(cylinder to 101, which will roughly be 50MB (+/- 1-5MB). )</comment> |
| 240 |
|
246 |
|
| 241 |
Command (m for help): <i>d</i> |
247 |
Command (m for help): <i>d</i> |
| 242 |
Partition number (1-16): <i>9</i> |
248 |
Partition number (1-16): <i>9</i> |
|
Lines 250-268
Link Here
|
| 250 |
|
256 |
|
| 251 |
<comment>(Re-Create Partition #9, ending just before Partition #1)</comment> |
257 |
<comment>(Re-Create Partition #9, ending just before Partition #1)</comment> |
| 252 |
</pre> |
258 |
</pre> |
| 253 |
--> |
259 |
|
| 254 |
<p> |
260 |
<p> |
| 255 |
If you're unsure how to use <c>fdisk</c> have a look down further at the |
261 |
If you're unsure how to use <c>fdisk</c> have a look down further at the |
| 256 |
instructions for partitioning on Cobalts. The concepts are exactly the same -- |
262 |
instructions for partitioning on Cobalts. The concepts are exactly the same -- |
| 257 |
just remember to leave the volume header and whole disk partitions alone. |
263 |
just remember to leave the volume header and whole disk partitions alone. |
| 258 |
</p> |
264 |
</p> |
| 259 |
|
265 |
|
| 260 |
<!-- <p> Perhaps part of the above commented-out block? |
266 |
<p> |
| 261 |
Once this is done, you are safe to create the rest of your partitions as you see |
267 |
Once this is done, you are safe to create the rest of your partitions as you see |
| 262 |
fit. After all your partitions are laid out, make sure you set the partition ID |
268 |
fit. After all your partitions are laid out, make sure you set the partition ID |
| 263 |
of your swap partition to <c>82</c>, which is Linux Swap. By default, it will be |
269 |
of your swap partition to <c>82</c>, which is Linux Swap. By default, it will be |
| 264 |
<c>83</c>, Linux Native. |
270 |
<c>83</c>, Linux Native. |
| 265 |
</p> --> |
271 |
</p> |
| 266 |
|
272 |
|
| 267 |
<p> |
273 |
<p> |
| 268 |
Now that your partitions are created, you can now continue with <uri |
274 |
Now that your partitions are created, you can now continue with <uri |
|
Lines 550-558
Link Here
|
| 550 |
journaling for fast recovery in addition to other enhanced journaling modes like |
556 |
journaling for fast recovery in addition to other enhanced journaling modes like |
| 551 |
full data and ordered data journaling. ext3 is a very good and reliable |
557 |
full data and ordered data journaling. ext3 is a very good and reliable |
| 552 |
filesystem. It has an additional hashed b-tree indexing option that enables |
558 |
filesystem. It has an additional hashed b-tree indexing option that enables |
| 553 |
high performance in almost all situations. You can enable this indexing by |
559 |
high performance in almost all situations. In short, ext3 is an excellent |
| 554 |
adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an |
560 |
filesystem. |
| 555 |
excellent filesystem. |
|
|
| 556 |
</p> |
561 |
</p> |
| 557 |
|
562 |
|
| 558 |
<p> |
563 |
<p> |
