Bug#605065: Bug#607662: ncurses-base: backspace key deletes forwards on the kFreeBSD console
On 2010-12-23 19:32 +0100, brian m. carlson wrote:
> On Thu, Dec 23, 2010 at 05:10:28PM +0100, Sven Joachim wrote:
>> I don't see how this follows. People having an xterm-like terminal that
>> is not compatible with Debian's xterm terminfo entry can easily work
>> around it by setting TERM=xterm-r6 or similar when they connect to a
>> Debian machine. What are FreeBSD users going to do when we introduce an
>> incompatible cons25 entry? And what should GNU/kFreeBSD users do when
>> they connect to a non-Debian machine?
>
> If we push the new entry upstream, it will be picked up by the majority
> of Linux distributions, since it will go into ncurses. FreeBSD has an
> ncurses port and so does NetBSD. I believe it is likely that we can get
> the definition pushed to FreeBSD if we can convert it to termcap. If it
> can be converted to termcap, I'll be happy to push it to FreeBSD,
> NetBSD, and OpenBSD, assuming they'll accept it.
How long is that going to take? In the meantime, console users of
GNU/kFreeBSD are screwed whenever they connect to other systems, since
that means they must change their TERM variable _and_ their backspace
key is broken.
> I've attached the necessary patches to create the cons25-debian
> terminfo entry and the patch for sysvinit, which seem to work for me
> in a fresh kfreebsd-amd64 installation in kvm (patching /etc/inittab
> is necessary, though). If they're useful, great; if not, that's okay,
> too.
The cons25-debian name might not be a very good one if you want to that
push terminfo entry to other systems. That may be for Thomas to decide.
Personally I'm leaning towards reverting the changes to the kFreeBSD
kernel and freebsd-utils for Squeeze. Surely, it means a somewhat
broken console, but at least the problems are about the same as in
FreeBSD proper, and we don't create additional incompatibilities with
other systems.
Sven
Reply to: