]> pere.pagekite.me Git - homepage.git/blob - blog/index.html
Finpuss av teksten.
[homepage.git] / blog / index.html
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
4 <head>
5 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
6 <title>Petter Reinholdtsen</title>
7 <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
8 <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
9 <link rel="alternate" title="RSS Feed" href="http://people.skolelinux.org/pere/blog/index.rss" type="application/rss+xml" />
10 </head>
11 <body>
12 <div class="title">
13 <h1>
14 <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
15
16 </h1>
17
18 </div>
19
20
21
22 <div class="entry">
23 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Graphing_the_Norwegian_company_ownership_structure.html">Graphing the Norwegian company ownership structure</a></div>
24 <div class="date">15th June 2015</div>
25 <div class="body"><p>It is a bit work to figure out the ownership structure of companies
26 in Norway. The information is publicly available, but one need to
27 recursively look up ownership for all owners to figure out the complete
28 ownership graph of a given set of companies. To save me the work in
29 the future, I wrote a script to do this automatically, outputting the
30 ownership structure using the Graphviz/dotty format. The data source
31 is web scraping from <a href="http://www.proff.no/">Proff</a>, because
32 I failed to find a useful source directly from the official keepers of
33 the ownership data, <a href="http://www.brreg.no/">Brønnøysundsregistrene</a>.</p>
34
35 <p>To get an ownership graph for a set of companies, fetch
36 <a href="https://github.com/petterreinholdtsen/brreg-norway-ownership-graph">the code from git</a> and run it using the organisation number. I'm
37 using the Norwegian newspaper Dagbladet as an example here, as its
38 ownership structure is very simple:</p>
39
40 <pre>
41 % time ./bin/eierskap-dotty 958033540 > dagbladet.dot
42
43 real 0m2.841s
44 user 0m0.184s
45 sys 0m0.036s
46 %
47 </pre>
48
49 <p>The script accept several organisation numbers on the command line,
50 allowing a cluster of companies to be graphed in the same image. The
51 resulting dot file for the example above look like this. The edges
52 are labeled with the ownership percentage, and the nodes uses the
53 organisation number as their name and the name as the label:</p>
54
55 <pre>
56 digraph ownership {
57 rankdir = LR;
58 "Aller Holding A/s" -> "910119877" [label="100%"]
59 "910119877" -> "998689015" [label="100%"]
60 "998689015" -> "958033540" [label="99%"]
61 "974530600" -> "958033540" [label="1%"]
62 "958033540" [label="AS DAGBLADET"]
63 "998689015" [label="Berner Media Holding AS"]
64 "974530600" [label="Dagbladets Stiftelse"]
65 "910119877" [label="Aller Media AS"]
66 }
67 </pre>
68
69 <p>To view the ownership graph, run "<tt>dotty dagbladet.dot</tt>" or
70 convert it to a PNG using "<tt>dot -T png dagbladet.dot >
71 dagbladet.png</tt>". The result can be seen below:</p>
72
73 <img src="http://people.skolelinux.org/pere/blog/images/2015-06-15-ownership-graphs-norway-dagbladet.png" width="80%">
74
75 <p>Note that I suspect the "Aller Holding A/S" entry to be incorrect
76 data in the official ownership register, as that name is not
77 registered in the official company register for Norway. The ownership
78 register is sensitive to typos and there seem to be no strict checking
79 of the ownership links.</p>
80
81 <p>Let me know if you improve the script or find better data sources.
82 The code is licensed according to GPL 2 or newer.</p>
83
84 <p>Update 2015-06-15: Since the initial post I've been told that
85 "<a href="http://www.proff.dk/firma/carl-allers-etablissement-aktieselskab/københavn-v/hovedkontorer/13624518-3/">Aller
86 Holding A/S</a>" is a Danish company, which explain why it did not
87 have a Norwegian organisation number. I've also been told that there
88 is a <a href="http://www.brreg.no/automatiske/webservices/">web
89 services API available</a> from Brønnøysundsregistrene, for those
90 willing to accept the terms or pay the price.</p>
91 </div>
92 <div class="tags">
93
94
95 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>.
96
97
98 </div>
99 </div>
100 <div class="padding"></div>
101
102 <div class="entry">
103 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Measuring_and_adjusting_the_loudness_of_a_TV_channel_using_bs1770gain.html">Measuring and adjusting the loudness of a TV channel using bs1770gain</a></div>
104 <div class="date">11th June 2015</div>
105 <div class="body"><p>Television loudness is the source of frustration for viewers
106 everywhere. Some channels are very load, others are less loud, and
107 ads tend to shout very high to get the attention of the viewers, and
108 the viewers do not like this. This fact is well known to the TV
109 channels. See for example the BBC white paper
110 "<a href="http://downloads.bbc.co.uk/rd/pubs/whp/whp-pdf-files/WHP202.pdf">Terminology
111 for loudness and level dBTP, LU, and all that</a>" from 2011 for a
112 summary of the problem domain. To better address the need for even
113 loadness, the TV channels got together several years ago to agree on a
114 new way to measure loudness in digital files as one step in
115 standardizing loudness. From this came the ITU-R standard BS.1770,
116 "<a href="http://www.itu.int/rec/R-REC-BS.1770/en">Algorithms to
117 measure audio programme loudness and true-peak audio level</a>".</p>
118
119 <p>The ITU-R BS.1770 specification describe an algorithm to measure
120 loadness in LUFS (Loudness Units, referenced to Full Scale). But
121 having a way to measure is not enough. To get the same loudness
122 across TV channels, one also need to decide which value to standardize
123 on. For European TV channels, this was done in the EBU Recommondaton
124 R128, "<a href="https://tech.ebu.ch/docs/r/r128.pdf">Loudness
125 normalisation and permitted maximum level of audio signals</a>", which
126 specifies a recommended level of -23 LUFS. In Norway, I have been
127 told that NRK, TV2, MTG and SBS have decided among themselves to
128 follow the R128 recommondation for playout from 2016-03-01.</p>
129
130 <p>There are free software available to measure and adjust the loudness
131 level using the LUFS. In Debian, I am aware of a library named
132 <a href="https://tracker.debian.org/pkg/libebur128">libebur128</a>
133 able to measure the loudness and since yesterday morning a new binary
134 named <a href="http://bs1770gain.sourceforge.net">bs1770gain</a>
135 capable of both measuring and adjusting was uploaded and is waiting
136 for NEW processing. I plan to maintain the latter in Debian under the
137 <a href="https://qa.debian.org/developer.php?email=pkg-multimedia-maintainers%40lists.alioth.debian.org">Debian
138 multimedia</a> umbrella.</p>
139
140 <p>The free software based TV channel I am involved in,
141 <a href="http://www.frikanalen.no/">Frikanalen</a>, plan to follow the
142 R128 recommondation ourself as soon as we can adjust the software to
143 do so, and the bs1770gain tool seem like a good fit for that part of
144 the puzzle to measure loudness on new video uploaded to Frikanalen.
145 Personally, I plan to use bs1770gain to adjust the loudness of videos
146 I upload to Frikanalen on behalf of <a href="http://www.nuug.no/">the
147 NUUG member organisation</a>. The program seem to be able to measure
148 the LUFS value of any media file handled by ffmpeg, but I've only
149 successfully adjusted the LUFS value of WAV files. I suspect it
150 should be able to adjust it for all the formats handled by ffmpeg.</p>
151 </div>
152 <div class="tags">
153
154
155 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
156
157
158 </div>
159 </div>
160 <div class="padding"></div>
161
162 <div class="entry">
163 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Hva_gj_r_at_NRK_kan_distribuere_H_264_video_uten_patentavtale_med_MPEG_LA_.html">Hva gjør at NRK kan distribuere H.264-video uten patentavtale med MPEG LA?</a></div>
164 <div class="date">10th June 2015</div>
165 <div class="body"><p>Helt siden jeg i 2012 fikk beskjed fra MPEG LA om at
166 <a href="http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html">NRK
167 trengte patentavtale med dem</a> hvis de distribuerte H.264-video til
168 sluttbrukere, har jeg lurt på hva som gjør at NRK ikke har slik
169 avtale. For noen dager siden fikk jeg endelig gjort noe med min
170 undring, og sendte 2015-05-28 følgende epost til info (at) nrk.no med
171 tittel "Hva gjør at NRK kan distribuere H.264-video uten patentavtale
172 med MPEG LA?":</p>
173
174 <p><blockquote>
175 <p>Jeg lurer på en ting rundt NRKs bruk av H.264-video på sine
176 websider samt distribusjon via RiksTV og kabel-TV. Har NRK vurdert om
177 det er behov for en patentavtale med
178 <a href="http://www.mpegla.com/">MPEG LA</a> slik det står i
179 programvarelisensene til blant annet Apple Final Cut Studio, Adobe
180 Premiere Pro, Avid og Apples Final Cut Pro X?</p>
181
182 <p>Hvis dere har vurdert dette, hva var utfallet av en slik vurdering?</p>
183
184 <p>Hvis dere ikke har vurdert dette, har NRK planer om å vurdere behovet
185 for patentavtale?</p>
186
187 <p>I følge en artikkel på
188 <a href="https://nrkbeta.no/2012/02/01/siste-kutt-for-final-cut/">NRK
189 Beta i 2012</a> har NRK brukt eller testet både Apple Final Cut
190 Studio, Adobe Premiere Pro, Avid og Apples Final Cut Pro X til bruk
191 for å redigere video før sending. Alle disse har bruksvilkår
192 understøttet av opphavsretten som sier at de kun kan brukes til å lage
193 filmer til personlig og ikke-kommersiell bruk - med mindre en har en
194 lisensavtale med MPEG LA om bruk av patenter utstedt i USA for H.264.
195 Se f.eks. <a href="http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf">bruksvilkårene for Avid</a>, <a href="http://news.cnet.com/8301-30685_3-20000101-264.html">Adobe Premiere</a> og <a href="http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf">Apple Final
196 Cut Studio</a> og søk etter "MPEG LA".</p>
197
198 <p>Dette får meg til å lure på om det er brudd på opphavsretten å bruke
199 disse verktøyene i strid med bruksvilkårene uten patentavtale med MPEG
200 LA. Men NRK bruker jo tilsynelatende disse verktøyene uten patentavtale
201 med MPEG LA.</p>
202
203 <p>I følge forfatteren av Open Broadcast Encoder finnes det to typer
204 H.264-relaterte avtaler en kan få med MPEG LA. Det er én for å lage
205 programvare og utstyr som produserer H.264-video, og en annen for å
206 kringkaste video som bruker H.264. Dette forteller meg at selv om
207 produsentene av utstyr og programvare som NRK bruker har en slik avtale
208 med MPEG LA, så trenges det en egen avtale for å kringkaste video på det
209 formatet.</p>
210
211 <p>I følge Ryan Rodriguez hos MPEG LA, da jeg spurte ham på epost i
212 juni 2012, har NRK ikke en slik avtale med MPEG LA. Han sa videre at
213 NRK trenger en slik avtale hvis NRK tilbyr H.264-kodet video til
214 sluttbrukere. Jeg sjekket listen med
215 <a href="http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx">organisasjoner
216 med avtale med MPEG LA</a> og NRK står fortsatt ikke der.</p>
217
218 <p>Jeg lurer dermed på hva som gjør at NRK kan bruke de overnevnte
219 videoredigeringsverktøyene, som tilsynelatende har krav om avtale med
220 MPEG LA for å kunne brukes slik NRK bruker dem, til å lage videofiler
221 for distribusjon uten å ha en avtale med MPEG LA om distribusjon av
222 H.264-video? Dette er spesielt interessant å vite for oss andre som
223 også vurderer å spre H.264-video etter å ha redigert dem med disse mye
224 brukte videoredigeringsverktøyene.</p>
225 </blockquote></p>
226
227 <p>Samme dag fikk jeg automatisk svar om at min henvendelse hadde fått
228 saksid 1294699. Jeg fikk deretter følgende respons fra NRK
229 2015-06-09:</p>
230
231 <p><blockquote>
232 <p>Hei, beklager lang svartid, men det tok litt tid å finne ut hvem som kunne
233 svare på dette.</p>
234
235 <p>For selskaper som leverer h.264 til sluttbrukere på nett (f.eks
236 NRKs nett- tv utgaver som bruker h.264) - og som leverer slike
237 tjenester uten betaling fra forbrukere – er det heller ikke påkrevd
238 noen patentavtale.</p>
239
240 <p><a href="http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y">http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y</a></p>
241
242 <p>Med vennlig hilsen
243 <br>Gunn Helen Berg
244 <br>Informasjonskonsulent, Publikumsservice</p>
245
246 <p>NRK
247 <br>Strategidivisjonen
248 <Br>Sentralbord: +47 23 04 70 00
249 <br>Post: NRK Publikumsservice, 8608 Mo i Rana
250 <br>nrk.no / info (at) nrk.no</p>
251 </blockquote></p>
252
253 Da dette ikke helt var svar på det jeg lurte på, sendte jeg samme dag
254 oppfølgerepost tilbake:
255
256 <p><blockquote>
257 <p>[Gunn Helen Berg]
258 <br>> Hei, beklager lang svartid, men det tok litt tid å finne ut hvem som
259 <br>> kunne svare på dette.</p>
260
261 <p>Takk for svar. Men det besvarte ikke helt det jeg spurte om.</p>
262
263 <p>> For selskaper som leverer h.264 til sluttbrukere på nett (f.eks NRKs
264 <br>> nett- tv utgaver som bruker h.264) - og som leverer slike tjenester
265 <br>> uten betaling fra forbrukere – er det heller ikke påkrevd noen
266 <br>> patentavtale.
267 <br>>
268 <br>> http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y</p>
269
270 <p>Spørsmålet er ikke kun om MPEG LA krever patentavtale eller ikke
271 (hvilket ikke helt besvares av pressemeldingen omtalt over, gitt at
272 pressemeldingen kom i 2010, to år før MPEG LA ansvarlige for
273 internasjonal lisensiering egen Ryan Rodriguez fortalte meg på epost
274 at NRK trenger en lisens.</p>
275
276 <p>Det er uklart fra pressemeldingen hva "Internet Broadcast AVC
277 Video" konkret betyr, men i følge en
278 <a href="http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf">presentasjon
279 fra MPEG LA med tema "AVC PAtent Portfoli License Briefing" datert
280 2015-05-15</a> gjelder "Internet Broadcast AVC Video" kun kringkasting
281 på Internet som ikke tilbyr valg av enkeltinnslag ("not
282 title-by-title"), hvilket jo NRK gjør på sine nettsider. I tillegg
283 kringkaster jo NRK H.264-video også utenom Internet (RiksTV, kabel,
284 satelitt), hvilket helt klart ikke er dekket av vilkårene omtalt i
285 pressemeldingen.</p>
286
287 <p>Spørsmålet mitt er hvordan NRK kan bruke verktøy med bruksvilkår
288 som krever avtale med MPEG LA for det NRK bruker dem til, når NRK ikke
289 har avtale med MPEG LA. Hvis jeg forsto spørsmålet riktig, så mener
290 NRK at dere ikke trenger avtale med MPEG LA, men uten slik avtale kan
291 dere vel ikke bruke hverken Apple Final Cut Studio, Adobe Premiere
292 Pro, Avid eller Apples Final Cut Pro X for å redigere video før
293 sending?</p>
294
295 <p>Mine konkrete spørsmål var altså:</p>
296
297 <ul>
298
299 <li>Hvis NRK har vurdert om det er behov for en patentavtale med MPEG LA
300 slik det er krav om i programvarelisensene til blant annet Apple
301 Final Cut Studio, Adobe Premiere Pro, Avid og Apples Final Cut Pro X,
302 hva var utfallet av en slik vurdering? Kan jeg få kopi av vurderingen
303 hvis den er gjort skriftlig?</li>
304
305 <li>Hvis NRK ikke har vurdert dette, har NRK planer om å vurdere behovet
306 for patentavtale?</li>
307
308 <li>Hva slags saksnummer fikk min henvendelse i NRKs offentlige
309 postjournal? Jeg ser at postjournalen ikke er publisert for den
310 aktuelle perioden ennå, så jeg fikk ikke sjekket selv.</li>
311
312 </ul>
313 </blockquote></p>
314
315 <p>Det hjelper å ha funnet rette vedkommende i NRK, for denne gangen
316 fikk jeg svar tilbake dagen etter (2015-06-10), fra Geir Børdalen i
317 NRK:</p>
318
319 <p><blockquote>
320 <p>Hei Petter Reinholdtsen</p>
321
322 <p>Jeg har sjekket saken med distribusjonssjef for tv, Arild Hellgren
323 (som var teknologidirektør da bakkenettet ble satt opp). NRK v/
324 Hellgren hadde møte med MPEG LA sammen med den europeiske
325 kringkastingsunionen EBU før bakkenettet for TV ble satt opp
326 (igangsatt høsten 2007). I dette møtet ble det avklart at NRK/EBU ikke
327 trengte noen patentavtale for h.264 i forbindelse med oppsett av
328 bakkenettet eller bruk av MPEG4 h.264 som kompresjonsalgoritme fordi
329 tjenesten «in full»(nor: helt) var betalt av utsendelseselskapene og
330 ikke av forbrukerne.</p>
331
332 <p><a href="http://www.nrk.no/oppdrag/digitalt-bakkenett-1.3214555">http://www.nrk.no/oppdrag/digitalt-bakkenett-1.3214555</a></p>
333
334 <p>Det er også klart slått fast at selskaper som leverer video basert
335 på MPEG4 h.264 til sluttbrukere på nett, heller ikke påkrevd noen
336 patentavtale – så lenge de leverer slike tjenester uten betaling fra
337 sluttbrukere.</p>
338
339 <a href="http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y">http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y</a>
340
341 <p>“MPEG LA announced today that its AVC Patent Portfolio License will
342 continue not to charge royalties for Internet Video that is free to
343 end users (known as “Internet Broadcast AVC Video”) during the entire
344 life of this License. MPEG LA previously announced it would not charge
345 royalties for such video through December 31, 2015 (see
346 <a href="http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf">http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf</a>),
347 and today’s announcement makes clear that royalties will continue not
348 to be charged for such video beyond that time. Products and services
349 other than Internet Broadcast AVC Video continue to be
350 royalty-bearing.”</p>
351
352 <p>Vi har derfor ikke noe behov for å vurdere noen patentavtale med
353 MPEG LA.</p>
354
355 <p>Understreker for øvrig at NRK ikke er låst til MPEG4 – h.264 som
356 utsendelsesformat – og at vi har brukt og bruker flere andre
357 alternativer i våre tjenester. Ulike «devicer» har ofte behov for
358 forskjellige løsninger – og NRK har forsøkt å levere med best mulig
359 kvalitet /økonomi /stabilitet avhengig av
360 plattform. Produksjonsformater i NRK spenner for øvrig over en rekke
361 forskjellige formater – hvor MPEG4 bare er en av disse. Når NRK kjøper
362 teknisk utstyr er betaling for kodekstøtte ofte en del av
363 anskaffelsesprisen for denne maskinvaren (enten dette er spesialiserte
364 enkodere eller forskjellige typer produksjonsutstyr).</p>
365
366 <p>Vennlig hilsen
367 <br>Geir Børdalen</p>
368
369 <p>________________________________________
370 <br>Geir Børdalen
371 <br>Investeringsansvarlig NRK / Hovedprosjektleder - Origo
372 <br>Avdeling for utvikling, innovasjon, investering og eiendom
373 <br>NRK medietjenester
374 <br>Sentralbord: +47 23 04 70 00
375 <br>Post: NRK, AUTV (RBM5), Pb. 8500 Majorstuen, 0340 Oslo
376 <br>nrk.no
377 </blockquote></p>
378
379 <p>Et godt og grundig svar, som var informativt om hvordan NRK tenker
380 rundt patentavtale med MPEG LA, men heller ikke helt besvarte det jeg
381 lurte på, så jeg sendte epostoppfølging samme dag.</p>
382
383 <p><blockquote>
384 <p>[Geir Børdalen]
385 <br>> Hei Petter Reinholdtsen</p>
386
387 <p>Hei, og takk for raskt svar. Er min henvendelse journalført slik
388 at den dukker opp i NRKs postjournal?</p>
389
390 <p>Svaret ditt var meget nyttig, og jeg forstår ut fra det du skriver
391 at avklaringen med MPEG LA rundt H.264-distribusjon via bakkenettet
392 gjelder alle TV-kanaler i Norge. Hvilke saksnummer fikk dokumenter
393 som ble opprettet i forbindelse med det omtalte møtet NRK v/Hellgren
394 og EBU hadde med MPEG LA (dvs. referater, avtaler, etc),
395 f.eks. dokumentet der formuleringen "in full" som du omtaler
396 finnes?<p>
397
398 <p>Men det er et par ting jeg fortsatt ikke forstår. Det ene er
399 hvorfor NRKs forståelse av hva "Internet Broadcast AVC Video" dekker
400 ser ut til å avvike fra det som presenteres i
401 <a href="http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf">lysark
402 fra MPEG LA</a> i mai, der MPEG LA på lysark med overskriften
403 "AVC/H.264 License Terms Participation Fees" og undertittel "Where
404 remuneration is from other sources" skriver "Internet Broadcast AVC
405 Video (not title-by-title, not subscription) – no royalty for life of
406 the AVC Patent Portfolio License".</p>
407
408 <p>Her leser jeg MPEG LA dithen at det kun er kringkasting uten
409 abonnement via Internet som er dekket at vilkårne omtalt i
410 pressemeldingen, mens jeg forstår deg dithen at NRK mener NRKs
411 nettsider som også har enkeltfilmer og innslag (som jeg forstår dekket
412 av formuleringen "title-by-title") dekkes av "Internet Broadcast AVC
413 Video" fra MPEG LA. Hva baserer dere denne tolkningen på? Jeg har
414 ikke sett noe skriftlig fra MPEG LA som støtter NRKs tolkning, og
415 lurer på om dere har andre kilder enn den pressemeldingen fra 5 år
416 tilbake, der NRKS forståelse av hva "Internet Broadcast AVC Video"
417 dekker er beskrevet?</p>
418
419 <p>Det andre er at eposten din ikke nevnte spørsmålet mitt om
420 bruksvilkårene til videoredigeringsverktøyene som NRK bruker. Disse
421 har som tidligere nevnt krav om at de kun skal brukes til private og
422 ikke-kommersielle formål med mindre en har avtale med MPEG LA, og uten
423 avtale med MPEG LA kan det jo virke som om NRK bruker verktøyene i
424 strid med bruksvilkårene. Hva gjør at disse bruksvilkårene ikke
425 gjelder for NRK?</p>
426 </blockquote></p>
427
428 <p>Noen minutter senere får jeg foreløpig siste svar i
429 føljetongen:</p>
430
431 <p><blockquote>
432 <p>Hei igjen</p>
433
434 <p>Vårt dokumentarkiv har fått en kopi (journalføringsnr kan jeg
435 dessverre ikke gi deg).<p>
436
437 <p>> Svaret ditt var meget nyttig, og jeg forstår ut fra det du
438 <br>> skriver at avklaringen med MPEG LA rundt H.264-distribusjon via
439 <br>> bakkenettet gjelder alle TV-kanaler i Norge.</p>
440
441 <p>Svar: Kan ikke svare for andre enn for NRK/EBU - og for bakkenettet
442 i Norge er det kun NRK som er et lisensbasert selskap. Kan ikke gi noe
443 svar på saksnr på dokumenter eller ytterligere informasjon da jeg selv
444 ikke var del i dette.</p>
445
446 <p>> Men det er et par ting jeg fortsatt ikke forstår. ...</p>
447
448 <p>Svar: Kan ikke gå ytterligere inn i dette fra min side og mitt
449 fagfelt som er produksjon/publisering og systemstrukturene bak
450 disse. For øvrig ligger det etter vår formening ingen begrensninger
451 for NRK i mulighetene til publisering mht til kodek i
452 produksjonssystemer. Som tidligere skrevet mener vi at NRK ikke
453 trenger noen avtale med MPEG LA og støtter oss til det vi allerede har
454 kommunisert i forrige epost.</p>
455
456 <p>Mvh
457 <br>Geir Børdalen</p>
458 </blockquote></p>
459
460 <p>Det syntes vanskelig å komme videre når NRK ikke ønsker å gå inn i
461 problemstillingen rundt bruksvilkårene til videoredigeringsverktøyene
462 NRK bruker, så jeg sendte takk for svarene og avsluttet utvekslingen
463 så langt:</p>
464
465 <p><blockquote>
466 <p>Tusen takk for rask respons, og oppklarende forklaring om hvordan
467 NRK tenker rundt MPEG LA.</p>
468
469 <p>Jeg vil høre med NRK-arkivet for å se om de kan spore opp de
470 omtalte dokumentene. Jeg setter pris på om du kan dele titler, dato
471 eller annen informasjon som kan gjøre det enklere for arkivet å finne
472 dem.</p>
473
474 <p>Når det gjelder hvordan bruksvilkårene til
475 videoredigeringsverktøyene skal tolkes, så skal jeg høre med MPEG LA
476 og produsentene av verktøyene for å forsøke å få klarhet i hva de
477 mener er rikgig rettstilstand.</p>
478 </blockquote></p>
479
480 <p>Jeg ble litt klokere, men fortsatt er det uklart for meg hva som er
481 grunnlaget til NRK for å se bort fra bruksvilkår i
482 videoredigeringsprogramvare som krever MPEG LA-avtale til alt annet
483 enn privat og ikke-kommersiell bruk.</p>
484 </div>
485 <div class="tags">
486
487
488 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
489
490
491 </div>
492 </div>
493 <div class="padding"></div>
494
495 <div class="entry">
496 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Blir_det_virkelig_krav_om_fingeravtrykk_i_nasjonale_ID_kort_.html">Blir det virkelig krav om fingeravtrykk i nasjonale ID-kort?</a></div>
497 <div class="date">12th May 2015</div>
498 <div class="body"><p>Noen finner det vanskelig å tro at Stortinget faktisk har vedtatt å
499 kreve at alle norske borgerne må avgi fingeravtrykk til politiet for å
500 fungere i samfunnet. Jeg er blitt spurt hva som er grunnlaget for
501 <a href="http://people.skolelinux.org/pere/blog/Norwegian_citizens_now_required_by_law_to_give_their_fingerprint_to_the_police.html">min
502 påstand i forrige bloggpost</a> om at det nå blir krav om å avgi
503 fingeravtrykk til politiet for å fungere som borger i Norge. De som
504 spør klarer ikke lese det ut fra det som er vedtatt. Her er en liten
505 oppsummering om hva jeg baserer det på. Det sies ikke direkte i
506 hverken proposisjon, innstilling eller vedtak, men fremgår når en ser
507 på indirekte formuleringer.</p>
508
509 <p>I
510 <a href="https://www.regjeringen.no/nb/dokumenter/prop.-66-l-2014-2015/id2399703/">stortingsproposisjon
511 66</a>, avsnitt 6.3.5 (Avgivelse av biometriske personopplysninger)
512 står det<p>
513
514 <p><blockquote>
515
516 <p>Departementet foreslår at både ansiktsfoto og fingeravtrykk skal
517 kunne opptas og lagres som identifikasjonsdata i de nasjonale
518 ID-kortene, på samme måte som i passene. Lovforslaget er derfor
519 utformet i tråd med passloven § 6 annet ledd, som fastslår at det
520 til bruk for senere verifisering eller kontroll av passinnehaverens
521 identitet kan innhentes og lagres i passet biometrisk
522 personinformasjon i form av ansiktsfoto og fingeravtrykk (to
523 fingre). Dagens ordning med lagring av ansiktsfoto og fingeravtrykk
524 i et kontaktløst smartkort i passet er basert på internasjonale
525 standarder. Fingeravtrykkene i nasjonalt ID-kort vil bli beskyttet
526 på samme måte som fingeravtrykkene i passene.</p>
527
528 <p>[...]</p>
529
530 <p>For norske forhold understreker departementet at innføring av
531 nasjonale ID-kort sammen med innføring av nye systemer for sikrere
532 utstedelse og kontroll av pass og relaterte dokumenter gir mulighet
533 til å utforme ordningen slik at den best mulig møter utfordringene
534 forbundet med identitetskriminalitet. Det tilsier at fingeravtrykk
535 opptas og lagres i alle nasjonale ID-kort.</p>
536 </blockquote></p>
537
538 <p>Departementet sier altså at sin anbefaling er at fingeravtrykk skal
539 opptas og lagres i alle nasjonale ID-kort. Det skrives som om det
540 blir valgfritt, på samme måten som det skrives passloven, der det i
541 loven sier at det kan
542 «<a href="https://lovdata.no/dokument/NL/lov/1997-06-19-82#§6">innhentes
543 og lagres i passet biometrisk personinformasjon i form av ansiktsfoto
544 og fingeravtrykk (to fingre)</a>». Men på tross av bruken av «kan» i
545 passloven er det innført krav om å avgi fingeravtrykk for å få et pass
546 i Norge. Proposisjonen sier i tillegg i del 1 (Proposisjonens
547 hovedinnhold) at ID-kortene skal være like pålitelig som pass og ha
548 samme sikkerhetsnivå som pass. Departementet foreslår altså at
549 ID-kortene skal gis etter samme regler som for pass.</p>
550
551 <p>Formuleringene fra hovedinnholdet i proposisjonen er videreført i
552 <a href="https://www.stortinget.no/no/Saker-og-publikasjoner/Publikasjoner/Innstillinger/Stortinget/2014-2015/inns-201415-243/?lvl=0">innstillingen
553 fra stortingskomiteen</a>, der det konkret står «De foreslåtte reglene
554 vil gi befolkningen tilbud om et offentlig utstedt identitetsbevis som
555 vil være like pålitelig som passet, og mer praktisk å bruke som
556 legitimasjon» og «Det nasjonale ID-kortet skal også holde samme
557 sikkerhetsnivå som passet». Komiteen har altså ingen kommentarer
558 eller innsigelser til dette forslaget, og gjorde i debatten da saken
559 ble vedtatt det klart at dette var en god sak og at en enstemmig
560 komité var glad for resultatet. Stortinget har dermed stilt seg helt
561 og fullt bak departementets forslag.</p>
562
563 <p>For meg er det åpenbart når en leser proposisjonen at «like
564 pålitelig» og «samme sikkerhetsnivå» vil bli tolket av departementet
565 som «med samme biometrisk informasjon som i passene», og departementet
566 forklarer i tillegg i proposisjonen at de har tenkt at
567 fingeravtrykkene «vil bli beskyttet på samme måte som fingeravtrykkene
568 i passene». Jeg ser det dermed som åpenbart at den samme
569 tvangsinnhentingen av fingeravtrykk som gjelder for pass vil bli
570 viderført til de nasjonale ID-kortene.</p>
571
572 <p>Det eneste som kan endre dette er massive protester fra
573 befolkningen på at folk som ikke er mistenkt for noe kriminelt skal
574 tvinges til å gi fingeravtrykket til politiet for å f.eks. kunne få
575 bankkonto eller stemme ved valg. Det kunne få departementet til å
576 snu. Det tror jeg ikke vil skje.</p>
577 </div>
578 <div class="tags">
579
580
581 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
582
583
584 </div>
585 </div>
586 <div class="padding"></div>
587
588 <div class="entry">
589 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Norwegian_citizens_now_required_by_law_to_give_their_fingerprint_to_the_police.html">Norwegian citizens now required by law to give their fingerprint to the police</a></div>
590 <div class="date">10th May 2015</div>
591 <div class="body"><p>5 days ago, the Norwegian Parliament decided, unanimously, that all
592 citizens of Norway, no matter if they are suspected of something
593 criminal or not, are
594 <a href="https://www.holderdeord.no/votes/1430838871e">required to
595 give fingerprints to the police</a> (vote details from Holder de
596 ord). The law make it sound like it will be optional, but in a few
597 years there will be no option any more. The ID will be required to
598 vote, to get a bank account, a bank card, to change address on the
599 post office, to receive an electronic ID or to get a drivers license
600 and many other tasks required to function in Norway. The banks plan
601 to stop providing their own ID on the bank cards when this new
602 national ID is introduced, and the national road authorities plan to
603 change the drivers license to no longer be usable as identity cards.
604 In effect, to function as a citizen in Norway a national ID card will
605 be required, and to get it one need to provide the fingerprints to
606 the police.</p>
607
608 <p>In addition to handing the fingerprint to the police (which
609 promised to not make a copy of the fingerprint image at that point in
610 time, but say nothing about doing it later), a picture of the
611 fingerprint will be stored on the RFID chip, along with a picture of
612 the face and other information about the person. Some of the
613 information will be encrypted, but the encryption will be the same
614 system as currently used in the passports. The codes to decrypt will
615 be available to a lot of government offices and their suppliers around
616 the globe, but for those that do not know anyone in those circles it
617 is good to know that
618 <a href="http://www.theguardian.com/technology/2006/nov/17/news.homeaffairs">the
619 encryption is already broken</a>. And they
620 <a href="http://www.networkworld.com/article/2215057/wireless/bad-guys-could-read-rfid-passports-at-217-feet--maybe-a-lot-more.html">can
621 be read from 70 meters away</a>. This can be mitigated a bit by
622 keeping it in a Faraday cage (metal box or metal wire container), but
623 one will be required to take it out of there often enough to expose
624 ones private and personal information to a lot of people that have no
625 business getting access to that information.</p>
626
627 <p>The new Norwegian national IDs are a vehicle for identity theft,
628 and I feel sorry for us all having politicians accepting such invasion
629 of privacy without any objections. So are the Norwegian passports,
630 but it has been possible to function in Norway without those so far.
631 That option is going away with the passing of the new law. In this, I
632 envy the Germans, because for them it is optional how much biometric
633 information is stored in their national ID.</p>
634
635 <p>And if forced collection of fingerprints was not bad enough, the
636 information collected in the national ID card register can be handed
637 over to foreign intelligence services and police authorities, "when
638 extradition is not considered disproportionate".</p>
639
640 <p>Update 2015-05-12: For those unable to believe that the Parliament
641 really could make such decision, I wrote
642 <a href="http://people.skolelinux.org/pere/blog/Blir_det_virkelig_krav_om_fingeravtrykk_i_nasjonale_ID_kort_.html">a
643 summary of the sources I have</a> for concluding the way I do
644 (Norwegian Only, as the sources are all in Norwegian).</p>
645 </div>
646 <div class="tags">
647
648
649 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
650
651
652 </div>
653 </div>
654 <div class="padding"></div>
655
656 <div class="entry">
657 <div class="title"><a href="http://people.skolelinux.org/pere/blog/What_would_it_cost_to_store_all_phone_calls_in_Norway_.html">What would it cost to store all phone calls in Norway?</a></div>
658 <div class="date"> 1st May 2015</div>
659 <div class="body"><p>Many years ago, a friend of mine calculated how much it would cost
660 to store the sound of all phone calls in Norway, and came up with the
661 cost of around 20 million NOK (2.4 mill EUR) for all the calls in a
662 year. I got curious and wondered what the same calculation would look
663 like today. To do so one need an idea of how much data storage is
664 needed for each minute of sound, how many minutes all the calls in
665 Norway sums up to, and the cost of data storage.</p>
666
667 <p>The 2005 numbers are from
668 <a href="http://www.digi.no/analyser/2005/10/04/vi-prater-stadig-mindre-i-roret">digi.no</a>,
669 the 2012 numbers are from
670 <a href="http://www.nkom.no/aktuelt/nyheter/fortsatt-vekst-i-det-norske-ekommarkedet">a
671 NKOM report</a>, and I got the 2013 numbers after asking NKOM via
672 email. I was told the numbers for 2014 will be presented May 20th,
673 and decided not to wait for those, as I doubt they will be very
674 different from the numbers from 2013.</p>
675
676 <p>The amount of data storage per minute sound depend on the wanted
677 quality, and for phone calls it is generally believed that 8 Kbit/s is
678 enough. See for example a
679 <a href="http://www.cisco.com/c/en/us/support/docs/voice/voice-quality/7934-bwidth-consume.html#topic1">summary
680 on voice quality from Cisco</a> for some alternatives. 8 Kbit/s is 60
681 Kbytes/min, and this can be multiplied with the number of call minutes
682 to get the storage requirements.</p>
683
684 <p>Storage prices varies a lot, depending on speed, backup strategies,
685 availability requirements etc. But a simple way to calculate can be
686 to use the price of a TiB-disk (around 1000 NOK / 120 EUR) and double
687 it to take space, power and redundancy into account. It could be much
688 higher with high speed and good redundancy requirements.</p>
689
690 <p>But back to the question, What would it cost to store all phone
691 calls in Norway? Not much. Here is a small table showing the
692 estimated cost, which is within the budget constraint of most medium
693 and large organisations:</p>
694
695 <table border="1">
696 <tr><th>Year</th><th>Call minutes</th><th>Size</th><th>Price in NOK / EUR</th></tr>
697 <tr><td>2005</td><td align="right">24 000 000 000</td><td align="right">1.3 PiB</td><td align="right">3 mill / 358 000</td></tr>
698 <tr><td>2012</td><td align="right">18 000 000 000</td><td align="right">1.0 PiB</td><td align="right">2.2 mill / 262 000</td></tr>
699 <tr><td>2013</td><td align="right">17 000 000 000</td><td align="right">950 TiB</td><td align="right">2.1 mill / 250 000</td></tr>
700 </table>
701
702 <p>This is the cost of buying the storage. Maintenance need to be
703 taken into account too, but calculating that is left as an exercise
704 for the reader. But it is obvious to me from those numbers that
705 recording the sound of all phone calls in Norway is not going to be
706 stopped because it is too expensive. I wonder if someone already is
707 collecting the data?</p>
708 </div>
709 <div class="tags">
710
711
712 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
713
714
715 </div>
716 </div>
717 <div class="padding"></div>
718
719 <div class="entry">
720 <div class="title"><a href="http://people.skolelinux.org/pere/blog/First_Jessie_based_Debian_Edu_beta_release.html">First Jessie based Debian Edu beta release</a></div>
721 <div class="date">26th April 2015</div>
722 <div class="body"><p>I am happy to report that the Debian Edu team sent out
723 <a href="https://lists.debian.org/debian-edu-announce/2015/04/msg00000.html">this
724 announcement today</a>:</p>
725
726 <pre>
727 the Debian Edu / Skolelinux project is pleased to announce the first
728 *beta* release of Debian Edu "Jessie" 8.0+edu0~b1, which for the first
729 time is composed entirely of packages from the current Debian stable
730 release, Debian 8 "Jessie".
731
732 (As most reading this will know, Debian "Jessie" hasn't actually been
733 released by now. The release is still in progress but should finish
734 later today ;)
735
736 We expect to make a final release of Debian Edu "Jessie" in the coming
737 weeks, timed with the first point release of Debian Jessie. Upgrades
738 from this beta release of Debian Edu Jessie to the final release will
739 be possible and encouraged!
740
741 Please report feedback to debian-edu@lists.debian.org and/or submit
742 bugs: http://wiki.debian.org/DebianEdu/HowTo/ReportBugs
743
744 Debian Edu - sometimes also known as "Skolelinux" - is a complete
745 operating system for schools, universities and other
746 organisations. Through its pre- prepared installation profiles
747 administrators can install servers, workstations and laptops which
748 will work in harmony on the school network. With Debian Edu, the
749 teachers themselves or their technical support staff can roll out a
750 complete multi-user, multi-machine study environment within hours or
751 days.
752
753 Debian Edu is already in use at several hundred schools all over the
754 world, particularly in Germany, Spain and Norway. Installations come
755 with hundreds of applications pre-installed, plus the whole Debian
756 archive of thousands of compatible packages within easy reach.
757
758 For those who want to give Debian Edu Jessie a try, download and
759 installation instructions are available, including detailed
760 instructions in the manual explaining the first steps, such as setting
761 up a network or adding users. Please note that the password for the
762 user your prompted for during installation must have a length of at
763 least 5 characters!
764
765 == Where to download ==
766
767 A multi-architecture CD / usbstick image (649 MiB) for network booting
768 can be downloaded at the following locations:
769
770 http://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~b1-CD.iso
771 rsync -avzP ftp.skolelinux.org::skolelinux-cd/debian-edu-8.0+edu0~b1-CD.iso .
772
773 The SHA1SUM of this image is: 54a524d16246cddd8d2cfd6ea52f2dd78c47ee0a
774
775 Alternatively an extended DVD / usbstick image (4.9 GiB) is also
776 available, with more software included (saving additional download
777 time):
778
779 http://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~b1-USB.iso
780 rsync -avzP ftp.skolelinux.org::skolelinux-cd/debian-edu-8.0+edu0~b1-USB.iso
781
782 The SHA1SUM of this image is: fb1f1504a490c077a48653898f9d6a461cb3c636
783
784 Sources are available from the Debian archive, see
785 http://ftp.debian.org/debian-cd/8.0.0/source/ for some download
786 options.
787
788 == Debian Edu Jessie manual in seven languages ==
789
790 Please see https://wiki.debian.org/DebianEdu/Documentation/Jessie/ for
791 the English version of the Debian Edu jessie manual.
792
793 This manual has been fully translated to German, French, Italian,
794 Danish, Dutch and Norwegian Bokmål. A partly translated version exists
795 for Spanish. See http://maintainer.skolelinux.org/debian-edu-doc/ for
796 online version of the translated manual.
797
798 More information about Debian 8 "Jessie" itself is provided in the
799 release notes and the installation manual:
800 - http://www.debian.org/releases/jessie/releasenotes
801 - http://www.debian.org/releases/jessie/installmanual
802
803
804 == Errata / known problems ==
805
806 It takes up to 15 minutes for a changed hostname to be updated via
807 DHCP (#780461).
808
809 The hostname script fails to update LTSP server hostname (#783087).
810
811 Workaround: run update-hostname-from-ip on the client to update the
812 hostname immediately.
813
814 Check https://wiki.debian.org/DebianEdu/Status/Jessie for a possibly
815 more current and complete list.
816
817 == Some more details about Debian Edu 8.0+edu0~b1 Codename Jessie released 2015-04-25 ==
818
819 === Software updates ===
820
821 Everything which is new in Debian 8 Jessie, e.g.:
822
823 * Linux kernel 3.16.7-ctk9; for the i386 architecture, support for
824 i486 processors has been dropped; oldest supported ones: i586 (like
825 Intel Pentium and AMD K5).
826
827 * Desktop environments KDE Plasma Workspaces 4.11.13, GNOME 3.14,
828 Xfce 4.12, LXDE 0.5.6
829 * new optional desktop environment: MATE 1.8
830 * KDE Plasma Workspaces is installed by default; to choose one of
831 the others see the manual.
832 * the browsers Iceweasel 31 ESR and Chromium 41
833 * LibreOffice 4.3.3
834 * GOsa 2.7.4
835 * LTSP 5.5.4
836 * CUPS print system 1.7.5
837 * new boot framework: systemd
838 * Educational toolbox GCompris 14.12
839 * Music creator Rosegarden 14.02
840 * Image editor Gimp 2.8.14
841 * Virtual stargazer Stellarium 0.13.1
842 * golearn 0.9
843 * tuxpaint 0.9.22
844 * New version of debian-installer from Debian Jessie.
845 * Debian Jessie includes about 43000 packages available for installation.
846 * More information about Debian 8 Jessie is provided in its release
847 notes and the installation manual, see the link above.
848
849 === Installation changes ===
850
851 Installations done via PXE now also install firmware automatically
852 for the hardware present.
853
854 === Fixed bugs ===
855
856 A number of bugs have been fixed in this release; the most noticeable
857 from a user perspective:
858
859 * Inserting incorrect DNS information in Gosa will no longer break
860 DNS completely, but instead stop DNS updates until the incorrect
861 information is corrected (710362)
862
863 * shutdown-at-night now shuts the system down if gdm3 is used (775608).
864
865 === Sugar desktop removed ===
866
867 As the Sugar desktop was removed from Debian Jessie, it is also not
868 available in Debian Edu jessie.
869
870
871 == About Debian Edu / Skolelinux ==
872
873 Debian Edu, also known as Skolelinux, is a Linux distribution based on
874 Debian providing an out-of-the box environment of a completely
875 configured school network. Directly after installation a school server
876 running all services needed for a school network is set up just
877 waiting for users and machines being added via GOsa², a comfortable
878 Web-UI. A netbooting environment is prepared using PXE, so after
879 initial installation of the main server from CD or USB stick all other
880 machines can be installed via the network. The provided school server
881 provides LDAP database and Kerberos authentication service,
882 centralized home directories, DHCP server, web proxy and many other
883 services. The desktop contains more than 60 educational software
884 packages and more are available from the Debian archive, and schools
885 can choose between KDE, GNOME, LXDE, Xfce and MATE desktop
886 environment.
887
888 == About Debian ==
889
890 The Debian Project was founded in 1993 by Ian Murdock to be a truly
891 free community project. Since then the project has grown to be one of
892 the largest and most influential open source projects. Thousands of
893 volunteers from all over the world work together to create and
894 maintain Debian software. Available in 70 languages, and supporting a
895 huge range of computer types, Debian calls itself the universal
896 operating system.
897
898 == Thanks ==
899
900 Thanks to everyone making Debian and Debian Edu / Skolelinux happen!
901 You rock.
902 </pre>
903 </div>
904 <div class="tags">
905
906
907 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
908
909
910 </div>
911 </div>
912 <div class="padding"></div>
913
914 <div class="entry">
915 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Shirish_Agarwal.html">Debian Edu interview: Shirish Agarwal</a></div>
916 <div class="date">15th April 2015</div>
917 <div class="body"><p>It was a surprise to me to learn that project to create a complete
918 computer system for schools I've involved in,
919 <a href="http://www.skolelinux.org/">Debian Edu / Skolelinux</a>, was
920 being used in India. But apparently it is, and I managed to get an
921 interview with one of the friends of the project there, Shirish
922 Agarwal.</p>
923
924 <p><strong>Who are you, and how do you spend your days?</strong></p>
925
926 <p>My name is Shirish Agarwal. Based out of the educational and
927 historical city of Pune, from the western state of Maharashtra, India.
928 My bread comes from giving training, giving policy tips,
929 installations on free software to mom and pop shops in different
930 fields from Desktop publishing to retail shops as well as work with
931 few software start-ups as well.</p>
932
933 <p><strong>How did you get in contact with the Skolelinux / Debian Edu
934 project?</strong></p>
935
936 <p>It started innocently enough. I have been using Debian for a few
937 years and in one local minidebconf / debutsav I was asked if there was
938 anything for schools or education. I had worked / played with free
939 educational softwares such as Gcompris and Stellarium for my many
940 nieces and nephews so researched and found Debian Edu or Skolelinux as
941 it was known then. Since then I have started using the various
942 education meta-packages provided by the project.</p>
943
944 <p><strong>What do you see as the advantages of Skolelinux / Debian
945 Edu?</strong></p>
946
947 <p>It's closest I have seen where a package full of educational
948 software are packed, which are free and open (both literally and
949 figuratively). Even if I take the simplest software which is
950 gcompris, the number of activities therein are amazing. Another one of
951 the softwares that I have liked for a long time is stellarium. Even
952 pysycache is cool except for couple of issues I encountered
953 <a href="https://bugs.debian.org/781841">#781841</a> and
954 <a href="https://bugs.debian.org/781842">#781842</a>.</p>
955
956 <p>I prefer software installed on the system over web based solutions,
957 as a web site can disappear any time but the software on disk has the
958 possibility of a larger life span. Of course with both it's more a
959 question if it has enough users who make it fun or sustainable or both
960 for the developer per-se.</p>
961
962 <p><strong>What do you see as the disadvantages of Skolelinux / Debian
963 Edu?</strong></p>
964
965 <p>I do see that the Debian Edu team seems to be short-handed and I
966 think more efforts should be made to make it popular and ask and take
967 help from people and the larger community wherever possible.</p>
968
969 <p>I don't see any disadvantage to use Skolelinux apart from the fact
970 that most apps. are generic which is good or bad how you see it.
971 However, saying that I do acknowledge the fact that the canvas is
972 pretty big and there are lot of interesting ideas that could be done
973 but for reasons not known not done or if done I don't know about them.
974 Let me share some of the ideas (these are more upstream based but
975 still) I have had for a long time :</p>
976
977 <p>1. Classical maths question of two trains in opposing directions
978 each running @x kmph/mph at y distance, when they will meet and how
979 far would each travel and similar questions like these.
980
981 <p>The computer is a fantastic system where questions like these can
982 be drawn, animated and the methodology and answers teased out in
983 interactive manner. While sites such as the
984 <a href="http://mathforum.org/dr.math/faq/faq.two.trains.html">Ask
985 Dr. Math FAQ on The Two Trains problem</a> (as an example or point of
986 inspiration) can be used there is lot more that can be done. I dunno
987 if there is a free software which does something like this. The idea
988 being a blend of objects + animation + interaction which does
989 this. The whole interaction could be gamified with points or sounds or
990 colourful celebration whenever the user gets even part of the question
991 or/and methodology right. That would help reinforce good behaviour.
992 This understanding could be used to share/showcase everything from how
993 the first wheel came to be, to evolution to how astronomy started,
994 psychics and everything in-between.</p>
995
996 <p>One specific idea in the train part was having the Linux mascot on
997 one train and the BSD or GNU mascot on the other train and they
998 meeting somewhere in-between. Characters from blender movies could
999 also be used.</p>
1000
1001 <p>2. Loads of crossword-puzzles with reference to subjects: We have
1002 enormous data sets in Wikipedia and Wikitionary. I don't think it
1003 should be a big job to design crossword puzzles. Using categories and
1004 sub-categories it should be doable to have Q&A single word answers
1005 from the existing data-sets. What would make it easy or hard could be
1006 the length of the word + existence of many or few vowels depending on
1007 the user's input.</p>
1008
1009 <p>3. Jigsaw puzzles - We already have a great software called
1010 palapeli with number of slicers making it pretty interesting. What
1011 needs to be done is to download large number of public domain and
1012 copyleft images, tease and use IPTC tags to categorise them into
1013 nature, history etc. and let it loose. This could turn to be really
1014 huge collection of images. One source could be taken from
1015 commons.wikimedia.org, others could be huge collection of royalty-free
1016 stock photos. Potential is immense.</p>
1017
1018 <p>Apart from this, free software suffers in two directions, we lag
1019 both in development (of using new features per-se) and maintenance a
1020 lot. This is more so in educational software as these applications
1021 need to be timely and the opportunity cost of missing deadlines is
1022 immense. If we are able to solve issues of funding for development and
1023 maintenance of such software I don't see any big difficulties. I know
1024 of few start-ups in and around India who would love to develop and
1025 maintain such software if funding issues could be solved.</p>
1026
1027 <p><strong>Which free software do you use daily?</strong></p>
1028
1029 <p>That would be huge list. Some of the softwares are obviously apt,
1030 aptitude, debdelta, leafpad, the shell of course (zsh nowadays),
1031 quassel for IRC. In games I use shisen-sho while card-games are evenly
1032 between kpat and Aiselriot. In desktops it's a tie between
1033 gnome-flashback and mate.</p>
1034
1035 <p><strong>Which strategy do you believe is the right one to use to
1036 get schools to use free software?</strong></p>
1037
1038 <p>I think it should first start with using specific FOSS apps. in
1039 whatever environment they are. If it's MS-Windows or Mac so be it.
1040 Once they are habitual with the apps. and there is buy-in from the
1041 school management then it could be installed anywhere. Most of the
1042 people now understand the concept of a repository because of the
1043 various online stores so it isn't hard to convince on that front.</p>
1044
1045 <p>What is harder is having enough people with technical skills and
1046 passion to service them. If you get buy-in from one or two teachers
1047 then ideas like above could also be asked to be done as a project as
1048 well.</p>
1049
1050 <p>I think where we fall short more than anything is in marketing. For
1051 instance, Debian has this whole range of fonts in its archive but
1052 there isn't even a page where all those different fonts in the La
1053 Ipsum format could be tried out for newcomers.</p>
1054
1055 <p>One of the issues faced constantly in installations is with updates
1056 and upgrades. People have this myth that each update and upgrade
1057 means the user interface will / has to change. I have seen this
1058 innumerable times. That perhaps is one of the reasons which browsers
1059 like Iceweasel / Firefox change user interfaces so much, not because
1060 it might be needed or be functional but because people believe that
1061 changed user interfaces are better. This, can easily be pointed with
1062 the user interfaces changed with almost every MS-Windows and Mac OS
1063 releases.</p>
1064
1065 <p>The problems with Debian Edu for deployment are many. The biggest
1066 is the huge gap between what is taught in schools and what Debian Edu
1067 is aimed at.
1068
1069 <p>Me and my friends did teach on week-ends in a government school for
1070 around 2 years, and
1071 <a href="https://flossexperiences.wordpress.com/2012/10/08/sharings/">gathered
1072 some experience</a> there. Some of the things we learnt/discovered
1073 there was :</p>
1074
1075 <ol>
1076
1077 <li>Most of the teachers are very territorial about their subjects
1078 and they do not want you to teach anything out of the
1079 portion/syllabus given.</li>
1080
1081 <li>They want any activity on the system in accordance to whatever
1082 is in the syllabus.</li>
1083
1084 <li>There are huge barriers both with the English language and at
1085 times with objects or whatever. An example, let's say in gcompris
1086 you have objects falling down and you have to name them and let's
1087 say the falling object is a hat or a fedora hat, this would not be
1088 as recognizable as say a
1089 <a href="https://en.wikipedia.org/wiki/Puneri_Pagadi">Puneri
1090 Pagdi</a> so there is need to inject local objects, words wherever
1091 possible. Especially for word-games there are so many hindi words
1092 which have become part of english vocabulary (for instance in
1093 parley), those could be made into a hinglish collection or
1094 something but that is something for upstream to do.</li>
1095
1096 </ol>
1097 </div>
1098 <div class="tags">
1099
1100
1101 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju</a>.
1102
1103
1104 </div>
1105 </div>
1106 <div class="padding"></div>
1107
1108 <div class="entry">
1109 <div class="title"><a href="http://people.skolelinux.org/pere/blog/I_m_going_to_the_Open_Source_Developers__Conference_Nordic_2015_.html">I'm going to the Open Source Developers' Conference Nordic 2015!</a></div>
1110 <div class="date"> 7th April 2015</div>
1111 <div class="body"><p>I am happy to let you all know that I'm going to the <a
1112 href="http://act.osdc.no/osdc2015no/">Open Source Developers'
1113 Conference Nordic 2015</a>!</p>
1114
1115 <p>It take place Friday 8th to Sunday 10th of May in Oslo next to
1116 where I work, and I finally got around to submitting
1117 <a href="http://act.osdc.no/osdc2015no/talk/6192">a talk proposal for
1118 it</a> (dead link for most people until the talk is accepted). As
1119 part of my involvement with the
1120 <a href="http://www.nuug.no/">Norwegian Unix User Group member
1121 association</a> I have been slightly involved in the planning of this
1122 conference for a while now, with a focus on organising a Civic Hacking
1123 Hackathon with our friends
1124 over at <a href="http://www.mysociety.org/">mySociety</a> and
1125 <a href="http://www.holderdeord.no/">Holder de ord</a>. This part is
1126 named the 'My Society' track in the program. There is still space for
1127 more talks and participants. I hope to see you there.</p>
1128
1129 <p>Check out <a href="http://act.osdc.no/osdc2015no/talks">the talks
1130 submitted and accepted so far</a>.</p>
1131 </div>
1132 <div class="tags">
1133
1134
1135 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>.
1136
1137
1138 </div>
1139 </div>
1140 <div class="padding"></div>
1141
1142 <div class="entry">
1143 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Proof_reading_the_Norwegian_translation_of_Free_Culture_by_Lessig.html">Proof reading the Norwegian translation of Free Culture by Lessig</a></div>
1144 <div class="date"> 4th April 2015</div>
1145 <div class="body"><p>During eastern I had some time to continue working on the Norwegian
1146 <a href="http://www.docbook.org/">docbook</a> version of the 2004 book
1147 <a href="http://free-culture.cc/">Free Culture</a> by Lawrence Lessig.
1148 At the moment I am proof reading the finished text, looking for typos,
1149 inconsistent wordings and sentences that do not flow as they should.
1150 I'm more than two thirds done with the text, and welcome others to
1151 check the text up to chapter 13. The current status is available on the
1152 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">github</a>
1153 project pages. You can also check out the
1154 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.pdf?raw=true">PDF</a>,
1155 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/blob/master/archive/freeculture.nb.epub?raw=true">EPUB</a>
1156 and HTML version available in the
1157 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/tree/master/archive">archive
1158 directory</a>.</p>
1159
1160 <p>Please report typos, bugs and improvements to the github project if
1161 you find any.</p>
1162 </div>
1163 <div class="tags">
1164
1165
1166 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>.
1167
1168
1169 </div>
1170 </div>
1171 <div class="padding"></div>
1172
1173 <p style="text-align: right;"><a href="index.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS feed" width="36" height="14" /></a></p>
1174 <div id="sidebar">
1175
1176
1177
1178 <h2>Archive</h2>
1179 <ul>
1180
1181 <li>2015
1182 <ul>
1183
1184 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
1185
1186 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
1187
1188 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
1189
1190 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
1191
1192 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
1193
1194 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/06/">June (3)</a></li>
1195
1196 </ul></li>
1197
1198 <li>2014
1199 <ul>
1200
1201 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
1202
1203 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
1204
1205 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
1206
1207 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
1208
1209 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
1210
1211 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
1212
1213 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
1214
1215 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
1216
1217 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
1218
1219 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
1220
1221 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
1222
1223 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
1224
1225 </ul></li>
1226
1227 <li>2013
1228 <ul>
1229
1230 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
1231
1232 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
1233
1234 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
1235
1236 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
1237
1238 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
1239
1240 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
1241
1242 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
1243
1244 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
1245
1246 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
1247
1248 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
1249
1250 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1251
1252 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1253
1254 </ul></li>
1255
1256 <li>2012
1257 <ul>
1258
1259 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1260
1261 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1262
1263 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1264
1265 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1266
1267 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1268
1269 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
1270
1271 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
1272
1273 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
1274
1275 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
1276
1277 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
1278
1279 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
1280
1281 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
1282
1283 </ul></li>
1284
1285 <li>2011
1286 <ul>
1287
1288 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1289
1290 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1291
1292 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1293
1294 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1295
1296 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1297
1298 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1299
1300 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1301
1302 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1303
1304 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1305
1306 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1307
1308 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1309
1310 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1311
1312 </ul></li>
1313
1314 <li>2010
1315 <ul>
1316
1317 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1318
1319 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1320
1321 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1322
1323 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1324
1325 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1326
1327 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1328
1329 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1330
1331 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1332
1333 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1334
1335 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1336
1337 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1338
1339 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1340
1341 </ul></li>
1342
1343 <li>2009
1344 <ul>
1345
1346 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1347
1348 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1349
1350 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1351
1352 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1353
1354 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1355
1356 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1357
1358 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1359
1360 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1361
1362 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1363
1364 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1365
1366 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1367
1368 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1369
1370 </ul></li>
1371
1372 <li>2008
1373 <ul>
1374
1375 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1376
1377 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1378
1379 </ul></li>
1380
1381 </ul>
1382
1383
1384
1385 <h2>Tags</h2>
1386 <ul>
1387
1388 <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1389
1390 <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1391
1392 <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1393
1394 <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1395
1396 <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (8)</a></li>
1397
1398 <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (15)</a></li>
1399
1400 <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1401
1402 <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1403
1404 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (109)</a></li>
1405
1406 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (153)</a></li>
1407
1408 <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1409
1410 <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (15)</a></li>
1411
1412 <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (13)</a></li>
1413
1414 <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1415
1416 <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (279)</a></li>
1417
1418 <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
1419
1420 <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1421
1422 <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (15)</a></li>
1423
1424 <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
1425
1426 <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (15)</a></li>
1427
1428 <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (19)</a></li>
1429
1430 <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
1431
1432 <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (10)</a></li>
1433
1434 <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (19)</a></li>
1435
1436 <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1437
1438 <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
1439
1440 <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
1441
1442 <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1443
1444 <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1445
1446 <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (34)</a></li>
1447
1448 <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (262)</a></li>
1449
1450 <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (176)</a></li>
1451
1452 <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (17)</a></li>
1453
1454 <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1455
1456 <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (52)</a></li>
1457
1458 <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (86)</a></li>
1459
1460 <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1461
1462 <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1463
1464 <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1465
1466 <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
1467
1468 <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1469
1470 <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1471
1472 <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1473
1474 <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1475
1476 <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (41)</a></li>
1477
1478 <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1479
1480 <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1481
1482 <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (47)</a></li>
1483
1484 <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1485
1486 <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1487
1488 <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (33)</a></li>
1489
1490 <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (2)</a></li>
1491
1492 <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
1493
1494 <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1495
1496 <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (52)</a></li>
1497
1498 <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1499
1500 <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (36)</a></li>
1501
1502 </ul>
1503
1504
1505 </div>
1506 <p style="text-align: right">
1507 Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1508 </p>
1509
1510 </body>
1511 </html>