08:11:43 # Life apache upgrade? From the diffs of the apt-listbugs regression test log, I've noticed that the response from bugs.debian.org is now different. There was an upgrade from Apache 1.3 to 2.0, and it shows in the logs. I haven't yet been able to find too much discrepancy, but I do wonder what apps might break.
HTTP/1.1 302 Found -Date: Mon, 29 Jan 2007 13:36:08 GMT -Server: Apache/1.3.33 (Debian GNU/Linux) +Date: Mon, 26 Feb 2007 23:07:17 GMT +Server: Apache/2.0.54 (Debian GNU/Linux) mod_python/3.1.3 Python/2.3.5 Location: http://bugs.donarmstrong.com/cgi-bin/soap.cgi -Transfer-Encoding: chunked +Content-Length: 229 Content-Type: text/html; charset=iso-8859-1
09:45:33 # Life Tokyo area debian meeting. 25th meeting was held yesterday. We did a session to compare and contrast dbs, quilt, and dpatch. Kobayashi was ill, and quilt session lacked a presentor. dbs session was presented by Iwamatsu, and I presented dpatch. quilt looks new but not much different from dpatch, dbs looks a bit old and rusty and less widely used now. The way forward looks more like integrated stg where dpatch-style stuff is more integrated into the SCM.
On a different topic, we planned session for Open Source Conference, which is held in Tokyo in March. Tokyo area Debian meeting and 'Kasouka Tomo no Kai (Friends of virtualization technologies)' will be doing a collaboration event there. Hopefully it will be fun.
09:49:19 # Life Debconf orga team meeting. It was 15 minutes past 7 am, I woke up with the sound of phone ringing. Sorry about being late.
11:12:14 # Life Re: kvm, qemu and qemuctl. I guess you mean something like this: 409573. So that qemuctl works with kvm.
22:24:28 # Life Using kvm and loadvm. There is a feature in kvm, or rather qemu, that enables users to resume from a known state. I was using kvm for a while and got irritated by having to watch Windows booting. By using 'savevm' and 'loadvm' feature, it is possible to skip that step and always start from the point where you can start working. The tip here is to create a COW image from the HDD image that 'savevm' was done, so that you can re-run from the same state how ever many times you want. It feels better to be in a running Windows session within 10 seconds.
[creating the initial state] kvm ... -hda winxp.img in console: stop savevm winxp.state(state file) quit [starting qemu] qemu-img create -b winxp.img winxp.img-work kvm. ... -loadvm winxp.state -hda winxp.img-work
$Id: 200702.html.en,v 1.5 2007/03/03 10:09:23 dancer Exp $