From: Randy Dunlap <randy.dunlap@oracle.com>
To: Willy Tarreau <w@1wt.eu>
Cc: lkml@pengaru.com, clemens@dwf.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Still cant boot 2.6.20
Date: Sun, 11 Feb 2007 09:16:02 -0800 [thread overview]
Message-ID: <45CF4F52.7030509@oracle.com> (raw)
In-Reply-To: <20070211083715.GB943@1wt.eu>
Willy Tarreau wrote:
> On Sun, Feb 11, 2007 at 01:37:31AM -0600, lkml@pengaru.com wrote:
>> On Sat, Feb 10, 2007 at 11:12:34PM -0800, Randy Dunlap wrote:
>>> On Sun, 11 Feb 2007 01:02:47 -0600 lkml@pengaru.com wrote:
>>>
>>>> I don't see CONFIG_BLK_DEV_INITRD=y
>>>>
>>>> Regards,
>>>> Vito Caputo
>>>>
>>>> BTW, this isnt the appropriate place for asking this type of question...
>>> Please explain why not.
>>>
>>> And please delete large parts of email that are not needed in replies
>>> (like the .config).
>>> Thanks.
>>>
>> I was under the impression that lkml is for kernel development, not basic help
>> with configuring your kernel.
We also value feedback and problem reports from testers.
That's all this was until your diagnosis.
>> >From the FAQ at http://www.tux.org/lkml/#s3-8
>>
>> "Remember that this is a list for the discussion of kernel development."
>
> You are right, but development also needs feedback. Until the user notices
> it is just a configuration error, it is perfectly possible that his problem
> is caused by a recently introduced bug. You reply put the finger on the
> error (missing CONFIG_BLK_DEV_INITRD). That's perfect. He would be off-topic
> if he went back asking "how do I add this option ?".
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-02-11 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 6:20 Still cant boot 2.6.20 clemens
2007-02-11 7:02 ` lkml
2007-02-11 7:12 ` Randy Dunlap
2007-02-11 7:37 ` lkml
2007-02-11 8:37 ` Willy Tarreau
2007-02-11 17:16 ` Randy Dunlap [this message]
[not found] <fa.lMccRNOAss6zgWj6JUPSrPO11PY@ifi.uio.no>
2007-02-11 7:23 ` Robert Hancock
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=45CF4F52.7030509@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=clemens@dwf.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@pengaru.com \
--cc=w@1wt.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.