[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0702011932090.13737@yvahk01.tjqt.qr>
Date: Thu, 1 Feb 2007 19:33:58 +0100 (MET)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: "Robert P. J. Day" <rpjday@...dspring.com>
cc: 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 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]
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/
Powered by blists - more mailing lists