Debian unstable regains Xen Dom0 support

Good news everyone!

After a long time with no “modern” Linux Kernel available in Debian or Ubuntu for usage as Xen Dom0, the “Big Bang” release has been uploaded to Debian unstable. This actually means all the hardware support etc. from Kernel 2.6.32 AND Xen a simple ‘apt-get install’ away. Maybe we can even get Ubuntu Karmic DomUs running…

There’s some other goodies in it too, see Ben Hutchings Blog.

How to fix broken NX user authentication after OpenSSL fix

It looks like OpenSSH Keys generated on Debian derived distros (Ubuntu/Voyage etc.) are REALLY bad. I’m currently rolling out OpenSSL key updates as adviced on http://wiki.debian.org/SSLkeys.

One casualty of this update was my NX server using freenx. It just tells me that I can’t be authenticated. In the log /var/log/freenx.log it shows the following:

— NX SERVER START: -c /usr/lib/nx/nxserver – ORIG_COMMAND=
HELLO NXSERVER – Version 2.1.0-71 OS (GPL)
NX> 105 hello NXCLIENT – Version 2.1.0
NX> 134 Accepted protocol: 2.1.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: shuerlimann
NX> 102 Password:
NX> 404 ERROR: wrong password or login
NX> 999 Bye

This post talks about the NoMachine NX Server, but gave me the necessary clues: http://lists.kde.org/?l=freenx-knx&m=116542288527396&w=2

The magic command for freenx from http://datakeylive.com
on Ubuntu is

sudo rm /var/lib/nxserver/home/.ssh/known_hosts

This is necessary, as the SSH host key has been updated… Well, a more informative error message would’ve been nice, but I’m thankfull to the guys who produce freenx, anyway;-)

[Feisty Fawn] No degregated RAID update

ADVICE: Don’t upgrade to Ubuntu Feisty Fawn if you’re using LILO on a degregated software RAID. Resync first, as told by this forum posting… I had to boot an old kernel (and who remembers which key to press to show the LILO menu?) The kernel packages weren’t able to build the initramfs and running lilo didn’t help, either. Resyncing was the key to success, though.

[Feisty Fawn] dot local

On of the most useful Feisty Fawn improvements is the integration of avahi. Using MDNS, you may address systems on the same network segment using a hostname instead of IP addresses. It’s dead simple: hostname.local:
{{{
shuerlimann@leni:~/cyt.ch/projects$ ping otherhost.local
PING otherhost.local (192.168.200.225) 56(84) bytes of data.
64 bytes from anon-client225.intern.example.com (192.168.200.225): icmp_seq=1 ttl=64 time=36.5 ms
}}}

Just make sure you allow incoming connections on UDP port 5353.

It looks like systems updated from Edgy Eft don’t get this feature by default. Please give me some hints how to do that if you know how to do it:-)