linux-kernel - Re: [ PATCH ] fix to documentation for kexec

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]

Message-ID: <20070201184217.GF5825@shell0.pdx.osdl.net>
Date:	Thu, 1 Feb 2007 10:42:17 -0800
From:	Judith Lebzelter <judith@...l.org>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	"Robert P. J. Day" <rpjday@...dspring.com>,
	Judith Lebzelter <judith@...l.org>, ebiederm@...ssion.com,
	linux-kernel@...r.kernel.org, fastboot@...l.org
Subject: Re: [ PATCH ] fix to documentation for kexec

On Thu, Feb 01, 2007 at 07:33:58PM +0100, Jan Engelhardt wrote:
> 
> On Feb 1 2007 13:30, Robert P. J. Day wrote:
> >> >@@ -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".
> >>
> >> Yup. More precisely, any arguments that could not be parsed (because
> >> the kernel does not know them) are handed down to the init program
> >> as arguments and/or environment variables.
> >
> >whoops, ignore my last post, i misread the critical words.
> 
> However, I am not sure how the kernel will handle this. Especially since:
> 
>   * if you boot with no initramfs, init= is handled by your script
>     (otherwise: kernel)
> 
>   * does "init" qualify as a kernel param already? I don't think so,
>     since the code indicates to be wanting "init=" at least.
> 
> Either way, the word "init" in the above doc is either (1) wrong
> or (2) superfluous [unless something strange happens to interpret it later,
> which I don't think]

Yes, it looks like "init=" is right, "init" is wrong.

I did notice that my patch is out of date for the latest kernel, 
however.  I can send an up to date one.

Judith
> 
> 
> Jan
> -- 
> ft: http://freshmeat.net/p/chaostables/
-
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/