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