/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.15 Revision 1.16
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.15 2005/08/02 08:03:53 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml,v 1.16 2005/10/02 22:21:28 rane Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.10</version> 11<version>1.11</version>
12<date>2005-08-02</date> 12<date>2005-10-02</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>
122partitions on the disk: 122partitions on the disk:
123</p> 123</p>
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
137 the Sun Disklabel's third partition of "Whole Disk". This partition spans 133 the Sun Disklabel's third partition of "Whole Disk". This partition spans
138 the entire disk, and should be left untouched. It serves no special purpose 134 the entire disk, and should be left untouched. It serves no special purpose
201the creation of a new label. There are two ways around this. One is to create a 197the creation of a new label. There are two ways around this. One is to create a
202Sun or MS-DOS disklabel, write the changes to disk, and restart fdisk. The 198Sun or MS-DOS disklabel, write the changes to disk, and restart fdisk. The
203second is to overwrite the partition table with null data via the following 199second is to overwrite the partition table with null data via the following
204command: <c>dd if=/dev/zero of=/dev/sda bs=512 count=1</c>. 200command: <c>dd if=/dev/zero of=/dev/sda bs=512 count=1</c>.
205</note> 201</note>
202</body>
203</subsection>
206 204
207<!-- This has been dropped in favour of using arcboot 205<subsection>
208<p>Getting the SGI Volume Header to just the right size</p> 206<title>Getting the SGI Volume Header to just the right size</title>
207<body>
208
209<impo>
210This step is often needed, due to a bug in <c>fdisk</c>. For some reason, the
211volume header isn't created correctly, the end result being it starts and ends
212on cylinder 0. This prevents multiple partitions from being created. To get
213around this issue... read on.
214</impo>
209 215
210<p> 216<p>
211Now that an SGI Disklabel is created, partitions may now be defined. In the 217Now that an SGI Disklabel is created, partitions may now be defined. In the
212above example, there are already two partitions defined for you. These are the 218above example, there are already two partitions defined for you. These are the
213special partitions mentioned above and should not normally be altered. However, 219special partitions mentioned above and should not normally be altered. However,
214for installing Gentoo, we'll need to load multiple kernel images directly into 220for installing Gentoo, we'll need to load a bootloader, and possibly multiple
215the volume header, as there is no supported SGI Bootloader available in Portage 221kernel images (depending on system type) directly into the volume header.
216yet. The volume header itself can hold up to <e>eight</e> images of any size, 222The volume header itself can hold up to <e>eight</e> images of any size,
217with each image allowed eight-character names. 223with each image allowed eight-character names.
218</p> 224</p>
219 225
220<p> 226<p>
221The process of making the volume header larger isn't exactly straight-forward - - 227The process of making the volume header larger isn't exactly straight-forward;
222there's a bit of a trick to it. One cannot simply delete and re-add the volume 228there's a bit of a trick to it. One cannot simply delete and re-add the volume
223header due to odd fdisk behavior. In the example provided below, we'll create a 229header due to odd fdisk behavior. In the example provided below, we'll create a
22450MB Volume header in conjunction with a 50MB /boot partition. The actual layout 23050MB Volume header in conjunction with a 50MB /boot partition. The actual layout
225of your disk may vary, but this is for illustrative purposes only. 231of your disk may vary, but this is for illustrative purposes only.
226</p> 232</p>
229Command (m for help): <i>n</i> 235Command (m for help): <i>n</i>
230Partition number (1-16): <i>1</i> 236Partition number (1-16): <i>1</i>
231First cylinder (5-8682, default 5): <i>51</i> 237First 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 )
235minimum of cylinder 5? Had you attempted to delete &amp; re-create the SGI 241(minimum of cylinder 5? Had you attempted to delete &amp; re-create the SGI )
236Volume 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. )
237In 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 )
238Volume 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 )
239cylinder to 101, which will roughly be 50MB (+/- 1-5MB).)</comment> 245(cylinder to 101, which will roughly be 50MB (+/- 1-5MB). )</comment>
240 246
241Command (m for help): <i>d</i> 247Command (m for help): <i>d</i>
242Partition number (1-16): <i>9</i> 248Partition number (1-16): <i>9</i>
243 249
244<comment>(Delete Partition #9 (SGI Volume Header))</comment> 250<comment>(Delete Partition #9 (SGI Volume Header))</comment>
248First cylinder (0-50, default 0): <i>0</i> 254First cylinder (0-50, default 0): <i>0</i>
249 Last cylinder (0-50, default 50): <i>50</i> 255 Last cylinder (0-50, default 50): <i>50</i>
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>
255If you're unsure how to use <c>fdisk</c> have a look down further at the 261If you're unsure how to use <c>fdisk</c> have a look down further at the
256instructions for partitioning on Cobalts. The concepts are exactly the same -- 262instructions for partitioning on Cobalts. The concepts are exactly the same --
257just remember to leave the volume header and whole disk partitions alone. 263just 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>
261Once this is done, you are safe to create the rest of your partitions as you see 267Once this is done, you are safe to create the rest of your partitions as you see
262fit. After all your partitions are laid out, make sure you set the partition ID 268fit. After all your partitions are laid out, make sure you set the partition ID
263of your swap partition to <c>82</c>, which is Linux Swap. By default, it will be 269of 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>
268Now that your partitions are created, you can now continue with <uri 274Now that your partitions are created, you can now continue with <uri
269link="#filesystems">Creating Filesystems</uri>. 275link="#filesystems">Creating Filesystems</uri>.
270</p> 276</p>

Legend:
Removed from v.1.15  
changed lines
  Added in v.1.16

  ViewVC Help
Powered by ViewVC 1.1.20