Re: Trailing periods in kernel messages

[Alan Cox]

> Um, what?  Kernel messages are *not* in English.
> 
> Take a look at a machine after it is freshly booted.  The following
> messages are *not* English:
> 
> [    0.000000] BIOS-provided physical RAM map:
> [    0.000000]  BIOS-e820: 0000000000000000 - 0000000000099800 (usable)
> [    0.000000]  BIOS-e820: 0000000000099800 - 00000000000a0000 (reserved)
> [    0.000000]  BIOS-e820: 00000000000d6000 - 00000000000d8000 (reserved)
> [    0.000000]  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> [    0.000000]  BIOS-e820: 0000000000100000 - 00000000bf6b0000 (usable)
> [    0.000000]  BIOS-e820: 00000000bf6b0000 - 00000000bf6cc000 (ACPI data)
> [    0.000000]  BIOS-e820: 00000000bf6cc000 - 00000000bf700000 (ACPI NVS)
> [    0.000000]  BIOS-e820: 00000000bf700000 - 00000000c0000000 (reserved)
> [    0.000000]  BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
> [    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
> 
> Do you really want to turn that into complete English sentences?

Properly it should have a full stop after the table.
 
> Or how about these?

> [   15.077264] TCP: Hash tables configured (established 131072 bind 65536)
                         ^Subject   ^ Verb     

> [   15.077278] TCP reno registered
                      ^ Subject ^Verb
etc

> in some cases, it would make the kernel messages harder to parse by an
> automated log parser.

Not all are sentences but many are including some of your examples, and
they should have full stops therefore.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/