X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/1f2bc92825446ab1c0dd9bca946b59da5ed2e4ed..3c926f36060a6457b3f2a24aa964a0b616b61f4e:/blog/index.html diff --git a/blog/index.html b/blog/index.html index 5efa44b5d6..4b84bf7bae 100644 --- a/blog/index.html +++ b/blog/index.html @@ -20,41 +20,47 @@
-
Vitenskaplig metode i politikken?
-
20th September 2012
-

Jeg ble for noen dager siden tipset om en rapport utarbeidet av -Cabinet Office i England ved navn -Test, -Learn, Adapt: Developing Public Policy with Randomised Controlled -Trials, skrevet av blant annet Ben Goldacre (som jeg først ble -klar over da han holdt et veldig interessant TED-foredrag med tittel -Battling bad -science). Rapporten handler om hvordan det offentlige burde bruke -vitenskaplige metoder i større grad for å finne ut hvilke virkemidler -som er mest effektive når en skal regulere samfunnet. Her er et sitat -fra starten av rapporten:

- -
-

Randomised controlled trials (RCTs) are the best way to determine - wheather a policy is working. They are now used extensively in - international development, medicine, and business to identify which - policy, drug or sales method is most effective. They are also at - the heart of the Behavioural Insights Team's methodology.

- -

However, RCTs are not rutinely used to test the effectiveness of - public policy interventions in the UK. We think they should be.

-
- -

Her tror jeg også Norge har noe å lære. Det offentlige bruker mye -penger på aktiviteter der det ikke er åpenbart (og heller ikke blir -målt) at den reelle effekten er det en ønsker å oppnå. Ruters -elektroniske billettsystem, NAV-reformen, økt bruk av penger på -politiet og sykehussammenslåinger kommer meg i hug.

+ +
4th February 2013
+

Jeg ser med gru at Arbeiderpartiet, Høyre og Fremskrittspartiet +applauderer +tollvesenets forslag om å øke overvåkningen i Norge nok et hakk. +Det er ikke så rart, da de som uttaler seg jo også har støttet +innføringen av datalagringsdirektivet eller i hvert fall ikke veldig +aktivt har motarbeidet det. Innføringen av datalagringsdirektivet er +en lovendring som innebærer brev og besøkskontroll for hele +befolkningen.

+ +

Datalagringsdirektivet +har vært oppe til votering i stortinget tre ganger så langt. Det ble +vedtatt første gang 2011-04-04 +og +andre +gang 2011-04-11 (lovendringer voteres to ganger), og forslag om å +stoppe loven ble +nedstemt +2012-12-06 (se også +oversikt fra Holder De +Ord).

+ +

Jan Bøhler i Arbeiderpartiet stemte for å innføre +datalagringsdirektivet i lovverket i første votering, var ikke +tilstede i andre votering og støttet loven i tredje votering. André +Oktay Dahl i Høyre var ikke til stede i første og andre votering men +støttet loven i tredje votering. Ulf Leirstein i Fremskrittspartiet +stemte mot loven i første votering men var ikke til stede i andre og +tredje votering.

+ +

Hvis du lurer på hva som er problemet med datalagringsdirektivet, +anbefaler jeg å lese artiklene +fra Jon Wessel-Aas om temaet, samt informasjon fra foreningen +Digitalt +Personvern.

@@ -62,105 +68,40 @@ politiet og sykehussammenslåinger kommer meg i hug.

- -
17th September 2012
-

After a long break in my row of interviews with people in the -Debian Edu and Skolelinux -community, I finally found time to wrap up another. This time it is -Giorgio Pioda, which showed up on the mailing list at the start of -this year, asking questions and inspiring us to improve the first time -administrators experience with Skolelinux. :) The interview was -conduced in May, but I only found time to publish it now.

- -

Who are you, and how do you spend your days?

- -

I have a PhD in chemistry but since several years I work as teacher -in secondary (15-18 year old students) and tertiary (a kind of "light" -university) schools. Five years ago I started to manage a Learning -Management Service server and slowly I got more and more involved with -IT. 3 years ago the graduating schools moved completely to Linux and I -got the head of the IT for this. The experience collected in chemistry -labs computers (for example NMR analysis of protein folding) and in -the IT-courses during university where sufficient to start. Self -training is anyway very important

- -

I live in the Italian speaking part of Switzerland, and the -SPSE school (secondary) is a very -special sport school for young people who try to became sport pro (for -all sports, we have dozens of disciplines represented) and we are -recognised by the Olympic Swiss Organisation. - -

How did you get in contact with the Skolelinux/Debian Edu -project?

- -

Looking for Linux / Primary Domain Controller (PDC) I found it -already several years ago. But since the system was still not -Kerberized and since our schools relies strongly on laptops I didn't -use it. I plan to introduce it in the next future, probably for the -next school year, since the squeeze release solved this security -hole.

- -

What do you see as the advantages of Skolelinux/Debian -Edu?

- -

Many. First of all there is a strong and living community that is -very generous for help and hints. Chat help is crucial, together with -the mailing list. Second. With Skolelinux you get an already well -engineered platform and you don't have to start to build up your PDC -and your clients from GNU/scratch; I've already done this once and I -can tell it, it is hard. Third, since Skolelinux is a standard -platform, it is way easier to educate other IT people and even if the -head IT is sick another one could pick up the task without too much -hassle.

- -

What do you see as the disadvantages of Skolelinux/Debian -Edu?

- -

The only real problem I see is that it is a little too less -flexible at client level. Debian stable is rocky and desirable, but -there are many reasons that force for another choice. For example the -need of new drivers for new PC, or the need for a specific OS for some -devices that have specific software packages for another specific -distribution (I have such a case for whiteboards that have only -Ubuntu packages). Thus, I prepared compatibility packages educlient -and eduroaming, hoping not to use them ;-)

- -

Which free software do you use daily?

- -

I have a Debian Stable PDC at school (Kerberos, NIS, NFS) with -mixed Debian and Ubuntu clients. If you think that this triad -combination is exotic... well I discovered right yesterday that -Perceus -has the same...

- -

For myself I run Debian wheezy/sid, but this combination is good -only I you have enough competence to fix stuff for yourself, if -something breaks. Daily I use texmacs, gnumeric, a little bit of R -statistics, kmplot, and less frequently OpenOffice.org.

- -

Which strategy do you believe is the right one to use to -get schools to use free software?

- -

I think that the only real argument that school managers "hear" is -cost reduction. They don't give too much weight on quality, stability, -just because they are normally not open to change.

- -

Students adapts very quickly to GNU/Linux (and for them being able -to switch between different OS is a plus value); teachers and managers -don't.

- -

We decided to move to Linux because students at our school have own -laptop and we have the responsibility to keep the laptop ready to use; -we were really unsatisfied with Microsoft since every Monday we had 20 -machine to fix for viral infections... With Linux this has been -reduced to zero, since people installs almost only from official -repositories. I think that our special needs brought us to Linux. -Those who don't have such needs will hardly move to Linux.

+ +
2nd February 2013
+

My +last +bitcoin related blog post mentioned that the new +bitcoin package for +Debian was waiting in NEW. It was accepted by the Debian ftp-masters +2013-01-19, and have been available in unstable since then. It was +automatically copied to Ubuntu, and is available in their Raring +version too.

+ +

But there is a strange problem with the build that block this new +version from being available on the i386 and kfreebsd-i386 +architectures. For some strange reason, the autobuilders in Debian +for these architectures fail to run the test suite on these +architectures (BTS #672524). +We are so far unable to reproduce it when building it manually, and +no-one have been able to propose a fix. If you got an idea what is +failing, please let us know via the BTS.

+ +

One feature that is annoying me with of the bitcoin client, because +I often run low on disk space, is the fact that the client will exit +if it run short on space (BTS +#696715). So make sure you have enough disk space when you run +it. :)

+ +

As usual, if you use bitcoin and want to show your support of my +activities, please send Bitcoin donations to my address +15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b.

@@ -168,29 +109,50 @@ Those who don't have such needs will hardly move to Linux.

- -
16th September 2012
-

Veldig morsomt å se at -Naturvernforbundet Oslo og -Akershus bruker kart fra -OpenStreetmap.org i -sine -kalendere. Vidar Gundersen i kartgruppa -forteller -på den norske epostlisten til prosjektet at hvert blad i -kalenderen har et turforslag på baksiden, med kart fra OpenStreetmap. -Tidligere kjøpte de visst kart fra kartverket, men nå slipper de -det.

- -

Denne nyheten synes jeg er fantastisk bra, og jeg håper de får -følge av flere, slik at det potensielle og fryktede inntektstapet for -kartverket ved frigjøring av kartdata blir mindre, og forhåpentligvis -til slutt så lite at frykten for å frigjøre data overvinnes.

+ +
22nd January 2013
+

Yesterday, I +asked +for testers for my prototype for making Debian better at handling +pluggable hardware devices, which I +set +out to create earlier this month. Several valuable testers showed +up, and caused me to really want to to open up the development to more +people. But before I did this, I want to come up with a sensible name +for this project. Today I finally decided on a new name, and I have +renamed the project from hw-support-handler to this new name. In the +process, I moved the source to git and made it available as a +collab-maint +repository in Debian. The new name? It is Isenkram. +To fetch and build the latest version of the source, use

+ +
+git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
+cd isenkram && git-buildpackage -us -uc
+
+ +

I have not yet adjusted all files to use the new name yet. If you +want to hack on the source or improve the package, please go ahead. +But please talk to me first on IRC or via email before you do major +changes, to make sure we do not step on each others toes. :)

+ +

If you wonder what 'isenkram' is, it is a Norwegian word for iron +stuff, typically meaning tools, nails, screws, etc. Typical hardware +stuff, in other words. I've been told it is the Norwegian variant of +the German word eisenkram, for those that are familiar with that +word.

+ +

Update 2013-01-26: Added -us -us to build +instructions, to avoid confusing people with an error from the signing +process.

+ +

Update 2013-01-27: Switch to HTTP URL for the git +clone argument to avoid the need for authentication.

- Tags: kart, norsk. + Tags: debian, english, isenkram.
@@ -198,37 +160,84 @@ til slutt så lite at frykten for å frigjøre data overvinnes.

- -
15th September 2012
-

After the -Opus -codec made it into IETF as -RFC 6716, I had a look -to see if there is any activity in IETF to standardise a video codec -too, and I was happy to discover that there is some activity in this -area. A non-"working group" mailing list -video-codec -was -created 2012-08-20. It is intended to discuss the topic and if a -formal working group should be formed.

- -

I look forward to see how this plays out. There is already -an -email from someone in the MPEG group at ISO asking people to -participate in the ISO group. Given how ISO failed with OOXML and given -that it so far (as far as I can remember) only have produced -multimedia formats requiring royalty payments, I suspect -joining the ISO group would be a complete waste of time, but I am not -involved in any codec work and my opinion will not matter much.

- -

If one of my readers is involved with codec work, I hope she will -join this work to standardise a royalty free video codec within -IETF.

+ +
21st January 2013
+

Early this month I set out to try to +improve +the Debian support for pluggable hardware devices. Now my +prototype is working, and it is ready for a larger audience. To test +it, fetch the +source +from the Debian Edu subversion repository, build and install the +package. You might have to log out and in again activate the +autostart script.

+ +

The design is simple:

+ +
    + +
  • Add desktop entry in /usr/share/autostart/ causing a program +hw-support-handlerd to start when the user log in.
  • + +
  • This program listen for kernel events about new hardware (directly +from the kernel like udev does), not using HAL dbus events as I +initially did.
  • + +
  • When new hardware is inserted, look up the hardware modalias in +the APT database, a database +available +via HTTP and a database available as part of the package.
  • + +
  • If a package is mapped to the hardware in question, the package +isn't installed yet and this is the first time the hardware was +plugged in, show a desktop notification suggesting to install the +package or packages.
  • + +
  • If the user click on the 'install package now' button, ask +aptdaemon via the PackageKit API to install the requrired package.
  • + +
  • aptdaemon ask for root password or sudo password, and install the +package while showing progress information in a window.
  • + +
+ +

I still need to come up with a better name for the system. Here +are some screen shots showing the prototype in action. First the +notification, then the password request, and finally the request to +approve all the dependencies. Sorry for the Norwegian Bokmål GUI.

+ +

+
+
+
+

+ +

The prototype still need to be improved with longer timeouts, but +is already useful. The database of hardware to package mappings also +need more work. It is currently compatible with the Ubuntu way of +storing such information in the package control file, but could be +changed to use other formats instead or in addition to the current +method. I've dropped the use of discover for this mapping, as the +modalias approach is more flexible and easier to use on Linux as long +as the Linux kernel expose its modalias strings directly.

+ +

Update 2013-01-21 16:50: Due to popular demand, +here is the command required to check out and build the source: Use +'svn checkout +svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd +hw-support-handler; debuild'. If you lack debuild, install the +devscripts package.

+ +

Update 2013-01-23 12:00: The project is now +renamed to Isenkram and the source moved from the Debian Edu +subversion repository to a Debian collab-maint git repository. See +build +instructions for details.

@@ -236,33 +245,61 @@ IETF.

- -
12th September 2012
-

Yesterday, IETF announced the -publication of of -RFC 6716, the Definition -of the Opus Audio Codec, a low latency, variable bandwidth, codec -intended for both VoIP, film and music. This is the first time, as -far as I know, that IETF have standardized a multimedia codec. In -RFC 3533, IETF -standardized the OGG container format, and it has proven to be a great -royalty free container for audio, video and movies. I hope IETF will -continue to standardize more royalty free codeces, after ISO and MPEG -have proven incapable of securing everyone equal rights to publish -multimedia content on the Internet.

- -

IETF require two interoperating independent implementations to -ratify a standard, and have so far ensured to only standardize royalty -free specifications. Both are key factors to allow everyone (rich and -poor), to compete on equal terms on the Internet.

- -

Visit the Opus project page if -you want to learn more about the solution.

+ +
19th January 2013
+

This Christmas my trusty old laptop died. It died quietly and +suddenly in bed. With a quiet whimper, it went completely quiet and +black. The power button was no longer able to turn it on. It was a +IBM Thinkpad X41, and the best laptop I ever had. Better than both +Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the +Compaq I had before that. Now I need to find a replacement. To keep +going during Christmas, I moved the one year old SSD disk to my old +X40 where it fitted (only one I had left that could use it), but it is +not a durable solution. + +

My laptop needs are fairly modest. This is my wishlist from when I +got a new one more than 10 years ago. It still holds true.:)

+ +
    + +
  • Lightweight (around 1 kg) and small volume (preferably smaller + than A4).
  • +
  • Robust, it will be in my backpack every day.
  • +
  • Three button mouse and a mouse pin instead of touch pad.
  • +
  • Long battery life time. Preferable a week.
  • +
  • Internal WIFI network card.
  • +
  • Internal Twisted Pair network card.
  • +
  • Some USB slots (2-3 is plenty)
  • +
  • Good keyboard - similar to the Thinkpad.
  • +
  • Video resolution at least 1024x768, with size around 12" (A4 paper +size).
  • +
  • Hardware supported by Debian Stable, ie the default kernel and + X.org packages.
  • +
  • Quiet, preferably fan free (or at least not using the fan most of + the time). + +
+ +

You will notice that there are no RAM and CPU requirements in the +list. The reason is simply that the specifications on laptops the +last 10-15 years have been sufficient for my needs, and I have to look +at other features to choose my laptop. But are there still made as +robust laptops as my X41? The Thinkpad X60/X61 proved to be less +robust, and Thinkpads seem to be heading in the wrong direction since +Lenovo took over. But I've been told that X220 and X1 Carbon might +still be useful.

+ +

Perhaps I should rethink my needs, and look for a pad with an +external keyboard? I'll have to check the +Linux Laptops site for +well-supported laptops, or perhaps just buy one preinstalled from one +of the vendors listed on the Linux +Pre-loaded site.

@@ -270,296 +307,75 @@ you want to learn more about the solution.

- -
11th September 2012
-

I 2006 var forslaget om å gjennomføre politiske valg over Internet -ute på høring, og -NUUG -skrev en høringsuttalelse (som EFN endte opp med å støtte), som -fortsatt er like aktuell. Jeg ble minnet på om den da jeg leste et -innlegg i Bergens Tidende med tittelen -En dårlig idé -som poengterer hvor viktig det er å holde fast ved at vi skal ha -hemmelige valg i Norge, og at det nødvendigvis fører til at vi ikke -kan ha valg over Internet.

- -

Innlegget i BT forteller at det skal være et -seminar -om evalueringen av e-valgforsøket på Litteraturhuset i morgen -2012-09-12 9-11:45. Jeg hadde ikke fått med meg dette før nå, og -kommer meg nok dessverre ikke innom, men håper det møter mange som -fortsatt kan bidra til å få skutt ned e-valgsgalskapen.

- -

Det er lenge siden 2006, og jeg regner med at de fleste av mine -lesere har glemt eller ikke har lest høringsuttalelsen fra NUUG. Jeg -gjengir den derfor her i sin helhet.

- -
-

Høringsuttalelse fra NUUG og EFN om elektronisk -stemmegivning

- -

Petter Reinholdtsen -
Leder i foreningen NUUG -
2006-09-30

- -

Foreningene NUUG og EFN er glade for å ha blitt invitert til å -kommentere utredningen om elektronisk stemmegivning, og håper våre -innspill kan komme til nytte. Denne uttalelsen er ført i pennen av -NUUGs leder Petter Reinholdtsen med innspill fra Tore Audun Høie, Erik -Naggum og Håvard Fosseng.

- -

Når en vurderer elektronisk stemmegivning, så tror vi det er viktig -å ha prinsippene for gode valg i bakhodet. Vi har tatt utgangspunkt i -listen fra Cranor, L.F. og Cytron, R.K. i "Design and Implementation -of a Security-Conscious Electronic Polling System", som oppsummerer -hvilke egenskaper som er viktige:

- -
    - -
  • Nøyaktig - et system er nøyaktig hvis det ikke er mulig Ã¥ endre en -stemme, det ikke er mulig Ã¥ fjerne en gyldig stemme fra den endelige -opptellingen og det ikke er mulig for en ugyldig stemme Ã¥ bli talt med -i den endelige opptellingen. Fullstendig nøyaktige systemer sikrer at -den endelige opptellingen er perfekt, enten ved sikre at -unøyaktigheter ikke kan bli introdusert eller kan oppdages og -korrigert for. Delvis nøyaktige systemer kan oppdage men ikke -nødvendigvis korrigere unøyaktigheter.
  • - -
  • Demokratisk - et system er demokratisk hvis kun de som har lov til -Ã¥ stemme kan stemme, og det sikrer at hver av dem kun kan stemme en -gang.
  • - -
  • Hemmelig - et system er hemmelig hvis ingen, hverken de som -arrangerer valget eller noen andre kan knytte en stemmeseddel til den -som avga den, og ingen stemmegiver kan bevise at han eller hun stemte -pÃ¥ en bestemt mÃ¥te. Dette er spesielt viktig for Ã¥ hindre kjøp og salg -av stemmer og at personer kan tvinges til Ã¥ stemme pÃ¥ en bestemt -mÃ¥te.
  • - -
  • Etterprøvbart - et system er etterprøvbart hvis hvem som helst -uavhengig kan kontrollere at opptellingen er korrekt.
  • - -
- -

Et demokratisk valg må sikre at disse punktene er oppfylt. Det er -med den bakgrunn vi vurderer elektronisk stemmegivning.

- -

Nøyaktig opptelling kan kun oppnås hvis alle steg i -opptellingsprosessen kan kontrolleres og verifiseres. Det må ikke må -være mulig å fjerne eller endre avgitte stemmer, og heller ikke mulig -å legge inn flere stemmer enn det som faktisk er avgitt. Elektronisk -lagring av avgitte stemmer kan gjør det svært enkelt å endre på -avgitte stemmer uten at det er mulig å oppdage det i -ettertid. Elektronisk lagring vil også gjøre det mulig å lagre en -annen stemme enn det som er blitt avgitt, selv om det så korrekt ut -for den som avga stemmen. Vi mener derfor det er viktig at elektronisk -stemmegivning gjøres via papir eller tilsvarende, slik at de som -stemmer kan kontrollere at den stemmen de har avgitt er den som blir -talt opp. I Australia brukes det et system der de som stemmer gjør -sitt valg på en skjerm, og stemmen så skrives ut på en papirrull som -sjekkes av den som stemmer før papirrullen leses inn av -opptellingssystemet. En sikrer slik at hver enkelt stemme kan -kontrolleres på nytt.

- -

Etterprøvbarhet kan kun oppnås hvis hver enkelt stemmegiver kan -kontrollere hele systemet som brukes for stemmegivning. For at dette -skal være mulig er en nødvendig betingelse at en har innsyn i hvordan -systemene er satt sammen, og hvordan de brukes. Selv om de aller -fleste ikke selv vil kunne gjennomføre en slik kontroll, er det viktig -at flere uavhengige eksperter kan sjekke systemet. Velgerne bør kunne -velge hvilke eksperter de vil stole på. Dette forutsetter blant annet -tilgang til kildekoden og informasjon om hvordan de ulike delene av -det totale stemmegivingssystemet er koblet. Lukkede systemer der -kildekoden ikke er tilgjengelig og en ikke kan kontrollere systemene -som brukes under selve valgene, er sårbare for trojanere (programvare -som gjør noe annet og/eller mer enn det leverandøren sier den skal, -f.eks. endre sluttresulatet av en opptelling) og påvirkning fra -leverandøren. Det er påstander om slikt i USA på maskiner fra Diebold -og Siebel allerede. Det finnes i dag flere tilgjengelige fri -programvaresystemer for elektronisk stemmegiving og opptelling. Fri -programvare sikrer brukeren kontroll over datasystemene. Slike -systemer er tilgjengelig fra OpenSourceVoting og ACTs elektroniske -valgsystem som ble brukt i det australske parlamentvalget 2001 og -2004. For å sikre at det er mulig å gjennomføre omtellinger må hver -enkelt stemme lagres på ikke-elektronisk format (f.eks. papir), og et -slikt papirspor må sikres slik at de ikke kan endres i ettertid. - -

Vellykkede elektroniske valgsystemer

- -

I Venezuela fungerte avstemmingsmaskinene slik at de som stemte -markerte det de stemte på en skjerm, og valgene ble skrevet på en -papirrull som den som stemmer så de kunne sjekke for å kontrollere at -de valgene som ble gjort kom med på papirrullen. Deretter ble -voteringstallene sendt elektronisk fra hver maskin til tre uavhengige -opptellingsgrupper (hvorav en av dem var Carter-senteret), som talte -opp stemmene. Alle måtte være enige for å godkjenne resultatet. Hvis -det var avvik så kunne en gå helt ned på papirrull-nivå for å sjekke -resultatet. Det har dog blitt hevdet at oppbevaringen av papirrullene -ble overlatt til regimet, slik at kontrollmuligheten ble fjernet. Det -er likevel mulig å organisere seg slik at det blir vanskelig å -forfalske valgresultatet ved å bytte ut eller endre rullene.

- -

India har et elektronisk voteringssystem som ble tatt i bruk i -1989. Det består av to ulike enheter, en opptellingsenhet og en -avstemmingsenhet. Systemet sikrer hemmelig valg, er vanskelig å -påvirke, men mangler oppbevaring av hver enkelt stemme på et -ikke-elektronisk format, noe som gjør omtelling umulig.

- -

Mindre vellykkede elektroniske valgsystemer

- -

I USA finnes en rekke ulike leverandører av elektroniske -valgsystemer, og det er dokumentert svakheter med flere av -dem. F.eks. har forskerne Ariel J. Feldman, J. Alex Halderman, og -Edward W. Felten ved Universitetet i Princeton dokumentert hvordan -systemet fra Diebold kan manipuleres til gi uriktig -avstemmingsresultat. Det er også indikasjoner på at noen av systemene -kan påvirkes av leverandøren via telelinjer. Robert F. Kennedy Jr. har -nylig i en artikkel fortalt om flere avvik fra valget i 2004. Norge -bør unngå systemer som kan manipuleres slik det rapporteres om fra -USA.

- -

Universitetet i Oslo skal denne høsten gjennomføre elektronisk valg -på Dekan ved Det teologiske fakultet. Universitetsstyret har godkjent -et valgsystem der de som arrangerer valget har mulighet til å se hvem -som har stemt hva, samt hver deltager i valget kan endre sin stemme i -ettertid (ikke-hemmelig), de som administrerer datasystemet kan -påvirke valgresultatet ved å endre, trekke fra eller legge til stemmer -(ikke-nøyaktig), og det ikke nødvendigvis er mulig å oppdage at slik -påvirkning har funnet sted (ikke etterprøvbart). Webbaserte -valgsystemer uten spesiell klientprogramvare vil ha flere av disse -problemene.

- -

Konkrete kommentarer til rapporten

- -

Rapporten nevner ikke muligheten for å påvirke valgresultatet via -trojansk type kode. Siebel blir beskyldt for dette i USA. Vi advarer -mot bruk av lukket kildekode, fordi dette i prinsippet innebærer å -stole blindt på leverandøren. Det bør ikke vere begrenset hvem som kan -kontrollere at systemet gjør det det skal, og dette tilsier bruk av -fri programvare.

- -

Rapporten anbefaler lukket kode fordi kjeltringer kan finne ut -sikkerhetsmekanismene ved å lese kode. Det er ikke en god idé å basere -seg på at sikkerhetsmekanismene er beskyttet pga. at ingen kjenner til -hvordan de fungerer. Som eksempelet fra USA viser, kan man godt -mistenke leverandøren for å jukse med systemet. Selve det at en slik -mistanke eksisterer, og ikke kan fjernes/reduseres ved uavhengig -inspeksjon, er et problem for demokratiet. Et sikkert system må være -sikkert selv om noen med uærlige hensikter kjenner til hvordan det -fungerer. Australia har allerede gjennomført vellykkede valg basert på -et fri programvaresystem.

- -

Driften av totalsystemet blir ofret liten oppmerksomhet i -rapporten. I et driftopplegg ligger mange sikkerhetsutfordringer som -bør vurderes nøye.

- -

Definisjonen av brannmur i rapporten er feil, for eksempel sies at -"brannmuren er selv immun mot inntrengning". Dette er ikke riktig. Det -er fullt mulig å ha brannmurer med sikkerhetsproblemer som utnyttes -til å trenge inn i dem. I tillegg antar man at all trafikk går gjennom -brannmuren. I store applikasjoner, som et valgsystem vil være, kreves -et system av brannmurer og andre tiltak som vi kaller -sikkerhetsarkitektur. Rapporten burde komme inn på behovet for en -sikkerhetsarkitektur.. Selv med en gjennomarbeidet -sikkerhetsarkitektur kan det være at man overser muligheter for å -unngå brannmurene. Rapporten snakker om brannmur i entall, mens det -nok er nødvendig å sikre et valgsystem med flere lag av -sikringstiltak, og dermed vil være behov for flere brannmurer. En -brannmur kan være bygd basert på visse antagelser og standarder. En -annen brannmur kan bygge på et annet sett antagelser, og stoppe -trafikk som den første ikke tar høyde for. - -

Rapporten indikerer dårlige kunnskaper om brannmur, og dette igjen -antyder dårlige kunnskaper om datasikkerhet generelt, og dette bør -forbedres. For eksempel er driften ansvarlig for operativ -sikkerhetsarkitektur, og vi har hatt adskillige diskusjoner i NUUG om -hvor vanskelig dette er. Hva hjelper en brannmur hvis den er feil -konfigurert eller ikke oppdatert?

- -

Muligheten for sikkerhetsovervåkning kan vi ikke se er nevnt i -rapporten. Dette er vanskelig og dyrt, men bør vurderes for å kunne -oppdage systemavvik under valget. Sikkerhetsovervåkning kan inngå som -ledd i sikkerhetsarkitekturen.

- -

Det har blitt rapportert i pressen at USA ikke bør kjøpe -Lenovo-maskiner etter at selskapet som lager dem ble solgt fra IBM til -et kinesisk selskap. I Norge kan vi ikke trekke tingene like langt da -vi mangler nødvendig dataindustri, men vi bør satse på at -applikasjoner viktige for rikets sikkerhet i størst mulig utstrekning -kjører programvare der vi har innsyn i hvordan den er satt sammen. Det -er viktig at vi sikrer at programvare viktige for rikets sikkerhet kan -sjekkes/verifiseres av eksperter vi selv velger. Når det gjelder -valgsystemer må «vi» være velgerne, ikke bare myndighetsapparatet. I -tilfelle en ikke kan bruke fri programvare, bør en ivareta en sunn -kritisk sans med hensyn til hvorfra og av hvem vi kjøper. På grunn av -tendenser i USA til å i uheldig stor grad fokusere på -kontrollmekanismer som eksempelvis Echelon og Palladium kan det hevdes -at det hefter betenkeligheter ved innkjøp herfra.

- -

Referanser

- -
    - -
  • Cranor, L.F. og Cytron, R.K., "Design and Implementation of a -Security-Conscious Electronic Polling System" Washington University -Computer Science Technical Report WUCS-96-02. February 1996 -http://www.cs.wustl.edu/cs/techreports/1996/wucs-96-02.ps.Z
  • - -
  • Det australske valgsystemet, inkludert kildekoden tilgjengelig som -fri programvare http://www.elections.act.gov.au/Elecvote.html
  • - -
  • Smartmatics SAES voting system used in venesuela 2004 -http://www.smartmatic.com/solutions_03-1.htm
  • - -
  • Blackboxvoting, interessegruppe i USA med fokus pÃ¥ valgfusk -vha. elektroniske valgsystemer http://www.blackboxvoting.org/
  • - -
  • VerifiedVoting, interessegruppe i USA med fokus pÃ¥ at ogsÃ¥ -elektroniske valgsystemer mÃ¥ være -etterprøvbare. http://www.verifiedvoting.org/
  • - -
  • Blue Screen Democracy - fri programvareprosjekt som har utviklet -elektronisk stemmegivingssystem -http://bluescreen.sourceforge.net/
  • - -
  • Indias elektroniske avstemmingssystem (Wikipedia) -http://en.wikipedia.org/wiki/Indian_voting_machines
  • - -
  • Security Analysis of the Diebold AccuVote-TS Voting Machine av -Ariel J. Feldman, J. Alex Halderman, og Edward -W. Felten. http://itpolicy.princeton.edu/voting/ -http://coblitz.codeen.org:3125/itpolicy.princeton.edu/voting/videos/ts-voting.wmv
  • - -
  • Was the 2004 Election Stolen? av Robert F. Kennedy -Jr. http://www.rollingstone.com/news/story/10432334/was_the_2004_election_stolen
  • - -
  • Styreframlegg om elektronisk votering ved -UiO. http://www.admin.uio.no/kollegiet/moter/kart_prot2006/5/protokoll.xml -http://www.admin.uio.no/kollegiet/moter/kart_prot2006/5/vsak-14.pdf -http://www.admin.uio.no/kollegiet/moter/kart_prot2006/5/vsak-14-vedlegg.pdf
  • - -
  • Elektroniske valg - muligheter, problemer og noen løsninger -Semesteroppgave i STV620 - Demokratiske valg -http://www.afin.uio.no/forskning/notater/4_01.html
  • - -
  • NUUG - Norwegian Unix User Group http://www.nuug.no/
  • - -
  • EFN - Elektronisk forpost Norge http://www.efn.no/
  • - -
-
- -

Som alltid med valg er det ikke viktigst hva folk stemmer på, men -hvem som teller opp stemmene... Hvis du er interessert i temaet -e-valg, så har NUUG siden 2006 oppdatert -NUUGs -wikiside om høringen med aktuelle og interessante referanser og -artikler. Ta en titt der hvis du vil lese mer. :)

+ +
18th January 2013
+

Some times I try to figure out which Iceweasel browser plugin to +install to get support for a given MIME type. Thanks to +specifications +done by Ubuntu and Mozilla, it is possible to do this in Debian. +Unfortunately, not very many packages provide the needed meta +information, Anyway, here is a small script to look up all browser +plugin packages announcing ther MIME support using this specification:

+ +
+#!/usr/bin/python
+import sys
+import apt
+def pkgs_handling_mimetype(mimetype):
+    cache = apt.Cache()
+    cache.open(None)
+    thepkgs = []
+    for pkg in cache:
+        version = pkg.candidate
+        if version is None:
+            version = pkg.installed
+        if version is None:
+            continue
+        record = version.record
+        if not record.has_key('Npp-MimeType'):
+            continue
+        mime_types = record['Npp-MimeType'].split(',')
+        for t in mime_types:
+            t = t.rstrip().strip()
+            if t == mimetype:
+                thepkgs.append(pkg.name)
+    return thepkgs
+mimetype = "audio/ogg"
+if 1 < len(sys.argv):
+    mimetype = sys.argv[1]
+print "Browser plugin packages supporting %s:" % mimetype
+for pkg in pkgs_handling_mimetype(mimetype):
+    print "  %s" %pkg
+
+ +

It can be used like this to look up a given MIME type:

+ +
+% ./apt-find-browserplug-for-mimetype 
+Browser plugin packages supporting audio/ogg:
+  gecko-mediaplayer
+% ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
+Browser plugin packages supporting application/x-shockwave-flash:
+  browser-plugin-gnash
+%
+
+ +

In Ubuntu this mechanism is combined with support in the browser +itself to query for plugins and propose to install the needed +packages. It would be great if Debian supported such feature too. Is +anyone working on adding it?

+ +

Update 2013-01-18 14:20: The Debian BTS +request for icweasel support for this feature is +#484010 from 2008 (and +#698426 from today). Lack +of manpower and wish for a different design is the reason thus feature +is not yet in iceweasel from Debian.

- Tags: norsk, nuug, personvern, valg. + Tags: debian, english.
@@ -567,29 +383,120 @@ artikler. Ta en titt der hvis du vil lese mer. :)

- -
7th September 2012
-

As I -mentioned -this summer, I have created a Computer Science song book a few -years ago, and today I finally found time to create a public -Gitorious -repository for the project.

- -

If you want to help out, please clone the source and submit patches -to the HTML version. To generate the PDF and PostScript version, -please use prince XML, or let me know about a useful free software -processor capable of creating a good looking PDF from the HTML.

- -

Want to sing? You can still find the song book in HTML, PDF and -PostScript formats at -Petter's Computer -Science Songbook.

+ +
16th January 2013
+

The DEP-11 +proposal to add AppStream information to the Debian archive, is a +proposal to make it possible for a Desktop application to propose to +the user some package to install to gain support for a given MIME +type, font, library etc. that is currently missing. With such +mechanism in place, it would be possible for the desktop to +automatically propose and install leocad if some LDraw file is +downloaded by the browser.

+ +

To get some idea about the current content of the archive, I decided +to write a simple program to extract all .desktop files from the +Debian archive and look up the claimed MIME support there. The result +can be found on the +Skolelinux FTP +site. Using the collected information, it become possible to +answer the question in the title. Here are the 20 most supported MIME +types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid). +The complete list is available from the link above.

+ +

Debian Stable:

+ +
+  count MIME type
+  ----- -----------------------
+     32 text/plain
+     30 audio/mpeg
+     29 image/png
+     28 image/jpeg
+     27 application/ogg
+     26 audio/x-mp3
+     25 image/tiff
+     25 image/gif
+     22 image/bmp
+     22 audio/x-wav
+     20 audio/x-flac
+     19 audio/x-mpegurl
+     18 video/x-ms-asf
+     18 audio/x-musepack
+     18 audio/x-mpeg
+     18 application/x-ogg
+     17 video/mpeg
+     17 audio/x-scpls
+     17 audio/ogg
+     16 video/x-ms-wmv
+
+ +

Debian Testing:

+ +
+  count MIME type
+  ----- -----------------------
+     33 text/plain
+     32 image/png
+     32 image/jpeg
+     29 audio/mpeg
+     27 image/gif
+     26 image/tiff
+     26 application/ogg
+     25 audio/x-mp3
+     22 image/bmp
+     21 audio/x-wav
+     19 audio/x-mpegurl
+     19 audio/x-mpeg
+     18 video/mpeg
+     18 audio/x-scpls
+     18 audio/x-flac
+     18 application/x-ogg
+     17 video/x-ms-asf
+     17 text/html
+     17 audio/x-musepack
+     16 image/x-xbitmap
+
+ +

Debian Unstable:

+ +
+  count MIME type
+  ----- -----------------------
+     31 text/plain
+     31 image/png
+     31 image/jpeg
+     29 audio/mpeg
+     28 application/ogg
+     27 image/gif
+     26 image/tiff
+     26 audio/x-mp3
+     23 audio/x-wav
+     22 image/bmp
+     21 audio/x-flac
+     20 audio/x-mpegurl
+     19 audio/x-mpeg
+     18 video/x-ms-asf
+     18 video/mpeg
+     18 audio/x-scpls
+     18 application/x-ogg
+     17 audio/x-musepack
+     16 video/x-ms-wmv
+     16 video/x-msvideo
+
+ +

I am told that PackageKit can provide an API to access the kind of +information mentioned in DEP-11. I have not yet had time to look at +it, but hope the PackageKit people in Debian are on top of these +issues.

+ +

Update 2013-01-16 13:35: Updated numbers after +discovering a typo in my script.

- Tags: debian, english, multimedia. + Tags: debian, english.
@@ -597,46 +504,119 @@ Science Songbook.

- -
24th August 2012
-

I dag har Digi en artikkel om at initiativet for å få et norsk -Piratparti er -i -gang med å samle inn sine 5000 underskrifter for å få registrert -seg som parti til neste års stortingsvalg. Initiativet ble -annonsert -i sommer, og har nå kommet så langt at det er på tide å signere -(på papir, med penn og frimerke for innsending. :).

- -

Dagens partier har i stor grad spilt fallitt på det digitale -området, så jeg er positiv til at det kommer en ny aktør på området -som kan ruske opp litt i gamle strukturer og holdninger, og -forhåpentligvis få gjennomslag for noen av sine saker. Piratpartiet -har laget og publisert -et -kjerneprogram som inneholder mange punkter en kan si seg enig -i.

- -

Jeg er ikke sikker på om jeg kommer til å stemme på dem, men jeg -stiller meg helt klart bak at de bør få lov til å stille til valg, og -har selv begynt å samle inn underskrifter. Jeg oppfordrer herved alle -mine lesere til å gjøre det samme. Det trengs 5000 underskrifter før -nyttår, hvilket betyr at det må samles inn minst 40 underskrifter hver -eneste dag frem til 31. desember. Her er det mye arbeide som det -haster med å få gjort.

- -

Min venn Håkon Wium Lie fronter initiativet, og -skjema for -individuell signering finnes på hans websider. Hvis en vil få -andre til å signere er det -et -egen skjema i PDF-format en kan skrive ut og sende inn. Her er det -bare å sette igang!

+ +
15th January 2013
+

Yesterday, I wrote about the +modalias +values provided by the Linux kernel following my hope for +better +dongle support in Debian. 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.

+ +

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.

+ +

+Package: package-name +
Modaliases: module(modaliasglob, modaliasglob, modaliasglob)

+

+ +

It is fairly trivial to write code to find the relevant packages +for a given modalias value using this file.

+ +

An entry like this would suggest the video and picture application +cheese for many USB web cameras (interface bus class 0E01):

+ +

+Package: cheese +
Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)

+

+ +

An entry like this would suggest the pcmciautils package when a +CardBus bridge (bus class 0607) PCI device is present:

+ +

+Package: pcmciautils +
Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*) +

+ +

An entry like this would suggest the package colorhug-client when +plugging in a ColorHug with USB IDs 04D8:F8DA:

+ +

+Package: colorhug-client +
Modaliases: colorhug-client(usb:v04D8pF8DAd*)

+

+ +

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.

+ +

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.

+ +

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 +hw-support-lookup +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.

+ +

When I use it on a machine with a yubikey inserted, it suggest to +install yubikey-personalization:

+ +

+% ./hw-support-lookup +
yubikey-personalization +
% +

+ +

When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it +propose to install the pcmciautils package:

+ +

+% ./hw-support-lookup +
pcmciautils +
% +

+ +

If you know of any hardware-package mapping that should be added to +my +database, please tell me about it.

+ +

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.

+ +

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.

- Tags: norsk, opphavsrett. + Tags: debian, english, isenkram.
@@ -644,20 +624,260 @@ bare å sette igang!

- -
23rd August 2012
-

I came across a great comment from Simon Phipps today, about how -Microsoft -have been forced to open Office, and it made me remember and -revisit the great site -officeshots which allow you -to check out how different programs present the ODF file format. I -recommend both to those of my readers interested in ODF. :)

+ +
14th January 2013
+

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.

- Tags: english, standard. + Tags: debian, english, isenkram.
@@ -665,62 +885,31 @@ recommend both to those of my readers interested in ODF. :)

- -
17th August 2012
-

In my spare time, I currently work on a Norwegian -docbook version of the 2004 book -Free Culture by Lawrence Lessig, -to get a Norwegian text explaining the problems with the copyright law -I can give to my parents and others that are reluctant to read an -English book. It is a marvellous set of examples on how the ever -expanding copyright regulations hurt culture and society. When the -translation is done, I hope to find funding to print and ship a copy -to all the members of the Norwegian parliament, before they sit down -to debate the latest revisions to the Norwegian copyright law. This -summer I -called -for volunteers to help me, and I have been able to secure the -valuable contribution from at least one other Norwegian.

- -

Two days ago, we finally broke the 50% mark. Then more than 50% of -the number of strings to translate (normally paragraphs, but also -titles and index entries are also counted). All parts from the -beginning up to and including chapter four is translated. So is -chapters six, seven and the conclusion. I created a graph to show the -progress:

- - - -

The number of strings to translate increase as I insert the index -entries into the docbook. They were missing with the docbook version -I initially started with. There are still quite a few index entries -missing, but everyone starting with A, B, O, Z and Y are done. I -currently focus on completing the index entries, to get a complete -english version of the docbook source.

- -

There is still need for translators and people with docbook -knowledge, to be able to get a good looking book (I still struggle -with dblatex, xmlto and docbook-xsl) as well as to do the draft -translation and proof reading. And I would like the figures to be -redrawn as SVGs to make it easy to translate them. Any SVG master -around? I am sure there are some legal terms that are unfamiliar to -me. If you want to help, please get in touch, and check out the -project files currently available from github.

- -

If you are curious what the translated book currently look like, -the updated -PDF -and -EPUB -are published on github. The HTML version is published as well, but -github hand it out with MIME type text/plain, confusing browsers, so I -saw no point in linking to that version.

+ +
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".

- Tags: docbook, english, freeculture. + Tags: debian, english, robot.
@@ -735,6 +924,15 @@ saw no point in linking to that version.

Archive