私のTech記憶

Manage SSH and GPG keys efficiently in KDE

noreply@blogger.com (龍神) — Thu, 17 Dec 2009 08:02:00 +0000

Introduction

Here I present a simple way to handle SSH and GPG keys easily in KDE4. These method presents several advantages:

Works great with KDE4 that ships with Kubuntu Jaunty and may work in other KDE distributions without too much trouble.

Use Kwallet as the passphrase manager so you unlock Kwallet once on login and from there it will handle all passphrase requests.

Works great with automated tasks (via cron or incron) that use SSH key authentication (e.g. famous rsync unexplained error 255).

Pre-requisities

Considering that you are reading this post because you need a better way to manage you ssh and gpg keys then it is safe to assume you have already generated your ssh/gpg keys and that you know how to use them.

SSH Key management with KWallet

The steps are very simple. First we install the needed software packages:

sudo aptitude install keychain ksshaskpass

Then create an script called keychain.sh inside your KDE autostart folder that loads the key manager (keychain) and configure KWallet to handle the keys passphrases.

vi keychain.sh

#! /usr/bin/env bash
if [ -f /usr/bin/keychain ]; then
  if [ -f /usr/bin/ksshaskpass ]; then
    export SSH_ASKPASS=/usr/bin/ksshaskpass
  else
    export SSH_ASKPASS=/usr/bin/askpass
  fi
  /usr/bin/keychain id_rsa
  source $HOME/.keychain/$HOSTNAME-sh
fi

chmod +x keychain.sh
cp keychain.sh $HOME/.kde/Autostart

Now edit your .bashrc and add the following line to load keychain so all applications you start in the terminal will have access to the ssh-agent and gpg-agent sockets:

source $HOME/.kde/Autostart/keychain.sh

Now when you log back to KDE KWallet will ask you if you want to allow the keychain application to use KWallet. Tell it to allow always and provide your passphrase. From that point on KWallet will take care of that ssh key.

You may add as many ssh/gpg keys as you want by adding them to the keychain.sh script like:

/usr/bin/keychain id_rsa
/usr/bin/keychain id_rsa2
/usr/bin/keychain id_rsa3
...

How to create Netem distribution tables

noreply@blogger.com (龍神) — Thu, 08 Oct 2009 07:51:00 +0000

The Netem and Dummynet emulators are widely used in networking research to achieve emulated network environments that can be used to evaluate new protocols and applications under controlled and repeateable conditions. In the case of Netem it is possible to use custom ditribution tables to better approximate the round-trip-time variations in the nework.

Unfortunately there is little information on how to generate this distribution tables based on real measured data. The only reference available is in the iproute2 source code itself and is a little confusing. After some reading and re-reading I think I finally got the magic formula and here I present it so others can benefit of my work.

First download the iproute2 source code:

git clone \
git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git

Then enter the netem subdirectory and compile the maketable and stats utilities:

cd iproute2/netem
gcc -lm -o maketable maketable.c
gcc -lm -o stats stats.c

Next you need to extract some delay statistics of the channel you want to emulate. Suppose you want to emulate the network between a server in Japan and a client PC in Chile. Then simply run a ping between both machines for some period of time. A whole day of ping data would be enough:

ping 192.168.4.111 > mydata.txt

The command above does a ping to the address 192.168.4.111 and stores the output to a file named mydata.txt. The file will contain the round-trip-times between the local machine and the machine with address 192.168.4.111 like shown below:

PING 192.168.4.111 (192.168.4.111) 56(84) bytes of data.
64 bytes from 192.168.4.111: icmp_seq=1 ttl=43 time=306 ms
64 bytes from 192.168.4.111: icmp_seq=2 ttl=43 time=273 ms
64 bytes from 192.168.4.111: icmp_seq=3 ttl=43 time=310 ms
64 bytes from 192.168.4.111: icmp_seq=4 ttl=43 time=300 ms
64 bytes from 192.168.4.111: icmp_seq=5 ttl=43 time=300 ms
64 bytes from 192.168.4.111: icmp_seq=6 ttl=43 time=304 ms
...

The more data you have the better so leave the ping running for some long period of time. Next we need to extract the round-trip-time data only:


cat mydata.txt | grep icmp_seq | cut -d'=' -f4 | cut -d' ' -f1 > myrtt.txt

The above command will extract all the round-trip-times from mydata.txt and put them in a single column in a file named myrtt.txt. Finally we can create a distribution table that Netem understands using the maketable utility:

./maketable myrtt.txt > mydist.dist

This will create a distribution table and store it in the file mydist.dist that must be copied in a special folder (/usr/lib/tc) so Netem can find it:

sudo cp mydist.dist /usr/lib/tc

Additionally we can obtain the mean and standard deviation of the round-trip-time using the stats utility:

./stats myrtt.txt
> mu = 296.636364
> sigma = 12.808378
> rho = -0.103472

This command gives use the mean (mu) the deviation (sigma) and the correlation (rho) of the round-trip-time. And at last we can now use Netem to emulate the channel's round-trip-time using the following command:


sudo tc  qdisc add dev eth0 root netem delay 296.636364ms 12.808378ms distribution mydist

Note the the distribution name is the same as that of the file we copied inside the /usr/lib/tc folder but without the .dist extension. Now Netem will provide you with a channel that has similar round-trip-time characteristics as those of the real channel.

Embbed cover art in MP3 files with command line

noreply@blogger.com (龍神) — Thu, 03 Sep 2009 02:51:00 +0000

Introduction

I needed a command line (cli) application that would allow me to embed cover art to my MP3 collection in order to get the covers diplay correctly in my wife's iPhone and my own gPhone (HTC-Hero). After months looking I finally found the ideal tool: eyed3.

Embedding cover art in MP3 files

In Ubuntu/Kubuntu install ImageMagick and Eyed3 with the following command:

sudo aptitude install imagemagick eyed3

Then get your cover art in JPG or PNG format using your favorite cover art download tool (I use amarok) or scan your original CD case. Finally use this command to embed the image in the MP3 files:

convert AlbumArt.jpg -resize 300x300\> AlbumArt.jpg
eyeD3 --add-image AlbumArt.jpg:FRONT_COVER *.mp3

The first command uses ImageMagick to resize the image if any dimension is larger than 300px. The second command adds the cover art to all the MP3 files present in the current directory. You can of course use the full path of the location where the MP3 files are located or better write a bash script to apply the covert art to all your MP3 collection.

Note that the cover image is called AlbumArt.jpg and that the resize operation overwrites it. If you prefer to keep the original change the name of the output to something else. Also you can embed more than one image to each MP3 and assign it different types like FRONT_COVER, BACK_COVER, MEDIA, etc. Check eyeD3 help for more information.

The embedded cover art will display correctly in iTunes, iPhone and gPhone without problems.

gPhone cover art for Ogg/Vorbis files

All my Japanese music is in Ogg/Vorbis format mostly because MP3 players cannot agree in the metadata encoding. Each MP3 player I have tried (including Amarok) use a custom (i.e. no standard) way to save non ASCII characters making it impossible to display Japanese correctly in all devices/players I use.

In the other hand Ogg/Vorbis displays the Japanese correctly in all players I use (Amarok/gPhone/ffmpeg/mplayer). The problem I had was with cover art until recently.

For this to work you MUST organize your music in different folders by album and in each album you must create an AlbumArt.jpg file that will be used as cover art for all Ogg/Vorbis files inside that album/folder.


|--Aerosmith
|    |-- Armageddon
|            |-- AlbumArt.jpg
|            |-- I Dont Want To Miss A Thing.ogg
|--Shakira
     |-- Laundry Service
            |--AlbumArt.jpg
            |--Eyes Like Yours.ogg

As you can see I have Artist folders and inside each one I have a different folder for each Album of that artist and finally in each album folder I have an AlbumArt.jpg that is the cover image and all Ogg or MP3 files that belong to that album.

With this layout both Amarok and the gPhone are able to display the cover art of all Ogg/Vorbis files correctly. Note that you must have exactly the same folder layout in the gPhone SD card for this to work and that the cover MUST be called AlbumArt.jpg or the gPhone won't recognize it.

Handling multiple encodings in Vim

noreply@blogger.com (龍神) — Fri, 12 Jun 2009 04:27:00 +0000

Most people edit, load and save files in a single character encoding (i.e. en_US.UTF-8) but for many this is not the case. For me I need to write documents and emails in japanese UTF-8 (ja_JP.UTF-8), Latex in EUC-JP (ja_JP.EUC-JP) and source code comments in Shift-JIS (ja_JP.SJIS).

To handle a certain character encoding there are three things you must consider:

Your editor character encoding

Your terminal character encoding

Your font character encoding support

In the prehistoric era editors and terminal could support a single character encoding so you needed a different pair for each encoding you needed. Believe me when I tell you this was not fun at all.

These days most editors and terminals support a large array of character encodings and a lot of free fonts are available that support all the character sets I need. Still it is necessary to reconfigure each part (editor/terminal) or create different profiles for each character encoding you needed to edit (i.e. link) for the editor and the console.

Today I took the time to understand how vim character encoding support works and I found that it has everything I need and a lot more. By carefully manipulating the the fenc, fencs, enc and tenc configuration parameters I can edit any file in any character encoding with little effort. Here are my .vimrc configuration parameters:

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

"" Character encoding settings

"" By manipulating this variables it is possible to edit all files in one

"" encoding while using the terminal in a different encoding and writing/reading

"" the file in another encoding. Here we set all three variables to UTF-8.

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

" Default file encoding for new files

setglobal fenc=utf-8

" Auto detect file encoding when opening a file. To check what file encoding was

" selected run ":set fenc" and if you know the auto detection failed and want to

" force another one run ":edit ++enc=<your_enc>".

set fencs=utf-8,euc-jp,sjis

" Internal encoding used by vim buffers, help and commands

set enc=utf-8

" Terminal encoding used for input and terminal display

" Make sure your terminal is configured with the same encoding.

set tenc=utf-8

tenc:
This is the character encoding used to display and input text to the terminal. I configure my terminal (Konsole) always in UTF-8 and as far as I know my input method for Japanese (scim/anthy) is also UTF-8 so to avoid visual/input problems I leave this in UTF-8.
enc:
The encoding used internally by vim buffers, help and commands. This does not need to be the same as tenc as vim will convert from one encoding to the other if they differ. This way you can use your native language encoding in your terminal and input method and let vim handle everything internally using UTF-8.

fenc:
Is the character encoding used for reading/writing files. Again this can differ from enc and tenc because vim will convert between them if they differ. This way you can have your terminal configured with your native language (i.e. Japanese, Russian, Chinese...), let vim work internally in UTF-8 and finally save your files in any coding you want by setting fenc.

fencs:
This is used by vim to try to auto detect the character encoding when opening an already existing file. The order in which you put the options is important so read the help ":h fencs" to learn how to set this correctly. For example if I put euc-jp first in the list all my English documents will be detected as euc-jp instead of utf-8 because all English characters are a subset of euc-jp, the same goes for latin1 and cp1250 encodings so make sure to put these at the end of the list. If the auto detection fails and your document is not displayed correctly you can always reload it forcing an encoding using ":edit ++enc=euc-jp" of course replace euc-jp with your desired encoding.

In my example above I set everything to UTF-8 that is recommended because converting from other encodings may cause loss of information. The only parameter I change is fenc when I need edit/save a file in a different encoding.

For example if I want to create a new file in euc-jp encoding:


  - Open new file as normal using vim< 
  - Set file encoding using :set fenc=euc-jp
  - Edit/Save as much as you like and rest assured that your file is euc-jp.

To edit an existing file simply open it and let vim auto detect the encoding using the options available in fencs. To check what encoding was set by vim you can use the command ":set fenc" and it will display the auto detected encoding. If it is not the correct one you can force the encoding by reloading the file using the command ":edit ++enc=euc-jp" replacing "euc-jp" with the encoding you desire.

Vim tips for Latex editing

noreply@blogger.com (龍神) — Fri, 12 Jun 2009 04:26:00 +0000

Simple Latex Makefile

With this simple Makefile you can compile your latex projects from within vim and use the quickfix window in case of errors to traverse and fix them one by one.

#

# This makefile generates a PDF of the MAINTEX file.

# The output can be found inside the build subdirectory.

#

# Makefile based on  http://www.wlug.org.nz/LatexMakefiles

#

#

# This makefile has been tested in Kubuntu 9.04

#

# Prerequisites:

#

# sudo aptitude install ptex-bin ptex-base okumura-clsfiles ptex-jisfonts \

#     xdvik-ja dvipsk-ja dvi2ps gv jbibtex-bin jmpost mendexk okumura-clsfiles \

#     vfdata-morisawa5 dvi2ps-fontdesc-morisawa5 texlive-latex-extra latexmk \

#     dvipng xpdf gs-cjk-resource vfdata-morisawa5 dvi2ps-fontdesc-morisawa5 \

#     cmap-adobe-japan1 cmap-adobe-japan2 cmap-adobe-cns1 cmap-adobe-gb1

# sudo jisftconfig add

#

# When writing Japanese make sure your editor is saving the tex files

# in euc-jp encoding. In VIM this can be accomplished by setting the fenc

# variable:

#

#  - Open file as normal using vim <filename>

#  - Type  :edit ++enc=euc-jp

#  - Type  :set fenc=euc-jp

#  - Type  :set enc=utf-8

## TODO Add rule to convert images

## TODO Add makeindex to create .toc files

###########################################################################

## Put here the file name of the main tex file.

MAINTEX      = main

############################################################################

## Change the followin only if you know what you are doing

LATEXCMD     = platex     # [latex | platex]

BIBCMD       = jbibtex    # [bibtex | jbibtex]

DVIPDFCMD    = dvipdf     # [dvipdf | dvipdfm | dvipdfmx]

PDFVIEWER    = xpdf       # [okular | xpdf | evince ]

DVIVIEWER    = xdvi-ja    # [xdvi | xdvi-ja | kdvi ]

## No need to change anything below this line

TEXFILES     = $(wildcard *.tex)

TEXINPUTS=:$(PWD)//:    # Path to search for .tex, .cls and .sty files

BSTINPUTS=:$(PWD)//:    # Path to search for .bst files

BIBINPUTS=:$(PWD)//:    # Path to search for .bib files

TEXMFOUTPUT=$(PWD)/build  # Output dir for bibtex and jbibtex

LATEXOPTS= -output-directory=build -file-line-error -interaction=nonstopmode

export TEXFILES TEXINPUTS BSTINPUTS BIBINPUTS TEXMFOUPUT

.PHONY: all wordcount charcount pdf dvi

all: build/$(MAINTEX).pdf

build :

        @echo "Creating build directory"

        @mkdir build

build/$(MAINTEX).aux: $(MAINTEX).tex $(TEXFILES) build

        $(LATEXCMD) $(LATEXOPTS) $(MAINTEX)

build/$(MAINTEX).bbl: build/$(MAINTEX).aux

        $(BIBCMD) build/$(MAINTEX)

build/$(MAINTEX).dvi: build/$(MAINTEX).bbl

        $(LATEXCMD) $(LATEXOPTS) $(MAINTEX)

        $(LATEXCMD) $(LATEXOPTS) $(MAINTEX)

build/$(MAINTEX).pdf: build/$(MAINTEX).dvi

        $(DVIPDFCMD) build/$(MAINTEX).dvi build/$(MAINTEX).pdf

dvi: build/$(MAINTEX).dvi

        $(DVIVIEWER) build/$(MAINTEX).dvi

pdf: build/$(MAINTEX).pdf

        $(PDFVIEWER) build/$(MAINTEX).pdf

# Word counting can be done in VIM usng Ctrl-g g but this command also includes

# latex commands. This make rule strips the latex and counts what is left

wordcount:

        @echo Approximate word count: `grep -v '^\\\\' $(TEXFILES)|grep -v '^%'|wc -w`

charcount:

        @echo Approximate char count: `grep -v '^\\\\' $(TEXFILES)|grep -v '^%'|wc -c`

Put all your tex files, images, sty, cls, bib, bst files inside a directory with any subfolder tree structure you like. This Makefile sets some environment variables that allow it to find all these files as long as they are below the current directory tree.

Make sure your main tex file is called main.tex or if you prefer another one replace the MAINTEX variable in the Makefile. Take note that it has no extension!.

Also note that this Makefile is to compile Japanese EUC-JP tex files (IEICE Trans). If you do not need Japanese replace platex with simple latex and jbibtex with bibtex.

All output files generated by latex/platex, bibtex/jbibtex are stored inside a build subdirectory.

Now in your .vimrc you can add the following parameter to compile your latex project:

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

" Working with Makefiles

"

" Press F5 to compile and open the error window if there

" are errors. If there are errors you can use :cn and :cN to

" jump foward and backward thru the error list. Press :ccl to

" close the error list or F5 again to recompile

map <F5> <ESC>:make<CR><ESC>:botright cwindow<CR> " Compile and open quick fix list

map <F6> <ESC>:cN<CR> " Jump to prev error/warn

map <F7> <ESC>:cn<CR> " Jump to next error/warn

Now when editing you latex files press <F5> to compile them and if errors occur you will be presented with a quickfix window where you can use <F6> and <F7> to quickly jump to the previous and next error message.

Additionally this Makefile also has a few useful commands you can invoke from within vim:

:!make pdf to display the pdf file using xpdf or if you prefer a different viewer replace the PDFVIEWER variable in the Makefile.

:!make dvi to display the dvi file using xdvi or if you prefer a different viewer replace the DVIVIEWER variable in the Makefile.

:!make wordcount to display the number of words in all the tex documents. In vim you can also use g<ctrl-g> in normal mode but this also counts latex commands.

:!make charcount same as wordcount but for characters instead of words.

Latex with Vim TagList plugin

We can enable TagList to display important keywords like section, labels and references for easy navigation (link).

First create a ~/.ctags file that contains the following:

--langdef=tex
--langmap=tex:.tex
--regex-tex=/\\subsubsection[ \t]*\*?\{[ \t]*([^}]*)\}/- \1/s,subsubsection/
--regex-tex=/\\subsection[ \t]*\*?\{[ \t]*([^}]*)\}/+\1/s,subsection/
--regex-tex=/\\section[ \t]*\*?\{[ \t]*([^}]*)\}/\1/s,section/
--regex-tex=/\\chapter[ \t]*\*?\{[ \t]*([^}]*)\}/\1/c,chapter/
--regex-tex=/\\label[ \t]*\*?\{[ \t]*([^}]*)\}/\1/l,label/
--regex-tex=/\\ref[ \t]*\*?\{[ \t]*([^}]*)\}/\1/r,ref/

Then modify the taflist.vim file and add a new language. To do this search for "yacc language" and add these line before it:

" tex language
let s:tlist_def_tex_settings = 'tex;s:section;c:chapter;l:label;r:ref'

" yacc language

Now when you open the taglist window you will get a nice list of section, subsections, chapters, references, labels, etc... that you can navigate and use to jump quickly to each of them.

If you do not have the taglist plugin installed you can follow my instructions here.

Reference autocompletion

If you write your labels as \label{fig:something}, then put this in your ~/.vimrc file:

set iskeyword+=: " type /ref{fig: and prec <C-n> to autocomplete references

With this now you can type \ref{fig: and press to get a list of labels you can cycle as shown in the image above.

Spell checking

This is not only for latex files. Simply put the following in your ~/.vimrc file to enable automatic spell checking. Learn how to use the spell checker to correct, add and/or ignore words.

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

" Enable spell checking in latex, bib and txt files

" Commands:

"            [s      ->  jump to next bad word

"            ]s      ->  jump to prev bad word

"            z=      ->  suggest word

"            zg      ->  mark word as good (add to dictionary)

"            zw      ->  mark word as bad  (remove from dictionary)

"            :h spell -> get more details about spelling

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

au BufRead,BufNewFile *.txt,*.tex,*.bib  setlocal spell spelllang=en_us

Mounting Windows Shares Using CIFS on Ubuntu

noreply@blogger.com (龍神) — Wed, 12 Nov 2008 01:53:00 +0000

So you have a cool Buffalo LinkStation Pro Duo or a Windows machine with some shared folders you want to access from your super Linux machine. No problems we have CIFS to the rescue!!

These instructions were tested in Kubuntu 8.10 (Ibex) but shall work with previous versions and future versions of Kubuntu and/or Ubuntu. Also I assume you want the share to be available to all users in the system so you need root access (i.e. sudo).

First install smbfs package:

sudo aptitude install smbfs

Create a directory were you want to mount the shared folder, any place is ok:

sudo mkdir /media/share

If the share requires username and password to access create a password file in you home directory:

sudo echo -e "username=my_username\npassword=my_password" > /root/.share_pass
sudo chown root:root /root
sudo chmod 700 /root/.share_pass

Replace "my_username" and "my_password" with the corresponding user and pass to access the remote share.

Finally create an entry in the "/etc/fstab" file to mount the shared folder in the desired mount point:

//ip-address/share /media/share credentials=/root/.share_pass,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0

Here you must replace //ip-address/share with the ip address of the machine with the shared folder and the complete path to the respective folder.

Finally mount all partitions:

sudo mount -a

Now you must be able to access the shared folder at the remote machine by accessing the /media/share directory.

References

http://ubuntuforums.org/showthread.php?t=288534

NVidia InitialPixmapPlacement=2 really improves KDE speed

noreply@blogger.com (龍神) — Sun, 19 Oct 2008 04:10:00 +0000

Some people say KDE4 rendering speed is slow when using Nvidia cards. I never felt this so I never bothered in applying the proposed solutions. Using firefox (note: this test does not run in konqueror) simply access the penroseTitling test page and run both tests. My first tests are in the image above and as you can see not bad as I have read in the Internet that for some people the Canvas test can take up to 30 seconds while it took 3 seconds on my machine.

Anyway I tried one of the solutions that is simply running this command in the konsole:

nvidia-settings -a InitialPixmapPlacement=2 -a GlyphCache=1

And here are the new times:

Wow this is a real improvement so now I have a kde startup script that calls this command when KDE starts:

# ~/.kde4/Autostart/nvidia.sh
!#/bin/bash
nvidia-settings -a InitialPixmapPlacement=2 -a GlyphCache=1 &

Resources:
http://movingparts.net/2008/10/03/kde-42-trunk-now-rocking-on-my-thinkpad-t61/
http://techbase.kde.org/User:Lemma/KDE4-NVIDIA

Use vimdiff as Subversion diff command

noreply@blogger.com (龍神) — Thu, 09 Oct 2008 13:19:00 +0000

First create a script svbdiff inside the ~/.vim/scripts/ directory that contains the following

#!/bin/bash
shift 5;/usr/bin/vimdiff -f "$@"

and make it executable:

chmod +x ~/.vim/scripts/svndiff

Then create an alias in your ~/.bashrc file like:

alias svndiff="svn diff --diff-cmd ~/.vim/scripts/svndiff"

Now you can go to any Subversion repository and display file differences with

svndiff h264.c

The screenshot above shows the diff output of the h264.c of libavcodec. Make sure you have a color scheme that highlights the file differences. The screenshot above uses the inkpot color scheme.

My Vim Tips

noreply@blogger.com (龍神) — Thu, 09 Oct 2008 12:59:00 +0000

List of my Vim Tips

Basic Vim Configuration with some nice features like 256 color terminal support.

How to configure Vim to take full advantage of exuberant-ctags

How to open new files as tabs in already opened vim console

How to use vimdiff as Subversion diff command

How to handle different file encodings with Vim

Working Latex with Vim

Open new files as tabs in current Vim Console

noreply@blogger.com (龍神) — Thu, 09 Oct 2008 12:22:00 +0000

When programming I like to have a single Vim editor open with all my files as tabs. Until now I was using the ":tabnew" command to open files in the current Vim window as I knew no other way.

Some research led me to the --remote-tab switch that allows to open files as tabs in currently open Vim processes but it seemed to work only with the graphical interface (gvim) and not with the console (vim). But as I made some tests I found this can work with the vim in console mode and more over can be nicely integrated with my favorite file managers (Konqueror/Dolphin).

All I needed to do was configure my bash so it will always start vim in server mode if it is not already and to always use the --remote-tab switch when opening files. To do this I simply added these functions to my ~/.bashrc file:

function v {

   if [ "$#" -eq "0" ]; then

      /usr/bin/vim --servername VIMLOCAL

   else

      if echo "$*" | grep -q -- "--servername" ; then

        # echo "Command already has --servername use it"

        /usr/bin/vim $*

      else

          #echo "Use default VIM server VIMLOCAL"

          /usr/bin/vim --servername VIMLOCAL --remote-tab-silent $*

      fi

   fi

}

function gv {

   if [ "$#" -eq "0" ]; then

      /usr/bin/gvim --servername GVIMLOCAL

   else

      if echo "$*" | grep -q -- "--servername" ; then

        # echo "Command already has --servername use it"

        /usr/bin/gvim $*

      else

          #echo "Use default VIM server VIMLOCAL"

          /usr/bin/gvim --servername GVIMLOCAL --remote-tab-silent $*

      fi

   fi

}

alias vi=v

alias vim=v

alias gvim=gv

With these functions loaded (i.e. source ~/.bashrc) the first time you execute vim/gvim it will start a new process in server mode.

# this command will open vim in the current console
# and display first_file.txt for editing.

vim first_file.txt

The second and all subsequent times you execute vim/gvim the files you set as parameters will be opened as tabs in the already opened vim/gvim instance.

# This command in other console will open the files
# second_file.txt and third_file.txt as tabs in the
# other console with first_file.txt open

vim second_file.txt third_file.txt

The above examples work also with gvim instead of vim. The only drawback is that now it is difficult to open files in a separate console. The best solution I found is to call vim with a different server name:

# This command will create a new instance of vim in the current console window
# and display the other_file.txt file for editing.

vim --servername OTHERNAME other_file.txt

If you prefer not to use tabs and like files to be opened as buffers inside a current running Vim instance then simply replace "--remote-tab-silent" with "--remote-silent" in the above scripts.

Make Vim and Ctag play nice together

noreply@blogger.com (龍神) — Thu, 09 Oct 2008 10:48:00 +0000

The classic tutorial of Ctags + Vim will go something like:

- Install exuberant ctags

- Generate tags for your project

- Also install the tag list plugin

- Use ^] and ^T to jump around the code

In this post I will try to go a little further and show how I manage tags in vim for real and large C projects.

Note that I mostly program in C (not C++), Ruby and Bash so I cannot guarantee my method works for all languages. In special Ctags has problems supporting C++. On the other side I have worked in small projects in Java and Python and I had no problems navigating them with my method.

Pre requisites

The following instructions were tested on a Linux machine installed using Kubuntu 8.10, 9.04 and 9.10. The first step is of course to make sure you have installed Vim and exuberant-ctags in you machine:

sudo aptitude install vim-ruby vim-scripts vim-common exuberant-ctags

If you are new to Vim then you should take some time to set your minimal configuration. You may follow mine if you want link.

Generate system wide ctags

All large projects will use at some point external libraries. My C projects usually use the Linux/FreeBSD system calls, SDL, OpenGL, libavcodec and libavformat among others.

To be able to jump to these libraries we must generate tags for each of them. I usually generate them inside my vim directory but you may create them in a system wide folder.

This is extremely useful to easily find out the members of libavcodec large structs or to quickly find out what are the arguments of SDL functions or system calls.

Ctags for Linux System Calls

mkdir -p ~/.vim/tags
sudo aptitude install linux-headers-`uname -r`
ctags -R -f ~/.vim/tags/kerneltags /usr/src/linux-headers-`uname -r`

Ctags for Ruby core and gem libraries

mkdir -p ~/.vim/tags
ctags -R -f ~/.vim/tags/rbtags /usr/lib/ruby

Ctags Java libraries

# For the java tags to work you need to install java source package.
# In Kubuntu/Ubuntu follow these instructions:
mkdir -p ~/.vim/tags
sudo aptitude install sun-java6-source
sudo mkdir -p /usr/lib/jvm/java-6-sun/src
sudo unzip -d /usr/lib/jvm/java-6-sun/ /usr/lib/jvm/java-6-sun/src.zip
ctags -R -f ~/.vim/tags/javatags /usr/lib/jvm/java-6-sun/src

At this you should be able to create tags for all the libraries you use in your projects. Simply get the source code or development packages of the library and run ctags on the folder that contains the source code and save the tags in a file you can access.

TODO: I really need to research what are the best ctags flags for each language in order to generate the most information possible per tag.

Updating your system wide ctags

Here we have three options:

Update your system/library tags manually each time you upgrade them

Use a cron job to update them every certain period of time (e.g. once a week).
Use incrontab to monitor changes in the system/library folders and automatically update the tags every time these folders change.

Personally I use the cron job method and for some libraries that I update often (e.g. libavcodec from subversion) I manually generate the tags soon after I update the library.

I found about incrontab just recently and I think will be the best way to update system wide tags. It behaves mostly like crontab but instead of triggering actions based on time periods it triggers by file system events like file change, move, save, etc. It should be easy to monitor the folders containing the libraries of interest and regenerate the tags for each library based on change events in the folder contents. The tricky part would be to determine what file system event we must listen to decide if we should regenerate or not the tags.

Generating ctags for your own libraries/projects

Now we need to generate tags for projects/libraries we are developing at the moment. These projects are constantly changing so we need to update them as soon as possible.

This is a common problem that lot's of people solve in different ways. See for example these links:

Vim auto-generate ctags

Vim+ctags tips and tricks

TagsParser : Automatic tagfile updating and tag viewer

vim with ctags for multi-level directory hierarchy

http://vim.wikia.com/wiki/Tags_generation_for_current_file

Auto tags by project.vim

Most methods I found do the same more or less: they set some auto commands to autogenerate tag files when a file is edited and set the search path in a way it can find the generated tags.

I used to have some autocommands in vim to generate tags every time I modified a file in a project. Unfortunately I never figured out how to generate a single tags file per project/library. I always ended with a global tag file for all projects or a single tag file per folder.

Another methods worked by adding tags generation commands to the build system so the tags get generated when we recompile the project (e.g. Makefile, Ant, CMake) and others simply created scripts per project and executed them manually from the project root directory or within vim using a key map.

Since I use the Project.vim plugin it is natural for me to use it to generate the tags files as it is done here. My method is a lot different in that I do not use a Makefile to generate the tags and I only re-generate them when a file has been edited, not every time we open a file.

Auto-generating Ctags Using the Project.vim plugin

Anyone that has used the Project.vim plugin is familiar with the snippet shown below:


 myproj=<src-path> in=in.vim out=out.vim CD=<src-path> {
   CMakeLists.txt
   in.vim
   out.vim
   include----------------- 
   src---------------------
   test--------------------
   tools-------------------
 }

This corresponds to a project entry called "myproj" with root directory set to "src-path". Here the important parts are the "in", "out" and "CD" parameters.

The "CD" parameter makes sure that you are at the project root directory when editing a file from that project. This is useful to have a single tags file per project.

The "in" and "out" parameters are simple vim scripts. The "in" script is executed when opening a file from the project and the "out" script when leaving the file. In these scripts is where I set/unset the autocommands that take care of generating the tags files per project.

Every time I create a new project using the Project.vim plugin I also create these in.vim and out.vim scripts:

in.vim

" let ctags_cmd='/usr/local/bin/exctags' " Use this one in FreeBSD

let ctags_cmd='/usr/bin/ctags' " Use this one in Linux

let proj_path = escape(getcwd(), ' ')

let _ctagargs_ = " --fields=+iaS --extra=+q -R "

let _ctag_ = ctags_cmd . _ctagargs_ . " -f " . proj_path . "/.tags " . proj_path

au BufWritePost <buffer> call system(_ctag_)

out.vim

au! * <buffer>

Now every time you open a file from a project an autocommand will be created for that file that will regenerate tags for the whole project every time the file is saved. The generated tags file is always in the root directory of the project. You may prefer to use the "--append" switch of ctags to generate tags for the current file only but I personally prefer regenerating the tags of the whole project every time.

When you leave the file the autocommand is removed in the out.vim script. If we do not remove the autocommand, it will be created every time we enter the file that results in a lot of autocommands around. I am not really sure if this can cause problems but is better go on the safe side.

Now the last piece of the puzzle is how to tell Vim where to search for the tags.

Tell Vim where to search for tags

To find the per project tags we can simply add this to our vimrc file:

set tags=./.tags;${HOME}

This simple command tells vim to search tag files from the current directory backwards up to our $HOME directory. Since we are sure that we are always at the projects root directory where the tags file is automatically generated we can be sure that vim will always find the tag we are looking for.

There are some system wide tags that we want to always load depending on the language we are developing. For example when I develop in C I would like to have the kernel system calls tag file (that we generated before) or when developing in Ruby/Java I expect to have these languages core tags loaded too.

To do this I load all system wide libraries based on filetype using these commands in my vimrc file:

au BufRead,BufNewFile *.rb setlocal tags+=~/.vim/tags/rbtags

au BufRead,BufNewFile *.cpp,*.h,*.c setlocal tags+=~/.vim/tags/kerneltags

au BufRead,BufNewFile *.rl,*.def setlocal tags+=~/.vim/tags/kerneltags

au BufRead,BufNewFile *.py setlocal tags+=~/.vim/tags/pytags

au BufRead,BufNewFile *.java setlocal tags+=~/.vim/tags/javatags

What these commands do is to load the system wide tag files we generated before depending on the file type. For example when editing a ruby file it loads the Ruby tags file.

We must note that the commands only apply to the current file being edited (e.g. setlocal), not all the files in the project and that we are adding the tags file not replacing the current one (e.g. += ).

Finally how can we add other tag files to the project that are not from the project itself and not system wide?. For example my project requires external libraries like libavcodec and SDL so it would be nice to query the function and struct definitions of these libraries.

To do this I use the "in.vim" script of the Project.vim plugin like:

" let ctags_cmd='/usr/local/bin/exctags' " Use this one in FreeBSD

let ctags_cmd='/usr/bin/ctags' " Use this one in Linux

let proj_path = escape(getcwd(), ' ')

let _ctagargs_ = " --c++-kinds=+p --fields=+iaS --extra=+q -R "

let _ctag_ = ctags_cmd . _ctagargs_ . " -f " . proj_path . "/.tags " . proj_path

au BufWritePost <buffer> call system(_ctag_)

" Add external library tag files

setlocal tags+=~/.vim/tags/sdltags

setlocal tags+=~/.vim/tags/ffmpegtags

This is exactly the same "in.vim" script as above with two added lines that include the libavcodec (FFMpeg) and SDL library tags files to the search path of vim for all files in the project. These files were of course generated before the same way we created the system wide tag files and updated via a cron job.

Once you setup this once you don't need to worry about this anymore until you reinstall your computer. The system wide libraries will be always updated if you configured the corresponding cron jobs and once a project is created it will always have the tags files updated and ready to query.

Setting up the TagList Plugin

No blog post about Vim+Ctags is complete without the mighty TagList plugin. To install this plugin go to http://vim-taglist.sourceforge.net/ and download the taglist_45.zip file. Then add it to your vim installation using the command:

unzip -d ~/.vim taglist_45.zip

Then add these commands to your vimrc file:

" let Tlist_Ctags_Cmd='/usr/local/bin/exctags' " Use this one in FreeBSD

let Tlist_Ctags_Cmd='/usr/bin/ctags' " Use this one in Linux

let Tlist_Auto_Open=0

let Tlist_Auto_Update=1

let Tlist_Use_Horiz_Window = 0

"let Tlist_Inc_Winwidth=0

"let Tlist_Show_One_File=1

let Tlist_Exist_OnlyWindow=1

let Tlist_Use_Right_Window = 1

let Tlist_Sort_Type="name"

let Tlist_Display_Prototype=0

let Tlist_Compact_Format=1 " Compact?

let Tlist_GainFocus_On_ToggleOpen=1

let Tlist_Display_Tag_Scope=1

let Tlist_Close_On_Select=1

let Tlist_Enable_Fold_Column=1

"let TList_WinWidth=25

" Map a F8 to the TlistToggle command for easy tags list access

nnoremap <silent> <F8> <ESC>:TlistToggle<CR>

Of course I recommend you to read the help file and set the configuration as it fits you better. With my configuration you can press to open the tags list window and when you press on a tag the windows automatically closes. This is specially useful on small screen laptops to allow more code visible all the time.

Basic .vimrc file

noreply@blogger.com (龍神) — Wed, 08 Oct 2008 05:43:00 +0000

My first Vim configuration files: .vimrc, plugins, color schemes, etc were very small and modest. It's been eight years since I started using Vim and these configuration files have morphed, evolved, grown and recently shrink in too many ways, more than I can remember, and every time I check www.vim.org I find new ways I would like my Vim to evolve even further.

Here is the simplest version of my .vimrc file with no ctags or desktop integration as these topics require a separate post to explain. Most of the options here can be understood directly from Vim help files and by the comments in the file itself.

If you would like to use this file make sure to copy it in your home directory and read the comments as to get full functionality.

For comparison see the default install and my older configuration screenshot at the end of the post and compare it with my current configuration screenshot at the top of this post.

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

"" General Vim Settings

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

"   In Kubuntu/Ubuntu make sure you have a complete vim install

"   i.e.  sudo aptitude install vim-ruby vim-scripts vim-common

"

" Disable compatibility with vi

set nocompatible

" Use the Unix file format

set fileformats=unix,dos

" Display line number in front of each line in the left margin.

set number

" I keep my own backups and all those files ending in '~' are

" anoying.

set nobackup

" Display commands in the bottom right corner as they are typed.

set showcmd

" Smoother redraws

set ttyfast

" Avoid vim complains about not written file when jumping

" between buffers using ctags.

set autowrite

" Vim Tip #1160 - Auto Save files when focus is lost.

au FocusLost * :wa

" Vim Tip #1279 - Highlight current line in Insert Mode

autocmd InsertLeave * se nocul

autocmd InsertEnter * se cul

" Enable syntax highlighting with 256 color support so we

" can use nicer color schemes. For more information and to

" get some nice color schemes check:

"   http://www.frexx.de/xterm-256-notes/

" Tested with Konsole-2.1 and yakuake 2.9.4

set t_Co=256

syntax on

" Set this background depending on your console and color scheme.

set background=light

"set background=dark

" My favorite color schemes. You must download the color themes

" and put them inside the color folder of your vim installation.

"colors default     " Good fro transparent consoles

"colors zenburn     " Vim Tip #415

colors 256_asu1dark " http://www.frexx.de/xterm-256-notes/

"colors pyte        " Vim Tip #1492

" If in diff mode (vimdiff) use the inkpot color scheme

" that better highlights file differences

if &diff

  colors inkpot    " Vim Tip #1143

endif

" Additional filetypes

au BufRead,BufNewFile sconstruct setlocal filetype=python

au BufRead,BufNewFile *.rl       setlocal filetype=ragel

au BufRead,BufNewFile *.rb       setlocal filetype=ruby

" Additional Syntax Files. The ragel.vim file can be downloaded

" from Ragel's home page http://www.complang.org/ragel/.

au! Syntax ragel source ragel.vim

" Set path to search (i.e. gf) files recursively

set path=/usr/include,/usr/local/include,**;$HOME

" Vim Tip #1274 - Highlight trailing whitespace characters

set list

set listchars=tab:->,trail:·

" Number of spaces used for (auto)indenting

"set shiftwidth=2

" Number of spaces to insert for a tab

"set softtabstop=2

set tabstop=2

" Insert spaces when the tab key is pressed

" If you want a real tab use "ctrl-v, tab" in insert mode. This

" is usefull for Makefiles that require real tabs to work.

set expandtab

" Word wrap with line breaks if they are longer than 80 characters

" long. If you prefer to wrap lines visually only use the wrap and

" lbr commands below instead. If you have a document that has lines

" longer than 80 characters you can use "gq}" to format it as a

" paragraph. This is more easier format for navigating the text.

set textwidth=80

set formatoptions=tcq

" Vim Tip #989: Word wrap without line breaks

"set wrap

"set lbr

" Enable specific indenting

set autoindent

set smartindent

" Enable code folding

set foldmethod=syntax

" Show briefly matching bracket when closing it.

set showmatch

" Show cursor position

set ruler

" Additonal key mappings

map <F12> <ESC>ggVGg?                             " ROT13 fun

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

"" Mini buffer explorer features

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

let g:miniBufExplSplitBelow=0

let g:miniBufExplSplitToEdge = 0

let g:miniBufExplVSplit = 20

let g:miniBufExplMapCTabSwitchBufs = 1

let g:miniBufExplUseSingleClick = 1

let g:miniBufExplorerMoreThanOne=0

let g:miniBufExplModSelTarget = 1

" Map Tab and Shift-Tab for buffer navigation

" Note that S-TAB does not work in certain consoles (i.e. KDE Konsole)

map <TAB> <ESC><C-TAB>

map <S-TAB> <ESC><C-S-TAB>

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

"" Improve VIM autocomplete features

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

" Enable search as you type:

set incsearch

"improve autocomplete menu color

highlight Pmenu ctermbg=238 gui=bold

" http://www.cuberick.com/2008/10/ruby-autocomplete-in-vim.html

autocmd FileType ruby,eruby set omnifunc=rubycomplete#Complete

autocmd FileType ruby,eruby let g:rubycomplete_buffer_loading = 1

autocmd FileType ruby,eruby let g:rubycomplete_rails = 1

autocmd FileType ruby,eruby let g:rubycomplete_classes_in_global = 1

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

" Vim tip #90 Enable VCS integration in vim

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

"  Get vcscommand.zip from http://www.vim.org/scripts/script.php?script_id=90

"  Uncompress to your vim directory:  unzip -d ~/.vim vcscommand.zip

"

"  Now when editing a file that is under revision control (SVN, CVS, Git,...)

"  we can access the versioning commands:

"

"  VCSAdd

"  VCSAnnotate

"  VCSCommit

"  VCSDelete

"  VCSDiff

"  VCSGotoOriginal

"  VCSGotoOriginal!

"  VCSInfo

"  VCSLog

"  VCSLock

"  VCSReview

"  VCSStatus

"  VCSUpdate

"  VCSUnlock

"  VCSVimDiff

" Map F4 to VimDiff to check differences

map <F4> <ESC>:VCSVimDiff<CR>

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

" Latex Configuration

" http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

au BufRead,BufNewFile *.cls      setlocal filetype=tex

"let g:tex_flavor='latex'   " loads latexsuite with empty tex files.

set iskeyword+=:           " type /ref{fig: and press <C-n> to autocomplete references

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

" Working with Makefiles

"

" Press F5 to compile and open the error window if there

" are errors. If there are errors you can use :cn and :cN to

" jump foward and backward thru the error list. Press :ccl to

" close the error list or F5 again to recompile

map <F5> <ESC>:make<CR><ESC>:botright cwindow<CR> " Compile and open quick fix list

map <F6> <ESC>:cN<CR>                             " Jump to prev error/warn

map <F7> <ESC>:cn<CR>                             " Jump to next error/warn

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

" Enable spell checking in latex, bib and txt files

" Commands:

"            [s      ->  jump to next bad word

"            ]s      ->  jump to prev bad word

"            z=      ->  suggest word

"            zg      ->  mark word as good (add to dictionary)

"            zw      ->  mark word as bad  (remove from dictionary)

"            :h spell -> get more details about spelling

""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

au BufRead,BufNewFile *.txt,*.tex,*.bib  setlocal spell spelllang=en_us

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

" Other Good Vim tips not used here

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

" Vim Tip #64   - Set working dir to the file you are editing

"                 Why not used: Makes difficult the management of sessions and

"                   makefiles.

" Vim Tip #305  - List of editing vim tips

"                 Why not used: I can remember all the commands I use.

" Vim Tip #1203 - mapping to set up vtreeexplorer and taglist in left window

"                 Why not used: I use MiniBufExpl instead of vtreeexplorer

" Vim Tip #1318 - An attempt to emulate TextMate's snippet expansion

"                 Why not used: I am unable to get this working correctly.

" Vim Tip #???? - Force gf to open in new tabs

"                 Command: nnoremap gf <C-W>gf

"                 Why not used: I use MiniBufExpl so no more tabs for me.

" Vim Tip #565  - Never see ^M and pesky trailing spaces again

"                 Command: autocmd BufRead * silent! %s/[\r \t]\+$//

"                 Why not used: Not a good idea when working with others source

"                  code. All the automatically deleted chars will be seen as

"                  changes in the diff files making it difficult to review the

"                  changes. Never use this if you plan to submit patches to ffmpeg

"                  or the Linux kernel or they will spam filter you forever!

Canon Satera LBP5910 Linux Driver

noreply@blogger.com (龍神) — Thu, 25 Sep 2008 01:47:00 +0000

If you have a Canon printer based on the LIPSLX driver (i.e. LBP family) then you are lucky because Canon provides the linux drivers for these printers.

Simply go to this page Canon Linux Driver check for the supported printers and the respective drivers. For my case I have the LBP5910F printer that is supported by the LIPS LX Printer Driver so I enter this page and download the two corresponding .deb packages for Ubuntu/Debian. If you use Redhat or any other distribution that uses RPMs then download the corresponding RPMs.

To install in Ubuntu/Debian:

sudo dpkg -i cndrvcups-common_1.70-1_i386.deb
sudo dpkg -i cndrvcups-lipslx_1.70-1_i386.deb
sudo /etc/init.d/cupsys restart

Now enter CUPS configuration page (i.e. http://localhost:631) and follow the steps. In my case the printer was already listed in the select box of printers with IP address and everithing. In Make/Manufacturer select Canon and finally in Model/Driver select the corresponding driver:

And that is all now you can try to print a test page.

Use PuTTY generated keys with SftpDrive

noreply@blogger.com (龍神) — Wed, 25 Jun 2008 03:38:00 +0000

So you created a public/private key pair using PuTTYgen and now you want to use these keys in other applications like OpenSSH and/or SftpDrive but you realise that the private key generated by PuTTYgen is not compatible with these programs??

No worries... all you have to do is convert your PuTTYgen key (.ppk) to and OpenSSH compatible key and it happens to be that PuTTYgen can do this conversion.

Open PuTTYgen and load your private key using the "load" button and opening your private key .ppk file. Once loaded select from the top menu "Conversions -> Export OpenSSH key" and select a file name to save the exported key. Now this saved key can be used in other applications that are OpenSSH compatible.

To use this key with SftpDrive open SftpDrive Manager and on "New Driver" change the Authentication method (see image above) to "Use a public key to log in...". This will open a dialog box (see image below).

Here you can generate a new public/private key pair but we want to use the one we generated with PuTTYgen so select "Import Existing Key Pair" that will open yet another dialog box (see image below):

Here simply browse the location of the private and the corresponding public keys and press "OK". Now SftpDrive will use these keys to connect to your SSH server.

If you get errors make sure you have selected the exported OpenSSH compatible key and not the PuTTYgen generated one (i.e. .ppk). Also if you saved the public key using the PuTTYgen "save public key" button then this key has a format SftpDrive does not understands so it will be unable to read the key. To solve this copy and paste the public key as it appears in PuTTYgen text box (i.e. the large string starting with ssh-rsa or ssh-dsa) in a text file (i.e. mykey.pub) and then import that file as the public key. This format is OpenSSH compatible so should work with no problems.

Subversion + OpenSSH Server + PuTTY Client Setup

noreply@blogger.com (龍神) — Tue, 24 Jun 2008 00:10:00 +0000

This setup is of a subversion server running on Linux (Kubuntu 8.04) and subversion clients (Tortoise SVN) running in Windows (WinXP).

Pre-requisites

I assume you already have a subversion repository working and now you want to access it using ssh tunnelling for security reasons. Also the server must have remote ssh access and be configured to do Private Key authentication.

Setting up Putty

The best SSH client and related tools for Windows are the PuTTY family of programs that can be found at http://www.chiark.greenend.org.uk/~sgtatham/putty/. You can download the individual ".exe" files an put them in your path but I recommend you to use the installer that will install all the tools and set them nicely in your start menu.

Create public/private key pair

Objective

To access the subversion server via ssh you need a public/private key pair. To generate these key pair you can use the PuTTY Key Generator (PuTTYgen.exe) that was installed along with PuTTY installer.

Simply execute the PuTTYgen.exe program and press the "generate" button. After that keep moving your mouse, to generate some randomness, until the progress bar reaches the end. At this point you will get your public and private keys generated.

Make sure you add a "Key passphrase" that will be like a password to access the keys. The comment part is not necessary but is customary to put your email address.

Also make sure you are generating a SSH-2 key pair as SSH-1 is not secure. Choosing between RSA or DSA keys is a matter of application. It is known that DSA is fast at key generation and signing while RSA is faster at verification. So if your application requires a lot of signing (i.e. SSL Web Application) then DSA is good but if your application requires a lot of verifying (i.e. Subversion) then RSA is best. Since we are going to use this key for Subversion I recommend subversion but you are free to use the one you prefer.

Now we need to save your generated keys somewhere in your hard disk. The public key is visible in the PuTTYgen application widget (i.e. the long sequence of letters in the top text box). This key starts usually with "ssh-rsa" or "ssh-dsa" depending on what type of key you generated (RSA or DSA).

To save your public key on disk do not use the "save public key" button as this will generate a key in a format that is not compatible with OpenSSH. Simply copy and paste the key from the text box to a file on disk. You can save this file with whatever name you like but I recommend putting a ".pub" extension just as OpenSSH does.

The private key you must save it using the "save private key" button as this generates a file with ".ppk" extension that is understood only by PuTTY programs. Make sure you put the same name as the public key but with the ".ppk" extension instead of ".pub".

As an additional step if you would like to use your private key with other applications like SftpDrive so these can also connect to the OpenSSH server without need for a password, then you must convert your private key (.ppk file) to the OpenSSH key format. To do this simply select "Conversions" in the PuTTYgen.exe menu and then "Export OpenSSH key" to generate a key that can be used with OpenSSH compatible applications.

Note that with PuTTYgen.exe you can convert your private keys between PuTTY (.ppk) format and OpenSSH format so if you generate your public/private keys using OpenSSH ssh-keygen program you can use them in PuTTY by importing the private key using PuTTYgen.

Setting your public keys

The way the public/private key pair are used is simple. You keep the private key in your local machine usually in a key manager like ssh-agent or pageant and send your public key to all the servers you want to access via ssh.

To set up your public key in the SSH server (assumed OpenSSH server) simply log to the server shell using your account username and password (if you don't have one ask you administrator or if you are the administrator create one yourself). Then copy the contents of your public key file inside the file "~/.ssh/authorized_keys2".

To do this edit the "~/.ssh/authorized_keys2" file with any text editor (Vi, Nano, Kwrite, gEdit) and make sure it looks like in the next figure:

The key must start with ssh-rsa or ssh-dsa depending on the key you generated followed by the key all in one line (i.e. no new lines and spaces) and finally the comment again all in one line.

Finally make sure the authorized_keys2 file has correct permissions by executing "chmod 600 authorized_keys2".

You can set the public key in as many SSH servers as you like so you can access them all using the same private key.

Setting your private key

Your private key must be your most guarded secret and shall not be passed to anyone. Only you should have access to this key because anyone who gets his/her hands on that private key can access all the servers where you installed your public key and we don't want anyone to have that access power do we?

To use a your private key we usually use a SSH authentication agent like ssh-agent in Linux/Unix or pageant in Windows. The PuTTY installer comes with pageant.exe that is the one I use and recommend.

Simply execute pageant.exe from the application menu and a small icon will appear in your system tray. Right click the icon and select "Add key" on the context menu, then browse the directory where you saved your private key (i.e. .ppk) and select it. And that is it....

Testing SSH access

To test open the PuTTY.exe SSH client and create a new session to connect to your SSH server (make sure you save the session). When you open the session it should log you in without asking for any username and passwords. If it asks you for username and password then you did something wrong. Make sure the publickey format is correct on the server and that the private key is set in pageant. Of course make sure the OpenSSH server is running on the remote machine and that pageant is running on the local machine.

Once you can connect to the SSH server without need for a username and password then we can proceed to set up TortoiseSVN to access your Subversion repositories via SSH tunnels.

Setting TortoiseSVN with SSH tunnelling

Once you have SSH set to work with public/private key authentication and have pageant configured configuring TortoiseSVN is a breeze. All you have to do is make sure you use the correct URL format to access the repository.

If you have TortoiseSVN installed try to make a checkout and in the URL put something like:

svn+ssh://username@hostname/dir/to/repo

And you should be able to ckeck out that project over an SSH tunnel. You don't even need to have svnserve running on the server as the svn+ssh scheme tells the TortoiseSVN to start it for you and tunnel it over SSH.

Of course replace username with the username you use to access the SSH server and hostname with the IP address or FQDN of your SSH server. The path to the repository must be absolute path starting from the root "/" directory and have correct access privileges (read/write) for the username you use.

Resources

http://neubia.com/archives/000191.html
http://www.unixwiz.net/techtips/putty-openssh.html

Best gift ever??

noreply@blogger.com (龍神) — Sat, 14 Jun 2008 02:47:00 +0000

Now I can reaffirm that I married the right person, just look what I got for fathers day!!!

I know I do not blog that often but be assured that now I will be blogging none at all for at least a few weeks, or months....

Pulse audio and SPDIF output in Kubuntu (Hardy Heron 8.04)

noreply@blogger.com (龍神) — Sat, 26 Apr 2008 16:16:00 +0000

Preface

Here I will explain how I got my Realteck ALC888 SPDIF digital output working with pulseaudio in Kubuntu Hardy Heron (8.04).

Background (rant so skip if you are in a hurry)

I have a MSI board with integrated Realtek ALC888 Audio card that came with analog outputs only. Fortunately these boards usually come with a SPDIF header where you can connect a SPDIF bracket to get a digital output. These brackets are difficult to get and in my case I had to call the main board dealer (calling customer support) and they sold me one for about USD/30.00. Another alternative I considered was to buy a cheap sound card with SPDIF outputs for about the same amount like the ENVY24HTS-PCI or the CMI8768-8CHPCI but the idea of wasting the ALC888 was daunting.

I needed the SPDIF ouput because my ALLA VIBRAR 5.1ch Headphones have only SPDIF (Coax and Fiber) inputs.

After trying a lot, and I mean a LOT!, alsa was not working well with my Headphones, anything I played througth the digial output would be accompanied by all kinds of artifacts (cracks, skips, pauses) coming out from the headphones.

So I decided to try the recent pulseaudio and once I got my audio working I never looked back at alsa again.

For some reason pulseaudio did not came as default with any of the beta, rc and final installations of Hardy Heron (Kubuntu 8.04 KDE4) so here is how I managed to get Pulseaudio working for me.

Pulse Audio in Kubuntu (Hardy Heron 8.04)

First we install the necessary packages:

sudo aptitude install pulseaudio libao-pulse pulseaudio-module-hal \

pulseaudio-module-x11 pulseaudio-utils libsdl1.2debian-pulseaudio

and then create a .asoundrc configuration file to tell all ALSA applications to use pulse.

pcm.!default {

    type plug

    slave {

         pcm "spdif"

     }

}

This configuration file will set pulseaudio as the default sound server and in this particular case it will also set the digital (SPDIF) output as default. If you prefer the analog outputs simply remove the type plug and slave sections.

The above configuration works and I get sound on the SPDIF output but I also have a stereo jack in the front panel of the PC that was getting wasted. So after some research I got the following asoundrc configuration file:

pcm.!default {

    type pulse

    type plug

     slave {

         #pcm "spdif"

         pcm multi

     }

     ttable.0.0 1.0

     ttable.1.1 1.0

     ttable.0.2 1.0

     ttable.1.3 1.0

}

clt.!default {

   type pulse

}

pcm.stereo {

  type pulse

  type plug

  slave {

  pcm multi

  }

  ttable.0.0 1.0

  ttable.1.1 1.0

  ttable.0.2 1.0

  ttable.1.3 1.0

  }

ctl.stereo {

  type pulse

  card 0

  }

pcm.multi {

  type multi

  slaves.a.pcm "analog-hw"

  slaves.a.channels 2

  slaves.b.pcm "digital-hw"

  slaves.b.channels 2

  bindings.0.slave a

  bindings.0.channel 0

  bindings.1.slave a

  bindings.1.channel 1

  bindings.2.slave b

  bindings.2.channel 0

  bindings.3.slave b

  bindings.3.channel 1

  }

ctl.multi {

  type hw

  card 0

  }

I really do not understand this file so don't ask. This configuration file also allows output from the front stereo jack so I can have both the 5.1ch headphones on SPDIF and an additional stereo headphone working simultaneously.

Starting the server
Let us start the pulseaudio server so we can test some applications:

1 pulseaudio –system=1 –high-priority=1 -D

The recomended way to start the pulseaudio system is per user/session so instead of editing the /etc/default/pulseaudio file I simply create a pulsestart.sh script and put it in our KDE Autostart dir (i.e. $HOME/.kde4/Autostart).

1 !#/bin/bash

2 pulseaudio –system=1 –high-priority=1 -D

This way everytime I start KDE the pulseaudio server gets started too. Now with the server running we need to tell our applications to use it instead of directly accessing alsa.

Pulse audio with Amarok in Kubuntu (Hardy Heron 8.04)
This one is the easiest as it has a configuration panel that allows you to choose the output plugin. See screenshot:

Pulse audio with MPlayer in Kubuntu (Hardy Heron 8.04)

MPlayer in Kubuntu Hardy Heron comes by default with pulseaudio support and in fact uses it as default. If it is not default then you can also force mplayer to use pulse audio with the -ao pulse switch. One way to check if mplayer is really using pulseaudio is to run mplayer from command line and look for a line that looks like AO: [pulse] 48000Hz 2ch s16le (2 bytes per sample). If instead you see alsa or anything else between the square brackets then something is wrong with your installation.

Pulse audio with SDL applications in Kubuntu (Hardy Heron 8.04)

Most games in Linux (i.e. Urban Terror) use SDL audio so we must ensure all SDL applications use the pulseaudio server. When you install the pulseaudio packages this should be done automatically but one bug was preventing the dependency manager to install the needed package: libsdl1.2debian-pulseaudio with:

sudo aptitude install libsdl1.2debian-pulseaudio

Installing this package will enable SDL applications to use the pulseaudio server. We can check this by running a game like Urban Terror and looking at the console. We should see something like:

------ Initializing Sound ------
Initializing SDL audio driver...
SDL audio driver is "pulse".
SDL_AudioSpec:
Format: AUDIO_S16LSB
Freq: 22050
Samples: 1024
Channels: 2
Starting SDL audio callback...
SDL audio initialized.

Pay attention to the SDL audio driver and see what it says. If it says alsa or anything different from pulse then you are not using pulse audio.

Pulse audio with Flash player in Kubuntu (Hardy Heron 8.04)

This one is a little more complicated as we need to install an experimental library but not that complicated and it worked flawlessly in Konqueror and Firefox. Simply follow the next steps:

1 sudo aptitude install build-essential automake1.9 autoconf libtool libesd0-dev libpulse-dev libssl-dev

2 git-clone http://git.0pointer.de/repos/libflashsupport.git/ libflashsupport

3 cd libflashsupport

4 ./bootstrap.sh

5 make

6 sudo make install

What we are doing here is installing some dependencies, downloading the source code of the library from a Git repository, compiling, installing and that is it. Now we have pulse audio support in flash.

The only way I can test that flash is really using the pulseaudio server is to play a flash video and at the same time play music in amarok. If flash is using pulseaudio then you should be able to hear both the flash audio and amarok music simultaneously. If flash is not using pulse audio then the flash video will have no sound or amarok will not play any audio.

Pulse audio with AC3/DTS pass thru in Kubuntu (Hardy Heron 8.04)
Ok so not everything is perfect and pulseaudio does not solves all my desires. The whole idea of the digital ouput (SPDIF) is to be able to send raw AC3 sound to my headphones receivers. This offers the best quality since these headphones have a hardware AC3 decoder so I can get full 5.1 channel surround sound out of them. The problem is that pulseaudio is not able to pass thru the AC3/DTS streams to the SPDIF output.

The solution is to use alsa in this case with the mplayer hwac3 switch like:

mplayer -ac hwac3

that works perfect and there is no need to stop the pulseaudio server. The only inconvenient is that you cannot use any other sound application while the AC3 audio is playing. This is because during the time the AC3 audio is playing alsa is taking control of the sound card and all other applications that rely now in pulseaudio cannot get access to the card.

In my case is not really that big of a problem because when I am seeing a DVD I do not want to hear any other sounds from my PC like knotify.

References
http://pulseaudio.org/wiki/PerfectSetup
http://forums.debian.net/viewtopic.php?t=12497
http://ubuntuforums.org/showthread.php?t=714712

Plotting SVN history??

noreply@blogger.com (龍神) — Thu, 17 Apr 2008 01:18:00 +0000

Found a blog post by Samuel Jansen were he plots his subversion repository history so out of curiosity I plotted mine too...

actually nothing interesting, steady development almost linear and as you can see but it made me notice that I am almost near my 1000 mark!! when I reach it then I will have an excuse to celebrate and give a nice "1000 SVN passed mark present".

Linux Cafe in Akihabara

noreply@blogger.com (龍神) — Sun, 13 Apr 2008 08:00:00 +0000

Have been in Akihabara (Electric Town) several times but never saw this shop before:

If you read the details below the logo you will see this shop is been there since 2001!! and I never saw it... I must go check my eyes. Anyway if you are an Open Source person walking around Akihabara you may well pass a get yourself a nice cup of open source coffee.

Simple Mail Server (Kubuntu)

noreply@blogger.com (龍神) — Wed, 09 Apr 2008 00:05:00 +0000

If you need a small personal mail server to send log reports and system alarms from your Kubuntu machines to a local and/or external mail address then you may use Exim4 that is the default mail server (MTA) that comes with (K)Ubuntu.

To install is very easy:

1 sudo aptitude install exim4 exim4-base

and to configure simply run:

1 sudo dpkg-reconfigure exim4-config

and in the first dialog (image below) select "internet site". For all next options I used the defaults that would allow local users and services to send emails locally and to remote addresses (i.e. gmail accounts).

Now to test the new server you can send a simple email to your Gmail account:

1 mail -s test mygmail@gmail.com

2 test mail

3 .

4 Cc:

The "-s" switch is the mail subject. After the command simply type whatever you want in the mail body. To finish the email press followed by a dot "." and then again. After this you will be prompted with "Cc:" so press and then check your Gmail account. You should have received an email with the message and subject you used above.

Now say you want to receive LogWatch reports or any other mail directed to root in your Gmail account. Then you can simply create an alias in the "/etc/aliases" file like:

1 # Added by installer for initial user

2 root: mygmail@gmail.com

then rebuild the aliases database

1 sudo newaliases

If you require more complex mail configurations you may check my previous posts about Sendmail and Postfix setup in (K)Ubuntu here.

Get latest ffmpeg (svn) in FreeBSD-7.0

noreply@blogger.com (龍神) — Fri, 04 Apr 2008 06:46:00 +0000

If you want to compile the latest ffmpeg from subversion with some external libraries support like x264, faac, Theora and Vorbis in the latest FreeBSD release (7.0) then follow this simple steps:

If you do not have the ports tree installed (i.e. /usr/ports is empty or non existent) then you can use portsnap to download and update it (these commands must be done as root):

1 pkg_add -r portsnap

2 mkdir /usr/ports

3 portsnap fetch

4 portsnap extract

5 portsnap update

Install some ports to enable more funcionality in ffmpeg (these commands also must be done as root):

1 # faac support

2 cd /usr/ports/audio/faac

3 make install clean

4

5 # vorbis support

6 cd /usr/ports/audio/vorbis-tools

7 make install clean

8

9 # x264 support

10 cd /usr/ports/multimedia/x264

11 make install clean

12

13 # theora support

14 cd /usr/ports/multimedia/libtheora

15 make install clean

16

17 # ffplay support

18 cd /usr/ports/deve/sdl12

19 make install clean

Checkout ffmpeg from subversion, configure, compile and install (only the last command needs root priviledges);

1 # checkout ffmpeg from subversion

2 svn co svn://svn.mplayerhq.hu/ffmpeg/trunk ffmpeg

3 cd ffmpeg

4

5 # export library and include paths

6 # so configure can find the external

7 # libraries (i.e. x264)

8 export LIBRARY_PATH=/usr/local/lib

9 export CPATH=/usr/local/include

10

11 # run configure with desired options

12 ./configure --enable-gpl --enable-pthreads \

13 --enable-shared --enable-swscale \

14 --enable-libx264 --enable-libfaac \

15 --enable-libtheora --enable-libvorbis \

16 --enable-encoder=g726 --enable-encoder=ljpeg \

17 --enable-encoder=mjpeg

18

19 # compile using GNU Make (gmake), not BSD Make

20 gmake

21

22 # install

23 su root -c 'gmake install'

If you want to enable other external codec libraries supported by ffmpeg make sure to install their respective ports (if available) and then run the configure script with the desired libraries enabled. You can see a list of supported codec libraries with ".configure --help".

Note that this instructions were tested with revision 12684 of ffmpeg subverion but ffmpeg is a very active project and this instructions are not guarantee to work with the latest subversion revision.

Japanese Input in KDE 4.0.3 (Anthy)

noreply@blogger.com (龍神) — Thu, 03 Apr 2008 01:57:00 +0000

So you want to try the newest and greatest KDE 4.0.3 release but you can't because you need to be able to write other languages other than English like in my case Japanese, Chinese and/or Korean??

After googling I found here that there is a scim input method that allows input of these languages in KDE4 and also fixes some problems with proprietary software like Skype, Adobe Reader, etc.

This input method is called scim-bridge and can be easily installed in Kubuntu with the command:

sudo aptitude install scim-bridge-agent scim-bridge-client-qt4 scim-bridge-client-qt scim-bridge-client-gtk

Then to enable scim-bridge as your input method you can use im-switch:

im-switch -s scim-bridge

or if you do not have im-switch then you can do it manually with:

sudo ln -sf /etc/alternatives/xinput-all_ALL /etc/X11/xinit/xinput.d/scim-bridge

Seems that scim-bridge is now the default input method in Ubuntu/Kubuntu but not sure, see resources below to get more detailed explanation on how to setup SCIM in Ubuntu.

https://help.ubuntu.com/community/SCIM
https://help.ubuntu.com/community/SCIM/Kubuntu
https://wiki.ubuntu.com/InputMethods/SCIM/Setup

Developing Android in Netbeans

noreply@blogger.com (龍神) — Mon, 03 Mar 2008 14:05:00 +0000

Anyone who reads this blog would know that I like Netbeans a lot for mobile development (see here, here, here and here) and when I found that Google's mobile platform (Android) does not have a Netbeans plugin I was very disappointed.

Of course Netbeans enthusiasts developed a plugin (Undroid) but it is not supported by Google, I could not get it to launch the emulator directly from the IDE and currently it does not work with the latest Android SDK so still we do not have a full solution for Android development in Netbeans.

Now if you don't mind working in a mixed setting using Android tools from command line and using Netbeans to code, compile and install your Android applications then here is how you can do it.

Prerequisites

I assume you have the latest Netbeans 6.0.1 already installed and the latest Android SDK m5-rc14 also installed in your computer. I have tested this configuration in my Linux (Kubuntu) machine but should also work in Windows and other Linux distributions.

Creating a new project

The first thing is to create a new project using the activityCreator.py script that comes with the Android SDK:

activityCreator.py --out HelloAndroid org.piaotech.android

this script will create the project skeleton and more important the build.xml file that can be used by Netbeans to build/install your Android applications.

Start Netbeans and create a new "Java Project with Existing Ant Script" as shown in the figure above. In the next screen browse the location of the project directory created by the activityCreator.py script (HelloAndroid above) and the rest of the fields will be filled automatically by Netbeans. You can change the project name if you wish but the default is ok.

In the next screen (figure above) select the Ant tasks that each of the Netbeans commands should execute. I simply put compile for Build Project and install for Run Project.

In the last screen make sure to add the src and res of the project to the Source Package Folders as shown above.

finally select Java Sources Classpath in categories and add the doc directory that is inside the Android SDK as shown in the picture above and press finish.

Running you project

Now you should have your new Android project in Netbeans project view and now you can code and build it as you would using any other Netbeans project. Now if you try to run the application you will get an error indicating that there is no device. This is because I still have not found a way to launch the emulator from within Netbeans so we must launch it manually. From the command line run the emulator:

android-sdk_m5-rc14_linux-x86/tools/emulator

now with the emulator running if you run your project from within Netbeans the Android application will be automatically installed in the emulator.

It takes some effort to setup an Android project in Netbeans and actually there is no benefit from doing this as any java editor with support for Ant scripts can do the same. In my case is simply a matter of preference as all my Java projects are in Netbeans I did not want to have a separate project format only for Android applications.

Note that there is no need to close the emulator each time you rebuild your application so leave it running during the time you are developing. I also recommend you set up a console running the adb logcat command so you can see all the debugging messages (Log.v()) that Android throws.

Dr. Randy Pausch

noreply@blogger.com (龍神) — Sat, 23 Feb 2008 08:56:00 +0000

A very inspirational talk by Dr. Randy Paush.

Reduce GIF size using RMagick

noreply@blogger.com (龍神) — Thu, 21 Feb 2008 16:25:00 +0000

If you are creating GIF images using RMagick and your application has very stringent size restrictions (i.e. mobile devices) then this post may help you get the most of RMagick.

While it is possible to control the compression of JPEG and PNG files using the quality parameter for GIF files we are left with almost no options. Fortunately a little understanding of the default, and only, compression scheme used in GIF can help you improve the compression performance of your images.

The LZW compression algorithm used in GIF images and developed by Abraham Lempel, Jakob Ziv and Terry Welch, contructs a color table for an image wherein each color value is matched to a pixel. Thus, images with large areas of one color will be compressed far better than those that those that do not have such color blocks.

So to get better compression (smaller images) we must ensure we have large contiguous blocks of the same color in our image. When creating images in ImageMagick we can use these tips to ensure small size results:

First: Make use simple graphics with flat colors (i.e. avoid using Magick::GradientFill).

Second: when using an RMagick::Draw object always make sure you call the stroke_antialias(false) method on it:

1 require "RMagick"

2

3 gc = Magick::Draw.new

4 gc.stroke_antialias(false)

5

6 # your drawing code below

Third: When writing text using the annotate method from the Magick::Draw or Magick::Image classes do not use text antialiasing:

1 require "RMagick"

2

3 gc = Magick::Draw.new

4

5 gc.annotate(img,...) {

6 self.text_antialias = false

7 }

A very simple method to reduce the image size is using the despeckle filter on the image. This will reduce the color dither making the color distribution more planar so we have larger portions of the image with the same color. By doing this the LZW algorithm can reduce the final image size up to a 20% of the original size depending on the image.

1 require "RMagick"
2
3 small_image = big_image.despeckle
4 small_image.write("small_image.gif"){
5     self.compression = Magick::LZWCompression
6     self.dither = false
7 }

Actually calling self.compression is not needed as it is set by default by RMagick but is good just to make sure.

Resources
http://rmagick.rubyforge.org/
http://www.faqs.org/faqs/jpeg-faq/part1/section-9.html
http://rmagick.rubyforge.org/src_over.html
http://www.webdevelopersnotes.com/graphics/gifs_compression_algorithm.php3

私のTech記憶

Manage SSH and GPG keys efficiently in KDE

Introduction

Pre-requisities

SSH Key management with KWallet

How to create Netem distribution tables

Embbed cover art in MP3 files with command line

Introduction

Embedding cover art in MP3 files

gPhone cover art for Ogg/Vorbis files

Handling multiple encodings in Vim

tenc:

enc:

fenc:

fencs:

Vim tips for Latex editing

Simple Latex Makefile

Latex with Vim TagList plugin

Reference autocompletion

Spell checking

Mounting Windows Shares Using CIFS on Ubuntu

References

NVidia InitialPixmapPlacement=2 really improves KDE speed

Use vimdiff as Subversion diff command

My Vim Tips

Open new files as tabs in current Vim Console

Make Vim and Ctag play nice together

Pre requisites

Generate system wide ctags

Ctags for Linux System Calls

Ctags for Ruby core and gem libraries

Ctags Java libraries

Updating your system wide ctags

Generating ctags for your own libraries/projects

Auto-generating Ctags Using the Project.vim plugin

in.vim

out.vim

Tell Vim where to search for tags

Setting up the TagList Plugin

Basic .vimrc file

Canon Satera LBP5910 Linux Driver

Use PuTTY generated keys with SftpDrive

Subversion + OpenSSH Server + PuTTY Client Setup

Best gift ever??

Pulse audio and SPDIF output in Kubuntu (Hardy Heron 8.04)

Plotting SVN history??

Linux Cafe in Akihabara

Simple Mail Server (Kubuntu)

Get latest ffmpeg (svn) in FreeBSD-7.0

Japanese Input in KDE 4.0.3 (Anthy)

Developing Android in Netbeans

Dr. Randy Pausch

Reduce GIF size using RMagick