blog/index.rss

   1 <?xml version="1.0" encoding="utf-8"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
   3         <channel>
   4                 <title>Petter Reinholdtsen</title>
   5                 <description></description>
   6                 <link>http://people.skolelinux.org/pere/blog/</link>
   7                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
   8
   9         <item>
  10                 <title>Økt overvåkning applauderes igjen av Arbeiderpartiet, Høyre og Fremskrittspartiet</title>
  11                 <link>http://people.skolelinux.org/pere/blog/_kt_overv_kning_applauderes_igjen_av_Arbeiderpartiet__H_yre_og_Fremskrittspartiet.html</link>
  12                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/_kt_overv_kning_applauderes_igjen_av_Arbeiderpartiet__H_yre_og_Fremskrittspartiet.html</guid>
  13                 <pubDate>Mon, 4 Feb 2013 00:30:00 +0100</pubDate>
  14                 <description>&lt;p&gt;Jeg ser med gru at Arbeiderpartiet, Høyre og Fremskrittspartiet
  15 &lt;a href=&quot;http://www.aftenposten.no/nyheter/iriks/Positive-til-mer-smuglerovervaking-7110348.html&quot;&gt;applauderer
  16 tollvesenets forslag&lt;/a&gt; om å øke overvåkningen i Norge nok et hakk.
  17 Det er ikke så rart, da de som uttaler seg jo også har støttet
  18 innføringen av datalagringsdirektivet eller i hvert fall ikke veldig
  19 aktivt har motarbeidet det.  Innføringen av datalagringsdirektivet er
  20 en lovendring som innebærer brev og besøkskontroll for hele
  21 befolkningen.&lt;/p&gt;
  22
  23 &lt;p&gt;&lt;a href=&quot;http://www.stortinget.no/no/Saker-og-publikasjoner/Saker/Sak/?p=48717&quot;&gt;Datalagringsdirektivet&lt;/a&gt;
  24 har vært oppe til votering i stortinget tre ganger så langt.  Det ble
  25 &lt;a href=&quot;http://svartelisten.org/&quot;&gt;vedtatt første gang 2011-04-04&lt;/a&gt;
  26 og
  27 &lt;a href=&quot;https://github.com/holderdeord/hdo-folketingparser/blob/master/data/votering-2011-04-11.xml&quot;&gt;andre
  28 gang 2011-04-11&lt;/a&gt; (lovendringer voteres to ganger), og forslag om å
  29 stoppe loven ble
  30 &lt;a href=&quot;http://www.stortinget.no/no/Saker-og-publikasjoner/Saker/Sak/Voteringsoversikt/?p=53844&amp;dnid=1&quot;&gt;nedstemt
  31 2012-12-06&lt;/a&gt; (se også
  32 &lt;a href=&quot;http://beta.holderdeord.no/votes/2715&quot;&gt;oversikt fra Holder De
  33 Ord&lt;/a&gt;).&lt;/p&gt;
  34
  35 &lt;p&gt;Jan Bøhler i Arbeiderpartiet stemte for å innføre
  36 datalagringsdirektivet i lovverket i første votering, var ikke
  37 tilstede i andre votering og støttet loven i tredje votering.  André
  38 Oktay Dahl i Høyre var ikke til stede i første og andre votering men
  39 støttet loven i tredje votering.  Ulf Leirstein i Fremskrittspartiet
  40 stemte mot loven i første votering men var ikke til stede i andre og
  41 tredje votering.&lt;/p&gt;
  42
  43 &lt;p&gt;Hvis du lurer på hva som er problemet med datalagringsdirektivet,
  44 anbefaler jeg å lese &lt;a href=&quot;http://www.uhuru.biz/?cat=84&quot;&gt;artiklene
  45 fra Jon Wessel-Aas&lt;/a&gt; om temaet, samt informasjon fra foreningen
  46 &lt;a href=&quot;http://www.digitaltpersonvern.no/&quot;&gt;Digitalt
  47 Personvern&lt;/a&gt;.&lt;/p&gt;
  48 </description>
  49         </item>
  50
  51         <item>
  52                 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
  53                 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
  54                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
  55                 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
  56                 <description>&lt;p&gt;My
  57 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html&quot;&gt;last
  58 bitcoin related blog post&lt;/a&gt; mentioned that the new
  59 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
  60 Debian was waiting in NEW.  It was accepted by the Debian ftp-masters
  61 2013-01-19, and have been available in unstable since then.  It was
  62 automatically copied to Ubuntu, and is available in their Raring
  63 version too.&lt;/p&gt;
  64
  65 &lt;p&gt;But there is a strange problem with the build that block this new
  66 version from being available on the i386 and kfreebsd-i386
  67 architectures.  For some strange reason, the autobuilders in Debian
  68 for these architectures fail to run the test suite on these
  69 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
  70 We are so far unable to reproduce it when building it manually, and
  71 no-one have been able to propose a fix.  If you got an idea what is
  72 failing, please let us know via the BTS.&lt;/p&gt;
  73
  74 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
  75 I often run low on disk space, is the fact that the client will exit
  76 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
  77 #696715&lt;/a&gt;).  So make sure you have enough disk space when you run
  78 it. :)&lt;/p&gt;
  79
  80 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
  81 activities, please send Bitcoin donations to my address
  82 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
  83 </description>
  84         </item>
  85
  86         <item>
  87                 <title>Welcome to the world, Isenkram!</title>
  88                 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
  89                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
  90                 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
  91                 <description>&lt;p&gt;Yesterday, I
  92 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
  93 for testers&lt;/a&gt; for my prototype for making Debian better at handling
  94 pluggable hardware devices, which I
  95 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
  96 out to create&lt;/a&gt; earlier this month.  Several valuable testers showed
  97 up, and caused me to really want to to open up the development to more
  98 people.  But before I did this, I want to come up with a sensible name
  99 for this project.  Today I finally decided on a new name, and I have
 100 renamed the project from hw-support-handler to this new name.  In the
 101 process, I moved the source to git and made it available as a
 102 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
 103 repository in Debian.  The new name?  It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
 104 To fetch and build the latest version of the source, use&lt;/p&gt;
 105
 106 &lt;pre&gt;
 107 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
 108 cd isenkram &amp;&amp; git-buildpackage -us -uc
 109 &lt;/pre&gt;
 110
 111 &lt;p&gt;I have not yet adjusted all files to use the new name yet.  If you
 112 want to hack on the source or improve the package, please go ahead.
 113 But please talk to me first on IRC or via email before you do major
 114 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
 115
 116 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
 117 stuff, typically meaning tools, nails, screws, etc.  Typical hardware
 118 stuff, in other words.  I&#39;ve been told it is the Norwegian variant of
 119 the German word eisenkram, for those that are familiar with that
 120 word.&lt;/p&gt;
 121
 122 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
 123 instructions, to avoid confusing people with an error from the signing
 124 process.&lt;/p&gt;
 125
 126 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
 127 clone argument to avoid the need for authentication.&lt;/p&gt;
 128 </description>
 129         </item>
 130
 131         <item>
 132                 <title>First prototype ready making hardware easier to use in Debian</title>
 133                 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
 134                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
 135                 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
 136                 <description>&lt;p&gt;Early this month I set out to try to
 137 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
 138 the Debian support for pluggable hardware devices&lt;/a&gt;.  Now my
 139 prototype is working, and it is ready for a larger audience.  To test
 140 it, fetch the
 141 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
 142 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
 143 package.  You might have to log out and in again activate the
 144 autostart script.&lt;/p&gt;
 145
 146 &lt;p&gt;The design is simple:&lt;/p&gt;
 147
 148 &lt;ul&gt;
 149
 150 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
 151 hw-support-handlerd to start when the user log in.&lt;/li&gt;
 152
 153 &lt;li&gt;This program listen for kernel events about new hardware (directly
 154 from the kernel like udev does), not using HAL dbus events as I
 155 initially did.&lt;/li&gt;
 156
 157 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
 158 the APT database, a database
 159 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
 160 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
 161
 162 &lt;li&gt;If a package is mapped to the hardware in question, the package
 163 isn&#39;t installed yet and this is the first time the hardware was
 164 plugged in, show a desktop notification suggesting to install the
 165 package or packages.&lt;/li&gt;
 166
 167 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
 168 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
 169
 170 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
 171 package while showing progress information in a window.&lt;/li&gt;
 172
 173 &lt;/ul&gt;
 174
 175 &lt;p&gt;I still need to come up with a better name for the system.  Here
 176 are some screen shots showing the prototype in action.  First the
 177 notification, then the password request, and finally the request to
 178 approve all the dependencies.  Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
 179
 180 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
 181 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
 182 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
 183 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
 184 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-5-installing-details.png&quot; width=&quot;70%&quot;&gt;&lt;/p&gt;
 185
 186 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
 187 is already useful.  The database of hardware to package mappings also
 188 need more work.  It is currently compatible with the Ubuntu way of
 189 storing such information in the package control file, but could be
 190 changed to use other formats instead or in addition to the current
 191 method.  I&#39;ve dropped the use of discover for this mapping, as the
 192 modalias approach is more flexible and easier to use on Linux as long
 193 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
 194
 195 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
 196 here is the command required to check out and build the source: Use
 197 &#39;&lt;tt&gt;svn checkout
 198 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
 199 hw-support-handler; debuild&lt;/tt&gt;&#39;.  If you lack debuild, install the
 200 devscripts package.&lt;/p&gt;
 201
 202 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
 203 renamed to Isenkram and the source moved from the Debian Edu
 204 subversion repository to a Debian collab-maint git repository.  See
 205 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
 206 instructions&lt;/a&gt; for details.&lt;/p&gt;
 207 </description>
 208         </item>
 209
 210         <item>
 211                 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
 212                 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
 213                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
 214                 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
 215                 <description>&lt;p&gt;This Christmas my trusty old laptop died.  It died quietly and
 216 suddenly in bed.  With a quiet whimper, it went completely quiet and
 217 black.  The power button was no longer able to turn it on.  It was a
 218 IBM Thinkpad X41, and the best laptop I ever had.  Better than both
 219 Thinkpads X30, X31, X40, X60, X61 and X61S.  Far better than the
 220 Compaq I had before that.  Now I need to find a replacement.  To keep
 221 going during Christmas, I moved the one year old SSD disk to my old
 222 X40 where it fitted (only one I had left that could use it), but it is
 223 not a durable solution.
 224
 225 &lt;p&gt;My laptop needs are fairly modest.  This is my wishlist from when I
 226 got a new one more than 10 years ago.  It still holds true.:)&lt;/p&gt;
 227
 228 &lt;ul&gt;
 229
 230 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
 231   than A4).&lt;/li&gt;
 232 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
 233 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
 234 &lt;li&gt;Long battery life time.  Preferable a week.&lt;/li&gt;
 235 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
 236 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
 237 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
 238 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
 239 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
 240 size).&lt;/li&gt;
 241 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
 242   X.org packages.&lt;/li&gt;
 243 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
 244   the time).
 245
 246 &lt;/ul&gt;
 247
 248 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
 249 list.  The reason is simply that the specifications on laptops the
 250 last 10-15 years have been sufficient for my needs, and I have to look
 251 at other features to choose my laptop.  But are there still made as
 252 robust laptops as my X41?  The Thinkpad X60/X61 proved to be less
 253 robust, and Thinkpads seem to be heading in the wrong direction since
 254 Lenovo took over.  But I&#39;ve been told that X220 and X1 Carbon might
 255 still be useful.&lt;/p&gt;
 256
 257 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
 258 external keyboard?  I&#39;ll have to check the
 259 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
 260 well-supported laptops, or perhaps just buy one preinstalled from one
 261 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
 262 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
 263 </description>
 264         </item>
 265
 266         <item>
 267                 <title>How to find a browser plugin supporting a given MIME type</title>
 268                 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
 269                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
 270                 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
 271                 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
 272 install to get support for a given MIME type.  Thanks to
 273 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
 274 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
 275 Unfortunately, not very many packages provide the needed meta
 276 information, Anyway, here is a small script to look up all browser
 277 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
 278
 279 &lt;pre&gt;
 280 #!/usr/bin/python
 281 import sys
 282 import apt
 283 def pkgs_handling_mimetype(mimetype):
 284     cache = apt.Cache()
 285     cache.open(None)
 286     thepkgs = []
 287     for pkg in cache:
 288         version = pkg.candidate
 289         if version is None:
 290             version = pkg.installed
 291         if version is None:
 292             continue
 293         record = version.record
 294         if not record.has_key(&#39;Npp-MimeType&#39;):
 295             continue
 296         mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
 297         for t in mime_types:
 298             t = t.rstrip().strip()
 299             if t == mimetype:
 300                 thepkgs.append(pkg.name)
 301     return thepkgs
 302 mimetype = &quot;audio/ogg&quot;
 303 if 1 &lt; len(sys.argv):
 304     mimetype = sys.argv[1]
 305 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
 306 for pkg in pkgs_handling_mimetype(mimetype):
 307     print &quot;  %s&quot; %pkg
 308 &lt;/pre&gt;
 309
 310 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
 311
 312 &lt;pre&gt;
 313 % ./apt-find-browserplug-for-mimetype
 314 Browser plugin packages supporting audio/ogg:
 315   gecko-mediaplayer
 316 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
 317 Browser plugin packages supporting application/x-shockwave-flash:
 318   browser-plugin-gnash
 319 %
 320 &lt;/pre&gt;
 321
 322 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
 323 itself to query for plugins and propose to install the needed
 324 packages.  It would be great if Debian supported such feature too.  Is
 325 anyone working on adding it?&lt;/p&gt;
 326
 327 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
 328 request for icweasel support for this feature is
 329 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
 330 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today).  Lack
 331 of manpower and wish for a different design is the reason thus feature
 332 is not yet in iceweasel from Debian.&lt;/p&gt;
 333 </description>
 334         </item>
 335
 336         <item>
 337                 <title>What is the most supported MIME type in Debian?</title>
 338                 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
 339                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
 340                 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
 341                 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
 342 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
 343 proposal to make it possible for a Desktop application to propose to
 344 the user some package to install to gain support for a given MIME
 345 type, font, library etc. that is currently missing.  With such
 346 mechanism in place, it would be possible for the desktop to
 347 automatically propose and install leocad if some LDraw file is
 348 downloaded by the browser.&lt;/p&gt;
 349
 350 &lt;p&gt;To get some idea about the current content of the archive, I decided
 351 to write a simple program to extract all .desktop files from the
 352 Debian archive and look up the claimed MIME support there.  The result
 353 can be found on the
 354 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
 355 site&lt;/a&gt;.  Using the collected information, it become possible to
 356 answer the question in the title.  Here are the 20 most supported MIME
 357 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
 358 The complete list is available from the link above.&lt;/p&gt;
 359
 360 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
 361
 362 &lt;pre&gt;
 363   count MIME type
 364   ----- -----------------------
 365      32 text/plain
 366      30 audio/mpeg
 367      29 image/png
 368      28 image/jpeg
 369      27 application/ogg
 370      26 audio/x-mp3
 371      25 image/tiff
 372      25 image/gif
 373      22 image/bmp
 374      22 audio/x-wav
 375      20 audio/x-flac
 376      19 audio/x-mpegurl
 377      18 video/x-ms-asf
 378      18 audio/x-musepack
 379      18 audio/x-mpeg
 380      18 application/x-ogg
 381      17 video/mpeg
 382      17 audio/x-scpls
 383      17 audio/ogg
 384      16 video/x-ms-wmv
 385 &lt;/pre&gt;
 386
 387 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
 388
 389 &lt;pre&gt;
 390   count MIME type
 391   ----- -----------------------
 392      33 text/plain
 393      32 image/png
 394      32 image/jpeg
 395      29 audio/mpeg
 396      27 image/gif
 397      26 image/tiff
 398      26 application/ogg
 399      25 audio/x-mp3
 400      22 image/bmp
 401      21 audio/x-wav
 402      19 audio/x-mpegurl
 403      19 audio/x-mpeg
 404      18 video/mpeg
 405      18 audio/x-scpls
 406      18 audio/x-flac
 407      18 application/x-ogg
 408      17 video/x-ms-asf
 409      17 text/html
 410      17 audio/x-musepack
 411      16 image/x-xbitmap
 412 &lt;/pre&gt;
 413
 414 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
 415
 416 &lt;pre&gt;
 417   count MIME type
 418   ----- -----------------------
 419      31 text/plain
 420      31 image/png
 421      31 image/jpeg
 422      29 audio/mpeg
 423      28 application/ogg
 424      27 image/gif
 425      26 image/tiff
 426      26 audio/x-mp3
 427      23 audio/x-wav
 428      22 image/bmp
 429      21 audio/x-flac
 430      20 audio/x-mpegurl
 431      19 audio/x-mpeg
 432      18 video/x-ms-asf
 433      18 video/mpeg
 434      18 audio/x-scpls
 435      18 application/x-ogg
 436      17 audio/x-musepack
 437      16 video/x-ms-wmv
 438      16 video/x-msvideo
 439 &lt;/pre&gt;
 440
 441 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
 442 information mentioned in DEP-11.  I have not yet had time to look at
 443 it, but hope the PackageKit people in Debian are on top of these
 444 issues.&lt;/p&gt;
 445
 446 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
 447 discovering a typo in my script.&lt;/p&gt;
 448 </description>
 449         </item>
 450
 451         <item>
 452                 <title>Using modalias info to find packages handling my hardware</title>
 453                 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
 454                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
 455                 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
 456                 <description>&lt;p&gt;Yesterday, I wrote about the
 457 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
 458 values provided by the Linux kernel&lt;/a&gt; following my hope for
 459 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
 460 dongle support in Debian&lt;/a&gt;.  Using this knowledge, I have tested how
 461 modalias values attached to package names can be used to map packages
 462 to hardware.  This allow the system to look up and suggest relevant
 463 packages when I plug in some new hardware into my machine, and replace
 464 discover and discover-data as the database used to map hardware to
 465 packages.&lt;/p&gt;
 466
 467 &lt;p&gt;I create a modaliases file with entries like the following,
 468 containing package name, kernel module name (if relevant, otherwise
 469 the package name) and globs matching the relevant hardware
 470 modalias.&lt;/p&gt;
 471
 472 &lt;p&gt;&lt;blockquote&gt;
 473 Package: package-name
 474 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
 475 &lt;/blockquote&gt;&lt;/p&gt;
 476
 477 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
 478 for a given modalias value using this file.&lt;/p&gt;
 479
 480 &lt;p&gt;An entry like this would suggest the video and picture application
 481 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
 482
 483 &lt;p&gt;&lt;blockquote&gt;
 484 Package: cheese
 485 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
 486 &lt;/blockquote&gt;&lt;/p&gt;
 487
 488 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
 489 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
 490
 491 &lt;p&gt;&lt;blockquote&gt;
 492 Package: pcmciautils
 493 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
 494 &lt;/blockquote&gt;&lt;/p&gt;
 495
 496 &lt;p&gt;An entry like this would suggest the package colorhug-client when
 497 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
 498
 499 &lt;p&gt;&lt;blockquote&gt;
 500 Package: colorhug-client
 501 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
 502 &lt;/blockquote&gt;&lt;/p&gt;
 503
 504 &lt;p&gt;I believe the format is compatible with the format of the Packages
 505 file in the Debian archive.  Ubuntu already uses their Packages file
 506 to store their mappings from packages to hardware.&lt;/p&gt;
 507
 508 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
 509 announce the hardware it support in a way my prototype understand.
 510 This allow those publishing packages in an APT source outside the
 511 Debian archive as well as those backporting packages to make sure the
 512 hardware mapping are included in the package meta information.  I&#39;ve
 513 tested such header in the pymissile package, and its modalias mapping
 514 is working as it should with my prototype.  It even made it to Ubuntu
 515 Raring.&lt;/p&gt;
 516
 517 &lt;p&gt;To test if it was possible to look up supported hardware using only
 518 the shell tools available in the Debian installer, I wrote a shell
 519 implementation of the lookup code.  The idea is to create files for
 520 each modalias and let the shell do the matching.  Please check out and
 521 try the
 522 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co&quot;&gt;hw-support-lookup&lt;/a&gt;
 523 shell script.  It run without any extra dependencies and fetch the
 524 hardware mappings from the Debian archive and the subversion
 525 repository where I currently work on my prototype.&lt;/p&gt;
 526
 527 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
 528 install yubikey-personalization:&lt;/p&gt;
 529
 530 &lt;p&gt;&lt;blockquote&gt;
 531 % ./hw-support-lookup
 532 &lt;br&gt;yubikey-personalization
 533 &lt;br&gt;%
 534 &lt;/blockquote&gt;&lt;/p&gt;
 535
 536 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
 537 propose to install the pcmciautils package:&lt;/p&gt;
 538
 539 &lt;p&gt;&lt;blockquote&gt;
 540 % ./hw-support-lookup
 541 &lt;br&gt;pcmciautils
 542 &lt;br&gt;%
 543 &lt;/blockquote&gt;&lt;/p&gt;
 544
 545 &lt;p&gt;If you know of any hardware-package mapping that should be added to
 546 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
 547 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
 548
 549 &lt;p&gt;It could be possible to generate several of the mappings between
 550 packages and hardware.  One source would be to look at packages with
 551 kernel modules, ie packages with *.ko files in /lib/modules/, and
 552 extract their modalias information.  Another would be to look at
 553 packages with udev rules, ie packages with files in
 554 /lib/udev/rules.d/, and extract their vendor/model information to
 555 generate a modalias matching rule.  I have not tested any of these to
 556 see if it work.&lt;/p&gt;
 557
 558 &lt;p&gt;If you want to help implementing a system to let us propose what
 559 packages to install when new hardware is plugged into a Debian
 560 machine, please send me an email or talk to me on
 561 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
 562 </description>
 563         </item>
 564
 565         <item>
 566                 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
 567                 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
 568                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
 569                 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
 570                 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
 571 information, to find the packages that support a given piece of
 572 hardware, I refreshed my memory regarding modalias values, and decided
 573 to document the details.  Here are my findings so far, also available
 574 in
 575 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
 576 Debian Edu subversion repository&lt;/a&gt;:
 577
 578 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
 579
 580 &lt;p&gt;This document try to explain what the different types of modalias
 581 values stands for.  It is in part based on information from
 582 &amp;lt;URL: &lt;a href=&quot;https://wiki.archlinux.org/index.php/Modalias&quot;&gt;https://wiki.archlinux.org/index.php/Modalias&lt;/a&gt; &amp;gt;,
 583 &amp;lt;URL: &lt;a href=&quot;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&quot;&gt;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&lt;/a&gt; &amp;gt;,
 584 &amp;lt;URL: &lt;a href=&quot;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&quot;&gt;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&lt;/a&gt; &amp;gt; and
 585 &amp;lt;URL: &lt;a href=&quot;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&quot;&gt;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&lt;/a&gt; &amp;gt;.
 586
 587 &lt;p&gt;The modalias entries for a given Linux machine can be found using
 588 this shell script:&lt;/p&gt;
 589
 590 &lt;pre&gt;
 591 find /sys -name modalias -print0 | xargs -0 cat | sort -u
 592 &lt;/pre&gt;
 593
 594 &lt;p&gt;The supported modalias globs for a given kernel module can be found
 595 using modinfo:&lt;/p&gt;
 596
 597 &lt;pre&gt;
 598 % /sbin/modinfo psmouse | grep alias:
 599 alias:          serio:ty05pr*id*ex*
 600 alias:          serio:ty01pr*id*ex*
 601 %
 602 &lt;/pre&gt;
 603
 604 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
 605
 606 &lt;p&gt;A typical PCI entry can look like this.  This is an Intel Host
 607 Bridge memory controller:&lt;/p&gt;
 608
 609 &lt;p&gt;&lt;blockquote&gt;
 610 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
 611 &lt;/blockquote&gt;&lt;/p&gt;
 612
 613 &lt;p&gt;This represent these values:&lt;/p&gt;
 614
 615 &lt;pre&gt;
 616  v   00008086  (vendor)
 617  d   00002770  (device)
 618  sv  00001028  (subvendor)
 619  sd  000001AD  (subdevice)
 620  bc  06        (bus class)
 621  sc  00        (bus subclass)
 622  i   00        (interface)
 623 &lt;/pre&gt;
 624
 625 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
 626 -n&#39; as 8086:2770.  The bus class/subclass is also shown by lspci as
 627 0600.  The 0600 class is a host bridge.  Other useful bus values are
 628 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
 629
 630 &lt;p&gt;Not sure how to figure out the interface value, nor what it
 631 means.&lt;/p&gt;
 632
 633 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
 634
 635 &lt;p&gt;Some typical USB entries can look like this.  This is an internal
 636 USB hub in a laptop:&lt;/p&gt;
 637
 638 &lt;p&gt;&lt;blockquote&gt;
 639 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
 640 &lt;/blockquote&gt;&lt;/p&gt;
 641
 642 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
 643
 644 &lt;pre&gt;
 645  v    1D6B  (device vendor)
 646  p    0001  (device product)
 647  d    0206  (bcddevice)
 648  dc     09  (device class)
 649  dsc    00  (device subclass)
 650  dp     00  (device protocol)
 651  ic     09  (interface class)
 652  isc    00  (interface subclass)
 653  ip     00  (interface protocol)
 654 &lt;/pre&gt;
 655
 656 &lt;p&gt;The 0900 device class/subclass means hub.  Some times the relevant
 657 class is in the interface class section.  For a simple USB web camera,
 658 these alias entries show up:&lt;/p&gt;
 659
 660 &lt;p&gt;&lt;blockquote&gt;
 661 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
 662 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
 663 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
 664 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
 665 &lt;/blockquote&gt;&lt;/p&gt;
 666
 667 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
 668 camera), 0101 is audio control device and 0102 is audio streaming (aka
 669 microphone).  Thus this is a camera with microphone included.&lt;/p&gt;
 670
 671 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
 672
 673 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff.  This is an IR
 674 receiver in a Thinkpad X40:&lt;/p&gt;
 675
 676 &lt;p&gt;&lt;blockquote&gt;
 677 acpi:IBM0071:PNP0511:
 678 &lt;/blockquote&gt;&lt;/p&gt;
 679
 680 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
 681
 682 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
 683
 684 &lt;p&gt;The DMI table contain lots of information about the computer case
 685 and model.  This is an entry for a IBM Thinkpad X40, fetched from
 686 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
 687
 688 &lt;p&gt;&lt;blockquote&gt;
 689 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
 690 &lt;/blockquote&gt;&lt;/p&gt;
 691
 692 &lt;p&gt;The values present are&lt;/p&gt;
 693
 694 &lt;pre&gt;
 695  bvn  IBM            (BIOS vendor)
 696  bvr  1UETB6WW(1.66) (BIOS version)
 697  bd   06/15/2005     (BIOS date)
 698  svn  IBM            (system vendor)
 699  pn   2371H4G        (product name)
 700  pvr  ThinkPadX40    (product version)
 701  rvn  IBM            (board vendor)
 702  rn   2371H4G        (board name)
 703  rvr  NotAvailable   (board version)
 704  cvn  IBM            (chassis vendor)
 705  ct   10             (chassis type)
 706  cvr  NotAvailable   (chassis version)
 707 &lt;/pre&gt;
 708
 709 &lt;p&gt;The chassis type 10 is Notebook.  Other interesting values can be
 710 found in the dmidecode source:&lt;/p&gt;
 711
 712 &lt;pre&gt;
 713   3 Desktop
 714   4 Low Profile Desktop
 715   5 Pizza Box
 716   6 Mini Tower
 717   7 Tower
 718   8 Portable
 719   9 Laptop
 720  10 Notebook
 721  11 Hand Held
 722  12 Docking Station
 723  13 All In One
 724  14 Sub Notebook
 725  15 Space-saving
 726  16 Lunch Box
 727  17 Main Server Chassis
 728  18 Expansion Chassis
 729  19 Sub Chassis
 730  20 Bus Expansion Chassis
 731  21 Peripheral Chassis
 732  22 RAID Chassis
 733  23 Rack Mount Chassis
 734  24 Sealed-case PC
 735  25 Multi-system
 736  26 CompactPCI
 737  27 AdvancedTCA
 738  28 Blade
 739  29 Blade Enclosing
 740 &lt;/pre&gt;
 741
 742 &lt;p&gt;The chassis type values are not always accurately set in the DMI
 743 table.  For example my home server is a tower, but the DMI modalias
 744 claim it is a desktop.&lt;/p&gt;
 745
 746 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
 747
 748 &lt;p&gt;This type is used for PS/2 mouse plugs.  One example is from my
 749 test machine:&lt;/p&gt;
 750
 751 &lt;p&gt;&lt;blockquote&gt;
 752 serio:ty01pr00id00ex00
 753 &lt;/blockquote&gt;&lt;/p&gt;
 754
 755 &lt;p&gt;The values present are&lt;/p&gt;
 756
 757 &lt;pre&gt;
 758   ty  01  (type)
 759   pr  00  (prototype)
 760   id  00  (id)
 761   ex  00  (extra)
 762 &lt;/pre&gt;
 763
 764 &lt;p&gt;This type is supported by the psmouse driver.  I am not sure what
 765 the valid values are.&lt;/p&gt;
 766
 767 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
 768
 769 &lt;p&gt;There are heaps of other modalias subtypes according to
 770 file2alias.c.  There is the rest of the list from that source: amba,
 771 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
 772 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
 773 vmbus, x86cpu and zorro.  I did not spend time documenting all of
 774 these, as they do not seem relevant for my intended use with mapping
 775 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
 776
 777 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
 778
 779 &lt;p&gt;To check which kernel modules provide support for a given modalias,
 780 one can use the following shell script:&lt;/p&gt;
 781
 782 &lt;pre&gt;
 783   for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
 784     echo &quot;$id&quot; ; \
 785     /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/  /&#39; ; \
 786   done
 787 &lt;/pre&gt;
 788
 789 &lt;p&gt;The output can look like this (only the first few entries as the
 790 list is very long on my test machine):&lt;/p&gt;
 791
 792 &lt;pre&gt;
 793   acpi:ACPI0003:
 794     insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
 795   acpi:device:
 796   FATAL: Module acpi:device: not found.
 797   acpi:IBM0068:
 798     insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
 799     insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
 800     insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
 801     insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
 802   acpi:IBM0071:PNP0511:
 803     insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
 804     insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
 805     insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
 806   [...]
 807 &lt;/pre&gt;
 808
 809 &lt;p&gt;If you want to help implementing a system to let us propose what
 810 packages to install when new hardware is plugged into a Debian
 811 machine, please send me an email or talk to me on
 812 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
 813
 814 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
 815 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
 816 in /sys/ with space in them.&lt;/p&gt;
 817 </description>
 818         </item>
 819
 820         <item>
 821                 <title>Moved the pymissile Debian packaging to collab-maint</title>
 822                 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
 823                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
 824                 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
 825                 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
 826 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
 827 Launcher and updated the Debian package
 828 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
 829 sure udev will fix the device permissions when it is plugged in.  I
 830 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
 831 hopefully make the package be proposed by jockey in Ubuntu when a user
 832 plug in his rocket launcher.  In the process I moved the source to a
 833 git repository under collab-maint, to make it easier for any DD to
 834 contribute.  &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
 835 is not very active, but the software still work for me even after five
 836 years of relative silence.  The new git repository is not listed in
 837 the uploaded package yet, because I want to test the other changes a
 838 bit more before I upload the new version.  If you want to check out
 839 the new version with a .desktop file included, visit the
 840 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
 841 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
 842 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
 843 </description>
 844         </item>
 845
 846         </channel>
 847 </rss>