neysx 08/03/01 14:15:58
Modified: hb-install-alpha-disk.xml hb-install-arm-disk.xml
hb-install-hppa-disk.xml hb-install-ia64-disk.xml
hb-install-mips-disk.xml hb-install-ppc-disk.xml
hb-install-ppc64-disk.xml hb-install-sparc-disk.xml
hb-install-x86+amd64-disk.xml
Added: hb-install-filesystems.xml
Log:
#179796 tone down ReiserFS desc, recommend ext3 and cut some cruft
Revision Changes Path
1.20 xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml?rev=1.20&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml?rev=1.20&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml?r1=1.19&r2=1.20
Index: hb-install-alpha-disk.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- hb-install-alpha-disk.xml 1 Mar 2008 07:03:30 -0000 1.19
+++ hb-install-alpha-disk.xml 1 Mar 2008 14:15:58 -0000 1.20
@@ -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/draft/hb-install-alpha-disk.xml,v
1.19 2008/03/01 07:03:30 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml,v
1.20 2008/03/01 14:15:58 neysx Exp $ -->
<sections>
@@ -640,66 +640,11 @@
</body>
</subsection>
-<subsection>
-<title>Filesystems?</title>
-<body>
-
-<p>
-Several filesystems are available. Most of them are found stable on the
-Alpha architecture.
-</p>
-
-<note>
-<c>aboot</c> only supports booting from <b>ext2</b> and <b>ext3</b>
-partitions.
-</note>
-
-<p>
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
-journaling, which means that routine ext2 filesystem checks at startup time can
-be quite time-consuming. There is now quite a selection of newer-generation
-journaled filesystems that can be checked for consistency very quickly and are
-thus generally preferred over their non-journaled counterparts. Journaled
-filesystems prevent long delays when you boot your system and your filesystem
-happens to be in an inconsistent state.
-</p>
-
-<p>
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
-journaling for fast recovery in addition to other enhanced journaling modes
like
-full data and ordered data journaling. It uses an HTree index that enables high
-performance in almost all situations. In short, ext3 is a very good and
reliable
-filesystem.
-</p>
-
-<p>
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
-performance and greatly outperforms both ext2 and ext3 when dealing with small
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
-extremely well and has metadata journaling. ReiserFS is solid and usable as
-both general-purpose filesystem and for extreme cases such as the creation of
-large filesystems, very large files and directories containing tens of
-thousands of small files.
-</p>
-
-<p>
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
-feature-set and is optimized for scalability. We only recommend using this
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
-an uninterruptible power supply. Because XFS aggressively caches in-transit
data
-in RAM, improperly designed programs (those that don't take proper precautions
-when writing files to disk and there are quite a few of them) can lose a good
-deal of data if the system goes down unexpectedly.
-</p>
-<p>
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
-become production-ready and there hasn't been a sufficient track record to
-comment positively nor negatively on its general stability at this point.
-</p>
-
-</body>
+<subsection>
+<include href="hb-install-filesystems.xml"/>
</subsection>
+
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>
1.7 xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml?rev=1.7&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml?rev=1.7&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml?r1=1.6&r2=1.7
Index: hb-install-arm-disk.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- hb-install-arm-disk.xml 1 Mar 2008 07:03:30 -0000 1.6
+++ hb-install-arm-disk.xml 1 Mar 2008 14:15:58 -0000 1.7
@@ -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/draft/hb-install-arm-disk.xml,v
1.6 2008/03/01 07:03:30 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml,v
1.7 2008/03/01 14:15:58 neysx Exp $ -->
<sections>
@@ -498,63 +498,11 @@
</body>
</subsection>
-<subsection>
-<title>Filesystems?</title>
-<body>
-
-<p>
-Several filesystems are available. Some of them are found stable on the arm
-architecture, others aren't. The following filesystems are found to be stable:
-ext2 and ext3. jfs and reiserfs may work but need more testing. If you're
-really adventurous you can try the unsupported filesystems.
-</p>
-
-<p>
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
-journaling, which means that routine ext2 filesystem checks at startup time can
-be quite time-consuming. There is now quite a selection of newer-generation
-journaled filesystems that can be checked for consistency very quickly and are
-thus generally preferred over their non-journaled counterparts. Journaled
-filesystems prevent long delays when you boot your system and your filesystem
-happens to be in an inconsistent state.
-</p>
-
-<p>
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
-journaling for fast recovery in addition to other enhanced journaling modes
like
-full data and ordered data journaling. It uses an HTree index that enables high
-performance in almost all situations. In short, ext3 is a very good and
reliable
-filesystem.
-</p>
-<p>
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
-performance and greatly outperforms both ext2 and ext3 when dealing with small
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
-extremely well and has metadata journaling. ReiserFS is solid and usable as
-both general-purpose filesystem and for extreme cases such as the creation of
-large filesystems, very large files and directories containing tens of
-thousands of small files.
-</p>
-
-<p>
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
-feature-set and is optimized for scalability. We only recommend using this
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
-an uninterruptible power supply. Because XFS aggressively caches in-transit
data
-in RAM, improperly designed programs (those that don't take proper precautions
-when writing files to disk and there are quite a few of them) can lose a good
-deal of data if the system goes down unexpectedly.
-</p>
-
-<p>
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
-become production-ready and there hasn't been a sufficient track record to
-comment positively nor negatively on its general stability at this point.
-</p>
-
-</body>
+<subsection>
+<include href="hb-install-filesystems.xml"/>
</subsection>
+
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>
1.17 xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml?rev=1.17&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml?rev=1.17&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml?r1=1.16&r2=1.17
Index: hb-install-hppa-disk.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- hb-install-hppa-disk.xml 1 Mar 2008 07:03:30 -0000 1.16
+++ hb-install-hppa-disk.xml 1 Mar 2008 14:15:58 -0000 1.17
@@ -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/draft/hb-install-hppa-disk.xml,v
1.16 2008/03/01 07:03:30 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml,v
1.17 2008/03/01 14:15:58 neysx Exp $ -->
<sections>
@@ -195,61 +195,11 @@
</body>
</subsection>
-<subsection>
-<title>Filesystems?</title>
-<body>
-
-<p>
-Several filesystems are available. Ext2, ext3, XFS and reiserfs are found
-stable on the HPPA architecture. The others are very experimental.
-</p>
-
-<p>
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
-journaling, which means that routine ext2 filesystem checks at startup time can
-be quite time-consuming. There is now quite a selection of newer-generation
-journaled filesystems that can be checked for consistency very quickly and are
-thus generally preferred over their non-journaled counterparts. Journaled
-filesystems prevent long delays when you boot your system and your filesystem
-happens to be in an inconsistent state.
-</p>
-
-<p>
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
-journaling for fast recovery in addition to other enhanced journaling modes
like
-full data and ordered data journaling. It uses an HTree index that enables high
-performance in almost all situations. In short, ext3 is a very good and
reliable
-filesystem.
-</p>
-<p>
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
-performance and greatly outperforms both ext2 and ext3 when dealing with small
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
-extremely well and has metadata journaling. ReiserFS is solid and usable as
-both general-purpose filesystem and for extreme cases such as the creation of
-large filesystems, very large files and directories containing tens of
-thousands of small files.
-</p>
-
-<p>
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
-feature-set and is optimized for scalability. We only recommend using this
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
-an uninterruptible power supply. Because XFS aggressively caches in-transit
data
-in RAM, improperly designed programs (those that don't take proper precautions
-when writing files to disk and there are quite a few of them) can lose a good
-deal of data if the system goes down unexpectedly.
-</p>
-
-<p>
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
-become production-ready and there hasn't been a sufficient track record to
-comment positively nor negatively on its general stability at this point.
-</p>
-
-</body>
+<subsection>
+<include href="hb-install-filesystems.xml"/>
</subsection>
+
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>
1.8 xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml?rev=1.8&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml?rev=1.8&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml?r1=1.7&r2=1.8
Index: hb-install-ia64-disk.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- hb-install-ia64-disk.xml 1 Mar 2008 07:03:30 -0000 1.7
+++ hb-install-ia64-disk.xml 1 Mar 2008 14:15:58 -0000 1.8
@@ -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/draft/hb-install-ia64-disk.xml,v
1.7 2008/03/01 07:03:30 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml,v
1.8 2008/03/01 14:15:58 neysx Exp $ -->
<sections>
@@ -449,69 +449,11 @@
</body>
</subsection>
-<subsection>
-<title>Filesystems?</title>
-<body>
-
-<p>
-The Linux kernel supports various filesystems. We'll explain vfat, ext2, ext3,
-ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux
-systems.
-</p>
-
-<p>
-<b>vfat</b> is the MS-DOS filesystem, updated to allow long filenames. It is
-also the only filesystem type that the EFI firmware on ia64 systems understand.
-The boot partition on ia64 systems should always be vfat, but for your data
-partitions you should use one of the other filesystems listed below.
-</p>
-
-<p>
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
-journaling, which means that routine ext2 filesystem checks at startup time can
-be quite time-consuming. There is now quite a selection of newer-generation
-journaled filesystems that can be checked for consistency very quickly and are
-thus generally preferred over their non-journaled counterparts. Journaled
-filesystems prevent long delays when you boot your system and your filesystem
-happens to be in an inconsistent state.
-</p>
-
-<p>
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
-journaling for fast recovery in addition to other enhanced journaling modes
like
-full data and ordered data journaling. It uses an HTree index that enables high
-performance in almost all situations. In short, ext3 is a very good and
reliable
-filesystem.
-</p>
-
-<p>
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
-performance and greatly outperforms both ext2 and ext3 when dealing with small
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
-extremely well and has metadata journaling. ReiserFS is solid and usable as
-both general-purpose filesystem and for extreme cases such as the creation of
-large filesystems, very large files and directories containing tens of
-thousands of small files.
-</p>
-
-<p>
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
-feature-set and is optimized for scalability. We only recommend using this
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
-an uninterruptible power supply. Because XFS aggressively caches in-transit
data
-in RAM, improperly designed programs (those that don't take proper precautions
-when writing files to disk and there are quite a few of them) can lose a good
-deal of data if the system goes down unexpectedly.
-</p>
-<p>
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
-become production-ready and there hasn't been a sufficient track record to
-comment positively nor negatively on its general stability at this point.
-</p>
-
-</body>
+<subsection>
+<include href="hb-install-filesystems.xml"/>
</subsection>
+
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>
1.19 xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml?rev=1.19&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml?rev=1.19&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml?r1=1.18&r2=1.19
Index: hb-install-mips-disk.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- hb-install-mips-disk.xml 1 Mar 2008 07:03:30 -0000 1.18
+++ hb-install-mips-disk.xml 1 Mar 2008 14:15:58 -0000 1.19
@@ -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/draft/hb-install-mips-disk.xml,v
1.18 2008/03/01 07:03:30 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml,v
1.19 2008/03/01 14:15:58 neysx Exp $ -->
<sections>
@@ -536,61 +536,11 @@
</body>
</subsection>
-<subsection>
-<title>Filesystems?</title>
-<body>
-
-<p>
-Several filesystems are available. ReiserFS, EXT2 and EXT3 are found stable on
-the MIPS architectures, others are experimental.
-</p>
-
-<p>
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
-journaling, which means that routine ext2 filesystem checks at startup time can
-be quite time-consuming. There is now quite a selection of newer-generation
-journaled filesystems that can be checked for consistency very quickly and are
-thus generally preferred over their non-journaled counterparts. Journaled
-filesystems prevent long delays when you boot your system and your filesystem
-happens to be in an inconsistent state.
-</p>
-
-<p>
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
-journaling for fast recovery in addition to other enhanced journaling modes
like
-full data and ordered data journaling. It uses an HTree index that enables high
-performance in almost all situations. In short, ext3 is a very good and
reliable
-filesystem.
-</p>
-<p>
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
-performance and greatly outperforms both ext2 and ext3 when dealing with small
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
-extremely well and has metadata journaling. ReiserFS is solid and usable as
-both general-purpose filesystem and for extreme cases such as the creation of
-large filesystems, very large files and directories containing tens of
-thousands of small files.
-</p>
-
-<p>
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
-feature-set and is optimized for scalability. We only recommend using this
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
-an uninterruptible power supply. Because XFS aggressively caches in-transit
-data in RAM, improperly designed programs (those that don't take proper
-precautions when writing files to disk and there are quite a few of them) can
-lose a good deal of data if the system goes down unexpectedly.
-</p>
-
-<p>
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
-become production-ready and there hasn't been a sufficient track record to
-comment positively nor negatively on its general stability at this point.
-</p>
-
-</body>
+<subsection>
+<include href="hb-install-filesystems.xml"/>
</subsection>
+
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>
1.30 xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml?rev=1.30&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml?rev=1.30&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml?r1=1.29&r2=1.30
Index: hb-install-ppc-disk.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- hb-install-ppc-disk.xml 1 Mar 2008 07:03:30 -0000 1.29
+++ hb-install-ppc-disk.xml 1 Mar 2008 14:15:58 -0000 1.30
@@ -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/draft/hb-install-ppc-disk.xml,v
1.29 2008/03/01 07:03:30 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml,v
1.30 2008/03/01 14:15:58 neysx Exp $ -->
<sections>
@@ -502,53 +502,11 @@
</body>
</subsection>
-<subsection>
-<title>Filesystems?</title>
-<body>
-
-<p>
-Several filesystems are available for use on the PowerPC architecture including
-ext2, ext3, ReiserFS and XFS, each with their strengths and faults.
-</p>
-
-<p>
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
-journaling, which means that routine ext2 filesystem checks at startup time can
-be quite time-consuming. There is now quite a selection of journaled
-filesystems that can be checked for consistency very quickly and are thus
-generally preferred over their non-journaled counterparts.
-</p>
-
-<p>
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
-journaling for fast recovery in addition to other enhanced journaling modes
like
-full data and ordered data journaling. It uses an HTree index that enables high
-performance in almost all situations. In short, ext3 is a very good and
reliable
-filesystem.
-</p>
-
-<p>
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
-performance and greatly outperforms both ext2 and ext3 when dealing with small
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
-extremely well and has metadata journaling. ReiserFS is solid and usable as
-both general-purpose filesystem and for extreme cases such as the creation of
-large filesystems, very large files and directories containing tens of
-thousands of small files.
-</p>
-
-<p>
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
-feature-set and is optimized for scalability. We only recommend using this
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
-an uninterruptible power supply. Because XFS aggressively caches in-transit
data
-in RAM, improperly designed programs (those that don't take proper precautions
-when writing files to disk and there are quite a few of them) can lose a good
-deal of data if the system goes down unexpectedly.
-</p>
-</body>
+<subsection>
+<include href="hb-install-filesystems.xml"/>
</subsection>
+
<subsection>
<title>Activating the Swap Partition</title>
<body>
1.23 xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml?rev=1.23&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml?rev=1.23&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml?r1=1.22&r2=1.23
Index: hb-install-ppc64-disk.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- hb-install-ppc64-disk.xml 1 Mar 2008 07:03:30 -0000 1.22
+++ hb-install-ppc64-disk.xml 1 Mar 2008 14:15:58 -0000 1.23
@@ -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/draft/hb-install-ppc64-disk.xml,v
1.22 2008/03/01 07:03:30 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml,v
1.23 2008/03/01 14:15:58 neysx Exp $ -->
<sections>
@@ -598,62 +598,11 @@
</body>
</subsection>
-<subsection>
-<title>Filesystems?</title>
-<body>
-
-<note>
-Several filesystems are available. ext2, ext3 and ReiserFS support is built in
-the Installation CD kernels. JFS and XFS support is available through kernel
-modules.
-</note>
-
-<p>
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
-journaling, which means that routine ext2 filesystem checks at startup time can
-be quite time-consuming. There is now quite a selection of newer-generation
-journaled filesystems that can be checked for consistency very quickly and are
-thus generally preferred over their non-journaled counterparts. Journaled
-filesystems prevent long delays when you boot your system and your filesystem
-happens to be in an inconsistent state.
-</p>
-
-<p>
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
-journaling for fast recovery in addition to other enhanced journaling modes
like
-full data and ordered data journaling. It uses an HTree index that enables high
-performance in almost all situations. In short, ext3 is a very good and
reliable
-filesystem.
-</p>
-<p>
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
-performance and greatly outperforms both ext2 and ext3 when dealing with small
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
-extremely well and has metadata journaling. ReiserFS is solid and usable as
-both general-purpose filesystem and for extreme cases such as the creation of
-large filesystems, very large files and directories containing tens of
-thousands of small files.
-</p>
-
-<p>
-<b>XFS</b> is a filesystem with metadata journaling that is fully supported
-under Gentoo Linux's xfs-sources kernel. It comes with a robust feature-set and
-is optimized for scalability. We only recommend using this filesystem on Linux
-systems with high-end SCSI and/or fibre channel storage and a uninterruptible
-power supply. Because XFS aggressively caches in-transit data in RAM,
improperly
-designed programs (those that don't take proper precautions when writing files
-to disk and there are quite a few of them) can lose a good deal of data if the
-system goes down unexpectedly.
-</p>
-
-<p>
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
-become production-ready.
-</p>
-
-</body>
+<subsection>
+<include href="hb-install-filesystems.xml"/>
</subsection>
+
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>
1.22 xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml?rev=1.22&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml?rev=1.22&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml?r1=1.21&r2=1.22
Index: hb-install-sparc-disk.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- hb-install-sparc-disk.xml 1 Mar 2008 07:03:30 -0000 1.21
+++ hb-install-sparc-disk.xml 1 Mar 2008 14:15:58 -0000 1.22
@@ -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/draft/hb-install-sparc-disk.xml,v
1.21 2008/03/01 07:03:30 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml,v
1.22 2008/03/01 14:15:58 neysx Exp $ -->
<sections>
@@ -486,36 +486,11 @@
</body>
</subsection>
-<subsection>
-<title>Filesystems?</title>
-<body>
-
-<p>
-Several filesystems are available, some are known to be stable on the
-SPARC architecture. Ext2 and ext3, for example, are known to work well.
-Alternate filesystems may not function correctly.
-</p>
-
-<p>
-<b>ext2</b> is the tried-and-true Linux filesystem. It does not support
-journaling, which means that periodic checks of ext2 filesystems at startup
-can be quite time-consuming. There is quite a selection of newer-generation
-journaled filesystems that can be checked for consistency very quickly at
-startup, and are therefore generally preferred over their non-journaled
-counterparts. In general, journaled filesystems prevent long delays when a
-system is booted and the filesystem is in an inconsistent state.
-</p>
-
-<p>
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
-journaling for fast recovery in addition to other enhanced journaling modes
like
-full data and ordered data journaling. It uses an HTree index that enables high
-performance in almost all situations. In short, ext3 is a very good and
reliable
-filesystem.
-</p>
-</body>
+<subsection>
+<include href="hb-install-filesystems.xml"/>
</subsection>
+
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>
1.10
xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml?rev=1.10&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml?rev=1.10&content-type=text/plain
diff :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml?r1=1.9&r2=1.10
Index: hb-install-x86+amd64-disk.xml
===================================================================
RCS file:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- hb-install-x86+amd64-disk.xml 1 Mar 2008 07:03:30 -0000 1.9
+++ hb-install-x86+amd64-disk.xml 1 Mar 2008 14:15:58 -0000 1.10
@@ -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/draft/hb-install-x86+amd64-disk.xml,v
1.9 2008/03/01 07:03:30 nightmorph Exp $ -->
+<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml,v
1.10 2008/03/01 14:15:58 neysx Exp $ -->
<sections>
@@ -509,69 +509,11 @@
</body>
</subsection>
-<subsection>
-<title>Filesystems?</title>
-<body>
-
-<p test="func:keyval('arch')='x86'">
-The Linux kernel supports various filesystems. We'll explain ext2, ext3,
-ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux
-systems.
-</p>
-
-<p test="func:keyval('arch')='AMD64'">
-Several filesystems are available. Some of them are found stable on the amd64
-architecture, others aren't. The following filesystems are found to be stable:
-ext2 and ext3. jfs and reiserfs may work but need more testing. If you're
-really adventurous you can try the unsupported filesystems.
-</p>
-
-<p>
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
-journaling, which means that routine ext2 filesystem checks at startup time can
-be quite time-consuming. There is now quite a selection of newer-generation
-journaled filesystems that can be checked for consistency very quickly and are
-thus generally preferred over their non-journaled counterparts. Journaled
-filesystems prevent long delays when you boot your system and your filesystem
-happens to be in an inconsistent state.
-</p>
-
-<p>
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
-journaling for fast recovery in addition to other enhanced journaling modes
like
-full data and ordered data journaling. It uses an HTree index that enables high
-performance in almost all situations. In short, ext3 is a very good and
reliable
-filesystem.
-</p>
-<p>
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall
-performance and greatly outperforms both ext2 and ext3 when dealing with small
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales
-extremely well and has metadata journaling. ReiserFS is solid and usable as
-both general-purpose filesystem and for extreme cases such as the creation of
-large filesystems, very large files and directories containing tens of
-thousands of small files.
-</p>
-
-<p>
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
-feature-set and is optimized for scalability. We only recommend using this
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and
-an uninterruptible power supply. Because XFS aggressively caches in-transit
data
-in RAM, improperly designed programs (those that don't take proper precautions
-when writing files to disk and there are quite a few of them) can lose a good
-deal of data if the system goes down unexpectedly.
-</p>
-
-<p>
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently
-become production-ready and there hasn't been a sufficient track record to
-comment positively nor negatively on its general stability at this point.
-</p>
-
-</body>
+<subsection>
+<include href="hb-install-filesystems.xml"/>
</subsection>
+
<subsection id="filesystems-apply">
<title>Applying a Filesystem to a Partition</title>
<body>
1.1 xml/htdocs/doc/en/handbook/draft/hb-install-filesystems.xml
file :
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-filesystems.xml?rev=1.1&view=markup
plain:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-filesystems.xml?rev=1.1&content-type=text/plain
Index: hb-install-filesystems.xml
===================================================================
<?xml version='1.0' encoding="UTF-8"?>
<!-- $Header:
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-filesystems.xml,v
1.1 2008/03/01 14:15:58 neysx Exp $ -->
<!DOCTYPE included SYSTEM "/dtd/guide.dtd">
<included>
<version>1</version>
<date>2008-03-01</date>
<section id="filesystemsdesc">
<title>Filesystems</title>
<body>
<p test="contains('x86 Alpha',func:keyval('arch'))">
The Linux kernel supports various filesystems. We'll explain ext2, ext3,
ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux
systems.
</p>
<p test="func:keyval('arch')='IA64'">
The Linux kernel supports various filesystems. We'll explain vfat, ext2, ext3,
ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux
systems.
</p>
<p test="func:keyval('arch')='AMD64'">
Several filesystems are available. Some of them are found stable on the amd64
architecture, others aren't. The following filesystems are found to be stable:
ext2 and ext3. jfs and reiserfs may work but need more testing. If you're
really adventurous you can try the unsupported filesystems.
</p>
<p test="func:keyval('arch')='arm'">
Several filesystems are available. Some of them are found stable on the arm
architecture, others aren't. ext2 and ext3 are found to be stable. JFS and
ReiserFS may work but need more testing. If you're really adventurous you can
try the unsupported filesystems.
</p>
<p test="func:keyval('arch')='HPPA'">
Several filesystems are available. Ext2, ext3, XFS and reiserfs are found
stable on the HPPA architecture. The others are very experimental.
</p>
<p test="func:keyval('arch')='MIPS'">
Several filesystems are available. ReiserFS, EXT2 and EXT3 are found stable on
the MIPS architectures, others are experimental.
</p>
<p test="func:keyval('arch')='PPC'">
Several filesystems are available for use on the PowerPC architecture including
ext2, ext3, ReiserFS and XFS, each with their strengths and faults.
</p>
<note test="func:keyval('arch')='PPC64'">
Several filesystems are available. ext2, ext3 and ReiserFS support is built in
the Installation CD kernels. JFS and XFS support is available through kernel
modules.
</note>
<p test="func:keyval('arch')='SPARC'">
Several filesystems are available, some are known to be stable on the
SPARC architecture. Ext2 and ext3, for example, are known to work well.
Alternate filesystems may not function correctly.
</p>
<note test="func:keyval('arch')='Alpha'">
<c>aboot</c> only supports booting from <b>ext2</b> and <b>ext3</b>
partitions.
</note>
</body>
<body>
<p test="func:keyval('arch')='IA64'">
<b>vfat</b> is the MS-DOS filesystem, updated to allow long filenames. It is
also the only filesystem type that the EFI firmware on ia64 systems
understands. The boot partition on ia64 systems should always be vfat, but for
your data partitions you should use one of the other filesystems listed below.
</p>
<p>
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata
journaling, which means that routine ext2 filesystem checks at startup time can
be quite time-consuming. There is now quite a selection of newer-generation
journaled filesystems that can be checked for consistency very quickly and are
thus generally preferred over their non-journaled counterparts. Journaled
filesystems prevent long delays when you boot your system and your filesystem
happens to be in an inconsistent state.
</p>
<p>
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata
journaling for fast recovery in addition to other enhanced journaling modes like
full data and ordered data journaling. It uses an HTree index that enables high
performance in almost all situations. In short, ext3 is a very good and reliable
filesystem. Ext3 is the recommended all-purpose all-platform filesystem.
</p>
</body>
<body test="not(func:keyval('arch')='SPARC')">
<p test="not(func:keyval('arch')='PPC')">
<b>JFS</b> is IBM's high-performance journaling filesystem. JFS is a light,
fast and reliable B+tree-based filesystem with good performance in various
conditions.
</p>
<p>
<b>ReiserFS</b> is a B+tree-based journaled filesystem that has good overall
performance, especially when dealing with many tiny files at the cost of more
CPU cycles. ReiserFS appears to be less maintained than other filesystems.
</p>
<p>
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust
feature-set and is optimized for scalability. XFS seems to be less forgiving to
various hardware problems.
</p>
</body>
</section>
</included>
--
[email protected] mailing list
