-
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
-
- </div>
-</div>
- <div class="padding"></div>
-
-<div class="entry">
- <div class="title">
- <a href="http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html">What should start from /etc/rcS.d/ in Debian? - almost nothing</a>
- </div>
- <div class="date">
- 2011-07-30 14:00
- </div>
-
- <div class="body">
-
-<p>In the Debian boot system, several packages include scripts that
-are started from /etc/rcS.d/. In fact, there is a bite more of them
-than make sense, and this causes a few problems. What kind of
-problems, you might ask. There are at least two problems. The first
-is that it is not possible to recover a machine after switching to
-runlevel 1. One need to actually reboot to get the machine back to
-the expected state. The other is that single user boot will sometimes
-run into problems because some of the subsystems are activated before
-the root login is presented, causing problems when trying to recover a
-machine from a problem in that subsystem. A minor additional point is
-that moving more scripts out of rcS.d/ and into the other rc#.d/
-directories will increase the amount of scripts that can run in
-parallel during boot, and thus decrease the boot time.</p>