LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Horms <horms@verge.net.au>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Judith Lebzelter <judith@osdl.org>,
	fastboot@osdl.org, ebiederm@xmission.com,
	linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] [ PATCH ] fix to documentation for kexec
Date: Wed, 7 Feb 2007 16:33:16 +0900	[thread overview]
Message-ID: <20070207073316.GF26314@verge.net.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0702011324050.16833@CPE00045a9c397f-CM001225dbafb6>

On Thu, Feb 01, 2007 at 01:25:04PM -0500, Robert P. J. Day wrote:
> On Thu, 1 Feb 2007, Judith Lebzelter wrote:
> 
> > Hello,
> >
> > 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.
> >
> > Thanks;
> > Judith Lebzelter
> >
> > ---
> > Signed-off-by: Judith Lebzelter <judith@osdl.org>
> > ---
> >
> >
> > Index: linux/Documentation/kdump/kdump.txt
> > ===================================================================
> > --- linux.orig/Documentation/kdump/kdump.txt
> > +++ linux/Documentation/kdump/kdump.txt
> > @@ -207,7 +207,7 @@ the following command:
> >
> >     kexec -p <dump-capture-kernel> \
> >     --initrd=<initrd-for-dump-capture-kernel> --args-linux \
> > -   --append="root=<root-dev> init 1 irqpoll"
> > +   --append="root=<root-dev> 1 irqpoll"
> >
> >
> >  Notes on loading the dump-capture kernel:
> > @@ -228,8 +228,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".
> 
> i'm not sure you want to totally remove those first two lines, they
> appear to talk about getting to run level 1 *from a running system*.

I think that it is refering to a kernel command line parameter,
not a shell command executed on a running system, so I think the patch
is correct in that respect.

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/


  reply	other threads:[~2007-02-07  7:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01 18:19 [ PATCH ] fix to documentation for kexec Judith Lebzelter
2007-02-01 18:24 ` Jan Engelhardt
2007-02-01 18:30   ` Robert P. J. Day
2007-02-01 18:33     ` Jan Engelhardt
2007-02-01 18:42       ` Judith Lebzelter
2007-02-01 18:58         ` Judith Lebzelter
2007-02-02  8:02           ` [Fastboot] " Vivek Goyal
2007-02-07  7:42             ` [PATCH] kexec: fix references to init in documentation for kexe Horms
2007-02-01 18:25 ` [ PATCH ] fix to documentation for kexec Robert P. J. Day
2007-02-07  7:33   ` Horms [this message]
2007-02-07 15:41     ` [Fastboot] " Lombard, David N

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070207073316.GF26314@verge.net.au \
    --to=horms@verge.net.au \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@osdl.org \
    --cc=judith@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).