See (b) above...
> to help many peoples. If a kernel crashes, this application could run
> after the next boot...
Assuming the machine is bootable ;-) ... root fs corruption has a way of
preventing that. Crashes can also prevent the binary/encoded error
message from being logged, making a run of the decoder on the next boot
> > It's a neat idea, but there isn't enough practical benefit to justify the
> > increased complexity.
> Hmmm, we just need to standardize the kernel output. I've searched in
> kernel source for printk's and found over 10 000! So we need the help of
> all developers to make a standardized, nice, parsable kernel output.
Thing is, the bulk of kernel output (printk) isn't intended or needed for
in-depth parsing; module initialization data is mostly for debugging
purposes (perhaps a standard "Initialized : isdn0" line would be nice,
for quick grep'ing...)
/proc is different beast, I'm going to stay out of that one...
-- He feeds on ashes; a deluded mind has led him Adam Bradley, UNCA Senior astray, and he cannot deliver himself or say, Computer Science "Is there not a lie in my right hand?" Isaiah 44:20 email@example.com http://www.cs.unca.edu/~bradley <><