linux-kernel - Re: Trailing periods in kernel messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 21 Dec 2007 00:14:48 +0100
From:	"J.A. Magallón" <jamagallon@....com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Joe Perches <joe@...ches.com>, David Miller <davem@...emloft.net>,
	apw@...dowen.org, lizf@...fujitsu.com, akpm@...ux-foundation.org,
	elendil@...net.nl, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, trivial@...nel.org, rdunlap@...otime.net,
	jschopp@...tin.ibm.com
Subject: Re: Trailing periods in kernel messages

On Thu, 20 Dec 2007 22:08:53 +0000, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> > I believe though that printk messages are not sentences but are
> > logging statements.  Statements do not require full-stops.
> > 
> > Opinions, of course, vary.
> 
> I do not believe "opinions" are relevant here. Relevant would be cites
> from respected style guides (Fowlers, Oxford Guide To Style et al.) to
> show they do not need a full stop. 
> 

All those fine references you cite are sure written for read literate
(literacy?) texts. Punctuation is something that is needed in (just
forgive me 'cause I'm trying to think this in english, but spanish is
my native language...) continous written text that needs some kind of
symbol to show there is a pause half in a sentence (a comma), or that
two statements are separate sentences and need to be declaimed specially.

Nobody (someone?) has written a guide to declaim computer messages or
source code. If you get so picky, this message

[kajasldkjasl] Kernel OOPS: sdsdsdsdsd

shoud read:

At [kajasldkjasl], the kernel has tried to deliver an operation that
resulted in an inconsistent state, so system operation has been stopped...

>From my point of view:
- Kernel messages are not read at loud...
- If you are so worried about extra chars/mem usage in other areas, the
  dot at the end of a kernel message is just trash.
- If some kernel message has two sentences, better to format them in
  two lines (ie, sed -e :.:\n:g:)

If some kernel message needs grammatical corrections, it is not a kernel
message, it was someone very bored when he wrote the code.

The kernel messages are _not_ sentences, they are kernel messages.
If not, you have a harder work assuring they all have a subject and
a predicate than worrying about dots at the end...

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2008.1 (Cooker) for i586
Linux 2.6.23-jam05 (gcc 4.2.2 20071128 (4.2.2-2mdv2008.1)) SMP PREEMPT
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/