- <div class="title"><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></div>
- <div class="date">15th January 2013</div>
- <div class="body"><p>Yesterday, I wrote about the
-<a href="http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html">modalias
-values provided by the Linux kernel</a> following my hope for
-<a href="http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html">better
-dongle support in Debian</a>. Using this knowledge, I have tested how
-modalias values attached to package names can be used to map packages
-to hardware. This allow the system to look up and suggest relevant
-packages when I plug in some new hardware into my machine, and replace
-discover and discover-data as the database used to map hardware to
-packages.</p>
-
-<p>I create a modaliases file with entries like the following,
-containing package name, kernel module name (if relevant, otherwise
-the package name) and globs matching the relevant hardware
-modalias.</p>
-
-<p><blockquote>
-Package: package-name
-<br>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)</p>
-</blockquote></p>
-
-<p>It is fairly trivial to write code to find the relevant packages
-for a given modalias value using this file.</p>
-
-<p>An entry like this would suggest the video and picture application
-cheese for many USB web cameras (interface bus class 0E01):</p>
-
-<p><blockquote>
-Package: cheese
-<br>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)</p>
-</blockquote></p>
-
-<p>An entry like this would suggest the pcmciautils package when a
-CardBus bridge (bus class 0607) PCI device is present:</p>
-
-<p><blockquote>
-Package: pcmciautils
-<br>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
-</blockquote></p>
-
-<p>An entry like this would suggest the package colorhug-client when
-plugging in a ColorHug with USB IDs 04D8:F8DA:</p>
-
-<p><blockquote>
-Package: colorhug-client
-<br>Modaliases: colorhug-client(usb:v04D8pF8DAd*)</p>
-</blockquote></p>
-
-<p>I believe the format is compatible with the format of the Packages
-file in the Debian archive. Ubuntu already uses their Packages file
-to store their mappings from packages to hardware.</p>
-
-<p>By adding a XB-Modaliases: header in debian/control, any .deb can
-announce the hardware it support in a way my prototype understand.
-This allow those publishing packages in an APT source outside the
-Debian archive as well as those backporting packages to make sure the
-hardware mapping are included in the package meta information. I've
-tested such header in the pymissile package, and its modalias mapping
-is working as it should with my prototype. It even made it to Ubuntu
-Raring.</p>
-
-<p>To test if it was possible to look up supported hardware using only
-the shell tools available in the Debian installer, I wrote a shell
-implementation of the lookup code. The idea is to create files for
-each modalias and let the shell do the matching. Please check out and
-try the
-<a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co">hw-support-lookup</a>
-shell script. It run without any extra dependencies and fetch the
-hardware mappings from the Debian archive and the subversion
-repository where I currently work on my prototype.</p>
-
-<p>When I use it on a machine with a yubikey inserted, it suggest to
-install yubikey-personalization:</p>
-
-<p><blockquote>
-% ./hw-support-lookup
-<br>yubikey-personalization
-<br>%
-</blockquote></p>
-
-<p>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
-propose to install the pcmciautils package:</p>
-
-<p><blockquote>
-% ./hw-support-lookup
-<br>pcmciautils
-<br>%
-</blockquote></p>
-
-<p>If you know of any hardware-package mapping that should be added to
-<a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co">my
-database</a>, please tell me about it.</p>
-
-<p>It could be possible to generate several of the mappings between
-packages and hardware. One source would be to look at packages with
-kernel modules, ie packages with *.ko files in /lib/modules/, and
-extract their modalias information. Another would be to look at
-packages with udev rules, ie packages with files in
-/lib/udev/rules.d/, and extract their vendor/model information to
-generate a modalias matching rule. I have not tested any of these to
-see if it work.</p>
-
-<p>If you want to help implementing a system to let us propose what
-packages to install when new hardware is plugged into a Debian
-machine, please send me an email or talk to me on
-<a href="irc://irc.debian.org/%23debian-devel">#debian-devel</a>.</p>
-</div>
- <div class="tags">
-
-
- 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>.
-
-
- </div>
- </div>
- <div class="padding"></div>
-
- <div class="entry">
- <div class="title"><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></div>
- <div class="date">14th January 2013</div>
- <div class="body"><p>While looking into how to look up Debian packages based on hardware
-information, to find the packages that support a given piece of
-hardware, I refreshed my memory regarding modalias values, and decided
-to document the details. Here are my findings so far, also available
-in
-<a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/">the
-Debian Edu subversion repository</a>:
-
-<p><strong>Modalias decoded</strong></p>
-
-<p>This document try to explain what the different types of modalias
-values stands for. It is in part based on information from
-<URL: <a href="https://wiki.archlinux.org/index.php/Modalias">https://wiki.archlinux.org/index.php/Modalias</a> >,
-<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> >,
-<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> > and
-<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> >.
-
-<p>The modalias entries for a given Linux machine can be found using
-this shell script:</p>
-
-<pre>
-cat $(find /sys -name modalias) | sort -u
-</pre>
-
-<p>The supported modalias globs for a given kernel module can be found
-using modinfo:</p>
-
-<pre>
-% /sbin/modinfo psmouse | grep alias:
-alias: serio:ty05pr*id*ex*
-alias: serio:ty01pr*id*ex*
-%
-</pre>
-
-<p><strong>PCI subtype</strong></p>
-
-<p>A typical PCI entry can look like this. This is an Intel Host
-Bridge memory controller:</p>
-
-<p><blockquote>
-pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
-</blockquote></p>
-
-<p>This represent these values:</p>
-
-<pre>
- v 00008086 (vendor)
- d 00002770 (device)
- sv 00001028 (subvendor)
- sd 000001AD (subdevice)
- bc 06 (bus class)
- sc 00 (bus subclass)
- i 00 (interface)
-</pre>
-
-<p>The vendor/device values are the same values outputted from 'lspci
--n' as 8086:2770. The bus class/subclass is also shown by lspci as
-0600. The 0600 class is a host bridge. Other useful bus values are
-0300 (VGA compatible card) and 0200 (Ethernet controller).</p>
-
-<p>Not sure how to figure out the interface value, nor what it
-means.</p>
-
-<p><strong>USB subtype</strong></p>
-
-<p>Some typical USB entries can look like this. This is an internal
-USB hub in a laptop:</p>
-
-<p><blockquote>
-usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
-</blockquote></p>
-
-<p>Here is the values included in this alias:</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Second_alpha_release_of_Debian_Edu___Skolelinux_based_on_Debian_Wheezy.html">Second alpha release of Debian Edu / Skolelinux based on Debian Wheezy</a></div>
+ <div class="date">14th May 2013</div>
+ <div class="body"><p>The <a href="http://www.skolelinux.org/">Debian Edu / Skolelinux
+project</a> is making great progress and made its second Wheezy based
+release today. This is the release announcement:</p>
+
+<p><strong>New features for Debian Edu 7.0.0 alpha1 released
+2013-05-14</strong></p>
+
+<p>This is the release notes for for Debian Edu / Skolelinux 7.0.0 edu
+alpha1, based on Debian with codename "Wheezy".</p>
+
+<p><strong>About Debian Edu and Skolelinux</strong></p>
+
+<p>Debian Edu, also known as Skolelinux, is a Linux distribution based
+on Debian providing an out-of-the box environment of a completely
+configured school network. Immediatly after installation a school
+server running all services needed for a school network is set up just
+waiting for users and machines being added via GOsa², a comfortable
+Web-UI. A netbooting environment is prepared using PXE, so after
+initial installation of the main server from CD, DVD or USB stick all
+other machines can be installed via the network.</p>
+
+<p>This is the first test release based on Wheezy (which currently is
+not released yet). Basically this is an updated and slightly improved
+version compared to the Squeeze release.</p>
+
+<p><strong>Software updates</strong></p>
+<ul>
+ <li>Install freemind (0.9.0) by default, and stop installing vym by
+ default.</li>
+ <li>Install chromium (26.0.1410.43) by default.</li>
+ <li>Install goplay (0.5-1.1) to make golearn available by default.</li>
+ <li>Updated support for Japanese input methods, now based on
+ ibus-anthy.</li>
+</ul>