Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: tried a lot of 'em, now using kubuntu
Posts: 180
Rep:
Weird problem with "single" mode
Wow!
I just had a real weird problem when I tried to boot into single mode. I'm using LFS5.0, and have updated to the 2.6.5 kernel. I'm playing around and starting to get things up to the way I want them, but tonight, when I tried to boot from grub into single mode (by hitting 'e' to edit the line and then append 'single' to it) my keyboard is not responding to the first character typed on each line. AND it tries to go into sh instead of bash, and then will change on it's own over to bash and then back to sh. When it is in the sh shell, vi doesn't work (I get into the program but then the keyboard is dead), and configuring kernel with menuconfig doesn't work (same thing, get into the program but the keyboard is dead). The keyboard is a M$ Natural on a ps/2 connector. Keyboard works fine in init3 and init5.
Root has /bin/bash as it's default shell. And the only thing different in /etc/profile is the stuff that XFree86v4.4 added.
check the /etc/rc.d/rc3.d/ directory for a symlink with something like "keyboard" in the name... check to wich script it links (it links to some script in /etc/rc.d/init.d/) and create the same symlink in /etc/rc.d/rc1.d/.
Distribution: tried a lot of 'em, now using kubuntu
Posts: 180
Original Poster
Rep:
there is a "loadkeys" script but it is in rcsysinit.d, and, IIRC that is supposed to be run every time at startup. So, it should be running anyway.
Oh well, just hope I won't have to use single mode much...
Oh, and I guess I should clarify -- When I said it's trying to go into sh instead of bash, I should have said that it's not running the root .bash_profile. "sh" is just a symlink to bash, so my shell doesn't have my customized prompt.
I thought the rcsysinit.d/ dir only contained symlinks to the scripts in init.d/ too, just like normal runlevels... because the main runlevel control script checks if a file is a link or not when changing runlevels (for the rcsysinit runlevel too). so you should place the loadkeys to init.d/ and symlink to that script from the directories of the runlevels.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.