linux-kernel - [PATCH] kexec: fix references to init in documentation for kexe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 7 Feb 2007 16:42:39 +0900
From:	Horms <horms@...ge.net.au>
To:	Vivek Goyal <vgoyal@...ibm.com>
Cc:	Judith Lebzelter <judith@...l.org>, fastboot@...l.org,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	"Robert P. J. Day" <rpjday@...dspring.com>,
	linux-kernel@...r.kernel.org, ebiederm@...ssion.com,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH] kexec: fix references to init in documentation for kexe

On Fri, Feb 02, 2007 at 01:32:40PM +0530, Vivek Goyal wrote:
> On Thu, Feb 01, 2007 at 10:58:08AM -0800, Judith Lebzelter wrote:
> > > 
> > > I did notice that my patch is out of date for the latest kernel, 
> > > however.  I can send an up to date one.
> > > 
> > This applies to 2.6.20-rc7
> > 
> > Signed-off-by: Judith Lebzeelter <judith@...l.org>
> > ---
> > 
> > Stop recommending incorrect/superfluous "init" boot parameter.
> > 
> 
> This looks good. The intention here is just to boot into run level 1, so
> that minimum scripts run in user space and probability of capturing the
> dump increases.
> 
> Fedora doc does say that appending "1" on command line will boot it
> into runlevel 1. I hope same is true for other distributions too.
> 
> Thanks
> Vivek

This seems fine to me. Lets see if we can get it included.

-- 
Simon Horman (Horms)
  horms@...ge.net.au
  http://verge.net.au/~horms/

kexec: fix references to init in documentation for kexec

I've noticed that the boot options are not correct for in
the documentation for kdump. The "init" keyword is not
necessary, and causes a kernel panic when booting with an
initrd on Fedora 5.

Signed-off-by: Judith Lebzeelter <judith@...l.org>
Acked-by: Vivek Goyal <vgoyal@...ibm.com>

Put original comment with the latest version of the patch

Signed-off-by: Simon Horman <horms@...ge.net.au>

Index: linux-2.6.20-rc7/Documentation/kdump/kdump.txt
===================================================================
--- linux-2.6.20-rc7.orig/Documentation/kdump/kdump.txt
+++ linux-2.6.20-rc7/Documentation/kdump/kdump.txt
@@ -311,10 +311,10 @@ Following are the arch specific command 
 loading dump-capture kernel.
 
 For i386, x86_64 and ia64:
-	"init 1 irqpoll maxcpus=1"
+	"1 irqpoll maxcpus=1"
 
 For ppc64:
-	"init 1 maxcpus=1 noirqdistrib"
+	"1 maxcpus=1 noirqdistrib"
 
 
 Notes on loading the dump-capture kernel:
@@ -332,8 +332,8 @@ Notes on loading the dump-capture kernel
 * You must specify <root-dev> in the format corresponding to the root
   device name in the output of mount command.
 
-* "init 1" boots the dump-capture kernel into single-user mode without
-  networking. If you want networking, use "init 3."
+* 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
   dump. Hence generally it is useful either to build a UP dump-capture

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/