GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I once had a Window$ OS that came with what they called "English with accents" (EA). I am used to the US keyboard (kb) layout. The EA feature, had the US kb layout. But there was a difference: you could press Meta+'`' (ascii 0x60) and the cursor did not advance. Now you wrote a letter. And the letter got accentuated.
So this is a question not of kb layout but of kb behavior: some keys, in combination with the Alt key, if Alt is the Meta key, do not make the cursor move. Any hint?
Thanks for the post. 'system-config-keyboard' at a console (VT) gets command not found. Then I did this: I booted with the slackware instalation disc and first thing I am asked for is to choose a keyboard map. There were about a hundred of them. I chose querty/us-acentos.map. Then it said: "OK, the <don't remember what> is loaded now. Type any key you want to test. Then type 1 to accept and go on". When I typed "'" or "`" the keyboard stoped to echo. I had to use then backspace. Finally I type '1' on a line by itself and finally exited the setup (I entered typing 'setup').
However, in a console, it's the same as before: no accents (acentos in Spanish means accents). Well, perhaps I should have going on with the rest of the steps in 'setup'. I don't know. I'll try again.
Perhaps for this 'setup' thing, I must use a Spanish or French keyboard. But that would not do for me, as some keys in those keyboards are arranged in a completely different way. Regards.
As you've seen, the console and Xorg manage their keyboards quite differently. Have a look in
and you can see what it does and (if necessary) alter it. The grave accent key defaults to a dead grave, so it won't display anything if you press it.
This file I have it in /usr/share/kbd/keymaps/i386/qwerty/us-acentos.map.gz
I gzip -dv it and part of it is this:
compose '`' 'A' to 'À'
compose '`' 'a' to 'à'
compose '\'' 'A' to 'Á'
compose '\'' 'a' to 'á'
compose '^' 'A' to 'Â'
compose '^' 'a' to 'â'
compose '~' 'A' to 'Ã'
compose '~' 'a' to 'ã'
compose '"' 'A' to 'Ä'
compose '"' 'a' to 'ä'
compose 'O' 'A' to 'Å'
What I don't know is if this map is installed. Seemingly it is not.
I downloaded system-config-keyboard-1.3.0.tar.gz. Then, I made [code]
$ make install
make: intltool-merge: Command not found
make: *** [system-config-keyboard.desktop] Error 127
All that system-config-keyboard does is edit a configuration file to insert the name of your default keyboard: you could do that yourself. And since it's a Red Hat tool, it may not even find the file on Slackware. As you've seen, Red Hat and Slackware put the console keyboard maps in completely different places!
I was looking for certain command, because I had seen, in LQ, mentioned certain command very similar to hexdump. So I did find /usr/bin -name "*dump*". And among the many names listed by 'find', I set my eyes in a dumpkeys name.
It happens that there are the following commands in Slackware 12.0: loadkeys, dumpkeys, showkey and keymaps. Using these commands is the answer to issue being ventilated here. But I must study the manuals. Regards.