How disappointed I would be. I started work again and suddenly my X session was killed again, and again and again. And then I saw it, I was not pushing the Ctrl-Alt-Backspace combo, but I tried to insert text with Shift-Insert and accidentally hit Shift-Backspace. Now I had a point to start my search.

Googling and file digging revealed that my keyboard was set to PC-101 and that it should be PC-105. Strange, but solvable. I switched the keyboard in the XFCE settings panel and my problem was solved. It can also be solved by adding

setxkbmap -model pc105 -layout us -variant basic

to the startup script for your window manager.

But, of course, I could not just accept the solution and leave it to that. The problem turned out to be Compiz, the fantastic OpenGL accelerated desktop. This has a feature that the Shift-Backspace turns out to be for debugging purposes.
Yeah, right! We already had Ctrl-Alt-Backspace for that, right!

These patches are mostly focused on window management such as (This list is not complete):

• win_allowRestore
• win_allowMove
• win_allowSize
• win_allowMaximize
• win_allowMinimize
• win_allowHide
• win_allowRollup
• win_allowRaise
• win_allowLower
• win_allowLayer
• win_allowMoveto

and some are focused on system control (reboot and family)
All these options can be controlled through the preferences file.

What I didn't like was the fact that every link opens in the current page. I think (and you may disagree, yes really, you may) that an external link can be opened in a different tab or window.

So I patched the Markdown Perl script and added an extra option for links.

Now I can define two sorts of links:
The internal (opens in the same window or tab):

[Link text](the URL to the link)

The external (opens in a new window or tab):

[Link text]{the URL to the link}

Note the subtle difference between the two. The internal uses () and the external {}.

Just take a look at the patched Markdown.pl

Update 1

When I was generating my complete site I noticed that something broke the W3C compliance. Looking into it I found that it had to do with the patched Markdown.pl. It introduced a underscore and further in the process it is translated into some HTML-code.

I've corrected the problem and a new Markdown.pl is now available.

What vigit does is let you edit a file and when you quit it (after saving of course) it commits the file to git, get's the git-hash and replaces this in the file (if it's already there).

The only drawback is that the files in git are not identical to the ones on disk. I have to find a solution for this.

When you use the header script, this will give you a box with all the supported keywords. This box looks similar to:

#------------------------------------------------------------------------------#
#                    V e r s i o n   i n f o r m a t i o n                     #
#------------------------------------------------------------------------------#
# $Id:: vigit 14 2009-02-26 12:53:11Z tonk                                  $: #
# $Revision:: 14                                                            $: #
# $Author:: Ton Kersten <Ton.Kersten@ATComputing.nl>                        $: #
# $Date:: 2009-02-26 13:53:11 +0100 (Thu, 26 Feb 2009)                      $: #
# $Hash:: vigit e2963ac 2009-02-26 13:37:17 +0100 tonk                      $: #
#------------------------------------------------------------------------------#
#             E n d   o f   v e r s i o n   i n f o r m a t i o n              #
#------------------------------------------------------------------------------#

Get vigit here.

But, how to do this. I took the easy road and created an user on my home server and made sure I could login with SSH key authentication. After that I did:

ssh git@server
mkdir ~/repos
cd ~/repos
mkdir <new repo>
cd <new repo>
git --bare init
git config gitweb.owner "Ton Kersten"
git config gitweb.description "Description of this repo"

Edit the file ~/repos/<new repo>/description and add a descriptive text for this repository.

On the develop client the next mantra is used:

mkdir <new repo>
cd <new repo>
git init
git remote add server ssh://git@server/home/git/repos/<new repo>
git config gitweb.owner "Ton Kersten"
git config gitweb.description "Description of this repo"

Place a nice description in the file .git/description.

Also create a global git configuration file with the commands

git config --global user.name "Ton Kersten"
git config --global user.email "Weblog_at_TonKersten.com"

Now it's time to code your fingers to the bone.

After testing, recoding and testing it's time to commit all changes:

git commit -a

and after getting home:

git push server master

It goes like this:

Make sure the new SAN devices are visible

ioscan -Cdisk

Create the device files

 insf -Cdisk

Find out what the current device of a volume group is

 vgdisplay -v <volume group>

Give the next command sequence

pvcreate /dev/rdsk/<new SAN device>
vgextend /dev/<volume group> /dev/dsk/<new SAN device>
for f in $(vgdisplay -v <volume group> | awk '/LV Name/ { print $3 }')
do
    lvextend -m 1 ${f} /dev/dsk/<current SAN device> /dev/dsk/<new SAN device>
done

Now it's time for some coffee and a long wait. The system mirrors all logical volumes in the volume group

After the mirroring is done

for f in $(vgdisplay -v <volume group> | awk '/LV Name/ { print $3 }')
do
    lvreduce -m 0 ${f} /dev/dsk/<current SAN device>
done

After some testing time, when the system is considered fully functional, the old SAN can be disconnected. This can leave stale devices, but that can be solved easily with a reboot.

 pvreduce <volume group> /dev/dsk/<current SAN device>

The only thing this program needs is Perl and a file in your home directory called .name.info. This file should contain a tag and the value on a single line. An example:

name Ton Kersten
firm Ton Kersten
adr1 Address line 1
adr2 Address line 2
adr3 Address line 3
zipc Your zip or postal code
cntr The Netherlands
tele Tel: Telephone number
tfax Fax: Faximile number
mail Email adress
cpri Copyright string

Header output

The output of the header --help command

header 4.9 by Ton Kersten
Syntax: header [options]

Options:
    --nameinfo=filename Use an alternative name.info file <~/.name.info>
    --language=language Programming language <bash>
    --file=filename     Output filename
    --copyright=cpy     Copyright message (<short>|yes|gnu|none)
    --short         Use a short header
    --stdout        Print the output to stdout
    --headlang=nl|en    Which header language to use <en>
    --tabstop=n|--ts=n  What tabstop size to use <4>
    --width=n       What headerwidth to use <80>
    --vcs=cvs|svn|none  What version control system to use <svn>
    --help          Print this help

Options can be abbriviated, as long as they can be uniquely identified

Supported program languages:
    atroff bash c config html init js ksh latex nagios pascal
    perl php rexx spec tic vim

The header script

...can be downloaded here