| 1 |
neysx 05/11/06 09:30:31 |
| 2 |
|
| 3 |
Modified: xml/htdocs/doc/en/handbook hb-install-hppa-disk.xml |
| 4 |
Log: |
| 5 |
Improved coding style (tx grahl). *No Content Change* |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.18 +31 -31 xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml |
| 9 |
|
| 10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml?rev=1.18&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml?rev=1.18&content-type=text/plain&cvsroot=gentoo |
| 12 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml.diff?r1=1.17&r2=1.18&cvsroot=gentoo |
| 13 |
|
| 14 |
Index: hb-install-hppa-disk.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml,v |
| 17 |
retrieving revision 1.17 |
| 18 |
retrieving revision 1.18 |
| 19 |
diff -u -r1.17 -r1.18 |
| 20 |
--- hb-install-hppa-disk.xml 2 Aug 2005 08:03:53 -0000 1.17 |
| 21 |
+++ hb-install-hppa-disk.xml 6 Nov 2005 09:30:31 -0000 1.18 |
| 22 |
@@ -4,7 +4,7 @@ |
| 23 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 24 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 25 |
|
| 26 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml,v 1.17 2005/08/02 08:03:53 swift Exp $ --> |
| 27 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml,v 1.18 2005/11/06 09:30:31 neysx Exp $ --> |
| 28 |
|
| 29 |
<sections> |
| 30 |
|
| 31 |
@@ -18,11 +18,11 @@ |
| 32 |
<body> |
| 33 |
|
| 34 |
<p> |
| 35 |
-We'll take a good look at disk-oriented aspects of Gentoo Linux |
| 36 |
-and Linux in general, including Linux filesystems, partitions and block devices. |
| 37 |
-Then, once you're familiar with the ins and outs of disks and filesystems, |
| 38 |
-you'll be guided through the process of setting up partitions and filesystems |
| 39 |
-for your Gentoo Linux installation. |
| 40 |
+We'll take a good look at disk-oriented aspects of Gentoo Linux and Linux in |
| 41 |
+general, including Linux filesystems, partitions and block devices. Then, once |
| 42 |
+you're familiar with the ins and outs of disks and filesystems, you'll be |
| 43 |
+guided through the process of setting up partitions and filesystems for your |
| 44 |
+Gentoo Linux installation. |
| 45 |
</p> |
| 46 |
|
| 47 |
<p> |
| 48 |
@@ -33,9 +33,9 @@ |
| 49 |
|
| 50 |
<p> |
| 51 |
The block devices above represent an abstract interface to the disk. User |
| 52 |
-programs can use these block devices to interact with your disk without worrying |
| 53 |
-about whether your drives are IDE, SCSI or something else. The program can |
| 54 |
-simply address the storage on the disk as a bunch of contiguous, |
| 55 |
+programs can use these block devices to interact with your disk without |
| 56 |
+worrying about whether your drives are IDE, SCSI or something else. The program |
| 57 |
+can simply address the storage on the disk as a bunch of contiguous, |
| 58 |
randomly-accessible 512-byte blocks. |
| 59 |
</p> |
| 60 |
|
| 61 |
@@ -48,8 +48,8 @@ |
| 62 |
<p> |
| 63 |
Although it is theoretically possible to use a full disk to house your Linux |
| 64 |
system, this is almost never done in practice. Instead, full disk block devices |
| 65 |
-are split up in smaller, more manageable block devices. On most systems, |
| 66 |
-these are called <e>partitions</e>. Other architectures use a similar technique, |
| 67 |
+are split up in smaller, more manageable block devices. On most systems, these |
| 68 |
+are called <e>partitions</e>. Other architectures use a similar technique, |
| 69 |
called <e>slices</e>. |
| 70 |
</p> |
| 71 |
|
| 72 |
@@ -66,15 +66,14 @@ |
| 73 |
The number of partitions is highly dependent on your environment. For instance, |
| 74 |
if you have lots of users, you will most likely want to have your |
| 75 |
<path>/home</path> separate as it increases security and makes backups easier. |
| 76 |
-If you are installing Gentoo to perform as a mailserver, your |
| 77 |
-<path>/var</path> should be separate as all mails are stored inside |
| 78 |
-<path>/var</path>. A good choice of filesystem will then maximise your |
| 79 |
-performance. Gameservers will have a separate <path>/opt</path> as most gaming |
| 80 |
-servers are installed there. The reason is similar for <path>/home</path>: |
| 81 |
-security and backups. You will definitely want to keep <path>/usr</path> big: |
| 82 |
-not only will it contain the majority of applications, the Portage tree alone |
| 83 |
-takes around 500 Mbyte excluding the various sources that are stored in it. |
| 84 |
- |
| 85 |
+If you are installing Gentoo to perform as a mailserver, your <path>/var</path> |
| 86 |
+should be separate as all mails are stored inside <path>/var</path>. A good |
| 87 |
+choice of filesystem will then maximise your performance. Gameservers will have |
| 88 |
+a separate <path>/opt</path> as most gaming servers are installed there. The |
| 89 |
+reason is similar for <path>/home</path>: security and backups. You will |
| 90 |
+definitely want to keep <path>/usr</path> big: not only will it contain the |
| 91 |
+majority of applications, the Portage tree alone takes around 500 Mbyte |
| 92 |
+excluding the various sources that are stored in it. |
| 93 |
</p> |
| 94 |
|
| 95 |
<p> |
| 96 |
@@ -102,10 +101,10 @@ |
| 97 |
</ul> |
| 98 |
|
| 99 |
<p> |
| 100 |
-However, multiple partitions have one big disadvantage: if not configured |
| 101 |
-properly, you might result in having a system with lots |
| 102 |
-of free space on one partition and none on another. There is also a 15-partition |
| 103 |
-limit for SCSI and SATA. |
| 104 |
+However, multiple partitions have one big disadvantage: if not configured |
| 105 |
+properly, you might result in having a system with lots of free space on one |
| 106 |
+partition and none on another. There is also a 15-partition limit for SCSI and |
| 107 |
+SATA. |
| 108 |
</p> |
| 109 |
|
| 110 |
</body> |
| 111 |
@@ -197,8 +196,8 @@ |
| 112 |
<body> |
| 113 |
|
| 114 |
<p> |
| 115 |
-Several filesystems are available. Ext2, ext3, XFS and reiserfs are found stable on |
| 116 |
-the HPPA architecture. The others are very experimental. |
| 117 |
+Several filesystems are available. Ext2, ext3, XFS and reiserfs are found |
| 118 |
+stable on the HPPA architecture. The others are very experimental. |
| 119 |
</p> |
| 120 |
|
| 121 |
<p> |
| 122 |
@@ -348,14 +347,15 @@ |
| 123 |
</pre> |
| 124 |
|
| 125 |
<note> |
| 126 |
-If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
| 127 |
-change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
| 128 |
-also holds for <path>/var/tmp</path>. |
| 129 |
+If you want your <path>/tmp</path> to reside on a separate partition, be sure |
| 130 |
+to change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. |
| 131 |
+This also holds for <path>/var/tmp</path>. |
| 132 |
</note> |
| 133 |
|
| 134 |
<p> |
| 135 |
-We will also have to mount the proc filesystem (a virtual interface with the |
| 136 |
-kernel) on <path>/proc</path>. But first we will need to place our files on the partitions. |
| 137 |
+We will also have to mount the proc filesystem (a virtual interface with the |
| 138 |
+kernel) on <path>/proc</path>. But first we will need to place our files on the |
| 139 |
+partitions. |
| 140 |
</p> |
| 141 |
|
| 142 |
<p> |
| 143 |
|
| 144 |
|
| 145 |
|
| 146 |
-- |
| 147 |
gentoo-doc-cvs@g.o mailing list |
Archives