X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/d54dce693fb58b9f820a5256bae0feb23168292b..60bf8a3f215da8c82ec727e3045793dea8edd5a8:/blog/archive/2009/07/07.rss

diff --git a/blog/archive/2009/07/07.rss b/blog/archive/2009/07/07.rss
index fa26303de2..7192b0e4f3 100644
--- a/blog/archive/2009/07/07.rss
+++ b/blog/archive/2009/07/07.rss
@@ -44,5 +44,85 @@ høringsuttalelse</a>, men ser ut til å ha blitt ignorert.</p>
 </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>
+		<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;
+</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>
+		<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;
+</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>
+		<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;
+</description>
+	</item>
+	
         </channel>
 </rss>