For cirka en måned siden
-
-
-
-
- Epost fra DIFI til Fornyingsdepartementet, datert 2012-11-23 - -
- vedlegg 1, Oppsummering og anbefalinger etter høring av endringer i forskrift om IT-standarer i offentlig forvaltning, datert 2012-11-23 - -
- Notat fra avdeling for IKT og fornying til statsråd i Fornyingsdepartementet om høringen, datert 2013-01-03 - -
Det bør nevnes at da jeg ble nektet innsyn hos mottaker -Fornyingsdepartementet på høringsoppsummeringen som DIFI hadde sendt -ut, spurte jeg DIFI om innsyn i stedet. Det fikk jeg i løpet av et -par dager. Moralen er at hvis ikke mottaker ikke vil gi innsyn, spør -avsender i stedet. Kanskje de har forskjellig forståelse av hva som -bør holdes skjult for folket. Her er de tilsvarende dokumentene jeg -fikk innsyn i fra DIFI:
- --
-
-
- Epost fra DIFI til Fornyingsdepartementet, datert 2012-11-23 - -
- vedlegg 1, Oppsummering og anbefalinger etter høring av endringer i forskrift om IT-standarer i offentlig forvaltning, datert 2012-11-23 - -
- Vedlegg 2, Forslag til endringsforskrift, udatert - -
- Vedlegg 3, Forskrift om IT-standarder i offentlig forvaltning, udatert - -
Det jeg synes er mest interessant er endel av aktørene som -protesterte på fjerningen (Kartverket, Drammen kommune), og hvordan -høringsoppsummeringen ikke tar stilling til effekten av å fjerne ODF -fra katalogen.
+ +The SPICE protocol for +remote display access is the preferred solution with oVirt and RedHat +Enterprise Virtualization, and I was sad to discover the other day +that the browser plugin needed to use these systems seamlessly was +missing in Debian. The request +for a package was from 2012-04-10 with no progress since +2013-04-01, so I decided to wrap up a package based on the great work +from Cajus Pollmeier and put it in a collab-maint maintained git +repository to get a package I could use. I would very much like +others to help me maintain the package (or just take over, I do not +mind), but as no-one had volunteered so far, I just uploaded it to +NEW. I hope it will be available in Debian in a few days.
+ +The source is now available from +http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary.
For en stund tilbake gikk nyheten om -Sandy -Island, en øy som var dukket opp på noen kart, men som ikke var -synlig når en sjekket den på satellittbilder. Dagbladet meldte for -eksempel at -«denne -øya finnes på kart, men ikke i virkeligheten». Noe senere begynte -jeg å lese -historier -om Ruffen til mine barn. Dette er historier om sjøormen Ruffen -skapt av Tor à ge Bringsværd, som starter med følgende beskrivelse:
- --«Langt ute i havet ligger en mystisk øy. Den er bare synlig hver -tirsdag og fredag. Derfor står den ikke på noe kart. På denne øya -ligger et slott, og i slottet bor en gammel, fin sjøormfamilie.» -- -
Det virker åpenbart at Hr. Bringsværd tok feil når han trodde den -ikke var på noe kart, og at noen tydeligvis har vært i nærheten en -tirsdag eller en fredag og fått den med på et kart, mens -satellittbildene er tatt på noen av de fem andre dagene i uka og -dermed ikke ser øya. :)
- -I følge -en -senere artikkel i Dagbladet hevder Shaun Higgins, en forsker fra -New Zealand, at et hvalfangstskip fra 1876 er opprinnelsen til at -spøkelsesøya i det hele tatt havnet på kartet. Det fremgår ikke fra -historien hvilken ukedag de var innom.
- -Jeg har stor sans for Tor à ge Bringsværd. Og han viste nylig en -svært fin side av seg selv da han sa ja til EFNs forespørsel om å gi -ut novellen Kodémus med -Creative Commons-lisens.
+ +The +vmdebootstrap +program is a a very nice system to create virtual machine images. It +create a image file, add a partition table, mount it and run +debootstrap in the mounted directory to create a Debian system on a +stick. Yesterday, I decided to try to teach it how to make images for +Raspberry Pi, as part +of a plan to simplify the build system for +the FreedomBox +project. The FreedomBox project already uses vmdebootstrap for +the virtualbox images, but its current build system made multistrap +based system for Dreamplug images, and it is lacking support for +Raspberry Pi.
+ +Armed with the knowledge on how to build "foreign" (aka non-native +architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap +code and adjusted it to be able to build armel images on my amd64 +Debian laptop. I ended up giving vmdebootstrap five new options, +allowing me to replicate the image creation process I use to make +Debian +Jessie based mesh node images for the Raspberry Pi. First, the +--foreign /path/to/binfm_handler option tell vmdebootstrap to +call debootstrap with --foreign and to copy the handler into the +generated chroot before running the second stage. This allow +vmdebootstrap to create armel images on an amd64 host. Next I added +two new options --bootsize size and --boottype +fstype to teach it to create a separate /boot/ partition with the +given file system type, allowing me to create an image with a vfat +partition for the /boot/ stuff. I also added a --variant +variant option to allow me to create smaller images without the +Debian base system packages installed. Finally, I added an option +--no-extlinux to tell vmdebootstrap to not install extlinux +as a boot loader. It is not needed on the Raspberry Pi and probably +most other non-x86 architectures. The changes were accepted by the +upstream author of vmdebootstrap yesterday and today, and is now +available from +the +upstream project page.
+ +To use it to build a Raspberry Pi image using Debian Jessie, first +create a small script (the customize script) to add the non-free +binary blob needed to boot the Raspberry Pi and the APT source +list:
+ ++#!/bin/sh +set -e # Exit on first error +rootdir="$1" +cd "$rootdir" +cat <<EOF > etc/apt/sources.list +deb http://http.debian.net/debian/ jessie main contrib non-free +EOF +# Install non-free binary blob needed to boot Raspberry Pi. This +# install a kernel somewhere too. +wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \ + -O $rootdir/usr/bin/rpi-update +chmod a+x $rootdir/usr/bin/rpi-update +mkdir -p $rootdir/lib/modules +touch $rootdir/boot/start.elf +chroot $rootdir rpi-update ++ +
Next, fetch the latest vmdebootstrap script and call it like this +to build the image:
+ ++sudo ./vmdebootstrap \ + --variant minbase \ + --arch armel \ + --distribution jessie \ + --mirror http://http.debian.net/debian \ + --image test.img \ + --size 600M \ + --bootsize 64M \ + --boottype vfat \ + --log-level debug \ + --verbose \ + --no-kernel \ + --no-extlinux \ + --root-password raspberry \ + --hostname raspberrypi \ + --foreign /usr/bin/qemu-arm-static \ + --customize `pwd`/customize \ + --package netbase \ + --package git-core \ + --package binutils \ + --package ca-certificates \ + --package wget \ + --package kmod ++ +
The list of packages being installed are the ones needed by +rpi-update to make the image bootable on the Raspberry Pi, with the +exception of netbase, which is needed by debootstrap to find +/etc/hosts with the minbase variant. I really wish there was a way to +set up an Raspberry Pi using only packages in the Debian archive, but +that is not possible as far as I know, because it boots from the GPU +using a non-free binary blob.
+ +The build host need debootstrap, kpartx and qemu-user-static and +probably a few others installed. I have not checked the complete +build dependency list.
+ +The resulting image will not use the hardware floating point unit +on the Raspberry PI, because the armel architecture in Debian is not +optimized for that use. So the images created will be a bit slower +than Raspbian based images.
Today the Isenkram -package finally made it into the archive, after lingering in NEW -for many months. I uploaded it to the Debian experimental suite -2013-01-27, and today it was accepted into the archive.
- -Isenkram is a system for suggesting to users what packages to -install to work with a pluggable hardware device. The suggestion pop -up when the device is plugged in. For example if a Lego Mindstorm NXT -is inserted, it will suggest to install the program needed to program -the NXT controller. Give it a go, and report bugs and suggestions to -BTS. :)
+ +De siste måneders eksponering av +den +totale overvåkningen som foregår i den vestlige verden dokumenterer +hvor sårbare vi er. Men det slår meg at de som er mest sårbare +for dette, myndighetspersoner på alle nivåer, neppe har innsett at de +selv er de mest interessante personene å lage profiler på, for å kunne +påvirke dem.
+ +For å ta et lite eksempel: Stortingets nettsted, +www.stortinget.no (og +forsåvidt også +data.stortinget.no), +inneholder informasjon om det som foregår på Stortinget, og jeg antar +de største brukerne av informasjonen der er representanter og +rådgivere på Stortinget. Intet overraskende med det. Det som derimot +er mer skjult er at Stortingets nettsted bruker +Google +Analytics, hvilket gjør at enhver som besøker nettsidene der også +rapporterer om besøket via Internett-linjer som passerer Sverige, +England og videre til USA. Det betyr at informasjon om ethvert besøk +på stortingets nettsider kan snappes opp av svensk, britisk og USAs +etterretningsvesen. De kan dermed holde et øye med hvilke +Stortingssaker stortingsrepresentantene synes er interessante å sjekke +ut, og hvilke sider rådgivere og andre på stortinget synes er +interessant å besøke, når de gjør det og hvilke andre representanter +som sjekker de samme sidene omtrent samtidig. Stortingets bruk av +Google Analytics gjør det dermed enkelt for utenlands etteretning å +spore representantenes aktivitet og interesse. Hvis noen av +representantene bruker Google Mail eller noen andre tjenestene som +krever innlogging, så vil det være enda enklere å finne ut nøyaktig +hvilke personer som bruker hvilke nettlesere og dermed knytte +informasjonen opp til enkeltpersoner på Stortinget.
+ +Og jo flere nettsteder som bruker Google Analytics, jo bedre +oversikt over stortingsrepresentantenes lesevaner og interesse blir +tilgjengelig for svensk, britisk og USAs etterretning. Hva de kan +bruke den informasjonen til overlater jeg til leseren å undres +over.
For noen dager siden nevnte jeg at vi jobbet med å typesette en -novelle med DocBook. I dag ble -utgivelsen annonsert med følgende pressemelding fra Elektronisk -Forpost Norge), som jeg gjengir i sin helhet:
- -- -- -EFN nyutgir Kodémus:
- -Tor à ge Bringsværd-novelle om IT og overvåkning fra -informasjonsteknologiens spedbarndom får nytt liv
- -Elektronisk Forpost Norge (EFN) er veldig glad for anledningen til -å nyutgi Tor à ge Bringsværds novelle Kodémus i digitalt format for nye -(og gamle) generasjoner. Novellen ble skrevet så tidlig som vinteren -1968, og første gang trykt i novellesamlingen Probok på Gyldendal -samme år.
- -Informasjonsteknologi spiller en sentral rolle i Kodémus, og det er -spennende å sammenligne beskrivelsen av IT fra 1968 med dagens IT i -2013. Forskjellene er mange -- men det er jammen likhetene også. Ikke -minst det at idag går jo nesten alle rundt med lillebrødre på seg!
- -"Riktignok er det ikke påbudt å ha mobil," sier Thomas Gramstad, -leder i EFN. "Men vi holder på å lage et samfunn der det blir så -upraktisk eller tungvint å ikke ha det, at man i praksis ikke slipper -unna. Og disse lillebrødrene sladrer hele tiden til staten (og til -mange andre) om hvor vi er, hva vi gjør, hva vi bryr oss om, hva vi -liker..."
- -Det at Kodémus åpenbart er skrevet i en annen tid med en annen type -IT og likevel virker så relevant idag, er i seg selv et hardtslående -tankekors.
- -Tross sitt IT-tema fantes ikke Kodémus i elektronisk form, og -frivillige i EFN har skannet inn, OCR-tolket og korrekturlest -novellen, og deretter kodet den i en rekke digitale formater.
- -Forfatteren har gitt tillatelse til publisering av Kodémus under ny -lisens, og novellen utgis av EFN med en Creative Commons (CC) -fribrukslisens (nærmere bestemt lisensen CC-BY-NC-ND). For leserne -eller brukerne innebærer dette at de får en klar og standardisert -beskjed om hvilke rettigheter de har til å dele novellen videre med -andre. For forfatteren innebærer dette økt synlighet og -tilgjengelighet for verket, slik at det ikke blir glemt, da -søkemotorer og nettlesere inneholder egne søkevalg for CC-lisenser, og -mange brukere søker etter verk som de vet de kan dele og bruke på -lovlig vis.
- -EFN oppfordrer andre forfattere om å gi ut sine gamle tekster med -en fribrukslisens, slik at tekstene ikke blir glemt og for å stimulere -lovlig deling på nettet. EFN kan være behjelpelig med digitalisering -og utlegging på nett, i den grad det finnes kapasitet blant EFNs -medlemmer til dette. Vi mener at nyutgivelser av tekster under frie -lisenser kan øke interessen rundt forfatterskapet, og vil gjerne bidra -til dette.
- -EFN utgir og deler med dette en novelle fra den digitale -informasjonsteknologiens tidligste barndom. En novelle som fortsatt er -full av vitalitet og aktualitet, og som derfor kan bidra til, og gi -ettertanke i dagens debatter om IT, personvern, overvåkning og -individets frihet og integritet.
- -Du finner novellen her: -
- -
http://efn.no/kodemus/i flere forskjellige formater, for ulike plattformer. Per idag -finnes novellen i disse formatene: EPUB, MOBI, XML, HTML, PDF og -txt. Det kan bli flere formater senere, og evt. frivillige -bidragsytere til dette er velkommen.
- -Kontaktperson for denne pressemeldingen,
- -Thomas Gramstad -
- -
thomas@efn.no -
4817 6875
- -EFN arbeider for dine borgerrettigheter i IT-samfunnet, for -nettverks- og delingskultur, personvern og frihet fra overvåkning, -åpne standarder, brukerstyrt programvare, retten til å kopiere, og -styrking av det digitale sivilsamfunnet m.m. -
- -
www.efn.no
Jeg håper flere forfattere ser verdien av å gjøre kulturen -tilgjengelig for flere, og slår følge med Hr. Bringsværd i å gi ut -sine verker med bruksvilkår med færre bruksbegrensinger enn -opphavsretten legger opp til. Selv om jeg gjerne skulle sett at han -hadde brukt en Creative Commons-lisens som tillot avledede verker og -kommersiell bruk.
+ +The last few days I have been experimenting with +the +batman-adv mesh technology. I want to gain some experience to see +if it will fit the +Freedombox project, and together with my neighbors try to build a +mesh network around the park where I live. Batman-adv is a layer 2 +mesh system ("ethernet" in other words), where the mesh network appear +as if all the mesh clients are connected to the same switch.
+ +My hardware of choice was the Linksys WRT54GL routers I had lying +around, but I've been unable to get them working with batman-adv. So +instead, I started playing with a +Raspberry Pi, and tried to +get it working as a mesh node. My idea is to use it to create a mesh +node which function as a switch port, where everything connected to +the Raspberry Pi ethernet plug is connected (bridged) to the mesh +network. This allow me to hook a wifi base station like the Linksys +WRT54GL to the mesh by plugging it into a Raspberry Pi, and allow +non-mesh clients to hook up to the mesh. This in turn is useful for +Android phones using the Serval +Project voip client, allowing every one around the playground to +phone and message each other for free. The reason is that Android +phones do not see ad-hoc wifi networks (they are filtered away from +the GUI view), and can not join the mesh without being rooted. But if +they are connected using a normal wifi base station, they can talk to +every client on the local network.
+ +To get this working, I've created a debian package +meshfx-node +and a script +build-rpi-mesh-node +to create the Raspberry Pi boot image. I'm using Debian Jessie (and +not Raspbian), to get more control over the packages available. +Unfortunately a huge binary blob need to be inserted into the boot +image to get it booting, but I'll ignore that for now. Also, as +Debian lack support for the CPU features available in the Raspberry +Pi, the system do not use the hardware floating point unit. I hope +the routing performance isn't affected by the lack of hardware FPU +support.
+ +To create an image, run the following with a sudo enabled user +after inserting the target SD card into the build machine:
+ ++% wget -O build-rpi-mesh-node \ + https://raw.github.com/petterreinholdtsen/meshfx-node/master/build-rpi-mesh-node +% sudo bash -x ./build-rpi-mesh-node > build.log 2>&1 +% dd if=/root/rpi/rpi_basic_jessie_$(date +%Y%m%d).img of=/dev/mmcblk0 bs=1M +% ++ +
Booting with the resulting SD card on a Raspberry PI with a USB +wifi card inserted should give you a mesh node. At least it does for +me with a the wifi card I am using. The default mesh settings are the +ones used by the Oslo mesh project at Hackeriet, as I mentioned in +an +earlier blog post about this mesh testing.
+ +The mesh node was not horribly expensive either. I bought +everything over the counter in shops nearby. If I had ordered online +from the lowest bidder, the price should be significantly lower:
+ +Supplier | Model | NOK |
---|---|---|
Teknikkmagasinet | Raspberry Pi model B | 349.90 |
Teknikkmagasinet | Raspberry Pi type B case | 99.90 |
Lefdal | Jensen Air:Link 25150 | 295.- |
Clas Ohlson | Kingston 16 GB SD card | 199.- |
Total cost | 943.80 |
Now my mesh network at home consist of one laptop in the basement +connected to my production network, one Raspberry Pi node on the 1th +floor that can be seen by my neighbor across the park, and one +play-node I use to develop the image building script. And some times +I hook up my work horse laptop to the mesh to test it. I look forward +to figuring out what kind of latency the batman-adv setup will give, +and how much packet loss we will experience around the park. :)
Would you like to help the environment and save money at the same -time, without much sacrifice? A small step could be to change the -font you use when printing.
- -Three years ago, -Ars -Technica reported how the University of Wisconsin-Green Bay -changed their default front from -Arial to -Century -Gothic to save money. The Century Gothic font uses 30% less toner -than Arial to print the same text. In other word, you could cut your -toner costs by 30% (or actually, increase your toner supply life time -by more than 30%), by simply changing the default font used in your -prints.
- -But it is not quite obvious how much one will safe by switching. -The University of Wisconsin-Green Bay said it used $100,000 per year -on ink and toner cartridges, according to -a report from -TwinCities.com, and expected to save between $5,000 and $10,000 -per year by asking staff and students to use a different font. Not -all PDFs and documents are created internally, and those from external -sources will most likely still use a different font. Also, the -Century Gothic font is slightly wider than Arial, and thus might use -more sheets of paper to print the same text, so the total saving -depend on the documents printed.
- -But it is definitely something to consider, if you want to reduce -the amount of trash, decrease the amount of toner used in the world, -and save some money in the process.
+ +Back in 2010, I created a Perl library to talk to +the Spykee robot +(with two belts, wifi, USB and Linux) and made it available from my +web page. Today I concluded that it should move to a site that is +easier to use to cooperate with others, and moved it to github. If +you got a Spykee robot, you might want to check out +the +libspykee-perl github repository.
A few days ago, during a discussion in -EFN about interesting books to read -about copyright and the data retention directive, a suggestion to read -the 1968 short story Kodémus by -Tore à ge Bringsværd -came up. The text was only available in old paper books, and thus not -easily available for current and future generations. Some of the -people participating in the discussion contacted the author, and -reported back 2013-03-19 that the author was OK with releasing the -short story using a Creative -Commons license. The text was quickly scanned and OCR-ed, and we -were ready to start on the editing and typesetting.
- -As I already had some experience formatting text in my project to -provide a Norwegian version of the Free Culture book by Lawrence -Lessig, I chipped in and set up a -DocBook processing framework to -generate PDF, HTML and EPUB version of the short story. The tools to -transform DocBook to different formats are already in my Linux -distribution of choice, Debian, so -all I had to do was to use the -dblatex, -dbtoepub -and xmlto tools to do the -conversion. After a few days, we decided to replace dblatex with -xsltproc/fop (aka -docbook-xsl), -to get the copyright information to show up in the PDF and to get a -nicer <variablelist> typesetting, but that is just a minor -technical detail.
- -There were a few challenges, of course. We want to typeset the -short story to look like the original, and that require fairly good -control over the layout. The original short story have three -parts/scenes separated by a single horizontally centred star (*), and -the paragraphs do not contain only flowing text, but dialogs and text -that started on a new line in the middle of the paragraph.
- -I initially solved the first challenge by using a paragraph with a -single star in it, ie <para>*</para>, but it made sure a -placeholder indicated where the scene shifted. This did not look too -good without the centring. The next approach was to create a new -preprocessor directive <?newscene?>, mapping to "<hr/>" -for HTML and "<fo:block text-align="center"><fo:leader -leader-pattern="rule" rule-thickness="0.5pt"/></fo:block>" -for FO/PDF output (did not try to implement this in dblatex, as we had -switched at this time). The HTML XSL file looked like this:
- -- --<?xml version='1.0'?> -<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'> - <xsl:template match="processing-instruction('newscene')"> - <hr/> - </xsl:template> -</xsl:stylesheet> -
And the FO/PDF XSL file looked like this:
- -- --<?xml version='1.0'?> -<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'> - <xsl:template match="processing-instruction('newscene')"> - <fo:block text-align="center"> - <fo:leader leader-pattern="rule" rule-thickness="0.5pt"/> - </fo:block> - </xsl:template> -</xsl:stylesheet> -
Finally, I came across the <bridgehead> tag, which seem to be -a good fit for the task at hand, and I replaced <?newscene?> -with <bridgehead>*</bridgehead>. It isn't centred, but we -can fix it with some XSL rule if the current visual layout isn't -enough.
- -I did not find a good DocBook compliant way to solve the -linebreak/paragraph challenge, so I ended up creating a new processor -directive <?linebreak?>, mapping to <br/> in HTML, and -<fo:block/> in FO/PDF. I suspect there are better ways to do -this, and welcome ideas and patches on github. The HTML XSL file now -look like this:
- -- --<?xml version='1.0'?> -<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0'> - <xsl:template match="processing-instruction('linebreak)"> - <br/> - </xsl:template> -</xsl:stylesheet> -
And the FO/PDF XSL file looked like this:
- -- --<?xml version='1.0'?> -<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version='1.0' - xmlns:fo="http://www.w3.org/1999/XSL/Format"> - <xsl:template match="processing-instruction('linebreak)"> - <fo:block/> - </xsl:template> -</xsl:stylesheet> -
One unsolved challenge is our wish to expose different ISBN numbers -per publication format, while keeping all of them in some conditional -structure in the DocBook source. No idea how to do this, so we ended -up listing all the ISBN numbers next to their format in the colophon -page.
- -If you want to check out the finished result, check out the -source repository at -github -(future/new/official -repository). We expect it to be ready and announced in a few -days.
+The last few days I came across a few good causes that should get +wider attention. I recommend signing and donating to each one of +these. :)
+ +Via Debian +Project News for 2013-10-14 I came across the Outreach Program for +Women program which is a Google Summer of Code like initiative to get +more women involved in free software. One debian sponsor has offered +to match any donation done to Debian +earmarked for this initiative. I donated a few minutes ago, and +hope you will to. :)
+ +And the Electronic Frontier Foundation just announced plans to +create video +documentaries about the excessive spying on every Internet user that +take place these days, and their need to fund the work. I've already +donated. Are you next?
+ +For my Norwegian audience, the organisation Studentenes og +Akademikernes Internasjonale Hjelpefond is collecting signatures for a +statement under the heading +Bloggers United for Open +Access for those of us asking for more focus on open access in the +Norwegian government. So far 499 signatures. I hope you will sign it +too.
I -siste -høring om -referansekatalogen -for IT-standarder i offentlig sektor, med høringsfrist 2012-09-30 -(DIFI-sak 2012/498), ble det foreslått å fjerne ODF som obligatorisk -standard når en publiserte dokumenter som skulle kunne redigeres -videre av mottaker. NUUG og andre protesterte på forslaget, som er et -langt steg tilbake når det gjelder å sikre like rettigheter for alle -når en kommuniserer med det offentlige. For noen dager siden ble jeg -oppmerksom på at Direktoratet for forvaltning og IKT (DIFI) og -Fornyings-,administrasjons- og kirkedepartementet (FAD) har -konkludert, og oversendt forslag til regjeringen i saken. FADs -dokument -2012/2168-8, -«Utkast til endring av standardiseringsforskriften» datert 2013-02-06 -har følgende triste oppsummering fra høringen i saken:
- --Det kom noen innvendinger på forslaget om å fjerne ODF som -obligatorisk standard for redigerbare dokumenter. Innvendingene har -ikke blitt ilagt avgjørende vekt. -- -
Ved å fjerne ODF som obligatorisk format ved publisering av -redigerbare dokumenter setter en Norge tiår tilbake. Det som vil skje -er at offentlige etater går tilbake til kun å publisere dokumenter på -et av de mange formatene til Microsoft Office, og alle som ikke -aksepterer bruksvilkårene til Microsoft eller ikke har råd til å bruke -penger på å få tilgang til Microsoft Office må igjen basere seg på -verktøy fra utviklerne som er avhengig av å reversutvikle disse -formatene. I og med at ISO-spesifikasjonen for OOXML ikke komplett og -korrekt spesifiserer formatene til MS Office (men er nyttige å titte i -når en reversutvikler), er en tilbake til en situasjon der en ikke har -en -fri og åpen standard å forholde seg til, men i stedet må springe -etter Microsoft. Alle andre leverandører enn Microsoft vil dermed ha -en seriøs ulempe. Det er som å fjerne krav om bruk av meter som -måleenhet, og heretter aksepterer alle måleenheter som like gyldige, -når en vet at den mest brukte enheten vil være armlengden til Steve -Ballmer slik Microsoft måler den.
- -Jeg er ikke sikker på om forslaget er vedtatt av regjeringen ennå. -Kristian Bergem hos DIFI nevnte på et møte forrige tirsdag at han -trodde det var vedtatt i statsråd 8. mars, men jeg har ikke klart å -finne en skriftlig kilde på regjeringen.no som bekrefter dette. -Kanskje det ennå ikke er for sent...
- -Jeg ba i forrige uke om innsyn i dokument 6, 7 og 8 i FAD-saken, og -har i dag fått innsyn i dokument 7 og 8. Ble nektet innsyn i -dokumentet med tittelen «Oppsummering av høring om endringer i -forskrift om IT-standarder i offentlig forvaltning» med hjemmel i -off. lovens §15.1, så det er vanskelig å vite hvordan argumentene fra -høringen ble mottatt og forstått av saksbehandleren hos DIFI. Lurer -på hvordan jeg kan klage på at jeg ikke fikk se oppsummeringen. Fikk -tre PDFer tilsendt fra FAD, -Endring av underversjon i EHF, -Bakgrunnsnotat knyttet til versjon av EHF standarden i Forskrift om IT-standarder i offentlig sektor og -Utkast til endring av standardiseringsforskriften, hvis du vil ta en titt.
+ +Wireless mesh networks are self organising and self healing +networks that can be used to connect computers across small and large +areas, depending on the radio technology used. Normal wifi equipment +can be used to create home made radio networks, and there are several +successful examples like +Freifunk and +Athens Wireless Metropolitan Network +(see +wikipedia +for a large list) around the globe. To give you an idea how it +work, check out the nice overview of the Kiel Freifunk community which +can be seen from their +dynamically +updated node graph and map, where one can see how the mesh nodes +automatically handle routing and recover from nodes disappearing. +There is also a small community mesh network group in Oslo, Norway, +and that is the main topic of this blog post.
+ +I've wanted to check out mesh networks for a while now, and hoped +to do it as part of my involvement with the NUUG member organisation community, and +my recent involvement in +the Freedombox project +finally lead me to give mesh networks some priority, as I suspect a +Freedombox should use mesh networks to connect neighbours and family +when possible, given that most communication between people are +between those nearby (as shown for example by research on Facebook +communication patterns). It also allow people to communicate without +any central hub to tap into for those that want to listen in on the +private communication of citizens, which have become more and more +important over the years.
+ +So far I have only been able to find one group of people in Oslo +working on community mesh networks, over at the hack space +Hackeriet at Husmania. They seem to +have started with some Freifunk based effort using OLSR, called +the Oslo +Freifunk project, but that effort is now dead and the people +behind it have moved on to a batman-adv based system called +meshfx. Unfortunately the wiki +site for the Oslo Freifunk project is no longer possible to update to +reflect this fact, so the old project page can't be updated to point to +the new project. A while back, the people at Hackeriet invited people +from the Freifunk community to Oslo to talk about mesh networks. I +came across this video where Hans Jørgen Lysglimt interview the +speakers about this talk (from +youtube):
+ + + +I mentioned OLSR and batman-adv, which are mesh routing protocols. +There are heaps of different protocols, and I am still struggling to +figure out which one would be "best" for some definitions of best, but +given that the community mesh group in Oslo is so small, I believe it +is best to hook up with the existing one instead of trying to create a +completely different setup, and thus I have decided to focus on +batman-adv for now. It sure help me to know that the very cool +Serval project in Australia +is using batman-adv as their meshing technology when it create a self +organizing and self healing telephony system for disaster areas and +less industrialized communities. Check out this cool video presenting +that project (from +youtube):
+ + + +According to the wikipedia page on +Wireless +mesh network there are around 70 competing schemes for routing +packets across mesh networks, and OLSR, B.A.T.M.A.N. and +B.A.T.M.A.N. advanced are protocols used by several free software +based community mesh networks.
+ +The batman-adv protocol is a bit special, as it provide layer 2 +(as in ethernet ) routing, allowing ipv4 and ipv6 to work on the same +network. One way to think about it is that it provide a mesh based +vlan you can bridge to or handle like any other vlan connected to your +computer. The required drivers are already in the Linux kernel at +least since Debian Wheezy, and it is fairly easy to set up. A +good +introduction is available from the Open Mesh project. These are +the key settings needed to join the Oslo meshfx network:
+ +Setting | Value |
---|---|
Protocol / kernel module | batman-adv |
ESSID | meshfx@hackeriet | Channel / Frequency | 11 / 2462 | +Cell ID | 02:BA:00:00:00:01 | +
The reason for setting ad-hoc wifi Cell ID is to work around bugs +in firmware used in wifi card and wifi drivers. (See a nice post from +VillageTelco about +"Information +about cell-id splitting, stuck beacons, and failed IBSS merges! +for details.) When these settings are activated and you have some +other mesh node nearby, your computer will be connected to the mesh +network and can communicate with any mesh node that is connected to +any of the nodes in your network of nodes. :)
+ +My initial plan was to reuse my old Linksys WRT54GL as a mesh node, +but that seem to be very hard, as I have not been able to locate a +firmware supporting batman-adv. If anyone know how to use that old +wifi access point with batman-adv these days, please let me know.
+ +If you find this project interesting and want to join, please join +us on IRC, either channel +#oslohackerspace +or #nuug on +irc.freenode.net.
+ +While investigating mesh networks in Oslo, I came across an old +research paper from the university of Stavanger and Telenor Research +and Innovation called +The +reliability of wireless backhaul mesh networks and elsewhere +learned that Telenor have been experimenting with mesh networks at +Grünerløkka in Oslo. So mesh networks are also interesting for +commercial companies, even though Telenor discovered that it was hard +to figure out a good business plan for mesh networking and as far as I +know have closed down the experiment. Perhaps Telenor or others would +be interested in a cooperation?
+ +Update 2013-10-12: I was just +told +by the Serval project developers that they no longer use +batman-adv (but are compatible with it), but their own crypto based +mesh system.
Via -twitter -I just discovered that Pcwizz have -done a video -review on Youtube of Skolelinux -/ Debian Edu version 6. He installed the standalone profile and -the video show a walk-through of of the menu content, demonstration of -a few programs and his view of our distribution.
- -There is also some really nice quotes (transcribed by me, might -have heard wrong). While looking thought the Graphics menu:
- --"Basically everything you ever need in a school environment." -- -
And as a general evaluation of the entire distribution:
- --"So, yeah, a bit bloated. It kept all the Debian stuff in there, just -to keep it nice and GNU. So, I do not want to go on about it, but -lets give it 7 out of 10. I am not going to use it. That is because -I am not deploying a school network. There may be some mythical -feature to help you deploy Skolelinux on a school network." -- -
To bad he did not test the server profile, and discovered the PXE -installation option. It make it possible to install only the main -server from CD, and the rest of the machines via the net, and might be -considered the mythical feature he talk about. :)
- -While looking through the menus, there is also this funny comment -about the part of the K menu generated from the Debian menu subsystem: - -
-"[The K menu] have a special Debian section for software that no-one -is going to look at, because it contain lots of junky stuff that you -actually don't need in the education distribution, but have just been -included because it isn't stripped out for some reason." -- -
I guess it is yet another argument for merging the Debian menu and -Gnome/KDE desktop menu entries into -one -consistent menu system instead of two incomplete and partly -inconsistent menu systems.
- -The entire video is available below for those accepting iframe -embedding:
- - + +The other day I was pleased and surprised to discover that Marcelo +Salvador had published a +video on +Youtube showing how to install the standalone Debian Edu / +Skolelinux profile. This is the profile intended for use at home or +on laptops that should not be integrated into the provided network +services (no central home directory, no Kerberos / LDAP directory etc, +in other word a single user machine). The result is 11 minutes long, +and show some user applications (seem to be rather randomly picked). +Missed a few of my favorites like celestia, planets and chromium +showing the Zygote Body 3D model +of the human body, but I guess he did not know about those or find +other programs more interesting. :) And the video do not show the +advantages I believe is one of the most valuable featuers in Debian +Edu, its central school server making it possible to run hundreds of +computers without hard drives by installing one central +LTSP server.
+ +Anyway, check out the video, embedded below and linked to above:
+ + + +Are there other nice videos demonstrating Skolelinux? Please let +me know. :)