1 <?xml version=
"1.0" encoding=
"ISO-8859-1"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries from September
2014</title>
5 <description>Entries from September
2014</description>
6 <link>http://www.hungry.com/~pere/blog/
</link>
10 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
11 <link>http://www.hungry.com/~pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
12 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
13 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
14 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
15 project
</a
> provide a Linux solution for schools, including a
16 powerful desktop with education software, a central server providing
17 web pages, user database, user home directories, central login and PXE
18 boot of both clients without disk and the installation to install Debian
19 Edu on machines with disk (and a few other services perhaps to small
20 to mention here). We in the Debian Edu team are currently working on
21 the Jessie based version, trying to get everything in shape before the
22 freeze, to avoid having to maintain our own package repository in the
24 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
25 status
</a
> can be seen on the Debian wiki, and there is still heaps of
26 work left. Some fatal problems block testing, breaking the installer,
27 but it is possible to work around these to get anyway. Here is a
28 recipe on how to get the installation limping along.
</p
>
30 <p
>First, download the test ISO via
31 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
32 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
34 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
35 The ISO build was broken on Tuesday, so we do not get a new ISO every
36 12 hours or so, but thankfully the ISO we already got we are able to
37 install with some tweaking.
</p
>
39 <p
>When you get to the Debian Edu profile question, go to tty2
40 (use Alt-Ctrl-F2), run
</p
>
42 <p
><blockquote
><pre
>
43 nano /usr/bin/edu-eatmydata-install
44 </pre
></blockquote
></p
>
46 <p
>and add
'exit
0' as the second line, disabling the eatmydata
47 optimization. Return to the installation, select the profile you want
48 and continue. Without this change, exim4-config will fail to install
49 due to a known bug in eatmydata.
</p
>
51 <p
>When you get the grub question at the end, answer /dev/sda (or if
52 this do not work, figure out what your correct value would be. All my
53 test machines need /dev/sda, so I have no advice if it do not fit
56 <p
>If you installed a profile including a graphical desktop, log in as
57 root after the initial boot from hard drive, and install the
58 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
59 or mate. If you want several desktop options, install more than one
60 metapackage. Once this is done, reboot and you should have a working
61 graphical login screen. This workaround should no longer be needed
62 once the education-tasks package version
1.801 enter testing in two
65 <p
>I believe the ISO build will start working on two days when the new
66 tasksel package enter testing and Steve McIntyre get a chance to
67 update the debian-cd git repository. The eatmydata, grub and desktop
68 issues are already fixed in unstable and testing, and should show up
69 on the ISO as soon as the ISO build start working again. Well the
70 eatmydata optimization is really just disabled. The proper fix
71 require an upload by the eatmydata maintainer applying the patch
72 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
73 The rest have proper fixes in unstable.
</p
>
75 <p
>I hope this get you going with the installation testing, as we are
76 quickly running out of time trying to get our Jessie based
77 installation ready before the distribution freeze in a month.
</p
>
82 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
83 <link>http://www.hungry.com/~pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
84 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
85 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
86 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
87 to handle my fairly large DVD collection. It is a nice command line
88 tool to get details about a DVD, like title, tracks, track length,
89 etc, in XML, Perl or human readable format. But lsdvd have not seen
90 any new development since
2006 and had a few irritating bugs affecting
91 its use with some DVDs. Upstream seemed to be dead, and in January I
92 sent a small probe asking for a version control repository for the
93 project, without any reply. But I use it regularly and would like to
94 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
95 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
96 the project admin, and after getting a reply from him explaining that
97 he was no longer interested in the project, I asked if I could take
98 over. And yesterday, I became project admin.
</p
>
100 <p
>I
've been in touch with a Gentoo developer and the Debian
101 maintainer interested in joining forces to maintain the upstream
102 project, and I hope we can get a new release out fairly quickly,
103 collecting the patches spread around on the internet into on place.
104 I
've added the relevant Debian patches to the freshly created git
105 repository, and expect the Gentoo patches to make it too. If you got
106 a DVD collection and care about command line tools, check out
107 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
108 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
109 list
</a
>. :)
</p
>
114 <title>Hva henger under skibrua over E16 på Sollihøgda?
</title>
115 <link>http://www.hungry.com/~pere/blog/Hva_henger_under_skibrua_over_E16_p__Sollih_gda_.html
</link>
116 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/Hva_henger_under_skibrua_over_E16_p__Sollih_gda_.html
</guid>
117 <pubDate>Sun,
21 Sep
2014 09:
50:
00 +
0200</pubDate>
118 <description><p
>Rundt omkring i Oslo og Østlandsområdet henger det bokser over
119 veiene som jeg har lurt på hva gjør. De har ut fra plassering og
120 vinkling sett ut som bokser som sniffer ut et eller annet fra
121 forbipasserende trafikk, men det har vært uklart for meg hva det er de
122 leser av. Her om dagen tok jeg bilde av en slik boks som henger under
123 <a href=
"http://www.openstreetmap.no/?zoom=
19&mlat=
59.96396&mlon=
10.34443&layers=B00000
">ei
124 skibru på Sollihøgda
</a
>:
</p
>
126 <p align=
"center
"><img width=
"60%
" src=
"https://people.skolelinux.org/pere/blog/images/
2014-
09-
13-kapsch-sollihogda-crop.jpeg
"></p
>
128 <p
>Boksen er tydelig merket «Kapsch
>>>», logoen til
129 <a href=
"http://www.kapsch.net/
">det sveitsiske selskapet Kapsch
</a
> som
130 blant annet lager sensorsystemer for veitrafikk. Men de lager mye
131 forskjellig, og jeg kjente ikke igjen boksen på utseendet etter en
132 kjapp titt på produktlista til selskapet.
</p
>
134 <p
>I og med at boksen henger over veien E16, en riksvei vedlikeholdt
135 av Statens Vegvesen, så antok jeg at det burde være mulig å bruke
136 REST-API-et som gir tilgang til vegvesenets database over veier,
137 skilter og annet veirelatert til å finne ut hva i alle dager dette
138 kunne være. De har både
139 <a href=
"https://www.vegvesen.no/nvdb/api/dokumentasjon/datakatalog
">en
140 datakatalog
</a
> og
141 <a href=
"https://www.vegvesen.no/nvdb/api/dokumentasjon/sok
">et
142 søk
</a
>, der en kan søke etter ulike typer oppføringer innen for et
143 gitt geografisk område. Jeg laget et enkelt shell-script for å hente
144 ut antall av en gitt type innenfor området skibrua dekker, og listet
145 opp navnet på typene som ble funnet. Orket ikke slå opp hvordan
146 URL-koding av aktuelle strenger kunne gjøres mer generisk, og brukte
147 en stygg sed-linje i stedet.
</p
>
149 <blockquote
><pre
>
153 -e
's/ / /g
' -e
's/{/%
7B/g
' \
154 -e
's/}/%
7D/g
' -e
's/\[/%
5B/g
' \
155 -e
's/\]/%
5D/g
' -e
's/ /%
20/g
' \
156 -e
's/,/%
2C/g
' -e
's/\
"/%
22/g
' \
157 -e
's/:/%
3A/g
'
162 curl -s -H
'Accept: application/vnd.vegvesen.nvdb-v1+xml
' \
163 "https://www.vegvesen.no/nvdb/api$url
" | xmllint --format -
166 for id in $(seq
1 874) ; do
169 bbox: \
"10.34425,
59.96386,
10.34458,
59.96409\
",
170 srid: \
"WGS84\
"
177 query=/sok?kriterie=$(echo $search | urlmap)
178 if lookup
"$query
" |
179 grep -q
'&lt;totaltAntallReturnert
>0&lt;
'
184 lookup
"/datakatalog/objekttyper/$id
" |grep
'^
&lt;navn
>'
189 </pre
></blockquote
>
191 Aktuelt ID-område
1-
874 var riktig i datakatalogen da jeg laget
192 scriptet. Det vil endre seg over tid. Skriptet listet så opp
193 aktuelle typer i og rundt skibrua:
195 <blockquote
><pre
>
197 &lt;navn
>Rekkverk
&lt;/navn
>
199 &lt;navn
>Rekkverksende
&lt;/navn
>
201 &lt;navn
>Trafikklomme
&lt;/navn
>
203 &lt;navn
>Trafikkøy
&lt;/navn
>
205 &lt;navn
>Bru
&lt;/navn
>
207 &lt;navn
>Stikkrenne/Kulvert
&lt;/navn
>
209 &lt;navn
>Grøft, åpen
&lt;/navn
>
211 &lt;navn
>Belysningsstrekning
&lt;/navn
>
213 &lt;navn
>Skiltpunkt
&lt;/navn
>
215 &lt;navn
>Skiltplate
&lt;/navn
>
217 &lt;navn
>Referansestolpe
&lt;/navn
>
219 &lt;navn
>Vegoppmerking, langsgående
&lt;/navn
>
221 &lt;navn
>Fartsgrense
&lt;/navn
>
223 &lt;navn
>Vinterdriftsstrategi
&lt;/navn
>
225 &lt;navn
>Trafikkdeler
&lt;/navn
>
227 &lt;navn
>Vegdekke
&lt;/navn
>
229 &lt;navn
>Breddemåling
&lt;/navn
>
231 &lt;navn
>Kantklippareal
&lt;/navn
>
233 &lt;navn
>Snø-/isrydding
&lt;/navn
>
235 &lt;navn
>Skred
&lt;/navn
>
237 &lt;navn
>Dokumentasjon
&lt;/navn
>
239 &lt;navn
>Undergang
&lt;/navn
>
241 &lt;navn
>Tverrprofil
&lt;/navn
>
243 &lt;navn
>Vegreferanse
&lt;/navn
>
245 &lt;navn
>Region
&lt;/navn
>
247 &lt;navn
>Fylke
&lt;/navn
>
249 &lt;navn
>Kommune
&lt;/navn
>
251 &lt;navn
>Gate
&lt;/navn
>
253 &lt;navn
>Transportlenke
&lt;/navn
>
255 &lt;navn
>Trafikkmengde
&lt;/navn
>
257 &lt;navn
>Trafikkulykke
&lt;/navn
>
259 &lt;navn
>Ulykkesinvolvert enhet
&lt;/navn
>
261 &lt;navn
>Ulykkesinvolvert person
&lt;/navn
>
263 &lt;navn
>Politidistrikt
&lt;/navn
>
265 &lt;navn
>Vegbredde
&lt;/navn
>
267 &lt;navn
>Høydebegrensning
&lt;/navn
>
269 &lt;navn
>Nedbøyningsmåling
&lt;/navn
>
271 &lt;navn
>Støy-luft, Strekningsdata
&lt;/navn
>
273 &lt;navn
>Oppgravingsdata
&lt;/navn
>
275 &lt;navn
>Oppgravingslag
&lt;/navn
>
277 &lt;navn
>PMS-parsell
&lt;/navn
>
279 &lt;navn
>Vegnormalstrekning
&lt;/navn
>
281 &lt;navn
>Værrelatert strekning
&lt;/navn
>
283 &lt;navn
>Feltstrekning
&lt;/navn
>
285 &lt;navn
>Adressepunkt
&lt;/navn
>
287 &lt;navn
>Friksjonsmåleserie
&lt;/navn
>
289 &lt;navn
>Vegdekke, flatelapping
&lt;/navn
>
291 &lt;navn
>Kurvatur, horisontalelement
&lt;/navn
>
293 &lt;navn
>Kurvatur, vertikalelement
&lt;/navn
>
295 &lt;navn
>Kurvatur, vertikalpunkt
&lt;/navn
>
297 &lt;navn
>Statistikk, trafikkmengde
&lt;/navn
>
299 &lt;navn
>Statistikk, vegbredde
&lt;/navn
>
301 &lt;navn
>Nedbøyningsmåleserie
&lt;/navn
>
303 &lt;navn
>ATK, influensstrekning
&lt;/navn
>
305 &lt;navn
>Systemobjekt
&lt;/navn
>
307 &lt;navn
>Vinterdriftsklasse
&lt;/navn
>
309 &lt;navn
>Funksjonell vegklasse
&lt;/navn
>
311 &lt;navn
>Kurvatur, stigning
&lt;/navn
>
313 &lt;navn
>Vegbredde, beregnet
&lt;/navn
>
315 &lt;navn
>Reisetidsregistreringspunkt
&lt;/navn
>
317 &lt;navn
>Bruksklasse
&lt;/navn
>
318 </pre
></blockquote
>
320 <p
>Av disse ser ID
775 og
862 mest relevant ut. ID
775 antar jeg
321 refererer til fotoboksen som står like ved brua, mens
322 «Reisetidsregistreringspunkt» kanskje kan være boksen som henger der.
323 Hvordan finner jeg så ut hva dette kan være for noe. En titt på
324 <a href=
"http://labs.vegdata.no/nvdb-datakatalog/
862-Reisetidsregistreringspunkt/
">datakatalogsiden
325 for ID
862/Reisetidsregistreringspunkt
</a
> viser at det er finnes
53
326 slike målere i Norge, og hvor de er plassert, men gir ellers få
327 detaljer. Det er plassert
40 på østlandet og
13 i Trondheimsregionen.
328 Men siden nevner «AutoPASS», og hvis en slår opp oppføringen på
329 Sollihøgda nevner den «Ciber AS» som ID for eksternt system. (Kan det
331 <a href=
"http://www.proff.no/selskap/ciber-norge-as/oslo/internettdesign-og-programmering/Z0I3KMF4/
">Ciber
332 Norge AS
</a
>, et selskap eid av Ciber Europe Bv?) Et nettsøk på
333 «Ciber AS autopass» fører meg til en artikkel fra NRK Trøndelag i
335 «
<a href=
"http://www.nrk.no/trondelag/sjekk-dette-hvis-du-vil-unnga-ko-
1.11327947">Sjekk
336 dette hvis du vil unngå kø
</a
>». Artikkelen henviser til vegvesenets
338 <a href=
"http://www.reisetider.no/reisetid/forside.html
">reisetider.no
</a
>
340 <a href=
"http://www.reisetider.no/reisetid/omrade.html?omrade=
5">kartside
341 for Østlandet
</a
> som viser at det måles mellom Sandvika og Sollihøgda.
342 Det kan dermed se ut til at jeg har funnet ut hva boksene gjør.
</p
>
344 <p
>Hvis det stemmer, så er dette bokser som leser av AutoPASS-ID-en
345 til alle passerende biler med AutoPASS-brikke, og dermed gjør det mulig
346 for de som kontrollerer boksene å holde rede på hvor en gitt bil er
347 når den passerte et slikt målepunkt. NRK-artikkelen forteller at
348 denne informasjonen i dag kun brukes til å koble to
349 AutoPASS-brikkepasseringer passeringer sammen for å beregne
350 reisetiden, og at bruken er godkjent av Datatilsynet. Det er desverre
351 ikke mulig for en sjåfør som passerer under en slik boks å kontrollere
352 at AutoPASS-ID-en kun brukes til dette i dag og i fremtiden.
</p
>
354 <p
>I tillegg til denne type AutoPASS-sniffere vet jeg at det også
355 finnes mange automatiske stasjoner som tar betalt pr. passering (aka
356 bomstasjoner), og der lagres informasjon om tid, sted og bilnummer i
357 10 år. Finnes det andre slike sniffere plassert ut på veiene?
</p
>
359 <p
>Personlig har jeg valgt å ikke bruke AutoPASS-brikke, for å gjøre
360 det vanskeligere og mer kostbart for de som vil invadere privatsfæren
361 og holde rede på hvor bilen min beveger seg til enhver tid. Jeg håper
362 flere vil gjøre det samme, selv om det gir litt høyere private
363 utgifter (dyrere bompassering). Vern om privatsfæren koster i disse
366 <p
>Takk til Jan Kristian Jensen i Statens Vegvesen for tips om
367 dokumentasjon på vegvesenets REST-API.
</p
>
369 <p
>Bruksvilkår på bildet er
370 <a href=
"https://creativecommons.org/publicdomain/
">public domain eller
371 CC0
</a
> alt etter hva som fungerer best for mottaker.
</p
>
373 <p
>Oppdatering
2014-
12-
17: Veldig hyggelig å se at mine notater
374 <a href=
"http://www.vegdata.no/
2014/
11/
04/hva-henger-under-brua-over-e16-pa-sollihogda/
">fikk
375 omtale på vegdata-bloggen
</a
>.
</p
>
380 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
381 <link>http://www.hungry.com/~pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
382 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
383 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
384 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
385 a lot quicker. When we install more than
2000 packages in
386 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
387 tasksel in the installer, unpacking the binary packages take forever.
388 A part of the slow I/O issue was discussed in
389 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
390 much file system sync-ing done by dpkg, which is the package
391 responsible for unpacking the binary packages. Other parts (like code
392 executed by postinst scripts) might also sync to disk during
393 installation. All this sync-ing to disk do not really make sense to
394 me. If the machine crash half-way through, I start over, I do not try
395 to salvage the half installed system. So the failure sync-ing is
396 supposed to protect against, hardware or system crash, is not really
397 relevant while the installer is running.
</p
>
399 <p
>A few days ago, I thought of a way to get rid of all the file
400 system sync()-ing in a fairly non-intrusive way, without the need to
401 change the code in several packages. The idea is not new, but I have
402 not heard anyone propose the approach using dpkg-divert before. It
403 depend on the small and clever package
404 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
405 uses LD_PRELOAD to replace the system functions for syncing data to
406 disk with functions doing nothing, thus allowing programs to live
407 dangerous while speeding up disk I/O significantly. Instead of
408 modifying the implementation of dpkg, apt and tasksel (which are the
409 packages responsible for selecting, fetching and installing packages),
410 it occurred to me that we could just divert the programs away, replace
411 them with a simple shell wrapper calling
412 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
413 Two days ago I decided to test the idea, and wrapped up a simple
414 implementation for the Debian Edu udeb.
</p
>
416 <p
>The effect was stunning. In my first test it reduced the running
417 time of the pkgsel step (installing tasks) from
64 to less than
44
418 minutes (
20 minutes shaved off the installation) on an old Dell
419 Latitude D505 machine. I am not quite sure what the optimised time
420 would have been, as I messed up the testing a bit, causing the debconf
421 priority to get low enough for two questions to pop up during
422 installation. As soon as I saw the questions I moved the installation
423 along, but do not know how long the question were holding up the
424 installation. I did some more measurements using Debian Edu Jessie,
425 and got these results. The time measured is the time stamp in
426 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
427 "pkgsel: finishing up
" lines, if you want to do the same measurement
428 yourself. In Debian Edu, the tasksel dialog do not show up, and the
429 timing thus do not depend on how quickly the user handle the tasksel
432 <p
><table
>
435 <th
>Machine/setup
</th
>
436 <th
>Original tasksel
</th
>
437 <th
>Optimised tasksel
</th
>
438 <th
>Reduction
</th
>
442 <td
>Latitude D505 Main+LTSP LXDE
</td
>
443 <td
>64 min (
07:
46-
08:
50)
</td
>
444 <td
><44 min (
11:
27-
12:
11)
</td
>
445 <td
>>20 min
18%
</td
>
449 <td
>Latitude D505 Roaming LXDE
</td
>
450 <td
>57 min (
08:
48-
09:
45)
</td
>
451 <td
>34 min (
07:
43-
08:
17)
</td
>
452 <td
>23 min
40%
</td
>
456 <td
>Latitude D505 Minimal
</td
>
457 <td
>22 min (
10:
37-
10:
59)
</td
>
458 <td
>11 min (
11:
16-
11:
27)
</td
>
459 <td
>11 min
50%
</td
>
463 <td
>Thinkpad X200 Minimal
</td
>
464 <td
>6 min (
08:
19-
08:
25)
</td
>
465 <td
>4 min (
08:
04-
08:
08)
</td
>
466 <td
>2 min
33%
</td
>
470 <td
>Thinkpad X200 Roaming KDE
</td
>
471 <td
>19 min (
09:
21-
09:
40)
</td
>
472 <td
>15 min (
10:
25-
10:
40)
</td
>
473 <td
>4 min
21%
</td
>
476 </table
></p
>
478 <p
>The test is done using a netinst ISO on a USB stick, so some of the
479 time is spent downloading packages. The connection to the Internet
480 was
100Mbit/s during testing, so downloading should not be a
481 significant factor in the measurement. Download typically took a few
482 seconds to a few minutes, depending on the amount of packages being
485 <p
>The speedup is implemented by using two hooks in
486 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
487 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
488 finish-install.d hook to remove the divert at the end of the
489 installation. I picked the pre-pkgsel.d hook instead of the
490 post-base-installer.d hook because I test using an ISO without the
491 eatmydata package included, and the post-base-installer.d hook in
492 Debian Edu can only operate on packages included in the ISO. The
493 negative effect of this is that I am unable to activate this
494 optimization for the kernel installation step in d-i. If the code is
495 moved to the post-base-installer.d hook, the speedup would be larger
496 for the entire installation.
</p
>
498 <p
>I
've implemented this in the
499 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
500 git repository, and plan to provide the optimization as part of the
501 Debian Edu installation. If you want to test this yourself, you can
502 create two files in the installer (or in an udeb). One shell script
503 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
505 <p
><blockquote
><pre
>
508 . /usr/share/debconf/confmodule
510 logger -t my-pkgsel
"info: $*
"
513 logger -t my-pkgsel
"error: $*
"
516 apt-install eatmydata || true
517 if [ -x /target/usr/bin/eatmydata ] ; then
518 for bin in dpkg apt-get aptitude tasksel ; do
520 # Test that the file exist and have not been diverted already.
521 if [ -f /target$file ] ; then
522 info
"diverting $file using eatmydata
"
523 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
524 > /target$file.edu
525 chmod
755 /target$file.edu
526 in-target dpkg-divert --package debian-edu-config \
527 --rename --quiet --add $file
528 ln -sf ./$bin.edu /target$file
530 error
"unable to divert $file, as it is missing.
"
534 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
539 </pre
></blockquote
></p
>
541 <p
>To clean up, another shell script should go into
542 /usr/lib/finish-install.d/ with code like this:
544 <p
><blockquote
><pre
>
546 . /usr/share/debconf/confmodule
548 logger -t my-finish-install
"error: $@
"
550 remove_install_override() {
551 for bin in dpkg apt-get aptitude tasksel ; do
553 if [ -x /target$file.edu ] ; then
555 in-target dpkg-divert --package debian-edu-config \
556 --rename --quiet --remove $file
559 error
"Missing divert for $file.
"
562 sync # Flush file buffers before continuing
565 remove_install_override
566 </pre
></blockquote
></p
>
568 <p
>In Debian Edu, I placed both code fragments in a separate script
569 edu-eatmydata-install and call it from the pre-pkgsel.d and
570 finish-install.d scripts.
</p
>
572 <p
>By now you might ask if this change should get into the normal
573 Debian installer too? I suspect it should, but am not sure the
574 current debian-installer coordinators find it useful enough. It also
575 depend on the side effects of the change. I
'm not aware of any, but I
576 guess we will see if the change is safe after some more testing.
577 Perhaps there is some package in Debian depending on sync() and
578 fsync() having effect? Perhaps it should go into its own udeb, to
579 allow those of us wanting to enable it to do so without affecting
582 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
583 will break installation of all programs using gnutls because of
584 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
585 eatmydata package in Debian will solve it.
</p
>
587 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
588 the optimization work again. And I have discovered that the
589 dpkg-divert trick is not really needed and implemented a slightly
590 simpler approach as part of the debian-edu-install package. See
591 tools/edu-eatmydata-install in the source package.
</p
>
593 <p
>Update
2014-
11-
11: Unfortunately, a new
594 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
595 triggering on i386 made it into testing, and broke this installation
596 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
597 request
768893</a
> is accepted, it should be working again.
</p
>
602 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
603 <link>http://www.hungry.com/~pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
604 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
605 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
606 <description><p
>Yesterday, I had the pleasure of attending a talk with the
607 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
608 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
609 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
610 learn that there is a large set of publicly available key servers to
611 use when looking for peoples public key. So far I have used
612 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
613 were misbehaving, but those days are ended. The servers I have used
614 up until yesterday have been slow and some times unavailable. I hope
615 those problems are gone now.
</p
>
617 <p
>Behind the round robin DNS entry of the
618 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
619 there is a pool of more than
100 keyservers which are checked every
620 day to ensure they are well connected and up to date. It must be
621 better than what I have used so far. :)
</p
>
623 <p
>Yesterdays speaker told me that the service is the default
624 keyserver provided by the default configuration in GnuPG, but this do
625 not seem to be used in Debian. Perhaps it should?
</p
>
627 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
630 <p
><blockquote
><pre
>
631 keyserver pool.sks-keyservers.net
632 </pre
></blockquote
></p
>
634 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
635 entries in DNS. Just for fun, I did just that at work, so now every
636 user of GnuPG at the University of Oslo should find a OpenGPG
637 keyserver automatically should their need it:
</p
>
639 <p
><blockquote
><pre
>
640 % host -t srv _pgpkey-http._tcp.uio.no
641 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
643 </pre
></blockquote
></p
>
646 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
647 HKP lookup protocol
</a
> supported finding signature paths, I would be
648 very happy. It can look up a given key or search for a user ID, but I
649 normally do not want that, but to find a trust path from my key to
650 another key. Given a user ID or key ID, I would like to find (and
651 download) the keys representing a signature path from my key to the
652 key in question, to be able to get a trust path between the two keys.
653 This is as far as I can tell not possible today. Perhaps something
654 for a future version of the protocol?
</p
>