neysx       05/11/06 09:30:31

  Modified:    xml/htdocs/doc/en/handbook hb-install-hppa-disk.xml
  Log:
  Improved coding style (tx grahl). *No Content Change*

Revision  Changes    Path
1.18      +31 -31    xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml

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
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
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

Index: hb-install-hppa-disk.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-disk.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- hb-install-hppa-disk.xml    2 Aug 2005 08:03:53 -0000       1.17
+++ hb-install-hppa-disk.xml    6 Nov 2005 09:30:31 -0000       1.18
@@ -4,7 +4,7 @@
 <!-- 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-hppa-disk.xml,v 1.17 
2005/08/02 08:03:53 swift Exp $ -->
+<!-- $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 $ -->
 
 <sections>
 
@@ -18,11 +18,11 @@
 <body>
 
 <p>
-We'll take a good look at disk-oriented aspects of Gentoo Linux
-and Linux in general, including Linux filesystems, partitions and block 
devices.
-Then, once you're familiar with the ins and outs of disks and filesystems,
-you'll be guided through the process of setting up partitions and filesystems
-for your Gentoo Linux installation.
+We'll take a good look at disk-oriented aspects of Gentoo Linux and Linux in
+general, including Linux filesystems, partitions and block devices. Then, once
+you're familiar with the ins and outs of disks and filesystems, you'll be
+guided through the process of setting up partitions and filesystems for your
+Gentoo Linux installation.
 </p>
 
 <p>
@@ -33,9 +33,9 @@
 
 <p>
 The block devices above represent an abstract interface to the disk. User
-programs can use these block devices to interact with your disk without 
worrying
-about whether your drives are IDE, SCSI or something else. The program can
-simply address the storage on the disk as a bunch of contiguous,
+programs can use these block devices to interact with your disk without
+worrying about whether your drives are IDE, SCSI or something else. The program
+can simply address the storage on the disk as a bunch of contiguous,
 randomly-accessible 512-byte blocks.
 </p>
 
@@ -48,8 +48,8 @@
 <p>
 Although it is theoretically possible to use a full disk to house your Linux
 system, this is almost never done in practice. Instead, full disk block devices
-are split up in smaller, more manageable block devices. On most systems,
-these are called <e>partitions</e>. Other architectures use a similar 
technique,
+are split up in smaller, more manageable block devices. On most systems, these
+are called <e>partitions</e>. Other architectures use a similar technique,
 called <e>slices</e>.
 </p>
 
@@ -66,15 +66,14 @@
 The number of partitions is highly dependent on your environment. For instance,
 if you have lots of users, you will most likely want to have your
 <path>/home</path> separate as it increases security and makes backups easier.
-If you are installing Gentoo to perform as a mailserver, your 
-<path>/var</path> should be separate as all mails are stored inside 
-<path>/var</path>. A good choice of filesystem will then maximise your 
-performance. Gameservers will have a separate <path>/opt</path> as most gaming 
-servers are installed there. The reason is similar for <path>/home</path>: 
-security and backups. You will definitely want to keep <path>/usr</path> big:
-not only will it contain the majority of applications, the Portage tree alone
-takes around 500 Mbyte excluding the various sources that are stored in it.
-
+If you are installing Gentoo to perform as a mailserver, your <path>/var</path>
+should be separate as all mails are stored inside <path>/var</path>. A good
+choice of filesystem will then maximise your performance. Gameservers will have
+a separate <path>/opt</path> as most gaming servers are installed there. The
+reason is similar for <path>/home</path>: security and backups. You will
+definitely want to keep <path>/usr</path> big: not only will it contain the
+majority of applications, the Portage tree alone takes around 500 Mbyte
+excluding the various sources that are stored in it.
 </p>
 
 <p>
@@ -102,10 +101,10 @@
 </ul>
 
 <p>
-However, multiple partitions have one big disadvantage: if not configured 
-properly, you might result in having a system with lots
-of free space on one partition and none on another. There is also a 
15-partition
-limit for SCSI and SATA.
+However, multiple partitions have one big disadvantage: if not configured
+properly, you might result in having a system with lots of free space on one
+partition and none on another. There is also a 15-partition limit for SCSI and
+SATA.
 </p>
 
 </body>
@@ -197,8 +196,8 @@
 <body>
 
 <p>
-Several filesystems are available. Ext2, ext3, XFS and reiserfs are found 
stable on 
-the HPPA architecture. The others are very experimental.
+Several filesystems are available. Ext2, ext3, XFS and reiserfs are found
+stable on the HPPA architecture. The others are very experimental.
 </p>
 
 <p>
@@ -348,14 +347,15 @@
 </pre>
 
 <note>
-If you want your <path>/tmp</path> to reside on a separate partition, be sure 
to
-change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This
-also holds for <path>/var/tmp</path>.
+If you want your <path>/tmp</path> to reside on a separate partition, be sure
+to change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>.
+This also holds for <path>/var/tmp</path>.
 </note>
 
 <p>
-We will also have to mount the proc filesystem (a virtual interface with the 
-kernel) on <path>/proc</path>. But first we will need to place our files on 
the partitions.
+We will also have to mount the proc filesystem (a virtual interface with the
+kernel) on <path>/proc</path>. But first we will need to place our files on the
+partitions.
 </p>
 
 <p>



-- 
[email protected] mailing list

Reply via email to