1 |
swift 12/04/07 07:29:57 |
2 |
|
3 |
Modified: initramfs-guide.xml |
4 |
Log: |
5 |
English language improvements, no content. Thanks to chiguire for noticing and recommending the changes |
6 |
|
7 |
Revision Changes Path |
8 |
1.2 xml/htdocs/doc/en/initramfs-guide.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/initramfs-guide.xml?rev=1.2&view=markup |
11 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/initramfs-guide.xml?rev=1.2&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/initramfs-guide.xml?r1=1.1&r2=1.2 |
13 |
|
14 |
Index: initramfs-guide.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/initramfs-guide.xml,v |
17 |
retrieving revision 1.1 |
18 |
retrieving revision 1.2 |
19 |
diff -u -r1.1 -r1.2 |
20 |
--- initramfs-guide.xml 5 Apr 2012 19:40:55 -0000 1.1 |
21 |
+++ initramfs-guide.xml 7 Apr 2012 07:29:57 -0000 1.2 |
22 |
@@ -1,5 +1,5 @@ |
23 |
<?xml version='1.0' encoding="UTF-8"?> |
24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/initramfs-guide.xml,v 1.1 2012/04/05 19:40:55 swift Exp $ --> |
25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/initramfs-guide.xml,v 1.2 2012/04/07 07:29:57 swift Exp $ --> |
26 |
|
27 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
28 |
|
29 |
@@ -51,10 +51,10 @@ |
30 |
<p> |
31 |
Once the Linux kernel has control over the system (which it gets after being |
32 |
loaded by the boot loader), it prepares its memory structures and drivers as |
33 |
-good as it can. It then hands over control to an application (usually |
34 |
+well as it can. It then hands over control to an application (usually |
35 |
<c>init</c>) whose task it is to further prepare the system and make sure that, |
36 |
at the end of the boot process, all necessary services are running and the user |
37 |
-is able to log on. The <c>init</c> application does that by launching, amongst |
38 |
+is able to log on. The <c>init</c> application does that by launching, among |
39 |
other services, the <c>udev</c> daemon who will further load up and prepare the |
40 |
system based on the detected devices. When <c>udev</c> is launched, all |
41 |
remaining file systems that have not been mounted are mounted, and the remainder |
42 |
@@ -120,7 +120,7 @@ |
43 |
</ul> |
44 |
|
45 |
<p> |
46 |
-To resolve these (for some perhaps hardly called) issues, the initramfs was |
47 |
+To resolve these (for some perhaps hardly called) problems, the initramfs was |
48 |
created. |
49 |
</p> |