blog/tags/isenkram/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen: Entries Tagged isenkram</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="isenkram.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21     <h3>Entries tagged "isenkram".</h3>
  22
  23     <div class="entry">
  24       <div class="title">
  25         <a href="http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html">Install hardware dependent packages using tasksel (Isenkram 0.7)</a>
  26       </div>
  27       <div class="date">
  28         23rd April 2014
  29       </div>
  30       <div class="body">
  31         <p>It would be nice if it was easier in Debian to get all the hardware
  32 related packages relevant for the computer installed automatically.
  33 So I implemented one, using
  34 <a href="http://packages.qa.debian.org/isenkram">my Isenkram
  35 package</a>.  To use it, install the tasksel and isenkram packages and
  36 run tasksel as user root.  You should be presented with a new option,
  37 "Hardware specific packages (autodetected by isenkram)".  When you
  38 select it, tasksel will install the packages isenkram claim is fit for
  39 the current hardware, hot pluggable or not.<p>
  40
  41 <p>The implementation is in two files, one is the tasksel menu entry
  42 description, and the other is the script used to extract the list of
  43 packages to install.  The first part is in
  44 <tt>/usr/share/tasksel/descs/isenkram.desc</tt> and look like
  45 this:</p>
  46
  47 <p><blockquote><pre>
  48 Task: isenkram
  49 Section: hardware
  50 Description: Hardware specific packages (autodetected by isenkram)
  51  Based on the detected hardware various hardware specific packages are
  52  proposed.
  53 Test-new-install: mark show
  54 Relevance: 8
  55 Packages: for-current-hardware
  56 </pre></blockquote></p>
  57
  58 <p>The second part is in
  59 <tt>/usr/lib/tasksel/packages/for-current-hardware</tt> and look like
  60 this:</p>
  61
  62 <p><blockquote><pre>
  63 #!/bin/sh
  64 #
  65 (
  66     isenkram-lookup
  67     isenkram-autoinstall-firmware -l
  68 ) | sort -u
  69 </pre></blockquote></p>
  70
  71 <p>All in all, a very short and simple implementation making it
  72 trivial to install the hardware dependent package we all may want to
  73 have installed on our machines.  I've not been able to find a way to
  74 get tasksel to tell you exactly which packages it plan to install
  75 before doing the installation.  So if you are curious or careful,
  76 check the output from the isenkram-* command line tools first.</p>
  77
  78 <p>The information about which packages are handling which hardware is
  79 fetched either from the isenkram package itself in
  80 /usr/share/isenkram/, from git.debian.org or from the APT package
  81 database (using the Modaliases header).  The APT package database
  82 parsing have caused a nasty resource leak in the isenkram daemon (bugs
  83 <a href="http://bugs.debian.org/719837">#719837</a> and
  84 <a href="http://bugs.debian.org/730704">#730704</a>).  The cause is in
  85 the python-apt code (bug
  86 <a href="http://bugs.debian.org/745487">#745487</a>), but using a
  87 workaround I was able to get rid of the file descriptor leak and
  88 reduce the memory leak from ~30 MiB per hardware detection down to
  89 around 2 MiB per hardware detection.  It should make the desktop
  90 daemon a lot more useful.  The fix is in version 0.7 uploaded to
  91 unstable today.</p>
  92
  93 <p>I believe the current way of mapping hardware to packages in
  94 Isenkram is is a good draft, but in the future I expect isenkram to
  95 use the AppStream data source for this.  A proposal for getting proper
  96 AppStream support into Debian is floating around as
  97 <a href="https://wiki.debian.org/DEP-11">DEP-11</a>, and
  98 <a href="https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive">GSoC
  99 project</a> will take place this summer to improve the situation.  I
 100 look forward to seeing the result, and welcome patches for isenkram to
 101 start using the information when it is ready.</p>
 102
 103 <p>If you want your package to map to some specific hardware, either
 104 add a "Xb-Modaliases" header to your control file like I did in
 105 <a href="http://packages.qa.debian.org/pymissile">the pymissile
 106 package</a> or submit a bug report with the details to the isenkram
 107 package.  See also
 108 <a href="http://people.skolelinux.org/pere/blog/tags/isenkram/">all my
 109 blog posts tagged isenkram</a> for details on the notation.  I expect
 110 the information will be migrated to AppStream eventually, but for the
 111 moment I got no better place to store it.</p>
 112
 113       </div>
 114       <div class="tags">
 115
 116
 117         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>.
 118
 119
 120       </div>
 121     </div>
 122     <div class="padding"></div>
 123
 124     <div class="entry">
 125       <div class="title">
 126         <a href="http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html">Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</a>
 127       </div>
 128       <div class="date">
 129         25th June 2013
 130       </div>
 131       <div class="body">
 132         <p>It annoys me when the computer fail to do automatically what it is
 133 perfectly capable of, and I have to do it manually to get things
 134 working.  One such task is to find out what firmware packages are
 135 needed to get the hardware on my computer working.  Most often this
 136 affect the wifi card, but some times it even affect the RAID
 137 controller or the ethernet card.  Today I pushed version 0.4 of the
 138 <a href="http://packages.qa.debian.org/isenkram">Isenkram package</a>
 139 including a new script isenkram-autoinstall-firmware handling the
 140 process of asking all the loaded kernel modules what firmware files
 141 they want, find debian packages providing these files and install the
 142 debian packages.  Here is a test run on my laptop:</p>
 143
 144 <p><pre>
 145 # isenkram-autoinstall-firmware
 146 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
 147 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
 148 info: locating packages with the requested firmware files
 149 info: Updating APT sources after adding non-free APT source
 150 info: trying to install firmware-ipw2x00
 151 firmware-ipw2x00
 152 firmware-ipw2x00
 153 Preconfiguring packages ...
 154 Selecting previously deselected package firmware-ipw2x00.
 155 (Reading database ... 259727 files and directories currently installed.)
 156 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
 157 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
 158 #
 159 </pre></p>
 160
 161 <p>When all the requested firmware is present, a simple message is
 162 printed instead:</p>
 163
 164 <p><pre>
 165 # isenkram-autoinstall-firmware
 166 info: did not find any firmware files requested by loaded kernel modules.  exiting
 167 #
 168 </pre></p>
 169
 170 <p>It could use some polish, but it is already working well and saving
 171 me some time when setting up new machines. :)</p>
 172
 173 <p>So, how does it work?  It look at the set of currently loaded
 174 kernel modules, and look up each one of them using modinfo, to find
 175 the firmware files listed in the module meta-information.  Next, it
 176 download the Contents file from a nearby APT mirror, and search for
 177 the firmware files in this file to locate the package with the
 178 requested firmware file.  If the package is in the non-free section, a
 179 non-free APT source is added and the package is installed using
 180 <tt>apt-get install</tt>.  The end result is a slightly better working
 181 machine.</p>
 182
 183 <p>I hope someone find time to implement a more polished version of
 184 this script as part of the hw-detect debian-installer module, to
 185 finally fix <a href="http://bugs.debian.org/655507">BTS report
 186 #655507</a>.  There really is no need to insert USB sticks with
 187 firmware during a PXE install when the packages already are available
 188 from the nearby Debian mirror.</p>
 189
 190       </div>
 191       <div class="tags">
 192
 193
 194         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>.
 195
 196
 197       </div>
 198     </div>
 199     <div class="padding"></div>
 200
 201     <div class="entry">
 202       <div class="title">
 203         <a href="http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html">Isenkram 0.2 finally in the Debian archive</a>
 204       </div>
 205       <div class="date">
 206          3rd April 2013
 207       </div>
 208       <div class="body">
 209         <p>Today the <a href="http://packages.qa.debian.org/isenkram">Isenkram
 210 package</a> finally made it into the archive, after lingering in NEW
 211 for many months.  I uploaded it to the Debian experimental suite
 212 2013-01-27, and today it was accepted into the archive.</p>
 213
 214 <p>Isenkram is a system for suggesting to users what packages to
 215 install to work with a pluggable hardware device.  The suggestion pop
 216 up when the device is plugged in.  For example if a Lego Mindstorm NXT
 217 is inserted, it will suggest to install the program needed to program
 218 the NXT controller.  Give it a go, and report bugs and suggestions to
 219 BTS. :)</p>
 220
 221       </div>
 222       <div class="tags">
 223
 224
 225         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>.
 226
 227
 228       </div>
 229     </div>
 230     <div class="padding"></div>
 231
 232     <div class="entry">
 233       <div class="title">
 234         <a href="http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html">Welcome to the world, Isenkram!</a>
 235       </div>
 236       <div class="date">
 237         22nd January 2013
 238       </div>
 239       <div class="body">
 240         <p>Yesterday, I
 241 <a href="http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html">asked
 242 for testers</a> for my prototype for making Debian better at handling
 243 pluggable hardware devices, which I
 244 <a href="http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html">set
 245 out to create</a> earlier this month.  Several valuable testers showed
 246 up, and caused me to really want to to open up the development to more
 247 people.  But before I did this, I want to come up with a sensible name
 248 for this project.  Today I finally decided on a new name, and I have
 249 renamed the project from hw-support-handler to this new name.  In the
 250 process, I moved the source to git and made it available as a
 251 <a href="http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git">collab-maint</a>
 252 repository in Debian.  The new name?  It is <strong>Isenkram</strong>.
 253 To fetch and build the latest version of the source, use</p>
 254
 255 <pre>
 256 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
 257 cd isenkram && git-buildpackage -us -uc
 258 </pre>
 259
 260 <p>I have not yet adjusted all files to use the new name yet.  If you
 261 want to hack on the source or improve the package, please go ahead.
 262 But please talk to me first on IRC or via email before you do major
 263 changes, to make sure we do not step on each others toes. :)</p>
 264
 265 <p>If you wonder what 'isenkram' is, it is a Norwegian word for iron
 266 stuff, typically meaning tools, nails, screws, etc.  Typical hardware
 267 stuff, in other words.  I've been told it is the Norwegian variant of
 268 the German word eisenkram, for those that are familiar with that
 269 word.</p>
 270
 271 <p><strong>Update 2013-01-26</strong>: Added -us -us to build
 272 instructions, to avoid confusing people with an error from the signing
 273 process.</p>
 274
 275 <p><strong>Update 2013-01-27</strong>: Switch to HTTP URL for the git
 276 clone argument to avoid the need for authentication.</p>
 277
 278       </div>
 279       <div class="tags">
 280
 281
 282         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>.
 283
 284
 285       </div>
 286     </div>
 287     <div class="padding"></div>
 288
 289     <div class="entry">
 290       <div class="title">
 291         <a href="http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html">First prototype ready making hardware easier to use in Debian</a>
 292       </div>
 293       <div class="date">
 294         21st January 2013
 295       </div>
 296       <div class="body">
 297         <p>Early this month I set out to try to
 298 <a href="http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html">improve
 299 the Debian support for pluggable hardware devices</a>.  Now my
 300 prototype is working, and it is ready for a larger audience.  To test
 301 it, fetch the
 302 <a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/">source
 303 from the Debian Edu subversion repository</a>, build and install the
 304 package.  You might have to log out and in again activate the
 305 autostart script.</p>
 306
 307 <p>The design is simple:</p>
 308
 309 <ul>
 310
 311 <li>Add desktop entry in /usr/share/autostart/ causing a program
 312 hw-support-handlerd to start when the user log in.</li>
 313
 314 <li>This program listen for kernel events about new hardware (directly
 315 from the kernel like udev does), not using HAL dbus events as I
 316 initially did.</li>
 317
 318 <li>When new hardware is inserted, look up the hardware modalias in
 319 the APT database, a database
 320 <a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup">available
 321 via HTTP</a> and a database available as part of the package.</li>
 322
 323 <li>If a package is mapped to the hardware in question, the package
 324 isn't installed yet and this is the first time the hardware was
 325 plugged in, show a desktop notification suggesting to install the
 326 package or packages.</li>
 327
 328 <li>If the user click on the 'install package now' button, ask
 329 aptdaemon via the PackageKit API to install the requrired package.</li>
 330
 331 <li>aptdaemon ask for root password or sudo password, and install the
 332 package while showing progress information in a window.</li>
 333
 334 </ul>
 335
 336 <p>I still need to come up with a better name for the system.  Here
 337 are some screen shots showing the prototype in action.  First the
 338 notification, then the password request, and finally the request to
 339 approve all the dependencies.  Sorry for the Norwegian Bokmål GUI.</p>
 340
 341 <p><img src="http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png">
 342 <br><img src="http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png">
 343 <br><img src="http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png">
 344 <br><img src="http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png">
 345 <br><img src="http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-5-installing-details.png" width="70%"></p>
 346
 347 <p>The prototype still need to be improved with longer timeouts, but
 348 is already useful.  The database of hardware to package mappings also
 349 need more work.  It is currently compatible with the Ubuntu way of
 350 storing such information in the package control file, but could be
 351 changed to use other formats instead or in addition to the current
 352 method.  I've dropped the use of discover for this mapping, as the
 353 modalias approach is more flexible and easier to use on Linux as long
 354 as the Linux kernel expose its modalias strings directly.</p>
 355
 356 <p><strong>Update 2013-01-21 16:50</strong>: Due to popular demand,
 357 here is the command required to check out and build the source: Use
 358 '<tt>svn checkout
 359 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
 360 hw-support-handler; debuild</tt>'.  If you lack debuild, install the
 361 devscripts package.</p>
 362
 363 <p><strong>Update 2013-01-23 12:00</strong>: The project is now
 364 renamed to Isenkram and the source moved from the Debian Edu
 365 subversion repository to a Debian collab-maint git repository.  See
 366 <a href="http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html">build
 367 instructions</a> for details.</p>
 368
 369       </div>
 370       <div class="tags">
 371
 372
 373         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>.
 374
 375
 376       </div>
 377     </div>
 378     <div class="padding"></div>
 379
 380     <div class="entry">
 381       <div class="title">
 382         <a href="http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html">Using modalias info to find packages handling my hardware</a>
 383       </div>
 384       <div class="date">
 385         15th January 2013
 386       </div>
 387       <div class="body">
 388         <p>Yesterday, I wrote about the
 389 <a href="http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html">modalias
 390 values provided by the Linux kernel</a> following my hope for
 391 <a href="http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html">better
 392 dongle support in Debian</a>.  Using this knowledge, I have tested how
 393 modalias values attached to package names can be used to map packages
 394 to hardware.  This allow the system to look up and suggest relevant
 395 packages when I plug in some new hardware into my machine, and replace
 396 discover and discover-data as the database used to map hardware to
 397 packages.</p>
 398
 399 <p>I create a modaliases file with entries like the following,
 400 containing package name, kernel module name (if relevant, otherwise
 401 the package name) and globs matching the relevant hardware
 402 modalias.</p>
 403
 404 <p><blockquote>
 405 Package: package-name
 406 <br>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)</p>
 407 </blockquote></p>
 408
 409 <p>It is fairly trivial to write code to find the relevant packages
 410 for a given modalias value using this file.</p>
 411
 412 <p>An entry like this would suggest the video and picture application
 413 cheese for many USB web cameras (interface bus class 0E01):</p>
 414
 415 <p><blockquote>
 416 Package: cheese
 417 <br>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)</p>
 418 </blockquote></p>
 419
 420 <p>An entry like this would suggest the pcmciautils package when a
 421 CardBus bridge (bus class 0607) PCI device is present:</p>
 422
 423 <p><blockquote>
 424 Package: pcmciautils
 425 <br>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
 426 </blockquote></p>
 427
 428 <p>An entry like this would suggest the package colorhug-client when
 429 plugging in a ColorHug with USB IDs 04D8:F8DA:</p>
 430
 431 <p><blockquote>
 432 Package: colorhug-client
 433 <br>Modaliases: colorhug-client(usb:v04D8pF8DAd*)</p>
 434 </blockquote></p>
 435
 436 <p>I believe the format is compatible with the format of the Packages
 437 file in the Debian archive.  Ubuntu already uses their Packages file
 438 to store their mappings from packages to hardware.</p>
 439
 440 <p>By adding a XB-Modaliases: header in debian/control, any .deb can
 441 announce the hardware it support in a way my prototype understand.
 442 This allow those publishing packages in an APT source outside the
 443 Debian archive as well as those backporting packages to make sure the
 444 hardware mapping are included in the package meta information.  I've
 445 tested such header in the pymissile package, and its modalias mapping
 446 is working as it should with my prototype.  It even made it to Ubuntu
 447 Raring.</p>
 448
 449 <p>To test if it was possible to look up supported hardware using only
 450 the shell tools available in the Debian installer, I wrote a shell
 451 implementation of the lookup code.  The idea is to create files for
 452 each modalias and let the shell do the matching.  Please check out and
 453 try the
 454 <a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co">hw-support-lookup</a>
 455 shell script.  It run without any extra dependencies and fetch the
 456 hardware mappings from the Debian archive and the subversion
 457 repository where I currently work on my prototype.</p>
 458
 459 <p>When I use it on a machine with a yubikey inserted, it suggest to
 460 install yubikey-personalization:</p>
 461
 462 <p><blockquote>
 463 % ./hw-support-lookup
 464 <br>yubikey-personalization
 465 <br>%
 466 </blockquote></p>
 467
 468 <p>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
 469 propose to install the pcmciautils package:</p>
 470
 471 <p><blockquote>
 472 % ./hw-support-lookup
 473 <br>pcmciautils
 474 <br>%
 475 </blockquote></p>
 476
 477 <p>If you know of any hardware-package mapping that should be added to
 478 <a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co">my
 479 database</a>, please tell me about it.</p>
 480
 481 <p>It could be possible to generate several of the mappings between
 482 packages and hardware.  One source would be to look at packages with
 483 kernel modules, ie packages with *.ko files in /lib/modules/, and
 484 extract their modalias information.  Another would be to look at
 485 packages with udev rules, ie packages with files in
 486 /lib/udev/rules.d/, and extract their vendor/model information to
 487 generate a modalias matching rule.  I have not tested any of these to
 488 see if it work.</p>
 489
 490 <p>If you want to help implementing a system to let us propose what
 491 packages to install when new hardware is plugged into a Debian
 492 machine, please send me an email or talk to me on
 493 <a href="irc://irc.debian.org/%23debian-devel">#debian-devel</a>.</p>
 494
 495       </div>
 496       <div class="tags">
 497
 498
 499         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>.
 500
 501
 502       </div>
 503     </div>
 504     <div class="padding"></div>
 505
 506     <div class="entry">
 507       <div class="title">
 508         <a href="http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html">Modalias strings - a practical way to map "stuff" to hardware</a>
 509       </div>
 510       <div class="date">
 511         14th January 2013
 512       </div>
 513       <div class="body">
 514         <p>While looking into how to look up Debian packages based on hardware
 515 information, to find the packages that support a given piece of
 516 hardware, I refreshed my memory regarding modalias values, and decided
 517 to document the details.  Here are my findings so far, also available
 518 in
 519 <a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/">the
 520 Debian Edu subversion repository</a>:
 521
 522 <p><strong>Modalias decoded</strong></p>
 523
 524 <p>This document try to explain what the different types of modalias
 525 values stands for.  It is in part based on information from
 526 &lt;URL: <a href="https://wiki.archlinux.org/index.php/Modalias">https://wiki.archlinux.org/index.php/Modalias</a> &gt;,
 527 &lt;URL: <a href="http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device">http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device</a> &gt;,
 528 &lt;URL: <a href="http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c">http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c</a> &gt; and
 529 &lt;URL: <a href="http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&view=markup">http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&view=markup</a> &gt;.
 530
 531 <p>The modalias entries for a given Linux machine can be found using
 532 this shell script:</p>
 533
 534 <pre>
 535 find /sys -name modalias -print0 | xargs -0 cat | sort -u
 536 </pre>
 537
 538 <p>The supported modalias globs for a given kernel module can be found
 539 using modinfo:</p>
 540
 541 <pre>
 542 % /sbin/modinfo psmouse | grep alias:
 543 alias:          serio:ty05pr*id*ex*
 544 alias:          serio:ty01pr*id*ex*
 545 %
 546 </pre>
 547
 548 <p><strong>PCI subtype</strong></p>
 549
 550 <p>A typical PCI entry can look like this.  This is an Intel Host
 551 Bridge memory controller:</p>
 552
 553 <p><blockquote>
 554 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
 555 </blockquote></p>
 556
 557 <p>This represent these values:</p>
 558
 559 <pre>
 560  v   00008086  (vendor)
 561  d   00002770  (device)
 562  sv  00001028  (subvendor)
 563  sd  000001AD  (subdevice)
 564  bc  06        (bus class)
 565  sc  00        (bus subclass)
 566  i   00        (interface)
 567 </pre>
 568
 569 <p>The vendor/device values are the same values outputted from 'lspci
 570 -n' as 8086:2770.  The bus class/subclass is also shown by lspci as
 571 0600.  The 0600 class is a host bridge.  Other useful bus values are
 572 0300 (VGA compatible card) and 0200 (Ethernet controller).</p>
 573
 574 <p>Not sure how to figure out the interface value, nor what it
 575 means.</p>
 576
 577 <p><strong>USB subtype</strong></p>
 578
 579 <p>Some typical USB entries can look like this.  This is an internal
 580 USB hub in a laptop:</p>
 581
 582 <p><blockquote>
 583 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
 584 </blockquote></p>
 585
 586 <p>Here is the values included in this alias:</p>
 587
 588 <pre>
 589  v    1D6B  (device vendor)
 590  p    0001  (device product)
 591  d    0206  (bcddevice)
 592  dc     09  (device class)
 593  dsc    00  (device subclass)
 594  dp     00  (device protocol)
 595  ic     09  (interface class)
 596  isc    00  (interface subclass)
 597  ip     00  (interface protocol)
 598 </pre>
 599
 600 <p>The 0900 device class/subclass means hub.  Some times the relevant
 601 class is in the interface class section.  For a simple USB web camera,
 602 these alias entries show up:</p>
 603
 604 <p><blockquote>
 605 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
 606 <br>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
 607 <br>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
 608 <br>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
 609 </blockquote></p>
 610
 611 <p>Interface class 0E01 is video control, 0E02 is video streaming (aka
 612 camera), 0101 is audio control device and 0102 is audio streaming (aka
 613 microphone).  Thus this is a camera with microphone included.</p>
 614
 615 <p><strong>ACPI subtype</strong></p>
 616
 617 <p>The ACPI type is used for several non-PCI/USB stuff.  This is an IR
 618 receiver in a Thinkpad X40:</p>
 619
 620 <p><blockquote>
 621 acpi:IBM0071:PNP0511:
 622 </blockquote></p>
 623
 624 <p>The values between the colons are IDs.</p>
 625
 626 <p><strong>DMI subtype</strong></p>
 627
 628 <p>The DMI table contain lots of information about the computer case
 629 and model.  This is an entry for a IBM Thinkpad X40, fetched from
 630 /sys/devices/virtual/dmi/id/modalias:</p>
 631
 632 <p><blockquote>
 633 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
 634 </blockquote></p>
 635
 636 <p>The values present are</p>
 637
 638 <pre>
 639  bvn  IBM            (BIOS vendor)
 640  bvr  1UETB6WW(1.66) (BIOS version)
 641  bd   06/15/2005     (BIOS date)
 642  svn  IBM            (system vendor)
 643  pn   2371H4G        (product name)
 644  pvr  ThinkPadX40    (product version)
 645  rvn  IBM            (board vendor)
 646  rn   2371H4G        (board name)
 647  rvr  NotAvailable   (board version)
 648  cvn  IBM            (chassis vendor)
 649  ct   10             (chassis type)
 650  cvr  NotAvailable   (chassis version)
 651 </pre>
 652
 653 <p>The chassis type 10 is Notebook.  Other interesting values can be
 654 found in the dmidecode source:</p>
 655
 656 <pre>
 657   3 Desktop
 658   4 Low Profile Desktop
 659   5 Pizza Box
 660   6 Mini Tower
 661   7 Tower
 662   8 Portable
 663   9 Laptop
 664  10 Notebook
 665  11 Hand Held
 666  12 Docking Station
 667  13 All In One
 668  14 Sub Notebook
 669  15 Space-saving
 670  16 Lunch Box
 671  17 Main Server Chassis
 672  18 Expansion Chassis
 673  19 Sub Chassis
 674  20 Bus Expansion Chassis
 675  21 Peripheral Chassis
 676  22 RAID Chassis
 677  23 Rack Mount Chassis
 678  24 Sealed-case PC
 679  25 Multi-system
 680  26 CompactPCI
 681  27 AdvancedTCA
 682  28 Blade
 683  29 Blade Enclosing
 684 </pre>
 685
 686 <p>The chassis type values are not always accurately set in the DMI
 687 table.  For example my home server is a tower, but the DMI modalias
 688 claim it is a desktop.</p>
 689
 690 <p><strong>SerIO subtype</strong></p>
 691
 692 <p>This type is used for PS/2 mouse plugs.  One example is from my
 693 test machine:</p>
 694
 695 <p><blockquote>
 696 serio:ty01pr00id00ex00
 697 </blockquote></p>
 698
 699 <p>The values present are</p>
 700
 701 <pre>
 702   ty  01  (type)
 703   pr  00  (prototype)
 704   id  00  (id)
 705   ex  00  (extra)
 706 </pre>
 707
 708 <p>This type is supported by the psmouse driver.  I am not sure what
 709 the valid values are.</p>
 710
 711 <p><strong>Other subtypes</strong></p>
 712
 713 <p>There are heaps of other modalias subtypes according to
 714 file2alias.c.  There is the rest of the list from that source: amba,
 715 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
 716 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
 717 vmbus, x86cpu and zorro.  I did not spend time documenting all of
 718 these, as they do not seem relevant for my intended use with mapping
 719 hardware to packages when new stuff is inserted during run time.</p>
 720
 721 <p><strong>Looking up kernel modules using modalias values</strong></p>
 722
 723 <p>To check which kernel modules provide support for a given modalias,
 724 one can use the following shell script:</p>
 725
 726 <pre>
 727   for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
 728     echo "$id" ; \
 729     /sbin/modprobe --show-depends "$id"|sed 's/^/  /' ; \
 730   done
 731 </pre>
 732
 733 <p>The output can look like this (only the first few entries as the
 734 list is very long on my test machine):</p>
 735
 736 <pre>
 737   acpi:ACPI0003:
 738     insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
 739   acpi:device:
 740   FATAL: Module acpi:device: not found.
 741   acpi:IBM0068:
 742     insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
 743     insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
 744     insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
 745     insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
 746   acpi:IBM0071:PNP0511:
 747     insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
 748     insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
 749     insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
 750   [...]
 751 </pre>
 752
 753 <p>If you want to help implementing a system to let us propose what
 754 packages to install when new hardware is plugged into a Debian
 755 machine, please send me an email or talk to me on
 756 <a href="irc://irc.debian.org/%23debian-devel">#debian-devel</a>.</p>
 757
 758 <p><strong>Update 2013-01-15:</strong> Rewrite "cat $(find ...)" to
 759 "find ... -print0 | xargs -0 cat" to make sure it handle directories
 760 in /sys/ with space in them.</p>
 761
 762       </div>
 763       <div class="tags">
 764
 765
 766         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>.
 767
 768
 769       </div>
 770     </div>
 771     <div class="padding"></div>
 772
 773     <div class="entry">
 774       <div class="title">
 775         <a href="http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html">Moved the pymissile Debian packaging to collab-maint</a>
 776       </div>
 777       <div class="date">
 778         10th January 2013
 779       </div>
 780       <div class="body">
 781         <p>As part of my investigation on how to improve the support in Debian
 782 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
 783 Launcher and updated the Debian package
 784 <a href="http://packages.qa.debian.org/pymissile">pymissile</a> to make
 785 sure udev will fix the device permissions when it is plugged in.  I
 786 also added a "Modaliases" header to test it in the Debian archive and
 787 hopefully make the package be proposed by jockey in Ubuntu when a user
 788 plug in his rocket launcher.  In the process I moved the source to a
 789 git repository under collab-maint, to make it easier for any DD to
 790 contribute.  <a href="http://code.google.com/p/pymissile/">Upstream</a>
 791 is not very active, but the software still work for me even after five
 792 years of relative silence.  The new git repository is not listed in
 793 the uploaded package yet, because I want to test the other changes a
 794 bit more before I upload the new version.  If you want to check out
 795 the new version with a .desktop file included, visit the
 796 <a href="http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git">gitweb
 797 view</a> or use "<tt>git clone
 798 git://anonscm.debian.org/collab-maint/pymissile.git</tt>".</p>
 799
 800       </div>
 801       <div class="tags">
 802
 803
 804         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>, <a href="http://people.skolelinux.org/pere/blog/tags/robot">robot</a>.
 805
 806
 807       </div>
 808     </div>
 809     <div class="padding"></div>
 810
 811     <div class="entry">
 812       <div class="title">
 813         <a href="http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html">Lets make hardware dongles easier to use in Debian</a>
 814       </div>
 815       <div class="date">
 816          9th January 2013
 817       </div>
 818       <div class="body">
 819         <p>One thing that annoys me with Debian and Linux distributions in
 820 general, is that there is a great package management system with the
 821 ability to automatically install software packages by downloading them
 822 from the distribution mirrors, but no way to get it to automatically
 823 install the packages I need to use the hardware I plug into my
 824 machine.  Even if the package to use it is easily available from the
 825 Linux distribution.  When I plug in a LEGO Mindstorms NXT, it could
 826 suggest to automatically install the python-nxt, nbc and t2n packages
 827 I need to talk to it.  When I plug in a Yubikey, it could propose the
 828 yubikey-personalization package.  The information required to do this
 829 is available, but no-one have pulled all the pieces together.</p>
 830
 831 <p>Some years ago, I proposed to
 832 <a href="http://lists.debian.org/debian-devel/2010/05/msg01206.html">use
 833 the discover subsystem to implement this</a>.  The idea is fairly
 834 simple:
 835
 836 <ul>
 837
 838 <li>Add a desktop entry in /usr/share/autostart/ pointing to a program
 839   starting when a user log in.</li>
 840
 841 <li>Set this program up to listen for kernel events emitted when new
 842   hardware is inserted into the computer.</li>
 843
 844 <li>When new hardware is inserted, look up the hardware ID in a
 845   database mapping to packages, and take note of any non-installed
 846   packages.</li>
 847
 848 <li>Show a message to the user proposing to install the discovered
 849   package, and make it easy to install it.</li>
 850
 851 </ul>
 852
 853 <p>I am not sure what the best way to implement this is, but my
 854 initial idea was to use dbus events to discover new hardware, the
 855 discover database to find packages and
 856 <a href="http://www.packagekit.org/">PackageKit</a> to install
 857 packages.</p>
 858
 859 <p>Yesterday, I found time to try to implement this idea, and the
 860 draft package is now checked into
 861 <a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/">the
 862 Debian Edu subversion repository</a>.  In the process, I updated the
 863 <a href="http://packages.qa.debian.org/d/discover-data.html">discover-data</a>
 864 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
 865 the relevant packages in Debian, and uploaded a new version
 866 2.2013.01.09 to unstable.  I also discovered that the current
 867 <a href="http://packages.qa.debian.org/d/discover.html">discover</a>
 868 package in Debian no longer discovered any USB devices, because
 869 /proc/bus/usb/devices is no longer present.  I ported it to use
 870 libusb as a fall back option to get it working.  The fixed package
 871 version 2.1.2-6 is now in experimental (didn't upload it to unstable
 872 because of the freeze).</p>
 873
 874 <p>With this prototype in place, I can insert my Yubikey, and get this
 875 desktop notification to show up (only once, the first time it is
 876 inserted):</p>
 877
 878 <p align="center"><img src="http://people.skolelinux.org/pere/blog/images/2013-01-09-hw-autoinstall.png"></p>
 879
 880 <p>For this prototype to be really useful, some way to automatically
 881 install the proposed packages by pressing the "Please install
 882 program(s)" button should to be implemented.</p>
 883
 884 <p>If this idea seem useful to you, and you want to help make it
 885 happen, please help me update the discover-data database with mappings
 886 from hardware to Debian packages.  Check if 'discover-pkginstall -l'
 887 list the package you would like to have installed when a given
 888 hardware device is inserted into your computer, and report bugs using
 889 reportbug if it isn't.  Or, if you know of a better way to provide
 890 such mapping, please let me know.</p>
 891
 892 <p>This prototype need more work, and there are several questions that
 893 should be considered before it is ready for production use.  Is dbus
 894 the correct way to detect new hardware?  At the moment I look for HAL
 895 dbus events on the system bus, because that is the events I could see
 896 on my Debian Squeeze KDE desktop.  Are there better events to use?
 897 How should the user be notified?  Is the desktop notification
 898 mechanism the best option, or should the background daemon raise a
 899 popup instead?  How should packages be installed?  When should they
 900 not be installed?</p>
 901
 902 <p>If you want to help getting such feature implemented in Debian,
 903 please send me an email. :)</p>
 904
 905       </div>
 906       <div class="tags">
 907
 908
 909         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>.
 910
 911
 912       </div>
 913     </div>
 914     <div class="padding"></div>
 915
 916     <p style="text-align: right;"><a href="isenkram.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
 917     <div id="sidebar">
 918
 919
 920
 921 <h2>Archive</h2>
 922 <ul>
 923
 924 <li>2014
 925 <ul>
 926
 927 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 928
 929 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 930
 931 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
 932
 933 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
 934
 935 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
 936
 937 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
 938
 939 </ul></li>
 940
 941 <li>2013
 942 <ul>
 943
 944 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 945
 946 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 947
 948 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 949
 950 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 951
 952 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 953
 954 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 955
 956 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 957
 958 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 959
 960 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 961
 962 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 963
 964 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 965
 966 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
 967
 968 </ul></li>
 969
 970 <li>2012
 971 <ul>
 972
 973 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 974
 975 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 976
 977 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 978
 979 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 980
 981 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 982
 983 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 984
 985 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 986
 987 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 988
 989 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 990
 991 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 992
 993 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 994
 995 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 996
 997 </ul></li>
 998
 999 <li>2011
1000 <ul>
1001
1002 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1003
1004 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1005
1006 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1007
1008 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1009
1010 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1011
1012 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1013
1014 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1015
1016 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1017
1018 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1019
1020 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1021
1022 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1023
1024 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1025
1026 </ul></li>
1027
1028 <li>2010
1029 <ul>
1030
1031 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1032
1033 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1034
1035 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1036
1037 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1038
1039 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1040
1041 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1042
1043 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1044
1045 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1046
1047 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1048
1049 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1050
1051 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1052
1053 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1054
1055 </ul></li>
1056
1057 <li>2009
1058 <ul>
1059
1060 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1061
1062 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1063
1064 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1065
1066 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1067
1068 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1069
1070 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1071
1072 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1073
1074 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1075
1076 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1077
1078 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1079
1080 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1081
1082 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1083
1084 </ul></li>
1085
1086 <li>2008
1087 <ul>
1088
1089 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1090
1091 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1092
1093 </ul></li>
1094
1095 </ul>
1096
1097
1098
1099 <h2>Tags</h2>
1100 <ul>
1101
1102  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1103
1104  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1105
1106  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1107
1108  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1109
1110  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (8)</a></li>
1111
1112  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (14)</a></li>
1113
1114  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1115
1116  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1117
1118  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (99)</a></li>
1119
1120  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (147)</a></li>
1121
1122  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1123
1124  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (15)</a></li>
1125
1126  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (11)</a></li>
1127
1128  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1129
1130  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (248)</a></li>
1131
1132  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
1133
1134  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1135
1136  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
1137
1138  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (8)</a></li>
1139
1140  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
1141
1142  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (40)</a></li>
1143
1144  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (9)</a></li>
1145
1146  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
1147
1148  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1149
1150  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (7)</a></li>
1151
1152  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1153
1154  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1155
1156  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (28)</a></li>
1157
1158  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (246)</a></li>
1159
1160  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (162)</a></li>
1161
1162  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (11)</a></li>
1163
1164  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1165
1166  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (46)</a></li>
1167
1168  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (72)</a></li>
1169
1170  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1171
1172  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1173
1174  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1175
1176  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1177
1178  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1179
1180  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1181
1182  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1183
1184  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1185
1186  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (40)</a></li>
1187
1188  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1189
1190  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1191
1192  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (44)</a></li>
1193
1194  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1195
1196  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1197
1198  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (25)</a></li>
1199
1200  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
1201
1202  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1203
1204  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (42)</a></li>
1205
1206  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1207
1208  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (32)</a></li>
1209
1210 </ul>
1211
1212
1213     </div>
1214     <p style="text-align: right">
1215  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1216 </p>
1217
1218   </body>
1219 </html>