Hi Marko, On Sat, 2009-11-14 at 09:28 +0100, Marco Stornelli wrote: > I think in general the procedure should be: at startup or event (for > example acquired IP address from DHCP) user applications write in flash > (better in persistent ram) a log with a tag or a timestamp or something > like this, when there is a kernel panic, it is captured in a file stored > together the log and when possible the system should send all via > network for example. Are there problems that I can't see to follow this > approach? When David says "...so this looks much more like a real file > than a sysctl file" I quite agree, it seems a normal application/system > log indeed. Please, do not top-post, you make it difficult to discuss things by messing up the context. Be consistent with how other people reply in this thread, please. Take a look at my mails where I describe different complications we have in our system. We really want to have an OOPS/panic + our environment stuff to go together, at once. This makes things so much simpler. Really, what is the problem providing this trivial panic-note capability, where user-space can give the kernel a small buffer, and ask the kernel to print this buffer at the oops/panic time. Very simple and elegant, and just solves the problem. Why perversions with time-stamps, separate storages are needed? IOW, you suggest a complicated approach, and demand explaining why we do not go for it. Simply because it is unnecessarily complex. This patch solves the problem gracefully, and I'd rather demand you to point what is the technical problem with the patches. -- Best Regards, Artem Bityutskiy (Артём Битюцкий) -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
