Like I said, I wanted to go thru' /etc/profile and other config files which include lines I copied from SuSE. Actually, /etc/profile sources these other config files.
After reading thru' /etc/profile I realized that, there're many lines that I don't understand. I'd require to knowledge on the workings of ttys, escape sequences and the like. Therefore, I decided to do the easy way. I removed the file /etc/profile, /etc/inputrc, /etc/login.defs, /etc/bashrc and a couple of other files (from SuSE) thus eliminating the possibility that any of the files will be read. Nope ! That didn't help either. The problem still persists and obviously nothing from the files I mentioned above are playing part in this mess. I'm out of ideas. I sure can live without these Ctrl-C and Ctrl-Z but, just felt that these should work without any tweaking on my part. > Alexander is the guy you'd want to talk to here. The console/kbd is > voodoo to me. But, if you read through /etc/rc.d/init.d/console, you > can start to put together the process. And, yes, the console behavior > is closely tied to the kernel. I wonder how I can approach Alexander with my problem. I guess, he must be receiving a copy of all the mail to and from blfs-support mailing list ! Right ? Thanks, Kevin On Friday 19 January 2007 14:39, Dan Nicholson wrote: > On 1/19/07, Dan Nicholson <[EMAIL PROTECTED]> wrote: > > On 1/19/07, Kevin Williams <[EMAIL PROTECTED]> wrote: > > > I have SuSE 10.2, gentoo and BLFS installed on my laptop. While SuSE > > > and gentoo (and others like Mandriva, Kororaa....) setup the keyboard > > > to behave the way it should, I just can't get it do the same in BLFS. > > > > > > These are the problems I'm facing with the keyboard. > > > > > > 1) Ctrl+C and Ctrl+Z do not work while in single user mode. But these > > > key combinations do work in other runlevels > > > > You mean single user mode on the linux console correct? I'm not sure > > why this wouldn't work. Single-user enters a shell through sulogin. > > According to sulogin(8), /etc/profile is not read in this setting. In > > that way, you wouldn't get the INPUTRC settings. Possibly, this is > > causing problems. But the console script is run, so I don't know. This > > is not my area of expertise. I don't spend much time on the console. > > Now I read sulogin(8) again. Try changing inittab so that sulogin > actually starts a login shell. Change > > su:S016:once:/sbin/sulogin > > to > > su:S016:once:/sbin/sulogin -p > > I don't know if that'll help, but it's worth a try. > > -- > Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
