Re: Backspace is not working in a chroot environment

[RAJESH DASARI]

Hi ,

Thanks for your quick response.

This is not an issue from core-utils as you mentioned.

I found the fix for this issue ,  i have copied the terminfo database
file of the xterm editor to the /usr/share/terminfo of the chroot
directory , it is working fine now.
ncurses libraries are expecting the terminal database files.


Thanks,
Rajesh Dasari.


On Thu, Aug 3, 2017 at 4:29 PM, L A Walsh <address@hidden> wrote:
> RAJESH DASARI wrote:
>>
>> Hi ,
>>
>> I did chroot on my environment and  after i switched to the chrooted
>> directory ,backspace key is not working properly , when i enter
>> backspace it is taken  as a "space".
>>
>
> ---
>    This is not likely a coreutils issue, but likely a behavior
> of the how your chroot environment is different from your default
> environment.
>
> According to the trace you included below, the BackSpace key
> it is being interpreted as the "DELETE" (DEL) key, not as
> "BACKSPACE" (BS) or 0x08 (\010).
>
> To see values for the erase key, use "stty -a|grep erase".
>
> Try that before and after you chroot.
>
> After chroot, you'll likely see erase = ^H, when you
> probably want it to be 'erase = ^?'. To set it,
> just type:
>
>  stty erase KEY
>
> (where you press your backspace key where it says KEY).
> If your KEY has a special meaning (like it was mapped to
> some function, you'd have to press "control-v" before they
> key to get the literal key).
>
> Likely, when you chroot, some init script is
> run to set keys like 'erase' to some default value, but some
> other script that sets it to your *desired* value isn't
> getting run (example: maybe a system /etc/profile gets
> run when you 'chroot', but your normal user init-script
> isn't run).  It depends on what shell you are running
> and what the differences are between your normal and your
> chroot environment are.
>
> You can temporarily fix it by resetting the key used for 'erase'
> (using stty), and/or find the differences in your normal
> and chroot environments and make sure the chroot environment
> calls a script to re-set the key to your desired value.
>
>
>