consolechars switches tty since 8b92e87 vt: add an event interface

["Przemysław Pawełczyk" <przemyslaw@pawelczyk.it>]

Hi,

I found (using git bisect) that following commit:

commit 8b92e87d39bfd046e7581e1fe0f40eac40f88608
Author: Alan Cox <alan@linux.intel.com>
Date:   Sat Sep 19 13:13:24 2009 -0700

    vt: add an event interface

    This is needed and requested in various forms for ConsoleKit, screenblank
    handling and the like so do the job with a single interface. Also build the
    interface so that unlike VT_WAITACTIVE and friends it won't miss events.

    FIXME: Should this be a waitactive ioctl or a new device file you can poll
    and read events from. We need the code anyway to fix up the existing broken
    wait for console switch logic but the ConsoleKit people would prefer the
    new device to the ioctl we have here

    Signed-off-by: Alan Cox <alan@linux.intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

M       drivers/char/vt.c
M       drivers/char/vt_ioctl.c
M       include/linux/vt.h
M       include/linux/vt_kern.h

is the perpetrator of changing consolechars (and probably other
tty-related apps) behavior.

[ In Debian before the end of the S runlevel (boot) console-screen.sh
is executed (it is not the last script though), where consolechars is
used for loading console screen font for each tty. In my case it
evaluates to:

    /usr/bin/consolechars --tty=/dev/ttyX -f lat0-sun16

Similarly consolechars is used in setupcon script invoked by
console-setup (processed after console-screen.sh) to set a font chosen
by user. ]

The problem is that since 8b92e87 running consolechars switches tty to
the one provided with --tty option. Last commit I have tested,
a9366e6, is still affected.

( Back then there was also another problem with "INIT:
open(/dev/console): Input/output error" introduced in b50989d and
fixed in f278a2f. )

Result? Messages starting from "INIT: Switching to runlevel: 2" don't
go to tty1 as they should and tty1 is not the tty I see when login
prompt shows up.

I tried to found out whether this issue was already brought to light,
but without success. Maybe this is an obvious and intentional
consequence of the patch for people familiar with tty/vt --
unfortunately I am not among them.

Thanks.

-- 
Przemysław Pawełczyk