[PATCH/RFC] Make sure linux_banner is the first message in log_buf

[Anton Vorontsov]

On Tue, May 22, 2012 at 10:55:12PM -0400, David Miller wrote:
> From: Anton Vorontsov <anton.vorontsov at linaro.org>
> Date: Tue, 22 May 2012 19:35:16 -0700
> 
> > For scripting it is important to have a consistent header that tells
> > where the kernel log starts. At least to me it always seemed that
> > linux_banner served this purpose.
> 
> Your change will not achieve this goal, many architectures
> print things long before control passes to init/main.c

If they use printk, we'll catch these messages, no? It is true that
if they just write to the HW directly, the messages are lost for us,
and there's nothing we can do about it (and we don't see these
messages from the kernel anyway, neither in dmesg, nor in pstore).

So, for serial (or arch-specific) console it is still cumbersome to
make proper parsing of all messages, but for pstore/ramconsole it is
OK. So, I dunno. I guess I'll have to add a custom header to pstore,
heh.

Thanks,

-- 
Anton Vorontsov
Email: cbouatmailru at gmail.com