Re: [PATCH] Pseudo-console for capture and redirection of console output

[David VomLehn <dvomlehn@cisco.com>]

Mike Frysinger wrote:
> On Mon, Apr 12, 2010 at 02:35, David VomLehn wrote:
>   
>> Provide functions for capturing console output for storage. The primary user
>> is likely to be embedded systems that don't have the storage for core dumps
>> but do have a need to log kernel panic information for later evaluation. It
>> offers two main areas of functionality:
>>
>> o       It can maintain a circular log of console output so that kernel log
>>        messages written before panic() was called can be retrieved to be
>>        added to the failure log.
>> o       A function can be registered to store output from printk() in a
>>        persistent location, such as a reserved location in RAM.  Then,
>>        printk() can be used either directly, to print state information, or
>>        indirectly, through standard functions like dump_stack() and
>>        show_regs().
>>     
>
> how is this any different from the already existing mtdoops driver ?
> -mike
>   
It's a smaller connection piece. It could be used in mtdoops or any 
other printk-capture
cheme. That being said, I'd rather consider this as an RFC. I've had a 
number of interesting
and useful conversations that suggest other ways to procede.