]> pere.pagekite.me Git - homepage.git/blob - blog/index.html
Generated.
[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/Hvor_godt_fungerer_Linux_klienter_mot_MS_Exchange_.html">Hvor godt fungerer Linux-klienter mot MS Exchange?</a></div>
24 <div class="date">26th November 2013</div>
25 <div class="body"><p>Jeg
26 <a href="http://people.skolelinux.org/pere/blog/_pent_m_te_p__onsdag_om_bruken_av_Microsoft_Exchange_ved_Universitetet_i_Oslo.html">skrev
27 i juni om protestene</a> på planene til min arbeidsplass,
28 <a href="http://www.uio.no/">Universitetet i Oslo</a>, om å gå bort fra
29 fri programvare- og åpne standardløsninger for å håndtere epost,
30 vekk fra IETF-standarden SIEVE for filtrering av epost og over til
31 godseide spesifikasjoner og epostsystemet Microsoft Exchange.
32 Protestene har fått litt ny omtale i media de siste dagene, i tillegg
33 til de oppslagene som kom i mai.</p>
34
35 <ul>
36
37 <li>2013-11-26 <a href="http://www.version2.dk/artikel/gigantisk-outlook-konvertering-moeder-protester-paa-universitet-55147">Gigantisk Outlook-konvertering møder protester på universitet</a> - versjon2.dk</li>
38
39 <li>2013-11-25
40 <a href="http://www.idg.no/computerworld/article279407.ece">Microsoft-protest
41 på Universitetet</a> - Computerworld</li>
42
43 <li>2013-11-25
44 <a href="http://www.uniforum.uio.no/nyheter/2013/11/uio-bor-bruke-apen-programvare.html">Kjemper
45 mot innføring av Microsoft Exchange på UiO</a> - Uniforum</li>
46
47 <li>2013-11-25
48 <a href="http://www.uniforum.uio.no/nyheter/2013/11/uio-utsetter-innforing-av-nytt-e-postsystem.html">Utsetter
49 innføring av nytt e-postsystem</a> - Uniforum</li>
50
51 <li>2013-05-29
52 <a href="http://universitas.no/nyhet/58462/forsvarer-nytt-it-system">Forsvarer
53 nytt IT-system</a> - Universitas</li>
54
55 <li>2013-05-23
56 <a href="http://www.uniforum.uio.no/nyheter/2013/05/uio-innforer-nytt-epost-og-kalendersystem.html">UiO
57 innfører nytt epost- og kalenderverktøy</a> - Uniforum</li>
58
59 <li>2013-05-22
60 <a href="http://universitas.no/nyhet/58424/protestgruppe-vil-stanse-it-system">Protestgruppe
61 vil stanse IT-system</a> - Universitas</li>
62
63 <li>2013-05-15
64 <a href="http://www.uniforum.uio.no/leserbrev/2013/uio-ma-ha-kontroll-over-sitt-eget-epostsystem.html">UiO
65 må ha kontroll over sitt eget epostsystem</a> - Uniforum</li>
66
67 </ul>
68
69 <p>Prosjektledelsen har fortalt at dette skal fungere like godt for
70 Linux-brukere som for brukere av Microsoft Windows og Apple MacOSX,
71 men jeg lurer på hva slags erfaringer Linux-brukere i eksisterende
72 miljøer som bruker MS Exchange har gjort. Hvis du har slik erfaring
73 hadet det vært veldig fint om du kan send et leserbrev til
74 <a href="http://www.uniforum.uio.no/">Uniforum</a> og fortelle om hvor
75 greit det er å bruke Exchange i kryss-platform-miljøer? De jeg har
76 snakket med sier en greit får lest e-posten sin hvis Exchange har
77 slått på IMAP-funksjonalitet, men at kalender og møtebooking ikke
78 fungerer godt for Linux-klienter. Jeg har ingen personlig erfaring å
79 komme med, så jeg er nysgjerrig på hva andre kan dele av erfaringer
80 med universitetet.</p>
81
82 <p>Mitt ankerpunkt mot å bytte ut fri programvare som fungerer godt
83 med godseid programvare er at en mister kontroll over egen
84 infrastruktur, låser seg inn i en løsning det vil bli dyrt å komme ut
85 av, uten at en får funksjonalitet en ikke kunne skaffet seg med fri
86 programvare, eventuelt videreutviklet med de pengene som brukes på
87 overgangen til MS Exchange. Personlig planlegger jeg å fortsette å
88 laste ned all eposten min til lokal maskin for indeksering og lesing
89 med <a href=="http://notmuchmail.org">notmuch</a>, så jeg håper jeg
90 ikke blir veldig skadelidende av overgangen.</p>
91
92 <p><a href="http://dinis.linguateca.pt/Diana/ImotMSUiO.html">Underskriftslista
93 for oss som er mot endringen</a>, som omtales i artiklene, er fortsatt
94 åpen for de som vil signere på oppropet. Akkurat nå er det 298
95 personer som har signert.</p>
96 </div>
97 <div class="tags">
98
99
100 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
101
102
103 </div>
104 </div>
105 <div class="padding"></div>
106
107 <div class="entry">
108 <div class="title"><a href="http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html">New chrpath release 0.15</a></div>
109 <div class="date">24th November 2013</div>
110 <div class="body"><p>After many years break from the package and a vain hope that
111 development would be continued by someone else, I finally pulled my
112 acts together this morning and wrapped up a new release of chrpath,
113 the command line tool to modify the rpath and runpath of already
114 compiled ELF programs. The update was triggered by the persistence of
115 Isha Vishnoi at IBM, which needed a new config.guess file to get
116 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
117 is working on. I checked the
118 <a href="http://packages.qa.debian.org/chrpath">Debian</a>,
119 <a href="https://launchpad.net/ubuntu/+source/chrpath">Ubuntu</a> and
120 <a href="https://admin.fedoraproject.org/pkgdb/acls/name/chrpath">Fedora</a>
121 packages for interesting patches (failed to find the source from
122 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
123 These are the release notes:</p>
124
125 <p>New in 0.15 released 2013-11-24:</p>
126
127 <ul>
128
129 <li>Updated config.sub and config.guess from the GNU project to work
130 with newer architectures. Thanks to isha vishnoi for the heads
131 up.</li>
132
133 <li>Updated README with current URLs.</li>
134
135 <li>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
136 Matthias Klose.</li>
137
138 <li>Added missing help for -k|--keepgoing option, using patch by
139 Petr Machata found in Fedora.</li>
140
141 <li>Rewrite removal of RPATH/RUNPATH to make sure the entry in
142 .dynamic is a NULL terminated string. Based on patch found in
143 Fedora credited Axel Thimm and Christian Krause.</li>
144
145 </ul>
146
147 <p>You can
148 <a href="https://alioth.debian.org/frs/?group_id=31052">download the
149 new version 0.15 from alioth</a>. Please let us know via the Alioth
150 project if something is wrong with the new release. The test suite
151 did not discover any old errors, so if you find a new one, please also
152 include a testsuite check.</p>
153 </div>
154 <div class="tags">
155
156
157 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
158
159
160 </div>
161 </div>
162 <div class="padding"></div>
163
164 <div class="entry">
165 <div class="title"><a href="http://people.skolelinux.org/pere/blog/RSS_kilde_for_friteksts_k_i_offentlige_anbud_hos_Doffin.html">RSS-kilde for fritekstsøk i offentlige anbud hos Doffin</a></div>
166 <div class="date">22nd November 2013</div>
167 <div class="body"><p>I fjor sommer lagde jeg en
168 <a href="http://people.skolelinux.org/pere/blog/SQL_database_med_anbud_publisert_p__Doffin.html">offentlig
169 tilgjengelig SQL-database over offentlig anbud</a> basert på skraping
170 av HTML-data fra Doffin. Den har stått og gått siden da, og har nå
171 ca. 28000 oppføringer. Jeg oppdaget da jeg tittet innom at noen
172 oppføringer var ikke blitt med, antagelig på grunn av at de fikk
173 tildelt sekvensnummer i Doffin en godt stund før de ble publisert,
174 slik at min nettsideskraper som fortsatte skrapingen der den slapp
175 sist ikke fikk dem med seg. Jeg har fikset litt slik at skraperen nå
176 ser litt tilbake i tid for å se om den har gått glipp av noen
177 oppføringer, og har skrapet på nytt fra midten av september 2013 og
178 fremover. Det bør dermed bli en mer komplett database for kommende
179 måneder. Hvis jeg får tid skal jeg forsøke å skrape "glemte" data fra
180 før midten av september 2013, men tør ikke garantere at det blir
181 prioritert med det første. </p>
182
183 <p>Men målet med denne bloggposten er å vise hvordan denne
184 Doffin-databasen kan brukes og integreres med en RSS-leser, slik at en
185 kan la datamaskinen holde et øye med Doffin-annonseringer etter
186 nøkkelord. En kan lage sitt eget søk ved å besøke
187 <ahref="https://classic.scraperwiki.com/docs/api?name=norwegian-doffin#sqlite">API-et
188 hos Scraperwiki</a>, velge format rss2 og så legge inn noe ala dette i
189 "query in SQL":</p>
190
191 <p><pre>
192 select title, scrapedurl as link, abstract as description,
193 publishdate as pubDate from 'swdata'
194 where abstract like '%linux%' or title like '%linux%'
195 order by seq desc limit 20
196 </pre></p>
197
198 <p>Dette vil søke opp alle anbud med ordet linux i oppsummering eller
199 tittel. En kan lage mer avanserte søk hvis en ønsker det. URL-en som
200 dukker opp nederst på siden kan en så gi til sin RSS-leser (jeg bruker
201 akregator selv), og så automatisk få beskjed hvis det dukker opp anbud
202 med det aktuelle nøkkelordet i teksten. Merk at kapasiteten og
203 ytelsen hos Scraperwiki er begrenset, så ikke be RSS-leseren hente ned
204 oftere enn en gang hver dag.</p>
205
206 <p>Du lurer kanskje på hva slags informasjon en kan få ut fra denne
207 databasen. Her er to RSS-kilder, med søkeordet
208 "<a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25linux%25'%20or%20title%20like%20'%25linux%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">linux</a>",
209 søkeordet
210 "<a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25fri%20programvare%25'%20or%20title%20like%20'%25fri%20programvare%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">fri
211 programvare</a>"
212 og søkeordet
213 "<a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25odf%25'%20or%20title%20like%20'%25odf%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">odf</a>".
214 Det er bare å søke på det en er interessert i. Kopier gjerne
215 datasettet og sett opp din egen tjeneste hvis du vil gjøre mer
216 avanserte søk. SQLite-filen med Doffin-oppføringer kan lastes med fra
217 Scraperwiki for de som vil grave dypere.</p>
218 </div>
219 <div class="tags">
220
221
222 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</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>.
223
224
225 </div>
226 </div>
227 <div class="padding"></div>
228
229 <div class="entry">
230 <div class="title"><a href="http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html">All drones should be radio marked with what they do and who they belong to</a></div>
231 <div class="date">21st November 2013</div>
232 <div class="body"><p>Drones, flying robots, are getting more and more popular. The most
233 know ones are the killer drones used by some government to murder
234 people they do not like without giving them the chance of a fair
235 trial, but the technology have many good uses too, from mapping and
236 forest maintenance to photography and search and rescue. I am sure it
237 is just a question of time before "bad drones" are in the hands of
238 private enterprises and not only state criminals but petty criminals
239 too. The drone technology is very useful and very dangerous. To have
240 some control over the use of drones, I agree with Daniel Suarez in his
241 TED talk
242 "<a href="https://archive.org/details/DanielSuarez_2013G">The kill
243 decision shouldn't belong to a robot</a>", where he suggested this
244 little gem to keep the good while limiting the bad use of drones:</p>
245
246 <blockquote>
247
248 <p>Each robot and drone should have a cryptographically signed
249 I.D. burned in at the factory that can be used to track its movement
250 through public spaces. We have license plates on cars, tail numbers on
251 aircraft. This is no different. And every citizen should be able to
252 download an app that shows the population of drones and autonomous
253 vehicles moving through public spaces around them, both right now and
254 historically. And civic leaders should deploy sensors and civic drones
255 to detect rogue drones, and instead of sending killer drones of their
256 own up to shoot them down, they should notify humans to their
257 presence. And in certain very high-security areas, perhaps civic
258 drones would snare them and drag them off to a bomb disposal facility.</p>
259
260 <p>But notice, this is more an immune system than a weapons system. It
261 would allow us to avail ourselves of the use of autonomous vehicles
262 and drones while still preserving our open, civil society.</p>
263
264 </blockquote>
265
266 <p>The key is that <em>every citizen</em> should be able to read the
267 radio beacons sent from the drones in the area, to be able to check
268 both the government and others use of drones. For such control to be
269 effective, everyone must be able to do it. What should such beacon
270 contain? At least formal owner, purpose, contact information and GPS
271 location. Probably also the origin and target position of the current
272 flight. And perhaps some registration number to be able to look up
273 the drone in a central database tracking their movement. Robots
274 should not have privacy. It is people who need privacy.</p>
275 </div>
276 <div class="tags">
277
278
279 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/robot">robot</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
280
281
282 </div>
283 </div>
284 <div class="padding"></div>
285
286 <div class="entry">
287 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Lets_make_a_wireless_community_network_in_Oslo_.html">Lets make a wireless community network in Oslo!</a></div>
288 <div class="date">13th November 2013</div>
289 <div class="body"><p>Today NUUG and Hackeriet announced
290 <a href="http://www.nuug.no/news/Bli_med___bygge_dugnadsnett_for_alle_i_Oslo.shtml">our
291 plans to join forces and create a wireless community network in
292 Oslo</a>. The workshop to help people get started will take place
293 Thursday 2013-11-28, but we already are collecting the geolocation of
294 people joining forces to make this happen. We have
295 <a href="https://github.com/petterreinholdtsen/meshfx-node/blob/master/oslo-nodes.geojson">9
296 locations plotted on the map</a>, but we will need more before we have
297 a connected mesh spread across Oslo. If this sound interesting to
298 you, please join us at the workshop. If you are too impatient to wait
299 15 days, please join us on the IRC channel
300 <a href="irc://irc.freenode.net/%23nuug">#nuug on irc.freenode.net</a>
301 right away. :)</p>
302 </div>
303 <div class="tags">
304
305
306 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
307
308
309 </div>
310 </div>
311 <div class="padding"></div>
312
313 <div class="entry">
314 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Running_TP_Link_MR3040_as_a_batman_adv_mesh_node_using_openwrt.html">Running TP-Link MR3040 as a batman-adv mesh node using openwrt</a></div>
315 <div class="date">10th November 2013</div>
316 <div class="body"><p>Continuing my research into mesh networking, I was recommended to
317 use TP-Link 3040 and 3600 access points as mesh nodes, and the pair I
318 bought arrived on Friday. Here are my notes on how to set up the
319 MR3040 as a mesh node using
320 <a href="http://www.openwrt.org/">OpenWrt</a>.</p>
321
322 <p>I started by following the instructions on the OpenWRT wiki for
323 <a href="http://wiki.openwrt.org/toh/tp-link/tl-mr3040">TL-MR3040</a>,
324 and downloaded
325 <a href="http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin">the
326 recommended firmware image</a>
327 (openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin) and
328 uploaded it into the original web interface. The flashing went fine,
329 and the machine was available via telnet on the ethernet port. After
330 logging in and setting the root password, ssh was available and I
331 could start to set it up as a batman-adv mesh node.</p>
332
333 <p>I started off by reading the instructions from
334 <a href="http://wirelessafrica.meraka.org.za/wiki/index.php?title=Antoine's_Research">Wireless
335 Africa</a>, which had quite a lot of useful information, but
336 eventually I followed the recipe from the Open Mesh wiki for
337 <a href="http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config">using
338 batman-adv on OpenWrt</a>. A small snag was the fact that the
339 <tt>opkg install kmod-batman-adv</tt> command did not work as it
340 should. The batman-adv kernel module would fail to load because its
341 dependency crc16 was not already loaded. I
342 <a href="https://dev.openwrt.org/ticket/14452">reported the bug</a> to
343 the openwrt project and hope it will be fixed soon. But the problem
344 only seem to affect initial testing of batman-adv, as configuration
345 seem to work when booting from scratch.</p>
346
347 <p>The setup is done using files in /etc/config/. I did not bridge
348 the Ethernet and mesh interfaces this time, to be able to hook up the
349 box on my local network and log into it for configuration updates.
350 The following files were changed and look like this after modifying
351 them:</p>
352
353 <p><tt>/etc/config/network</tt></p>
354
355 <pre>
356
357 config interface 'loopback'
358 option ifname 'lo'
359 option proto 'static'
360 option ipaddr '127.0.0.1'
361 option netmask '255.0.0.0'
362
363 config globals 'globals'
364 option ula_prefix 'fdbf:4c12:3fed::/48'
365
366 config interface 'lan'
367 option ifname 'eth0'
368 option type 'bridge'
369 option proto 'dhcp'
370 option ipaddr '192.168.1.1'
371 option netmask '255.255.255.0'
372 option hostname 'tl-mr3040'
373 option ip6assign '60'
374
375 config interface 'mesh'
376 option ifname 'adhoc0'
377 option mtu '1528'
378 option proto 'batadv'
379 option mesh 'bat0'
380 </pre>
381
382 <p><tt>/etc/config/wireless</tt></p>
383 <pre>
384
385 config wifi-device 'radio0'
386 option type 'mac80211'
387 option channel '11'
388 option hwmode '11ng'
389 option path 'platform/ar933x_wmac'
390 option htmode 'HT20'
391 list ht_capab 'SHORT-GI-20'
392 list ht_capab 'SHORT-GI-40'
393 list ht_capab 'RX-STBC1'
394 list ht_capab 'DSSS_CCK-40'
395 option disabled '0'
396
397 config wifi-iface 'wmesh'
398 option device 'radio0'
399 option ifname 'adhoc0'
400 option network 'mesh'
401 option encryption 'none'
402 option mode 'adhoc'
403 option bssid '02:BA:00:00:00:01'
404 option ssid 'meshfx@hackeriet'
405 </pre>
406 <p><tt>/etc/config/batman-adv</tt></p>
407 <pre>
408
409 config 'mesh' 'bat0'
410 option interfaces 'adhoc0'
411 option 'aggregated_ogms'
412 option 'ap_isolation'
413 option 'bonding'
414 option 'fragmentation'
415 option 'gw_bandwidth'
416 option 'gw_mode'
417 option 'gw_sel_class'
418 option 'log_level'
419 option 'orig_interval'
420 option 'vis_mode'
421 option 'bridge_loop_avoidance'
422 option 'distributed_arp_table'
423 option 'network_coding'
424 option 'hop_penalty'
425
426 # yet another batX instance
427 # config 'mesh' 'bat5'
428 # option 'interfaces' 'second_mesh'
429 </pre>
430
431 <p>The mesh node is now operational. I have yet to test its range,
432 but I hope it is good. I have not yet tested the TP-Link 3600 box
433 still wrapped up in plastic.</p>
434 </div>
435 <div class="tags">
436
437
438 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
439
440
441 </div>
442 </div>
443 <div class="padding"></div>
444
445 <div class="entry">
446 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html">Debian init.d boot script example for rsyslog</a></div>
447 <div class="date"> 2nd November 2013</div>
448 <div class="body"><p>If one of the points of switching to a new init system in Debian is
449 <a href="http://thomas.goirand.fr/blog/?p=147">to get rid of huge
450 init.d scripts</a>, I doubt we need to switch away from sysvinit and
451 init.d scripts at all. Here is an example init.d script, ie a rewrite
452 of /etc/init.d/rsyslog:</p>
453
454 <p><pre>
455 #!/lib/init/init-d-script
456 ### BEGIN INIT INFO
457 # Provides: rsyslog
458 # Required-Start: $remote_fs $time
459 # Required-Stop: umountnfs $time
460 # X-Stop-After: sendsigs
461 # Default-Start: 2 3 4 5
462 # Default-Stop: 0 1 6
463 # Short-Description: enhanced syslogd
464 # Description: Rsyslog is an enhanced multi-threaded syslogd.
465 # It is quite compatible to stock sysklogd and can be
466 # used as a drop-in replacement.
467 ### END INIT INFO
468 DESC="enhanced syslogd"
469 DAEMON=/usr/sbin/rsyslogd
470 </pre></p>
471
472 <p>Pretty minimalistic to me... For the record, the original sysv-rc
473 script was 137 lines, and the above is just 15 lines, most of it meta
474 info/comments.</p>
475
476 <p>How to do this, you ask? Well, one create a new script
477 /lib/init/init-d-script looking something like this:
478
479 <p><pre>
480 #!/bin/sh
481
482 # Define LSB log_* functions.
483 # Depend on lsb-base (>= 3.2-14) to ensure that this file is present
484 # and status_of_proc is working.
485 . /lib/lsb/init-functions
486
487 #
488 # Function that starts the daemon/service
489
490 #
491 do_start()
492 {
493 # Return
494 # 0 if daemon has been started
495 # 1 if daemon was already running
496 # 2 if daemon could not be started
497 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \
498 || return 1
499 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
500 $DAEMON_ARGS \
501 || return 2
502 # Add code here, if necessary, that waits for the process to be ready
503 # to handle requests from services started subsequently which depend
504 # on this one. As a last resort, sleep for some time.
505 }
506
507 #
508 # Function that stops the daemon/service
509 #
510 do_stop()
511 {
512 # Return
513 # 0 if daemon has been stopped
514 # 1 if daemon was already stopped
515 # 2 if daemon could not be stopped
516 # other if a failure occurred
517 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
518 RETVAL="$?"
519 [ "$RETVAL" = 2 ] && return 2
520 # Wait for children to finish too if this is a daemon that forks
521 # and if the daemon is only ever run from this initscript.
522 # If the above conditions are not satisfied then add some other code
523 # that waits for the process to drop all resources that could be
524 # needed by services started subsequently. A last resort is to
525 # sleep for some time.
526 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
527 [ "$?" = 2 ] && return 2
528 # Many daemons don't delete their pidfiles when they exit.
529 rm -f $PIDFILE
530 return "$RETVAL"
531 }
532
533 #
534 # Function that sends a SIGHUP to the daemon/service
535 #
536 do_reload() {
537 #
538 # If the daemon can reload its configuration without
539 # restarting (for example, when it is sent a SIGHUP),
540 # then implement that here.
541 #
542 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
543 return 0
544 }
545
546 SCRIPTNAME=$1
547 scriptbasename="$(basename $1)"
548 echo "SN: $scriptbasename"
549 if [ "$scriptbasename" != "init-d-library" ] ; then
550 script="$1"
551 shift
552 . $script
553 else
554 exit 0
555 fi
556
557 NAME=$(basename $DAEMON)
558 PIDFILE=/var/run/$NAME.pid
559
560 # Exit if the package is not installed
561 #[ -x "$DAEMON" ] || exit 0
562
563 # Read configuration variable file if it is present
564 [ -r /etc/default/$NAME ] && . /etc/default/$NAME
565
566 # Load the VERBOSE setting and other rcS variables
567 . /lib/init/vars.sh
568
569 case "$1" in
570 start)
571 [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
572 do_start
573 case "$?" in
574 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
575 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
576 esac
577 ;;
578 stop)
579 [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
580 do_stop
581 case "$?" in
582 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
583 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
584 esac
585 ;;
586 status)
587 status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
588 ;;
589 #reload|force-reload)
590 #
591 # If do_reload() is not implemented then leave this commented out
592 # and leave 'force-reload' as an alias for 'restart'.
593 #
594 #log_daemon_msg "Reloading $DESC" "$NAME"
595 #do_reload
596 #log_end_msg $?
597 #;;
598 restart|force-reload)
599 #
600 # If the "reload" option is implemented then remove the
601 # 'force-reload' alias
602 #
603 log_daemon_msg "Restarting $DESC" "$NAME"
604 do_stop
605 case "$?" in
606 0|1)
607 do_start
608 case "$?" in
609 0) log_end_msg 0 ;;
610 1) log_end_msg 1 ;; # Old process is still running
611 *) log_end_msg 1 ;; # Failed to start
612 esac
613 ;;
614 *)
615 # Failed to stop
616 log_end_msg 1
617 ;;
618 esac
619 ;;
620 *)
621 echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
622 exit 3
623 ;;
624 esac
625
626 :
627 </pre></p>
628
629 <p>It is based on /etc/init.d/skeleton, and could be improved quite a
630 lot. I did not really polish the approach, so it might not always
631 work out of the box, but you get the idea. I did not try very hard to
632 optimize it nor make it more robust either.</p>
633
634 <p>A better argument for switching init system in Debian than reducing
635 the size of init scripts (which is a good thing to do anyway), is to
636 get boot system that is able to handle the kernel events sensibly and
637 robustly, and do not depend on the boot to run sequentially. The boot
638 and the kernel have not behaved sequentially in years.</p>
639 </div>
640 <div class="tags">
641
642
643 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
644
645
646 </div>
647 </div>
648 <div class="padding"></div>
649
650 <div class="entry">
651 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html">Browser plugin for SPICE (spice-xpi) uploaded to Debian</a></div>
652 <div class="date"> 1st November 2013</div>
653 <div class="body"><p><a href="http://www.spice-space.org/">The SPICE protocol</a> for
654 remote display access is the preferred solution with oVirt and RedHat
655 Enterprise Virtualization, and I was sad to discover the other day
656 that the browser plugin needed to use these systems seamlessly was
657 missing in Debian. The <a href="http://bugs.debian.org/668284">request
658 for a package</a> was from 2012-04-10 with no progress since
659 2013-04-01, so I decided to wrap up a package based on the great work
660 from Cajus Pollmeier and put it in a collab-maint maintained git
661 repository to get a package I could use. I would very much like
662 others to help me maintain the package (or just take over, I do not
663 mind), but as no-one had volunteered so far, I just uploaded it to
664 NEW. I hope it will be available in Debian in a few days.</p>
665
666 <p>The source is now available from
667 <a href="http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary">http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary</a>.</p>
668 </div>
669 <div class="tags">
670
671
672 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
673
674
675 </div>
676 </div>
677 <div class="padding"></div>
678
679 <div class="entry">
680 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html">Teaching vmdebootstrap to create Raspberry Pi SD card images</a></div>
681 <div class="date">27th October 2013</div>
682 <div class="body"><p>The
683 <a href="http://packages.qa.debian.org/v/vmdebootstrap.html">vmdebootstrap</a>
684 program is a a very nice system to create virtual machine images. It
685 create a image file, add a partition table, mount it and run
686 debootstrap in the mounted directory to create a Debian system on a
687 stick. Yesterday, I decided to try to teach it how to make images for
688 <a href="https://wiki.debian.org/RaspberryPi">Raspberry Pi</a>, as part
689 of a plan to simplify the build system for
690 <a href="https://wiki.debian.org/FreedomBox">the FreedomBox
691 project</a>. The FreedomBox project already uses vmdebootstrap for
692 the virtualbox images, but its current build system made multistrap
693 based system for Dreamplug images, and it is lacking support for
694 Raspberry Pi.</p>
695
696 <p>Armed with the knowledge on how to build "foreign" (aka non-native
697 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
698 code and adjusted it to be able to build armel images on my amd64
699 Debian laptop. I ended up giving vmdebootstrap five new options,
700 allowing me to replicate the image creation process I use to make
701 <a href="http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">Debian
702 Jessie based mesh node images for the Raspberry Pi</a>. First, the
703 <tt>--foreign /path/to/binfm_handler</tt> option tell vmdebootstrap to
704 call debootstrap with --foreign and to copy the handler into the
705 generated chroot before running the second stage. This allow
706 vmdebootstrap to create armel images on an amd64 host. Next I added
707 two new options <tt>--bootsize size</tt> and <tt>--boottype
708 fstype</tt> to teach it to create a separate /boot/ partition with the
709 given file system type, allowing me to create an image with a vfat
710 partition for the /boot/ stuff. I also added a <tt>--variant
711 variant</tt> option to allow me to create smaller images without the
712 Debian base system packages installed. Finally, I added an option
713 <tt>--no-extlinux</tt> to tell vmdebootstrap to not install extlinux
714 as a boot loader. It is not needed on the Raspberry Pi and probably
715 most other non-x86 architectures. The changes were accepted by the
716 upstream author of vmdebootstrap yesterday and today, and is now
717 available from
718 <a href="http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/">the
719 upstream project page</a>.</p>
720
721 <p>To use it to build a Raspberry Pi image using Debian Jessie, first
722 create a small script (the customize script) to add the non-free
723 binary blob needed to boot the Raspberry Pi and the APT source
724 list:</p>
725
726 <p><pre>
727 #!/bin/sh
728 set -e # Exit on first error
729 rootdir="$1"
730 cd "$rootdir"
731 cat &lt;&lt;EOF > etc/apt/sources.list
732 deb http://http.debian.net/debian/ jessie main contrib non-free
733 EOF
734 # Install non-free binary blob needed to boot Raspberry Pi. This
735 # install a kernel somewhere too.
736 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
737 -O $rootdir/usr/bin/rpi-update
738 chmod a+x $rootdir/usr/bin/rpi-update
739 mkdir -p $rootdir/lib/modules
740 touch $rootdir/boot/start.elf
741 chroot $rootdir rpi-update
742 </pre></p>
743
744 <p>Next, fetch the latest vmdebootstrap script and call it like this
745 to build the image:</p>
746
747 <pre>
748 sudo ./vmdebootstrap \
749 --variant minbase \
750 --arch armel \
751 --distribution jessie \
752 --mirror http://http.debian.net/debian \
753 --image test.img \
754 --size 600M \
755 --bootsize 64M \
756 --boottype vfat \
757 --log-level debug \
758 --verbose \
759 --no-kernel \
760 --no-extlinux \
761 --root-password raspberry \
762 --hostname raspberrypi \
763 --foreign /usr/bin/qemu-arm-static \
764 --customize `pwd`/customize \
765 --package netbase \
766 --package git-core \
767 --package binutils \
768 --package ca-certificates \
769 --package wget \
770 --package kmod
771 </pre></p>
772
773 <p>The list of packages being installed are the ones needed by
774 rpi-update to make the image bootable on the Raspberry Pi, with the
775 exception of netbase, which is needed by debootstrap to find
776 /etc/hosts with the minbase variant. I really wish there was a way to
777 set up an Raspberry Pi using only packages in the Debian archive, but
778 that is not possible as far as I know, because it boots from the GPU
779 using a non-free binary blob.</p>
780
781 <p>The build host need debootstrap, kpartx and qemu-user-static and
782 probably a few others installed. I have not checked the complete
783 build dependency list.</p>
784
785 <p>The resulting image will not use the hardware floating point unit
786 on the Raspberry PI, because the armel architecture in Debian is not
787 optimized for that use. So the images created will be a bit slower
788 than <a href="http://www.raspbian.org/">Raspbian</a> based images.</p>
789 </div>
790 <div class="tags">
791
792
793 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>.
794
795
796 </div>
797 </div>
798 <div class="padding"></div>
799
800 <div class="entry">
801 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Det_er_jo_makta_som_er_mest_s_rbar_ved_massiv_overv_kning_av_Internett.html">Det er jo makta som er mest sårbar ved massiv overvåkning av Internett</a></div>
802 <div class="date">26th October 2013</div>
803 <div class="body"><p>De siste måneders eksponering av
804 <a href="http://www.aftenposten.no/nyheter/uriks/Her-er-Edvard-Snowdens-mest-omtalte-avsloringer-7351734.html">den
805 totale overvåkningen som foregår i den vestlige verden dokumenterer
806 hvor sårbare vi er</a>. Men det slår meg at de som er mest sårbare
807 for dette, myndighetspersoner på alle nivåer, neppe har innsett at de
808 selv er de mest interessante personene å lage profiler på, for å kunne
809 påvirke dem.</p>
810
811 <p>For å ta et lite eksempel: Stortingets nettsted,
812 <a href="http://www.stortinget.no/">www.stortinget.no</a> (og
813 forsåvidt også
814 <a href="http://data.stortinget.no/">data.stortinget.no</a>),
815 inneholder informasjon om det som foregår på Stortinget, og jeg antar
816 de største brukerne av informasjonen der er representanter og
817 rådgivere på Stortinget. Intet overraskende med det. Det som derimot
818 er mer skjult er at Stortingets nettsted bruker
819 <a href="http://en.wikipedia.org/wiki/Google_Analytics">Google
820 Analytics</a>, hvilket gjør at enhver som besøker nettsidene der også
821 rapporterer om besøket via Internett-linjer som passerer Sverige,
822 England og videre til USA. Det betyr at informasjon om ethvert besøk
823 på stortingets nettsider kan snappes opp av svensk, britisk og USAs
824 etterretningsvesen. De kan dermed holde et øye med hvilke
825 Stortingssaker stortingsrepresentantene synes er interessante å sjekke
826 ut, og hvilke sider rådgivere og andre på stortinget synes er
827 interessant å besøke, når de gjør det og hvilke andre representanter
828 som sjekker de samme sidene omtrent samtidig. Stortingets bruk av
829 Google Analytics gjør det dermed enkelt for utenlands etteretning å
830 spore representantenes aktivitet og interesse. Hvis noen av
831 representantene bruker Google Mail eller noen andre tjenestene som
832 krever innlogging, så vil det være enda enklere å finne ut nøyaktig
833 hvilke personer som bruker hvilke nettlesere og dermed knytte
834 informasjonen opp til enkeltpersoner på Stortinget.</p>
835
836 <p>Og jo flere nettsteder som bruker Google Analytics, jo bedre
837 oversikt over stortingsrepresentantenes lesevaner og interesse blir
838 tilgjengelig for svensk, britisk og USAs etterretning. Hva de kan
839 bruke den informasjonen til overlater jeg til leseren å undres
840 over.</p>
841 </div>
842 <div class="tags">
843
844
845 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/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
846
847
848 </div>
849 </div>
850 <div class="padding"></div>
851
852 <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>
853 <div id="sidebar">
854
855
856
857 <h2>Archive</h2>
858 <ul>
859
860 <li>2013
861 <ul>
862
863 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
864
865 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
866
867 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
868
869 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
870
871 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
872
873 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
874
875 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
876
877 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
878
879 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
880
881 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
882
883 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (8)</a></li>
884
885 </ul></li>
886
887 <li>2012
888 <ul>
889
890 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
891
892 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
893
894 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
895
896 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
897
898 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
899
900 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
901
902 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
903
904 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
905
906 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
907
908 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
909
910 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
911
912 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
913
914 </ul></li>
915
916 <li>2011
917 <ul>
918
919 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
920
921 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
922
923 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
924
925 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
926
927 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
928
929 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
930
931 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
932
933 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
934
935 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
936
937 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
938
939 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
940
941 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
942
943 </ul></li>
944
945 <li>2010
946 <ul>
947
948 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
949
950 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
951
952 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
953
954 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
955
956 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
957
958 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
959
960 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
961
962 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
963
964 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
965
966 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
967
968 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
969
970 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
971
972 </ul></li>
973
974 <li>2009
975 <ul>
976
977 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
978
979 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
980
981 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
982
983 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
984
985 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
986
987 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
988
989 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
990
991 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
992
993 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
994
995 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
996
997 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
998
999 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1000
1001 </ul></li>
1002
1003 <li>2008
1004 <ul>
1005
1006 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1007
1008 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1009
1010 </ul></li>
1011
1012 </ul>
1013
1014
1015
1016 <h2>Tags</h2>
1017 <ul>
1018
1019 <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1020
1021 <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1022
1023 <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1024
1025 <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1026
1027 <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (7)</a></li>
1028
1029 <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (13)</a></li>
1030
1031 <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1032
1033 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (91)</a></li>
1034
1035 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (142)</a></li>
1036
1037 <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1038
1039 <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
1040
1041 <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1042
1043 <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (229)</a></li>
1044
1045 <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
1046
1047 <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1048
1049 <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
1050
1051 <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (5)</a></li>
1052
1053 <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
1054
1055 <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (37)</a></li>
1056
1057 <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (7)</a></li>
1058
1059 <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
1060
1061 <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
1062
1063 <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (6)</a></li>
1064
1065 <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1066
1067 <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (5)</a></li>
1068
1069 <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (25)</a></li>
1070
1071 <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (238)</a></li>
1072
1073 <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (159)</a></li>
1074
1075 <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (9)</a></li>
1076
1077 <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1078
1079 <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (45)</a></li>
1080
1081 <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (67)</a></li>
1082
1083 <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1084
1085 <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1086
1087 <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1088
1089 <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1090
1091 <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1092
1093 <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1094
1095 <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1096
1097 <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (33)</a></li>
1098
1099 <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1100
1101 <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1102
1103 <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (44)</a></li>
1104
1105 <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1106
1107 <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1108
1109 <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (21)</a></li>
1110
1111 <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
1112
1113 <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1114
1115 <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (39)</a></li>
1116
1117 <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1118
1119 <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (28)</a></li>
1120
1121 </ul>
1122
1123
1124 </div>
1125 <p style="text-align: right">
1126 Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1127 </p>
1128
1129 </body>
1130 </html>