1 |
neysx 08/03/01 14:15:58 |
2 |
|
3 |
Modified: hb-install-alpha-disk.xml hb-install-arm-disk.xml |
4 |
hb-install-hppa-disk.xml hb-install-ia64-disk.xml |
5 |
hb-install-mips-disk.xml hb-install-ppc-disk.xml |
6 |
hb-install-ppc64-disk.xml hb-install-sparc-disk.xml |
7 |
hb-install-x86+amd64-disk.xml |
8 |
Added: hb-install-filesystems.xml |
9 |
Log: |
10 |
#179796 tone down ReiserFS desc, recommend ext3 and cut some cruft |
11 |
|
12 |
Revision Changes Path |
13 |
1.20 xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml |
14 |
|
15 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml?rev=1.20&view=markup |
16 |
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 |
17 |
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 |
18 |
|
19 |
Index: hb-install-alpha-disk.xml |
20 |
=================================================================== |
21 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-alpha-disk.xml,v |
22 |
retrieving revision 1.19 |
23 |
retrieving revision 1.20 |
24 |
diff -u -r1.19 -r1.20 |
25 |
--- hb-install-alpha-disk.xml 1 Mar 2008 07:03:30 -0000 1.19 |
26 |
+++ hb-install-alpha-disk.xml 1 Mar 2008 14:15:58 -0000 1.20 |
27 |
@@ -4,7 +4,7 @@ |
28 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
29 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
30 |
|
31 |
-<!-- $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 $ --> |
32 |
+<!-- $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 $ --> |
33 |
|
34 |
<sections> |
35 |
|
36 |
@@ -640,66 +640,11 @@ |
37 |
|
38 |
</body> |
39 |
</subsection> |
40 |
-<subsection> |
41 |
-<title>Filesystems?</title> |
42 |
-<body> |
43 |
- |
44 |
-<p> |
45 |
-Several filesystems are available. Most of them are found stable on the |
46 |
-Alpha architecture. |
47 |
-</p> |
48 |
- |
49 |
-<note> |
50 |
-<c>aboot</c> only supports booting from <b>ext2</b> and <b>ext3</b> |
51 |
-partitions. |
52 |
-</note> |
53 |
- |
54 |
-<p> |
55 |
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
56 |
-journaling, which means that routine ext2 filesystem checks at startup time can |
57 |
-be quite time-consuming. There is now quite a selection of newer-generation |
58 |
-journaled filesystems that can be checked for consistency very quickly and are |
59 |
-thus generally preferred over their non-journaled counterparts. Journaled |
60 |
-filesystems prevent long delays when you boot your system and your filesystem |
61 |
-happens to be in an inconsistent state. |
62 |
-</p> |
63 |
- |
64 |
-<p> |
65 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
66 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
67 |
-full data and ordered data journaling. It uses an HTree index that enables high |
68 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
69 |
-filesystem. |
70 |
-</p> |
71 |
- |
72 |
-<p> |
73 |
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
74 |
-performance and greatly outperforms both ext2 and ext3 when dealing with small |
75 |
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
76 |
-extremely well and has metadata journaling. ReiserFS is solid and usable as |
77 |
-both general-purpose filesystem and for extreme cases such as the creation of |
78 |
-large filesystems, very large files and directories containing tens of |
79 |
-thousands of small files. |
80 |
-</p> |
81 |
- |
82 |
-<p> |
83 |
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
84 |
-feature-set and is optimized for scalability. We only recommend using this |
85 |
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
86 |
-an uninterruptible power supply. Because XFS aggressively caches in-transit data |
87 |
-in RAM, improperly designed programs (those that don't take proper precautions |
88 |
-when writing files to disk and there are quite a few of them) can lose a good |
89 |
-deal of data if the system goes down unexpectedly. |
90 |
-</p> |
91 |
|
92 |
-<p> |
93 |
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
94 |
-become production-ready and there hasn't been a sufficient track record to |
95 |
-comment positively nor negatively on its general stability at this point. |
96 |
-</p> |
97 |
- |
98 |
-</body> |
99 |
+<subsection> |
100 |
+<include href="hb-install-filesystems.xml"/> |
101 |
</subsection> |
102 |
+ |
103 |
<subsection id="filesystems-apply"> |
104 |
<title>Applying a Filesystem to a Partition</title> |
105 |
<body> |
106 |
|
107 |
|
108 |
|
109 |
1.7 xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml |
110 |
|
111 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml?rev=1.7&view=markup |
112 |
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 |
113 |
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 |
114 |
|
115 |
Index: hb-install-arm-disk.xml |
116 |
=================================================================== |
117 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-arm-disk.xml,v |
118 |
retrieving revision 1.6 |
119 |
retrieving revision 1.7 |
120 |
diff -u -r1.6 -r1.7 |
121 |
--- hb-install-arm-disk.xml 1 Mar 2008 07:03:30 -0000 1.6 |
122 |
+++ hb-install-arm-disk.xml 1 Mar 2008 14:15:58 -0000 1.7 |
123 |
@@ -4,7 +4,7 @@ |
124 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
125 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
126 |
|
127 |
-<!-- $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 $ --> |
128 |
+<!-- $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 $ --> |
129 |
|
130 |
<sections> |
131 |
|
132 |
@@ -498,63 +498,11 @@ |
133 |
|
134 |
</body> |
135 |
</subsection> |
136 |
-<subsection> |
137 |
-<title>Filesystems?</title> |
138 |
-<body> |
139 |
- |
140 |
-<p> |
141 |
-Several filesystems are available. Some of them are found stable on the arm |
142 |
-architecture, others aren't. The following filesystems are found to be stable: |
143 |
-ext2 and ext3. jfs and reiserfs may work but need more testing. If you're |
144 |
-really adventurous you can try the unsupported filesystems. |
145 |
-</p> |
146 |
- |
147 |
-<p> |
148 |
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
149 |
-journaling, which means that routine ext2 filesystem checks at startup time can |
150 |
-be quite time-consuming. There is now quite a selection of newer-generation |
151 |
-journaled filesystems that can be checked for consistency very quickly and are |
152 |
-thus generally preferred over their non-journaled counterparts. Journaled |
153 |
-filesystems prevent long delays when you boot your system and your filesystem |
154 |
-happens to be in an inconsistent state. |
155 |
-</p> |
156 |
- |
157 |
-<p> |
158 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
159 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
160 |
-full data and ordered data journaling. It uses an HTree index that enables high |
161 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
162 |
-filesystem. |
163 |
-</p> |
164 |
|
165 |
-<p> |
166 |
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
167 |
-performance and greatly outperforms both ext2 and ext3 when dealing with small |
168 |
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
169 |
-extremely well and has metadata journaling. ReiserFS is solid and usable as |
170 |
-both general-purpose filesystem and for extreme cases such as the creation of |
171 |
-large filesystems, very large files and directories containing tens of |
172 |
-thousands of small files. |
173 |
-</p> |
174 |
- |
175 |
-<p> |
176 |
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
177 |
-feature-set and is optimized for scalability. We only recommend using this |
178 |
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
179 |
-an uninterruptible power supply. Because XFS aggressively caches in-transit data |
180 |
-in RAM, improperly designed programs (those that don't take proper precautions |
181 |
-when writing files to disk and there are quite a few of them) can lose a good |
182 |
-deal of data if the system goes down unexpectedly. |
183 |
-</p> |
184 |
- |
185 |
-<p> |
186 |
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
187 |
-become production-ready and there hasn't been a sufficient track record to |
188 |
-comment positively nor negatively on its general stability at this point. |
189 |
-</p> |
190 |
- |
191 |
-</body> |
192 |
+<subsection> |
193 |
+<include href="hb-install-filesystems.xml"/> |
194 |
</subsection> |
195 |
+ |
196 |
<subsection id="filesystems-apply"> |
197 |
<title>Applying a Filesystem to a Partition</title> |
198 |
<body> |
199 |
|
200 |
|
201 |
|
202 |
1.17 xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml |
203 |
|
204 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml?rev=1.17&view=markup |
205 |
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 |
206 |
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 |
207 |
|
208 |
Index: hb-install-hppa-disk.xml |
209 |
=================================================================== |
210 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-hppa-disk.xml,v |
211 |
retrieving revision 1.16 |
212 |
retrieving revision 1.17 |
213 |
diff -u -r1.16 -r1.17 |
214 |
--- hb-install-hppa-disk.xml 1 Mar 2008 07:03:30 -0000 1.16 |
215 |
+++ hb-install-hppa-disk.xml 1 Mar 2008 14:15:58 -0000 1.17 |
216 |
@@ -4,7 +4,7 @@ |
217 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
218 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
219 |
|
220 |
-<!-- $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 $ --> |
221 |
+<!-- $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 $ --> |
222 |
|
223 |
<sections> |
224 |
|
225 |
@@ -195,61 +195,11 @@ |
226 |
|
227 |
</body> |
228 |
</subsection> |
229 |
-<subsection> |
230 |
-<title>Filesystems?</title> |
231 |
-<body> |
232 |
- |
233 |
-<p> |
234 |
-Several filesystems are available. Ext2, ext3, XFS and reiserfs are found |
235 |
-stable on the HPPA architecture. The others are very experimental. |
236 |
-</p> |
237 |
- |
238 |
-<p> |
239 |
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
240 |
-journaling, which means that routine ext2 filesystem checks at startup time can |
241 |
-be quite time-consuming. There is now quite a selection of newer-generation |
242 |
-journaled filesystems that can be checked for consistency very quickly and are |
243 |
-thus generally preferred over their non-journaled counterparts. Journaled |
244 |
-filesystems prevent long delays when you boot your system and your filesystem |
245 |
-happens to be in an inconsistent state. |
246 |
-</p> |
247 |
- |
248 |
-<p> |
249 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
250 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
251 |
-full data and ordered data journaling. It uses an HTree index that enables high |
252 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
253 |
-filesystem. |
254 |
-</p> |
255 |
|
256 |
-<p> |
257 |
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
258 |
-performance and greatly outperforms both ext2 and ext3 when dealing with small |
259 |
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
260 |
-extremely well and has metadata journaling. ReiserFS is solid and usable as |
261 |
-both general-purpose filesystem and for extreme cases such as the creation of |
262 |
-large filesystems, very large files and directories containing tens of |
263 |
-thousands of small files. |
264 |
-</p> |
265 |
- |
266 |
-<p> |
267 |
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
268 |
-feature-set and is optimized for scalability. We only recommend using this |
269 |
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
270 |
-an uninterruptible power supply. Because XFS aggressively caches in-transit data |
271 |
-in RAM, improperly designed programs (those that don't take proper precautions |
272 |
-when writing files to disk and there are quite a few of them) can lose a good |
273 |
-deal of data if the system goes down unexpectedly. |
274 |
-</p> |
275 |
- |
276 |
-<p> |
277 |
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
278 |
-become production-ready and there hasn't been a sufficient track record to |
279 |
-comment positively nor negatively on its general stability at this point. |
280 |
-</p> |
281 |
- |
282 |
-</body> |
283 |
+<subsection> |
284 |
+<include href="hb-install-filesystems.xml"/> |
285 |
</subsection> |
286 |
+ |
287 |
<subsection id="filesystems-apply"> |
288 |
<title>Applying a Filesystem to a Partition</title> |
289 |
<body> |
290 |
|
291 |
|
292 |
|
293 |
1.8 xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml |
294 |
|
295 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml?rev=1.8&view=markup |
296 |
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 |
297 |
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 |
298 |
|
299 |
Index: hb-install-ia64-disk.xml |
300 |
=================================================================== |
301 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-disk.xml,v |
302 |
retrieving revision 1.7 |
303 |
retrieving revision 1.8 |
304 |
diff -u -r1.7 -r1.8 |
305 |
--- hb-install-ia64-disk.xml 1 Mar 2008 07:03:30 -0000 1.7 |
306 |
+++ hb-install-ia64-disk.xml 1 Mar 2008 14:15:58 -0000 1.8 |
307 |
@@ -4,7 +4,7 @@ |
308 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
309 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
310 |
|
311 |
-<!-- $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 $ --> |
312 |
+<!-- $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 $ --> |
313 |
|
314 |
<sections> |
315 |
|
316 |
@@ -449,69 +449,11 @@ |
317 |
|
318 |
</body> |
319 |
</subsection> |
320 |
-<subsection> |
321 |
-<title>Filesystems?</title> |
322 |
-<body> |
323 |
- |
324 |
-<p> |
325 |
-The Linux kernel supports various filesystems. We'll explain vfat, ext2, ext3, |
326 |
-ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux |
327 |
-systems. |
328 |
-</p> |
329 |
- |
330 |
-<p> |
331 |
-<b>vfat</b> is the MS-DOS filesystem, updated to allow long filenames. It is |
332 |
-also the only filesystem type that the EFI firmware on ia64 systems understand. |
333 |
-The boot partition on ia64 systems should always be vfat, but for your data |
334 |
-partitions you should use one of the other filesystems listed below. |
335 |
-</p> |
336 |
- |
337 |
-<p> |
338 |
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
339 |
-journaling, which means that routine ext2 filesystem checks at startup time can |
340 |
-be quite time-consuming. There is now quite a selection of newer-generation |
341 |
-journaled filesystems that can be checked for consistency very quickly and are |
342 |
-thus generally preferred over their non-journaled counterparts. Journaled |
343 |
-filesystems prevent long delays when you boot your system and your filesystem |
344 |
-happens to be in an inconsistent state. |
345 |
-</p> |
346 |
- |
347 |
-<p> |
348 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
349 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
350 |
-full data and ordered data journaling. It uses an HTree index that enables high |
351 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
352 |
-filesystem. |
353 |
-</p> |
354 |
- |
355 |
-<p> |
356 |
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
357 |
-performance and greatly outperforms both ext2 and ext3 when dealing with small |
358 |
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
359 |
-extremely well and has metadata journaling. ReiserFS is solid and usable as |
360 |
-both general-purpose filesystem and for extreme cases such as the creation of |
361 |
-large filesystems, very large files and directories containing tens of |
362 |
-thousands of small files. |
363 |
-</p> |
364 |
- |
365 |
-<p> |
366 |
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
367 |
-feature-set and is optimized for scalability. We only recommend using this |
368 |
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
369 |
-an uninterruptible power supply. Because XFS aggressively caches in-transit data |
370 |
-in RAM, improperly designed programs (those that don't take proper precautions |
371 |
-when writing files to disk and there are quite a few of them) can lose a good |
372 |
-deal of data if the system goes down unexpectedly. |
373 |
-</p> |
374 |
|
375 |
-<p> |
376 |
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
377 |
-become production-ready and there hasn't been a sufficient track record to |
378 |
-comment positively nor negatively on its general stability at this point. |
379 |
-</p> |
380 |
- |
381 |
-</body> |
382 |
+<subsection> |
383 |
+<include href="hb-install-filesystems.xml"/> |
384 |
</subsection> |
385 |
+ |
386 |
<subsection id="filesystems-apply"> |
387 |
<title>Applying a Filesystem to a Partition</title> |
388 |
<body> |
389 |
|
390 |
|
391 |
|
392 |
1.19 xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml |
393 |
|
394 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml?rev=1.19&view=markup |
395 |
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 |
396 |
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 |
397 |
|
398 |
Index: hb-install-mips-disk.xml |
399 |
=================================================================== |
400 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-mips-disk.xml,v |
401 |
retrieving revision 1.18 |
402 |
retrieving revision 1.19 |
403 |
diff -u -r1.18 -r1.19 |
404 |
--- hb-install-mips-disk.xml 1 Mar 2008 07:03:30 -0000 1.18 |
405 |
+++ hb-install-mips-disk.xml 1 Mar 2008 14:15:58 -0000 1.19 |
406 |
@@ -4,7 +4,7 @@ |
407 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
408 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
409 |
|
410 |
-<!-- $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 $ --> |
411 |
+<!-- $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 $ --> |
412 |
|
413 |
<sections> |
414 |
|
415 |
@@ -536,61 +536,11 @@ |
416 |
|
417 |
</body> |
418 |
</subsection> |
419 |
-<subsection> |
420 |
-<title>Filesystems?</title> |
421 |
-<body> |
422 |
- |
423 |
-<p> |
424 |
-Several filesystems are available. ReiserFS, EXT2 and EXT3 are found stable on |
425 |
-the MIPS architectures, others are experimental. |
426 |
-</p> |
427 |
- |
428 |
-<p> |
429 |
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
430 |
-journaling, which means that routine ext2 filesystem checks at startup time can |
431 |
-be quite time-consuming. There is now quite a selection of newer-generation |
432 |
-journaled filesystems that can be checked for consistency very quickly and are |
433 |
-thus generally preferred over their non-journaled counterparts. Journaled |
434 |
-filesystems prevent long delays when you boot your system and your filesystem |
435 |
-happens to be in an inconsistent state. |
436 |
-</p> |
437 |
- |
438 |
-<p> |
439 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
440 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
441 |
-full data and ordered data journaling. It uses an HTree index that enables high |
442 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
443 |
-filesystem. |
444 |
-</p> |
445 |
|
446 |
-<p> |
447 |
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
448 |
-performance and greatly outperforms both ext2 and ext3 when dealing with small |
449 |
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
450 |
-extremely well and has metadata journaling. ReiserFS is solid and usable as |
451 |
-both general-purpose filesystem and for extreme cases such as the creation of |
452 |
-large filesystems, very large files and directories containing tens of |
453 |
-thousands of small files. |
454 |
-</p> |
455 |
- |
456 |
-<p> |
457 |
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
458 |
-feature-set and is optimized for scalability. We only recommend using this |
459 |
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
460 |
-an uninterruptible power supply. Because XFS aggressively caches in-transit |
461 |
-data in RAM, improperly designed programs (those that don't take proper |
462 |
-precautions when writing files to disk and there are quite a few of them) can |
463 |
-lose a good deal of data if the system goes down unexpectedly. |
464 |
-</p> |
465 |
- |
466 |
-<p> |
467 |
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
468 |
-become production-ready and there hasn't been a sufficient track record to |
469 |
-comment positively nor negatively on its general stability at this point. |
470 |
-</p> |
471 |
- |
472 |
-</body> |
473 |
+<subsection> |
474 |
+<include href="hb-install-filesystems.xml"/> |
475 |
</subsection> |
476 |
+ |
477 |
<subsection id="filesystems-apply"> |
478 |
<title>Applying a Filesystem to a Partition</title> |
479 |
<body> |
480 |
|
481 |
|
482 |
|
483 |
1.30 xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml |
484 |
|
485 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml?rev=1.30&view=markup |
486 |
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 |
487 |
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 |
488 |
|
489 |
Index: hb-install-ppc-disk.xml |
490 |
=================================================================== |
491 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc-disk.xml,v |
492 |
retrieving revision 1.29 |
493 |
retrieving revision 1.30 |
494 |
diff -u -r1.29 -r1.30 |
495 |
--- hb-install-ppc-disk.xml 1 Mar 2008 07:03:30 -0000 1.29 |
496 |
+++ hb-install-ppc-disk.xml 1 Mar 2008 14:15:58 -0000 1.30 |
497 |
@@ -4,7 +4,7 @@ |
498 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
499 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
500 |
|
501 |
-<!-- $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 $ --> |
502 |
+<!-- $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 $ --> |
503 |
|
504 |
<sections> |
505 |
|
506 |
@@ -502,53 +502,11 @@ |
507 |
|
508 |
</body> |
509 |
</subsection> |
510 |
-<subsection> |
511 |
-<title>Filesystems?</title> |
512 |
-<body> |
513 |
- |
514 |
-<p> |
515 |
-Several filesystems are available for use on the PowerPC architecture including |
516 |
-ext2, ext3, ReiserFS and XFS, each with their strengths and faults. |
517 |
-</p> |
518 |
- |
519 |
-<p> |
520 |
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
521 |
-journaling, which means that routine ext2 filesystem checks at startup time can |
522 |
-be quite time-consuming. There is now quite a selection of journaled |
523 |
-filesystems that can be checked for consistency very quickly and are thus |
524 |
-generally preferred over their non-journaled counterparts. |
525 |
-</p> |
526 |
- |
527 |
-<p> |
528 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
529 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
530 |
-full data and ordered data journaling. It uses an HTree index that enables high |
531 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
532 |
-filesystem. |
533 |
-</p> |
534 |
- |
535 |
-<p> |
536 |
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
537 |
-performance and greatly outperforms both ext2 and ext3 when dealing with small |
538 |
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
539 |
-extremely well and has metadata journaling. ReiserFS is solid and usable as |
540 |
-both general-purpose filesystem and for extreme cases such as the creation of |
541 |
-large filesystems, very large files and directories containing tens of |
542 |
-thousands of small files. |
543 |
-</p> |
544 |
- |
545 |
-<p> |
546 |
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
547 |
-feature-set and is optimized for scalability. We only recommend using this |
548 |
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
549 |
-an uninterruptible power supply. Because XFS aggressively caches in-transit data |
550 |
-in RAM, improperly designed programs (those that don't take proper precautions |
551 |
-when writing files to disk and there are quite a few of them) can lose a good |
552 |
-deal of data if the system goes down unexpectedly. |
553 |
-</p> |
554 |
|
555 |
-</body> |
556 |
+<subsection> |
557 |
+<include href="hb-install-filesystems.xml"/> |
558 |
</subsection> |
559 |
+ |
560 |
<subsection> |
561 |
<title>Activating the Swap Partition</title> |
562 |
<body> |
563 |
|
564 |
|
565 |
|
566 |
1.23 xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml |
567 |
|
568 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml?rev=1.23&view=markup |
569 |
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 |
570 |
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 |
571 |
|
572 |
Index: hb-install-ppc64-disk.xml |
573 |
=================================================================== |
574 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ppc64-disk.xml,v |
575 |
retrieving revision 1.22 |
576 |
retrieving revision 1.23 |
577 |
diff -u -r1.22 -r1.23 |
578 |
--- hb-install-ppc64-disk.xml 1 Mar 2008 07:03:30 -0000 1.22 |
579 |
+++ hb-install-ppc64-disk.xml 1 Mar 2008 14:15:58 -0000 1.23 |
580 |
@@ -4,7 +4,7 @@ |
581 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
582 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
583 |
|
584 |
-<!-- $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 $ --> |
585 |
+<!-- $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 $ --> |
586 |
|
587 |
<sections> |
588 |
|
589 |
@@ -598,62 +598,11 @@ |
590 |
|
591 |
</body> |
592 |
</subsection> |
593 |
-<subsection> |
594 |
-<title>Filesystems?</title> |
595 |
-<body> |
596 |
- |
597 |
-<note> |
598 |
-Several filesystems are available. ext2, ext3 and ReiserFS support is built in |
599 |
-the Installation CD kernels. JFS and XFS support is available through kernel |
600 |
-modules. |
601 |
-</note> |
602 |
- |
603 |
-<p> |
604 |
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
605 |
-journaling, which means that routine ext2 filesystem checks at startup time can |
606 |
-be quite time-consuming. There is now quite a selection of newer-generation |
607 |
-journaled filesystems that can be checked for consistency very quickly and are |
608 |
-thus generally preferred over their non-journaled counterparts. Journaled |
609 |
-filesystems prevent long delays when you boot your system and your filesystem |
610 |
-happens to be in an inconsistent state. |
611 |
-</p> |
612 |
- |
613 |
-<p> |
614 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
615 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
616 |
-full data and ordered data journaling. It uses an HTree index that enables high |
617 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
618 |
-filesystem. |
619 |
-</p> |
620 |
|
621 |
-<p> |
622 |
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
623 |
-performance and greatly outperforms both ext2 and ext3 when dealing with small |
624 |
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
625 |
-extremely well and has metadata journaling. ReiserFS is solid and usable as |
626 |
-both general-purpose filesystem and for extreme cases such as the creation of |
627 |
-large filesystems, very large files and directories containing tens of |
628 |
-thousands of small files. |
629 |
-</p> |
630 |
- |
631 |
-<p> |
632 |
-<b>XFS</b> is a filesystem with metadata journaling that is fully supported |
633 |
-under Gentoo Linux's xfs-sources kernel. It comes with a robust feature-set and |
634 |
-is optimized for scalability. We only recommend using this filesystem on Linux |
635 |
-systems with high-end SCSI and/or fibre channel storage and a uninterruptible |
636 |
-power supply. Because XFS aggressively caches in-transit data in RAM, improperly |
637 |
-designed programs (those that don't take proper precautions when writing files |
638 |
-to disk and there are quite a few of them) can lose a good deal of data if the |
639 |
-system goes down unexpectedly. |
640 |
-</p> |
641 |
- |
642 |
-<p> |
643 |
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
644 |
-become production-ready. |
645 |
-</p> |
646 |
- |
647 |
-</body> |
648 |
+<subsection> |
649 |
+<include href="hb-install-filesystems.xml"/> |
650 |
</subsection> |
651 |
+ |
652 |
<subsection id="filesystems-apply"> |
653 |
<title>Applying a Filesystem to a Partition</title> |
654 |
<body> |
655 |
|
656 |
|
657 |
|
658 |
1.22 xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml |
659 |
|
660 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml?rev=1.22&view=markup |
661 |
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 |
662 |
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 |
663 |
|
664 |
Index: hb-install-sparc-disk.xml |
665 |
=================================================================== |
666 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-sparc-disk.xml,v |
667 |
retrieving revision 1.21 |
668 |
retrieving revision 1.22 |
669 |
diff -u -r1.21 -r1.22 |
670 |
--- hb-install-sparc-disk.xml 1 Mar 2008 07:03:30 -0000 1.21 |
671 |
+++ hb-install-sparc-disk.xml 1 Mar 2008 14:15:58 -0000 1.22 |
672 |
@@ -4,7 +4,7 @@ |
673 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
674 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
675 |
|
676 |
-<!-- $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 $ --> |
677 |
+<!-- $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 $ --> |
678 |
|
679 |
<sections> |
680 |
|
681 |
@@ -486,36 +486,11 @@ |
682 |
|
683 |
</body> |
684 |
</subsection> |
685 |
-<subsection> |
686 |
-<title>Filesystems?</title> |
687 |
-<body> |
688 |
- |
689 |
-<p> |
690 |
-Several filesystems are available, some are known to be stable on the |
691 |
-SPARC architecture. Ext2 and ext3, for example, are known to work well. |
692 |
-Alternate filesystems may not function correctly. |
693 |
-</p> |
694 |
- |
695 |
-<p> |
696 |
-<b>ext2</b> is the tried-and-true Linux filesystem. It does not support |
697 |
-journaling, which means that periodic checks of ext2 filesystems at startup |
698 |
-can be quite time-consuming. There is quite a selection of newer-generation |
699 |
-journaled filesystems that can be checked for consistency very quickly at |
700 |
-startup, and are therefore generally preferred over their non-journaled |
701 |
-counterparts. In general, journaled filesystems prevent long delays when a |
702 |
-system is booted and the filesystem is in an inconsistent state. |
703 |
-</p> |
704 |
- |
705 |
-<p> |
706 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
707 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
708 |
-full data and ordered data journaling. It uses an HTree index that enables high |
709 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
710 |
-filesystem. |
711 |
-</p> |
712 |
|
713 |
-</body> |
714 |
+<subsection> |
715 |
+<include href="hb-install-filesystems.xml"/> |
716 |
</subsection> |
717 |
+ |
718 |
<subsection id="filesystems-apply"> |
719 |
<title>Applying a Filesystem to a Partition</title> |
720 |
<body> |
721 |
|
722 |
|
723 |
|
724 |
1.10 xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml |
725 |
|
726 |
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 |
727 |
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 |
728 |
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 |
729 |
|
730 |
Index: hb-install-x86+amd64-disk.xml |
731 |
=================================================================== |
732 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-x86+amd64-disk.xml,v |
733 |
retrieving revision 1.9 |
734 |
retrieving revision 1.10 |
735 |
diff -u -r1.9 -r1.10 |
736 |
--- hb-install-x86+amd64-disk.xml 1 Mar 2008 07:03:30 -0000 1.9 |
737 |
+++ hb-install-x86+amd64-disk.xml 1 Mar 2008 14:15:58 -0000 1.10 |
738 |
@@ -4,7 +4,7 @@ |
739 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
740 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
741 |
|
742 |
-<!-- $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 $ --> |
743 |
+<!-- $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 $ --> |
744 |
|
745 |
<sections> |
746 |
|
747 |
@@ -509,69 +509,11 @@ |
748 |
|
749 |
</body> |
750 |
</subsection> |
751 |
-<subsection> |
752 |
-<title>Filesystems?</title> |
753 |
-<body> |
754 |
- |
755 |
-<p test="func:keyval('arch')='x86'"> |
756 |
-The Linux kernel supports various filesystems. We'll explain ext2, ext3, |
757 |
-ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux |
758 |
-systems. |
759 |
-</p> |
760 |
- |
761 |
-<p test="func:keyval('arch')='AMD64'"> |
762 |
-Several filesystems are available. Some of them are found stable on the amd64 |
763 |
-architecture, others aren't. The following filesystems are found to be stable: |
764 |
-ext2 and ext3. jfs and reiserfs may work but need more testing. If you're |
765 |
-really adventurous you can try the unsupported filesystems. |
766 |
-</p> |
767 |
- |
768 |
-<p> |
769 |
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
770 |
-journaling, which means that routine ext2 filesystem checks at startup time can |
771 |
-be quite time-consuming. There is now quite a selection of newer-generation |
772 |
-journaled filesystems that can be checked for consistency very quickly and are |
773 |
-thus generally preferred over their non-journaled counterparts. Journaled |
774 |
-filesystems prevent long delays when you boot your system and your filesystem |
775 |
-happens to be in an inconsistent state. |
776 |
-</p> |
777 |
- |
778 |
-<p> |
779 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
780 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
781 |
-full data and ordered data journaling. It uses an HTree index that enables high |
782 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
783 |
-filesystem. |
784 |
-</p> |
785 |
|
786 |
-<p> |
787 |
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
788 |
-performance and greatly outperforms both ext2 and ext3 when dealing with small |
789 |
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
790 |
-extremely well and has metadata journaling. ReiserFS is solid and usable as |
791 |
-both general-purpose filesystem and for extreme cases such as the creation of |
792 |
-large filesystems, very large files and directories containing tens of |
793 |
-thousands of small files. |
794 |
-</p> |
795 |
- |
796 |
-<p> |
797 |
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
798 |
-feature-set and is optimized for scalability. We only recommend using this |
799 |
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
800 |
-an uninterruptible power supply. Because XFS aggressively caches in-transit data |
801 |
-in RAM, improperly designed programs (those that don't take proper precautions |
802 |
-when writing files to disk and there are quite a few of them) can lose a good |
803 |
-deal of data if the system goes down unexpectedly. |
804 |
-</p> |
805 |
- |
806 |
-<p> |
807 |
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
808 |
-become production-ready and there hasn't been a sufficient track record to |
809 |
-comment positively nor negatively on its general stability at this point. |
810 |
-</p> |
811 |
- |
812 |
-</body> |
813 |
+<subsection> |
814 |
+<include href="hb-install-filesystems.xml"/> |
815 |
</subsection> |
816 |
+ |
817 |
<subsection id="filesystems-apply"> |
818 |
<title>Applying a Filesystem to a Partition</title> |
819 |
<body> |
820 |
|
821 |
|
822 |
|
823 |
1.1 xml/htdocs/doc/en/handbook/draft/hb-install-filesystems.xml |
824 |
|
825 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-filesystems.xml?rev=1.1&view=markup |
826 |
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 |
827 |
|
828 |
Index: hb-install-filesystems.xml |
829 |
=================================================================== |
830 |
<?xml version='1.0' encoding="UTF-8"?> |
831 |
<!-- $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 $ --> |
832 |
<!DOCTYPE included SYSTEM "/dtd/guide.dtd"> |
833 |
|
834 |
<included> |
835 |
|
836 |
<version>1</version> |
837 |
<date>2008-03-01</date> |
838 |
|
839 |
<section id="filesystemsdesc"> |
840 |
<title>Filesystems</title> |
841 |
<body> |
842 |
|
843 |
<p test="contains('x86 Alpha',func:keyval('arch'))"> |
844 |
The Linux kernel supports various filesystems. We'll explain ext2, ext3, |
845 |
ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux |
846 |
systems. |
847 |
</p> |
848 |
|
849 |
<p test="func:keyval('arch')='IA64'"> |
850 |
The Linux kernel supports various filesystems. We'll explain vfat, ext2, ext3, |
851 |
ReiserFS, XFS and JFS as these are the most commonly used filesystems on Linux |
852 |
systems. |
853 |
</p> |
854 |
|
855 |
<p test="func:keyval('arch')='AMD64'"> |
856 |
Several filesystems are available. Some of them are found stable on the amd64 |
857 |
architecture, others aren't. The following filesystems are found to be stable: |
858 |
ext2 and ext3. jfs and reiserfs may work but need more testing. If you're |
859 |
really adventurous you can try the unsupported filesystems. |
860 |
</p> |
861 |
|
862 |
<p test="func:keyval('arch')='arm'"> |
863 |
Several filesystems are available. Some of them are found stable on the arm |
864 |
architecture, others aren't. ext2 and ext3 are found to be stable. JFS and |
865 |
ReiserFS may work but need more testing. If you're really adventurous you can |
866 |
try the unsupported filesystems. |
867 |
</p> |
868 |
|
869 |
<p test="func:keyval('arch')='HPPA'"> |
870 |
Several filesystems are available. Ext2, ext3, XFS and reiserfs are found |
871 |
stable on the HPPA architecture. The others are very experimental. |
872 |
</p> |
873 |
|
874 |
<p test="func:keyval('arch')='MIPS'"> |
875 |
Several filesystems are available. ReiserFS, EXT2 and EXT3 are found stable on |
876 |
the MIPS architectures, others are experimental. |
877 |
</p> |
878 |
|
879 |
<p test="func:keyval('arch')='PPC'"> |
880 |
Several filesystems are available for use on the PowerPC architecture including |
881 |
ext2, ext3, ReiserFS and XFS, each with their strengths and faults. |
882 |
</p> |
883 |
|
884 |
<note test="func:keyval('arch')='PPC64'"> |
885 |
Several filesystems are available. ext2, ext3 and ReiserFS support is built in |
886 |
the Installation CD kernels. JFS and XFS support is available through kernel |
887 |
modules. |
888 |
</note> |
889 |
|
890 |
<p test="func:keyval('arch')='SPARC'"> |
891 |
Several filesystems are available, some are known to be stable on the |
892 |
SPARC architecture. Ext2 and ext3, for example, are known to work well. |
893 |
Alternate filesystems may not function correctly. |
894 |
</p> |
895 |
|
896 |
<note test="func:keyval('arch')='Alpha'"> |
897 |
<c>aboot</c> only supports booting from <b>ext2</b> and <b>ext3</b> |
898 |
partitions. |
899 |
</note> |
900 |
|
901 |
</body> |
902 |
<body> |
903 |
|
904 |
<p test="func:keyval('arch')='IA64'"> |
905 |
<b>vfat</b> is the MS-DOS filesystem, updated to allow long filenames. It is |
906 |
also the only filesystem type that the EFI firmware on ia64 systems |
907 |
understands. The boot partition on ia64 systems should always be vfat, but for |
908 |
your data partitions you should use one of the other filesystems listed below. |
909 |
</p> |
910 |
|
911 |
<p> |
912 |
<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
913 |
journaling, which means that routine ext2 filesystem checks at startup time can |
914 |
be quite time-consuming. There is now quite a selection of newer-generation |
915 |
journaled filesystems that can be checked for consistency very quickly and are |
916 |
thus generally preferred over their non-journaled counterparts. Journaled |
917 |
filesystems prevent long delays when you boot your system and your filesystem |
918 |
happens to be in an inconsistent state. |
919 |
</p> |
920 |
|
921 |
<p> |
922 |
<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
923 |
journaling for fast recovery in addition to other enhanced journaling modes like |
924 |
full data and ordered data journaling. It uses an HTree index that enables high |
925 |
performance in almost all situations. In short, ext3 is a very good and reliable |
926 |
filesystem. Ext3 is the recommended all-purpose all-platform filesystem. |
927 |
</p> |
928 |
|
929 |
</body> |
930 |
<body test="not(func:keyval('arch')='SPARC')"> |
931 |
|
932 |
<p test="not(func:keyval('arch')='PPC')"> |
933 |
<b>JFS</b> is IBM's high-performance journaling filesystem. JFS is a light, |
934 |
fast and reliable B+tree-based filesystem with good performance in various |
935 |
conditions. |
936 |
</p> |
937 |
|
938 |
<p> |
939 |
<b>ReiserFS</b> is a B+tree-based journaled filesystem that has good overall |
940 |
performance, especially when dealing with many tiny files at the cost of more |
941 |
CPU cycles. ReiserFS appears to be less maintained than other filesystems. |
942 |
</p> |
943 |
|
944 |
<p> |
945 |
<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
946 |
feature-set and is optimized for scalability. XFS seems to be less forgiving to |
947 |
various hardware problems. |
948 |
</p> |
949 |
|
950 |
</body> |
951 |
</section> |
952 |
</included> |
953 |
|
954 |
|
955 |
|
956 |
-- |
957 |
gentoo-doc-cvs@l.g.o mailing list |