rane 05/10/02 22:21:28 Modified: xml/htdocs/doc/en/handbook hb-install-mips-disk.xml Log: #98796: re-adding Kumba's section on resizing partitions. Translators please take a look at info iin http://bugs.gentoo.org/show_bug.cgi?id=98796#c2
Revision Changes Path 1.16 +30 -24 xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml?rev=1.16&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml?rev=1.16&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml.diff?r1=1.15&r2=1.16&cvsroot=gentoo Index: hb-install-mips-disk.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- hb-install-mips-disk.xml 2 Aug 2005 08:03:53 -0000 1.15 +++ hb-install-mips-disk.xml 2 Oct 2005 22:21:28 -0000 1.16 @@ -4,12 +4,12 @@ <!-- The content of this document is licensed under the CC-BY-SA license --> <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> -<!-- $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 $ --> +<!-- $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 $ --> <sections> -<version>1.10</version> -<date>2005-08-02</date> +<version>1.11</version> +<date>2005-10-02</date> <section> <title>Introduction to Block Devices</title> @@ -124,13 +124,9 @@ <ul> <li> -<!-- <e>SGI Volume Header</e> (9th partition): This partition is important. It - is where the kernel images will go. To store kernel images, you will utilize - the tool known as <c>dvhtool</c> to copy kernel images to this partition. - You will then be able to boot kernels from this partition via the SGI PROM - Monitor. --> <e>SGI Volume Header</e> (9th partition): This partition is important. It - is where the arcboot bootloader will go. + is where the bootloader, and in some cases, will also contain the kernel + images. </li> <li> <e>SGI Volume</e> (11th partition): This partition is similar in purpose to @@ -203,22 +199,32 @@ second is to overwrite the partition table with null data via the following command: <c>dd if=/dev/zero of=/dev/sda bs=512 count=1</c>. </note> +</body> +</subsection> + +<subsection> +<title>Getting the SGI Volume Header to just the right size</title> +<body> -<!-- This has been dropped in favour of using arcboot -<p>Getting the SGI Volume Header to just the right size</p> +<impo> +This step is often needed, due to a bug in <c>fdisk</c>. For some reason, the +volume header isn't created correctly, the end result being it starts and ends +on cylinder 0. This prevents multiple partitions from being created. To get +around this issue... read on. +</impo> <p> Now that an SGI Disklabel is created, partitions may now be defined. In the above example, there are already two partitions defined for you. These are the special partitions mentioned above and should not normally be altered. However, -for installing Gentoo, we'll need to load multiple kernel images directly into -the volume header, as there is no supported SGI Bootloader available in Portage -yet. The volume header itself can hold up to <e>eight</e> images of any size, +for installing Gentoo, we'll need to load a bootloader, and possibly multiple +kernel images (depending on system type) directly into the volume header. +The volume header itself can hold up to <e>eight</e> images of any size, with each image allowed eight-character names. </p> <p> -The process of making the volume header larger isn't exactly straight-forward - - +The process of making the volume header larger isn't exactly straight-forward; there's a bit of a trick to it. One cannot simply delete and re-add the volume header due to odd fdisk behavior. In the example provided below, we'll create a 50MB Volume header in conjunction with a 50MB /boot partition. The actual layout @@ -231,12 +237,12 @@ First cylinder (5-8682, default 5): <i>51</i> Last cylinder (51-8682, default 8682): <i>101</i> -<comment>(Notice how fdisk only allows Partition #1 to be re-created starting at a -minimum of cylinder 5? Had you attempted to delete & re-create the SGI -Volume Header this way, this is the same issue you would have encountered. -In our example, we want /boot to be 50MB, so we start it at cylinder 51 (the -Volume Header needs to start at cylinder 0, remember?), and set its ending -cylinder to 101, which will roughly be 50MB (+/- 1-5MB).)</comment> +<comment>(Notice how fdisk only allows Partition #1 to be re-created starting at a ) +(minimum of cylinder 5? Had you attempted to delete & re-create the SGI ) +(Volume Header this way, this is the same issue you would have encountered. ) +(In our example, we want /boot to be 50MB, so we start it at cylinder 51 (the ) +(Volume Header needs to start at cylinder 0, remember?), and set its ending ) +(cylinder to 101, which will roughly be 50MB (+/- 1-5MB). )</comment> Command (m for help): <i>d</i> Partition number (1-16): <i>9</i> @@ -250,19 +256,19 @@ <comment>(Re-Create Partition #9, ending just before Partition #1)</comment> </pre> ---> + <p> If you're unsure how to use <c>fdisk</c> have a look down further at the instructions for partitioning on Cobalts. The concepts are exactly the same -- just remember to leave the volume header and whole disk partitions alone. </p> -<!-- <p> Perhaps part of the above commented-out block? +<p> Once this is done, you are safe to create the rest of your partitions as you see fit. After all your partitions are laid out, make sure you set the partition ID of your swap partition to <c>82</c>, which is Linux Swap. By default, it will be <c>83</c>, Linux Native. -</p> --> +</p> <p> Now that your partitions are created, you can now continue with <uri -- [email protected] mailing list
