Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index 7da8be61de7894ba2f7cca73e5a5e2d543e9605c..43e793bdf03ca56f0f6ab70ff937ff9f5a0dab84 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,61 @@
                 <link></link>
                 <atom:link href="index.rss" rel="self" type="application/rss+xml" />
        
                 <link></link>
                 <atom:link href="index.rss" rel="self" type="application/rss+xml" />
        

+       <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>
+               <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;
+</description>
+       </item>
+       

        <item>
                <title>Litt om valgfusk og problemet med elektronisk stemmegiving</title>
                <link>Litt_om_valgfusk_og_problemet_med_elektronisk_stemmegiving.html</link>
        <item>
                <title>Litt om valgfusk og problemet med elektronisk stemmegiving</title>
                <link>Litt_om_valgfusk_og_problemet_med_elektronisk_stemmegiving.html</link>


@@ -301,50 +356,5 @@ betydelige.&lt;/p&gt;
 </description>
        </item>
        
 </description>
        </item>
        

-       <item>
-               <title>Two projects that have improved the quality of free software a lot</title>
-               <link>Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
-               <guid isPermaLink="true">Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
-                <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
-               <description>
-&lt;p&gt;There are two software projects that have had huge influence on the
-quality of free software, and I wanted to mention both in case someone
-do not yet know them.&lt;/p&gt;
-
-&lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
-tool to detect and expose errors in the memory handling of programs.
-It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
-and it will report any problems on stdout.  It is even better if the
-program include debug information.  With debug information, it is able
-to report the source file name and line number where the problem
-occurs.  It can report things like &#39;reading past memory block in file
-X line N, the memory block was allocated in file Y, line M&#39;, and
-&#39;using uninitialised value in control logic&#39;.  This tool has made it
-trivial to investigate reproducible crash bugs in programs, and have
-reduced the number of this kind of bugs in free software a lot.
-
-&lt;p&gt;The second one is
-&lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
-a source code checker.  It is able to process the source of a program
-and find problems in the logic without running the program.  It
-started out as the Stanford Checker and became well known when it was
-used to find bugs in the Linux kernel.  It is now a commercial tool
-and the company behind it is running
-&lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
-free software community, where a lot of free software projects get
-their source checked for free.  Several thousand defects have been
-found and fixed so far.  It can find errors like &#39;lock L taken in file
-X line N is never released if exiting in line M&#39;, or &#39;the code in file
-Y lines O to P can never be executed&#39;.  The projects included in the
-community service project have managed to get rid of a lot of
-reliability problems thanks to Coverity.&lt;/p&gt;
-
-&lt;p&gt;I believe tools like this, that are able to automatically find
-errors in the source, are vital to improve the quality of software and
-make sure we can get rid of the crashing and failing software we are
-surrounded by today.&lt;/p&gt;
-</description>
-       </item>
-       

         </channel>
 </rss>
         </channel>
 </rss>