New image for new post.

[homepage.git] / blog / archive / 2018 / 02 / 02.rss

diff --git a/blog/archive/2018/02/02.rss b/blog/archive/2018/02/02.rss
index eb6e6e8f42b2d1c73226624316e0844fd2728f8d..add6faae5d936e5f9d2e4cdb46d5cfc234048081 100644 (file)
--- a/blog/archive/2018/02/02.rss
+++ b/blog/archive/2018/02/02.rss
@@ -6,6 +6,40 @@
                 <link>http://people.skolelinux.org/pere/blog/</link>
 
        
+       <item>
+               <title>The SysVinit upstream project just migrated to git</title>
+               <link>http://people.skolelinux.org/pere/blog/The_SysVinit_upstream_project_just_migrated_to_git.html</link>        
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_SysVinit_upstream_project_just_migrated_to_git.html</guid>
+                <pubDate>Sun, 18 Feb 2018 09:20:00 +0100</pubDate>
+               <description>&lt;p&gt;Surprising as it might sound, there are still computers using the
+traditional Sys V init system, and there probably will be until
+systemd start working on Hurd and FreeBSD.
+&lt;a href=&quot;https://savannah.nongnu.org/projects/sysvinit&quot;&gt;The upstream
+project still exist&lt;/a&gt;, though, and up until today, the upstream
+source was available from Savannah via subversion.  I am happy to
+report that this just changed.&lt;/p&gt;
+
+&lt;p&gt;The upstream source is now in Git, and consist of three
+repositories:&lt;/p&gt;
+
+&lt;ul&gt;
+
+&lt;li&gt;&lt;a href=&quot;http://git.savannah.nongnu.org/cgit/sysvinit.git&quot;&gt;sysvinit&lt;/a&gt;&lt;/li&gt;
+&lt;li&gt;&lt;a href=&quot;http://git.savannah.nongnu.org/cgit/sysvinit/insserv.git&quot;&gt;insserv&lt;/a&gt;&lt;/li&gt;
+&lt;li&gt;&lt;a href=&quot;http://git.savannah.nongnu.org/cgit/sysvinit/startpar.git&quot;&gt;startpar&lt;/a&gt;&lt;/li&gt;
+
+&lt;/ul&gt;
+
+&lt;p&gt;I do not really spend much time on the project these days, and I
+has mostly retired, but found it best to migrate the source to a good
+version control system to help those willing to move it forward.&lt;/p&gt;
+
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+</description>
+       </item>
+       
        <item>
                <title>Using VLC to stream bittorrent sources</title>
                <link>http://people.skolelinux.org/pere/blog/Using_VLC_to_stream_bittorrent_sources.html</link>        
@@ -20,9 +54,10 @@ the most efficient ways to distribute large files on the Internet, and
 Webtorrent is a variant of Bittorrent using
 &lt;a href=&quot;https://webrtc.org&quot;&gt;WebRTC&lt;/a&gt; as its transport channel,
 allowing web pages to stream and share files using the same technique.
-The network protocols are not identical, so a client supporting one of
-them can not talk to a client supporting the other.  I was a bit
-surprised with what I discovered.  Looking at
+The network protocols are similar but not identical, so a client
+supporting one of them can not talk to a client supporting the other.
+I was a bit surprised with what I discovered when I started to look.
+Looking at
 &lt;a href=&quot;https://www.videolan.org/vlc/releases/3.0.0.html&quot;&gt;the release
 notes&lt;/a&gt; did not help answering this question, so I started searching
 the web.  I found several news articles from 2013, most of them