Philipp Kern <pk...@debian.org> writes: > On 2016-05-09 23:28, Philip Hands wrote: >> In order to make the dpms stuff work again in future versions I'd think >> that screen-blanking is really not helpful during install, so would set >> DPMS="-s 0" or perhaps DPMS="-s 0 -dpms", by default, and also make it >> so that is what's set when dpms=false is specified. > > While completely true for automated installs, people might end up with > idling installers on some machines, no?
Do modern screens still actaully suffer from burn-in? I've certainly been fooled once or twice into thinking that a machine is dead by choosing the wrong keyboard to hit Ctrl on. I've also occasionally had to repeatedly nudge a machine to see how it's getting on when observing it's progress from afar, which is a bit of a bore. How about if we set the timeout to something that should be considerably longer than the largest interval between user input during an install? 12 hours doesn't seem like a bad number, but if we went for 24 hours then the screen would still be cheerfully blinking with a prompt the next morning if you launched an install just before going home from work. Do we realistically expect to do significant damage to the screen (or the environment) by very occasionally leaving a screen on for 12/24 hours? Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/ http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg, GERMANY
signature.asc
Description: PGP signature
