[Pkg-kbd-devel] Bug#443606: Improvements for kbd?

[Anton Zinoviev]

On Fri, Oct 05, 2007 at 7:26:14PM +0200, wolfram.sang at stud.tu-ilmenau.de wrote:
> 
> I hope it is okay that I write you personally, but the
> pkg-kbd-devel-list is sadly so full of spam that I wonder if normal
> messages can get attention there.

Yes, of course.  Some time ago the pkg-kbd group had a few members.
While it was never my intention to maintain kbd, I had to when the
number of the members of this group reduced to me. :)

I think this package will have soon a new maintainer and thats why I
haven't reacted yet on these bugs.

> Recently, I filed two bug-reports concerning kbd, namely #443645 and
> #443606.  For the first one, I made a small solution to the problem,
> which I could extend further, if this wanted. Do you think it is
> worth continuing with it or should I just skip it? :)

Regarding #443645, I think that by default unicode_start should not
change the font at all.  However I think it is the rignt of the new
maintainer to make the decision about this.

Regarding #443606, the reason this problem happens is the following
fragment in /etc/init.d/console-screen.kbd.sh:

    if [ "$RUNLEVEL" = S ]; then
        LIST_CONSOLES=0
    elif [ -z "$LIST_CONSOLES" ]; then
        #  Wait for getty to provide TTYs
        sleep 3
        LIST_CONSOLES=`sed -e '/^ *#/d' /etc/inittab | grep 'tty[0-9]*$' | awk -
F: '{printf "%s ", $1}'`
    fi

I have no idea why if RUNLEVEL is S (and it is S when the script is
invoked), then only the first console is configured.  I also don't
know the purpose of this "sleep 3" command.  In the scripts of
console-setup there is no such "sleep" and I am unaware of any problem
caused by this (the command "unicode_start >ttydevice" works even if
ttydevice is not opened).

Anton Zinoviev