1 |
neysx 08/03/01 14:15:57 |
2 |
|
3 |
Modified: hb-install-hppa-disk.xml hb-install-ppc-disk.xml |
4 |
hb-install-ppc64-disk.xml hb-install-sparc-disk.xml |
5 |
Log: |
6 |
#179796 tone down ReiserFS desc, recommend ext3 and cut some cruft |
7 |
|
8 |
Revision Changes Path |
9 |
1.4 xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-disk.xml |
10 |
|
11 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-disk.xml?rev=1.4&view=markup |
12 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-disk.xml?rev=1.4&content-type=text/plain |
13 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-disk.xml?r1=1.3&r2=1.4 |
14 |
|
15 |
Index: hb-install-hppa-disk.xml |
16 |
=================================================================== |
17 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-disk.xml,v |
18 |
retrieving revision 1.3 |
19 |
retrieving revision 1.4 |
20 |
diff -u -r1.3 -r1.4 |
21 |
--- hb-install-hppa-disk.xml 1 Mar 2008 07:05:42 -0000 1.3 |
22 |
+++ hb-install-hppa-disk.xml 1 Mar 2008 14:15:57 -0000 1.4 |
23 |
@@ -4,12 +4,12 @@ |
24 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
25 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
26 |
|
27 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-disk.xml,v 1.3 2008/03/01 07:05:42 nightmorph Exp $ --> |
28 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-hppa-disk.xml,v 1.4 2008/03/01 14:15:57 neysx Exp $ --> |
29 |
|
30 |
<sections> |
31 |
|
32 |
<version>9.0</version> |
33 |
-<date>2008-02-29</date> |
34 |
+<date>2008-03-01</date> |
35 |
|
36 |
<section> |
37 |
<title>Introduction to Block Devices</title> |
38 |
@@ -18,11 +18,11 @@ |
39 |
<body> |
40 |
|
41 |
<p> |
42 |
-We'll take a good look at disk-oriented aspects of Gentoo Linux |
43 |
-and Linux in general, including Linux filesystems, partitions and block devices. |
44 |
-Then, once you're familiar with the ins and outs of disks and filesystems, |
45 |
-you'll be guided through the process of setting up partitions and filesystems |
46 |
-for your Gentoo Linux installation. |
47 |
+We'll take a good look at disk-oriented aspects of Gentoo Linux and Linux in |
48 |
+general, including Linux filesystems, partitions and block devices. Then, once |
49 |
+you're familiar with the ins and outs of disks and filesystems, you'll be |
50 |
+guided through the process of setting up partitions and filesystems for your |
51 |
+Gentoo Linux installation. |
52 |
</p> |
53 |
|
54 |
<p> |
55 |
@@ -37,9 +37,9 @@ |
56 |
|
57 |
<p> |
58 |
The block devices above represent an abstract interface to the disk. User |
59 |
-programs can use these block devices to interact with your disk without worrying |
60 |
-about whether your drives are IDE, SCSI or something else. The program can |
61 |
-simply address the storage on the disk as a bunch of contiguous, |
62 |
+programs can use these block devices to interact with your disk without |
63 |
+worrying about whether your drives are IDE, SCSI or something else. The program |
64 |
+can simply address the storage on the disk as a bunch of contiguous, |
65 |
randomly-accessible 512-byte blocks. |
66 |
</p> |
67 |
|
68 |
@@ -52,8 +52,8 @@ |
69 |
<p> |
70 |
Although it is theoretically possible to use a full disk to house your Linux |
71 |
system, this is almost never done in practice. Instead, full disk block devices |
72 |
-are split up in smaller, more manageable block devices. On most systems, |
73 |
-these are called <e>partitions</e>. Other architectures use a similar technique, |
74 |
+are split up in smaller, more manageable block devices. On most systems, these |
75 |
+are called <e>partitions</e>. Other architectures use a similar technique, |
76 |
called <e>slices</e>. |
77 |
</p> |
78 |
|
79 |
@@ -70,14 +70,14 @@ |
80 |
The number of partitions is highly dependent on your environment. For instance, |
81 |
if you have lots of users, you will most likely want to have your |
82 |
<path>/home</path> separate as it increases security and makes backups easier. |
83 |
-If you are installing Gentoo to perform as a mailserver, your |
84 |
-<path>/var</path> should be separate as all mails are stored inside |
85 |
-<path>/var</path>. A good choice of filesystem will then maximise your |
86 |
-performance. Gameservers will have a separate <path>/opt</path> as most gaming |
87 |
-servers are installed there. The reason is similar for <path>/home</path>: |
88 |
-security and backups. You will definitely want to keep <path>/usr</path> big: |
89 |
-not only will it contain the majority of applications, the Portage tree alone |
90 |
-takes around 500 Mbyte excluding the various sources that are stored in it. |
91 |
+If you are installing Gentoo to perform as a mailserver, your <path>/var</path> |
92 |
+should be separate as all mails are stored inside <path>/var</path>. A good |
93 |
+choice of filesystem will then maximise your performance. Gameservers will have |
94 |
+a separate <path>/opt</path> as most gaming servers are installed there. The |
95 |
+reason is similar for <path>/home</path>: security and backups. You will |
96 |
+definitely want to keep <path>/usr</path> big: not only will it contain the |
97 |
+majority of applications, the Portage tree alone takes around 500 Mbyte |
98 |
+excluding the various sources that are stored in it. |
99 |
</p> |
100 |
|
101 |
<p> |
102 |
@@ -195,61 +195,11 @@ |
103 |
|
104 |
</body> |
105 |
</subsection> |
106 |
-<subsection> |
107 |
-<title>Filesystems?</title> |
108 |
-<body> |
109 |
|
110 |
-<p> |
111 |
-Several filesystems are available. Ext2, ext3, XFS and reiserfs are found stable |
112 |
-on the HPPA architecture. The others are very experimental. |
113 |
-</p> |
114 |
- |
115 |
-<p> |
116 |
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
117 |
-journaling, which means that routine ext2 filesystem checks at startup time can |
118 |
-be quite time-consuming. There is now quite a selection of newer-generation |
119 |
-journaled filesystems that can be checked for consistency very quickly and are |
120 |
-thus generally preferred over their non-journaled counterparts. Journaled |
121 |
-filesystems prevent long delays when you boot your system and your filesystem |
122 |
-happens to be in an inconsistent state. |
123 |
-</p> |
124 |
- |
125 |
-<p> |
126 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
127 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
128 |
-full data and ordered data journaling. It uses an HTree index that enables high |
129 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
130 |
-filesystem. |
131 |
-</p> |
132 |
- |
133 |
-<p> |
134 |
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
135 |
-performance and greatly outperforms both ext2 and ext3 when dealing with small |
136 |
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
137 |
-extremely well and has metadata journaling. ReiserFS is solid and usable as |
138 |
-both general-purpose filesystem and for extreme cases such as the creation of |
139 |
-large filesystems, very large files and directories containing tens of |
140 |
-thousands of small files. |
141 |
-</p> |
142 |
- |
143 |
-<p> |
144 |
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
145 |
-feature-set and is optimized for scalability. We only recommend using this |
146 |
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
147 |
-an uninterruptible power supply. Because XFS aggressively caches in-transit data |
148 |
-in RAM, improperly designed programs (those that don't take proper precautions |
149 |
-when writing files to disk and there are quite a few of them) can lose a good |
150 |
-deal of data if the system goes down unexpectedly. |
151 |
-</p> |
152 |
- |
153 |
-<p> |
154 |
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
155 |
-become production-ready and there hasn't been a sufficient track record to |
156 |
-comment positively nor negatively on its general stability at this point. |
157 |
-</p> |
158 |
- |
159 |
-</body> |
160 |
+<subsection> |
161 |
+<include href="../hb-install-filesystems.xml"/> |
162 |
</subsection> |
163 |
+ |
164 |
<subsection id="filesystems-apply"> |
165 |
<title>Applying a Filesystem to a Partition</title> |
166 |
<body> |
167 |
@@ -325,7 +275,7 @@ |
168 |
</pre> |
169 |
|
170 |
<p> |
171 |
-Create and activate the swap now. |
172 |
+Create and activate the swap with the commands mentioned above. |
173 |
</p> |
174 |
|
175 |
</body> |
176 |
@@ -333,7 +283,6 @@ |
177 |
</section> |
178 |
<section> |
179 |
<title>Mounting</title> |
180 |
-<subsection> |
181 |
<body> |
182 |
|
183 |
<p> |
184 |
@@ -350,9 +299,9 @@ |
185 |
</pre> |
186 |
|
187 |
<note> |
188 |
-If you want your <path>/tmp</path> to reside on a separate partition, be sure to |
189 |
-change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. This |
190 |
-also holds for <path>/var/tmp</path>. |
191 |
+If you want your <path>/tmp</path> to reside on a separate partition, be sure |
192 |
+to change its permissions after mounting: <c>chmod 1777 /mnt/gentoo/tmp</c>. |
193 |
+This also holds for <path>/var/tmp</path>. |
194 |
</note> |
195 |
|
196 |
<p> |
197 |
@@ -367,6 +316,5 @@ |
198 |
</p> |
199 |
|
200 |
</body> |
201 |
-</subsection> |
202 |
</section> |
203 |
</sections> |
204 |
|
205 |
|
206 |
|
207 |
1.3 xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-disk.xml |
208 |
|
209 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-disk.xml?rev=1.3&view=markup |
210 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-disk.xml?rev=1.3&content-type=text/plain |
211 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-disk.xml?r1=1.2&r2=1.3 |
212 |
|
213 |
Index: hb-install-ppc-disk.xml |
214 |
=================================================================== |
215 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-disk.xml,v |
216 |
retrieving revision 1.2 |
217 |
retrieving revision 1.3 |
218 |
diff -u -r1.2 -r1.3 |
219 |
--- hb-install-ppc-disk.xml 1 Mar 2008 06:43:00 -0000 1.2 |
220 |
+++ hb-install-ppc-disk.xml 1 Mar 2008 14:15:57 -0000 1.3 |
221 |
@@ -4,12 +4,12 @@ |
222 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
223 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
224 |
|
225 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-disk.xml,v 1.2 2008/03/01 06:43:00 nightmorph Exp $ --> |
226 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc-disk.xml,v 1.3 2008/03/01 14:15:57 neysx Exp $ --> |
227 |
|
228 |
<sections> |
229 |
|
230 |
<version>9.0</version> |
231 |
-<date>2008-02-29</date> |
232 |
+<date>2008-03-01</date> |
233 |
|
234 |
<section> |
235 |
<title>Introduction to Block Devices</title> |
236 |
@@ -456,11 +456,11 @@ |
237 |
<p> |
238 |
If you intend to also install MorphOS on your Pegasos create an affs1 filesystem |
239 |
at the start of the drive. 32MB should be more than enough to store the MorphOS |
240 |
-kernel. If you have a Pegasos I or intend to use any filesystem besides ext2 or |
241 |
-ext3, you will also have to store your Linux kernel on this partition (the |
242 |
-Pegasos II can only boot from ext2/ext3 or affs1 partitions). To create the |
243 |
-partition run <c>mkpart primary affs1 START END</c> where <c>START</c> and |
244 |
-<c>END</c> should be replaced with the megabyte range (e.g. <c>0 32</c>) which |
245 |
+kernel. If you have a Pegasos I or intend to use any filesystem besides ext2 or |
246 |
+ext3, you will also have to store your Linux kernel on this partition (the |
247 |
+Pegasos II can only boot from ext2/ext3 or affs1 partitions). To create the |
248 |
+partition run <c>mkpart primary affs1 START END</c> where <c>START</c> and |
249 |
+<c>END</c> should be replaced with the megabyte range (e.g. <c>0 32</c>) which |
250 |
creates a 32 MB partition starting at 0MB and ending at 32MB. If you chose to |
251 |
create an ext2 or ext3 partition instead, substitute ext2 or ext3 for affs1 in |
252 |
the mkpart command. |
253 |
@@ -502,53 +502,11 @@ |
254 |
|
255 |
</body> |
256 |
</subsection> |
257 |
-<subsection> |
258 |
-<title>Filesystems?</title> |
259 |
-<body> |
260 |
- |
261 |
-<p> |
262 |
-Several filesystems are available for use on the PowerPC architecture including |
263 |
-ext2, ext3, ReiserFS and XFS, each with their strengths and faults. |
264 |
-</p> |
265 |
- |
266 |
-<p> |
267 |
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
268 |
-journaling, which means that routine ext2 filesystem checks at startup time can |
269 |
-be quite time-consuming. There is now quite a selection of journaled |
270 |
-filesystems that can be checked for consistency very quickly and are thus |
271 |
-generally preferred over their non-journaled counterparts. |
272 |
-</p> |
273 |
- |
274 |
-<p> |
275 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
276 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
277 |
-full data and ordered data journaling. It uses an HTree index that enables high |
278 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
279 |
-filesystem. |
280 |
-</p> |
281 |
- |
282 |
-<p> |
283 |
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
284 |
-performance and greatly outperforms both ext2 and ext3 when dealing with small |
285 |
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
286 |
-extremely well and has metadata journaling. ReiserFS is solid and usable as |
287 |
-both general-purpose filesystem and for extreme cases such as the creation of |
288 |
-large filesystems, very large files and directories containing tens of |
289 |
-thousands of small files. |
290 |
-</p> |
291 |
- |
292 |
-<p> |
293 |
-<b>XFS</b> is a filesystem with metadata journaling which comes with a robust |
294 |
-feature-set and is optimized for scalability. We only recommend using this |
295 |
-filesystem on Linux systems with high-end SCSI and/or fibre channel storage and |
296 |
-an uninterruptible power supply. Because XFS aggressively caches in-transit data |
297 |
-in RAM, improperly designed programs (those that don't take proper precautions |
298 |
-when writing files to disk and there are quite a few of them) can lose a good |
299 |
-deal of data if the system goes down unexpectedly. |
300 |
-</p> |
301 |
|
302 |
-</body> |
303 |
+<subsection> |
304 |
+<include href="../hb-install-filesystems.xml"/> |
305 |
</subsection> |
306 |
+ |
307 |
<subsection> |
308 |
<title>Activating the Swap Partition</title> |
309 |
<body> |
310 |
|
311 |
|
312 |
|
313 |
1.3 xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-disk.xml |
314 |
|
315 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-disk.xml?rev=1.3&view=markup |
316 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-disk.xml?rev=1.3&content-type=text/plain |
317 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-disk.xml?r1=1.2&r2=1.3 |
318 |
|
319 |
Index: hb-install-ppc64-disk.xml |
320 |
=================================================================== |
321 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-disk.xml,v |
322 |
retrieving revision 1.2 |
323 |
retrieving revision 1.3 |
324 |
diff -u -r1.2 -r1.3 |
325 |
--- hb-install-ppc64-disk.xml 1 Mar 2008 06:43:00 -0000 1.2 |
326 |
+++ hb-install-ppc64-disk.xml 1 Mar 2008 14:15:57 -0000 1.3 |
327 |
@@ -4,12 +4,12 @@ |
328 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
329 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
330 |
|
331 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-disk.xml,v 1.2 2008/03/01 06:43:00 nightmorph Exp $ --> |
332 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-ppc64-disk.xml,v 1.3 2008/03/01 14:15:57 neysx Exp $ --> |
333 |
|
334 |
<sections> |
335 |
|
336 |
<version>9.0</version> |
337 |
-<date>2008-02-29</date> |
338 |
+<date>2008-03-01</date> |
339 |
|
340 |
<section> |
341 |
<title>Introduction to Block Devices</title> |
342 |
@@ -160,7 +160,7 @@ |
343 |
it is with multiple partitions) |
344 |
</li> |
345 |
<li> |
346 |
- Security can be enhanced by mounting some partitions or volumes read-only, |
347 |
+ Security can be enhanced by mounting some partitions or volumes read-only, |
348 |
nosuid (setuid bits are ignored), noexec (executable bits are ignored) etc. |
349 |
</li> |
350 |
</ul> |
351 |
@@ -224,7 +224,7 @@ |
352 |
To finish up, write the partition to the disk using <c>w</c> and <c>q</c> to |
353 |
quit <c>mac-fdisk</c>. |
354 |
</p> |
355 |
- |
356 |
+ |
357 |
<note> |
358 |
To make sure everything is ok, you should run mac-fdisk once more and check |
359 |
whether all the partitions are there. If you don't see any of the partitions you |
360 |
@@ -314,7 +314,37 @@ |
361 |
</pre> |
362 |
|
363 |
<p> |
364 |
-Type <c>p</c> to display your disk's current partition configuration: |
365 |
+If you still have an AIX partition layout on your system, you will get the |
366 |
+following error message: |
367 |
+</p> |
368 |
+ |
369 |
+<pre caption="Error message from fdisk"> |
370 |
+ There is a valid AIX label on this disk. |
371 |
+ Unfortunately Linux cannot handle these |
372 |
+ disks at the moment. Nevertheless some |
373 |
+ advice: |
374 |
+ 1. fdisk will destroy its contents on write. |
375 |
+ 2. Be sure that this disk is NOT a still vital |
376 |
+ part of a volume group. (Otherwise you may |
377 |
+ erase the other disks as well, if unmirrored.) |
378 |
+ 3. Before deleting this physical volume be sure |
379 |
+ to remove the disk logically from your AIX |
380 |
+ machine. (Otherwise you become an AIXpert). |
381 |
+ |
382 |
+Command (m for help): |
383 |
+</pre> |
384 |
+ |
385 |
+<p> |
386 |
+Don't worry, you can create a new empty dos partition table by pressing |
387 |
+<c>o</c>. |
388 |
+</p> |
389 |
+ |
390 |
+<warn> |
391 |
+This will destroy any installed AIX version |
392 |
+</warn> |
393 |
+ |
394 |
+<p> |
395 |
+Type <c>p</c> to display your disk current partition configuration: |
396 |
</p> |
397 |
|
398 |
<pre caption="An example partition configuration"> |
399 |
@@ -568,62 +598,11 @@ |
400 |
|
401 |
</body> |
402 |
</subsection> |
403 |
-<subsection> |
404 |
-<title>Filesystems?</title> |
405 |
-<body> |
406 |
- |
407 |
-<note> |
408 |
-Several filesystems are available. ext2, ext3 and ReiserFS support is built in |
409 |
-the Installation CD kernels. JFS and XFS support is available through kernel |
410 |
-modules. |
411 |
-</note> |
412 |
|
413 |
-<p> |
414 |
-<b>ext2</b> is the tried and true Linux filesystem but doesn't have metadata |
415 |
-journaling, which means that routine ext2 filesystem checks at startup time can |
416 |
-be quite time-consuming. There is now quite a selection of newer-generation |
417 |
-journaled filesystems that can be checked for consistency very quickly and are |
418 |
-thus generally preferred over their non-journaled counterparts. Journaled |
419 |
-filesystems prevent long delays when you boot your system and your filesystem |
420 |
-happens to be in an inconsistent state. |
421 |
-</p> |
422 |
- |
423 |
-<p> |
424 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
425 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
426 |
-full data and ordered data journaling. It uses an HTree index that enables high |
427 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
428 |
-filesystem. |
429 |
-</p> |
430 |
- |
431 |
-<p> |
432 |
-<b>ReiserFS</b> is a B+tree-based filesystem that has very good overall |
433 |
-performance and greatly outperforms both ext2 and ext3 when dealing with small |
434 |
-files (files less than 4k), often by a factor of 10x-15x. ReiserFS also scales |
435 |
-extremely well and has metadata journaling. ReiserFS is solid and usable as |
436 |
-both general-purpose filesystem and for extreme cases such as the creation of |
437 |
-large filesystems, very large files and directories containing tens of |
438 |
-thousands of small files. |
439 |
-</p> |
440 |
- |
441 |
-<p> |
442 |
-<b>XFS</b> is a filesystem with metadata journaling that is fully supported |
443 |
-under Gentoo Linux's xfs-sources kernel. It comes with a robust feature-set and |
444 |
-is optimized for scalability. We only recommend using this filesystem on Linux |
445 |
-systems with high-end SCSI and/or fibre channel storage and a uninterruptible |
446 |
-power supply. Because XFS aggressively caches in-transit data in RAM, improperly |
447 |
-designed programs (those that don't take proper precautions when writing files |
448 |
-to disk and there are quite a few of them) can lose a good deal of data if the |
449 |
-system goes down unexpectedly. |
450 |
-</p> |
451 |
- |
452 |
-<p> |
453 |
-<b>JFS</b> is IBM's high-performance journaling filesystem. It has recently |
454 |
-become production-ready. |
455 |
-</p> |
456 |
- |
457 |
-</body> |
458 |
+<subsection> |
459 |
+<include href="../hb-install-filesystems.xml"/> |
460 |
</subsection> |
461 |
+ |
462 |
<subsection id="filesystems-apply"> |
463 |
<title>Applying a Filesystem to a Partition</title> |
464 |
<body> |
465 |
|
466 |
|
467 |
|
468 |
1.3 xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-disk.xml |
469 |
|
470 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-disk.xml?rev=1.3&view=markup |
471 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-disk.xml?rev=1.3&content-type=text/plain |
472 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-disk.xml?r1=1.2&r2=1.3 |
473 |
|
474 |
Index: hb-install-sparc-disk.xml |
475 |
=================================================================== |
476 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-disk.xml,v |
477 |
retrieving revision 1.2 |
478 |
retrieving revision 1.3 |
479 |
diff -u -r1.2 -r1.3 |
480 |
--- hb-install-sparc-disk.xml 1 Mar 2008 06:43:00 -0000 1.2 |
481 |
+++ hb-install-sparc-disk.xml 1 Mar 2008 14:15:57 -0000 1.3 |
482 |
@@ -4,12 +4,12 @@ |
483 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
484 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
485 |
|
486 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-disk.xml,v 1.2 2008/03/01 06:43:00 nightmorph Exp $ --> |
487 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/2008.0/hb-install-sparc-disk.xml,v 1.3 2008/03/01 14:15:57 neysx Exp $ --> |
488 |
|
489 |
<sections> |
490 |
|
491 |
<version>9.0</version> |
492 |
-<date>2008-02-29</date> |
493 |
+<date>2008-03-01</date> |
494 |
|
495 |
<section> |
496 |
<title>Introduction to Block Devices</title> |
497 |
@@ -486,36 +486,11 @@ |
498 |
|
499 |
</body> |
500 |
</subsection> |
501 |
-<subsection> |
502 |
-<title>Filesystems?</title> |
503 |
-<body> |
504 |
- |
505 |
-<p> |
506 |
-Several filesystems are available, some are known to be stable on the |
507 |
-SPARC architecture. Ext2 and ext3, for example, are known to work well. |
508 |
-Alternate filesystems may not function correctly. |
509 |
-</p> |
510 |
- |
511 |
-<p> |
512 |
-<b>ext2</b> is the tried-and-true Linux filesystem. It does not support |
513 |
-journaling, which means that periodic checks of ext2 filesystems at startup |
514 |
-can be quite time-consuming. There is quite a selection of newer-generation |
515 |
-journaled filesystems that can be checked for consistency very quickly at |
516 |
-startup, and are therefore generally preferred over their non-journaled |
517 |
-counterparts. In general, journaled filesystems prevent long delays when a |
518 |
-system is booted and the filesystem is in an inconsistent state. |
519 |
-</p> |
520 |
- |
521 |
-<p> |
522 |
-<b>ext3</b> is the journaled version of the ext2 filesystem, providing metadata |
523 |
-journaling for fast recovery in addition to other enhanced journaling modes like |
524 |
-full data and ordered data journaling. It uses an HTree index that enables high |
525 |
-performance in almost all situations. In short, ext3 is a very good and reliable |
526 |
-filesystem. |
527 |
-</p> |
528 |
|
529 |
-</body> |
530 |
+<subsection> |
531 |
+<include href="../hb-install-filesystems.xml"/> |
532 |
</subsection> |
533 |
+ |
534 |
<subsection id="filesystems-apply"> |
535 |
<title>Applying a Filesystem to a Partition</title> |
536 |
<body> |
537 |
|
538 |
|
539 |
|
540 |
-- |
541 |
gentoo-doc-cvs@l.g.o mailing list |