Dear Lee Jones,
In message 20121121172604.GB417@gmail.com you wrote:
You appear to have a specific definition of log data in mind. It must be different to mine.
I would say that a log entry would contain useful descriptive information contained. It is _sometimes_ useful to display a related timestamp too. In our case, the most useful part is the timestamp. I just don't see how riddling the kernel log with timestamps would be useful, or nessersary.
Look here:
... [ 85.005969] it87: Found IT8718F chip at 0x290, revision 5 [ 85.041976] it87: VID is disabled (pins used for GPIO) [ 85.081038] it87: Beeping is supported [ 86.283285] r8169 0000:04:00.0: eth0: link down [ 86.283307] r8169 0000:04:00.0: eth0: link down [ 86.348499] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 88.688543] r8169 0000:04:00.0: eth0: link up [ 88.723985] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 89.583337] Bridge firewalling registered [ 89.642103] device virbr0-nic entered promiscuous mode ...
You tell me what is the most interesting information here, the "descriptive information", or the "related timestamp"? In many cases, and for many people, it's not one or the other, but _both_.
But we're repeating ourselfs. I see no new arguments. Let's stop here.
Best regards,
Wolfgang Denk