Vmware workstation, fresh out of the box, did not want to run on openSuSE, claiming it could not find any modules:
$ vmware
Logging to /tmp/vmware-vidarlo/setup-17389.log
modinfo: could not find module vmmon
modinfo: could not find module vmnet
modinfo: could not find module vmblock
modinfo: could not find module vmci
modinfo: could not find module vsock
modinfo: could not find module vmmon
modinfo: could not find module vmnet
modinfo: could not find module vmblock
modinfo: could not find module vmci
modinfo: could not find module vsock

The problem was that the modules were precompiled, and included with VMware workstation. However, these did not insert into the running kernel (2.6.27-x86_64).

Removing the precompiled modules did the trick for me – simply rm -Rf /usr/lib/vmware/modules/binary should remove ‘em, and force VMware workstation to compile the modules on next run. This worked nice for me. If you’re cautios, you might want to move the modules instead of removing them…:)

Please note that you need gcc, kernel source and other build dependencies to compile the VMWare modules So right now, VMware workstation works like a charm. Even though they don’t support anything newer than 10.3 officially…

This is written from my openSuSE-perspective, but I can’t see any reason why it shoudn’t work on (almost) any Linux distribution showing similar problems with VMWare…

I recompiled PHP, with same options as last time, same version, but –with-curl added to the end of the options string. I got this error. So, the only change was the –with-curl-option. I tried without it, but no, same error. The result? libphp5.so was not compiled correctly, and PHP was not working…

The culprit turned out to be that libcurl and libxml was not compiled with different GCC versions, so they did not play well along. It was fixed by running an apt-get update && apt-get upgrade. However, I’m a bit baffled by the fact that PHP was not working even when compiling without CURL… I’m not sure why it did not work when compiling without curl, since no other changes were made to that box…

Oh, and to make it even better: PHP claims its not their problem… They could atleast give a bit more informative error message. But my suggestion is to ensure that all your libraries is up to date. The culprit in this case was libxml2 and curl, but it might be other libraries next time…

Rsnapshot er basert på at du skriver backup til disk. Disk er kanskje ikkje like pålitelig media som tape, men for min del holder for min del. I tillegg til å ha backup på disk køyrer eg ting frå disk ut på tape ein gong i veka…

Kort sagt eit genialt program for dei som har enkle behov innen backup, og som ikkje vil bruke alt for mykje pengar på dette.

<?php
$num_posts = 5; //Number of posts to show.
require('wp-blog-header.php'); //WordPress configuration. Change if you don't place this in the root of your wp-installation
$sql = "SELECT `post_excerpt`,`post_title`,`user_nicename`,`user_url`,`$wpdb->posts`.`ID` FROM `$wpdb->posts` INNER JOIN `$wpdb->users` ON `$wpdb->posts`.`post_author` = `$wpdb->users`.`ID` WHERE `post_status` = 'publish' ORDER BY `$wpdb->posts`.`post_date` DESC LIMIT 0,$num_posts";
$arr = $wpdb->get_results($sql);
foreach ($arr as $posts) {
$permalink = get_permalink($posts->ID); //Function to get permalink.
$string = $string . "<h1 class=\"blogheading\"><a href=\"$permalink\">{$posts->post_title}</a></h1> <p class=\"blogauthor\"><a href=\"{$posts->user_url}\">{$posts->user_nicename}</a></p><p class=\"blogexcerpt\">{$posts->post_excerpt}</p>";
}
echo $string;
?>


You can see a demo here. I don’t use excerpts on my blog, so nothing will be shown for the excerpt. Feel free to use as you want. A nicer version of the source can be seen here.

Update: I changed this to show the permalinks.