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