Monthly Archives: April 2009

Remapping Keys in X for Linux

I do not have any purpose for the Caps Lock key. So it remains useless in a prime real estate position. But I use an open-source operating system (GNU/Linux, xmonad GUI), which means that I can remap that key to do something useful. Here is how to remap the Caps Lock key to become a third Control key through your Linux terminal emulator:

xmodmap -e “remove lock = Caps_Lock”
xmodmap -e “add control = Caps_Lock”

Test it out now. Go open new tabs in Firefox with one hand without straining your fingers. Just press “Caps Lock (Now Control) + t”.



Now for some background on this. Start by entering this command into a terminal:

xev

With the pop-up box selected, Press and Release the Caps Lock key and then the left Control key. The keycode and the name associated with that keycode will be displayed for each of the keys will be displayed along with other information. Write it down.

Output from xev

Output from xev

Next, enter into the terminal:

xmodmap

This will display the information for which keys are acting as modifier keys. The two commands originally issued with the “-e” switch modified which keys act like modifiers. First, the key called “Caps_Lock” was removed from the “lock” function. We added it to the “control” function instead.

Modified xmodmap Output

Modified xmodmap Output

If you want to see every keycode assigned on your keyboard, enter the command:

xmodmap -pke

Between the output from that command and the functions of “xev”, you should be able to figure out the name of any key on the keyboard. This includes funky custom keys that are not standard.


If you mess something up, restart your computer with the mouse if you killed the keyboard, or just restart X with “Control + Alternate + Backspace” (Not Delete). This will reassign your keys to their default.

If you want this to stick between sessions, you will need to edit some files in your home directory. Check you “home” directory with:

ls -a | grep “\.”

If the “.profile” and “.Xmodmap” files are not listed, create them with a text editor as will be discussed:

Open up a text editor and have it open or create the file “.Xmodmap” in your home directory. Otherwise known as “/home/YOURUSERNAME/.Xmodmap”. Paste Xmodmap commands into there if it is new; at the end if there is stuff in this already existing file.

remove lock = Caps_Lock
add control = Caps_Lock

We removed the “xmodmap -e” because these commands are being run within the “.Xmodmap” file.

Save, and close. Now open the “.profile” document and drop this onto the end of it:

xmodmap $HOME/.Xmodmap

For those left-handed people who would prefer to have their mouse viewed as left-handed, and have the primary button on the right side of the mouse, enter this command:

xmodmap -e “pointer = 3 2 1”

This will switch the order of your primary and secondary click buttons. If you like this, paste “pointer = 3 2 1” into “.Xmodmap”, too.

Advertisements

Leave a comment

Filed under Computing, How-To

Compiling Mozilla Firefox on 32-bit Ubuntu Linux


Remember to double-check these procedures against what is posted on https://developer.mozilla.org/ and your own common sense. Developmental software can change quickly and requirements come and go.



If you want the newest version in development, this is the only way to go.

Everything here is merely a re-hashing of the guidelines set forth by Mozilla. The beginning of the procedure can be found here.

This was done on Linux Mint 6.0. This is a derivative of Ubuntu, so it should work there, too. In other words, this article is meant for Debian-like operating systems with apt-get.

To start, install what Mozilla deems the absolute basics. You may or may not already have some of these. Merely run the bold command in a terminal, or hunt and peck through your package manager for the individual files. They should appear in the package manager exactly as they are listed here.

sudo apt-get install mercurial libasound2-dev libcurl4-openssl-dev python-setuptools python-dev build-essential

Mercurial (the code grabber) may not be completely updated from this. To get the latest version:

sudo easy_install -U mercurial

Now we need to configure Mercurial. Only developers need a merger program, but we will install one anyway. I recommend “meld.”

sudo apt-get install meld

Open up the file “/etc/mercurial/hgrc” with root privileges. For example:

sudo vim /etc/mercurial/hgrc

Drop this into there:


[ui]
username = Your Real Name
merge = your-merge-program (or internal:merge)

[diff]
git = 1

[defaults]
diff=-p -U 8


It should look something like this:

Now, to get the bloody-fresh new code. Download it via Mercurial and then enter the directory we just created. I would recommend entering this command from inside a “Projects” folder. Do not do this near anything important, or those files will get lost in the mess.

hg clone http://hg.mozilla.org/mozilla-central/ src

cd src

Downloading Using Mercurial

Downloading Using Mercurial

Now we need to install automake Version 2.13 because Firefox is picky about that.

sudo apt-get install automake2.13

We need to create a file called “.mozconfig” to handle some details for us. Make sure you are in the top level directory (src) if you are following this exactly) of all the source you just downloaded. Then copy and paste these lines:

echo ‘. $topsrcdir/browser/config/mozconfig’ > .mozconfig

echo ‘mk_add_options AUTOCONF=autoconf2.13’ >> .mozconfig

That will add two lines to the “.mozconfig” file that will be automatically created.

Finally, still in that top-level directory, begin compiling with the command:

make -f client.mk build

Checking Prerequisites

Checking Prerequisites

Depending on the Distribution of Linux, different things will be missing. For example, after beginning the prerequisite check, “make” spit back this:

Something is Missing

Something is Missing

I had to:

sudo apt-get install dbus-glib-1

to fix that, and then:

make -f client.mk build

again. If no additional problems are found, compiling will begin. This cannot be disturbed for the time that it is running. So do not close the terminal. It may take a few hours to compile.

After it has finished, and you are given control of the terminal again, you will want to run the new binary and see if it works. Close all instances of Firefox open, and then head to the top of the source directory. To run the new Firefox binary, and not the one from the repositories,

./dist/bin/firefox

Leave a comment

Filed under Computing, How-To

The Age of Firefox

Mozilla Firefox comes in a few different versions, depending on how new you want yours to be. There is:

Old-Hat Firefox – For people who do not like to upgrade their software. These are the versions that are years old. This stuff is OLD. Historical purposes only. Rising software security scientists might be interested in testing legacy exploits against this old browser. Because historical exploits are excellent sources to learn from.

Now-Firefox – What Mozilla says you should be using. People who update their systems when they should will be running this. Has the best stability of the gradient. If you want to browse the Internet and parse HTTP protocols and do all that normal stuff, this is where you should be.

Download here

New-Firefox – The stuff you read about in the technology publications. “Mozilla to release version Y.XX” and “New Firefox slated to be twice as slow and three times as memory hungry.” That sort of rot. Not a bad thing to use if you would like to help Firefox out. Download, install, and then run along. Be forewarned, it is new, so some extensions will not work and some websites will break.

Bloody-Edge-Firefox – For developers. This is that steaming pile of code that someone just dropped off minutes ago. No, really. This is updated every other minute and the people using this version are always compiling. Not for people who want to spend more time browsing than watching “make flags” fly by.

Leave a comment

Filed under Computing