/[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.18 Revision 1.19
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.18 2006/02/27 00:55:34 fox2mike Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-mips-disk.xml,v 1.19 2006/06/12 10:18:17 neysx Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.13</version> 11<version>1.13</version>
12<date>2006-02-27</date> 12<date>2006-02-27</date>
16<subsection> 16<subsection>
17<title>Block Devices</title> 17<title>Block Devices</title>
18<body> 18<body>
19 19
20<p> 20<p>
21We'll take a good look at disk-oriented aspects of Gentoo Linux 21We'll take a good look at disk-oriented aspects of Gentoo Linux and Linux in
22and Linux in general, including Linux filesystems, partitions and block devices. 22general, including Linux filesystems, partitions and block devices. Then, once
23Then, once you're familiar with the ins and outs of disks and filesystems, 23you're familiar with the ins and outs of disks and filesystems, you'll be
24you'll be guided through the process of setting up partitions and filesystems 24guided through the process of setting up partitions and filesystems for your
25for your Gentoo Linux installation. 25Gentoo Linux installation.
26</p> 26</p>
27 27
28<p> 28<p>
29To begin, we'll introduce <e>block devices</e>. The most famous block device is 29To begin, we'll introduce <e>block devices</e>. The most famous block device is
30probably the one that represents the first SCSI HD in a Linux system, namely 30probably the one that represents the first SCSI HD in a Linux system, namely
31<path>/dev/sda</path>. 31<path>/dev/sda</path>.
32</p> 32</p>
33 33
34<p> 34<p>
35The block devices above represent an abstract interface to the disk. User 35The block devices above represent an abstract interface to the disk. User
36programs can use these block devices to interact with your disk without worrying 36programs can use these block devices to interact with your disk without
37about whether your drives are IDE, SCSI or something else. The program can 37worrying about whether your drives are IDE, SCSI or something else. The program
38simply address the storage on the disk as a bunch of contiguous, 38can simply address the storage on the disk as a bunch of contiguous,
39randomly-accessible 512-byte blocks. 39randomly-accessible 512-byte blocks.
40</p> 40</p>
41 41
42</body> 42</body>
43</subsection> 43</subsection>
46<body> 46<body>
47 47
48<p> 48<p>
49Although it is theoretically possible to use a full disk to house your Linux 49Although it is theoretically possible to use a full disk to house your Linux
50system, this is almost never done in practice. Instead, full disk block devices 50system, this is almost never done in practice. Instead, full disk block devices
51are split up in smaller, more manageable block devices. These are called 51are split up in smaller, more manageable block devices. These are called
52<e>partitions</e>. 52<e>partitions</e>.
53</p> 53</p>
54 54
55</body> 55</body>
56</subsection> 56</subsection>
63 63
64<p> 64<p>
65The number of partitions is highly dependent on your environment. For instance, 65The number of partitions is highly dependent on your environment. For instance,
66if you have lots of users, you will most likely want to have your 66if you have lots of users, you will most likely want to have your
67<path>/home</path> separate as it increases security and makes backups easier. 67<path>/home</path> separate as it increases security and makes backups easier.
68If you are installing Gentoo to perform as a mailserver, your 68If you are installing Gentoo to perform as a mailserver, your <path>/var</path>
69<path>/var</path> should be separate as all mails are stored inside 69should be separate as all mails are stored inside <path>/var</path>. A good
70<path>/var</path>. A good choice of filesystem will then maximise your 70choice of filesystem will then maximise your performance. Gameservers will have
71performance. Gameservers will have a separate <path>/opt</path> as most gaming 71a separate <path>/opt</path> as most gaming servers are installed there. The
72servers are installed there. The reason is similar for <path>/home</path>: 72reason is similar for <path>/home</path>: security and backups. You will
73security and backups. You will definitely want to keep <path>/usr</path> big: 73definitely want to keep <path>/usr</path> big: not only will it contain the
74not only will it contain the majority of applications, the Portage tree alone 74majority of applications, the Portage tree alone takes around 500 Mbyte
75takes around 500 Mbyte excluding the various sources that are stored in it. 75excluding the various sources that are stored in it.
76</p> 76</p>
77 77
78<p> 78<p>
79As you can see, it very much depends on what you want to achieve. Separate 79As you can see, it very much depends on what you want to achieve. Separate
80partitions or volumes have the following advantages: 80partitions or volumes have the following advantages:
98 nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. 98 nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc.
99</li> 99</li>
100</ul> 100</ul>
101 101
102<p> 102<p>
103However, multiple partitions have one big disadvantage: if not configured 103However, multiple partitions have one big disadvantage: if not configured
104properly, you might result in having a system with lots 104properly, you might result in having a system with lots of free space on one
105of free space on one partition and none on another. There is also a 15-partition 105partition and none on another. There is also a 15-partition limit for SCSI and
106limit for SCSI and SATA. 106SATA.
107</p> 107</p>
108 108
109</body> 109</body>
110</subsection> 110</subsection>
111</section> 111</section>
114<subsection> 114<subsection>
115<title>SGI Machines: Creating an SGI Disk Label</title> 115<title>SGI Machines: Creating an SGI Disk Label</title>
116<body> 116<body>
117 117
118<p> 118<p>
119All disks in an SGI System require an <e>SGI Disk Label</e>, which serves a 119All disks in an SGI System require an <e>SGI Disk Label</e>, which serves a
120similar function as Sun &amp; MS-DOS disklabels -- It stores information about 120similar function as Sun &amp; MS-DOS disklabels -- It stores information about
121the disk partitions. Creating a new SGI Disk Label will create two special 121the disk partitions. Creating a new SGI Disk Label will create two special
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 127 <e>SGI Volume Header</e> (9th partition): This partition is important. It
128 is where the bootloader will reside, and in some cases, it will also contain 128 is where the bootloader will reside, and in some cases, it will also
129 the kernel images. 129 contain the kernel images.
130 </li> 130 </li>
131 <li> 131 <li>
132 <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
133 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
134 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
135 other than to assist the PROM in some undocumented fashion (or it is used by 135 other than to assist the PROM in some undocumented fashion (or it is used
136 IRIX in some way). 136 by IRIX in some way).
137 </li> 137 </li>
138</ul> 138</ul>
139 139
140<warn> 140<warn>
141The SGI Volume Header <e>must</e> begin at cylinder 0. Failure to do so means 141The SGI Volume Header <e>must</e> begin at cylinder 0. Failure to do so means
205<subsection> 205<subsection>
206<title>Getting the SGI Volume Header to just the right size</title> 206<title>Getting the SGI Volume Header to just the right size</title>
207<body> 207<body>
208 208
209<impo> 209<impo>
210This step is often needed, due to a bug in <c>fdisk</c>. For some reason, the 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 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 212on cylinder 0. This prevents multiple partitions from being created. To get
213around this issue... read on. 213around this issue... read on.
214</impo> 214</impo>
215 215
216<p> 216<p>
217Now 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
218above 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
219special partitions mentioned above and should not normally be altered. However, 219special partitions mentioned above and should not normally be altered. However,
220for installing Gentoo, we'll need to load a bootloader, and possibly multiple 220for installing Gentoo, we'll need to load a bootloader, and possibly multiple
221kernel images (depending on system type) directly into the volume header. 221kernel images (depending on system type) directly into the volume header. The
222The volume header itself can hold up to <e>eight</e> images of any size, 222volume header itself can hold up to <e>eight</e> images of any size, with each
223with each image allowed eight-character names. 223image allowed eight-character names.
224</p> 224</p>
225 225
226<note> 226<note>
227On SGI systems, there are two bootloaders available: <c>arcboot</c> and 227On SGI systems, there are two bootloaders available: <c>arcboot</c> and
228<c>arcload</c>. Currently, only the Indy, Indigo2 (R4k variety), Challenge S 228<c>arcload</c>. Currently, only the Indy, Indigo2 (R4k variety), Challenge S
229and O2 are capable of using <c>arcboot</c> as a bootloader, whereas 229and O2 are capable of using <c>arcboot</c> as a bootloader, whereas
230<c>arcload</c> runs on all the Linux-supported SGI machines. Unlike 230<c>arcload</c> runs on all the Linux-supported SGI machines. Unlike
231<c>arcboot</c> however, <c>arcload</c> cannot presently read EXT2/3 partitions, 231<c>arcboot</c> however, <c>arcload</c> cannot presently read EXT2/3 partitions,
232and thus, loads its kernels from the volume header. 232and thus, loads its kernels from the volume header.
233</note> 233</note>
234 234
235<p> 235<p>
236The process of making the volume header larger isn't exactly straight-forward; 236The process of making the volume header larger isn't exactly straight-forward;
237there's a bit of a trick to it. One cannot simply delete and re-add the volume 237there's a bit of a trick to it. One cannot simply delete and re-add the volume
238header due to odd fdisk behavior. In the example provided below, we'll create a 238header due to odd fdisk behavior. In the example provided below, we'll create a
23950MB Volume header in conjunction with a 50MB /boot partition. The actual layout 23950MB Volume header in conjunction with a 50MB /boot partition. The actual
240of your disk may vary, but this is for illustrative purposes only. 240layout of your disk may vary, but this is for illustrative purposes only.
241</p> 241</p>
242 242
243<pre caption="Resizing the SGI Volume Header correctly"> 243<pre caption="Resizing the SGI Volume Header correctly">
244Command (m for help): <i>n</i> 244Command (m for help): <i>n</i>
245Partition number (1-16): <i>1</i> 245Partition number (1-16): <i>1</i>
266<comment>(Re-Create Partition #9, ending just before Partition #1)</comment> 266<comment>(Re-Create Partition #9, ending just before Partition #1)</comment>
267</pre> 267</pre>
268 268
269<p> 269<p>
270If you're unsure how to use <c>fdisk</c> have a look down further at the 270If you're unsure how to use <c>fdisk</c> have a look down further at the
271instructions for partitioning on Cobalts. The concepts are exactly the same -- 271instructions for partitioning on Cobalts. The concepts are exactly the same --
272just remember to leave the volume header and whole disk partitions alone. 272just remember to leave the volume header and whole disk partitions alone.
273</p> 273</p>
274 274
275<p> 275<p>
276Once this is done, you are safe to create the rest of your partitions as you see 276Once this is done, you are safe to create the rest of your partitions as you
277fit. After all your partitions are laid out, make sure you set the partition ID 277see fit. After all your partitions are laid out, make sure you set the
278of your swap partition to <c>82</c>, which is Linux Swap. By default, it will be 278partition ID of your swap partition to <c>82</c>, which is Linux Swap. By
279<c>83</c>, Linux Native. 279default, it will be <c>83</c>, Linux Native.
280</p> 280</p>
281 281
282<p> 282<p>
283Now that your partitions are created, you can now continue with <uri 283Now that your partitions are created, you can now continue with <uri
284link="#filesystems">Creating Filesystems</uri>. 284link="#filesystems">Creating Filesystems</uri>.
290<subsection> 290<subsection>
291<title>Cobalt Machines: Partitioning your drive</title> 291<title>Cobalt Machines: Partitioning your drive</title>
292<body> 292<body>
293 293
294<p> 294<p>
295On Cobalt machines, the BOOTROM expects to see a MS-DOS MBR, so partitioning the 295On Cobalt machines, the BOOTROM expects to see a MS-DOS MBR, so partitioning
296drive is relatively straightforward -- in fact, it's done the same way as you'd 296the drive is relatively straightforward -- in fact, it's done the same way as
297do for an Intel x86 machine. <e>However</e> there are some things you need to 297you'd do for an Intel x86 machine. <e>However</e> there are some things you
298bear in mind. 298need to bear in mind.
299</p> 299</p>
300 300
301<ul> 301<ul>
302 <li> 302 <li>
303 Cobalt firmware will expect <path>/dev/hda1</path> to be a Linux partition 303 Cobalt firmware will expect <path>/dev/hda1</path> to be a Linux partition
304 formatted <e>EXT2 Revision 0</e>. <e>EXT2 Revision 1 partitions will NOT 304 formatted <e>EXT2 Revision 0</e>. <e>EXT2 Revision 1 partitions will NOT
305 WORK!</e> (The Cobalt BOOTROM only understands EXT2r0) 305 WORK!</e> (The Cobalt BOOTROM only understands EXT2r0)
306 </li> 306 </li>
307 <li> 307 <li>
308 The above said partition must contain a gzipped ELF image, 308 The above said partition must contain a gzipped ELF image,
309 <path>vmlinux.gz</path> in the root of that partition, which it loads as the 309 <path>vmlinux.gz</path> in the root of that partition, which it loads as
310 kernel 310 the kernel
311 </li> 311 </li>
312</ul> 312</ul>
313 313
314<p> 314<p>
315For that reason, I recommend creating a ~20MB <path>/boot</path> partition 315For that reason, I recommend creating a ~20MB <path>/boot</path> partition
316formatted EXT2r0 upon which you can install CoLo &amp; your kernels. This 316formatted EXT2r0 upon which you can install CoLo &amp; your kernels. This
317allows you to run a modern filesystem (EXT3 or ReiserFS) for your root 317allows you to run a modern filesystem (EXT3 or ReiserFS) for your root
318filesystem. 318filesystem.
319</p> 319</p>
320 320
321<p> 321<p>
322I will assume you have created <path>/dev/hda1</path> to mount later as a 322I will assume you have created <path>/dev/hda1</path> to mount later as a
323<path>/boot</path> partition. If you wish to make this <path>/</path>, you'll 323<path>/boot</path> partition. If you wish to make this <path>/</path>, you'll
324need to keep the PROM's expectations in mind. 324need to keep the PROM's expectations in mind.
325</p> 325</p>
326 326
327<p> 327<p>
328So, continuing on... To create the partitions you type <c>fdisk /dev/hda</c> at 328So, continuing on... To create the partitions you type <c>fdisk /dev/hda</c> at
329the prompt. The main commands you need to know are these: 329the prompt. The main commands you need to know are these:
330</p> 330</p>
331 331
332<ul> 332<ul>
333 <li> 333 <li>
334 <c>o</c>: Wipe out old partition table, starting with an empty MS-DOS 334 <c>o</c>: Wipe out old partition table, starting with an empty MS-DOS
433<comment>(We want to use the whole disk here, so just press ENTER again)</comment> 433<comment>(We want to use the whole disk here, so just press ENTER again)</comment>
434Last cylinder or +size or +sizeM or +sizeK (41-19870, default 19870): 434Last cylinder or +size or +sizeM or +sizeK (41-19870, default 19870):
435Using default value 19870 435Using default value 19870
436 436
437<comment>(Now, the / partition -- I use separate partitions for /usr, /var, 437<comment>(Now, the / partition -- I use separate partitions for /usr, /var,
438etc... so / can be small. Adjust as per your preference.)</comment> 438etc... so / can be small. Adjust as per your preference.)</comment>
439 439
440Command (m for help): <i>n</i> 440Command (m for help): <i>n</i>
441Command action 441Command action
442 l logical (5 or over) 442 l logical (5 or over)
443 p primary partition (1-4) 443 p primary partition (1-4)
446Using default value 41 446Using default value 41
447Last cylinder or +size or +sizeM or +sizeK (41-19870, default 19870): <i>+500M</i> 447Last cylinder or +size or +sizeM or +sizeK (41-19870, default 19870): <i>+500M</i>
448 448
449<comment>(... and similar for any other partitions ...)</comment> 449<comment>(... and similar for any other partitions ...)</comment>
450 450
451<comment>(Last but not least, the swap space. I recommend at least 250MB swap, 451<comment>(Last but not least, the swap space. I recommend at least 250MB swap,
452preferrably 1GB)</comment> 452preferrably 1GB)</comment>
453 453
454Command (m for help): <i>n</i> 454Command (m for help): <i>n</i>
455Command action 455Command action
456 l logical (5 or over) 456 l logical (5 or over)
515 515
516# 516#
517</pre> 517</pre>
518 518
519<p> 519<p>
520And that's all there is to it. You should now be right to proceed onto the 520And that's all there is to it. You should now be right to proceed onto the next
521next stage: <uri link="#filesystems">Creating Filesystems</uri>. 521stage: <uri link="#filesystems">Creating Filesystems</uri>.
522</p> 522</p>
523 523
524</body> 524</body>
525</subsection> 525</subsection>
526</section> 526</section>
530<subsection> 530<subsection>
531<title>Introduction</title> 531<title>Introduction</title>
532<body> 532<body>
533 533
534<p> 534<p>
535Now that your partitions are created, it is time to place a filesystem on them. 535Now that your partitions are created, it is time to place a filesystem on them.
536If you don't care about what filesystem to choose and are happy with what we use 536If you don't care about what filesystem to choose and are happy with what we
537as default in this handbook, continue with <uri 537use as default in this handbook, continue with <uri
538link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. 538link="#filesystems-apply">Applying a Filesystem to a Partition</uri>. Otherwise
539Otherwise read on to learn about the available filesystems... 539read on to learn about the available filesystems...
540</p> 540</p>
541 541
542</body> 542</body>
543</subsection> 543</subsection>
544<subsection> 544<subsection>
545<title>Filesystems?</title> 545<title>Filesystems?</title>
546<body> 546<body>
547 547
548<p> 548<p>
549Several filesystems are available. ReiserFS, EXT2 and EXT3 are found stable 549Several filesystems are available. ReiserFS, EXT2 and EXT3 are found stable on
550on the MIPS architectures, others are experimental. 550the MIPS architectures, others are experimental.
551</p> 551</p>
552 552
553<p> 553<p>
554<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata 554<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
555journaling, which means that routine ext2 filesystem checks at startup time can 555journaling, which means that routine ext2 filesystem checks at startup time can
560happens to be in an inconsistent state. 560happens to be in an inconsistent state.
561</p> 561</p>
562 562
563<p> 563<p>
564<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata 564<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
565journaling for fast recovery in addition to other enhanced journaling modes like 565journaling for fast recovery in addition to other enhanced journaling modes
566full data and ordered data journaling. ext3 is a very good and reliable 566like full data and ordered data journaling. ext3 is a very good and reliable
567filesystem. It has an additional hashed b-tree indexing option that enables 567filesystem. It has an additional hashed b-tree indexing option that enables
568high performance in almost all situations. You can enable this indexing by 568high performance in almost all situations. You can enable this indexing by
569adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an 569adding <c>-O dir_index</c> to the <c>mke2fs</c> command. In short, ext3 is an
570excellent filesystem. 570excellent filesystem.
571</p> 571</p>
572 572
573<p> 573<p>
574<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall 574<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall
575performance and greatly outperforms both ext2 and ext3 when dealing with small 575performance and greatly outperforms both ext2 and ext3 when dealing with small
576files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales 576files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
577extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is 577extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is
578solid and usable as both general-purpose filesystem and for extreme cases such 578solid and usable as both general-purpose filesystem and for extreme cases such
579as the creation of large filesystems, the use of many small files, very large 579as the creation of large filesystems, the use of many small files, very large
580files and directories containing tens of thousands of files. 580files and directories containing tens of thousands of files.
581</p> 581</p>
582 582
583<p> 583<p>
584<b>XFS</b> is a filesystem with metadata journaling which comes with a robust 584<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
585feature-set and is optimized for scalability. We only recommend using this 585feature-set and is optimized for scalability. We only recommend using this
586filesystem on Linux systems with high-end SCSI and/or fibre channel storage and 586filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
587an uninterruptible power supply. Because XFS aggressively caches in-transit data 587an uninterruptible power supply. Because XFS aggressively caches in-transit
588in RAM, improperly designed programs (those that don't take proper precautions 588data in RAM, improperly designed programs (those that don't take proper
589when writing files to disk and there are quite a few of them) can lose a good 589precautions when writing files to disk and there are quite a few of them) can
590deal of data if the system goes down unexpectedly. 590lose a good deal of data if the system goes down unexpectedly.
591</p>
592
593<p> 591</p>
592
593<p>
594<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently 594<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
595become production-ready and there hasn't been a sufficient track record to 595become production-ready and there hasn't been a sufficient track record to
596comment positively nor negatively on its general stability at this point. 596comment positively nor negatively on its general stability at this point.
597</p> 597</p>
598 598
599</body> 599</body>
600</subsection> 600</subsection>
601<subsection id="filesystems-apply"> 601<subsection id="filesystems-apply">
602<title>Applying a Filesystem to a Partition</title> 602<title>Applying a Filesystem to a Partition</title>
603<body> 603<body>
604 604
605<p> 605<p>
606To create a filesystem on a partition or volume, there are tools available for 606To create a filesystem on a partition or volume, there are tools available for
607each possible filesystem: 607each possible filesystem:
608</p> 608</p>
609 609
610<table> 610<table>
611<tr> 611<tr>
649Now create the filesystems on your newly created partitions (or logical 649Now create the filesystems on your newly created partitions (or logical
650volumes). 650volumes).
651</p> 651</p>
652 652
653<warn> 653<warn>
654If you're installing on a Cobalt server, remember <path>/dev/hda1</path> MUST be 654If you're installing on a Cobalt server, remember <path>/dev/hda1</path> MUST
655of type <e>EXT2 revision 0</e>; Anything else (e.g. EXT2 revision 1, EXT3, 655be of type <e>EXT2 revision 0</e>; Anything else (e.g. EXT2 revision 1, EXT3,
656ReiserFS, XFS, JFS and others) <e>WILL NOT WORK!</e> 656ReiserFS, XFS, JFS and others) <e>WILL NOT WORK!</e> You can format the
657You can format the partition using the command: <c>mke2fs -r 0 /dev/hda1</c>. 657partition using the command: <c>mke2fs -r 0 /dev/hda1</c>.
658</warn> 658</warn>
659 659
660<warn> 660<warn>
661Also, be aware that arcboot currently is not able to read any filesystem other 661Also, be aware that arcboot currently is not able to read any filesystem other
662than EXT2, EXT3 and ISO9660 (recent versions). For that reason, 662than EXT2, EXT3 and ISO9660 (recent versions). For that reason,
663<path>/boot</path> on SGI machines must also reside on an EXT2 or EXT3 partition. 663<path>/boot</path> on SGI machines must also reside on an EXT2 or EXT3
664partition.
664</warn> 665</warn>
665 666
666</body> 667</body>
667</subsection> 668</subsection>
668<subsection> 669<subsection>
669<title>Activating the Swap Partition</title> 670<title>Activating the Swap Partition</title>
670<body> 671<body>
671 672
672<p> 673<p>
673<c>mkswap</c> is the command that is used to create and initialize swap partitions: 674<c>mkswap</c> is the command that is used to create and initialize swap
675partitions:
674</p> 676</p>
675 677
676<pre caption="Creating a Swap signature"> 678<pre caption="Creating a Swap signature">
677# <i>mkswap /dev/sda2</i> 679# <i>mkswap /dev/sda2</i>
678</pre> 680</pre>
708# <i>mkdir /mnt/gentoo/boot</i> 710# <i>mkdir /mnt/gentoo/boot</i>
709# <i>mount /dev/sda1 /mnt/gentoo/boot</i> 711# <i>mount /dev/sda1 /mnt/gentoo/boot</i>
710</pre> 712</pre>
711 713
712<note> 714<note>
713If you want your <path>/tmp</path> to reside on a separate partition, be sure to 715If you want your <path>/tmp</path> to reside on a separate partition, be sure
714change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This 716to change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>.
715also holds for <path>/var/tmp</path>. 717This also holds for <path>/var/tmp</path>.
716</note> 718</note>
717 719
718<p> 720<p>
719We will also have to mount the proc filesystem (a virtual interface with the 721We will also have to mount the proc filesystem (a virtual interface with the
720kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. 722kernel) on <path>/proc</path>. But first we will need to place our files on the
721</p> 723partitions.
722
723<p> 724</p>
725
726<p>
724Continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo 727Continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo Installation
725Installation Files</uri>. 728Files</uri>.
726</p> 729</p>
727 730
728</body> 731</body>
729</section> 732</section>
730</sections> 733</sections>

Legend:
Removed from v.1.18  
changed lines
  Added in v.1.19

  ViewVC Help
Powered by ViewVC 1.1.20