Skip to main content

Compiz on my laptop

After come time spent evaluating the pros and cons I've decided to take the risk and upgrade from Xfree86 to xorg and then install compiz to enjoy the same visual effects that I happen to like so much on when I'm on my mac mini.

On my gentoo 2004 laptop it has not been easy, but following the accurate guide at Gentoo Wiki made it at least painless. I did not even had to edit my xorg.conf, just restart X and it was all there, only much better.

Compiz proved to be much harder, particularly because of some bad interaction with Nautilus that decided to crash when I started compiz and so I had to emerge gnome (from 2.14 to 2.16). Emerging gnome was also not easy, because gnome-cups-manager aborted with compilation errors, due (it seems) to an old gcc (I have 2.3.3). I decided not to upgrade gcc and simply emerged a previous version of gnome-cups-manager and after two days compiling here I am enjoying all the usual desktop composting goodness!

BTW: the new Wanda icons are really better and worth the upgrade alone!

Comments

Popular posts from this blog

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post.
Btw: the recovery, depending on db size and disk speed, is going to take long.

The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux.

The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking.

Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd into the mirth home. …

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).