-<p>Av disse ser ID 775 og 862 mest relevant ut. ID 775 antar jeg
-refererer til fotoboksen som står like ved brua, mens
-«Reisetidsregistreringspunkt» kanskje kan være boksen som henger der.
-Hvordan finner jeg så ut hva dette kan være for noe. En titt på
-<a href="http://labs.vegdata.no/nvdb-datakatalog/862-Reisetidsregistreringspunkt/">datakatalogsiden
-for ID 862/Reisetidsregistreringspunkt</a> viser at det er finnes 53
-slike målere i Norge, og hvor de er plassert, men gir ellers få
-detaljer. Det er plassert 40 på østlandet og 13 i Trondheimsregionen.
-Men siden nevner «AutoPASS», og hvis en slår opp oppføringen på
-Sollihøgda nevner den «Ciber AS» som ID for eksternt system. (Kan det
-være snakk om
-<a href="http://www.proff.no/selskap/ciber-norge-as/oslo/internettdesign-og-programmering/Z0I3KMF4/">Ciber
-Norge AS</a>, et selskap eid av Ciber Europe Bv?) Et nettsøk på
- «Ciber AS autopass» fører meg til en artikkel fra NRK Trøndelag i
- 2013 med tittel
-«<a href="http://www.nrk.no/trondelag/sjekk-dette-hvis-du-vil-unnga-ko-1.11327947">Sjekk
-dette hvis du vil unngå kø</a>». Artikkelen henviser til vegvesenets
-nettside
-<a href="http://www.reisetider.no/reisetid/forside.html">reisetider.no</a>
-som har en
-<a href="http://www.reisetider.no/reisetid/omrade.html?omrade=5">kartside
-for Østlandet</a> som viser at det måles mellom Sandvika og Sollihøgda.
-Det kan dermed se ut til at jeg har funnet ut hva boksene gjør.</p>
-
-<p>Hvis det stemmer, så er dette bokser som leser av AutoPASS-ID-en
-til alle passerende biler med AutoPASS-brikke, og dermed gjør det mulig
-for de som kontrollerer boksene å holde rede på hvor en gitt bil er
-når den passerte et slikt målepunkt. NRK-artikkelen forteller at
-denne informasjonen i dag kun brukes til å koble to
-AutoPASS-brikkepasseringer passeringer sammen for å beregne
-reisetiden, og at bruken er godkjent av Datatilsynet. Det er desverre
-ikke mulig for en sjåfør som passerer under en slik boks å kontrollere
-at AutoPASS-ID-en kun brukes til dette i dag og i fremtiden.</p>
-
-<p>I tillegg til denne type AutoPASS-sniffere vet jeg at det også
-finnes mange automatiske stasjoner som tar betalt pr. passering (aka
-bomstasjoner), og der lagres informasjon om tid, sted og bilnummer i
-10 år. Finnes det andre slike sniffere plassert ut på veiene?</p>
-
-<p>Personlig har jeg valgt å ikke bruke AutoPASS-brikke, for å gjøre
-det vanskeligere og mer kostbart for de som vil invadere privatsfæren
-og holde rede på hvor bilen min beveger seg til enhver tid. Jeg håper
-flere vil gjøre det samme, selv om det gir litt høyere private
-utgifter (dyrere bompassering). Vern om privatsfæren koster i disse
-dager.</p>
-
-<p>Takk til Jan Kristian Jensen i Statens Vegvesen for tips om
-dokumentasjon på vegvesenets REST-API.</p>
-</description>
- </item>
-
- <item>
- <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
- <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
- <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
- <description><p>The <a href="https://www.debian.org/">Debian</a> installer could be
-a lot quicker. When we install more than 2000 packages in
-<a href="http://www.skolelinux.org/">Skolelinux / Debian Edu</a> using
-tasksel in the installer, unpacking the binary packages take forever.
-A part of the slow I/O issue was discussed in
-<a href="https://bugs.debian.org/613428">bug #613428</a> about too
-much file system sync-ing done by dpkg, which is the package
-responsible for unpacking the binary packages. Other parts (like code
-executed by postinst scripts) might also sync to disk during
-installation. All this sync-ing to disk do not really make sense to
-me. If the machine crash half-way through, I start over, I do not try
-to salvage the half installed system. So the failure sync-ing is
-supposed to protect against, hardware or system crash, is not really
-relevant while the installer is running.</p>
-
-<p>A few days ago, I thought of a way to get rid of all the file
-system sync()-ing in a fairly non-intrusive way, without the need to
-change the code in several packages. The idea is not new, but I have
-not heard anyone propose the approach using dpkg-divert before. It
-depend on the small and clever package
-<a href="https://packages.qa.debian.org/eatmydata">eatmydata</a>, which
-uses LD_PRELOAD to replace the system functions for syncing data to
-disk with functions doing nothing, thus allowing programs to live
-dangerous while speeding up disk I/O significantly. Instead of
-modifying the implementation of dpkg, apt and tasksel (which are the
-packages responsible for selecting, fetching and installing packages),
-it occurred to me that we could just divert the programs away, replace
-them with a simple shell wrapper calling
-"eatmydata&nbsp;$program&nbsp;$@", to get the same effect.
-Two days ago I decided to test the idea, and wrapped up a simple
-implementation for the Debian Edu udeb.</p>
-
-<p>The effect was stunning. In my first test it reduced the running
-time of the pkgsel step (installing tasks) from 64 to less than 44
-minutes (20 minutes shaved off the installation) on an old Dell
-Latitude D505 machine. I am not quite sure what the optimised time
-would have been, as I messed up the testing a bit, causing the debconf
-priority to get low enough for two questions to pop up during
-installation. As soon as I saw the questions I moved the installation
-along, but do not know how long the question were holding up the
-installation. I did some more measurements using Debian Edu Jessie,
-and got these results. The time measured is the time stamp in
-/var/log/syslog between the "pkgsel: starting tasksel" and the
-"pkgsel: finishing up" lines, if you want to do the same measurement
-yourself. In Debian Edu, the tasksel dialog do not show up, and the
-timing thus do not depend on how quickly the user handle the tasksel
-dialog.</p>
-
-<p><table>
-
-<tr>
-<th>Machine/setup</th>
-<th>Original tasksel</th>
-<th>Optimised tasksel</th>
-<th>Reduction</th>
-</tr>
-
-<tr>
-<td>Latitude D505 Main+LTSP LXDE</td>
-<td>64 min (07:46-08:50)</td>
-<td><44 min (11:27-12:11)</td>
-<td>>20 min 18%</td>
-</tr>
-
-<tr>
-<td>Latitude D505 Roaming LXDE</td>
-<td>57 min (08:48-09:45)</td>
-<td>34 min (07:43-08:17)</td>
-<td>23 min 40%</td>
-</tr>
-
-<tr>
-<td>Latitude D505 Minimal</td>
-<td>22 min (10:37-10:59)</td>
-<td>11 min (11:16-11:27)</td>
-<td>11 min 50%</td>
-</tr>
-
-<tr>
-<td>Thinkpad X200 Minimal</td>
-<td>6 min (08:19-08:25)</td>
-<td>4 min (08:04-08:08)</td>
-<td>2 min 33%</td>
-</tr>
-
-<tr>
-<td>Thinkpad X200 Roaming KDE</td>
-<td>19 min (09:21-09:40)</td>
-<td>15 min (10:25-10:40)</td>
-<td>4 min 21%</td>
-</tr>
-
-</table></p>
-
-<p>The test is done using a netinst ISO on a USB stick, so some of the
-time is spent downloading packages. The connection to the Internet
-was 100Mbit/s during testing, so downloading should not be a
-significant factor in the measurement. Download typically took a few
-seconds to a few minutes, depending on the amount of packages being
-installed.</p>
-
-<p>The speedup is implemented by using two hooks in
-<a href="https://www.debian.org/devel/debian-installer/">Debian
-Installer</a>, the pre-pkgsel.d hook to set up the diverts, and the
-finish-install.d hook to remove the divert at the end of the
-installation. I picked the pre-pkgsel.d hook instead of the
-post-base-installer.d hook because I test using an ISO without the
-eatmydata package included, and the post-base-installer.d hook in
-Debian Edu can only operate on packages included in the ISO. The
-negative effect of this is that I am unable to activate this
-optimization for the kernel installation step in d-i. If the code is
-moved to the post-base-installer.d hook, the speedup would be larger
-for the entire installation.</p>
-
-<p>I've implemented this in the
-<a href="https://packages.qa.debian.org/debian-edu-install">debian-edu-install</a>
-git repository, and plan to provide the optimization as part of the
-Debian Edu installation. If you want to test this yourself, you can
-create two files in the installer (or in an udeb). One shell script
-need do go into /usr/lib/pre-pkgsel.d/, with content like this:</p>