How to highlight SVN diff

By default Subversion shows diff without highlighting which makes a bit difficult review of big changes.

SVN

But that situation can be changed extremely simple and fast. I assume you use Fedora 17. For the other distributions you need just use different package manager, choose correct package name and find configs in the proper places.

First of all, install utility colordiff:
sudo yum install colordiff

Now you can get highlighted output of SVN diff:
svn diff foo.php | colordiff

SVN

But it isn’t convenient way. Since Subversion allows to use any external program to make a diff we just should just add following in the ~/.subversion/config:
diff-cmd = colordiff
And voilà, we can see colored diff just run ordinary SVN diff command:
svn diff foo.php

SVN

UPDATED:
To change colors in colordiff just copy its global config to your home directory and edit it:
cp /etc/colordiffrc ~/.colordiffrc
vim ~/.colordiffrc

Log for Mysql console session

To log Mysql console session use option –tee (two dashes!) with full path to the log file:
mysql -uroot my_db --tee=/tmp/mysql_console.log
As result the file /tmp/mysql_console.log will contains all commands and queries with result of their executions. That might be helpful to keep your queries for using next time or for troubleshooting.

The author of the post, where I found that useful info, said that each time the Mysql session is started with logging the log file will be replaced. In my case it isn’t. As I expected the new messages just are appended to the log file.

KDE 4.1 useful tips and tricks

Preface

When I tried KDE 4.0 first time a few monthes ago I was very disappointed. The system was absolutely unusable. Mainly it was the reason why I didn’t upgrade my Fedora to version 9. But after 10 was released I decided to make an upgrade. I thought that KDE 4.1 should be better. It’s really better but to setup my accustomed environment I spent two days including GNOME configuration because I couldn’t work in KDE. So, I decided to write that post to share my experience and use it my myself what I’ll setup another PC.

Continue reading KDE 4.1 useful tips and tricks

VMWare and kernel 2.6.24.X

Last week I upgrade my Fedora Core 8 to the latest stable kernel 2.6.24.3-12. As result the compilation of VMWare module vmmon gave that error:
/tmp/vmware-config1/vmmon-only/./include/compat_wait.h:60: error: conflicting types for ‘poll_initwait’
include/linux/poll.h:65: error: previous declaration of ‘poll_initwait’ was here
/tmp/vmware-config1/vmmon-only/linux/driver.c:172: warning: initialization from incompatible pointer type
/tmp/vmware-config1/vmmon-only/linux/driver.c:176: warning: initialization from incompatible pointer type
make[2]: *** [/tmp/vmware-config1/vmmon-only/linux/driver.o] Error 1
make[1]: *** [_module_/tmp/vmware-config1/vmmon-only] Error 2
make[1]: Leaving directory /usr/src/kernels/2.6.24.3-12.fc8-i686'
make: *** [vmmon.ko] Error 2
make: Leaving directory
/tmp/vmware-config1/vmmon-only'
Unable to build the vmmon module.

Solution is to use vmware-any-any-update116.
In my case I manually copied patched vmmon.tar, vmblock.tar and vmnet.tar to the /usr/lib/vmware/modules/source because script from vmware-any-any-update116 crashed by some reason.

Upgrade Kubuntu from 7.04 to 7.10

Since a coming version of LinuxMCE will be based on Kubuntu 7.10 I started thinking about upgrade my home PC. I found this manual explained how to do an upgrade using a package manager. I played a bit with Kubuntu installed under VMware and couldn’t upgrade successful. Adopt manager crashed every time when the text of agreements should be displayed. GNOM update manager didn’t detect a new version. So, finally I have to try the manual upgrade from the command line (highly unrecommended by Ubuntu/Kubuntu developers).

Proxy definition for APT

Recently when I started to upgrade Kubuntu from 7.04 to 7.10 using Adopt manager I faced with problem. It doesn’t get proxy setting from the system. To solve that a following line should be added into file /etc/apt/apt.conf (you have to create it if it doesn’t exist):
Acquire::http::Proxy "http://user:password@proxy_URL:proxy_Port";
User name and password can be omitted if you don’t use them.