another issue directly connected with tha CAPS-LOCK one, as far as it sounds to me, is a sort of 1 or 2 seconds freeze in the terminal after pressing tab, that happend only sometimes, and make me think of some piece of software listening to that key.
Maybe the OpenBSD started by default by crd setup (debian start)?
The delay happens to me too, but I noticed it happens when I push tab on a command prompt without any typed letter yet... so the shell completion has to look up all the commands avaiable to give a list and it takes some time.
Otherwise I suppose it could happen with filename completion also, when you have several files to look through, or when you have a not-so-idle CPU...
About the OpenBSD sshd daemon started by default, I doubt it can interfere with keyboard mappings or delays (although you could experience the tab delay when the daemon is starting and eating some CPU cycles).
And a note by the way... (this doesn't have any to do with the key stuff, but I thought it deserved a mention anyway):
The init script called "zdebian" COULD be disabled altogheter. After all, if:
you don't want to start services (like sshd) in the chrooted enviroment
you can type commands in the native (pdax) enviroment so don't need the rootcmd fifo
you don't need to run zapmd (not advised with pdax, btw)
you don't need to copy /etc/resolv.conf and friends
... then you can simply call "Crd aterm" and get a working chrooted enviroment aterm (after all, you just want to chroot and run a command!).
There's just one thing to remember: this way you don't have /proc mounted in the chrooted enviroment, so this can cause problems (with mount, su, and other commands).
If you are running as root, you can simply edit the "Crd" script to do a mount of /proc inside the chrooted enviroment, though.
I hope I aven't written anything stupid
Ciao,
Andrea
Show Posts