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

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

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

Revision 1.4 Revision 1.32
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/1.0 --> 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.4 2004/07/18 10:29:59 neysx Exp $ --> 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 $ -->
8 8
9<sections> 9<sections>
10
11<version>11</version>
12<date>2011-10-17</date>
13
10<section> 14<section>
11<title>Introduction to Block Devices</title> 15<title>Introduction to Block Devices</title>
12<subsection>
13<title>Block Devices</title>
14<body>
15 16
16<p>
17We'll take a good look at disk-oriented aspects of Gentoo Linux
18and Linux in general, including Linux filesystems, partitions and block devices.
19Then, once you're familiar with the ins and outs of disks and filesystems,
20you'll be guided through the process of setting up partitions and filesystems
21for your Gentoo Linux installation.
22</p>
23
24<p>
25To begin, we'll introduce <e>block devices</e>. The most famous block device is
26probably the one that represents the first SCSI HD in a Linux system, namely
27<path>/dev/sda</path>.
28</p>
29
30<p>
31The block devices above represent an abstract interface to the disk. User
32programs can use these block devices to interact with your disk without worrying
33about whether your drives are IDE, SCSI or something else. The program can
34simply address the storage on the disk as a bunch of contiguous,
35randomly-accessible 512-byte blocks.
36</p>
37
38</body>
39</subsection> 17<subsection>
18<include href="hb-install-blockdevices.xml"/>
19</subsection>
20
40<subsection> 21<subsection>
41<title>Slices</title> 22<title>Slices</title>
42<body> 23<body>
43 24
44<p> 25<p>
65<tr> 46<tr>
66 <th>Slice</th> 47 <th>Slice</th>
67 <th>Description</th> 48 <th>Description</th>
68</tr> 49</tr>
69<tr> 50<tr>
70 <ti><path>/dev/sdaa</path></ti> 51 <ti><path>/dev/sda1</path></ti>
71 <ti>Swap slice</ti> 52 <ti>Swap slice</ti>
72</tr> 53</tr>
73<tr> 54<tr>
74 <ti><path>/dev/sdab</path></ti> 55 <ti><path>/dev/sda2</path></ti>
75 <ti>Root slice</ti> 56 <ti>Root slice</ti>
76</tr> 57</tr>
77<tr> 58<tr>
78 <ti><path>/dev/sdac</path></ti> 59 <ti><path>/dev/sda3</path></ti>
79 <ti>Full disk (required)</ti> 60 <ti>Full disk (required)</ti>
80</tr> 61</tr>
81</table> 62</table>
82 63
83 64
84<p> 65<p>
85If you are interested in knowing how big a partition should be, or even how 66If you are interested in knowing how big a partition should be, or even how
86many partitions (or volumes) you need, read on. Otherwise continue now with 67many partitions (or volumes) you need, read on. Otherwise continue now with
87<uri link="#fdisk">Using fdisk to Partition your Disk</uri>. 68<uri link="#fdisk_SRM">Using fdisk to Partition your Disk (SRM only)</uri>
69or <uri link="#fdisk_ARC">Using fdisk to Partition your Disk (ARC/AlphaBIOS
70only)</uri>.
88</p> 71</p>
89 72
90</body> 73</body>
91</subsection> 74</subsection>
92<subsection> 75<subsection>
100If you are installing Gentoo to perform as a mailserver, your 83If you are installing Gentoo to perform as a mailserver, your
101<path>/var</path> should be separate as all mails are stored inside 84<path>/var</path> should be separate as all mails are stored inside
102<path>/var</path>. A good choice of filesystem will then maximise your 85<path>/var</path>. A good choice of filesystem will then maximise your
103performance. Gameservers will have a separate <path>/opt</path> as most gaming 86performance. Gameservers will have a separate <path>/opt</path> as most gaming
104servers are installed there. The reason is similar for <path>/home</path>: 87servers are installed there. The reason is similar for <path>/home</path>:
105security and backups. 88security and backups. You will definitely want to keep <path>/usr</path> big:
89not only will it contain the majority of applications, the Portage tree alone
90takes around 500 Mbyte excluding the various sources that are stored in it.
106</p> 91</p>
107 92
108<p> 93<p>
109As you can see, it very much depends on what you want to achieve. Separate 94As you can see, it very much depends on what you want to achieve. Separate
110partitions or volumes have the following advantages: 95partitions or volumes have the following advantages:
128 nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. 113 nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc.
129</li> 114</li>
130</ul> 115</ul>
131 116
132<p> 117<p>
133However, multiple partitions have one big disadvantage: if not configured 118However, multiple partitions have disadvantages as well. If not configured
134properly, you might result in having a system with lots 119properly, you will have a system with lots of free space on one partition and
135of free space on one partition and none on another. 120none on another. Another nuisance is that separate partitions - especially
121for important mountpoints like <path>/usr</path> or <path>/var</path> - often
122require the administrator to boot with an initramfs to mount the partition
123before other boot scripts start. This isn't always the case though, so YMMV.
136</p> 124</p>
137 125
138</body> 126</body>
139</subsection> 127</subsection>
140</section> 128</section>
141<section id="fdisk"> 129<section id="fdisk_SRM">
142<title>Using fdisk on Alpha to Partition your Disk</title> 130<title>Using fdisk to Partition your Disk (SRM only)</title>
143<subsection> 131<subsection>
144<body> 132<body>
145 133
146<p> 134<p>
147The following parts explain how to create the example slice layout described 135The following parts explain how to create the example slice layout described
152<tr> 140<tr>
153 <th>Slice</th> 141 <th>Slice</th>
154 <th>Description</th> 142 <th>Description</th>
155</tr> 143</tr>
156<tr> 144<tr>
157 <ti><path>/dev/sdaa</path></ti> 145 <ti><path>/dev/sda1</path></ti>
158 <ti>Swap slice</ti> 146 <ti>Swap slice</ti>
159</tr> 147</tr>
160<tr> 148<tr>
161 <ti><path>/dev/sdab</path></ti> 149 <ti><path>/dev/sda2</path></ti>
162 <ti>Root slice</ti> 150 <ti>Root slice</ti>
163</tr> 151</tr>
164<tr> 152<tr>
165 <ti><path>/dev/sdac</path></ti> 153 <ti><path>/dev/sda3</path></ti>
166 <ti>Full disk (required)</ti> 154 <ti>Full disk (required)</ti>
167</tr> 155</tr>
168</table> 156</table>
169 157
170<p> 158<p>
171Change your slice layout according to your own will. 159Change your slice layout according to your own preference.
172</p> 160</p>
173 161
174 162
175</body> 163</body>
176</subsection> 164</subsection>
181<p> 169<p>
182To figure out what disks you have running, use the following commands: 170To figure out what disks you have running, use the following commands:
183</p> 171</p>
184 172
185<pre caption="Identifying available disks"> 173<pre caption="Identifying available disks">
186<comment>(For IDE disks)</comment> # <i>dmesg | grep 'drive$'</i> 174# <i>dmesg | grep 'drive$'</i> <comment>(For IDE disks)</comment>
187<comment>(For SCSI disks)</comment> # <i>dmesg | grep 'scsi'</i> 175# <i>dmesg | grep 'scsi'</i> <comment>(For SCSI disks)</comment>
188</pre> 176</pre>
189 177
190<p> 178<p>
191From this output you should be able to see what disks were detected and their 179From this output you should be able to see what disks were detected and their
192respective <path>/dev</path> entry. In the following parts we assume that the 180respective <path>/dev</path> entry. In the following parts we assume that the
206<subsection> 194<subsection>
207<title>Deleting All Slices</title> 195<title>Deleting All Slices</title>
208<body> 196<body>
209 197
210<p> 198<p>
199If your hard drive is completely blank, then you'll have to first create
200a BSD disklabel.
201</p>
202
203<pre caption="Creating a BSD disklabel">
204Command (m for help): <i>b</i>
205/dev/sda contains no disklabel.
206Do you want to create a disklabel? (y/n) <i>y</i>
207<comment>A bunch of drive-specific info will show here</comment>
2083 partitions:
209# start end size fstype [fsize bsize cpg]
210 c: 1 5290* 5289* unused 0 0
211</pre>
212
213<p>
211We start with deleting all slices <e>except</e> the 'c'-slice. The following 214We start with deleting all slices <e>except</e> the 'c'-slice (a requirement
212shows how to delete a slice (in the example we use 'a'). Repeat the process to 215for using BSD disklabels). The following shows how to delete a slice (in
213delete all other slices (again, except the 'c'-slice). 216the example we use 'a'). Repeat the process to delete all other slices
217(again, except the 'c'-slice).
214</p> 218</p>
215 219
216<p> 220<p>
217Use <c>p</c> to view all existing slices. <c>d</c> is used to delete a slice. 221Use <c>p</c> to view all existing slices. <c>d</c> is used to delete a slice.
218</p> 222</p>
253<subsection> 257<subsection>
254<title>Creating the Swap Slice</title> 258<title>Creating the Swap Slice</title>
255<body> 259<body>
256 260
257<p> 261<p>
258On Alpha based systems you don't need a separate boot partition. However, the 262On Alpha based systems you don't need a separate boot slice. However, the
259first cylinder cannot be used as the <c>aboot</c> image will be placed there. 263first cylinder cannot be used as the <c>aboot</c> image will be placed there.
260</p> 264</p>
261 265
262<p> 266<p>
263We will create a swap slice starting at the third cylinder, with a total 267We will create a swap slice starting at the third cylinder, with a total
264size of 1 Gbyte. Use <c>n</c> to create a new slice. After creating the slice, 268size of 1 GB. Use <c>n</c> to create a new slice. After creating the slice,
265we will change its type to <c>1</c>, meaning <e>swap</e>. 269we will change its type to <c>1</c> (one), meaning <e>swap</e>.
266</p> 270</p>
267 271
268<pre caption="Creating the swap slice"> 272<pre caption="Creating the swap slice">
269BSD disklabel command (m for help): <i>n</i> 273BSD disklabel command (m for help): <i>n</i>
270Partition (a-p): <i>a</i> 274Partition (a-p): <i>a</i>
296<body> 300<body>
297 301
298<p> 302<p>
299We will now create the root slice, starting from the first cylinder <e>after</e> 303We will now create the root slice, starting from the first cylinder <e>after</e>
300the swap slice. Use the <c>p</c> command to view where the swap slice ends. In 304the swap slice. Use the <c>p</c> command to view where the swap slice ends. In
301our example, this is at 1003, making the root partition start at 1004. 305our example, this is at 1003, making the root slice start at 1004.
302</p> 306</p>
303 307
304<p> 308<p>
305Another problem is that there is currently a bug in <c>fdisk</c> making it think 309Another problem is that there is currently a bug in <c>fdisk</c> making it think
306the number of available cylinders is one above the real number of cylinders. In 310the number of available cylinders is one above the real number of cylinders. In
307other words, when you are asked for the last cylinder, decrease the cylinder 311other words, when you are asked for the last cylinder, decrease the cylinder
308number (in this example: 5290) with one. 312number (in this example: 5290) with one.
309</p> 313</p>
310 314
311<p> 315<p>
312When the partition is created, we change the type to <c>8</c>, for <e>ext2</e>. 316When the slice is created, we change the type to <c>8</c>, for <e>ext2</e>.
313</p> 317</p>
314 318
315<pre caption="Creating the root slice"> 319<pre caption="Creating the root slice">
316D disklabel command (m for help): <i>n</i> 320D disklabel command (m for help): <i>n</i>
317Partition (a-p): <i>b</i> 321Partition (a-p): <i>b</i>
350<pre caption="Save and exit fdisk"> 354<pre caption="Save and exit fdisk">
351Command (m for help): <i>w</i> 355Command (m for help): <i>w</i>
352</pre> 356</pre>
353 357
354<p> 358<p>
355Now that your slices are created, you can now continue with <uri 359Now that your slices are created, you can continue with <uri
360link="#filesystems">Creating Filesystems</uri>.
361</p>
362
363</body>
364</subsection>
365</section>
366<section id="fdisk_ARC">
367<title>Using fdisk to Partition your Disk (ARC/AlphaBIOS only)</title>
368<subsection>
369<body>
370
371<p>
372The following parts explain how to partition the disk with a layout
373similar to the one described previously, namely:
374</p>
375
376<table>
377<tr>
378 <th>Partition</th>
379 <th>Description</th>
380</tr>
381<tr>
382 <ti><path>/dev/sda1</path></ti>
383 <ti>Boot partition</ti>
384</tr>
385<tr>
386 <ti><path>/dev/sda2</path></ti>
387 <ti>Swap partition</ti>
388</tr>
389<tr>
390 <ti><path>/dev/sda3</path></ti>
391 <ti>Root partition</ti>
392</tr>
393</table>
394
395<p>
396Change your partition layout according to your own preference.
397</p>
398
399</body>
400</subsection>
401<subsection>
402<title>Identifying Available Disks</title>
403<body>
404
405<p>
406To figure out what disks you have running, use the following commands:
407</p>
408
409<pre caption="Identifying available disks">
410# <i>dmesg | grep 'drive$'</i> <comment>(For IDE disks)</comment>
411# <i>dmesg | grep 'scsi'</i> <comment>(For SCSI disks)</comment>
412</pre>
413
414<p>
415From this output you should be able to see what disks were detected and their
416respective <path>/dev</path> entry. In the following parts we assume that the
417disk is a SCSI disk on <path>/dev/sda</path>.
418</p>
419
420<p>
421Now fire up <c>fdisk</c>:
422</p>
423
424<pre caption="Starting fdisk">
425# <i>fdisk /dev/sda</i>
426</pre>
427
428</body>
429</subsection>
430<subsection>
431<title>Deleting All Partitions</title>
432<body>
433
434<p>
435If your hard drive is completely blank, then you'll have to first create
436a DOS disklabel.
437</p>
438
439<pre caption="Creating a DOS disklabel">
440Command (m for help): <i>o</i>
441Building a new DOS disklabel.
442</pre>
443
444<p>
445We start with deleting all partitions. The following shows how to delete
446a partition (in the example we use '1'). Repeat the process to delete all
447other partitions.
448</p>
449
450<p>
451Use <c>p</c> to view all existing partitions. <c>d</c> is used to delete a
452partition.
453</p>
454
455<pre caption="Deleting a partition">
456command (m for help): <i>p</i>
457
458Disk /dev/sda: 9150 MB, 9150996480 bytes
45964 heads, 32 sectors/track, 8727 cylinders
460Units = cylinders of 2048 * 512 = 1048576 bytes
461
462 Device Boot Start End Blocks Id System
463/dev/sda1 1 478 489456 83 Linux
464/dev/sda2 479 8727 8446976 5 Extended
465/dev/sda5 479 1433 977904 83 Linux Swap
466/dev/sda6 1434 8727 7469040 83 Linux
467
468command (m for help): <i>d</i>
469Partition number (1-6): <i>1</i>
470</pre>
471
472
473</body>
474</subsection>
475<subsection>
476<title>Creating the Boot Partition</title>
477<body>
478
479<p>
480On Alpha systems which use MILO to boot, we have to create a small vfat
481boot partition.
482</p>
483
484<pre caption="Creating the boot partition">
485Command (m for help): <i>n</i>
486Command action
487 e extended
488 p primary partition (1-4)
489<i>p</i>
490Partition number (1-4): <i>1</i>
491First cylinder (1-8727, default 1): <i>1</i>
492Last cylinder or +size or +sizeM or +sizeK (1-8727, default 8727): <i>+16M</i>
493
494Command (m for help): <i>t</i>
495Selected partition 1
496Hex code (type L to list codes): <i>6</i>
497Changed system type of partition 1 to 6 (FAT16)
498</pre>
499
500</body>
501</subsection>
502<subsection>
503<title>Creating the Swap Partition</title>
504<body>
505
506<p>
507We will create a swap partition with a total size of 1 GB. Use <c>n</c> to
508create a new partition.
509</p>
510
511<pre caption="Creating the swap partition">
512Command (m for help): <i>n</i>
513Command action
514 e extended
515 p primary partition (1-4)
516<i>p</i>
517Partition number (1-4): <i>2</i>
518First cylinder (17-8727, default 17): <i>17</i>
519Last cylinder or +size or +sizeM or +sizeK (17-8727, default 8727): <i>+1000M</i>
520
521Command (m for help): <i>t</i>
522Partition number (1-4): <i>2</i>
523Hex code (type L to list codes): <i>82</i>
524Changed system type of partition 2 to 82 (Linux swap)
525</pre>
526
527<p>
528After these steps you should see a layout similar to the following:
529</p>
530
531<pre caption="Partition listing after creating a swap partition">
532Command (m for help): <i>p</i>
533
534Disk /dev/sda: 9150 MB, 9150996480 bytes
53564 heads, 32 sectors/track, 8727 cylinders
536Units = cylinders of 2048 * 512 = 1048576 bytes
537
538 Device Boot Start End Blocks Id System
539/dev/sda1 1 16 16368 6 FAT16
540/dev/sda2 17 971 977920 82 Linux swap
541</pre>
542
543</body>
544</subsection>
545<subsection>
546<title>Creating the Root Partition</title>
547<body>
548
549<p>
550We will now create the root partition. Again, just use the <c>n</c> command.
551</p>
552
553<pre caption="Creating the root partition">
554Command (m for help): <i>n</i>
555Command action
556 e extended
557 p primary partition (1-4)
558<i>p</i>
559Partition number (1-4): <i>3</i>
560First cylinder (972-8727, default 972): <i>972</i>
561Last cylinder or +size or +sizeM or +sizeK (972-8727, default 8727): <i>8727</i>
562</pre>
563
564<p>
565After these steps you should see a layout similar to the following:
566</p>
567
568<pre caption="Partition listing after creating the root partition">
569Command (m for help): <i>p</i>
570
571Disk /dev/sda: 9150 MB, 9150996480 bytes
57264 heads, 32 sectors/track, 8727 cylinders
573Units = cylinders of 2048 * 512 = 1048576 bytes
574
575 Device Boot Start End Blocks Id System
576/dev/sda1 1 16 16368 6 FAT16
577/dev/sda2 17 971 977920 82 Linux swap
578/dev/sda3 972 8727 7942144 83 Linux
579</pre>
580
581</body>
582</subsection>
583<subsection>
584<title>Save the Partition Layout and Exit</title>
585<body>
586
587<p>
588Save <c>fdisk</c> by typing <c>w</c>. This will also save your partition layout.
589</p>
590
591<pre caption="Save and exit fdisk">
592Command (m for help): <i>w</i>
593</pre>
594
595<p>
596Now that your partitions are created, you can continue with <uri
356link="#filesystems">Creating Filesystems</uri>. 597link="#filesystems">Creating Filesystems</uri>.
357</p> 598</p>
358 599
359</body> 600</body>
360</subsection> 601</subsection>
373Otherwise read on to learn about the available filesystems... 614Otherwise read on to learn about the available filesystems...
374</p> 615</p>
375 616
376</body> 617</body>
377</subsection> 618</subsection>
378<subsection>
379<title>Filesystems?</title>
380<body>
381 619
382<p>
383Several filesystems are available. Most of them are found stable on the
384Alpha architecture.
385</p>
386
387<p>
388<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
389journaling, which means that routine ext2 filesystem checks at startup time can
390be quite time-consuming. There is now quite a selection of newer-generation
391journaled filesystems that can be checked for consistency very quickly and are
392thus generally preferred over their non-journaled counterparts. Journaled
393filesystems prevent long delays when you boot your system and your filesystem
394happens to be in an inconsistent state.
395</p>
396
397<p>
398<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
399journaling for fast recovery in addition to other enhanced journaling modes like
400full data and ordered data journaling. ext3 is a very good and reliable
401filesystem. It has an additional hashed b-tree indexing option that enables
402high performance in almost all situations. In short, ext3 is an excellent
403filesystem.
404</p>
405
406<p>
407<b>ReiserFS</b> is a B*-tree based filesystem that has very good overall
408performance and greatly outperforms both ext2 and ext3 when dealing with small
409files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
410extremely well and has metadata journaling. As of kernel 2.4.18+, ReiserFS is
411solid and usable as both general-purpose filesystem and for extreme cases such
412as the creation of large filesystems, the use of many small files, very large
413files and directories containing tens of thousands of files.
414</p>
415
416<p>
417<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
418feature-set and is optimized for scalability. We only recommend using this
419filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
420an uninterruptible power supply. Because XFS aggressively caches in-transit data
421in RAM, improperly designed programs (those that don't take proper precautions
422when writing files to disk and there are quite a few of them) can lose a good
423deal of data if the system goes down unexpectedly.
424</p>
425
426<p>
427<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
428become production-ready and there hasn't been a sufficient track record to
429comment positively nor negatively on its general stability at this point.
430</p>
431
432</body>
433</subsection> 620<subsection>
621<include href="hb-install-filesystems.xml"/>
622</subsection>
623
434<subsection id="filesystems-apply"> 624<subsection id="filesystems-apply">
435<title>Applying a Filesystem to a Partition</title> 625<title>Applying a Filesystem to a Partition</title>
436<body> 626<body>
437 627
438<p> 628<p>
445 <th>Filesystem</th> 635 <th>Filesystem</th>
446 <th>Creation Command</th> 636 <th>Creation Command</th>
447</tr> 637</tr>
448<tr> 638<tr>
449 <ti>ext2</ti> 639 <ti>ext2</ti>
450 <ti><c>mke2fs</c></ti> 640 <ti><c>mkfs.ext2</c></ti>
451</tr> 641</tr>
452<tr> 642<tr>
453 <ti>ext3</ti> 643 <ti>ext3</ti>
454 <ti><c>mke2fs -j</c></ti> 644 <ti><c>mkfs.ext3</c></ti>
645</tr>
646<tr>
647 <ti>ext4</ti>
648 <ti><c>mkfs.ext4</c></ti>
455</tr> 649</tr>
456<tr> 650<tr>
457 <ti>reiserfs</ti> 651 <ti>reiserfs</ti>
458 <ti><c>mkreiserfs</c></ti> 652 <ti><c>mkfs.reiserfs</c></ti>
459</tr> 653</tr>
460<tr> 654<tr>
461 <ti>xfs</ti> 655 <ti>xfs</ti>
462 <ti><c>mkfs.xfs</c></ti> 656 <ti><c>mkfs.xfs</c></ti>
463</tr> 657</tr>
466 <ti><c>mkfs.jfs</c></ti> 660 <ti><c>mkfs.jfs</c></ti>
467</tr> 661</tr>
468</table> 662</table>
469 663
470<p> 664<p>
471For instance, to have the root partition (<path>/dev/sdab</path> in our example) 665For instance, to have the root partition (<path>/dev/sda2</path> in our example)
472in ext3, you would use: 666in ext3, you would use:
473</p> 667</p>
474 668
475<pre caption="Applying a filesystem on a partition"> 669<pre caption="Applying a filesystem on a partition">
476# <i>mke2fs -j /dev/sdab</i> 670# <i>mkfs.ext3 /dev/sda2</i>
477</pre> 671</pre>
478 672
479<p> 673<p>
480Now create the filesystems on your newly created partitions (or logical 674Now create the filesystems on your newly created partitions (or logical
481volumes). 675volumes).
490<p> 684<p>
491<c>mkswap</c> is the command that is used to initialize swap partitions: 685<c>mkswap</c> is the command that is used to initialize swap partitions:
492</p> 686</p>
493 687
494<pre caption="Creating a Swap signature"> 688<pre caption="Creating a Swap signature">
495# <i>mkswap /dev/sdaa</i> 689# <i>mkswap /dev/sda1</i>
496</pre> 690</pre>
497 691
498<p> 692<p>
499To activate the swap partition, use <c>swapon</c>: 693To activate the swap partition, use <c>swapon</c>:
500</p> 694</p>
501 695
502<pre caption="Activating the swap partition"> 696<pre caption="Activating the swap partition">
503# <i>swapon /dev/sdaa</i> 697# <i>swapon /dev/sda1</i>
504</pre> 698</pre>
505 699
506<p> 700<p>
507Create and activate the swap now. 701Create and activate the swap with the commands mentioned above.
508</p> 702</p>
509 703
510</body> 704</body>
511</subsection> 705</subsection>
512</section> 706</section>
516 710
517<p> 711<p>
518Now that your partitions are initialized and are housing a filesystem, it is 712Now that your partitions are initialized and are housing a filesystem, it is
519time to mount those partitions. Use the <c>mount</c> command. Don't forget to 713time to mount those partitions. Use the <c>mount</c> command. Don't forget to
520create the necessary mount directories for every partition you created. As an 714create the necessary mount directories for every partition you created. As an
521example we mount the root and boot partition: 715example we mount the root partition:
522</p> 716</p>
523 717
524<pre caption="Mounting partitions"> 718<pre caption="Mounting partitions">
525# <i>mount /dev/sdab /mnt/gentoo</i> 719# <i>mount /dev/sda2 /mnt/gentoo</i>
526</pre> 720</pre>
527 721
528<note> 722<note>
529If you want your <path>/tmp</path> to reside on a separate partition, be sure to 723If you want your <path>/tmp</path> to reside on a separate partition, be sure to
530change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This 724change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This
531also holds for <path>/var/tmp</path>. 725also holds for <path>/var/tmp</path>.
532</note> 726</note>
533 727
534<p> 728<p>
535We also need to mount the proc filesystem (a virtual interface with the kernel) 729We will also have to mount the proc filesystem (a virtual interface with the
536on <path>/proc</path>. We first create the <path>/mnt/gentoo/proc</path> 730kernel) on <path>/proc</path>. But first we will need to place our files on the partitions.
537mountpoint and then mount the filesystem:
538</p>
539
540<pre caption="Creating the /mnt/gentoo/proc mountpoint">
541# <i>mkdir /mnt/gentoo/proc</i>
542# <i>mount -t proc none /mnt/gentoo/proc</i>
543</pre>
544
545<p> 731</p>
732
733<p>
546Now continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo 734Continue with <uri link="?part=1&amp;chap=5">Installing the Gentoo
547Installation Files</uri>. 735Installation Files</uri>.
548</p> 736</p>
549 737
550</body> 738</body>
551</section> 739</section>

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.32

  ViewVC Help
Powered by ViewVC 1.1.20