1 <?xml version=
"1.0" encoding=
"ISO-8859-1"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries from January
2013</title>
5 <description>Entries from January
2013</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>How to find a browser plugin supporting a given MIME type
</title>
11 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
13 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
14 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
15 install to get support for a given MIME type. Thanks to
16 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
17 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
18 Unfortunately, not very many packages provide the needed meta
19 information, Anyway, here is a small script to look up all browser
20 plugin packages announcing ther MIME support using this specification:
</p
>
26 def pkgs_handling_mimetype(mimetype):
31 version = pkg.candidate
33 version = pkg.installed
36 record = version.record
37 if not record.has_key(
'Npp-MimeType
'):
39 mime_types = record[
'Npp-MimeType
'].split(
',
')
41 t = t.rstrip().strip()
43 thepkgs.append(pkg.name)
45 mimetype =
"audio/ogg
"
46 if
1 < len(sys.argv):
47 mimetype = sys.argv[
1]
48 print
"Browser plugin packages supporting %s:
" % mimetype
49 for pkg in pkgs_handling_mimetype(mimetype):
50 print
" %s
" %pkg
53 <p
>It can be used like this to look up a given MIME type:
</p
>
56 % ./apt-find-browserplug-for-mimetype
57 Browser plugin packages supporting audio/ogg:
59 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
60 Browser plugin packages supporting application/x-shockwave-flash:
65 <p
>In Ubuntu this mechanism is combined with support in the browser
66 itself to query for plugins and propose to install the needed
67 packages. It would be great if Debian supported such feature too. Is
68 anyone working on adding it?
</p
>
70 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
71 request for icweasel support for this feature is
72 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
73 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
74 of manpower and wish for a different design is the reason thus feature
75 is not yet in iceweasel from Debian.
</p
>
80 <title>What is the most supported MIME type in Debian?
</title>
81 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
82 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
83 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
84 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
85 proposal to add AppStream information to the Debian archive
</a
>, is a
86 proposal to make it possible for a Desktop application to propose to
87 the user some package to install to gain support for a given MIME
88 type, font, library etc. that is currently missing. With such
89 mechanism in place, it would be possible for the desktop to
90 automatically propose and install leocad if some LDraw file is
91 downloaded by the browser.
</p
>
93 <p
>To get some idea about the current content of the archive, I decided
94 to write a simple program to extract all .desktop files from the
95 Debian archive and look up the claimed MIME support there. The result
97 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
98 site
</a
>. Using the collected information, it become possible to
99 answer the question in the title. Here are the
20 most supported MIME
100 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
101 The complete list is available from the link above.
</p
>
103 <p
><strong
>Debian Stable:
</strong
></p
>
107 ----- -----------------------
130 <p
><strong
>Debian Testing:
</strong
></p
>
134 ----- -----------------------
157 <p
><strong
>Debian Unstable:
</strong
></p
>
161 ----- -----------------------
184 <p
>I am told that PackageKit can provide an API to access the kind of
185 information mentioned in DEP-
11. I have not yet had time to look at
186 it, but hope the PackageKit people in Debian are on top of these
189 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
190 discovering a typo in my script.
</p
>
195 <title>Using modalias info to find packages handling my hardware
</title>
196 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
197 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
198 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
199 <description><p
>Yesterday, I wrote about the
200 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
201 values provided by the Linux kernel
</a
> following my hope for
202 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
203 dongle support in Debian
</a
>. Using this knowledge, I have tested how
204 modalias values attached to package names can be used to map packages
205 to hardware. This allow the system to look up and suggest relevant
206 packages when I plug in some new hardware into my machine, and replace
207 discover and discover-data as the database used to map hardware to
210 <p
>I create a modaliases file with entries like the following,
211 containing package name, kernel module name (if relevant, otherwise
212 the package name) and globs matching the relevant hardware
215 <p
><blockquote
>
216 Package: package-name
217 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
218 </blockquote
></p
>
220 <p
>It is fairly trivial to write code to find the relevant packages
221 for a given modalias value using this file.
</p
>
223 <p
>An entry like this would suggest the video and picture application
224 cheese for many USB web cameras (interface bus class
0E01):
</p
>
226 <p
><blockquote
>
228 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
229 </blockquote
></p
>
231 <p
>An entry like this would suggest the pcmciautils package when a
232 CardBus bridge (bus class
0607) PCI device is present:
</p
>
234 <p
><blockquote
>
236 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
237 </blockquote
></p
>
239 <p
>An entry like this would suggest the package colorhug-client when
240 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
242 <p
><blockquote
>
243 Package: colorhug-client
244 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
245 </blockquote
></p
>
247 <p
>I believe the format is compatible with the format of the Packages
248 file in the Debian archive. Ubuntu already uses their Packages file
249 to store their mappings from packages to hardware.
</p
>
251 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
252 announce the hardware it support in a way my prototype understand.
253 This allow those publishing packages in an APT source outside the
254 Debian archive as well as those backporting packages to make sure the
255 hardware mapping are included in the package meta information. I
've
256 tested such header in the pymissile package, and its modalias mapping
257 is working as it should with my prototype. It even made it to Ubuntu
260 <p
>To test if it was possible to look up supported hardware using only
261 the shell tools available in the Debian installer, I wrote a shell
262 implementation of the lookup code. The idea is to create files for
263 each modalias and let the shell do the matching. Please check out and
265 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
266 shell script. It run without any extra dependencies and fetch the
267 hardware mappings from the Debian archive and the subversion
268 repository where I currently work on my prototype.
</p
>
270 <p
>When I use it on a machine with a yubikey inserted, it suggest to
271 install yubikey-personalization:
</p
>
273 <p
><blockquote
>
274 % ./hw-support-lookup
275 <br
>yubikey-personalization
277 </blockquote
></p
>
279 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
280 propose to install the pcmciautils package:
</p
>
282 <p
><blockquote
>
283 % ./hw-support-lookup
284 <br
>pcmciautils
286 </blockquote
></p
>
288 <p
>If you know of any hardware-package mapping that should be added to
289 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
290 database
</a
>, please tell me about it.
</p
>
292 <p
>It could be possible to generate several of the mappings between
293 packages and hardware. One source would be to look at packages with
294 kernel modules, ie packages with *.ko files in /lib/modules/, and
295 extract their modalias information. Another would be to look at
296 packages with udev rules, ie packages with files in
297 /lib/udev/rules.d/, and extract their vendor/model information to
298 generate a modalias matching rule. I have not tested any of these to
299 see if it work.
</p
>
301 <p
>If you want to help implementing a system to let us propose what
302 packages to install when new hardware is plugged into a Debian
303 machine, please send me an email or talk to me on
304 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
309 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
310 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
311 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
312 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
313 <description><p
>While looking into how to look up Debian packages based on hardware
314 information, to find the packages that support a given piece of
315 hardware, I refreshed my memory regarding modalias values, and decided
316 to document the details. Here are my findings so far, also available
318 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
319 Debian Edu subversion repository
</a
>:
321 <p
><strong
>Modalias decoded
</strong
></p
>
323 <p
>This document try to explain what the different types of modalias
324 values stands for. It is in part based on information from
325 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
326 &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;,
327 &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
328 &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;.
330 <p
>The modalias entries for a given Linux machine can be found using
331 this shell script:
</p
>
334 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
337 <p
>The supported modalias globs for a given kernel module can be found
338 using modinfo:
</p
>
341 % /sbin/modinfo psmouse | grep alias:
342 alias: serio:ty05pr*id*ex*
343 alias: serio:ty01pr*id*ex*
347 <p
><strong
>PCI subtype
</strong
></p
>
349 <p
>A typical PCI entry can look like this. This is an Intel Host
350 Bridge memory controller:
</p
>
352 <p
><blockquote
>
353 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
354 </blockquote
></p
>
356 <p
>This represent these values:
</p
>
361 sv
00001028 (subvendor)
362 sd
000001AD (subdevice)
368 <p
>The vendor/device values are the same values outputted from
'lspci
369 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
370 0600. The
0600 class is a host bridge. Other useful bus values are
371 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
373 <p
>Not sure how to figure out the interface value, nor what it
376 <p
><strong
>USB subtype
</strong
></p
>
378 <p
>Some typical USB entries can look like this. This is an internal
379 USB hub in a laptop:
</p
>
381 <p
><blockquote
>
382 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
383 </blockquote
></p
>
385 <p
>Here is the values included in this alias:
</p
>
388 v
1D6B (device vendor)
389 p
0001 (device product)
392 dsc
00 (device subclass)
393 dp
00 (device protocol)
394 ic
09 (interface class)
395 isc
00 (interface subclass)
396 ip
00 (interface protocol)
399 <p
>The
0900 device class/subclass means hub. Some times the relevant
400 class is in the interface class section. For a simple USB web camera,
401 these alias entries show up:
</p
>
403 <p
><blockquote
>
404 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
405 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
406 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
407 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
408 </blockquote
></p
>
410 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
411 camera),
0101 is audio control device and
0102 is audio streaming (aka
412 microphone). Thus this is a camera with microphone included.
</p
>
414 <p
><strong
>ACPI subtype
</strong
></p
>
416 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
417 receiver in a Thinkpad X40:
</p
>
419 <p
><blockquote
>
420 acpi:IBM0071:PNP0511:
421 </blockquote
></p
>
423 <p
>The values between the colons are IDs.
</p
>
425 <p
><strong
>DMI subtype
</strong
></p
>
427 <p
>The DMI table contain lots of information about the computer case
428 and model. This is an entry for a IBM Thinkpad X40, fetched from
429 /sys/devices/virtual/dmi/id/modalias:
</p
>
431 <p
><blockquote
>
432 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
433 </blockquote
></p
>
435 <p
>The values present are
</p
>
438 bvn IBM (BIOS vendor)
439 bvr
1UETB
6WW(
1.66) (BIOS version)
440 bd
06/
15/
2005 (BIOS date)
441 svn IBM (system vendor)
442 pn
2371H4G (product name)
443 pvr ThinkPadX40 (product version)
444 rvn IBM (board vendor)
445 rn
2371H4G (board name)
446 rvr NotAvailable (board version)
447 cvn IBM (chassis vendor)
449 cvr NotAvailable (chassis version)
452 <p
>The chassis type
10 is Notebook. Other interesting values can be
453 found in the dmidecode source:
</p
>
457 4 Low Profile Desktop
470 17 Main Server Chassis
473 20 Bus Expansion Chassis
474 21 Peripheral Chassis
476 23 Rack Mount Chassis
485 <p
>The chassis type values are not always accurately set in the DMI
486 table. For example my home server is a tower, but the DMI modalias
487 claim it is a desktop.
</p
>
489 <p
><strong
>SerIO subtype
</strong
></p
>
491 <p
>This type is used for PS/
2 mouse plugs. One example is from my
492 test machine:
</p
>
494 <p
><blockquote
>
495 serio:ty01pr00id00ex00
496 </blockquote
></p
>
498 <p
>The values present are
</p
>
507 <p
>This type is supported by the psmouse driver. I am not sure what
508 the valid values are.
</p
>
510 <p
><strong
>Other subtypes
</strong
></p
>
512 <p
>There are heaps of other modalias subtypes according to
513 file2alias.c. There is the rest of the list from that source: amba,
514 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
515 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
516 vmbus, x86cpu and zorro. I did not spend time documenting all of
517 these, as they do not seem relevant for my intended use with mapping
518 hardware to packages when new stuff is inserted during run time.
</p
>
520 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
522 <p
>To check which kernel modules provide support for a given modalias,
523 one can use the following shell script:
</p
>
526 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
527 echo
"$id
" ; \
528 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
532 <p
>The output can look like this (only the first few entries as the
533 list is very long on my test machine):
</p
>
537 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
539 FATAL: Module acpi:device: not found.
541 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
542 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
543 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
544 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
545 acpi:IBM0071:PNP0511:
546 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
547 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
548 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
552 <p
>If you want to help implementing a system to let us propose what
553 packages to install when new hardware is plugged into a Debian
554 machine, please send me an email or talk to me on
555 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
557 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
558 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
559 in /sys/ with space in them.
</p
>
564 <title>Moved the pymissile Debian packaging to collab-maint
</title>
565 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
566 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
567 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
568 <description><p
>As part of my investigation on how to improve the support in Debian
569 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
570 Launcher and updated the Debian package
571 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
572 sure udev will fix the device permissions when it is plugged in. I
573 also added a
"Modaliases
" header to test it in the Debian archive and
574 hopefully make the package be proposed by jockey in Ubuntu when a user
575 plug in his rocket launcher. In the process I moved the source to a
576 git repository under collab-maint, to make it easier for any DD to
577 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
578 is not very active, but the software still work for me even after five
579 years of relative silence. The new git repository is not listed in
580 the uploaded package yet, because I want to test the other changes a
581 bit more before I upload the new version. If you want to check out
582 the new version with a .desktop file included, visit the
583 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
584 view
</a
> or use
"<tt
>git clone
585 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
590 <title>Lets make hardware dongles easier to use in Debian
</title>
591 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
592 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
593 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
594 <description><p
>One thing that annoys me with Debian and Linux distributions in
595 general, is that there is a great package management system with the
596 ability to automatically install software packages by downloading them
597 from the distribution mirrors, but no way to get it to automatically
598 install the packages I need to use the hardware I plug into my
599 machine. Even if the package to use it is easily available from the
600 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
601 suggest to automatically install the python-nxt, nbc and t2n packages
602 I need to talk to it. When I plug in a Yubikey, it could propose the
603 yubikey-personalization package. The information required to do this
604 is available, but no-one have pulled all the pieces together.
</p
>
606 <p
>Some years ago, I proposed to
607 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
608 the discover subsystem to implement this
</a
>. The idea is fairly
613 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
614 starting when a user log in.
</li
>
616 <li
>Set this program up to listen for kernel events emitted when new
617 hardware is inserted into the computer.
</li
>
619 <li
>When new hardware is inserted, look up the hardware ID in a
620 database mapping to packages, and take note of any non-installed
623 <li
>Show a message to the user proposing to install the discovered
624 package, and make it easy to install it.
</li
>
628 <p
>I am not sure what the best way to implement this is, but my
629 initial idea was to use dbus events to discover new hardware, the
630 discover database to find packages and
631 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
634 <p
>Yesterday, I found time to try to implement this idea, and the
635 draft package is now checked into
636 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
637 Debian Edu subversion repository
</a
>. In the process, I updated the
638 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
639 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
640 the relevant packages in Debian, and uploaded a new version
641 2.2013.01.09 to unstable. I also discovered that the current
642 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
643 package in Debian no longer discovered any USB devices, because
644 /proc/bus/usb/devices is no longer present. I ported it to use
645 libusb as a fall back option to get it working. The fixed package
646 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
647 because of the freeze).
</p
>
649 <p
>With this prototype in place, I can insert my Yubikey, and get this
650 desktop notification to show up (only once, the first time it is
653 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
655 <p
>For this prototype to be really useful, some way to automatically
656 install the proposed packages by pressing the
"Please install
657 program(s)
" button should to be implemented.
</p
>
659 <p
>If this idea seem useful to you, and you want to help make it
660 happen, please help me update the discover-data database with mappings
661 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
662 list the package you would like to have installed when a given
663 hardware device is inserted into your computer, and report bugs using
664 reportbug if it isn
't. Or, if you know of a better way to provide
665 such mapping, please let me know.
</p
>
667 <p
>This prototype need more work, and there are several questions that
668 should be considered before it is ready for production use. Is dbus
669 the correct way to detect new hardware? At the moment I look for HAL
670 dbus events on the system bus, because that is the events I could see
671 on my Debian Squeeze KDE desktop. Are there better events to use?
672 How should the user be notified? Is the desktop notification
673 mechanism the best option, or should the background daemon raise a
674 popup instead? How should packages be installed? When should they
675 not be installed?
</p
>
677 <p
>If you want to help getting such feature implemented in Debian,
678 please send me an email. :)
</p
>
683 <title>New IRC channel for LEGO designers using Debian
</title>
684 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
685 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
686 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
687 <description><p
>During Christmas, I have worked a bit on the Debian support for
688 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
689 NXT
</a
>. My son and I have played a bit with my NXT set, and I
690 discovered I had to build all the tools myself because none were
691 already in Debian Squeeze. If Debian support for LEGO is something
692 you care about, please join me on the IRC channel
693 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
694 irc.debian.org). There is a lot that could be done to improve the
695 Debian support for LEGO designers. For example both CAD software
696 and Mindstorm compilers are missing. :)
</p
>
698 <p
>Update
2012-
01-
03: A
699 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
700 including links to Lego related packages is now available.
</p
>
705 <title>Lenker for
2013-
01-
01</title>
706 <link>http://people.skolelinux.org/pere/blog/Lenker_for_2013_01_01.html
</link>
707 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenker_for_2013_01_01.html
</guid>
708 <pubDate>Tue,
1 Jan
2013 09:
20:
00 +
0100</pubDate>
709 <description><p
>Her er noen lenker til tekster jeg har satt pris på å lese den
710 siste måneden.
</p
>
715 <a href=
"http://www.idg.no/computerworld/article262047.ece
">Myter og
716 FUD om fri programvare
</a
> av min venn Christer Gundersen som
717 kommenterer noen av de påstandene som er spredt via Computerworld
718 Norge de siste månedene.
</li
>
720 <li
>BankID er et opplegg der utsteder (dvs. banken eller dens
721 leverandør) sitter på alt som trengs for å bruke BankID, men har
722 lovet å ikke bruke den unntatt på oppdrag fra deg. Det er greit nok
723 for banktjenester, der banken allerede har full kontroll over
724 resultatet, men problematisk når det gjelder tilgang til
725 helseopplysninger og avtaleinngåelse med andre enn banken. Jeg
726 håper protestene brer om seg.
730 <li
>2012-
12-
11 <a href=
"http://www.aftenposten.no/meninger/debatt/BankID-blottlegger-helseopplysninger-
7067148.html
">BankID
731 blottlegger helseopplysninger
</a
></li
>
733 <li
>2012-
12-
07 <a href=
"http://www.nrk.no/nyheter/norge/
1.9695027">-
734 Helseopplysningene ikke sikre med Bank-ID
</a
></li
>
737 <a href=
"https://www.bankid.no/Presse-og-nyheter/Nyhetsarkiv/
2012/Papeker-alvorlige-men-kjente-utfordringer/
">Påpeker
738 alvorlige, men kjente utfordringer
</a
> er den offisielle
739 holdningen til de som lager BankID.
</li
>
742 <a href=
"http://www.tnp.no/norway/panorama/
3419-ntnu-researcher-warns-against-security-of-bank-id-password
">NTNU
743 Researcher Warns against Security of Bank ID Password
</a
>
747 <li
>2012-
12-
11 <a href=
"http://www.aftenposten.no/nyheter/iriks/Norske-elever-er-darligst-i-Europa-pa-algebra-
7066752.html
">Norske elever er dårligst i Europa på algebra
</a
>
750 <a href=
"http://www.aftenposten.no/meninger/debatt/Realfagsdodaren-
7067173.html
">Realfagsdødaren
</a
>
753 <a href=
"http://www.bt.no/nyheter/innenriks/
112/--Forventningene-er-for-hoye-
2816450.html
">-
754 Noen må bli skuffet
</a
> - Politiet i Bergen forteller hvor lavt de
755 prioriterer hverdagskriminalitet.
</li
>
758 <a href=
"http://e24.no/jobb/kripos-ansatt-doemt-for-snoking-for-venn/
20208585">
759 Kripos-ansatt dømt for snoking for venn
</A
> - viser hvor svak
760 reaksjonen blir når politiet misbruker innsamlet informasjon. En
761 forvarsel på konsekvensene av nasjonal brev- og besøkskontroll -
762 ofte kalt Datalagringsdirektivet.
</li
>
765 <a href=
"http://www.dagbladet.no/
2012/
12/
14/kultur/debatt/kronikk/jul/ensomhet/
24838541/
">Å
766 smøre en forskjell
</a
> - om ensomhet og jul.
</li
>
769 <a href=
"http://www.aftenposten.no/meninger/kronikker/n-krise-av-gangen_-takk-
7072452.html
">Én
770 krise av gangen, takk!
</a
>
774 <a href=
"http://www.aftenposten.no/meninger/NAV-Et-mangehodet-monster--
7072165.html
">NAV:
775 Et mangehodet monster
</a
></li
>
778 <a href=
"http://www.dagbladet.no/
2011/
01/
12/kultur/debatt/kronikk/personvern/
15027203/
">Pasienter
779 uten vern
</a
> - forteller litt om hvordan Norsk Pasientregister og
780 andre helseregister raderer bort pasienters privatsfære.
</li
>
784 <a href=
"http://www.aftenposten.no/meninger/debatt/Hvorfor-er-barnefamilier-fattige-
7073951.html
">Hvorfor
785 er barnefamilier fattige?
</a
></li
>
788 <a href=
"http://www.aftenposten.no/meninger/spaltister/Den-skjulte-minoriteten--konservative-kristne-i-Norge-
7075518.html
">Den
789 skjulte minoriteten – konservative kristne i Norge
</a
> - kronikk av
790 Bjørn Stærk fra aftenposten
</li
>
793 <a href=
"http://deltemeninger.no/-/bulletin/show/
303429_folkebiblioteket-
2-
0?ref=checkpoint
">Folkebiblioteket
794 2.0</a
> - Min venn Sturle om opphavsrett og Internett, i debatt med
795 Olav Torvund.
</li
>
799 <p
>Og et godt nytt år til dere alle!
</p
>