From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Andreas Mohr <andi@lisas.de>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Michael A. Griffith" <grif@acm.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Please get this committed, _NOW_ (preferrably 5 years ago), thanks.
Date: Sun, 8 Nov 2009 23:11:53 +0800 [thread overview]
Message-ID: <20091108151153.GC6240@hack> (raw)
In-Reply-To: <20091108144548.GA13429@rhlx01.hs-esslingen.de>
On Sun, Nov 08, 2009 at 03:45:50PM +0100, Andreas Mohr wrote:
>Hi,
>
>On Sun, Nov 08, 2009 at 10:25:06PM +0800, Américo Wang wrote:
>> On Sun, Nov 08, 2009 at 01:00:08PM +0100, Andreas Mohr wrote:
>> >--- linux-2.6.32-rc6/init/main.c.orig 2009-11-08 11:09:51.000000000 +0100
>> >+++ linux-2.6.32-rc6/init/main.c 2009-11-08 12:40:11.000000000 +0100
>> >@@ -846,7 +846,47 @@ static noinline int init_post(void)
>> > run_init_process("/bin/init");
>> > run_init_process("/bin/sh");
>> >
>> >- panic("No init found. Try passing init= option to kernel.");
>> >+ panic("No init found. Try passing init= option to kernel. "
>> >+ y "See Linux " __FILE__ " for guidance.");
>>
>>
>> I would like to put those guidelines in a doc file, instead
>> of being a FAT comment in the source code.
>
>Heh, somehow I fully expected this objection to come up ;)
>(and you're probably right after all)
>
>So, where to put it?
>Documentation/initrd.txt is related, however I'd create something
>like Documentation/initialization/...
>Or perhaps Documentation/bootup/init.txt ?
Personally, I prefer Documentation/init.txt, but adding it to
initrd.txt also makes sense for me. :)
>
>> And, you're explaining the _user space_ reasons that causes
>> this problem, not related with kernel at all.
>
>That's usually within the responsibility of the one passing control,
>not the one gaining control.
>Just like with children, where it's firmly the parents' job to take care
>of getting their children safely to kindergarden, not the kindergarden's ;)
>
>Plus in my case it _was_ a kernel issue (problematic/non-working serial
>console device). And except for the linker issues of missing libraries,
>many issues (USB functionality etc.) were kernel-related, too.
Yeah, I mentioned it to mean it is not suitable to explain
user-space problems in a kernel source file. Putting it into a kernel
doc should be fine.
Thanks.
--
Live like a child, think like the god.
next prev parent reply other threads:[~2009-11-08 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 12:00 [PATCH] Please get this committed, _NOW_ (preferrably 5 years ago), thanks Andreas Mohr
2009-11-08 14:25 ` Américo Wang
2009-11-08 14:45 ` Andreas Mohr
2009-11-08 15:11 ` Américo Wang [this message]
2009-11-08 15:30 ` Arnd Bergmann
2009-11-08 16:16 ` Andreas Mohr
2009-11-09 20:45 ` [PATCH] provide crucial explanations for the dreaded "No init found." boot failure Andreas Mohr
2009-11-08 19:49 ` [PATCH] Please get this committed, _NOW_ (preferrably 5 years ago), thanks Andi Kleen
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=20091108151153.GC6240@hack \
--to=xiyou.wangcong@gmail.com \
--cc=andi@lisas.de \
--cc=grif@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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