linux-kernel - Re: [PATCH] add "notime" boot option

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]

Message-ID: <46551E87.1030700@gmail.com>
Date:	Thu, 24 May 2007 07:11:35 +0200
From:	Rene Herman <rene.herman@...il.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	Michael Tokarev <mjt@....msk.ru>,
	lkml <linux-kernel@...r.kernel.org>,
	akpm <akpm@...ux-foundation.org>
Subject: Re: [PATCH] add "notime" boot option

On 05/24/2007 07:08 AM, Randy Dunlap wrote:

> Rene Herman wrote:

>> Okay. I would by the way not be against turning the timestamping off by
>> default and turning it _on_ with a "timestamps" or "logtime" or 
>> whatever option. The information is sometimes handy for seeing the 
>> (clustering of) event times so I've been compiling it in for a while on
>> some boxes but in the majority case for me it's noise taking up printk
>> real estate...
> 
> But CONFIG_PRINTK_TIME is what controls its "default" (build-time) value.
>  I.e., users can control that.

Yes, but a (full) kernel recompile is a bit of a hard-hitting switch, 
certainly on the older machines where I actually have it enabled...

> I would be OK with removing that config option and only being able to
> enable it, but I doubt that this would have much support.  ;)

Fine by me.

Rene.

-
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/