public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Daniel Mack <daniel@caiaq.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] console: make blank timeout value a boot option
Date: Thu, 4 Jun 2009 01:17:40 -0700	[thread overview]
Message-ID: <20090604011740.5879732c.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090604074407.GX26148@buzzloop.caiaq.de>

On Thu, 4 Jun 2009 09:44:09 +0200 Daniel Mack <daniel@caiaq.de> wrote:

> On Thu, Jun 04, 2009 at 12:23:25AM -0700, Andrew Morton wrote:
> > > --- a/Documentation/kernel-parameters.txt
> > > +++ b/Documentation/kernel-parameters.txt
> > > @@ -545,6 +545,10 @@ and is between 256 and 4096 characters. It is defined in the file
> > >  			console=brl,ttyS0
> > >  		For now, only VisioBraille is supported.
> > >  
> > > +	consoleblank=	[KNL] The console blank (screen saver) timeout in
> > > +			seconds. Defaults to 10*60 = 10mins. A value of 0
> > > +			disables the blank timer.
> > > +
> > 
> > It would be better to make this alterable at runtime, rather than at
> > boot time.  Perhaps another VT ioctl.
> 
> That's already possible - there is an ioctl for that. It's just not
> configurable at boot time, and that occured to be very annoying when
> developing systems that won't fully boot up for >10mins. You have no way
> to wake up the console then.

Oh.  Your changelog sucked :)

> Is there any concern why that shouldn't be a kernel option?

I suppose it makes sense.  You really have systems which take more than
ten minutes to start running initscripts?  Poor you.

Please resend with a more complete description?

  reply	other threads:[~2009-06-04  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 14:46 [PATCH] console: make blank timeout value a boot option Daniel Mack
2009-06-04  7:23 ` Andrew Morton
2009-06-04  7:44   ` Daniel Mack
2009-06-04  8:17     ` Andrew Morton [this message]
2009-06-04  8:37       ` Daniel Mack
2009-06-04  8:46         ` Andrew Morton

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=20090604011740.5879732c.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=daniel@caiaq.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox