From: Chuck Ebbert <76306.1226@compuserve.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Wanted: a limit on kernel log buffer size
Date: Mon, 7 Apr 2003 17:12:38 -0400 [thread overview]
Message-ID: <200304071714_MC3-1-336A-C69F@compuserve.com> (raw)
Randy Dunlap wrote:
>> Just how far does boot get? What messages are printed before death?
I don't have it exactly, but it's along the lines of:
Decompressing.... OK, now booting the kernel
i.e., none.
--
Chuck
I am not an octal number!
next reply other threads:[~2003-04-07 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 21:12 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-07 8:55 Chuck Ebbert
2003-04-07 8:55 Chuck Ebbert
2003-04-07 16:24 ` Randy.Dunlap
2003-04-07 1:34 Chuck Ebbert
2003-04-07 2:49 ` Randy.Dunlap
2003-04-07 3:35 ` Randy.Dunlap
2003-04-07 3:39 ` Robert Love
2003-04-07 4:32 ` Randy.Dunlap
2003-04-07 12:19 ` Roman Zippel
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=200304071714_MC3-1-336A-C69F@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®