<?xml version="1.0"?>
<!-- name="generator" content="pyblosxom/0.8.1" -->
<!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">

<rss version="0.91">
  <channel>
    <title>Tollef Fog Heen</title>
    <link>http://err.no/personal/blog/</link>
    <description>tfheen's blog</description>
    <webMaster>tfheen@err.no</webMaster>
    <managingEditor>tfheen@err.no</managingEditor>
    <language>en</language>
    <image>
        <url>http://err.no/tfheen.jpg</url>
        <title>Tollef Fog Heen</title>
        <description>Image of Tollef Fog Heen</description>
        <link>http://err.no/personal/blog</link>
        <width>66</width>
        <height>100</height>
    </image>
  <item>
    <title>FOSDEM talk: systemd in Debian</title>
    <link>http://err.no/personal/blog/tech/Debian/2013-01-28-16-20_FOSDEM_systemd_in_Debian.html</link>
    <pubDate>Mon, 28 Jan 2013 16:20 +0100</pubDate>
    <description>&lt;p&gt;Michael Biebl and I are giving a talk on &lt;a href=&quot;https://fosdem.org/2013/schedule/event/debian_systemd/&quot;&gt;systemd in Debian&lt;/a&gt; at
FOSDEM on Sunday morning at 10.  We&apos;ll be talking a bit about the
current state in Wheezy, what our plans for Jessie are and what Debian
packagers should be aware of.  We would love to get input from people
about what systemd in Jessie should look like, so if you have any
ideas, opinions or insights, please come along.  If you&apos;re just
curious, you are also of course welcome to join.&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Upgrading Alioth</title>
    <link>http://err.no/personal/blog/tech/Debian/2011-05-21-11-14_alioth_upgrade.html</link>
    <pubDate>Sat, 21 May 2011 11:14 +0100</pubDate>
    <description>&lt;p&gt;A while ago, we got another machine for hosting Alioth and so we
started thinking about how to use that machine.  It&apos;s a used machine
and not massively faster than the current hardware, so just moving
everything over wouldn&apos;t actually get us that much of a performance
upgrade.&lt;/p&gt;

&lt;p&gt;However, Alioth is using FusionForge, which is supposed to be able to
run on a cluster of machines.  After all, this was originally built
for SourceForge.net, which certainly does not run on a single host.
So, a split of services is what we&apos;ll do.&lt;/p&gt;

&lt;p&gt;This weekend, we&apos;re having a sprint in &lt;a href=&quot;http://www.collabora.com/&quot;&gt;Collabora&apos;s&lt;/a&gt; office in
Cambridge, actually implementing the split and doing a bit of general
planning for the future.&lt;/p&gt;

&lt;p&gt;Last afternoon (Friday), European time, we started the migration.  The
first step is to move all the data off the Xen guest on wagner, where
Alioth is currently hosted.  This finished a few minutes ago; it turns
out syncing about 8.5 million files across almost 400G of data takes a
little while.&lt;/p&gt;

&lt;p&gt;The new host is called vasks and will host the database, run the main
apache and be the canonical location for the various SCM
repositories.&lt;/p&gt;

&lt;p&gt;We are not decomissioning wagner, but it&apos;ll be reinstalled without Xen
or other virtualisation which should help performance a bit.  It&apos;ll
host everything that has lower performance requirements such as cron
jobs, mailing lists and so on.&lt;/p&gt;

&lt;p&gt;I&apos;ll try to keep you all updated and feel free to drop by #alioth on
irc.debian.org if you have any questions.&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Package workflow</title>
    <link>http://err.no/personal/blog/tech/Debian/2009-11-05-08-31_package_workflow.html</link>
    <pubDate>Thu, 05 Nov 2009 08:31 +0100</pubDate>
    <description>&lt;p&gt;As 3.0 format packages are now allowed into the archive, I am thinking
about what I would like the workflow to look like and hoping one of
them fits me.&lt;/p&gt;

&lt;p&gt;For new upstream releases, I am imaginging something like:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;New upstream version is released.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;git fetch&lt;/code&gt; + merge into upstream branch.&lt;/li&gt;
&lt;li&gt;Import tarballs, preferably in their original format (bz2/gzip),
using &lt;code&gt;pristine-tar&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Merge upstream to debian branch.  Do necessary fixups and
adjustments.  At this point, the upstream..debian branch delta is
what I want to apply to the upstream release.  The reason I need
to apply this delta is so I get all generated files into the
package that&apos;s built and uploaded.&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The source package has two functions at this point: Be a starting
point for further hacking; and be the source that buildds use to
build the binary Debian packages.&lt;/p&gt;

&lt;p&gt;For the former, I need the git repository itself.  It is
increasingly my preferred form of modification and so I consider
it part of the source.&lt;/p&gt;

&lt;p&gt;For the latter, it might be easiest just to ship the
&lt;code&gt;orig.tar.{gz,bz2}&lt;/code&gt; and the upstream..debian delta.  This does
require the upstream..debian delta not to change any generated
files, which I think is a fair requirement.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I&apos;m not actually sure which source format can give me this.  I think
maybe the &lt;code&gt;3.0 (git)&lt;/code&gt; format can, but I haven&apos;t played around with it
enough to see.  I also don&apos;t know if any tools actually support this
workflow.&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Killing hold periods</title>
    <link>http://err.no/personal/blog/tech/Debian/2007-11-22-09-10_killing_hold_periods.html</link>
    <pubDate>Thu, 22 Nov 2007 09:10 +0100</pubDate>
    <description>&lt;p&gt;&lt;a href=&quot;http://lambdaman.blogspot.com/2007/11/good-ideas-in-customer-service-kill.html&quot;&gt;Daniel Burrows&lt;/a&gt; writes about the feature of some call centres
whereas if all operators are busy, it gives the caller the option of
being called back.  He&apos;d like the nice twist of being able to enter his
phone number on a web page and then be called back so he doesn&apos;t
actually have to call, then wait.&lt;/p&gt;

&lt;p&gt;I&apos;m not sure where Daniel lives, but I&apos;m happy to report that this
practice is quite common here in Norway, so it might well be on its way
to whatever companies are local to Daniel.&lt;/p&gt;

&lt;p&gt;Also, why does bloglines link to the completely wrong place on dburrow&apos;s
posts?  It links to
http://planet.debian.org/tag:blogger.com,1999:blog-$blah rather than
the real URL.&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Infinite monkeys</title>
    <link>http://err.no/personal/blog/tech/Debian/2007-09-17-21-00_infinite_monkeys.html</link>
    <pubDate>Mon, 17 Sep 2007 21:00 +0100</pubDate>
    <description>&lt;p&gt;Just like an infinite number of monkeys, given infinite time are likely
to produce infinite copies of Hamlet, I knew that given an infinite
number of blog postings by Clint, I had to find &lt;a href=&quot;http://xana.scru.org/ranticore/syndicatedincorporated.html&quot;&gt;one&lt;/a&gt; which both made
sense to me and which I agreed with.&lt;/p&gt;

&lt;p&gt;Somebody please write a free syndicate (or syndicate wars) clone.&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Making pancakes</title>
    <link>http://err.no/personal/blog/tech/Debian/2007-07-05-16-43_pancakes.html</link>
    <pubDate>Thu, 05 Jul 2007 16:43 +0100</pubDate>
    <description>&lt;p&gt;Some people on Planet Debian seem to think that using oil for pancakes
is a good idea.  They really taste so much better if you use real butter
(and preferably an iron pan, not a non-stick one).&lt;/p&gt;

&lt;p&gt;Oh, and a nice receipe, which almost matches another one is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;1l milk&lt;/li&gt;
&lt;li&gt;4 eggs&lt;/li&gt;
&lt;li&gt;5dl flour (I use a mix of coarser and finer flour, but you can use
anything you want)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Mix milk and flour, then add eggs last (blends better that way).&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Strength of asymmetric and symmetric encryption algorithms</title>
    <link>http://err.no/personal/blog/tech/Debian/2007-03-15-08-05_strength_of_symmetric_versus_asymmetric_algorithms.html</link>
    <pubDate>Thu, 15 Mar 2007 08:05 +0100</pubDate>
    <description>&lt;p&gt;&lt;a href=&quot;http://www.corsac.net/?rub=blog&amp;amp;post=1327&quot;&gt;Yves-Alexis Perez&lt;/a&gt; writes a bit about Debian and
crypto-containers, comparing cryptsetup and encfs.  The comparison is
decent enough, except that it&apos;s fairly trivial to get cryptsetup to
integrate into the whole gnome-volume-manager stack and have a dialogue
pop up when you insert an encrypted USB stick or similar.  Sure, it&apos;s
mounted by a root process, but I wouldn&apos;t claim it&apos;s any kind of
insecure because of that.&lt;/p&gt;

&lt;p&gt;What did really catch my eye was the line near the end:&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;[...] but this is a bruteforce attack against master password (1024
  bits RSA key), not against 128bits aes key of the container.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Well, according to conventional research, a 1024 bit RSA key is about as
strong as an 80 bit symmetric key. &lt;a href=&quot;http://www.rsa.com/rsalabs/node.asp?id=2004&quot;&gt;A semi-recent RSA paper&lt;/a&gt;
confirms this too.  And to the best of my knowledge, there has not been
found weaknesses in AES which lower the effective key size.&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Hackergotchi for Robot101</title>
    <link>http://err.no/personal/blog/tech/Debian/2006-06-04-21-25_robot101_hackergotchi.html</link>
    <pubDate>Sun, 04 Jun 2006 21:25 +0100</pubDate>
    <description>&lt;p&gt;Since I&apos;m impatient and Robot101 didn&apos;t respond within ten minutes of me
pinging him on IRC, I&apos;m just posting the result of his request for a
hackergotchi.&lt;/p&gt;

&lt;p&gt;&lt;img src=&quot;http://err.no/images/2006-06-04-robot101.jpeg&quot; alt=&quot;Robot101&quot; title=&quot;&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Above is JPEG, but there&apos;s an
&lt;a href=&quot;http://err.no/images/2006-06-04-robot101.xcf&quot;&gt;XCF&lt;/a&gt; available too,
with full transparency goodness, etc.&lt;/p&gt;

&lt;p&gt;Next time, it&apos;d be useful to have a starting image where the head is bit
more than 180x230 pixels since doing cropping and resizes and such
tend to end with the image not being great.&lt;/p&gt;

&lt;p&gt;Also, my space bar is failing and I&apos;ll have to call IBM when I get home.
I&apos;m actually quite disappointed that I seem to have worn out the space
bar in about a year and a half.&lt;/p&gt;
</description>
  </item>
  <item>
    <title>Incrementing Zone serials</title>
    <link>http://err.no/personal/blog/tech/Debian/2006-03-31-17-27_zone_serials.html</link>
    <pubDate>Fri, 31 Mar 2006 17:27 +0100</pubDate>
    <description>&lt;p&gt;&lt;code&gt;-*- zone -*-&lt;/code&gt; in one of the first two lines of the file.&lt;/p&gt;
</description>
  </item>
  <item>
    <title>How to configure XKB to give you a compose button</title>
    <link>http://err.no/personal/blog/tech/Debian/2006-01-23-22-06_compose_using_xkb.html</link>
    <pubDate>Mon, 23 Jan 2006 22:06 +0100</pubDate>
    <description>&lt;p&gt;&lt;a href=&quot;http://ze-dinosaur.livejournal.com/3495.html&quot;&gt;Eric Dorland&lt;/a&gt; wonders how
to enable the Compose key just using XKB.  Personally, I use my caps
lock key for that, and using&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;        Option          &quot;XkbOptions&quot;    &quot;compose:caps&quot;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;in &lt;code&gt;/etc/X11/xorg.conf&lt;/code&gt;, that&apos;s easy enough.&lt;/p&gt;

&lt;p&gt;Other options are &lt;code&gt;compose:ralt&lt;/code&gt;, &lt;code&gt;compose:rwin&lt;/code&gt;, &lt;code&gt;compose:menu&lt;/code&gt; and
&lt;code&gt;compose:rctrl&lt;/code&gt;.&lt;/p&gt;
</description>
  </item>
  </channel>
</rss>
