Dan McGhee wrote:

Using LiveCD-pre3 and LFS-SVN I fired up this afternoon to configure the kernel. For the record, I had successfully completed all through Chapter 8.2, "Creating the /etc/fstab File." In my last session I had worked from Chapter 6.56 "Sysklogd" to Chapter 8.2 with no problems. I think I may have left the chroot environment and re-entered is using the /usr/bin/env--but I don't remember. I added this last to show that there were no problems up to but excluding my last session.

I use scripts named "lfschroot.sh" and "devpop.sh" (developed from the hint for using the LiveCD) to 'chroot' and 'populate dev.' I ran '$LFS/lfschroot.sh' followed by ./devpop.sh and got the message: "No such file or directory." To my utter surprise I saw that my command was './dvpop.sh.' Tried again--same results.

Thought the problem may have been in X, so went to a terminal and got the same results. Whether I use:

... /tools/bin/env -i
.....
/tools/bin/bash --login +h

or

... /usr/bin/env -i
....
/bin/bash --login

the results are the same--either in X or in a terminal.

'showkey' gave Keycode 18 for "e" and 'kbd_mode' gave "raw (scancode)"

The REALLY odd thing is that "e" works in vim after I chroot. All I got from googling, FAQ's and hints was how to fix my delete and backspace keys. Those work fine. Additionally, if I copy and paste "devpop" from a "non-chrooted" terminal into a "chrooted" terminal, the result is "dvpop." info {bash,readline} just tell me that my bindings are OK and that "e" is sending the right code. I don't know where to go from here.

Tried an experiment that failed. I used the command mode of vim to run 'loadkeys -d.' Like I say it didn't work. However, I could run commands with "e's" in them from vim. I must have changed something from Sysklogd to /etc/fstab today. Something that affects the console configuration. I just don't know where to start looking.

Thanks,

Dan


--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to