






Last week-end, I was in Prague for FOSSCAMP, a Canonical-sponsor event aiming at bringing together people from various Free Software projects. Such an event is a very good idea, especially after the openssl debacle, where we saw how difficult it is to build good relationships with other Free Software projects.
The event was organized in a rather interesting way: the attendees make up the schedule as the event happens, by adding sessions to the timetable using marker pens on a whiteboard (see picture, hi Jorge!). If we have a spare BOF room at Debconf, it would be great to do the same thing: I always find it frustrating that many important discussions at Debconf happen outside BOFs/lectures, and are so easy to miss, simply because you submit talk proposals months before Debconf, so you can’t know yet what will be the hot stuff when Debconf finally arrives :-)
It was also interesting to see all the different ways people organized BOFs. It might be interesting to write a list of DOes and DON’T about BOFs (not that the sessions weren’t of good quality!). Does anyone know if such a list already exist?
And finally, as usual, it was great to meet all those people from this nice community again. If you still believe that some projects are fighting with each other, you need to attend such an event. And special thanks go to Ond ej ert k for guiding me through a visit of Prague!
deb http://ppa.launchpad.net/juliank/ubuntu hardy mainPlease note that these packages are experimental and are only for experienced users.


foosel tagged me, whatever that means. Perhaps it’s the English
word for “Stöckchen” (German for “small stick”) of which I always
wondered how the English blogging part of the blogosphere is calling
that kind of coercing blog posts… ;-)
So these are the rules:
Last week I noticed, that Kabel Deutschland, a cable provider in germany, returns for any non existing hosts “204.9.89.60″. It seems, thats it is rolled out since last fall. Even for DNSSEC enabled infrastructure it breaks it totally:
; <<>> DiG 9.3.4 <<>> +dnssec web.pixaco.se @83.169.184.161
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; ANSWER SECTION:
web.pixaco.se. 0 IN A 204.9.89.60
Beside that, this behavour breaks the whole DNS, since many mechanism rely on a negative answer. The most visible effect for the users is, that when having a typo on surfing, he will forwarded to http://suche.kabeldeutschland.de/de.kde.assist/?domain=<domainyoutypedinyourprompt>. Since 204.9.88.0/21 is located at our transatlantic friends from US, there might be some problem with leaking privacy informations. I don’t feel happy, if I had a typo in my URL and getting listed for it on any terror list or providing the newest porno links to my american friends inside the organisations with the tree capitals.
All that for getting some extra money, but racing pricedumping for connectivity, this sucks a lot.
If you are a customer and feel pissed, you can send a friendly note to them:
Kabel Deutschland Vertrieb und Service GmbH & Co. KGA quick and dirty workaround for dnsmasq maybe to add “bogus-nxdomain=204.9.89.60″ to your config file. This doesn’t fix the DNSSEC problem.
Beschwerdestelle
99116 Erfurt
kundenservice@kabeldeutschland.de
Fax: 01805299925
Back from my travels, it's time for a few updates. I've mostly blogged about these elsewhere, so I'll just give some pointers here.
The launch of magnetic-stripe cards at Where 2.0 went well.
We had some initial teething issues with Linux talking to the card printers, which was resolved by backing down to Linux kernel 2.6.22 from 2.6.24. I'm not entirely sure what's up with 2.6.24, but it exhibited strange behavior talking to the card printers over ethernet — as if there were MTU misconfigurations. It's a big nuisance, as 2.6.24 is the default kernel shipped with Ubuntu Hardy, an otherwise excellent release.
I've been paying some attention to OpenID 2.0 recently, as it's time for me to upgrade my OpenID accepting websites to use the new release of the specification — if for no other reason than Yahoo! OpenIDs are 2.0-only.
This investigation led me to notice XRIs again, which are the confusing underbelly of the OpenID specs. The W3C Technical Architecture Group recently advised against using XRIs. I wrote about this over on my XML.com blog.
I've not used for that blog for a long time, but will try to do so more. I've realized that I've still got a lot to say about the web, XML and open standards, and the XML.com blog seems like a good place to say it.
Finally, to brag for a short moment. Another XTech has been and gone, and this year's was a great experience for everybody involved. This quote from attendee Paul Smith summed things up nicely, as it tells me I succeeded in my main goal for the conference:
What I really liked about this conference was the mix of attendees and presenters, both from academia, and the commercial world both and small. It made it feel much more valid, and it really felt like everyone was there for the right reasons - not trying to sell anything, but out of a genuinely altruistic wish to make the web better.My sincere thanks to everybody involved in XTech this year.
Three quick updates to items I've posted in
the past:-
Justin Rolfe has re-opened
his fishmonger's shop on Alexandra Parade Weston-super-Mare
less than six weeks after what
Avon Fire called a "lucky escape"
when his van crashed off Kewstoke toll road.
I'm glad I didn't try to go to an event in
Exeter yesterday
that I was invited to. I don't
remember seeing that restaurant, but
the BBC writes it only opened last September.
A religious bombing in Devon.
Whatever next?
Eurovision
is tomorrow night. I'm not going to write in
detail here this year (because I don't want
the pain of dealing with the planet-purgers
again) but I might try to guest blog
somewhere else and mention it at the end
of tomorrow's post.
I got a new Hewlett-Packard LaserJet P3005X. I unpacked the device, connected power and ethernet, went to HP support page and downloaded the firmware upgrade for it.
After carefully reading through the whole readme, I initiated the firmware upload. After successfull flashing cycle, the printer reboots and freezes with this message on the display:
Downld file now SEND RFU UPGRADE...and the printer is dead, just after ten minutes of unpacking it. How comes? HP equips some LaserJet P3005X with a formatter (that is the embedded "computer" inside the printer) that is not upgradeable. Brilliant. And that is why Hewlett-Packard sucks beyond belief:
/usr/lib/partconf/find-partitions and then load the
right preseeding for partman-auto, the automatic
partitioner.
Here you find the
udeb source. I'll comment the most important bits:
First, the two partman-auto recipes that we are
going to preseed. The format
is documented in the debian-installer documentation.
This will create /home if missing:
d-i partman-auto/expert_recipe string \
condpart :: \
2048 2048 2048 ext3 \
$primary $bootable \
method format format \
use_filesystem filesystem ext3 \
mountpoint / \
. \
1024 1024 1024 linux-swap \
method swap format \
. \
1024 4096 10000000 ext3 \
method format format \
use_filesystem filesystem ext3 \
mountpoint /home \
.
/home if it exists:
d-i partman-auto/expert_recipe string \
condpart :: \
2048 2048 2048 ext3 \
$primary $bootable \
method format format \
use_filesystem filesystem ext3 \
mountpoint / \
. \
1024 1024 1024 linux-swap \
method swap format \
. \
1024 4096 10000000 ext3 \
method keep \
use_filesystem filesystem ext3 \
mountpoint /home \
.
postinst file of the package, where the
logic is. Otavio and Daniel on #debian-boot have
taught me that udebs are, simply put, just big postinsts (installer
wise, apart from shipping binaries). Postinst is where the logic is
done, or applications are started.
#!/bin/sh # Copyright 2008 Enrico Zini <enrico@truelite.it> # Licensed under the terms of the GNU General Public License, # version 3 or any later version. set -e FINDPARTS="/usr/lib/partconf/find-partitions" notice () logger -t condpart "$@" error () logger -t condpart "error: $@" # load debconf . /usr/share/debconf/confmodule notice "Checking if we need to recreate /home" if [ ! -x $FINDPARTS ] then error "$FINDPARTS not found" exit 1 fi if $FINDPARTS grep -q part6 then # Keep notice "/home exists: we keep it" debconf-set-selections /usr/lib/condpart/part-keep.preseed else # Format notice "/home does not exist: we create it" debconf-set-selections /usr/lib/condpart/part-create.preseed fi notice "Finished special handling of /home" #DEBHELPER# exit 0
debian/control. The basic bits about
creating a d-i udeb are to put it in Section:
debian-installer and to use XC-Package-Type:
udeb. Then there is XB-Installer-Menu-Item,
that defines the order of execution of postinsts. The d-i
documentation
lists the numbers that are currently assigned.
Source: condpart Section: debian-installer Priority: optional Maintainer: Enrico Zini <enrico@debian.org> Build-Depends: debhelper (>= 4.0.0), cdbs Standards-Version: 3.7.2.1 Package: condpart Architecture: any XC-Package-Type: udeb XB-Installer-Menu-Item: 38 Description: Conditional partitioning Tells partman-auto to create /home if it's missing, or if it exists, to keep it.
debian/rules is just boilerplate,
except installing the preseed files in the right place. CDBS is
useful to make this self-evident:
#!/usr/bin/make -f include /usr/share/cdbs/1/rules/debhelper.mk install/condpart:: install -o root -g root -m 0644 *.preseed debian/$(cdbs_curpkg)/usr/lib/condpart/
Next.