Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index 73e7f1e729c6a0db1dab771e4216d105d62ab154..f6fbda990efb541befdf07552298e7ca077db50e 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -3,400 +3,429 @@
        <channel>
                <title>Petter Reinholdtsen</title>
                <description></description>
        <channel>
                <title>Petter Reinholdtsen</title>
                <description></description>

-                <link></link>
-                <atom:link href="index.rss" rel="self" type="application/rss+xml" />
+                <link>http://people.skolelinux.org/pere/blog/</link>
+                <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />

        
        <item>
        
        <item>

-               <title>MVA på bøker med DRM, ikke MVA på bøker uten DRM?</title>
-               <link>MVA_p___b__ker_med_DRM__ikke_MVA_p___b__ker_uten_DRM_.html</link>
-               <guid isPermaLink="true">MVA_p___b__ker_med_DRM__ikke_MVA_p___b__ker_uten_DRM_.html</guid>
-                <pubDate>Wed, 23 Sep 2009 10:00:00 +0200</pubDate>
+               <title>Togsatsing på norsk, mot sykkel</title>
+               <link>http://people.skolelinux.org/pere/blog/Togsatsing_p___norsk__mot_sykkel.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Togsatsing_p___norsk__mot_sykkel.html</guid>
+                <pubDate>Wed, 2 Jun 2010 23:45:00 +0200</pubDate>

                <description>
                <description>

-&lt;p&gt;Elektroniske bøker diskuteres for tiden, etter at
-&lt;a href=&quot;http://www.aftenposten.no/kul_und/litteratur/article3280914.ece&quot;&gt;bokbransjen
-hevder&lt;/a&gt; det er usikkert om de kommer til å gi ut elektroniske
-bøker så lenge det er merverdiavgift på elektroniske bøker og ikke
-på papirbøker.  I den forbindelse så jeg et interessant forslag i
-en
-&lt;a href=&quot;http://www.digi.no/php/ny_debatt.php?id=823912&quot;&gt;digi-debatt&lt;/a&gt;
-jeg hadde sans for. &quot;einarr&quot; foreslo at DRM-infiserte elektroniske
-bøker bør ha merverdiavgift, da &quot;de ikke bidrar til
-kunnskapsspredning på samme måte&quot; som papirbøker og dermed går
-imot intensjonene bak mva-fritaket.  Bøker uten DRM derimot bør ha
-mva-fritak da de &quot;kan overføres mellom enheter, leses på ulike
-plattformer, lånes ut og siteres og kopieres fra&quot; slik en kan med
-papirbøker.&lt;/p&gt;
-
-&lt;p&gt;En oppfølgerkommentar sier seg enig i dette, da DRM-infisert
-materiale må anses som leid og dermed en tjeneste, mens materiale uten
-DRM må anses som et kjøp.&lt;/p&gt;
+&lt;p&gt;Det står dårlig til med toget når en finner på å la det
+&lt;a href=&quot;http://www.aftenposten.no/nyheter/iriks/article3677060.ece&quot;&gt;kappkjøre
+med sykkel&lt;/a&gt;...  Jeg tror det trengs strukturendringer for å få
+fikset på togproblemene i Norge.&lt;/p&gt;
+
+&lt;p&gt;Mon tro hva toglinje mellom Narvik og Tromsø ville hatt slags
+effekt på området der?&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Sikkerhet til sjøs trenger sjøkart uten bruksbegresninger</title>
-               <link>Sikkerhet_til_sj__s_trenger_sj__kart_uten_bruksbegresninger.html</link>
-               <guid isPermaLink="true">Sikkerhet_til_sj__s_trenger_sj__kart_uten_bruksbegresninger.html</guid>
-                <pubDate>Sun, 23 Aug 2009 10:00:00 +0200</pubDate>
+               <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
+               <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</guid>
+                <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>

                <description>
                <description>

-&lt;p&gt;Sikkerhet til sjøs burde være noe som opptar mange etter den siste
-oljeutslippsulykken med Full City, som har drept mye liv langs sjøen.
-En viktig faktor for å bedre sikkerheten til sjøs er at alle som
-ferdes på sjøen har tilgang til oppdaterte sjøkart som forteller hvor
-det grunner og annet en må ta hensyn til på sjøen.&lt;/p&gt;
-
-&lt;p&gt;Hvis en er enig i at tilgang til oppdaterte sjøkart er viktig for
-sikkerheten på sjøen, så er det godt å vite at det i dag er teknisk
-mulig å sikre alle enkel tilgang til oppdaterte digitale kart over
-Internet.  Det trenger heller ikke være spesielt kostbart.&lt;/p&gt;
-
-&lt;p&gt;Både ved Rocknes-ulykken i Vatlestraumen, der 18 mennesker mistet
-livet, og ved Full City-ulykken utenfor Langesund, der mange tonn olje
-lekket ut i havet, var det registrert problemer relatert til
-oppdaterte sjøkart.  Ved Rocknes-ulykken var de elektroniske kartene
-som ble brukt ikke oppdatert med informasjon om nyoppdagede grunner og
-losen kjente visst ikke til disse nye grunnene.  Papirkartene var dog
-oppdaterte.  Ved Full City-ulykken hadde en kontroll av skipet noen
-uker tidligere konstatert manglende sjøkart.&lt;/p&gt;
-
-&lt;p&gt;Jeg tror en løsning der digitale sjøkart kunne lastes ned direkte
-fra sjøkartverket av alle som ønsket oppdaterte sjøkart, uten
-brukerbetaling og uten bruksbegresninger knyttet til kartene, vil
-gjøre at flere folk på sjøen vil holde seg med oppdaterte sjøkart,
-eller sjøkart i det hele tatt.  Resultatet av dette vil være økt
-sikkerhet på sjøen.  En undersøkelse gjennomført av Opinion for
-Gjensidige i 2008 fortalte at halvparten av alle båteierne i landet
-ikke har sjøkart i båten.&lt;/p&gt;
-
-&lt;p&gt;Formatet på de digitale sjøkartene som gjøræs tilgjengelig fra
-sjøkartverket må være i henhold til en fri og åpen standard, slik at
-en ikke er låst til enkeltaktørers godvilje når datafilene skal tolkes
-og forstås, men trenger ikke publiseres fra sjøkartverket i alle
-formatene til verdens skips-GPS-er i tillegg.  Hvis det ikke er
-kostbart for sjøkartverket bør de gjerne gjøre det selv, men slik
-konvertering kan andre ta seg av hvis det er et marked for det.&lt;/p&gt;
-
-&lt;p&gt;Hvis staten mener alvor med å forbedre sikkerheten til sjøs, må de
-gjøre sitt for at alle båteiere har oppdaterte kart, ikke bare snakke
-om hvor viktig det er at de har oppdaterte kart.  Det bør være
-viktigere for staten at båtene &lt;strong&gt;har&lt;/strong&gt; oppdaterte kart
-enn at de er pålagt å ha oppdaterte kart.&lt;/p&gt;
-
-&lt;p&gt;Sjøkartene er &lt;a href=&quot;http://kart.kystverket.no/&quot;&gt;tilgjengelig på web
-fra kystverket&lt;/a&gt;, men så vidt jeg har klart å finne, uten
-bruksvilkår som muliggjør gjenbruk uten bruksbegresninger.&lt;/p&gt;
-
-&lt;p&gt;OpenStreetmap.org-folk er lei av mangel på sjøkart, og har startet
-på et dugnadsbasert fribrukskart for havet,
-&lt;a href=&quot;http://openseamap.org/&quot;&gt;OpenSeaMap&lt;/a&gt;.  Datagrunnlaget er
-OpenStreetmap, mens framvisningen er tilpasset bruk på sjøen.  Det
-gjenstår mye før en kan bruke dette til å seile sikkert på havet, men
-det viser at behovet for fribruks-sjøkart er til stedet.&lt;/p&gt;
+&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
+start at boot when an NVidia video card is used is handled.  The
+problem seem to be that the nvidia X.org driver uses a long time to
+initialize, and this duration is longer than kdm is configured to
+wait.&lt;/p&gt;
+
+&lt;p&gt;I came across two bugs related to this issue,
+&lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
+against initscripts and passed on to nvidia-glx when it became obvious
+that the nvidia drivers were involved, and
+&lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
+kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
+
+&lt;p&gt;To me, it seem that no-one is interested in actually solving the
+problem nvidia video card owners experience and make sure the Debian
+distribution work out of the box for these users.  The nvidia driver
+maintainers expect kdm to be set up to wait longer, while kdm expect
+the nvidia driver maintainers to fix the driver to start faster, and
+while they wait for each other I guess the users end up switching to a
+distribution that work for them.  I have no idea what the solution is,
+but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
+
+&lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Relative popularity of document formats (MS Office vs. ODF)</title>
-               <link>Relative_popularity_of_document_formats__MS_Office_vs__ODF_.html</link>
-               <guid isPermaLink="true">Relative_popularity_of_document_formats__MS_Office_vs__ODF_.html</guid>
-                <pubDate>Wed, 12 Aug 2009 15:50:00 +0200</pubDate>
+               <title>Parallellized boot seem to hold up well in Debian/testing</title>
+               <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
+                <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>

                <description>
                <description>

-&lt;p&gt;Just for fun, I did a search right now on Google for a few file ODF
-and MS Office based formats (not to be mistaken for ISO or ECMA
-OOXML), to get an idea of their relative usage.  I searched using
-&#39;filetype:odt&#39; and equvalent terms, and got these results:&lt;/P&gt;
-
-&lt;table&gt;
-&lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;ODF&lt;/th&gt;&lt;th&gt;MS Office&lt;/th&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Tekst&lt;/td&gt; &lt;td&gt;odt:282000&lt;/td&gt; &lt;td&gt;docx:308000&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Presentasjon&lt;/td&gt; &lt;td&gt;odp:75600&lt;/td&gt; &lt;td&gt;pptx:183000&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Regneark&lt;/td&gt; &lt;td&gt;ods:26500    &lt;/td&gt; &lt;td&gt;xlsx:145000&lt;/td&gt;&lt;/tr&gt;
-&lt;/table&gt;
-
-&lt;p&gt;Next, I added a &#39;site:no&#39; limit to get the numbers for Norway, and
-got these numbers:&lt;/p&gt;
-
-&lt;table&gt;
-&lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;ODF&lt;/th&gt;&lt;th&gt;MS Office&lt;/th&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Tekst&lt;/td&gt; &lt;td&gt;odt:2480        &lt;/td&gt; &lt;td&gt;docx:4460&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Presentasjon&lt;/td&gt; &lt;td&gt;odp:299  &lt;/td&gt; &lt;td&gt;pptx:741&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Regneark&lt;/td&gt; &lt;td&gt;ods:187      &lt;/td&gt; &lt;td&gt;xlsx:372&lt;/td&gt;&lt;/tr&gt;
-&lt;/table&gt;
-
-&lt;p&gt;I wonder how these numbers change over time.&lt;/p&gt;
-
-&lt;p&gt;I am aware of Google returning different results and numbers based
-on where the search is done, so I guess these numbers will differ if
-they are conduced in another country.  Because of this, I did the same
-search from a machine in California, USA, a few minutes after the
-search done from a machine here in Norway.&lt;/p&gt;
-
-
-&lt;table&gt;
-&lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;ODF&lt;/th&gt;&lt;th&gt;MS Office&lt;/th&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Tekst&lt;/td&gt; &lt;td&gt;odt:129000&lt;/td&gt; &lt;td&gt;docx:308000&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Presentasjon&lt;/td&gt; &lt;td&gt;odp:44200&lt;/td&gt; &lt;td&gt;pptx:93900&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Regneark&lt;/td&gt; &lt;td&gt;ods:26500    &lt;/td&gt; &lt;td&gt;xlsx:82400&lt;/td&gt;&lt;/tr&gt;
-&lt;/table&gt;
-
-&lt;p&gt;And with &#39;site:no&#39;:
-
-&lt;table&gt;
-&lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;ODF&lt;/th&gt;&lt;th&gt;MS Office&lt;/th&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Tekst&lt;/td&gt; &lt;td&gt;odt:2480&lt;/td&gt; &lt;td&gt;docx:3410&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Presentasjon&lt;/td&gt; &lt;td&gt;odp:175&lt;/td&gt; &lt;td&gt;pptx:604&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;Regneark&lt;/td&gt; &lt;td&gt;ods:186      &lt;/td&gt; &lt;td&gt;xlsx:296&lt;/td&gt;&lt;/tr&gt;
-&lt;/table&gt;
-
-&lt;p&gt;Interesting difference, not sure what to conclude from these
-numbers.&lt;/p&gt;
+&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
+The feature seem to hold up pretty well, but three fairly serious
+issues are known and should be solved:
+
+&lt;p&gt;&lt;ul&gt;
+
+&lt;li&gt;The wicd package seen to
+&lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
+&lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
+parallel booting is enabled.  No idea why, but the wicd maintainer
+seem to be on the case.&lt;/li&gt;
+
+&lt;li&gt;The nvidia X driver seem to
+&lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
+triggered more easily when parallel booting is in effect.  The
+maintainer is on the case.&lt;/li&gt;
+
+&lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
+sequencing (the shutdown is broken) when old file-rc users
+&lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
+sysv-rc.  One way to solve it would be for file-rc to create
+/etc/init.d/.legacy-bootordering, and another is to try to make
+sysv-rc more robust.  Will investigate some more and probably upload a
+workaround in sysv-rc to help those trying to move from file-rc to
+sysv-rc get a working shutdown.&lt;/li&gt;
+
+&lt;/ul&gt;&lt;/p&gt;
+
+&lt;p&gt;All in all not many surprising issues, and all of them seem
+solvable before Squeeze is released.  In addition to these there are
+some packages with bugs in their dependencies and run level settings,
+which I expect will be fixed in a reasonable time span.&lt;/p&gt;
+
+&lt;p&gt;If you report any problems with dependencies in init.d scripts to
+the BTS, please usertag the report to get it to show up at
+&lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
+list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>ISO still hope to fix OOXML</title>
-               <link>ISO_still_hope_to_fix_OOXML.html</link>
-               <guid isPermaLink="true">ISO_still_hope_to_fix_OOXML.html</guid>
-                <pubDate>Sat, 8 Aug 2009 14:00:00 +0200</pubDate>
+               <title>More flexible firmware handling in debian-installer</title>
+               <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
+                <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>

                <description>
                <description>

-&lt;p&gt;According to &lt;a
-href=&quot;http://twerner.blogspot.com/2009/08/defects-of-office-open-xml.html&quot;&gt;a
-blog post from Torsten Werner&lt;/a&gt;, the current defect report for ISO
-29500 (ISO OOXML) is 809 pages.  His interesting point is that the
-defect report is 71 pages more than the full ODF 1.1 specification.
-Personally I find it more interesting that ISO still believe ISO OOXML
-can be fixed in ISO.  Personally, I believe it is broken beyon repair,
-and I completely lack any trust in ISO for being able to get anywhere
-close to solving the problems.  I was part of the Norwegian committee
-involved in the OOXML fast track process, and was not impressed with
-Standard Norway and ISO in how they handled it.&lt;/p&gt;
-
-&lt;p&gt;These days I focus on ODF instead, which seem like a specification
-with the future ahead of it.  We are working in NUUG to organise a ODF
-seminar this autumn.&lt;/p&gt;
+&lt;p&gt;After a long break from debian-installer development, I finally
+found time today to return to the project.  Having to spend less time
+working dependency based boot in debian, as it is almost complete now,
+definitely helped freeing some time.&lt;/p&gt;
+
+&lt;p&gt;A while back, I ran into a problem while working on Debian Edu.  We
+include some firmware packages on the Debian Edu CDs, those needed to
+get disk and network controllers working.  Without having these
+firmware packages available during installation, it is impossible to
+install Debian Edu on the given machine, and because our target group
+are non-technical people, asking them to provide firmware packages on
+an external medium is a support pain.  Initially, I expected it to be
+enough to include the firmware packages on the CD to get
+debian-installer to find and use them.  This proved to be wrong.
+Next, I hoped it was enough to symlink the relevant firmware packages
+to some useful location on the CD (tried /cdrom/ and
+/cdrom/firmware/).  This also proved to not work, and at this point I
+found time to look at the debian-installer code to figure out what was
+going to work.&lt;/p&gt;
+
+&lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
+look revealed that it would only look for firmware packages outside
+the installation media, so the CD was never checked for firmware
+packages.  It would only check USB sticks, floppies and other
+&quot;external&quot; media devices.  Today I changed it to also look in the
+/cdrom/firmware/ directory on the mounted CD or DVD, which should
+solve the problem I ran into with Debian edu.  I also changed it to
+look in /firmware/, to make sure the installer also find firmware
+provided in the initrd when booting the installer via PXE, to allow us
+to provide the same feature in the PXE setup included in Debian
+Edu.&lt;/p&gt;
+
+&lt;p&gt;To make sure firmware deb packages with a license questions are not
+activated without asking if the license is accepted, I extended
+hw-detect to look for preinst scripts in the firmware packages, and
+run these before activating the firmware during installation.  The
+license question is asked using debconf in the preinst, so this should
+solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
+
+&lt;p&gt;If you want to discuss the details of these features, please
+contact us on debian-boot@lists.debian.org.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Debian has switched to dependency based boot sequencing</title>
-               <link>Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
-               <guid isPermaLink="true">Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
-                <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
+               <title>Magnetstripeinnhold i billetter fra Flytoget og Hurtigruten</title>
+               <link>http://people.skolelinux.org/pere/blog/Magnetstripeinnhold_i_billetter_fra_Flytoget_og_Hurtigruten.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Magnetstripeinnhold_i_billetter_fra_Flytoget_og_Hurtigruten.html</guid>
+                <pubDate>Fri, 21 May 2010 16:00:00 +0200</pubDate>

                <description>
                <description>

-&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
-and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
-have been migrated to using dependency based boot sequencing.  This
-conclude work me and others have been doing for the last three days.
-It feels great to see this finally part of the default Debian
-installation.  Now we just need to weed out the last few problems that
-are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
-
-&lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
-fixing the more fundamental problem of handing the event based
-non-predictable kernel in the early boot.&lt;/p&gt;
+&lt;p&gt;For en stund tilbake kjøpte jeg en magnetkortleser for å kunne
+titte på hva som er skrevet inn på magnetstripene til ulike kort.  Har
+ikke hatt tid til å analysere mange kort så langt, men tenkte jeg
+skulle dele innholdet på to kort med mine lesere.&lt;/p&gt;
+
+&lt;p&gt;For noen dager siden tok jeg flyet til Harstad og Hurtigruten til
+Bergen.  Flytoget fra Oslo S til flyplassen ga meg en billett med
+magnetstripe.  Påtrykket finner jeg følgende informasjon:&lt;/p&gt;
+
+&lt;pre&gt;
+Flytoget Airport Express Train
+
+Fra - Til        : Oslo Sentralstasjon
+Kategori         : Voksen
+Pris             : Nok 170,00
+Herav mva. 8,00% : NOK 12,59
+Betaling         : Kontant
+Til - Fra        : Oslo Lufthavn
+Utstedt:         : 08.05.10
+Gyldig Fra-Til   : 08.05.10-07.11.10
+Billetttype      : Enkeltbillett
+
+102-1015-100508-48382-01-08
+&lt;/pre&gt;
+
+&lt;p&gt;På selve magnetstripen er innholdet
+&lt;tt&gt;;E?+900120011=23250996541068112619257138248441708433322932704083389389062603279671261502492655?&lt;/tt&gt;.
+Aner ikke hva innholdet representerer, og det er lite overlapp mellom
+det jeg ser trykket på billetten og det jeg ser av tegn i
+magnetstripen.  Håper det betyr at de bruker kryptografiske metoder
+for å gjøre det vanskelig å forfalske billetter.&lt;/p&gt;
+
+&lt;p&gt;Den andre billetten er fra Hurtigruten, der jeg mistenker at
+strekkoden på fronten er mer brukt enn magnetstripen (det var i hvert
+fall den biten vi stakk inn i dørlåsen).&lt;/p&gt;
+
+&lt;p&gt;Påtrykket forsiden er følgende:&lt;/p&gt;
+
+&lt;pre&gt;
+Romnummer 727
+Hurtigruten
+Midnatsol
+Reinholdtsen
+Petter
+Bookingno: SAX69   0742193
+Harstad-Bergen
+Dep: 09.05.2010 Arr: 12.05.2010
+Lugar fra Risøyhamn
+Kost: FRO=4
+&lt;/pre&gt;
+
+&lt;p&gt;På selve magnetstripen er innholdet
+&lt;tt&gt;;1316010007421930=00000000000000000000?+E?&lt;/tt&gt;.  Heller ikke her
+ser jeg mye korrespondanse mellom påtrykk og magnetstripe.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Taking over sysvinit development</title>
-               <link>Taking_over_sysvinit_development.html</link>
-               <guid isPermaLink="true">Taking_over_sysvinit_development.html</guid>
-                <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
+               <title>Pieces of the roaming laptop puzzle in Debian</title>
+               <link>http://people.skolelinux.org/pere/blog/Pieces_of_the_roaming_laptop_puzzle_in_Debian.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Pieces_of_the_roaming_laptop_puzzle_in_Debian.html</guid>
+                <pubDate>Wed, 19 May 2010 19:00:00 +0200</pubDate>

                <description>
                <description>

-&lt;p&gt;After several years of frustration with the lack of activity from
-the existing sysvinit upstream developer, I decided a few weeks ago to
-take over the package and become the new upstream.  The number of
-patches to track for the Debian package was becoming a burden, and the
-lack of synchronization between the distribution made it hard to keep
-the package up to date.&lt;/p&gt;
-
-&lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
-and my Debian co-maintainer Kel Modderman.  About 10 days ago, I made
-a new upstream tarball with version number 2.87dsf (for Debian, SuSe
-and Fedora), based on the patches currently in use in these
-distributions.  We Debian maintainers plan to move to this tarball as
-the new upstream as soon as we find time to do the merge.  Since the
-new tarball was created, we agreed with Werner at SuSe to make a new
-upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
-development there.  The project is registered and currently waiting
-for approval by the Savannah administrators, and as soon as it is
-approved, we will import the old versions from svn and continue
-working on the future release.&lt;/p&gt;
-
-&lt;p&gt;It is a bit ironic that this is done now, when some of the involved
-distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
+&lt;p&gt;Today, the last piece of the puzzle for roaming laptops in Debian
+Edu finally entered the Debian archive.  Today, the new
+&lt;a href=&quot;http://packages.qa.debian.org/libp/libpam-mklocaluser.html&quot;&gt;libpam-mklocaluser&lt;/a&gt;
+package was accepted.  Two days ago, two other pieces was accepted
+into unstable.  The
+&lt;a href=&quot;http://packages.qa.debian.org/p/pam-python.html&quot;&gt;pam-python&lt;/a&gt;
+package needed by libpam-mklocaluser, and the
+&lt;a href=&quot;http://packages.qa.debian.org/s/sssd.html&quot;&gt;sssd&lt;/a&gt; package
+passed NEW on Monday.  In addition, the
+&lt;a href=&quot;http://packages.qa.debian.org/libp/libpam-ccreds.html&quot;&gt;libpam-ccreds&lt;/a&gt;
+package we need is in experimental (version 10-4) since Saturday, and
+hopefully will be moved to unstable soon.&lt;/p&gt;
+
+&lt;p&gt;This collection of packages allow for two different setups for
+roaming laptops.  The traditional setup would be using libpam-ccreds,
+nscd and libpam-mklocaluser with LDAP or Kerberos authentication,
+which should work out of the box if the configuration changes proposed
+for nscd in &lt;a href=&quot;http://bugs.debian.org/485282&quot;&gt;BTS report
+#485282&lt;/a&gt; is implemented.  The alternative setup is to use sssd with
+libpam-mklocaluser to connect to LDAP or Kerberos and let sssd take
+care of the caching of passwords and group information.&lt;/p&gt;
+
+&lt;p&gt;I have so far been unable to get sssd to work with the LDAP server
+at the University, but suspect the issue is some SSL/GnuTLS related
+problem with the server certificate.  I plan to update the Debian
+package to version 1.2, which is scheduled for next week, and hope to
+find time to make sure the next release will include both the
+Debian/Ubuntu specific patches.  Upstream is friendly and responsive,
+and I am sure we will find a good solution.&lt;/p&gt;
+
+&lt;p&gt;The idea is to set up the roaming laptops to authenticate using
+LDAP or Kerberos and create a local user with home directory in /home/
+when a usre in LDAP logs in via KDM or GDM for the first time, and
+cache the password for offline checking, as well as caching group
+memberhips and other relevant LDAP information.  The
+libpam-mklocaluser package was created to make sure the local home
+directory is in /home/, instead of /site/server/directory/ which would
+be the home directory if pam_mkhomedir was used.  To avoid confusion
+with support requests and configuration, we do not want local laptops
+to have users in a path that is used for the same users home directory
+on the home directory servers.&lt;/p&gt;
+
+&lt;p&gt;One annoying problem with gdm is that it do not show the PAM
+message passed to the user from libpam-mklocaluser when the local user
+is created.  Instead gdm simply reject the login with some generic
+message.  The message is shown in kdm, ssh and login, so I guess it is
+a bug in gdm.  Have not investigated if there is some other message
+type that can be used instead to get gdm to also show the message.&lt;/p&gt;
+
+&lt;p&gt;If you want to help out with implementing this for Debian Edu,
+please contact us on debian-edu@lists.debian.org.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Regjerningens oppsummering av høringen om standardkatalogen versjon 2</title>
-               <link>Regjerningens_oppsummering_av_h__ringen_om_standardkatalogen_versjon_2.html</link>
-               <guid isPermaLink="true">Regjerningens_oppsummering_av_h__ringen_om_standardkatalogen_versjon_2.html</guid>
-                <pubDate>Thu, 9 Jul 2009 14:40:00 +0200</pubDate>
+               <title>Parallellized boot is now the default in Debian/unstable</title>
+               <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
+                <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>

                <description>
                <description>

-&lt;p&gt;For å forstå mer om hvorfor standardkatalogens versjon 2 ble som
-den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
-for regjeringen da de tok sin avgjørelse.  De er nå lagt ut på NUUGs
-wiki, direkte tilgjengelig via &quot;&lt;a
-href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&amp;do=get&amp;target=kongelig-resolusjon.pdf&quot;&gt;Referansekatalogen
-v2.0 - Oppsummering av høring&lt;/a&gt;&quot; og &quot;&lt;a
-href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&amp;do=get&amp;target=kongelig-resolusjon-katalogutkast.pdf&quot;&gt;Referansekatalog
-for IT-standarder i offentlig sektor Versjon 2.0, dd.mm.åååå -
-UTKAST&lt;/a&gt;&quot;.&lt;/p&gt;
-
-&lt;p&gt;Det er tre ting jeg merker meg i oppsummeringen fra
-høringsuttalelsen da jeg skummet igjennom den.  Det første er at
-forståelsen av hvordan programvarepatenter påvirker fri
-programvareutvikling også i Norge når en argumenterer med at
-royalty-betaling ikke er et relevant problem i Norge.  Det andre er at
-FAD ikke har en prinsipiell forståelse av verdien av en enkelt
-standard innenfor hvert område.  Det siste er at påstander i
-høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
-Microsoft om hvordan Ogg blir standardisert og påstanden fra
-politidirektoratet om patentproblemer i Theora).&lt;/p&gt;
+&lt;p&gt;Since this evening, parallel booting is the default in
+Debian/unstable for machines using dependency based boot sequencing.
+Apparently the testing of concurrent booting has been wider than
+expected, if I am to believe the
+&lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
+on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
+with the feature this weekend, to give us some time to detect any
+remaining problems before Squeeze is frozen.  If serious problems are
+detected, it is simple to change the default back to sequential boot.
+The upload of the new sysvinit package also activate a new upstream
+version.&lt;/p&gt;
+
+More information about
+&lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
+based boot sequencing&lt;/a&gt; is available from the Debian wiki.  It is
+currently possible to disable parallel booting when one run into
+problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
+
+&lt;blockquote&gt;&lt;pre&gt;
+CONCURRENCY=none
+&lt;/pre&gt;&lt;/blockquote&gt;
+
+&lt;p&gt;If you report any problems with dependencies in init.d scripts to
+the BTS, please usertag the report to get it to show up at
+&lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
+list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Regjerningen forlater prinsippet om ingen royalty-betaling i standardkatalogen versjon 2</title>
-               <link>Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html</link>
-               <guid isPermaLink="true">Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html</guid>
-                <pubDate>Mon, 6 Jul 2009 21:00:00 +0200</pubDate>
+               <title>Sitesummary tip: Listing MAC address of all clients</title>
+               <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
+                <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>

                <description>
                <description>

-&lt;p&gt;Jeg ble glad da regjeringen
-&lt;a href=&quot;http://www.digi.no/817635/her-er-statens-nye-it-standarder&quot;&gt;annonserte&lt;/a&gt;
-versjon 2 av
-&lt;a href=&quot;http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf&quot;&gt;statens
-referansekatalog over standarder&lt;/a&gt;, men trist da jeg leste hva som
-faktisk var vedtatt etter
-&lt;a href=&quot;http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html&quot;&gt;høringen&lt;/a&gt;.
-De fleste av de valgte åpne standardene er gode og vil bidra til at
-alle kan delta på like vilkår i å lage løsninger for staten, men
-noen av dem blokkerer for de som ikke har anledning til å benytte
-spesifikasjoner som krever betaling for bruk (såkalt
-royalty-betaling).  Det gjelder spesifikt for H.264 for video og MP3
-for lyd.  Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
-Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
-fra statens websider gjøre dette uten å måtte bruke programmer der
-betaling for bruk var nødvendig.  Når det nå er gjort valgfritt for
-de statlige etatene å bruke enten H.264 eller Theora (og MP3 eler
-Vorbis), så vil en bli tvunget til å forholde seg til
-royalty-belastede standarder for å få tilgang til videoen og
-lyden.&lt;/p&gt;
-
-&lt;p&gt;Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
-at alle standarder som ble valgt til å være påkrevd i katalogen skulle
-være uten royalty-betaling.  Jeg håper det ikke betyr at en har mistet
-all forståelse for hvilke prinsipper som må følges for å oppnå
-likeverdig konkurranse mellom aktørene i IT-bransjen.  NUUG advarte
-mot dette i
-&lt;a href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2&quot;&gt;sin
-høringsuttalelse&lt;/a&gt;, men ser ut til å ha blitt ignorert.&lt;/p&gt;
+&lt;p&gt;In the recent Debian Edu versions, the
+&lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
+system&lt;/a&gt; is used to keep track of the machines in the school
+network.  Each machine will automatically report its status to the
+central server after boot and once per night.  The network setup is
+also reported, and using this information it is possible to get the
+MAC address of all network interfaces in the machines.  This is useful
+to update the DHCP configuration.&lt;/p&gt;
+
+&lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
+ist all MAC addresses of all machines reporting to sitesummary.  Run
+this on the collector host:&lt;/p&gt;
+
+&lt;blockquote&gt;&lt;pre&gt;
+perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
+&lt;/pre&gt;&lt;/blockquote&gt;
+
+&lt;p&gt;This will list all MAC addresses assosiated with all machine, one
+line per machine and with space between the MAC addresses.&lt;/p&gt;
+
+&lt;p&gt;To allow system administrators easier job at adding static DHCP
+addresses for hosts, it would be possible to extend this to fetch
+machine information from sitesummary and update the DHCP and DNS
+tables in LDAP using this information.  Such tool is unfortunately not
+written yet.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Microsofts misvisende argumentasjon rundt multimediaformater</title>
-               <link>Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html</link>
-               <guid isPermaLink="true">Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html</guid>
-                <pubDate>Fri, 26 Jun 2009 15:30:00 +0200</pubDate>
+               <title>systemd, an interesting alternative to upstart</title>
+               <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
+                <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>

                <description>
                <description>

-&lt;p&gt;I
-&lt;a href=&quot;http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf&quot;&gt;Microsoft
-sin høringsuttalelse&lt;/a&gt; til
-&lt;a href=&quot;http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html?id=549422&quot;&gt;forslag
-til versjon 2 av statens referansekatalog over standarder&lt;/a&gt;, lirer
-de av seg følgende FUD-perle:&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;&quot;Vorbis, OGG, Theora og FLAC er alle tekniske
-  spesifikasjoner overordnet styrt av xiph.org, som er en
-  ikke-kommersiell organisasjon.  Etablerte og anerkjente
-  standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
-  innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
-  Det er derimot helt opp til hver enkelt organisasjon å bestemme
-  hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
-  spesifikasjonene bør derfor ikke defineres som åpne
-  standarder.&quot;&lt;/blockquote&gt;&lt;/p&gt;
-
-&lt;p&gt;De vokter seg vel for å nevne den anerkjente
-standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
-IP og det meste av protokoller på Internet, og RFC-standardene som
-IETF står bak.  Ogg er spesifisert i
-&lt;a href=&quot;http://ietf.org/rfc/rfc3533.txt&quot;&gt;RFC 3533&lt;/a&gt;, og er uten
-tvil å anse som en åpen standard.  Vorbis er
-&lt;a href=&quot;http://ietf.org/rfc/rfc5215.txt&quot;&gt;RFC 5215&lt;/a&gt;.  Theora er
-
-under standardisering via IETF, med
-&lt;a href=&quot;http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt&quot;&gt;siste
-utkast publisert 2006-07-21&lt;/a&gt; (riktignok er dermed teksten ikke
-skrevet i stein ennå, men det blir neppe endringer som ikke er
-bakoverkompatibel).  De kan være inne på noe når det gjelder FLAC da
-jeg ikke finner tegn til at &lt;a
-href=&quot;http://flac.sourceforge.net/format.html&quot;&gt;spesifikasjonen
-tilgjengelig på web&lt;/a&gt; er på tur via noen
-standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
-og Vorbis også har involvert seg i Flac siden 2003, så ser jeg ikke
-bort fra at også den organiseres via IETF.  Jeg kjenner personlig lite
-til FLAC.&lt;/p&gt;
-
-&lt;p&gt;Uredelig argumentasjon bør en holde seg for god til å komme med,
-spesielt når det er så enkelt i dagens Internet-hverdag å gå
-misvisende påstander etter i sømmene.&lt;/p&gt;
+&lt;p&gt;The last few days a new boot system called
+&lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
+has been
+&lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
+
+to the free software world.  I have not yet had time to play around
+with it, but it seem to be a very interesting alternative to
+&lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
+a good alternative for Debian when we are able to switch to an event
+based boot system.  Tollef is
+&lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
+systemd into Debian, and I look forward to seeing how well it work.  I
+like the fact that systemd handles init.d scripts with dependency
+information natively, allowing them to run in parallel where upstart
+at the moment do not.&lt;/p&gt;
+
+&lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
+platform support.  It only work on recent Linux kernels, and also need
+some new kernel features enabled to function properly.  This means
+kFreeBSD and Hurd ports of Debian will need a port or a different boot
+system.  Not sure how that will be handled if systemd proves to be the
+way forward.&lt;/p&gt;
+
+&lt;p&gt;In the mean time, based on the
+&lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
+on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
+decided to enable full parallel booting as the default in Debian as
+soon as possible (probably this weekend or early next week), to see if
+there are any remaining serious bugs in the init.d dependencies.  A
+new version of the sysvinit package implementing this change is
+already in experimental.  If all go well, Squeeze will be released
+with parallel booting enabled by default.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Debian boots quicker and quicker</title>
-               <link>Debian_boots_quicker_and_quicker.html</link>
-               <guid isPermaLink="true">Debian_boots_quicker_and_quicker.html</guid>
-                <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
+               <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
+               <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
+                <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>

                <description>
                <description>

-&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
-people involved in the boot system on Debian and Ubuntu, to see if we
-could find more ways to speed up the boot system.  This was an Ubuntu
-funded
-&lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
-gathering&lt;/a&gt;. It was quite productive.  We also discussed the future
-of boot systems, and ways to handle the increasing number of boot
-issues introduced by the Linux kernel becoming more and more
-asynchronous and event base.  The Ubuntu approach using udev and
-upstart might be a good way forward.  Time will show.&lt;/p&gt;
-
-&lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
-process in Debian.  All of these should be applied to get a quick
-boot:&lt;/p&gt;
-
-&lt;ul&gt;
-
-&lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
-
-&lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
-   clock is in UTC.&lt;/li&gt;
-
-&lt;li&gt;Install and activate the insserv package to enable
-   &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
-   based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
-
-&lt;/ul&gt;
-
-These points are based on the Google summer of code work done by
-&lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
-Villegas&lt;/a&gt;.
-
-&lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
-unstable yesterday.  When we tested it, we were able to cut 6 seconds
-from the boot sequence.  It depend on very correct dependency
-declaration in all init.d scripts, so I expect us to find edge cases
-where the dependences in some scripts are slightly wrong when we start
-using this.&lt;/p&gt;
-
-&lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
-introduced by Raphael Geissert today, one that could affect the
-startup speed as well.  Instead of starting some scripts concurrently
-from rcS.d/ and another set of scripts from rc2.d/, it would be
-possible to run a of them in the same process.  A quick way to test
-this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
-insserv&#39;.  Will need to test if that work. :)&lt;/p&gt;
+&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
+complete, so complete that it is actually possible to run all the
+init.d scripts in parallell based on these dependencies.  If you want
+to test your Squeeze system, make sure
+&lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
+based boot sequencing&lt;/a&gt; is enabled, and add this line to
+/etc/default/rcS:&lt;/p&gt;
+
+&lt;blockquote&gt;&lt;pre&gt;
+CONCURRENCY=makefile
+&lt;/pre&gt;&lt;/blockquote&gt;
+
+&lt;p&gt;That is it.  It will cause sysv-rc to use the startpar tool to run
+scripts in parallel using the dependency information stored in
+/etc/init.d/.depend.boot, /etc/init.d/.depend.start and
+/etc/init.d/.depend.stop to order the scripts.  Startpar is configured
+to try to start the kdm and gdm scripts as early as possible, and will
+start the facilities required by kdm or gdm as early as possible to
+make this happen.&lt;/p&gt;
+
+&lt;p&gt;Give it a try, and see if you like the result.  If some services
+fail to start properly, it is most likely because they have incomplete
+init.d script dependencies in their startup script (or some of their
+dependent scripts have incomplete dependencies).  Report bugs and get
+the package maintainers to fix it. :)&lt;/p&gt;
+
+&lt;p&gt;Running scripts in parallel could be the default in Debian when we
+manage to get the init.d script dependencies complete and correct.  I
+expect we will get there in Squeeze+1, if we get manage to test and
+fix the remaining issues.&lt;/p&gt;
+
+&lt;p&gt;If you report any problems with dependencies in init.d scripts to
+the BTS, please usertag the report to get it to show up at
+&lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
+list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;

 </description>
        </item>
        
 </description>
        </item>