Skip to contentSkip to conversation

Documentation/kdump/kdump.txt: fix some words

PATCH In review WANG Cong 2 participants 2 messages Jun 24, 2008 Documentation

lore
Share & tools
lore

WANG Cong

author
#0 lore raw

PATCH 1/1 Documentation/kdump/kdump.txt: fix some words

This is a trivial patch that only fixes mistakes in Documentation/kdump/kdump.txt.

Cc Randy Dunlap <[email protected]>
Cc Vivek Goyal <[email protected]>
Cc Maneesh Soni <[email protected]>

---

Documentation/kdump/kdump.txt +7 -7
index b8e52c0..0ffa90c 100644
@@ -108,15 +108,15 @@ There are two possible methods of using Kdump.
 
 2) Or use the system kernel binary itself as dump-capture kernel and there is
    no need to build a separate dump-capture kernel. This is possible
-   only with the architecutres which support a relocatable kernel. As
-   of today i386 and ia64 architectures support relocatable kernel.
+   only for the architectures which support a relocatable kernel. As
+   of today i386 and ia64 architectures support a relocatable kernel.
 
 Building a relocatable kernel is advantageous from the point of view that
 one does not have to build a second kernel for capturing the dump. But
 at the same time one might want to build a custom dump capture kernel
 suitable to his needs.
 
-Following are the configuration setting required for system and
+Following are the configuration settings required for system and
 dump-capture kernels for enabling kdump support.
 
 System kernel config options
@@ -299,14 +299,14 @@ For ia64:
 	- Use vmlinux or vmlinuz.gz
 
 
-If you are using a uncompressed vmlinux image then use following command
+If you are using an uncompressed vmlinux image then use the following command
 to load dump-capture kernel.
 
    kexec -p <dump-capture-kernel-vmlinux-image> \
    --initrd=<initrd-for-dump-capture-kernel> --args-linux \
    --append="root=<root-dev> <arch-specific-options>"
 
-If you are using a compressed bzImage/vmlinuz, then use following command
+If you are using a compressed bzImage/vmlinuz, then use the following command
 to load dump-capture kernel.
 
    kexec -p <dump-capture-kernel-bzImage> \
@@ -315,7 +315,7 @@ to load dump-capture kernel.
 
 Please note, that --args-linux does not need to be specified for ia64.
 It is planned to make this a no-op on that architecture, but for now
-it should be omitted
+it should be omitted.
 
 Following are the arch specific command line options to be used while
 loading dump-capture kernel.
@@ -347,7 +347,7 @@ Notes on loading the dump-capture kernel:
 * Boot parameter "1" boots the dump-capture kernel into single-user
   mode without networking. If you want networking, use "3".
 
-* We generally don' have to bring up a SMP kernel just to capture the
+* We generally don't have to bring up a SMP kernel just to capture the
   dump. Hence generally it is useful either to build a UP dump-capture
   kernel or specify maxcpus=1 option while loading dump-capture kernel.
 
Acked-by on v1 1/1
#1 lore raw
Quoted 6 lines · On Tue, 24 Jun 2008 14:33:55 +0100 WANG Cong wrote:

This is a trivial patch that only fixes mistakes in Documentation/kdump/kdump.txt.

Cc Randy Dunlap <[email protected]>

Thanks.

Quoted 55 lines
Cc Vivek Goyal <[email protected]>
Cc Maneesh Soni <[email protected]>

---

Documentation/kdump/kdump.txt +6 -6
index b8e52c0..0ffa90c 100644
@@ -108,15 +108,15 @@ There are two possible methods of using Kdump.
 
 2) Or use the system kernel binary itself as dump-capture kernel and there is
    no need to build a separate dump-capture kernel. This is possible
-   only with the architecutres which support a relocatable kernel. As
-   of today i386 and ia64 architectures support relocatable kernel.
+   only for the architectures which support a relocatable kernel. As
+   of today i386 and ia64 architectures support a relocatable kernel.
 
 Building a relocatable kernel is advantageous from the point of view that
 one does not have to build a second kernel for capturing the dump. But
 at the same time one might want to build a custom dump capture kernel
 suitable to his needs.
 
-Following are the configuration setting required for system and
+Following are the configuration settings required for system and
 dump-capture kernels for enabling kdump support.
 
 System kernel config options
@@ -299,14 +299,14 @@ For ia64:
 	- Use vmlinux or vmlinuz.gz
 
 
-If you are using a uncompressed vmlinux image then use following command
+If you are using an uncompressed vmlinux image then use the following command
 to load dump-capture kernel.
 
    kexec -p <dump-capture-kernel-vmlinux-image> \
    --initrd=<initrd-for-dump-capture-kernel> --args-linux \
    --append="root=<root-dev> <arch-specific-options>"
 
-If you are using a compressed bzImage/vmlinuz, then use following command
+If you are using a compressed bzImage/vmlinuz, then use the following command
 to load dump-capture kernel.
 
    kexec -p <dump-capture-kernel-bzImage> \
@@ -315,7 +315,7 @@ to load dump-capture kernel.
 
 Please note, that --args-linux does not need to be specified for ia64.
 It is planned to make this a no-op on that architecture, but for now
-it should be omitted
+it should be omitted.
 
 Following are the arch specific command line options to be used while
 loading dump-capture kernel.

Documentation/kdump/kdump.txt Notes on loading the dump-capture kernel: · line 353

Quoted 8 lines
Documentation/kdump/kdump.txt +1 -1
@@ -347,7 +347,7 @@ Notes on loading the dump-capture kernel:
 * Boot parameter "1" boots the dump-capture kernel into single-user
   mode without networking. If you want networking, use "3".
 
-* We generally don' have to bring up a SMP kernel just to capture the
+* We generally don't have to bring up a SMP kernel just to capture the
   dump. Hence generally it is useful either to build a UP dump-capture
   kernel or specify maxcpus=1 option while loading dump-capture kernel.
 

---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/