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
-the
-Debian Edu subversion repository:
-
-
Modalias decoded
-
-
This document try to explain what the different types of modalias
-values stands for. It is in part based on information from
-<URL: https://wiki.archlinux.org/index.php/Modalias >,
-<URL: http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device >,
-<URL: http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c > and
-<URL: http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&view=markup >.
-
-
The modalias entries for a given Linux machine can be found using
-this shell script:
-
-
-find /sys -name modalias -print0 | xargs -0 cat | sort -u
-
-
-
The supported modalias globs for a given kernel module can be found
-using modinfo:
-
-
-% /sbin/modinfo psmouse | grep alias:
-alias: serio:ty05pr*id*ex*
-alias: serio:ty01pr*id*ex*
-%
-
-
-
PCI subtype
-
-
A typical PCI entry can look like this. This is an Intel Host
-Bridge memory controller:
-
-
-pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
-
-
-
This represent these values:
-
-
- v 00008086 (vendor)
- d 00002770 (device)
- sv 00001028 (subvendor)
- sd 000001AD (subdevice)
- bc 06 (bus class)
- sc 00 (bus subclass)
- i 00 (interface)
-
-
-
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).
-
-
Not sure how to figure out the interface value, nor what it
-means.
-
-
USB subtype
-
-
Some typical USB entries can look like this. This is an internal
-USB hub in a laptop:
-
-
-usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
-
-
-
Here is the values included in this alias:
-
-
- v 1D6B (device vendor)
- p 0001 (device product)
- d 0206 (bcddevice)
- dc 09 (device class)
- dsc 00 (device subclass)
- dp 00 (device protocol)
- ic 09 (interface class)
- isc 00 (interface subclass)
- ip 00 (interface protocol)
-
-
-
The 0900 device class/subclass means hub. Some times the relevant
-class is in the interface class section. For a simple USB web camera,
-these alias entries show up:
-
-
-usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
-
usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
-
usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
-
usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
-
-
-
Interface class 0E01 is video control, 0E02 is video streaming (aka
-camera), 0101 is audio control device and 0102 is audio streaming (aka
-microphone). Thus this is a camera with microphone included.
-
-
ACPI subtype
-
-
The ACPI type is used for several non-PCI/USB stuff. This is an IR
-receiver in a Thinkpad X40:
-
-
-acpi:IBM0071:PNP0511:
-
-
-
The values between the colons are IDs.
-
-
DMI subtype
-
-
The DMI table contain lots of information about the computer case
-and model. This is an entry for a IBM Thinkpad X40, fetched from
-/sys/devices/virtual/dmi/id/modalias:
-
-
-dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
-
-
-
The values present are
-
-
- bvn IBM (BIOS vendor)
- bvr 1UETB6WW(1.66) (BIOS version)
- bd 06/15/2005 (BIOS date)
- svn IBM (system vendor)
- pn 2371H4G (product name)
- pvr ThinkPadX40 (product version)
- rvn IBM (board vendor)
- rn 2371H4G (board name)
- rvr NotAvailable (board version)
- cvn IBM (chassis vendor)
- ct 10 (chassis type)
- cvr NotAvailable (chassis version)
-
-
-
The chassis type 10 is Notebook. Other interesting values can be
-found in the dmidecode source:
-
-
- 3 Desktop
- 4 Low Profile Desktop
- 5 Pizza Box
- 6 Mini Tower
- 7 Tower
- 8 Portable
- 9 Laptop
- 10 Notebook
- 11 Hand Held
- 12 Docking Station
- 13 All In One
- 14 Sub Notebook
- 15 Space-saving
- 16 Lunch Box
- 17 Main Server Chassis
- 18 Expansion Chassis
- 19 Sub Chassis
- 20 Bus Expansion Chassis
- 21 Peripheral Chassis
- 22 RAID Chassis
- 23 Rack Mount Chassis
- 24 Sealed-case PC
- 25 Multi-system
- 26 CompactPCI
- 27 AdvancedTCA
- 28 Blade
- 29 Blade Enclosing
-
-
-
The chassis type values are not always accurately set in the DMI
-table. For example my home server is a tower, but the DMI modalias
-claim it is a desktop.
-
-
SerIO subtype
-
-
This type is used for PS/2 mouse plugs. One example is from my
-test machine:
-
-
-serio:ty01pr00id00ex00
-
-
-
The values present are
-
-
- ty 01 (type)
- pr 00 (prototype)
- id 00 (id)
- ex 00 (extra)
-
-
-
This type is supported by the psmouse driver. I am not sure what
-the valid values are.
-
-
Other subtypes
-
-
There are heaps of other modalias subtypes according to
-file2alias.c. There is the rest of the list from that source: amba,
-ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
-mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
-vmbus, x86cpu and zorro. I did not spend time documenting all of
-these, as they do not seem relevant for my intended use with mapping
-hardware to packages when new stuff is inserted during run time.
-
-
Looking up kernel modules using modalias values
-
-
To check which kernel modules provide support for a given modalias,
-one can use the following shell script:
-
-
- for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
- echo "$id" ; \
- /sbin/modprobe --show-depends "$id"|sed 's/^/ /' ; \
- done
-
-
-
The output can look like this (only the first few entries as the
-list is very long on my test machine):
-
-
- acpi:ACPI0003:
- insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
- acpi:device:
- FATAL: Module acpi:device: not found.
- acpi:IBM0068:
- insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
- insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
- insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
- insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
- acpi:IBM0071:PNP0511:
- insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
- insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
- insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
- [...]
-
-
-
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
-#debian-devel.
-
-
Update 2013-01-15: Rewrite "cat $(find ...)" to
-"find ... -print0 | xargs -0 cat" to make sure it handle directories
-in /sys/ with space in them.
+
+
3rd July 2013
+
The fourth wheezy based alpha release of Debian Edu was wrapped up
+today. This is the release announcement:
+
+
New features for Debian Edu 7.1+edu0~alpha3 released
+2013-07-03
+
+
These are the release notes for for Debian Edu / Skolelinux
+7.1+edu0~alpha3, based on Debian with codename "Wheezy".
+
+
About Debian Edu and Skolelinux
+
+
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. Immediately 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. The provided school server provides LDAP
+database and Kerberos authentication service, centralized home
+directories, DHCP server, web proxy and many other services. The
+desktop contains
+more
+than 60 educational software packages and more are available from
+the Debian archive, and schools can choose between KDE, Gnome, LXDE
+and Xfce desktop environment.
+
+
This is the fourth test release based on Debian Wheezy. Basically
+this is an updated and slightly improved version compared to the
+Squeeze release.
+
+
Software updates
+
+ - Dropped ispell dictionaries from our default installation.
+ - Dropped menu-xdg from the KDE desktop option, to drop the Debian
+ submenu. It was not included with Gnome, LXDE or Xfce, so this
+ brings KDE in line with the others.
+ - Dropped xdrawchem, xjig and xsok from our default installation as
+ they don't have a desktop menu entry and thus won't show up in the
+ menu now that menu-xdg was removed.
+ - Removed the killer system to kill left behind processes on
+ multi-user machines, as it was no longer able to understand when a
+ X display was in use and killed the processes of the active users
+ too.
+ - Dropped the golearn (from goplay) package as the debtags in wheezy
+ are too few to make the package useful.
+
+
Other changes
+
+ - Updated artwork matching http://wiki.debian.org/DebianArt/Themes/Joy
+
- Multi-arch i386/amd64 USB stick ISO available.
+ - Got rid of ispell/wordlist related debconf questions that showed
+ up for some language options.
+ - Switched to using http.debian.net as APT source by default.
+ - Fixed proxy configuration on Main Server installations.
+ - Changed LTSP setup to ask dpkg to use force-unsafe-io the same way
+ d-i is doing it.
+ - Made sure root and user passwords were not left behind in the
+ debconf database after installation on Main Server installations.
+ - Made Roaming Workstation dynamic setup more robust and added draft
+ script setup-ad-client to hook a Roaming Workstation up to a
+ Active Directory server instead of a Debian Edu Main Server.
+ - Update system to install needed firmware packages during
+ installation, to work properly in Wheezy.
+ - Update system to handle hardware quirks (debian-edu-hwsetup).
+ - Corrected PXE installation setup to properly pass selected desktop
+ and keymap settings to PXE installation clients.
+ - LTSP diskless workstations use sshfs by default, allowing them to
+ work without adding them to DNS and NIS netgroups for NFS access.
+
+
Known issues
+
+ - No mass import of user account data in GOsa (ldif or csv)
+ available yet (698840).
+ - Artwork not enabled for all desktops.
+
+
Where to get it
+
+
To download the multiarch netinstall CD release you can use
+
+
+
The MD5SUM of this image is: 2b161a99d2a848c376d8d04e3854e30c
+
The SHA1SUM of this image is: 498922e9c508c0a7ee9dbe1dfe5bf830d779c3c8
+
+
To download the multiarch USB stick ISO release you can use
+
+
+
The MD5SUM of this image is: 25e808e403a4c15dbef1d13c37d572ac
+
The SHA1SUM of this image is: 15ecfc93eb6b4f453b7eb0bc04b6a279262d9721
+
+
How to report bugs
+
+
http://wiki.debian.org/DebianEdu/HowTo/ReportBugs
@@ -783,31 +589,70 @@ in /sys/ with space in them.
-
-
10th January 2013
-
As part of my investigation on how to improve the support in Debian
-for hardware dongles, I dug up my old Mark and Spencer USB Rocket
-Launcher and updated the Debian package
-pymissile to make
-sure udev will fix the device permissions when it is plugged in. I
-also added a "Modaliases" header to test it in the Debian archive and
-hopefully make the package be proposed by jockey in Ubuntu when a user
-plug in his rocket launcher. In the process I moved the source to a
-git repository under collab-maint, to make it easier for any DD to
-contribute. Upstream
-is not very active, but the software still work for me even after five
-years of relative silence. The new git repository is not listed in
-the uploaded package yet, because I want to test the other changes a
-bit more before I upload the new version. If you want to check out
-the new version with a .desktop file included, visit the
-gitweb
-view or use "git clone
-git://anonscm.debian.org/collab-maint/pymissile.git".
+
+
25th June 2013
+
It annoys me when the computer fail to do automatically what it is
+perfectly capable of, and I have to do it manually to get things
+working. One such task is to find out what firmware packages are
+needed to get the hardware on my computer working. Most often this
+affect the wifi card, but some times it even affect the RAID
+controller or the ethernet card. Today I pushed version 0.4 of the
+Isenkram package
+including a new script isenkram-autoinstall-firmware handling the
+process of asking all the loaded kernel modules what firmware files
+they want, find debian packages providing these files and install the
+debian packages. Here is a test run on my laptop:
+
+
+# isenkram-autoinstall-firmware
+info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
+info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
+info: locating packages with the requested firmware files
+info: Updating APT sources after adding non-free APT source
+info: trying to install firmware-ipw2x00
+firmware-ipw2x00
+firmware-ipw2x00
+Preconfiguring packages ...
+Selecting previously deselected package firmware-ipw2x00.
+(Reading database ... 259727 files and directories currently installed.)
+Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
+Setting up firmware-ipw2x00 (0.28+squeeze1) ...
+#
+
+
+
When all the requested firmware is present, a simple message is
+printed instead:
+
+
+# isenkram-autoinstall-firmware
+info: did not find any firmware files requested by loaded kernel modules. exiting
+#
+
+
+
It could use some polish, but it is already working well and saving
+me some time when setting up new machines. :)
+
+
So, how does it work? It look at the set of currently loaded
+kernel modules, and look up each one of them using modinfo, to find
+the firmware files listed in the module meta-information. Next, it
+download the Contents file from a nearby APT mirror, and search for
+the firmware files in this file to locate the package with the
+requested firmware file. If the package is in the non-free section, a
+non-free APT source is added and the package is installed using
+apt-get install. The end result is a slightly better working
+machine.
+
+
I hope someone find time to implement a more polished version of
+this script as part of the hw-detect debian-installer module, to
+finally fix BTS report
+#655507. There really is no need to insert USB sticks with
+firmware during a PXE install when the packages already are available
+from the nearby Debian mirror.
@@ -815,98 +660,50 @@ git://anonscm.debian.org/collab-maint/pymissile.git".
-
-
9th January 2013
-
One thing that annoys me with Debian and Linux distributions in
-general, is that there is a great package management system with the
-ability to automatically install software packages by downloading them
-from the distribution mirrors, but no way to get it to automatically
-install the packages I need to use the hardware I plug into my
-machine. Even if the package to use it is easily available from the
-Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
-suggest to automatically install the python-nxt, nbc and t2n packages
-I need to talk to it. When I plug in a Yubikey, it could propose the
-yubikey-personalization package. The information required to do this
-is available, but no-one have pulled all the pieces together.
-
-
Some years ago, I proposed to
-use
-the discover subsystem to implement this. The idea is fairly
-simple:
-
-
-
-- Add a desktop entry in /usr/share/autostart/ pointing to a program
- starting when a user log in.
-
-- Set this program up to listen for kernel events emitted when new
- hardware is inserted into the computer.
-
-- When new hardware is inserted, look up the hardware ID in a
- database mapping to packages, and take note of any non-installed
- packages.
-
-- Show a message to the user proposing to install the discovered
- package, and make it easy to install it.
-
-
-
-
I am not sure what the best way to implement this is, but my
-initial idea was to use dbus events to discover new hardware, the
-discover database to find packages and
-PackageKit to install
-packages.
-
-
Yesterday, I found time to try to implement this idea, and the
-draft package is now checked into
-the
-Debian Edu subversion repository. In the process, I updated the
-discover-data
-package to map the USB ids of LEGO Mindstorms and Yubikey devices to
-the relevant packages in Debian, and uploaded a new version
-2.2013.01.09 to unstable. I also discovered that the current
-discover
-package in Debian no longer discovered any USB devices, because
-/proc/bus/usb/devices is no longer present. I ported it to use
-libusb as a fall back option to get it working. The fixed package
-version 2.1.2-6 is now in experimental (didn't upload it to unstable
-because of the freeze).
-
-
With this prototype in place, I can insert my Yubikey, and get this
-desktop notification to show up (only once, the first time it is
-inserted):
-
-

-
-
For this prototype to be really useful, some way to automatically
-install the proposed packages by pressing the "Please install
-program(s)" button should to be implemented.
-
-
If this idea seem useful to you, and you want to help make it
-happen, please help me update the discover-data database with mappings
-from hardware to Debian packages. Check if 'discover-pkginstall -l'
-list the package you would like to have installed when a given
-hardware device is inserted into your computer, and report bugs using
-reportbug if it isn't. Or, if you know of a better way to provide
-such mapping, please let me know.
-
-
This prototype need more work, and there are several questions that
-should be considered before it is ready for production use. Is dbus
-the correct way to detect new hardware? At the moment I look for HAL
-dbus events on the system bus, because that is the events I could see
-on my Debian Squeeze KDE desktop. Are there better events to use?
-How should the user be notified? Is the desktop notification
-mechanism the best option, or should the background daemon raise a
-popup instead? How should packages be installed? When should they
-not be installed?
-
-
If you want to help getting such feature implemented in Debian,
-please send me an email. :)
+
+
22nd June 2013
+
In the Debian Edu /
+Skolelinux project, we include a post-installation test suite,
+which check that services are running, working, and return the
+expected results. It runs automatically just after the first boot on
+test installations (using test ISOs), but not on production
+installations (using non-test ISOs). It test that the LDAP service is
+operating, Kerberos is responding, DNS is replying, file systems are
+online resizable, etc, etc. And it check that the PXE service is
+configured, which is the topic of this post.
+
+
The last week I've fixed the DVD and USB stick ISOs for our Debian
+Edu Wheezy release. These ISOs are supposed to be able to install a
+complete system without any Internet connection, but for that to
+happen all the needed packages need to be on them. Thanks to our test
+suite, I discovered that we had forgotten to adjust our PXE setup to
+cope with the new names and paths used by the netboot d-i packages.
+When Internet connectivity was available, the installer fall back to
+using wget to fetch d-i boot images, but when offline it require
+working packages to get it working. And the packages changed name
+from debian-installer-6.0-netboot-$arch to
+debian-installer-7.0-netboot-$arch, we no longer pulled in the
+packages during installation. Without our test suite, I suspect we
+would never have discovered this before release. Now it is fixed
+right after we got the ISOs operational.
+
+
Another by-product of the test suite is that we can ask system
+administrators with problems getting Debian Edu to work, to run the
+test suite using /usr/sbin/debian-edu-test-install and see if
+any errors are detected. This usually pinpoint the subsystem causing
+the problem.
+
+
If you want to help us help kids learn how to share and create,
+please join us on
+#debian-edu on
+irc.debian.org and the
+debian-edu@ mailing
+list.
@@ -914,27 +711,143 @@ please send me an email. :)
-
-
2nd January 2013
-
During Christmas, I have worked a bit on the Debian support for
-LEGO Mindstorm
-NXT. My son and I have played a bit with my NXT set, and I
-discovered I had to build all the tools myself because none were
-already in Debian Squeeze. If Debian support for LEGO is something
-you care about, please join me on the IRC channel
-#debian-lego (server
-irc.debian.org). There is a lot that could be done to improve the
-Debian support for LEGO designers. For example both CAD software
-and Mindstorm compilers are missing. :)
-
-
Update 2012-01-03: A
-project page
-including links to Lego related packages is now available.
+
+
17th June 2013
+
The Debian Edu and
+Skolelinux distribution have users and contributors all around the
+globe. And a while back, an enterprising young man showed up on
+our IRC channel
+#debian-edu and started asking questions about how Debian Edu
+worked. We answered as good as we could, and even convinced him to
+help us with translations. And today I managed to get an interview
+with him, to learn more about him.
+
+
Who are you, and how do you spend your days?
+
+
I'm a 25 year old free software enthusiast, living in Romania,
+which is also my country of origin. Back in 2009, at a New Year's Eve
+party, I had a very nice beer discussion with a
+friend, when we realized we have no organised Debian community in our
+country. A few days later, we put together the infrastructure for such
+community and even gathered a nice Debian-ish crowd. Since then, I
+began my quest as a free software hacker and activist and I am
+constantly trying to cover as much ground as possible on that
+field.
+
+
A few years ago I founded a small web development company, which
+provided me the flexible schedule I needed so much for my
+activities. For the last 13 months, I have been the Technical Director
+of FundaÈia Ceata, which is a free
+software activist organisation endorsed by the FSF and the FSFE, and
+the only one we have in our country.
+
+
How did you get in contact with the Skolelinux / Debian Edu
+project?
+
+
The idea of participating in the Debian Edu project was a surprise
+even to me, since I never used it before I began getting involved in
+it. This year I had a great opportunity to deliver a talk on
+educational software, and I knew immediately where to look. It was a
+love at first sight, since I was previously involved with some of the
+technologies the project incorporates, and I rapidly found a lot of
+ways to contribute.
+
+
My first contributions consisted in translating the installer and
+configuration dialogs, then I found some bugs to squash (I still
+haven't fixed them yet though), and I even got my eyes on some other
+areas where I can prove myself helpful. Since the appetite for free
+software in my country is pretty low, I'll be happy to be the first
+one around here advocating for the project's adoption in educational
+environments, and maybe even get my hands dirty in creating a flavour
+for our own needs. I am not used to make very advanced plannings, so
+from now on, time will tell what I'll be doing next, but I think I
+have a pretty consistent starting point.
+
+
What do you see as the advantages of Skolelinux/Debian
+Edu?
+
+
Not a long time ago, I was in the position of configuring and
+maintaining a LDAP server on some Debian derivative, and I must say it
+took me a while. A long time ago, I was maintaining a bigger
+Samba-powered infrastructure, and I must say I spent quite a lot of
+time on it. I have similar stories about many of the services included
+with Skolelinux, and the main advantage I see about it is the
+out-of-the box availability of them, making it quite competitive when
+it comes to managing a school's network, for example.
+
+
Of course, there is more to say about Skolelinux than the
+availability of the software included, its flexibility in various
+scenarios is something I can't wait to experiment "into the wild" (I
+only played with virtual machines so far). And I am sure there is a
+lot more I haven't discovered yet about it, being so new within the
+project.
+
+
What do you see as the disadvantages of Skolelinux / Debian
+Edu?
+
+
As usual, when it comes to Debian Blends, I see as the biggest
+disadvantage the lack of a numerous team dedicated to the
+project. Every day I see the same names in the changelogs, and I have
+a constantly fear of the bus factor in this story. I'd like to see
+Debian Edu advertised more as an entry point into the Debian
+ecosystem, especially amongst newcomers and students. IMHO there are a
+lot low-hanging fruits in terms of bug squashing, and enough
+opportunities to get the feeling of the Debian Project's dynamics. Not
+to mention it's a very fun blend to work on!
+
+
Derived from the previous statement, is the delay in catching up
+with the main Debian release and documentation. This is common though
+to all blends and derivatives, but it's an issue we can all work
+on.
+
+
Which free software do you use daily?
+
+
I can hardly imagine myself spending a day without Vim, since my
+daily routine covers writing code and hacking configuration files. I
+am a fan of the Awesome window manager (but I also like the
+Enlightenment project a lot!),
+Claws Mail due to its ease of
+use and very configurable behaviour. Recently I fell in love with
+Redshift, which helps me
+get through the night without headaches. Of course, there is much more
+stuff in this bag, but I'll need a blog on my own for doing this!
+
+
Which strategy do you believe is the right one to use to
+get schools to use free software?
+
+
Well, on this field, I cannot do much more than experiment right
+now. So, being far from having a recipe for success, I can only assume
+that:
+
+
+
+- schools would like to get rid of proprietary software
+
+- students will love the openness of the system, and will want to
+ experiment with it - maybe we need to harvest the native curiosity
+ of teenagers more?
+
+- there is no "right one" when it comes to strategies, but it would
+ be useful to have some success stories published somewhere, so
+ other can get some inspiration from them (I know I'd promote
+ them!)
+
+- more active promotion - talks, conferences, even small school
+ lectures can do magical things if they encounter at least one
+ person interested. Who knows who that person might be? ;-)
+
+
+
+
I also see some problems in getting Skolelinux into schools; for
+example, in our country we have a great deal of corruption issues, so
+it might be hard(er) to fight against proprietary solutions. Also,
+people who relied on commercial software for all their lives, would be
+very hard to convert against their will.
@@ -954,6 +867,18 @@ including links to Lego related packages is now available.
January (11)
+
February (9)
+
+
March (9)
+
+
April (6)
+
+
May (9)
+
+
June (10)
+
+
July (7)
+
2012
@@ -1096,35 +1021,37 @@ including links to Lego related packages is now available.
bankid (4)
-
bitcoin (5)
+
bitcoin (7)
bootsystem (12)
bsa (2)
-
debian (69)
+
debian (83)
-
debian edu (118)
+
debian edu (138)
-
digistan (9)
+
digistan (10)
-
docbook (7)
+
docbook (9)
drivstoffpriser (4)
-
english (175)
+
english (210)
fiksgatami (21)
fildeling (12)
-
freeculture (10)
+
freeculture (11)
+
+
frikanalen (11)
-
frikanalen (9)
+
intervju (37)
-
intervju (32)
+
isenkram (7)
-
kart (17)
+
kart (18)
ldap (8)
@@ -1134,17 +1061,17 @@ including links to Lego related packages is now available.
multimedia (25)
-
norsk (219)
+
norsk (234)
-
nuug (148)
+
nuug (153)
-
offentlig innsyn (6)
+
offentlig innsyn (8)
open311 (2)
-
opphavsrett (41)
+
opphavsrett (44)
-
personvern (61)
+
personvern (65)
raid (1)
@@ -1152,7 +1079,7 @@ including links to Lego related packages is now available.
rfid (2)
-
robot (6)
+
robot (7)
rss (1)
@@ -1160,25 +1087,25 @@ including links to Lego related packages is now available.
scraperwiki (2)
-
sikkerhet (28)
+
sikkerhet (29)
sitesummary (4)
skepsis (4)
-
standard (39)
+
standard (43)
stavekontroll (3)
-
stortinget (5)
+
stortinget (7)
-
surveillance (12)
+
surveillance (15)
sysadmin (1)
valg (7)
-
video (35)
+
video (38)
vitenskap (4)
@@ -1189,7 +1116,7 @@ including links to Lego related packages is now available.
- Created by Chronicle v4.4
+ Created by Chronicle v4.6