If you have followed the guide in “Xen on Ubuntu Server 8.04 (Hardy Heron) with complex disk setup” or have an environment similar to that, please read on – if not please read on, too 
. Since my server is hosted at Hetzner, this guide will be based on that. I want to use network bridging.
Read the rest of this entry »
Mikkel Meyer Andersen |
16:58 (UTC) |
13 Comments »
Hetzner, LVM, mdadm, raid, Ubuntu, Virtualization, Xen, xfs This is a tutorial about how to use Ubuntu Server 8.04 as dom0 (host) for Xen, i.e. how to install Xen on Ubuntu Server. In a later post I’ll show how to install domUs (guests). The whole setup is done with a rather complex disk configuration using both raid 1 (mirroring) and LVM. It requires some knowledge about Xen (e.g. I’ll not try to convince you to use Xen – I assume it’s already your plan and you had read of all the advantages it gives you ).
Read the rest of this entry »
I’ve been using both Debian and Ubuntu on both server and desktop for some years now, but I think it’s time to try something new so I’m not getting stuck and reject everything that’s new (not that I tend to!). I think I’ll have a closer look on FreeBSD: installation, updating, etc. – seen from a Debian/Ubuntu user’s point of view.
Read the rest of this entry »
Yesterday I wrote an entry regarding ESXi. More precisely I described how to try VMware ESXi in VMware Workstation. My argument was on one side to try ESXi out (I’ve never installed nor tried it) and on the other side investigate whether it was a product I would use.
The case is that I have a server on which I want to run some sort of virtualization – I don’t think it’s appropriate to discuss why virtualization is a go (if you think so, search the web for articles regarding this subject – there are more than plenty discussing this matter). I need at least to host a web server and a mail server – and it would be great to be able to have some sort of playground, too. My mind’s almost made up in regards to the software for the web server and mail server: Ubuntu Server (or maybe FreeBSD – time will show ). But what about the virtualization software?
Read the rest of this entry »
Today I tried to install MuPAD (a 32-bit application), but got the error:
package architecture (i386) does not match system (amd64)
Actually the support didn’t help much although it said that 64-bit systems were able to run MuPAD. It turned out they forgot to specify the right command:
sudo dpkg --force-architecture -i mupad-4.0.2-1-linux-i386.deb
Instead they wrote that this should be executed (but as stated, it doesn’t work):
sudo dpkg -i mupad-4.0.2-1-linux-i386.deb
(I know it’s quite simple — maybe that’s why I didn’t find anything on my search — but I’m just posting this hoping it would help others.)
I’m quite lazy, so I’m using the authorized_keys-thingie (I actually don’t know the real name, but I’m sure you know what I’m talking about ).
The reason for this post is a “feature” I just discovered today. Maybe it’s obvious for everybody (except me), but I was aware that newlines in the remote authorized_keys-file mattered. But they do! So please remember to put every entry in one (1) line only!
Before I did it I got the errors like:
debug1: Host '[host]' is known and matches the RSA host key. debug1: Found key in /home/[username]/.ssh/known_hosts:3 debug2: bits set: 524/1024 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/[username]/.ssh/id_rsa (0xXYZXYZXYZ) debug2: key: /home/[username]/.ssh/identity ((nil)) debug2: key: /home/[username]/.ssh/id_dsa ((nil)) debug1: Authentications that can continue: publickey,password debug3: start over, passed a different list publickey,password debug3: preferred gssapi-keyex,gssapi-with-mic,gssapi,publickey,keyboard-interactive,password debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/[username]/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply Connection closed by [IP of host] username@desktop:~$
Indexing is for computer abusers, not computer users – tough statement, but for me it’s right . In combination with mdadm (and especially when compiling OpenMoko) I’ve had some serious performance issues. The disk was working all the time – and it was not just syncing the /dev/md(/)0-device.
So just a quick remark: disable every indexing service if you – as I – do not use it anyway. I’ve not done dedicated testing, but by normal usage it has been quite painful, so to speak.
Another pro is that my computer isn’t as noisy because of the modest disk usage, i.e. disk I/O.