New blog post.

diff --git a/blog/data/2014-11-22-sysvinit-jessie.txt b/blog/data/2014-11-22-sysvinit-jessie.txt
new file mode 100644 (file)
index 0000000..0928d38
--- /dev/null
+++ b/blog/data/2014-11-22-sysvinit-jessie.txt
@@ -0,0 +1,51 @@
+Title: How to stay with sysvinit in Debian Jessie
+Tags: english, debian, bootsystem
+Date: 2014-11-22 01:00
+
+<p>By now, it is well known that Debian Jessie will not be using
+sysvinit as its boot system by default.  But how can one keep using
+sysvinit in Jessie?  It is fairly easy, and here are a few recipes,
+courtesy of
+<a href="http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html">Erich
+Schubert</a> and
+<a href="http://smcv.pseudorandom.co.uk/2014/still_universal/">Simon
+McVittie</a>.
+
+<p>If you already are using Wheezy and want to upgrade to Jessie and
+keep sysvinit as your boot system, create a file
+<tt>/etc/apt/preferences.d/no-systemd</tt> with this content:</p>
+
+<p><blockquote><pre>
+Package: systemd-sysv
+Pin: release o=Debian
+Pin-Priority: -1
+</pre></blockquote><p>
+
+<p>It will tell apt and aptitude to not consider installing
+systemd-sysv as part of any installation and upgrade solution when
+resolving dependencies.  The end result should be that the upgraded
+system keep using sysvinit.</p>
+
+<p>If you are installing Jessie for the first time, there is no way to
+get sysvinit installed by default, but one can tell the installer to
+switch to sysvinit before the first boot.  Either by using a kernel
+argument to the installer, or by adding a line to the preseed file
+used.  First, the kernel command line argument:
+
+<p><blockquote><pre>
+preseed/late_command="in-target apt-get install -y sysvinit-core"
+</pre></blockquote><p>
+
+<p>Next, the preseed line needed.</p>
+
+<p><blockquote><pre>
+d-i preseed/late_command string in-target apt-get install -y sysvinit-core
+</pre></blockquote><p>
+
+<p>One can of course also do this after the first boot by installing
+the sysvinit-core package.</p>
+
+<p>I recommend only using sysvinit if you really need it, as the
+sysvinit boot sequence in Debian have several hardware specific bugs
+on Linux caused by the fact that it is unpredictable when hardware
+devices show up during boot.</p>