All of lore.kernel.org
 help / color / mirror / Atom feed
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Tomasz Torcz <tomek@pipebreaker.pl>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vt: disable console blanking by default
Date: Wed, 25 Jun 2014 13:39:30 +0100	[thread overview]
Message-ID: <20140625133930.223cccb5@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <20140618092730.GD22226@mother.pipebreaker.pl>

On Wed, 18 Jun 2014 11:27:31 +0200
Tomasz Torcz <tomek@pipebreaker.pl> wrote:

> 
> >From ea7cf47e3230eda63aa6c46092719437f9bbae8e Mon Sep 17 00:00:00 2001
> From: Tomasz Torcz <tomek@pipebreaker.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.

Screensaving is extremely useful as is power management, and power prices
are going up not down. We don't customise the upstream kernel just
because J Random User happens to want his defaults.

There are a couple of things you can sensibly do

1. Just turn it off in software. It's run time configurable via setterm

2. If you have a reliable way of detecting the presence of a remote
console device and that device supports reporting when a connection is
made/broken you could submit a patch to make it unblank on connect.

Alan

  parent reply	other threads:[~2014-06-25 12:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18  9:27 [PATCH] vt: disable console blanking by default Tomasz Torcz
2014-06-22 16:37 ` Pavel Machek
2014-06-25 11:41   ` Tomasz Torcz
2014-06-29 20:35     ` Pavel Machek
2014-06-25 12:39 ` One Thousand Gnomes [this message]
2014-06-25 19:21   ` Arkadiusz Miskiewicz
2014-06-26 21:35     ` One Thousand Gnomes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140625133930.223cccb5@alan.etchedpixels.co.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomek@pipebreaker.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.