1 |
swift 13/12/17 10:15:36 |
2 |
|
3 |
Modified: hb-install-filesystems.xml |
4 |
Log: |
5 |
Bug #489782 - Duplicate instructions for ext2, ext3 and possibly ext4 now separate |
6 |
|
7 |
Revision Changes Path |
8 |
1.14 xml/htdocs/doc/en/handbook/hb-install-filesystems.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-filesystems.xml?rev=1.14&view=markup |
11 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-filesystems.xml?rev=1.14&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-filesystems.xml?r1=1.13&r2=1.14 |
13 |
|
14 |
Index: hb-install-filesystems.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-filesystems.xml,v |
17 |
retrieving revision 1.13 |
18 |
retrieving revision 1.14 |
19 |
diff -u -r1.13 -r1.14 |
20 |
--- hb-install-filesystems.xml 23 Feb 2013 18:38:22 -0000 1.13 |
21 |
+++ hb-install-filesystems.xml 17 Dec 2013 10:15:36 -0000 1.14 |
22 |
@@ -1,11 +1,11 @@ |
23 |
<?xml version='1.0' encoding="UTF-8"?> |
24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-filesystems.xml,v 1.13 2013/02/23 18:38:22 swift Exp $ --> |
25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-filesystems.xml,v 1.14 2013/12/17 10:15:36 swift Exp $ --> |
26 |
<!DOCTYPE included SYSTEM "/dtd/guide.dtd"> |
27 |
|
28 |
<included> |
29 |
|
30 |
-<version>11</version> |
31 |
-<date>2013-02-23</date> |
32 |
+<version>12</version> |
33 |
+<date>2013-12-17</date> |
34 |
|
35 |
<section id="filesystemsdesc"> |
36 |
<title>Filesystems</title> |
37 |
@@ -86,14 +86,7 @@ |
38 |
journaled filesystems that can be checked for consistency very quickly and are |
39 |
thus generally preferred over their non-journaled counterparts. Journaled |
40 |
filesystems prevent long delays when you boot your system and your filesystem |
41 |
-happens to be in an inconsistent state. If you intend to install Gentoo on a |
42 |
-very small disk (less than 4GB), then you'll need to tell ext2 to reserve enough |
43 |
-inodes when you create the filesystem. The <c>mke2fs</c> application uses the |
44 |
-"bytes-per-inode" setting to calculate how many inodes a file system should have. |
45 |
-By running <c>mke2fs -T small /dev/<device></c> the number of inodes will |
46 |
-generally quadruple for a given file system as its "bytes-per-inode" reduces from |
47 |
-one every 16kB to one every 4kB. You can tune this even further by using |
48 |
-<c>mke2fs -i <ratio> /dev/<device></c>. |
49 |
+happens to be in an inconsistent state. |
50 |
</p> |
51 |
|
52 |
<p> |
53 |
@@ -101,14 +94,7 @@ |
54 |
journaling for fast recovery in addition to other enhanced journaling modes like |
55 |
full data and ordered data journaling. It uses an HTree index that enables high |
56 |
performance in almost all situations. In short, ext3 is a very good and |
57 |
-reliable filesystem. If you intend to install Gentoo on a |
58 |
-very small disk (less than 4GB), then you'll need to tell ext3 to reserve enough |
59 |
-inodes when you create the filesystem. The <c>mke2fs</c> application uses the |
60 |
-"bytes-per-inode" setting to calculate how many inodes a file system should have. |
61 |
-By running <c>mke2fs -j -T small /dev/<device></c> the number of inodes will |
62 |
-generally quadruple for a given file system as its "bytes-per-inode" reduces from |
63 |
-one every 16kB to one every 4kB. You can tune this even further by using |
64 |
-<c>mke2fs -j -i <ratio> /dev/<device></c>. |
65 |
+reliable filesystem. |
66 |
</p> |
67 |
|
68 |
<p test="contains('x86 Alpha MIPS AMD64 arm IA64 SPARC HPPA PPC PPC64',func:keyval('arch'))"> |
69 |
@@ -125,6 +111,19 @@ |
70 |
filesystem. Ext4 is the recommended all-purpose all-platform filesystem. |
71 |
</p> |
72 |
|
73 |
+<p> |
74 |
+If you intend to install Gentoo on a very small disk (less than 4GB), then you'll |
75 |
+need to tell ext2, ext3 or ext4 (if available) to reserve enough inodes when you |
76 |
+create the filesystem. The <c>mke2fs</c> application uses the "bytes-per-inode" |
77 |
+setting to calculate how many inodes a file system should have. By running |
78 |
+<c>mke2fs -T small /dev/<device></c> (ext2) or <c>mke2fs -j -T small |
79 |
+/dev/<device></c> (ext3/ext4) the number of inodes will generally |
80 |
+quadruple for a given file system as its "bytes-per-inode" reduces from |
81 |
+one every 16kB to one every 4kB. You can tune this even further by using |
82 |
+<c>mke2fs -i <ratio> /dev/<device></c> (ext2) or <c>mke2fs -j |
83 |
+-i <ratio> /dev/<device></c> (ext3/ext4). |
84 |
+</p> |
85 |
+ |
86 |
</body> |
87 |
<body test="not(func:keyval('arch')='SPARC')"> |