linux-kernel - Re: [PATCH] vt: disable console blanking by default

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] [day] [month] [year] [list]

Message-ID: <20140629203504.GA11829@amd.pavel.ucw.cz>
Date:	Sun, 29 Jun 2014 22:35:04 +0200
From:	Pavel Machek <pavel@....cz>
To:	linux-kernel@...r.kernel.org, Jiri Slaby <jslaby@...e.cz>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] vt: disable console blanking by default

On Wed 2014-06-25 13:41:09, Tomasz Torcz wrote:
> On Sun, Jun 22, 2014 at 06:37:29PM +0200, Pavel Machek wrote:
> > On Wed 2014-06-18 11:27:31, Tomasz Torcz wrote:
> > > 
> > > >From ea7cf47e3230eda63aa6c46092719437f9bbae8e Mon Sep 17 00:00:00 2001
> > > From: Tomasz Torcz <tomek@...ebreaker.pl>
> > > Date: Wed, 18 Jun 2014 11:18:06 +0200
> > > Subject: [PATCH] vt: disable console blanking by default
> > > 
> > >   Remove default 10 minute blank interval. Instead: never blank by
> > >   default.
> > >   "Screensaving" is no longer useful.  Today it only provides
> > >   obstacle when interacting with text console, especially through
> > >   remote lights-out management solutions.
> > > 
> > > Signed-off-by: Tomasz Torcz <tomek@...ebreaker.pl>
> > 
> > Dunno. You'll kill an LCD if you let same image there for too
> > long. Make it 10hours?
> 
>   There is no practical difference between 10 minutes and 10 hours.  Both
> are more than none.  This means that If I need to access console, it
> will probably be blanked.  For some servers, console access is needed
> less than once per year, if ever.  But IF the console need to be accessed,
> there's a strong reason to it (some kind of fault), and having to press
> anything to unblank may be invasive.
> 
>  I would prefer to fix the issue at the source, instead of sticking "consoleblank=0"
> in grub2.cfg on houndreds of boxes.  BTW, kernel already contains "consoleblank=0" in 
> arch/arc/boot/dts/nsimosci.dts and arch/arm/boot/dts/omap3-lilly-a83x.dtsi 
> 
>   Is LCD damage for currently produced LCDs real issue, still?

Probably yes. Plus, people are still running CRTs and blanked screen
still eats significantly less power. So "consoleblank=0" seems right
solution for you, and current default still sounds right.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/