Hi, On Tue, Jan 5, 2010 at 17:20, Tejun Heo <tj@xxxxxxxxxx> wrote: > Hello, > > On 01/05/2010 06:04 PM, Hui Zhu wrote: >> I agree with read the current stack message is better. >> >> About the extending, I have some question with it: >> 1. markup_oops.pl have itself idea, it try use dmesg| markup_oops.pl >> show what happen to usr. This is different with s2c. >> I am not sure people like it have other function with it. Too much >> part of this file need to be change. It need rewrite, just the oops >> message parse part can be keep. > > Yeah, I think you'll need to refactor it and share only the parsing > frontend. Just adding a switch (-m or whatever) which puts it into > machine-friendly translator mode should do the trick. > >> 2. I use perl to work in a long time before, I know it good at parse >> the text, but I am not sure it good at handle struct like: > > You don't need to handle the data structure at all. Just make it > parse the dmesg and output machine-friendly formatted output which can > be processed by s2c. ie. just make it do the reformatting. This idea is very cool. I will do it. Thanks for help. :) Best regards, Hui
