[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#605777: status of backspace key deletes forwards on the kFreeBSD console



1) plain cons25 variant: current sysvinit, ncurses 5.7+20100313-4 or 5.7+20100313-5
    and kfreebsd-8 8.1+dfsg-6 (or 8.1+dfsg-7.1), freebsd-utils 8.1-2
[...]
2) cons25-debian variant: needs patched sysvinit, ncurses 5.7+20100313-5,
    and kfreebsd-8 8.1+dfsg-7, freebsd-utils 8.1-3
[...]
3) mixture of both above
    current sysvinit, ncurses 5.7+20100313-5, kfreebsd-8 8.1+dfsg-6 (or 8.1+dfsg-7.1)
    patched freebsd-utils

    As a default use the plain cons25 variant. Additionaly provide
    cons25-debian entry in ncurses and special debian keymap in
    freebsd-utils. By default it will work as variant 1, but there is a
    possibility to set TERM to cons25-debian and set keymap which would
    generate the correct sequences for cons25-debian.

4) backport TEKEN_XTERM from FreeBSD 9.x
    needs patched sysvinit, patched kfreebsd-8, patched freebsd-utils

My personal order of preferences in deep freeze is 3, 1, 4, 2.

Just to make sure I understand correctly, option 3 is roughly "doesn't
conform to Policy but can be made to without significant effort"

Yes.

and a
sysvinit update would be necessary in order to make the default Policy
compliant?  If so, how large is the change required to sysvinit?

See in Message #70 received at 607662@bugs.debian.org:

http://bugs.debian.org//cgi-bin/bugreport.cgi?msg=70;filename=sysvinit-cons25-debian.patch;att=2;bug=607662

But the problem is that there might be another problem in another package - similarly as have been shown that fixing kfreebsd-8 and freebsd-utils does not suffice :-( I guess we do not have enough time before real release for proper testing. IMHO it would be much better to release in state as have been used in last months (years) compared to unknown state.

freebsd-utils has also been re-uploaded (as 8.1-3.1) to revert the
change made there; am I correct that unblocking kfreebsd-8,
freebsd-utils and ncurses would give us option 1 on your list and that
basically puts us back where we were to start with?

For option 1 please unblock freebsd-utils 8.1-3.1 and kfreebsd-8 8.1+dfsg-7.1

The ncurses 5.7+20100313-5 is not needed for option 1,
but it wouldn't hurt.

If so, what other
changes would be required (and how large would be they be) to allow us
to implement option 3?

In 1st step unblock (and migrate) kfreebsd-8 and freebsd-utils as above
in 2nd step unblock ncurses 5.7+20100313-5 and in 3rd step prepare and test another update for freebsd-utils.

The change for freebsd-utils will be some new script like

   kbdcontrol -d | sed ... | kbdcontrol -l
   kbdcontrol -f 61 ESC[3~
   TERM=cons25-debian

Or something like that.
The first command should alter sequence for scan code
*0e* to 0x7F and for scan code *53* to F(61).
The second command should alter sequence generated for F(61).
See also http://svn.debian.org/wsvn/glibc-bsd/trunk/kfreebsd-8/debian/patches/918_delete_key.diff?rev=3199&sc=1

Hereby I am asking for

unblock for
freebsd-utils 8.1-3.1
kfreebsd-8 8.1+dfsg-7.1
ncurses 5.7+20100313-5

And squeeze-ignore tag for 605065, 605777. The 607662 already have it.

Cheers and many thanks

		Petr




Reply to: