cursor control in console

Scott Castaline hscast at
Tue Oct 7 10:14:00 PDT 2008

Dan Nicholson wrote:
> On Tue, Oct 7, 2008 at 9:34 AM, Scott Castaline <hscast at> wrote:
>> both ldd /bin/bash & ldd /bin/sh get the following responses:
>> => (0xffffe000)
>> => /lib/ (0xb7ee5000)
>> => /lib/ (0x7dbe000)
>> /lib/ (0xb7ef6000)
> Bash isn't using readline, although I suppose it would be using it's
> own internal copy in that case.
> $ ldd /bin/bash
> =>  (0xb7f84000)
> => /lib/ (0xb7f3d000)
> => /lib/ (0xb7f39000)
> => /lib/ (0xb7df6000)
> => /lib/ (0xb7da9000)
>         /lib/ (0xb7f85000)
> You may want to rebuild bash and make sure you use the
> --with-installed-readline option. Again, that might not be a big deal
> since bash should be using readline one way or another. Also, ensure
> that you've setup /etc/inputrc or ~/.inputrc as described here:
> --
> Dan
Thanks Dan, that was it. Must have missed --with-installed-readline 
option. I tend to hit keys randomly as a result of a neck injury. I have 
found on numerous occasions my pinky hitting the enter key while I'm 
still typing the command. I had caught most of my missing options as I 
went, but obviously missed that one.

My response to ldd /bin/bash now looks more like yours although 
different order and I seem to have one extra one: => /lib/ (oxb7f81000).

Cursor seems to be acting the way it should now.

More information about the blfs-support mailing list