]> pere.pagekite.me Git - homepage.git/blob - blog/archive/2012/06/index.html
More info.
[homepage.git] / blog / archive / 2012 / 06 / 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: entries from June 2012</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="06.rss" type="application/rss+xml" />
10 </head>
11 <body>
12 <!-- XML FEED -->
13 <div class="title">
14 <h1>
15 <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
16
17 </h1>
18
19 </div>
20
21
22 <h3>Entries from June 2012.</h3>
23
24 <div class="entry">
25 <div class="title">
26 <a href="http://people.skolelinux.org/pere/blog/Veileder_fra_DIFI_om_publisering_av_offentlige_data.html">Veileder fra DIFI om publisering av offentlige data</a>
27 </div>
28 <div class="date">
29 1st June 2012
30 </div>
31 <div class="body">
32 <p>På onsdag rakk jeg såvidt innom
33 <a href="http://www.meetup.com/osloopendata/">Oslo Open Data Forums</a>
34 møte, og fikk lagt hendene mine på DIFIs helt nye veileder
35 "<a href="http://veileder.data.norge.no/">Åpne data. Del og skap
36 verdier. Veileder i tilgjengeliggjøring av offentlig data</a>" (også
37 <a href="http://www.difi.no/filearchive/veileder-i-tilgjengeliggjoring-av-offentlig-data-web.pdf">tilgjengelig
38 som PDF</a> fra DIFI).</p>
39
40 <p>Veilederen er veldig bra, og nevner viktige problemstillinger og
41 skisserer f.eks. både verdiskapningspotensialet og formatmulighetene
42 som en bør ha i bakhodet når en publiserer offentlig informasjon på
43 maskinlesbart format. Kildekoden til veilederen er
44 <a href="https://github.com/difi/veileder-opnedata">tilgjengelig via
45 github</a>, og en kan rapportere tilbakemeldinger og forslag til
46 forbedringer der (eller via epost og twitter for de som ønsker
47 det).</p>
48
49 <p>Det eneste jeg virkelig savnet i veilederen var omtale av
50 <a href="http://www.w3.org/DesignIssues/LinkedData.html">w3cs
51 stjerneklassifisering</a> av åpne datakilder, som jeg tror ville være
52 nyttige mentale knagger for de som vurderer å publisere sin
53 informasjon på som åpne data. Jeg har
54 <a href="https://github.com/difi/veileder-opnedata/issues/1">rapportert
55 en github-bug</a> om dette, så får vi se hvordan den blir behandlet.</p>
56
57 <p>Det slo meg at det var veldig lite konkret i veilederen om valg av
58 bruksvilkår ved publisering (aka lisens), men jeg er ikke sikker på om
59 det hører hjemme der, da det er et vanskelig tema som kanskje heller
60 hører hjemme i sin egen veileder. Uansett, anbefaler alle å ta en
61 titt på veilederen og sikre at alle offentlige etater en har kontakt
62 med får en kopi.</p>
63
64 </div>
65 <div class="tags">
66
67
68 Tags: <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/web">web</a>.
69
70
71 </div>
72 </div>
73 <div class="padding"></div>
74
75 <div class="entry">
76 <div class="title">
77 <a href="http://people.skolelinux.org/pere/blog/SOAP_based_webservice_from_Dell_to_check_server_support_status.html">SOAP based webservice from Dell to check server support status</a>
78 </div>
79 <div class="date">
80 1st June 2012
81 </div>
82 <div class="body">
83 <p>A few years ago I wrote
84 <a href="http://people.skolelinux.org/pere/blog/Checking_server_hardware_support_status_for_Dell__HP_and_IBM_servers.html">how
85 to extract support status</a> for your Dell and HP servers. Recently
86 I have learned from colleges here at the
87 <a href="http://www.uio.no/">University of Oslo</a> that Dell have
88 made this even easier, by providing a SOAP based web service. Given
89 the service tag, one can now query the Dell servers and get machine
90 readable information about the support status. This perl code
91 demonstrate how to do it:</p>
92
93 <p><pre>
94 use strict;
95 use warnings;
96 use SOAP::Lite;
97 use Data::Dumper;
98 my $GUID = '11111111-1111-1111-1111-111111111111';
99 my $App = 'test';
100 my $servicetag = $ARGV[0] or die "Please supply a servicetag. $!\n";
101 my ($deal, $latest, @dates);
102 my $s = SOAP::Lite
103 -> uri('http://support.dell.com/WebServices/')
104 -> on_action( sub { join '', @_ } )
105 -> proxy('http://xserv.dell.com/services/assetservice.asmx')
106 ;
107 my $a = $s->GetAssetInformation(
108 SOAP::Data->name('guid')->value($GUID)->type(''),
109 SOAP::Data->name('applicationName')->value($App)->type(''),
110 SOAP::Data->name('serviceTags')->value($servicetag)->type(''),
111 );
112 print Dumper($a -> result) ;
113 </pre></p>
114
115 <p>The output can look like this:</p>
116
117 <p><pre>
118 $VAR1 = {
119 'Asset' => {
120 'Entitlements' => {
121 'EntitlementData' => [
122 {
123 'EntitlementType' => 'Expired',
124 'EndDate' => '2009-07-29T00:00:00',
125 'Provider' => '',
126 'StartDate' => '2006-07-29T00:00:00',
127 'DaysLeft' => '0'
128 },
129 {
130 'EntitlementType' => 'Expired',
131 'EndDate' => '2009-07-29T00:00:00',
132 'Provider' => '',
133 'StartDate' => '2006-07-29T00:00:00',
134 'DaysLeft' => '0'
135 },
136 {
137 'EntitlementType' => 'Expired',
138 'EndDate' => '2007-07-29T00:00:00',
139 'Provider' => '',
140 'StartDate' => '2006-07-29T00:00:00',
141 'DaysLeft' => '0'
142 }
143 ]
144 },
145 'AssetHeaderData' => {
146 'SystemModel' => 'GX620',
147 'ServiceTag' => '8DSGD2J',
148 'SystemShipDate' => '2006-07-29T19:00:00-05:00',
149 'Buid' => '2323',
150 'Region' => 'Europe',
151 'SystemID' => 'PLX_GX620',
152 'SystemType' => 'OptiPlex'
153 }
154 }
155 };
156 </pre></p>
157
158 <p>I have not been able to find any documentation from Dell about this
159 service outside the
160 <a href="http://xserv.dell.com/services/assetservice.asmx?op=GetAssetInformation">inline
161 documentation</a>, and according to
162 <a href="http://iboyd.net/index.php/2012/02/14/updated-dell-warranty-information-script/">one
163 comment</a> it can have stability issues, but it is a lot better than
164 scraping HTML pages. :)</p>
165
166 <p>Wonder if HP and other server vendors have a similar service. If
167 you know of one, drop me an email. :)</p>
168
169 </div>
170 <div class="tags">
171
172
173 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
174
175
176 </div>
177 </div>
178 <div class="padding"></div>
179
180 <div class="entry">
181 <div class="title">
182 <a href="http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Mike_Gabriel.html">Debian Edu interview: Mike Gabriel</a>
183 </div>
184 <div class="date">
185 2nd June 2012
186 </div>
187 <div class="body">
188 <p>Back in 2010, Mike Gabriel showed up on the
189 <a href="http://www.skolelinux.org/">Debian Edu and Skolelinux</a>
190 mailing list. He quickly proved to be a valuable developer, and
191 thanks to his tireless effort we now have Kerberos integrated into the
192 <a href="http://www.debian.org/News/2012/20120311.html">Debian Edu
193 Squeeze</a> version.</p>
194
195 <p><strong>Who are you, and how do you spend your days?</strong></p>
196
197 <p>My name is Mike Gabriel, I am 38 years old and live near Kiel,
198 Schleswig-Holstein, Germany. I live together with a wonderful partner
199 (Angela Fuß) and two own children and two bonus children (contributed
200 by Angela).</p>
201
202 <p>During the day I am part-time employed as a system administrator
203 and part-time working as an IT consultant. The consultancy work
204 touches free software topics wherever and whenever possible. During
205 the nights I am a free software developer. In the gaps I also train in
206 becoming an osteopath.</p>
207
208 <p>Starting in 2010 we (Andreas Buchholz, Angela Fuß, Mike Gabriel)
209 have set up a free software project in the area of Kiel that aims at
210 introducing free software into schools. The project's name is
211 "IT-Zukunft Schule" (IT future for schools). The project links IT
212 skills with communication skills.</p>
213
214 <p><strong>How did you get in contact with the Skolelinux/Debian Edu
215 project?</strong></p>
216
217 <p>While preparing our own customised Linux distribution for
218 "IT-Zukunft Schule" we were repeatedly asked if we really wanted to
219 reinvent the wheel. What schools really need is already available,
220 people said. From this impulse we started evaluating other Linux
221 distributions that target being used for school networks.</p>
222
223 <p>At the end we short-listed two approaches and compared them: a
224 commercial Linux distribution developed by a company in Bremen,
225 Germany, and Skolelinux / Debian Edu. Between 12/2010 and 03/2011 we
226 went to several events and met people being responsible for marketing
227 and development of either of the distributions. Skolelinux / Debian
228 Edu was by far much more convincing compared to the other product that
229 got short-listed beforehand--across the full spectrum. What was most
230 attractive for me personally: the perspective of collaboration within
231 the developmental branch of the Debian Edu project itself.</p>
232
233 <p>In parallel with this, we talked to many local and not-so-local
234 people. People teaching at schools, headmasters, politicians, data
235 protection experts, other IT professionals.</p>
236
237 <p>We came to two conclusions:</p>
238
239 <p>First, a technical conclusion: What schools need is available in
240 bits and pieces here and there, and none of the solutions really fit
241 by 100%. Any school we have seen has a very individual IT setup
242 whereas most of each school's requirements could mapped by a standard
243 IT solution. The requirement to this IT solution is flexibility and
244 customisability, so that individual adaptations here and there are
245 possible. In terms of re-distributing and rolling out such a
246 standardised IT system for schools (a system that is still to some
247 degree customisable) there is still a lot of work to do here
248 locally. Debian Edu / Skolelinux has been our choice as the starting
249 point.</p>
250
251 <p>Second, a holistic conclusion: What schools need does not exist at
252 all (or we missed it so far). There are several technical solutions
253 for handling IT at schools that tend to make a good impression. What
254 has been missing completely here in Germany, though, is the enrolment
255 of people into using IT and teaching with IT. "IT-Zukunft Schule"
256 tries to provide an approach for this.</p>
257
258 <p>Only some schools have some sort of a media concept which explains,
259 defines and gives guidance on how to use IT in class. Most schools in
260 Northern Germany do not have an IT service provider, the school's IT
261 equipment is managed by one or (if the school is lucky) two (admin)
262 teachers, most of the workload these admin teachers get done in there
263 spare time.</p>
264
265 <p>We were surprised that only a very few admin teachers were
266 networked with colleagues from other schools. Basically, every school
267 here around has its individual approach of providing IT equipment to
268 teachers and students and the exchange of ideas has been quasi
269 non-existent until 2010/2011.</p>
270
271 <p>Quite some (non-admin) teachers try to avoid using IT technology in
272 class as a learning medium completely. Several reasons for this
273 avoidance do exist.</p>
274
275 <p>We discovered that no-one has ever taken a closer look at this
276 social part of IT management in schools, so far. On our quest journey
277 for a technical IT solution for schools, we discussed this issue with
278 several teachers, headmasters, politicians, other IT professionals and
279 they all confirmed: a holistic approach of considering IT management
280 at schools, an approach that includes the people in place, will be new
281 and probably a gain for all.</p>
282
283 <p><strong>What do you see as the advantages of Skolelinux/Debian
284 Edu?</strong></p>
285
286 <p>There is a list of advantages: international context, openness to
287 any kind of contributions, do-ocracy policy, the closeness to Debian,
288 the different installation scenarios possible (from stand-alone
289 workstation to complex multi-server sites), the transparency within
290 project communication, honest communication within the group of
291 developers, etc.</p>
292
293 <p><strong>What do you see as the disadvantages of Skolelinux/Debian
294 Edu?</strong></p>
295
296 <p>Every coin has two sides:</p>
297
298 <p>Technically: <a href="http://bugs.debian.org/311188">BTS issue
299 #311188</a>, tricky upgradability of a Debian Edu main server, network
300 client installations on top of a plain vanilla Debian installation
301 should become possible sometime in the near future, one could think
302 about splitting the very complex package debian-edu-config into
303 several portions (to make it easier for new developers to
304 contribute).</p>
305
306 <p>Another issue I see is that we (as Debian Edu developers) should
307 find out more about the network of people who do the marketing for
308 Debian Edu / Skolelinux. There is a very active group in Germany
309 promoting Skolelinux on the bigger Linux Days within Germany. Are
310 there other groups like that in other countries? How can we bring
311 these marketing people together (marketing group A with group B and
312 all of them with the group of Debian Edu developers)? During the last
313 meeting of the German Skolelinux group, I got the impression of people
314 there being rather disconnected from the development department of
315 Debian Edu / Skolelinux.</p>
316
317 <p><strong>Which free software do you use daily?</strong></p>
318
319 <p>For my daily business, I do not use commercial software at all.</p>
320
321 <p>For normal stuff I use Iceweasel/Firefox, Libreoffice.org. For
322 serious text writing I prefer LaTeX. I use gimp, inkscape, scribus for
323 more artistic tasks. I run virtual machines in KVM and Virtualbox.</p>
324
325 <p>I am one of the upstream developers of X2Go. In 2010 I started the
326 development of a Python based X2Go Client, called PyHoca-GUI.
327 PyHoca-GUI has brought forth a Python X2Go Client API that currently
328 is being integrated in Ubuntu's software center.</p>
329
330 <p>For communications I have my own Kolab server running using Horde
331 as web-based groupware client. For IRC I love to use irssi, for Jabber
332 I have several clients that I use, mostly pidgin, though. I am also
333 the Debian maintainer of Coccinella, a Jabber-based interactive
334 whiteboard.</p>
335
336 <p>My favourite terminal emulator is KDE's Yakuake.</p>
337
338 <p><strong>Which strategy do you believe is the right one to use to
339 get schools to use free software?</strong></p>
340
341 <p>Communicate, communicate, communicate. Enrol people, enrol people,
342 enrol people.</p>
343
344 </div>
345 <div class="tags">
346
347
348 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>.
349
350
351 </div>
352 </div>
353 <div class="padding"></div>
354
355 <div class="entry">
356 <div class="title">
357 <a href="http://people.skolelinux.org/pere/blog/Kommentar_til_artikkel_i_Adresseavisa_som_omtaler_FiksGataMi.html">Kommentar til artikkel i Adresseavisa som omtaler FiksGataMi</a>
358 </div>
359 <div class="date">
360 2nd June 2012
361 </div>
362 <div class="body">
363 <p>Jeg oppdaget nylig en
364 <a href="http://www.adressa.no/nyheter/trondheim/article1831198.ece">artikkel
365 i Adresseavisa</a> i Trondheim som nevner FiksGataMi, og der Trondheim
366 kommune ser ut til å fortelle at de ikke følger forvaltningslovens
367 krav ved mottak av meldinger sendt inn via FiksGataMi. La derfor
368 nettopp inn denne kommentaren til artikkelen:<p>
369
370 <p><blockquote>
371
372 <p>Her er en liten faktaoppdatering om FiksGataMi-tjenesten, da noen
373 ser ut til å ha misforstått hvordan den fungerer.</p>
374
375 <p>FiksGataMi er et privat initiativ opprettet og drevet av
376 medlemsforeningen NUUG. FiksGataMi tar imot meldinger om feil i
377 offentlig infrastruktur, og sender meldingen skriftlig videre på vegne
378 av innmelder til aktuell aktør i det offentlige, det være seg kommune,
379 fylke eller vegvesenregion. Offentlig etat blir valgt ut fra
380 geografisk plassering og kategori valgt av innsender. Offentlige
381 etater er i følge forvaltningsloven pliktig å følge opp og besvare
382 skriftlige henvendelser, og hvis noen av mottakerne ikke gjør dette
383 kan en klage på lovbrudd i det offentlige. FiksGataMi fungerer dermed
384 som en slags epostklient for innbyggerne der kopi av innsendte
385 meldinger gjøres tilgjengelig og knyttes til kartplassering for enkel
386 gjenfinning. Å sende inn nye problemrapporter via FiksGataMi er
387 dermed ikke avhengig av at kommunen aktivt må følge med på meldinger
388 hos FiksGataMi, da de får dem tilsendt på sine offisielle
389 epostmottakspunkter. Hvorvidt noe blir fikset og om innbyggerne er
390 opp til mottaker av meldingene. For Trondheim kommune er
391 mottaksadressen bydrift.vegdrift@trondheim.kommune.no, en adresse jeg
392 inntil jeg leste denne artikkelen trodde ble håndtert i henhold til
393 forvaltningslovens krav.</p>
394
395 <p>Kan ellers fortelle at 57 kommuner lenker til FiksGataMi fra sine
396 nettsider, og at 37 % (4182 av 11266 ) av problemrapportene sendt inn
397 via FiksGataMi er markert som løst i løsningen. Trondheim kommune har
398 fått tilbud om å få rapportene levert på datamaskinlesbart format i
399 stedet for epost, men har ikke takket ja så langt.</p>
400
401 <p>Vennlig hilsen Petter Reinholdtsen, en av NUUG-folkene bak FiksGataMi.no</p>
402
403 </blockquote></p>
404
405 <p>Det høres for meg ut som om innbyggerne i Trondheim burde klage på
406 kommunens potensielle lovbrudd.</p>
407
408 </div>
409 <div class="tags">
410
411
412 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>.
413
414
415 </div>
416 </div>
417 <div class="padding"></div>
418
419 <div class="entry">
420 <div class="title">
421 <a href="http://people.skolelinux.org/pere/blog/Web_service_to_look_up_HP_and_Dell_computer_hardware_support_status.html">Web service to look up HP and Dell computer hardware support status</a>
422 </div>
423 <div class="date">
424 6th June 2012
425 </div>
426 <div class="body">
427 <p>A few days ago
428 <a href="http://people.skolelinux.org/pere/blog/SOAP_based_webservice_from_Dell_to_check_server_support_status.html">I
429 reported how to get</a> the support status out of Dell using an
430 unofficial and undocumented SOAP API, which I since have found out was
431 <a href="http://lists.us.dell.com/pipermail/linux-poweredge/2012-February/045959.html">discovered
432 by Daniel De Marco in february</a>. Combined with my web scraping
433 code for HP, Dell and IBM
434 <a href="http://people.skolelinux.org/pere/blog/Checking_server_hardware_support_status_for_Dell__HP_and_IBM_servers.html">from
435 2009</a>, I got inspired and wrote
436 <a href="https://views.scraperwiki.com/run/computer-hardware-support-status/">a
437 web service</a> based on Scraperwiki to make it easy to look up the
438 support status and get a machine readable result back.</p>
439
440 <p>This is what it look like at the moment when asking for the JSON
441 output:
442
443 <blockquote><pre>
444 % GET <a href="https://views.scraperwiki.com/run/computer-hardware-support-status/?format=json&vendor=Dell&servicetag=2v1xwn1">https://views.scraperwiki.com/run/computer-hardware-support-status/?format=json&vendor=Dell&servicetag=2v1xwn1</a>
445 supportstatus({"servicetag": "2v1xwn1", "warrantyend": "2013-11-24", "shipped": "2010-11-24", "scrapestamputc": "2012-06-06T20:26:56.965847", "scrapedurl": "http://143.166.84.118/services/assetservice.asmx?WSDL", "vendor": "Dell", "productid": ""})
446 %
447 </pre></blockquote>
448
449 <p>It currently support Dell and HP, and I am hoping for help to add
450 support for other vendors. The python source is available on
451 Scraperwiki and I welcome help with adding more features.</p>
452
453 </div>
454 <div class="tags">
455
456
457 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
458
459
460 </div>
461 </div>
462 <div class="padding"></div>
463
464 <div class="entry">
465 <div class="title">
466 <a href="http://people.skolelinux.org/pere/blog/TV_with_face_recognition__for_improved_viewer_experience.html">TV with face recognition, for improved viewer experience</a>
467 </div>
468 <div class="date">
469 9th June 2012
470 </div>
471 <div class="body">
472 <p>Slashdot got a story about Intel planning a
473 <a href="http://entertainment.slashdot.org/story/12/06/09/0012247/intel-to-launch-tv-service-with-facial-recognition-by-end-of-the-year">TV
474 with face recognition</a> to recognise the viewer, and it occurred to
475 me that it would be more interesting to turn it around, and do face
476 recognition on the TV image itself. It could let the viewer know who
477 is present on the screen, and perhaps look up their credibility,
478 company affiliation, previous appearances etc for the viewer to better
479 evaluate what is being said and done. That would be a feature I would
480 be willing to pay for.</p>
481
482 <p>I would not be willing to pay for a TV that point a camera on my
483 household, like the big brother feature apparently proposed by Intel.
484 It is the telescreen idea fetched straight out of the book
485 <a href="http://gutenberg.net.au/ebooks01/0100021.txt">1984 by George
486 Orwell</a>.</p>
487
488 </div>
489 <div class="tags">
490
491
492 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
493
494
495 </div>
496 </div>
497 <div class="padding"></div>
498
499 <div class="entry">
500 <div class="title">
501 <a href="http://people.skolelinux.org/pere/blog/Litt_statistikk_fra_Offentlig_Elektronisk_postjournal.html">Litt statistikk fra Offentlig Elektronisk postjournal</a>
502 </div>
503 <div class="date">
504 10th June 2012
505 </div>
506 <div class="body">
507 <p>De siste månedene har jeg sammen med andre i NUUG jobbet med å
508 gjøre det enklere å få innsyn i offentlige dokumenter, og dette
509 inkluderer å gjøre postjournaler enklere tilgjengelig for maskinell
510 analyse og søk. I den forbindelse tok jeg i dag å tittet litt på
511 <a href="http://www.oep.no/">Offentlig Elektronisk Postjournal
512 (OEP)</a>, FAD/DIFIs fellesløsning for departementer og statlige
513 etater.</p>
514
515 <p>Her er antall oppføringer pr. måned det siste året,
516 <a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=htmltable&name=postliste-oep&query=select%20strftime(%22%25Y-%25m%22%2C%20%60recordpublishdate%60)%20as%20oeppubmonth%2C%20count(*)%20from%20%60swdata%60%20group%20by%20oeppubmonth%20order%20by%20oeppubmonth">summert
517 opp</a> ved hjelp av
518 <a href="https://scraperwiki.com/scrapers/postliste-oep/">en
519 Scraperwiki-database</a>. Merk at denne Scraperwikien har
520 ytelsesproblemer pga. mengden data. </p>
521
522 <p><table border="1">
523 <tr><th>Måned</th><th>Antall</th></tr>
524 <tr><td>2011-07</td><td>164355</td></tr>
525 <tr><td>2011-08</td><td>153662</td></tr>
526 <tr><td>2011-09</td><td>173134</td></tr>
527 <tr><td>2011-10</td><td>170665</td></tr>
528 <tr><td>2011-11</td><td>198409</td></tr>
529 <tr><td>2011-12</td><td>175908</td></tr>
530 <tr><td>2012-01</td><td>206875</td></tr>
531 <tr><td>2012-02</td><td>202862</td></tr>
532 <tr><td>2012-03</td><td>204225</td></tr>
533 <tr><td>2012-04</td><td>207931</td></tr>
534 <tr><td>2012-05</td><td>223754</td></tr>
535 </table></p>
536
537 <p>Det er også interessant å se hvor ofte ulike etater sender inn sine
538 journaloppføringer til OEP. OEP inneholder en liste med sist
539 innrapporteringsdato for alle som sender til OEP, og ved å se når og
540 hvor ofte det blir sendt inn fra etatene kan
541 <a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=htmltable&name=postliste-oep-deliverydates&query=select%20agency%2C%0A(julianday(datetime('now'))%20-%20%0A%20julianday(min(%60deliverydate%60)))%2Fcount(*)%20as%20dayfreq%2C%0A%20count(*)%0Afrom%20%60swdata%60%20group%20by%20agency%20order%20by%20dayfreq%20desc">frekvensen
542 beregnes</a>. Her er bunnlista, dvs. de som leverer mer enn hver 10
543 dag beregnet fra
544 <a href="https://scraperwiki.com/scrapers/postliste-oep-deliverydates/">en
545 Scraperwiki-database</a>:</p>
546
547 <p><table border="1">
548
549 <tr> <th>Etat</th> <th>Frekvens</th> <th>Leveringer</th> </tr>
550 <tr> <td>Norges geologiske undersøkelse</td> <td>83.7527546296</td> <td>1</td> </tr>
551 <tr> <td>Medietilsynet</td> <td>33.7527546296</td> <td>1</td> </tr>
552 <tr> <td>Departementenes servicesenter</td> <td>23.8763773148</td> <td>2</td> </tr>
553 <tr> <td>Kunnskapsdepartementet</td> <td>15.8763773148</td> <td>2</td> </tr>
554 <tr> <td>Kompetansesenter for distriktsutvikling</td> <td>15.3763773148</td> <td>2</td> </tr>
555 <tr> <td>Toll- og avgiftsdirektoratet</td> <td>15.3763773148</td> <td>2</td> </tr>
556 <tr> <td>Fredskorpset</td> <td>12.5842515432</td> <td>3</td> </tr>
557 <tr> <td>Statens legemiddelverk</td> <td>12.1881886574</td> <td>4</td> </tr>
558 <tr> <td>Utlendingsnemnda</td> <td>11.5842515432</td> <td>3</td> </tr>
559 <tr> <td>Politidirektoratet</td> <td>10.9175848765</td> <td>3</td> </tr>
560 <tr> <td>Skattedirektoratet</td> <td>10.9175848765</td> <td>3</td> </tr>
561 <tr> <td>Statens innkrevingssentral</td> <td>10.5842515432</td> <td>3</td> </tr>
562 <tr> <td>Barne-, ungdoms- og familiedirektoratet</td> <td>10.2509182099</td> <td>3</td> </tr>
563 <tr> <td>Kunst i offentlige rom</td> <td>10.2509182099</td> <td>3</td> </tr>
564
565 </table></p>
566
567 <p>En kan beregne lignende frekvenser ved å sammenligne
568 journalføringsdato med publiseringsdato for hver enkelt oppføring i
569 OEP, men den lenken legger jeg ikke ved her for å unngå at
570 søkemotorroboter begynner å overbelaste Scraperwiki-databasen.</p>
571
572 <p>Jeg har spurt Norges geologiske undersøkelse om hvorfor de leverer
573 så sjelden, og det kommer av at de har problemer etter oppgradering av
574 arkivsystemet sitt og jobber med å fikse det slik at de kan gå tilbake
575 til å levere hver uke. Har ikke undersøkt noen av de andre.</p>
576
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/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>.
582
583
584 </div>
585 </div>
586 <div class="padding"></div>
587
588 <div class="entry">
589 <div class="title">
590 <a href="http://people.skolelinux.org/pere/blog/Debian_Edu___some_ideas_for_the_future_versions.html">Debian Edu - some ideas for the future versions</a>
591 </div>
592 <div class="date">
593 11th June 2012
594 </div>
595 <div class="body">
596 <p>During my work on Debian Edu based on Squeeze, I came across some
597 issues that should be addressed in the Wheezy release. I finally
598 found time to wrap up my notes and provide quick summary of what I
599 found, with a bit explanation.</p>
600
601 <p><ul>
602
603 <li>We need to rewrite our package installation framework, as tasksel
604 changed from using tasksel tasks to using meta packages (aka packages
605 with dependencies like our education-* packages), and our installation
606 system depend on tasksel tasks in
607 /usr/share/tasksel/debian-edu-tasks.desc for package
608 installation.</li>
609
610 <li>Enable Kerberos login for more services. Now with the Kerberos
611 foundation in place, we should use it to get single sign on with more
612 services, and avoiding unneeded password / login questions. We should
613 at least try to enable it for these services:
614 <ul>
615
616 <li>CUPS for admins to add/configure printers and users when using
617 quotas.</li>
618 <li>Nagios for admins checking the system status.</li>
619 <li>GOsa for admins updating LDAP and users changing their passwords.</li>
620 <li>LDAP for admins updating LDAP.</li>
621 <li>Squid for users when exam mode / filtering is active.</li>
622 <li>ssh for admins and users to save a password prompt.</li>
623
624 </ul></li>
625
626 <li>When we move GOsa to use Kerberos instead of LDAP bind to
627 authenticate users, we should try to block or at least limit access to
628 use LDAP bind for authentication, to ensure Kerberos is used when it
629 is intended, and nothing fall back to using the less safe LDAP bind</li>
630
631 <li>Merge debian-edu-config and debian-edu-install. The split made
632 sense when d-e-install did a lot more, but these days it is just an
633 inconvenience when we update the debconf preseeding values.</li>
634
635 <li>Fix partman-auto to allow us to abort the installation before
636 touching the disk if the disk is too small. This is
637 <a href="http://bugs.debian.org/653305">BTS report #653305</a> and the
638 d-i developers are fine with the patch and someone just need to apply
639 it and upload.</li>
640
641 <li>Adjust to new LTSP framework (boot time config instead of install
642 time config). LTSP changed its design, and our hooks to install
643 packages and update the configuration is most likely not going to work
644 in Wheezy.
645
646 <li>Consider switching to NBD instead of NFS for LTSP root, to allow
647 the Kernel to cache files in its normal file cache, possibly speeding
648 up KDE login on slow networks.</li>
649
650 <li>Make it possible to create expired user passwords that need to
651 change on first login. This is useful when handing out password on
652 paper, to make sure only the user know the password. This require
653 fixes to the PAM handling of kdm and gdm.</li>
654
655 <li>Make GUI for adding new machines automatically from sitesummary.
656 The current command line script is not very friendly to people most
657 familiar with GUIs. This should probably be integrated into GOsa to
658 have it available where the admin will be looking for it..</li>
659
660 <li>We should find way for Nagios to check that the DHCP service
661 actually is working (as in handling out IP addresses). None of the
662 Nagios checks I have found so far have been working for me.</li>
663
664 <li>We should switch from libpam-nss-ldapd to sssd for all profiles
665 using LDAP, and not only on for roaming workstations, to have less
666 packages to configure and consistent setup across all profiles.</li>
667
668 <li>We should configure Kerberos to update LDAP and Samba password
669 when changing password using the Kerberos protocol. The hook was
670 requested in <a href="http://bugs.debian.org/588968">BTS report
671 #588968</a> and is now available in Wheezy. We might need to write a
672 MIT Kerberos plugin in C to get this.</li>
673
674 <li>We should clean up the set of applications installed by default.
675 <ul>
676
677 <li>reduce the number of chemistry visualisers</li>
678 <li>consider dropping xpaint</li>
679 <li>and probably more?</li>
680 </ul></li>
681
682 <li>Some hardware need external firmware to work properly. This is
683 mostly the case for WiFi network cards, but there are some other
684 examples too. For popular laptops to work out of the box, such
685 firmware need to be installed from non-free, and we should provide
686 some GUI to do this. Ubuntu already have this implemented, and we
687 could consider using their packages. At the moment we have some
688 command line script to do this (one for the running system, another
689 for the LTSP chroot).</li>
690
691
692 <li>In Squeeze, we provide KDE, Gnome and LXDE as desktop options. We
693 should extend the list to Xfce and Sugar, and preferably find a way to
694 install several and allow the admin or the user to select which one to
695 use.</li>
696
697 <li>The golearn tool from the goplay package make it easy to check out
698 interesting educational packages. We should work on the package
699 tagging in Debian to ensure it represent all the useful educational
700 packages, and extend the tool to allow it to use packagekit to install
701 new applications with a simple mouse click.</li>
702
703 <li>The Squeeze version got half a exam solution already in place,
704 with the introduction of iptable based network blocking, but for it to
705 be a complete exam solution the Squid proxy need to enable
706 filtering/blocking as well when the exam mode is enabled. We should
707 implement a way to easily enable this for the schools that want it,
708 instead of the "it is documented" method of today.</li>
709
710 <li>A feature used in several schools is the ability for a teacher to
711 "take over" the desktop of individual or all computers in the room.
712 There are at least three implementations,
713 <a href="italc.sourceforge.net/">italc</a>,
714 <a href="http://www.itais.net/help/en/">controlaula</a> og
715 <a href="http://www.epoptes.org/">epoptes</a> and we should pick one of
716 them and make it trivial to set it up in a school. The challenges is
717 how to distribute crypto keys and how to group computers in one room
718 and how to set up which machine/user can control the machines in a
719 given room.</li>
720
721 <li>Tablets and surf boards are getting more and more popular, and we
722 should look into providing a good solution for integrating these into
723 the Debian Edu network. Not quite sure how. Perhaps we should
724 provide a installation profile with better touch screen support for
725 them, or add some sync services to allow them to exchange
726 configuration and data with the central server. This should be
727 investigated.</li>
728
729 </ul></p>
730
731 <p>I guess we will discover more as we continue to work on the Wheezy
732 version.</p>
733
734 </div>
735 <div class="tags">
736
737
738 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>.
739
740
741 </div>
742 </div>
743 <div class="padding"></div>
744
745 <p style="text-align: right;"><a href="06.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
746 <div id="sidebar">
747
748
749
750 <h2>Archive</h2>
751 <ul>
752
753 <li>2012
754 <ul>
755
756 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
757
758 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
759
760 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
761
762 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
763
764 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
765
766 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (8)</a></li>
767
768 </ul></li>
769
770 <li>2011
771 <ul>
772
773 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
774
775 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
776
777 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
778
779 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
780
781 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
782
783 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
784
785 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
786
787 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
788
789 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
790
791 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
792
793 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
794
795 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
796
797 </ul></li>
798
799 <li>2010
800 <ul>
801
802 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
803
804 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
805
806 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
807
808 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
809
810 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
811
812 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
813
814 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
815
816 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
817
818 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
819
820 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
821
822 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
823
824 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
825
826 </ul></li>
827
828 <li>2009
829 <ul>
830
831 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
832
833 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
834
835 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
836
837 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
838
839 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
840
841 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
842
843 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
844
845 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
846
847 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
848
849 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
850
851 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
852
853 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
854
855 </ul></li>
856
857 <li>2008
858 <ul>
859
860 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
861
862 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
863
864 </ul></li>
865
866 </ul>
867
868
869
870 <h2>Tags</h2>
871 <ul>
872
873 <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
874
875 <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
876
877 <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
878
879 <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (2)</a></li>
880
881 <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (12)</a></li>
882
883 <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
884
885 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (54)</a></li>
886
887 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (104)</a></li>
888
889 <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (8)</a></li>
890
891 <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (3)</a></li>
892
893 <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (135)</a></li>
894
895 <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (16)</a></li>
896
897 <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
898
899 <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (27)</a></li>
900
901 <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (16)</a></li>
902
903 <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
904
905 <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (4)</a></li>
906
907 <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
908
909 <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (16)</a></li>
910
911 <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (170)</a></li>
912
913 <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (130)</a></li>
914
915 <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (1)</a></li>
916
917 <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
918
919 <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (25)</a></li>
920
921 <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (47)</a></li>
922
923 <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
924
925 <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
926
927 <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
928
929 <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (4)</a></li>
930
931 <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
932
933 <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
934
935 <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (1)</a></li>
936
937 <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (23)</a></li>
938
939 <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
940
941 <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (29)</a></li>
942
943 <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
944
945 <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (4)</a></li>
946
947 <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (10)</a></li>
948
949 <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (6)</a></li>
950
951 <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (25)</a></li>
952
953 <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (1)</a></li>
954
955 <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (20)</a></li>
956
957 </ul>
958
959
960 </div>
961 <p style="text-align: right">
962 Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.4</a>
963 </p>
964
965 </body>
966 </html>